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

Provide way to define/override Vino sub-cluster VM flavor definitions & apply to STL3 #170

Open
eak13 opened this issue Jun 7, 2021 · 2 comments
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 size s <=1 days [refactor, 1 function, documentation]
Milestone

Comments

@eak13
Copy link

eak13 commented Jun 7, 2021

Sub-cluster VM flavors are defined in https://github.com/airshipit/vino/blob/master/config/manager/flavors.yaml for ViNO to use when creating the sub-cluster VMs. We need the ability to define/override the control plane & worker flavor settings at least at a type level within Treasuremap and then have them consumed by ViNO at sub-cluster creation time.

Specifically for STL3, we need the following configurations:
image

Tasks:

  1. Provide manifests/template where user can define control plane & work node VM definitions based on https://github.com/airshipit/vino/blob/master/config/manager/flavors.yaml. At a minimum, this will be needed for the multi-tenant type.
  2. Provide a mechanism for passing the VM definitions to ViNO to be used in defining the sub-cluster VMs
  3. Validate ViNO defines the sub-cluster VMs using the specified flavors in STL3
@eak13 eak13 added enhancement New feature or request triage labels Jun 7, 2021
@drewwalters96 drewwalters96 self-assigned this Jun 7, 2021
@drewwalters96 drewwalters96 added the size s <=1 days [refactor, 1 function, documentation] label Jun 7, 2021
@drewwalters96
Copy link
Contributor

@jezogwza jezogwza added 2-Manifests Relates to manifest/document set related issues and removed triage labels Jun 9, 2021
@jezogwza jezogwza added this to the v2.1 milestone Jun 9, 2021
@jezogwza jezogwza added the priority/critical Items critical to be implemented, usually by the next release label Jun 9, 2021
@drewwalters96
Copy link
Contributor

The current approach will work with the new version of ViNO. This change is ready for review but has been rebased on Kostiantyn's uplift PS: https://review.opendev.org/c/airship/treasuremap/+/796014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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 size s <=1 days [refactor, 1 function, documentation]
Projects
None yet
Development

No branches or pull requests

3 participants