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

Deploy base multi-tenant type site in STL3 #129

Closed
eak13 opened this issue Apr 28, 2021 · 5 comments
Closed

Deploy base multi-tenant type site in STL3 #129

eak13 opened this issue Apr 28, 2021 · 5 comments
Assignees
@imarijitbose
Labels
4-CI/CD Relates to issues with versioning, Zuul & gating enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release size m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]]
Projects
Airship 2.0
Milestone
v2.1

Comments

@eak13
Copy link

eak13 commented Apr 28, 2021 •
edited by lb4368

Once issue #132 has been completed & the multi-tenant type has be derived from the airship-core reference type, we want to deploy the multi-tenant type site in STL3 before adding in the sub-cluster components. This ensure that the base multi-tenant type deploys successfully and will also allow for making any necessary changes to the CI/CD pipeline to deploy the multi-tenant type site alongside the airship-core type site on an ongoing basis.
@eak13 eak13 added enhancement New feature or request triage labels Apr 28, 2021
@eak13 eak13 changed the title Deploy multi-tenant site in STL3 Deploy multi-tenant type site in STL3 Apr 28, 2021
@eak13 eak13 changed the title Deploy multi-tenant type site in STL3 Deploy base multi-tenant type site in STL3 Apr 28, 2021
@eak13 eak13 mentioned this issue Apr 28, 2021
Closed
@eak13 eak13 added this to the v2.1 milestone Apr 30, 2021
@jezogwza jezogwza added priority/critical Items critical to be implemented, usually by the next release and removed triage labels May 5, 2021
@jezogwza jezogwza added this to To do in Airship 2.0 via automation May 5, 2021
@jezogwza jezogwza added the 4-CI/CD Relates to issues with versioning, Zuul & gating label May 5, 2021
@imarijitbose
Copy link
Contributor

Assigning to me.

@imarijitbose
Copy link
Contributor

This is been verified once in the stl3. Pending PS for this : https://review.opendev.org/c/airship/treasuremap/+/790795

@imarijitbose
Copy link
Contributor

The issue has been verified once more at the current tip of treasuremap master and pinned airshipctl.
Traesuremap hash: e0a4439
airshictl : c355b600d7a3fd66f03016ad9384a13cf17e80e7

Requesting close of this issue.

@eak13
Copy link
Author

eak13 commented May 13, 2021

Closing per above

@eak13 eak13 closed this as completed May 13, 2021
Airship 2.0 automation moved this from To do to Done May 13, 2021
@eak13 eak13 added the size m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]] label May 13, 2021
@imarijitbose
Copy link
Contributor

The airshpctl hash was mentioned wrong. correct hash : e12b1e2fa639e02a54cb982d372dcdd8e3ee39de

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@imarijitbose imarijitbose

Labels
4-CI/CD Relates to issues with versioning, Zuul & gating enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release size m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]]
Projects
Airship 2.0
  
Done
Milestone
v2.1
Development

No branches or pull requests
3 participants
@eak13 @imarijitbose @jezogwza