Coming from vmware environments where vcenter has almost always been a hosted vm. You could give mgmt node highest priority over other VMs, but safe approach as you stated is to keep it outside. Environment I am stand up is going to be very light use and wanting to keep infrastructure as light as possible.
2 KVM hosts 1 mgmt hosts (as it seems now) ceph cluster for shared stroage (overkill, but I need redundancy and ability to grow if we expand foot print) On Thu, Jun 20, 2019 at 3:09 PM Andrija Panic <andrija.pa...@gmail.com> wrote: > In short, > > Never, EVER, do such thing (especially in production of any kind). > > Mgmt server (any auxiliary components like standalone DB server, billing > software, monitoring software, load balancers etc - all things that are > needed for production...) can be on KVM nodes, but a standalone KVM nodes, > which are NOT managed by CloudStack. Whether you use VMM from Linux > Desktop, plain/manual management via libvirt and "nano" etc...all good as > long as not managed by ACS - you want to avoid cyclic dependency and mgmt > server issues due to high host usage/overload, etc, etc, etc. > > Regards, > Andrija > > > > > On Thu, Jun 20, 2019, 20:48 <jesse.wat...@gmail.com> wrote: > > > How are most of you running your management node? On a standalone host(s) > > outside hypervisors? On managed hypervisor hosts? > > > > What I want to do is have management node on kvm hosts that it manages. > > What I am not certain is how I get it in there in 1st place. Other than > > standing up a temporary mgmt node, get it managing the kvm hosts. Then > > stand new mgmt node from with in. > > > > Thoughts recommendations, I'm wondering about best practice and worst > case > > scenario where all hosts lose power (dr different issue in itself). How > > will I start mgmt node if there is no mgmt node to start it. virsh start > > mgmtnnode? > > > > TIA, > > > > Jesse > > >
