Open Stack

> On Dec 19, 2016, at 5:24 PM, Kimball, Conrad <conrad.kimball at boeing.com> wrote:
> 
> Hi All,
>  
> What mechanisms does OpenStack provide that would enable me to implement behaviors analogous to AWS EC2 dedicated instances and dedicated hosts?
>  
> ·         Dedicated instances:  an OpenStack tenant can deploy VM instances that are guaranteed to not share a compute host with any other tenant (for example, as the tenant I want physical segregation of my compute).

I don’t think this type of thing exists yet (unless you’re talking bare-metal / Ironic).

> ·         Dedicated hosts: goes beyond dedicated instances, allowing an OpenStack tenant to explicitly place only specific VM instances onto the same compute host (for example, as the tenant I want to place VMs foo and bar onto the same compute host to share a software license that is licensed per host).

http://docs.openstack.org/newton/config-reference/compute/schedulers.html#samehostfilter

>  
> Conrad Kimball
> Associate Technical Fellow
> Chief Architect, Enterprise Cloud Services
> Engineering, Operations & Technology / Information Technology / Core Infrastructure Engineering
> conrad.kimball at boeing.com <mailto:conrad.kimball at boeing.com>
> P.O. Box 3707, Mail Code 7M-TE
> Seattle, WA  98124-2207
> Bellevue 33-11 bldg, office 3A6-3.9
> Mobile:  425-591-7802
>  
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org <mailto:OpenStack-operators at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20161219/3a305051/attachment.html>