Open Stack

Thank you Chris.

CUSTOM_PHYSNET1 - custom Traits name , but the value should be something like ens160 for NIC.

How that NIC value is assigned to CUSTOM_PHYSNET1.

-----Original Message-----
From: Chris Dent [mailto:cdent+os at anticdent.org] 
Sent: Tuesday, October 10, 2017 7:32 PM
To: openstack at lists.openstack.org
Subject: Re: [Openstack] Use of CUSTOM Traits

On Tue, 10 Oct 2017, Ramu, MohanX wrote:

> Please let me know, what is the main purpose of Custom Traits, can we use for assigning some value to traits. If yes, how?

You can't assign a value to a trait. The trait is the value. You're assigning the trait to a resource provider. If it is a custom trait, you may need to create it first.

You can think of traits like a tag: it describes a qualitative aspect of the resource provider it is associated with. So while a disk can have 2000 GB, it either is or is not an SSD.

If you haven't had a chance to read
http://specs.openstack.org/openstack/nova-specs/specs/pike/implemented/resource-provider-traits.html
that may be of some help.

Also: https://developer.openstack.org/api-ref/placement/#traits

So, with custom traits, the idea is that there is some qualitative "trait" that is specific ("custom") to your environment. One of the ways this been discussed as being useful is associating a NIC to a physical network: CUSTOM_PHYSNET1

For more on that see this spec that is under consideration:

     https://review.openstack.org/#/c/510244/

it plans to make extensive use of custom traits.

-- 
Chris Dent                      (⊙＿⊙')         https://anticdent.org/
freenode: cdent                                         tw: @anticdent