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

Deliver ViNO CR in multi-tenant type Airship Phase #106

Closed
lb4368 opened this issue Mar 3, 2021 · 0 comments
Closed

Deliver ViNO CR in multi-tenant type Airship Phase #106

lb4368 opened this issue Mar 3, 2021 · 0 comments
Assignees
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 m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]] type: multi-tenant
Milestone

Comments

@lb4368
Copy link

lb4368 commented Mar 3, 2021

Problem description
As an operator, I want to deliver a configured ViNO CR within an Airship phase of the multi-tenant site type delivery, so that I can define VMs based upon VM flavors/templates for use as nodes in Kubernetes sub-clusters.

Proposed change
The ViNO CR may be delivered as part of a target cluster workload phase. Applying one or more ViNO CRs will indicate to the ViNO operator the VMs to be created on target/management worker nodes and their associated infrastructure. Upon completion of this phase the VM infrastructure will be set up and virtual BareMetalHost (vBMH) resources will be defined with appropriate labels for use by SIP.

  1. Integrate the delivery of a customized ViNO CR into an Airship phase defined in the multi-tenant manifest type.
  2. Verify capability to run Airship phase delivering ViNO CR to the target cluster to create the required VMs with the virtual BareMetalHost (vBMH) resources defined with appropriate labels for use by SIP operator as part of a multi-tenant site deployment leveraging the multi-tenant type manifests.
@lb4368 lb4368 added enhancement New feature or request triage 2-Manifests Relates to manifest/document set related issues type: multi-tenant and removed triage labels Mar 3, 2021
@lb4368 lb4368 added this to the v2.0 milestone Mar 3, 2021
@lb4368 lb4368 added the priority/critical Items critical to be implemented, usually by the next release label Mar 3, 2021
@lb4368 lb4368 modified the milestones: v2.0, postV2.0 Mar 3, 2021
@ian-howell ian-howell self-assigned this Mar 5, 2021
@lb4368 lb4368 modified the milestones: Future, v2.1 Mar 11, 2021
@ian-howell ian-howell added the size m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]] label Mar 19, 2021
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 m 2-5 days [moderate complexity, generic code, or enhancement to existing feature]] type: multi-tenant
Projects
None yet
Development

No branches or pull requests

2 participants