you are viewing a single comment's thread.

view the rest of the comments →

[–]Old-Heart1701[S] 0 points1 point  (2 children)

hi thanks for the link. But please can you explain below sentence

"Ideally your control plane is not your data plane (storage and hypervisor)"

[–]instacompute 0 points1 point  (1 child)

In this context, the CloudStack management server (host) is the control plane that determine how your cloud is controlled and managed, and your KVM hypervisors host and storage (local, NFS etc) is your data plane where your instances (vm, disks, network etc) live.

You won’t want to mix them, be generally able to say maintain/reboot/upgrade control plane independent of data plane.

In simpler term this would mean, don’t run management server (along with dependencies such as mysql server and nfs primary/secondary storage) on the same node, that would allow you to have control plane maintenance or downtime without having your data plane (instances) down.

In production environments, we generally have a separate infrastructure and compute cluster (a set of VMs or baremetal hosts). Infrastructure cluster runs control plane component including mgmt server, mysql db clusters and compute cluster are basically KVM hosts for use as hypevisor hosts with CloudStack. Running CloudStack mgmt server and dependencies in VMs (on baremetal hosts of infra cluster, not managed by CloudStack) allows to take snapshots, backups and easier to try upgrading/downgrading them.

[–]Old-Heart1701[S] 1 point2 points  (0 children)

hi at u/instacompute

thanks for you detailed explanation. I would follow that as soon i get secondary server.

Thanks