Mailing List Archive

Not availability zones, but host aggregates. See https://docs.openstack.org/nova/latest/user/aggregates.html.

Bernd

> On Jul 1, 2018, at 22:52, Satish Patel <satish.txt@gmail.com> wrote:
>
> Folks,
>
> Recently we build openstack for production and i have question related
> flavor metadata.
>
> I have 3 kind of servers 8 core / 32 core / 40 core servers, now i
> want to tell my openstack my one of specific application always go to
> 32 core machine, how do i tell that to flavor metadata?
>
> Or should i use availability zone option and create two group?
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

I would recommend using availability zones for this.

Torin Woltjer

Grand Dial Communications - A ZK Tech Inc. Company

616.776.1066 ext. 2006
www.granddial.com

----------------------------------------
From: Satish Patel <satish.txt@gmail.com>
Sent: 7/1/18 9:56 AM
To: openstack <openstack@lists.openstack.org>
Subject: [Openstack] flavor metadata
Folks,

Recently we build openstack for production and i have question related
flavor metadata.

I have 3 kind of servers 8 core / 32 core / 40 core servers, now i
want to tell my openstack my one of specific application always go to
32 core machine, how do i tell that to flavor metadata?

Or should i use availability zone option and create two group?

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Now i am confused, what is the best option and can you give me example
how should i use them?

~S

On Mon, Jul 2, 2018 at 8:48 AM, Torin Woltjer
<torin.woltjer@granddial.com> wrote:
> I would recommend using availability zones for this.
>
> Torin Woltjer
>
> Grand Dial Communications - A ZK Tech Inc. Company
>
> 616.776.1066 ext. 2006
> www.granddial.com
>
> ________________________________
> From: Satish Patel <satish.txt@gmail.com>
> Sent: 7/1/18 9:56 AM
> To: openstack <openstack@lists.openstack.org>
> Subject: [Openstack] flavor metadata
> Folks,
>
> Recently we build openstack for production and i have question related
> flavor metadata.
>
> I have 3 kind of servers 8 core / 32 core / 40 core servers, now i
> want to tell my openstack my one of specific application always go to
> 32 core machine, how do i tell that to flavor metadata?
>
> Or should i use availability zone option and create two group?
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

The purpose of availability zones is segregating your servers so that
downtime of a group of servers doesn't affect another group of servers.
Such as, servers in different buildings or hooked up to different power
lines. Important detail: A server can be in a single availability zone
at most.

This is not the same as segregating servers according to their
capabilities. For example, you may want to categorize your servers by
core numbers, storage type and network bandwidth. In this case, a server
may be in three groups: the 24-core group, the SSD group and the 40Gbit
group. For that, you need host aggregates.

Nova documentation tells you how to use host aggregates
https://docs.openstack.org/nova/latest/user/aggregates.html.

Bernd Bausch

On 7/2/2018 10:31 PM, Satish Patel wrote:
> Now i am confused, what is the best option and can you give me example
> how should i use them?
>
> ~S
>
> On Mon, Jul 2, 2018 at 8:48 AM, Torin Woltjer
> <torin.woltjer@granddial.com> wrote:
>> I would recommend using availability zones for this.
>>
>> Torin Woltjer
>>
>> Grand Dial Communications - A ZK Tech Inc. Company
>>
>> 616.776.1066 ext. 2006
>> www.granddial.com
>>
>> ________________________________
>> From: Satish Patel <satish.txt@gmail.com>
>> Sent: 7/1/18 9:56 AM
>> To: openstack <openstack@lists.openstack.org>
>> Subject: [Openstack] flavor metadata
>> Folks,
>>
>> Recently we build openstack for production and i have question related
>> flavor metadata.
>>
>> I have 3 kind of servers 8 core / 32 core / 40 core servers, now i
>> want to tell my openstack my one of specific application always go to
>> 32 core machine, how do i tell that to flavor metadata?
>>
>> Or should i use availability zone option and create two group?
>>
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Bernd has this right.

Host aggregates (sometimes called Haggs) is the right soluton to this
problem. You can setup a flavor to only run on a certain hagg.

This works well (in production, at scale).

On Sun, Jul 1, 2018 at 7:52 AM, Satish Patel <satish.txt@gmail.com> wrote:

> Folks,
>
> Recently we build openstack for production and i have question related
> flavor metadata.
>
> I have 3 kind of servers 8 core / 32 core / 40 core servers, now i
> want to tell my openstack my one of specific application always go to
> 32 core machine, how do i tell that to flavor metadata?
>
> Or should i use availability zone option and create two group?
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>