Re: [Openstack-operators] Workload Management (post-instantiation)

2016-03-02 Thread Adam Lawson
s Lindgren > Senior Linux Systems Engineer > GoDaddy > > From: Edgar Magana <edgar.mag...@workday.com> > Date: Wednesday, March 2, 2016 at 4:31 PM > To: Adam Lawson <alaw...@aqorn.com>, " > openstack-operators@lists.openstack.org" < > openstack-oper

Re: [Openstack-operators] Workload Management (post-instantiation)

2016-03-02 Thread Kris G. Lindgren
ck-operators@lists.openstack.org>" <openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>> Subject: Re: [Openstack-operators] Workload Management (post-instantiation) We have done it with nagios checks and customize ruby code. Edgar From: Ada

Re: [Openstack-operators] Workload Management (post-instantiation)

2016-03-02 Thread Edgar Magana
quot; <openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>> Subject: [Openstack-operators] Workload Management (post-instantiation) Hello fellow Ops-minded stackers! I understand OpenStack uses scheduler logic to place a VM on a host to ensure the load

[Openstack-operators] Workload Management (post-instantiation)

2016-03-02 Thread Adam Lawson
Hello fellow Ops-minded stackers! I understand OpenStack uses scheduler logic to place a VM on a host to ensure the load is balanced across hosts. My 64 million dollar question is: Has anyone identified a way to monitor capacity across all hosts on an ongoing basis and automatically live migrate