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

developer friendly gate hook scripts #32

Closed
alanmeadows opened this issue Feb 10, 2020 · 4 comments
Closed

developer friendly gate hook scripts #32

alanmeadows opened this issue Feb 10, 2020 · 4 comments
Assignees
Labels
devops Relates to automation, testing, and build infrastructure enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release ready for review Change related to the issue is ready for review
Projects
Milestone

Comments

@alanmeadows
Copy link
Contributor

Problem description (if applicable)
The airshipctl end-to-end test is currently launched by Zuul infrastructure. We need to ensure these same gates can act as developer friendly scripts to launch a virtualized airshipctl environment locally.

Proposed change
While the ansible gate playbooks can be launched by hand with a series of flags and environmental settings, we need to make this more approachable to new developers. This issue proposes a series of simple idempotent scripts that developers can run which will exercise the gate locally, without Zuul infrastructure, e.g.

tools/gate/01_create_iso.sh
tools/gate/02_launch_ephemeral_node.sh
...

Potential impacts
None

@alanmeadows alanmeadows added enhancement New feature or request component/cicd labels Feb 10, 2020
@teoyaomiqui
Copy link
Contributor

We have decided that we will use bash for that, correct? because right now there is some work going on around ansible roles instead of bash

@alanmeadows
Copy link
Contributor Author

I think the point here is that these simple bash scripts could simply call the ansible roles that are being created. It provides a simple way for developers unfamiliar with ansible, the right environment variables, flags, and so on to set to be able to use those roles.

@ianpittwood ianpittwood added devops Relates to automation, testing, and build infrastructure and removed component/cicd labels Feb 11, 2020
@realsystem
Copy link

@ian-howell ian-howell added wip Work in progress ready for review Change related to the issue is ready for review and removed wip Work in progress labels Feb 25, 2020
@jezogwza jezogwza added triage Needs evaluation by project members priority/critical Items critical to be implemented, usually by the next release and removed triage Needs evaluation by project members labels Mar 4, 2020
@jezogwza jezogwza added this to To do in Airship 2.0 via automation Mar 4, 2020
@jezogwza jezogwza added this to the betav1 milestone Mar 4, 2020
airshipbot pushed a commit that referenced this issue Mar 6, 2020
Change-Id: Ia3f0e1461149f4ff887f965dd5b5a00fe2f8f04b
@realsystem
Copy link

scripts has been merged long time ago, closing

Airship 2.0 automation moved this from To do to Done Apr 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Relates to automation, testing, and build infrastructure enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release ready for review Change related to the issue is ready for review
Projects
Airship 2.0
  
Done
Development

No branches or pull requests

6 participants