airshipit / treasuremap

Reference Airship manifests, CICD, and reference architecture.
http://openstack.org
Apache License 2.0
52 stars 39 forks source link

Spike: Verify Triple Nested Virtualization of ViNO BMH CR Will Work in Zuul #133

Closed lb4368 closed 3 years ago

lb4368 commented 3 years ago

As the ViNO and SIP operators are introduced into the multi-tenant site type for creating sub-clusters, we will need a way to run the sub-cluster build in our Zuul gates. This will required triple nested virtualization as Zuul runs within a VM, and the target cluster nodes are deployed as VMs within Zuul, and VMs are created when a ViNO CR is deployed to the target cluster nodes to be used by sub-clusters.

This spike issue is for verifying that this setup can be used for gating the creation of sub-clusters within the multi-tenant site type.

  1. Validate that triple nested VM setup will work in Zull
  2. Verify that Ironic will boot the sub-cluster VMs and that the VMs will be working and available.

Reference template for creating libvirt domains: a. https://github.com/airshipit/airshipctl/blob/master/roles/libvirt-domain/defaults/main.yaml#L94-L193

lb4368 commented 3 years ago

Moving this to treasuremap

sreejithpunnapuzha commented 3 years ago

Default domain configuration is having host-passthrough already (https://github.com/airshipit/airshipctl/blob/master/roles/libvirt-domain/defaults/main.yaml#L92). triple nested virtualization should work well. will check the gates once vino manifests are merged

sirajyasin commented 3 years ago

Now that the vino is added part of the multi-tenant type, we can verify if it gets deployed and if vino can launch a VM. However there are issues with multi-tenant type gate scripts and it stuck at deploy control plane ephemeral stage. Once the gating issues are resolved, will check back on the vino status in virtual-network-cloud site.

lb4368 commented 3 years ago

@sirajyasin @sreejithpunnapuzha - It has been decided that this is no longer needed in the immediate future so closing this issue. We will re-open at some point if necessary.