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

Rename network-cloud type to multi-tenant type #97

Closed
eak13 opened this issue Feb 24, 2021 · 5 comments
Closed

Rename network-cloud type to multi-tenant type #97

eak13 opened this issue Feb 24, 2021 · 5 comments
Assignees
@manojkva
Labels
2-Manifests Relates to manifest/document set related issues enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release triage
Milestone
v2.0

Comments

@eak13
Copy link

eak13 commented Feb 24, 2021

In an effort to include sub-cluster support functions, the network-core type needs to be renamed multi-tenant and all impacted manifests should be updated to reference multi-tenant vs. network-cloud.

A new network-cloud type will be created in the future which will provide Open Stack Helm support but will not necessarily include the sub-cluster functionality.

https://github.com/airshipit/treasuremap/tree/v2/manifests/type/network-cloud
@eak13 eak13 added enhancement New feature or request triage labels Feb 24, 2021
@eak13 eak13 added this to the v2.0 milestone Feb 24, 2021
@eak13 eak13 added 2-Manifests Relates to manifest/document set related issues priority/critical Items critical to be implemented, usually by the next release labels Feb 24, 2021
@eak13 eak13 mentioned this issue Feb 24, 2021
Closed
@manojkva
Copy link
Contributor

Please assign it to me. Thanks

@eak13
Copy link
Author

eak13 commented Feb 25, 2021

@manojkva all yours!

@manojkva
Copy link
Contributor

manojkva commented Mar 2, 2021

Fix : https://review.opendev.org/c/airship/treasuremap/+/777526

@lb4368
Copy link

lb4368 commented Mar 3, 2021

@manojkva - Patchset is merged. Can we close this issue?

@lb4368
Copy link

lb4368 commented Mar 3, 2021

Patchset merged so closing.

@lb4368 lb4368 closed this as completed Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@manojkva manojkva

Labels
2-Manifests Relates to manifest/document set related issues enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release triage
Projects
None yet
Milestone
v2.0
Development

No branches or pull requests
3 participants
@manojkva @lb4368 @eak13