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.

Sign up for GitHub

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

Jump to bottom

Release workflows should spin up temporary AWS instances #284

Open
arm4b opened this issue Jun 14, 2017 · 2 comments
Open

Release workflows should spin up temporary AWS instances #284

arm4b opened this issue Jun 14, 2017 · 2 comments
Labels
enhancement

Comments

@arm4b
Copy link
Member

arm4b commented Jun 14, 2017 •
edited
Loading

Current Release workflows should spin-up + destroy temporary nodes when it's neeeded, instead of relying on oudated & always running ubuntu-build002 ubuntu-build003 ubuntu-build-itest001 slave nodes.

If provisioning a new node from 0 is not an option, - use at least pre-packed AMIs (start/destroy).
@arm4b arm4b mentioned this issue Jun 14, 2017
Open
@arm4b
Copy link
Member Author

arm4b commented Jun 14, 2017 •
edited
Loading

Related: #283 when there is outdated Mongo 2.4 is installed on those old nodes

@bigmstone
Copy link
Contributor

This also somehow seems far less complex than relying on the build slaves and consul.

@arm4b arm4b changed the title 'st2cd.mistral_release_candidate' should spin up temporary AWS instances Release workflows should spin up temporary AWS instances Jun 20, 2017
@arm4b arm4b removed the bug label Jun 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arm4b @bigmstone