[openstack-dev] [release][kolla] Announcing release of Kolla Mitaka rc3

2016-04-02 Thread Steven Dake (stdake)
Hey folks, We did a bangup job in the last 7 days fixing 25 bugs in Kolla. Our weekly capacity to solve bugs as a community is 25-30 bugs. Our final deadline is April 8th. Targeted for 2.0.0 (April 8tih) are currently 22 bugs. Many of these don't have owners, so if you want to contribute, p

[openstack-dev] Announcing release of Kolla Mitaka rc3

2016-04-02 Thread Steven Dake (stdake)
Hey folks, We did a bangup job in the last 7 days fixing 25 bugs in Kolla. Our weekly capacity to solve bugs as a community is 25-30 bugs. Our final deadline is April 8th. Targeted for 2.0.0 (April 8tih) are currently 22 bugs. Many of these don't have owners, so if you want to contribute, p

[openstack-dev] [TripleO] FreeIPA integration

2016-04-02 Thread Adam Young
I finally have enough understanding of what is going on with Tripleo to reasonably discuss how to implement solutions for some of the main security needs of a deployment. FreeIPA is an identity management solution that can provide support for: 1. TLS on all network communications: A. HTTPS

Re: [openstack-dev] [tc][kolla] Change to kolla's release model to gain access to release's website marketing

2016-04-02 Thread Steven Dake (stdake)
On 4/2/16, 1:08 PM, "Doug Hellmann" wrote: > >> On Apr 2, 2016, at 1:20 PM, Steven Dake (stdake) >>wrote: >> >> A big correction to this thread below. >> >> On 4/2/16, 10:05 AM, "Steven Dake (stdake)" wrote: >> >>> >>> >>> On 4/2/16, 10:01 AM, "Jeremy Stanley" wrote: >>> On 2016-0

Re: [openstack-dev] Acknowledging Jim Blair's work on the TC

2016-04-02 Thread Doug Hellmann
> On Apr 1, 2016, at 3:06 PM, Anita Kuno wrote: > > Jim is an incumbent on the TC this election and he didn't run. I'm > posting this to express my thanks to Jim for his work and dedication on > the TC. > > Jim, I think your commitment to open source, spanning many years before > OpenStack, and

Re: [openstack-dev] [tc][kolla] Change to kolla's release model to gain access to release's website marketing

2016-04-02 Thread Doug Hellmann
> On Apr 2, 2016, at 1:20 PM, Steven Dake (stdake) wrote: > > A big correction to this thread below. > > On 4/2/16, 10:05 AM, "Steven Dake (stdake)" wrote: > >> >> >> On 4/2/16, 10:01 AM, "Jeremy Stanley" wrote: >> >>> On 2016-04-02 16:13:28 + (+), Steven Dake (stdake) wrote: >>>

Re: [openstack-dev] [tc][kolla] Change to kolla's release model to gain access to release's website marketing

2016-04-02 Thread Doug Hellmann
> On Apr 2, 2016, at 1:01 PM, Jeremy Stanley wrote: > > On 2016-04-02 16:13:28 + (+), Steven Dake (stdake) wrote: > [...] >> I feel as though we are not permitted to participate in the >> marketing that takes place on the releases website > [...] > > I'll refrain from commenting on the

Re: [openstack-dev] [tc][kolla] Change to kolla's release model to gain access to release's website marketing

2016-04-02 Thread Steven Dake (stdake)
A big correction to this thread below. On 4/2/16, 10:05 AM, "Steven Dake (stdake)" wrote: > > >On 4/2/16, 10:01 AM, "Jeremy Stanley" wrote: > >>On 2016-04-02 16:13:28 + (+), Steven Dake (stdake) wrote: >>[...] >>> I feel as though we are not permitted to participate in the >>> marketing

Re: [openstack-dev] [tc][kolla] Change to kolla's release model to gain access to release's website marketing

2016-04-02 Thread Steven Dake (stdake)
On 4/2/16, 10:01 AM, "Jeremy Stanley" wrote: >On 2016-04-02 16:13:28 + (+), Steven Dake (stdake) wrote: >[...] >> I feel as though we are not permitted to participate in the >> marketing that takes place on the releases website >[...] > >I'll refrain from commenting on the rest since I'

Re: [openstack-dev] [tc][kolla] Change to kolla's release model to gain access to release's website marketing

