rg>"
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: Adam Lawson mailto:alaw...@aqorn.com>>
Date: Wednesday, March 2, 201
Linux Systems Engineer
> GoDaddy
>
> From: Edgar Magana
> Date: Wednesday, March 2, 2016 at 4:31 PM
> To: Adam Lawson , "
> openstack-operators@lists.openstack.org" <
> openstack-operators@lists.openstack.org>
> Subject: Re: [Openstack-operators] Workload Ma
gt;"
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: Adam Lawson mailto:alaw...@aqorn.com>>
Date: Wednesday, March 2, 2016 at 1:48 PM
To:
"o
rs@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 is balanced across hosts. My 64 million dollar question is: Has anyone
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 V
