Re: [openstack-dev] [nova] os-capabilities library created

2016-08-16 Thread Chris Dent
On Tue, 16 Aug 2016, Alex Xu wrote: There are two solutions in my mind 1. There aren't different dependence for traits, that is easy. The validation API in the placement engine API is enough. 2. There are different dependence for traits. We need API for compute node report those dependence.

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-15 Thread Alex Xu
2016-08-16 7:31 GMT+08:00 Jay Pipes : > On 08/15/2016 03:57 AM, Alex Xu wrote: > >> 2016-08-15 12:56 GMT+08:00 Yingxin Cheng > >: >> >> >> Hi, >> >> I'm concerned with the dependencies between "os-capabilities" >>

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-15 Thread Jay Pipes
On 08/15/2016 03:57 AM, Alex Xu wrote: 2016-08-15 12:56 GMT+08:00 Yingxin Cheng >: Hi, I'm concerned with the dependencies between "os-capabilities" library and all the other OpenStack services such as Nova, Placement,

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-15 Thread Jay Pipes
On 08/15/2016 12:56 AM, Yingxin Cheng wrote: Hi, I'm concerned with the dependencies between "os-capabilities" library and all the other OpenStack services such as Nova, Placement, Ironic, etc. Rather than embedding the universal "os-capabilities" in Nova, Cinder, Glance, Ironic services that

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-15 Thread Alex Xu
2016-08-15 12:56 GMT+08:00 Yingxin Cheng : > Hi, > > I'm concerned with the dependencies between "os-capabilities" library and > all the other OpenStack services such as Nova, Placement, Ironic, etc. > > Rather than embedding the universal "os-capabilities" in Nova,

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-14 Thread Yingxin Cheng
Hi, I'm concerned with the dependencies between "os-capabilities" library and all the other OpenStack services such as Nova, Placement, Ironic, etc. Rather than embedding the universal "os-capabilities" in Nova, Cinder, Glance, Ironic services that will introduce complexities if the library

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-14 Thread Jay Pipes
Word up, Travis :) A few comments inline, but overall I'm looking forward to collaborating with you, Steve, and all the other Searchlight contributors on os-capabilities (or os-caps as Sean wants to rename it ;) On 08/11/2016 08:00 PM, Tripp, Travis S wrote: [Graffit] was originally

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-12 Thread Mooney, Sean K
> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Friday, August 12, 2016 2:20 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova] os-capabilities library created > > On 08/12/2016 04:05 AM, Daniel P. Berrange w

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-12 Thread Jay Pipes
On 08/12/2016 04:05 AM, Daniel P. Berrange wrote: On Wed, Aug 03, 2016 at 07:47:37PM -0400, Jay Pipes wrote: Hi Novas and anyone interested in how to represent capabilities in a consistent fashion. I spent an hour creating a new os-capabilities Python library this evening:

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-12 Thread Jay Pipes
On 08/12/2016 07:49 AM, Jim Rollenhagen wrote: On Thu, Aug 11, 2016 at 9:03 PM, Jay Pipes wrote: On 08/11/2016 05:46 PM, Clay Gerrard wrote: On Thu, Aug 11, 2016 at 2:25 PM, Ed Leafe > wrote: Overall this looks good, although

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-12 Thread Jim Rollenhagen
On Thu, Aug 11, 2016 at 9:03 PM, Jay Pipes wrote: > On 08/11/2016 05:46 PM, Clay Gerrard wrote: >> >> On Thu, Aug 11, 2016 at 2:25 PM, Ed Leafe > > wrote: >> >> >> Overall this looks good, although it seems a bit odd to have >>

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-12 Thread Daniel P. Berrange
On Wed, Aug 03, 2016 at 07:47:37PM -0400, Jay Pipes wrote: > Hi Novas and anyone interested in how to represent capabilities in a > consistent fashion. > > I spent an hour creating a new os-capabilities Python library this evening: > > http://github.com/jaypipes/os-capabilities > > Please see

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-11 Thread Jay Pipes
On 08/11/2016 05:50 PM, John Dickinson wrote: On 3 Aug 2016, at 16:47, Jay Pipes wrote: Hi Novas and anyone interested in how to represent capabilities in a consistent fashion. I spent an hour creating a new os-capabilities Python library this evening:

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-11 Thread Jay Pipes
On 08/11/2016 05:25 PM, Ed Leafe wrote: On Aug 3, 2016, at 6:47 PM, Jay Pipes wrote: Please see the README for examples of how the library works and how I'm thinking of structuring these capability strings and symbols. I intend os-capabilities to be the place where the

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-11 Thread Jay Pipes
On 08/11/2016 05:46 PM, Clay Gerrard wrote: On Thu, Aug 11, 2016 at 2:25 PM, Ed Leafe > wrote: Overall this looks good, although it seems a bit odd to have ALL_CAPS_STRINGS to represent all:caps:strings throughout. The example you gave:

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-11 Thread Tripp, Travis S
Excerpts from Jay Pipes's message of 2016-08-03 19:47:37 -0400: >> Hi Novas and anyone interested in how to represent capabilities in a >> consistent fashion. >> >> I spent an hour creating a new os-capabilities Python library this evening: > >>

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-11 Thread Ed Leafe
On Aug 11, 2016, at 5:29 PM, John Dickinson wrote: >> I will let Jay speak for himself (as if I could somehow prevent that!), but >> the intent here is that this won’t be for Nova specifically; it is targeted >> primarily for the forthcoming placement service (you might know it as

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-11 Thread John Dickinson
On 11 Aug 2016, at 15:14, Ed Leafe wrote: > On Aug 11, 2016, at 4:50 PM, John Dickinson wrote: > >> Is this intended to be a cross-project thing? The message is tagged >> "[nova]", so I'm kinda surprised I saw it, but the library seems to be >> called openstack capabilities. So

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-11 Thread Ed Leafe
On Aug 11, 2016, at 4:50 PM, John Dickinson wrote: > Is this intended to be a cross-project thing? The message is tagged "[nova]", > so I'm kinda surprised I saw it, but the library seems to be called openstack > capabilities. So if this is going to be a big thing for everyone,

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-11 Thread Clint Byrum
Excerpts from Jay Pipes's message of 2016-08-03 19:47:37 -0400: > Hi Novas and anyone interested in how to represent capabilities in a > consistent fashion. > > I spent an hour creating a new os-capabilities Python library this evening: > > http://github.com/jaypipes/os-capabilities > > Please

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-11 Thread John Dickinson
On 3 Aug 2016, at 16:47, Jay Pipes wrote: > Hi Novas and anyone interested in how to represent capabilities in a > consistent fashion. > > I spent an hour creating a new os-capabilities Python library this evening: > > http://github.com/jaypipes/os-capabilities > > Please see the README for

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-11 Thread Clay Gerrard
On Thu, Aug 11, 2016 at 2:25 PM, Ed Leafe wrote: > > Overall this looks good, although it seems a bit odd to have > ALL_CAPS_STRINGS to represent all:caps:strings throughout. The example you > gave: > > >>> print os_caps.HW_CPU_X86_SSE42 > hw:cpu:x86:sse42 > > Just to be clear,

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-11 Thread Ed Leafe
On Aug 3, 2016, at 6:47 PM, Jay Pipes wrote: > Please see the README for examples of how the library works and how I'm > thinking of structuring these capability strings and symbols. I intend > os-capabilities to be the place where the OpenStack community catalogs and >

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-10 Thread Chris Dent
On Wed, 3 Aug 2016, Jay Pipes wrote: Let me know what you think about the structure of the library and whether you would be interested in owning additions to the library of constants in your area of expertise. Seems mostly sane to me. I don't really care for the inspection of sys.modules (or

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-05 Thread Jim Rollenhagen
>> On Aug 4, 2016, at 10:48, Jay Pipes wrote: >> >>> On 08/04/2016 10:31 AM, Jim Rollenhagen wrote: >>> On Wed, Aug 03, 2016 at 07:47:37PM -0400, Jay Pipes wrote: >>> Hi Novas and anyone interested in how to represent capabilities in a >>> consistent fashion. >>> >>> I

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-04 Thread Jay Pipes
On 08/04/2016 10:31 AM, Jim Rollenhagen wrote: On Wed, Aug 03, 2016 at 07:47:37PM -0400, Jay Pipes wrote: Hi Novas and anyone interested in how to represent capabilities in a consistent fashion. I spent an hour creating a new os-capabilities Python library this evening:

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-04 Thread Jim Rollenhagen
On Wed, Aug 03, 2016 at 07:47:37PM -0400, Jay Pipes wrote: > Hi Novas and anyone interested in how to represent capabilities in a > consistent fashion. > > I spent an hour creating a new os-capabilities Python library this evening: > > http://github.com/jaypipes/os-capabilities > > Please see

[openstack-dev] [nova] os-capabilities library created

2016-08-03 Thread Jay Pipes
Hi Novas and anyone interested in how to represent capabilities in a consistent fashion. I spent an hour creating a new os-capabilities Python library this evening: http://github.com/jaypipes/os-capabilities Please see the README for examples of how the library works and how I'm thinking of