2016-04-02 Thread Jeremy Stanley
On 2016-04-02 16:13:28 + (+), Steven Dake (stdake) wrote: [...] > I feel as though we are not permitted to participate in the > marketing that takes place on the releases website [...] I'll refrain from commenting on the rest since I'm not a member of the release team, but I *seriously* ho

[openstack-dev] [tc][kolla] Change to kolla's release model to gain access to release's website marketing

2016-04-02 Thread Steven Dake (stdake)
Technical Committee, Please accept my change prior to our April 8th deadline for tagging Mitaka 2.0.0 of Kolla. To be clear, this is a clunky workaround but I feel as though we are not permitted to participate in the marketing that takes place on the releases website, and this is the lesser of

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

2016-04-02 Thread Qiming Teng
> parameters: > env: >type: string >default: prod > > is_prod: > type: boolean > default: {equals: {get_param, env}} > > From an interface standpoint this seems much cleaner and more intuitive than > the other solutions discussed IMHO, but I suspect it's potentially harder t

[openstack-dev] [ptl] [security][tc] Tidy up language in section 5 of the vulnerability:managed tag

2016-04-02 Thread Steven Dake (stdake)
Apologies for not copying the [ptl] tag, since this change affects mostly the PTLs and the projects for which they facilitate. Note PTL's the purpose of this change is to make your lives easier and streamline the VMT application process, but keep the spirit of the original requirement in place.

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

2016-04-02 Thread Kai Qiang Wu
+ 1 for Eli :) Thanks Best Wishes, Kai Qiang Wu (吴开强 Kennan) IBM China System and Technology Lab, Beijing E-mail: wk...@cn.ibm.com Tel: 86-10-82451647 Address: Building 28(Ring Building), ZhongGuanCun Software Par

Re: [openstack-dev] Acknowledging Jim Blair's work on the TC

2016-04-02 Thread Morgan Fainberg
On Fri, Apr 1, 2016 at 12:06 PM, Anita Kuno wrote: > Jim is an incumbent on the TC this election and he didn't run. I'm > posting this to express my thanks to Jim for his work and dedication on > the TC. > > Jim, I think your commitment to open source, spanning many years before > OpenStack, and

Re: [openstack-dev] [Neutron][python-neutronclient] Adding new options to the existing Neutron CLIs

2016-04-02 Thread Akihiro Motoki
2016-03-18 12:06 GMT+09:00 reedip banerjee : > Dear All Neutron Developers and Reviewers, > > I have a query/concern related to the parsing of options in > python-neutronclient. > I would like to bring this up, as it "may" also impact the transition of the > CLIs to the openstack client as well. >

Re: [openstack-dev] [bifrost][ironic][release] missing build artifacts

2016-04-02 Thread Doug Hellmann
Excerpts from Julia Kreger's message of 2016-04-01 18:21:24 -0400: > On Fri, Apr 1, 2016 at 4:48 PM, Doug Hellmann wrote: > > > Excerpts from Doug Hellmann's message of 2016-04-01 16:25:07 -0400: > > > Ironic/Bifrost team, > > > > > > > > > It would be good to understand what your intent is for

Re: [openstack-dev] [monasca][release] missing build artifacts

2016-04-02 Thread Doug Hellmann
Excerpts from Hochmuth, Roland M's message of 2016-04-02 01:35:35 +: > Hi Doug, You had mentioned issues with three repos: > > 1. monasca-ceilometer > 2. monasca-log-api > 3. monasca-thresh > > All the repos that have Python code I believe are in reasonable shape with > respect to the Python

Re: [openstack-dev] [congress][release] missing build artifacts

2016-04-02 Thread Doug Hellmann
Excerpts from Tim Hinrichs's message of 2016-04-01 22:46:59 +: > Hi Doug, > > Thanks for letting us know. Here's what we're intending... > - We'd like to release the server code for Mitaka. > - We release the client to Pypi, so that's already taken care of. > - We haven't moved our docs off o

Re: [openstack-dev] [magnum] Split k8s-client in separate python package

2016-04-02 Thread Davanum Srinivas
Hongbin, Here's what i came up with based on your feedback: https://review.openstack.org/#/c/300729/ Thanks, Dims On Fri, Apr 1, 2016 at 6:19 PM, Hongbin Lu wrote: > Dims, > > Thanks for splitting the k8sclient code out. Below is my answer to your > question. > > - Should this be a new opensta