Hello!
When I setup a KVM host, I notice that if I create new subnets or VLANs that they are not available on the host when I deploy a pod even if I add them manually to the host in question.
Is this intended behaviour?
Thank you!
Hello!
When I setup a KVM host, I notice that if I create new subnets or VLANs that they are not available on the host when I deploy a pod even if I add them manually to the host in question.
Is this intended behaviour?
Thank you!
Hi @pfak, welcome to the MAAS Discourse.
Can you share more details about your setup? What MAAS version are you using, what OS are you deploying etc.?
Ubuntu 18.04, 2.6.2-7841-ga10625be3-0ubuntu1~18.04.1
Once you have updated the configuration, you should redeploy the KVM host (note this will destroy any workloads on there).
We have docs on KVM hosts (pods) - https://maas.io/docs/kvm-introduction have you worked through those?
Thank you for clarifying my understanding of networking with KVM pods.
Has the team thought of changing this at all? As you might imagine tearing everything down on a server might not be possible in many cases. Therefore you can’t add a vlan.
I guess I understand the issue given MAAS doesn’t configure the OS once it has been deployed but in the case if running a KVM micro cloud it seems like a big issue. If I add a tenant to my cloud on a separate VLAN all partially deployed KVM hosts are off limits for deployments of their non-allocated cores. If I want to fix it I need to drain them all. Seems onerous. Am I thinking of this the wrong way?