OpenNebula CAPONE support

[raider444]

Hi, OpenNebula provides its CAPI provider CAPONE. As I can understand the main idea is to integrate cloud controller to control plane. Is it possible to integrate it?

[prometherion]

Hey 👋🏻 thanks for opening the discussion: this is the right place to discuss how to integrate Kamaji's CP Provider with Infrastructure ones!

It seems the CAPONE Provider automatically assigns a floating IP from the External Router, if it's provided:
https://github.com/OpenNebula/cluster-api-provider-opennebula/blob/491455b4759a976527345ed2c88e388f3f997c10/internal/controller/onecluster_controller.go#L208-L212

I'm not an expert on CAPONE, your help would be appreciated: is VirtualRouter used just for the Control Plane, or does it have a dependency also for Worker Nodes?

[raider444]

Thanks for quick answer, @prometherion!

It is hard to say. I'm just planning the infrastructure and looking for solutions for my project. I'll give you more context when I create some MVP environment with OpenNebula.

[prometherion]

No worries, take your time! At first sight, it seems the external router is just used for Control Plane machines: https://github.com/OpenNebula/cluster-api-provider-opennebula/blob/491455b4759a976527345ed2c88e388f3f997c10/internal/controller/onemachine_controller.go#L154-L163

If that's true, Kamaji could be easily integrated: we also have support for testing the dynamic patching of CAPI Infrastructure Clusters without changing the code.

cluster-api-control-plane-provider-kamaji/main.go

Lines 57 to 59 in 08ceb49

	flagSet.StringSliceVar(&dynamicInfraClusters, "dynamic-infrastructure-clusters", nil, "When the DynamicInfrastructureClusterPatch feature flag is enabled, "+
	"allows specifying which Infrastructure Clusters can be dynamically patched. "+
	"This feature is useful for developers of custom or non public Cluster API infrastructure providers.")

[raider444]

Hi, @prometherion!

After some research I found that virtual router is used only as proxy and load balancer for control plane. Also another virtual router instance is initialized when you request load balancer, but it is a job of cloud control manager.

No worries, take your time! At first sight, it seems the external router is just used for Control Plane machines: https://github.com/OpenNebula/cluster-api-provider-opennebula/blob/491455b4759a976527345ed2c88e388f3f997c10/internal/controller/onemachine_controller.go#L154-L163

If that's true, Kamaji could be easily integrated: we also have support for testing the dynamic patching of CAPI Infrastructure Clusters without changing the code.

cluster-api-control-plane-provider-kamaji/main.go

Lines 57 to 59 in 08ceb49

	flagSet.StringSliceVar(&dynamicInfraClusters, "dynamic-infrastructure-clusters", nil, "When the DynamicInfrastructureClusterPatch feature flag is enabled, "+
	"allows specifying which Infrastructure Clusters can be dynamically patched. "+
	"This feature is useful for developers of custom or non public Cluster API infrastructure providers.")