Update qa-scenario-2a (SOC-10460) #3711
Conversation
gosipyan
force-pushed
the
update_scenario-2a
branch
from
f2d3076 to
fc479f6
Compare
| @@ -222,19 +208,6 @@ proposals: | |||
| heat-server: | |||
| - cluster:services | |||
|
|
|||
| - barclamp: ceilometer | |||
There was a problem hiding this comment.
Why are you removing Ceilometer from the scenario?
There was a problem hiding this comment.
during prechecks if monasca is missing upgrade wont go further unless i remove ceilometer and as such case already covered in qa-scenario-8a(deploying monasca) I decided remove it from here ,other option would be deploy monasca , but because not enough nodes avaible i think it would be complicated .
There was a problem hiding this comment.
Ah, ok. I was wondering about that because I created dedicated precheck clean scenarios in #3682 which is a little...starved for reviews... :-)
What do we do about this? Merge the dedicated scenarios or remove all precheck breakers from the existing ones (in that case there'd be more things to change). I for one would prefer having dedicated upgrade scenarios in order to continue testing the barclamps that are still supported on Cloud 8 for Cloud 8 rather than disabling them for regular Cloud 8 (i.e. in non-upgrade situations) as well.
There was a problem hiding this comment.
I wanted do two things together fix broken scenario in general for SOC8 and make them working for upgrade so we dont need duplicate
I expect those scenarios under cloud8 run only for upgrade porpuse I dont think we would use them for anything else .
There was a problem hiding this comment.
Ok. Then I'll +1 this for now, since I have none of the non-precheck fixes in my pull request. We may need a follow-up to take care of Aodh, Trove and more Ceilometer occurences as well though (unless someone has taken care of that in the time since I created #3682 ; haven't checked).
gosipyan
force-pushed
the
update_scenario-2a
branch
from
fc479f6 to
f034c77
Compare
gosipyan
force-pushed
the
update_scenario-2a
branch
from
f034c77 to
97d41a9
Compare
Deploy cluster on 3 node Use mysql for database Add scenario with CA certs
gosipyan
force-pushed
the
update_scenario-2a
branch
from
97d41a9 to
9f1974b
Compare
|
tested here for ssl case https://ci.suse.de/view/Cloud/view/QA/job/cloud-mkphyscloud-qa-scenario-2a/34/parameters/ |
| hawk-server: | ||
| - "@@data1@@" | ||
| - "@@data2@@" | ||
|
|
||
| - barclamp: pacemaker | ||
| name: network |
There was a problem hiding this comment.
why did we loose a dedicated network cluster?
There was a problem hiding this comment.
we have only enough nodes for 2 clusters(with 3 nodes) I can remove data and add network back if you think its better coverage /scenario
There was a problem hiding this comment.
No. Lets leave it like this if there are no more nodes available.
Deploy cluster on 3 node
Use mysql for database
Add scenario with CA certs