Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multinode deployments #7

Open
gbraad opened this issue Mar 25, 2016 · 3 comments
Open

Support multinode deployments #7

gbraad opened this issue Mar 25, 2016 · 3 comments

Comments

@gbraad
Copy link

gbraad commented Mar 25, 2016

Currently tested deployments are based on a single node, either using the standard all-in-one or a scenario.

@dmsimard
Copy link
Contributor

So, this is a tricky one.
The scope of WeIRDO is to run gate jobs outside of the gate to improve our CI coverage.

Right now, none of the implemented projects (packstack, puppet-openstack, kolla) have multi-node jobs upstream.

I do not want to implement custom jobs in WeIRDO. If we want to test multi node, it will need to follow the right path and be done upstream first.

I know it is possible and @EmilienM looked into it a while back for puppet openstack jobs but it gets a bit hard.

We can definitely keep this issue opened for when upstream starts testing multi node.

@gbraad
Copy link
Author

gbraad commented Mar 28, 2016

I agree with your viewpoint that this is something that needs to be upstream; however for both PackStack and Kolla a multi-node deployment is possible to realize. Just not so sure how this can be achieved and implemented at the OpenStack infrastructure.

@dmsimard
Copy link
Contributor

I believe upstream multinode will be facilitated by zuul v3 -- at which point they actually intend to get rid of Jenkins as it will no longer be necessary. There's more details available about it here: https://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html

We're talking Ocata timeframe for Zuul v3 unless significant effort is put towards it in the meantime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants