Re: [openstack-dev] [ALL][requirements] A freeze is coming and you should be prepared

On 18-01-26 23:05:11, Matthew Thode wrote: > On 18-01-26 00:12:38, Matthew Thode wrote: > > On 18-01-24 22:32:27, Matthew Thode wrote: > > > On 18-01-24 01:29:47, Matthew Thode wrote: > > > > On 18-01-23 01:23:50, Matthew Thode wrote: > > > > > Requirements is freezing Friday at 23:59:59 UTC so any

Re: [openstack-dev] [tc] Technical Committee Status update, January 26th

> > Sorry. Did anyone talk about goals for Rocky in Sydney? I remember talking > about goals in Boston, I think for Queens. That worked out better since we > had a lot more lead time. > > -- > > Thanks, > > Matt > I think the problem this time around was that, until relatively recently, we o

[openstack-dev] [api] Idea for a simple way to expose compute driver capabilities in the REST API

We've talked about a type of capabilities API within nova and across OpenStack for at least a couple of years (earliest formal session I remember is a session in BCN). At the PTG in Denver, I think there was general sentiment that rather than never do anything because we can't come up with the

[openstack-dev] [keystone] Keystone Team Update - Week of 22 January 2018

# Keystone Team Update - Week of 22 January 2018 ## News ### Feature freeze This week was feature freeze and client freeze. While we approved everything we cared about for this release on time, some CI issues (some unexpected and some predictable) delayed these features being merged. The release

[openstack-dev] [nova][placement] Re: VMWare's resource pool / cluster and nested resource providers

Rado-     [+dev ML.  We're getting pretty general here; maybe others will get some use out of this.] > is there a way to make the scheduler allocate only from one specific RP     "...one specific RP" - is that Resource Provider or Resource Pool?     And are we talking about scheduling an instan

Re: [openstack-dev] [infra][all] New Zuul Depends-On syntax

Eric Fried writes: > For my part, I tried it [1] and it doesn't seem to have worked. (The > functional test failure is what the dep is supposed to have fixed.) Did > I do something wrong? > > [1] https://review.openstack.org/#/c/533821/12 If you examine the "items:" section in this file: h

Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement

2018-01-27 2:45 GMT+09:00 Jeremy Stanley : > On 2018-01-24 08:47:30 -0600 (-0600), Monty Taylor wrote: > [...] >> Horizon and neutron were updated to start publishing to PyPI >> already. >> >> https://review.openstack.org/#/c/531822/ >> >> This is so that we can start working on unwinding the neutr