Yiping
I've done this before - several times in very large environments.
I'm not certain why you require a restart of VMs. Restart of VMs will
not reflect the change in cloudstack resources until you modify the DB.
If you want for mem.overprovisiong to take effect, you would need to
modify for e
I sent the following on Dec 15 2015 to the dev list
To my knowledge no one took any interest at the time but perhaps we
could work on this or point out where I am too picky.
Ron
http://docs.cloudstack.apache.org/en/latest/concepts.html#deployment-archi
I wouldn't recommend to skip basic zone set-up. It is much simpler to
start with it to get basic knowledge of CS net configuration process. I
also had many troubles during set-up, but remembering those days I would
say - I didn't have enough knowledge of hypervisor network layer at that
time. P
Hi,
Before I dig through that I was just wondering if maybe it's really just a
networking issue. Here's how my network is setup right now:
a. Management server cluster running galera sitting behind a gateway that NATs
port 8080 to a HAproxy load balancer. All public traffic that is a result
HVs will be running XS and the primary storage is an EQL SAN via iSCSI.
Is it advisable to have two different NFS shares, one with a SATA array for
snapshots and one with a faster array for template deployment? Or is it a
complete waste of resources?
The storage network runs on 10GbE.
