Open Stack

Hi Kris,

When using aggregates as an example, anyone can assign
workloadA<>aggregateA and workloadB<>aggregateB. That's easy. But if we
have outstanding requests for workloadB and have a glut of capacity in
aggregateA, workloadB won't be able to use those hosts so we have spare
capacity and no way to utilize it.

So I want to set an affinity for workloads and not at the host level. That
way, hosts remain fungible, workload affinity policies are respected and
cloud capacity is properly utilizing capacity.

Does that make sense?

//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

On Wed, Mar 2, 2016 at 3:08 PM, Kris G. Lindgren <klindgren at godaddy.com>
wrote:

> You can set attributes on flavors that must match the attributes on hosts
> or the host aggregates.  So you can basically always make sure a specific
> flavors goes to a specific compute node or type (like disks=ssd or
> class=gpu).  Look at nova flavor extra_specs documentation and the
> aggregate_Instance_extra_specs under the scheduler options.
>
>
> ___________________________________________________________________
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy
>
> From: "Fox, Kevin M" <Kevin.Fox at pnnl.gov>
> Date: Wednesday, March 2, 2016 at 3:58 PM
> To: Adam Lawson <alawson at aqorn.com>, "
> openstack-operators at lists.openstack.org" <
> openstack-operators at lists.openstack.org>
> Subject: Re: [Openstack-operators] Setting affinity based on instance type
>
> you usually do that on an instance level with server groups. do you have
> an example where you might want to do it at the flavor level?
>
> Thanks,
> Kevin
> ------------------------------
> *From:* Adam Lawson [alawson at aqorn.com]
> *Sent:* Wednesday, March 02, 2016 2:48 PM
> *To:* openstack-operators at lists.openstack.org
> *Subject:* [Openstack-operators] Setting affinity based on instance type
>
> I'm sure this is possible but I'm trying to find the info I need in the
> docs so I figured I'd pitch this to you guys while I continue looking:
>
> Is it possible to set an affinity/anti-affinity policy to ensure instance
> Type A is weighted for/against co-location on the same physical host with
> instance Type B?
>
> Basically I have no requirement for server-group affinity but rather to
> ensure specific workloads are as separate as possible.
>
> Thoughts?
>
> //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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160302/9088a4e1/attachment.html>