We have done it with nagios checks and customize ruby code. Edgar
From: Adam Lawson <alaw...@aqorn.com<mailto:alaw...@aqorn.com>> Date: Wednesday, March 2, 2016 at 1:48 PM To: "openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>" <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 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 VM's as needed to ensure hosts resource consumption is balanced over time? It seems the scheduler addresses capacity at the time of instantiation but there's nothing that addresses optimal usage AFTER the VM is initially placed. Thoughts/experiences? //adam Adam Lawson AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1 302-387-4660 Direct: +1 916-246-2072
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
