Skip to content

Conversation

@ibrokethecloud
Copy link
Collaborator

Problem:

Improve hardware utilisation by allowing nested harvester clusters to be provisioned by seeder by using VM's and kubevirt BMC to allow VM's to be managed as inventory

Solution:

The PR introduces two new types

  • InventoryTemplates - Allow a user to create and register VM based inventory in an existing seeder cluster. This is achieved by creating VM's from an InventoryTemplate and subsequently registering the VM's via Inventory construct in seeder. The VM's leverage kubevirt bmc to allow redfish/ipmi based power operations. InventoryTemplates can exist on their own, in which case they can be used like normal inventory by manually creating clusters
  • NestedClusters - Allow a user to create Harvester clusters running in VM on top of existing Harvester clusters. NestedClusters leverage InventoryTemplates which allow users to define VMs managed as Inventory, and the newly provisioned Inventory is added to a cluster with the same name as NestedCluster. The lifecycle of InventoryTemplates in this case is managed by the NestedCluster, and deletion of NestedCluster will trigger cleanup of associated Cluster, InventoryTemplates, Inventory and VM's.

Related Issue(s):

Test plan:

Additional documentation or context

provisoining of VM based Harvester clusters via seeder

Signed-off-by: Gaurav Mehta <gaurav.mehta@suse.com>
@khushboo-rancher
Copy link

This looks great!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants