Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On Mon, Aug 1, 2016, at 08:08 AM, Jay Pipes wrote: > On 07/31/2016 10:03 PM, Alex Xu wrote: > > 2016-07-28 22:31 GMT+08:00 Jay Pipes > >: > > > > On 07/20/2016 11:25 PM, Alex Xu wrote: > > > > One more for end users: Capabilities

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Monday, August 1, 2016 1:09 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage > Capabilities with ResourceProvider > >

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 07/31/2016 10:03 PM, Alex Xu wrote: 2016-07-28 22:31 GMT+08:00 Jay Pipes >: On 07/20/2016 11:25 PM, Alex Xu wrote: One more for end users: Capabilities Discovery API, it should be 'GET /resource_providers/tags'. Or a

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

Nova-spec is submitted: https://review.openstack.org/345138, welcome review and comments! 2016-07-11 19:08 GMT+08:00 Alex Xu : > This propose is about using ResourceProviderTags as a solution to manage > Capabilities (Qualitative) in ResourceProvider. > The ResourceProviderTags

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-28 22:31 GMT+08:00 Jay Pipes : > On 07/20/2016 11:25 PM, Alex Xu wrote: > >> One more for end users: Capabilities Discovery API, it should be 'GET >> /resource_providers/tags'. Or a proxy API from nova to the placement >> API? >> > > I would imagine that it should

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 07/20/2016 11:25 PM, Alex Xu wrote: One more for end users: Capabilities Discovery API, it should be 'GET /resource_providers/tags'. Or a proxy API from nova to the placement API? I would imagine that it should be a `GET /resource-providers/{uuid}/capabilities` call on the placement

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-20 11:43 GMT-07:00 Mooney, Sean K <sean.k.moo...@intel.com>: > > > > -Original Message- > > From: Jay Pipes [mailto:jaypi...@gmail.com] > > Sent: Wednesday, July 20, 2016 7:16 PM > > To: openstack-dev@lists.openstack.org > >

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-20 11:08 GMT-07:00 Jay Pipes : > On 07/18/2016 01:45 PM, Matt Riedemann wrote: > >> On 7/15/2016 8:06 PM, Alex Xu wrote: >> >>> >>> Actually I still think aggregates isn't good for Manage Caps, just as I >>> said in previous reply about Aggregates. One of reason is

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Wednesday, July 20, 2016 7:16 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage > Capabilities with ResourceProvider > >

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 07/13/2016 01:37 PM, Ed Leafe wrote: On Jul 11, 2016, at 6:08 AM, Alex Xu wrote: For example, the capabilities can be defined as: COMPUTE_HW_CAP_CPU_AVX COMPUTE_HW_CAP_CPU_SSE COMPUTE_HV_CAP_LIVE_MIGRATION COMPUTE_HV_CAP_LIVE_SNAPSHOT (

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 07/18/2016 01:45 PM, Matt Riedemann wrote: On 7/15/2016 8:06 PM, Alex Xu wrote: Actually I still think aggregates isn't good for Manage Caps, just as I said in previous reply about Aggregates. One of reason is just same with #2 you said :) And It's totally not managable. User is even no way

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-18 13:45 GMT-07:00 Matt Riedemann : > On 7/15/2016 8:06 PM, Alex Xu wrote: > >> >> Actually I still think aggregates isn't good for Manage Caps, just as I >> said in previous reply about Aggregates. One of reason is just same with >> #2 you said :) And It's

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 7/15/2016 8:06 PM, Alex Xu wrote: Actually I still think aggregates isn't good for Manage Caps, just as I said in previous reply about Aggregates. One of reason is just same with #2 you said :) And It's totally not managable. User is even no way to query a specific host in which

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-14 10:38 GMT+08:00 Cheng, Yingxin : > > On 7/14/16, 05:42, "Ed Leafe" wrote: > On Jul 12, 2016, at 2:43 AM, Cheng, Yingxin > wrote: > > 4. Capabilities are managed/grouped/abstracted by namespaces, and > scheduler

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 7/14/16, 12:18, "Edward Leafe" wrote: On Jul 13, 2016, at 9:38 PM, Cheng, Yingxin wrote: >>Thinking about that a bit, it would seem that a host aggregate could also be represented as a namespace:name tag. That makes sense, since the fact

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On Jul 13, 2016, at 9:38 PM, Cheng, Yingxin wrote: >>Thinking about that a bit, it would seem that a host aggregate could also >> be represented as a namespace:name tag. That makes sense, since the fact >> that a host belongs to a particular aggregate is a

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 7/14/16, 05:42, "Ed Leafe" wrote: On Jul 12, 2016, at 2:43 AM, Cheng, Yingxin wrote: > 4. Capabilities are managed/grouped/abstracted by namespaces, and scheduler can make decisions based on either cap_names or cap_namespaces > 5.

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On Jul 12, 2016, at 2:43 AM, Cheng, Yingxin wrote: > 4. Capabilities are managed/grouped/abstracted by namespaces, and scheduler > can make decisions based on either cap_names or cap_namespaces > 5. Placement service DON’T have any specific knowledge of a capability, it

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On Jul 11, 2016, at 6:08 AM, Alex Xu wrote: > For example, the capabilities can be defined as: > > COMPUTE_HW_CAP_CPU_AVX > COMPUTE_HW_CAP_CPU_SSE > > COMPUTE_HV_CAP_LIVE_MIGRATION > COMPUTE_HV_CAP_LIVE_SNAPSHOT > > > ( The COMPUTE means this

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

Some thoughts of “Capability” use cases: 1. Nova-compute service can discover host capabilities and tag them into its compute-node resource provider record. 2. Other services such as ironic and cinder may want to manage its resource pool, and they can tag capabilities themselves to that pool. 3.

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

Matt mentioned Aggregate in the scheduler meeting, that is good question and also reminder me I should explain the relationship between Aggregate and ResourceProviderTags. The Aggregate is expected to keep as a tool for group the hosts, and just for group hosts. People used to manage Capabilities

[openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

This propose is about using ResourceProviderTags as a solution to manage Capabilities (Qualitative) in ResourceProvider. The ResourceProviderTags is to describe the capabilities which are defined by OpenStack Service (Compute Service, Storage Service, Network Service etc.) and by users. The