Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

2016-11-09 Thread Dean Troyer
On Tue, Nov 8, 2016 at 4:12 PM, Gage Hugo wrote: > The idea is that a cloud admin could define a list of keys that they need > for their setup within keystone's configuration file, then only those keys > will be valid for storing values in the project properties table. Then

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

2016-11-08 Thread Matt Riedemann
On 11/8/2016 7:14 PM, Adrian Turjak wrote: On 09/11/16 11:12, Gage Hugo wrote: This spec was discussed at the keystone meeting today and during the conversation that continued afterwards, an idea of using the keystone configuration to set a list of keys was mentioned. The idea is that a

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

2016-11-08 Thread Adrian Turjak
On 09/11/16 11:12, Gage Hugo wrote: > This spec was discussed at the keystone meeting today and during the > conversation that continued afterwards, an idea of using the keystone > configuration to set a list of keys was mentioned. > > The idea is that a cloud admin could define a list of keys

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

2016-11-08 Thread Matt Riedemann
On 11/8/2016 4:12 PM, Gage Hugo wrote: This spec was discussed at the keystone meeting today and during the conversation that continued afterwards, an idea of using the keystone configuration to set a list of keys was mentioned. The idea is that a cloud admin could define a list of keys that

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

2016-11-08 Thread gordon chung
On 04/11/16 08:15 PM, Steve Martinelli wrote: > > We have somewhat had support for this, we have an "extras" column > defined in our database schema, whatever a user puts in a request that > doesn't match up with our API, those key-values are dumped into the > "extras" column. It's not a

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

2016-11-08 Thread Gage Hugo
This spec was discussed at the keystone meeting today and during the conversation that continued afterwards, an idea of using the keystone configuration to set a list of keys was mentioned. The idea is that a cloud admin could define a list of keys that they need for their setup within keystone's

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

2016-11-06 Thread Matt Riedemann
On 11/4/2016 7:15 PM, Steve Martinelli wrote: The keystone team has a new spec being proposed for the Ocata release, it essentially boils down to adding properties / metadata for projects (for now) [1]. We have somewhat had support for this, we have an "extras" column defined in our database

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

2016-11-06 Thread Adrian Turjak
On 06/11/16 13:17, Steve Martinelli wrote: > > Interesting, I'll add this to the review and see how some if the folks > proposing the new APIs would find that as suitable for their use > cases. For reference: http://developer.openstack.org/api-ref/compute/ For our use case, I need key:value

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

2016-11-05 Thread Steve Martinelli
On Sat, Nov 5, 2016 at 6:15 PM, Jay Pipes wrote: > On 11/05/2016 01:15 AM, Steve Martinelli wrote: > >> The keystone team has a new spec being proposed for the Ocata release, >> it essentially boils down to adding properties / metadata for projects >> (for now) [1]. >> > >

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

2016-11-05 Thread Jay Pipes
On 11/05/2016 01:15 AM, Steve Martinelli wrote: The keystone team has a new spec being proposed for the Ocata release, it essentially boils down to adding properties / metadata for projects (for now) [1]. Yes, I'd seen that particular spec review and found it interesting in a couple ways.

[openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

2016-11-04 Thread Steve Martinelli
The keystone team has a new spec being proposed for the Ocata release, it essentially boils down to adding properties / metadata for projects (for now) [1]. We have somewhat had support for this, we have an "extras" column defined in our database schema, whatever a user puts in a request that