On 06/09/2014 12:47 PM, Joe Cropper wrote:
There may also be specific software entitlement issues that make it useful to deterministically know which host your VM will be placed on. This can be quite common in large organizations that have certain software that can be tied to certain hardware or hardware with certain # of CPU capacity, etc.
Sure, agreed. However the "cloudy" way of doing things (as opposed to the enterprise IT/managed hosting way of doing things) is to rely on abstractions like host aggregates and not allow details of the physical host machine to leak out of the public cloud API.
Best, -jay
On Mon, Jun 9, 2014 at 11:32 AM, Chris Friesen <chris.frie...@windriver.com <mailto:chris.frie...@windriver.com>> wrote: On 06/09/2014 07:59 AM, Jay Pipes wrote: On 06/06/2014 08:07 AM, Murray, Paul (HP Cloud) wrote: Forcing an instance to a specific host is very useful for the operator - it fulfills a valid use case for monitoring and testing purposes. Pray tell, what is that valid use case? I find it useful for setting up specific testcases when trying to validate things....put *this* instance on *this* host, put *those* instances on *those* hosts, now pull the power plug on *this* host...etc. I wouldn't expect the typical openstack end-user to need it though. Chris _________________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.__org <mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
