Open Stack

Not aware of an easy answer for #1, without creating a flavor or image with metadata on it and adding specific hosts to a host_aggregate that has the same metadata on it.
http://docs.openstack.org/kilo/config-reference/content/section_compute-scheduler.html - Look at isolatedhostfilter or the aggregate_instance_extra_specs and the config example for specifying a compute host with SSD’s.


#2 just sounds like affinity/anti-affinity rules? Combined with #1.

ServerGroupAffinityFilter
The ServerGroupAffinityFilter ensures that an instance is scheduled on to a host from a set of group hosts. To take advantage of this filter, the requester must create a server group with anʼ/span>affinityʼ/span>policy, and pass a scheduler hint, usingʼ/span>groupʼ/span>as the key and the server group UUID as the value. Using theʼ/span>novaʼ/span>command-line tool, use theʼ/span>--hintʼ/span>flag. For example:
$ nova server-group-create --policy affinity group-1
$ nova boot --image IMAGE_ID --flavor 1 --hint group=SERVER_GROUP_UUID server-1
ServerGroupAntiAffinityFilter
The ServerGroupAntiAffinityFilter ensures that each instance in a group is on a different host. To take advantage of this filter, the requester must create a server group with anʼ/span>anti-affinityʼ/span>policy, and pass a scheduler hint, usinggroupʼ/span>as the key and the server group UUID as the value. Using theʼ/span>novaʼ/span>command-line tool, use theʼ/span>--hintʼ/span>flag. For example:
$ nova server-group-create --policy anti-affinity group-1
$ nova boot --image IMAGE_ID --flavor 1 --hint group=SERVER_GROUP_UUID server-1

___________________________________________________________________
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy

From: "Kimball, Conrad" <conrad.kimball at boeing.com>
Date: Monday, December 19, 2016 at 3:24 PM
To: "openstack-operators at lists.openstack.org" <openstack-operators at lists.openstack.org>
Subject: [Openstack-operators] Analogs of EC2 dedicated instances & dedicated hosts?

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).


·         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).

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20161219/e2c6fb8b/attachment.html>