Re: [openstack-dev] [Ironic] When to bump the microversion?

2015-06-06 Thread Alex Xu
2015-06-05 5:35 GMT+08:00 Devananda van der Veen : > > On Jun 4, 2015 11:11 AM, "Chris Friesen" > wrote: > > > > On 06/04/2015 10:14 AM, Devananda van der Veen wrote: > >> > >> > >> On Jun 4, 2015 8:57 AM, "Monty Taylor" > > > > >> > So, seriously - let's grow up and start telling people that t

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

2015-06-06 Thread Alex Xu
2015-06-05 19:35 GMT+08:00 Sean Dague : > On 06/05/2015 01:28 AM, Adrian Otto wrote: > > > >> On Jun 4, 2015, at 11:03 AM, Devananda van der Veen > >> mailto:devananda@gmail.com>> wrote: > >> > >> > >> On Jun 4, 2015 12:00 AM, "Xu, Hejie" >> > wrote: > >> > > >> > H

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

2015-06-06 Thread Alex Xu
2015-06-04 22:23 GMT+08:00 Ruby Loo : > > > On 4 June 2015 at 02:58, Xu, Hejie wrote: > >> ... >> And another guideline for when we should bump Mircoversion >> *https://review.openstack.org/#/c/187896/* >> >> >> > > This is timely because just this very

Re: [openstack-dev] [opnfv-tech-discuss] [Tricircle] Polling for weekly team meeting

2015-06-06 Thread joehuang
+1 Really funny, and helpful for innovation. Best Regards Chaoyi Huang ( joehuang ) From: opnfv-tech-discuss-boun...@lists.opnfv.org [opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Daniel Smith [daniel.sm...@ericsson.com] Sent: 06 June 2015 21:35 To

Re: [openstack-dev] [magnum] Proposing Kai Qiang Wu (Kennan) for Core for Magnum

2015-06-06 Thread Haomeng, Wang
GRATZ, Kai Qiang! On Sun, Jun 7, 2015 at 7:59 AM, Steven Dake (stdake) wrote: > Kennan, > > Welcome to the magnum-core team! > > Regards > -steve > > > From: Steven Dake > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date

Re: [openstack-dev] [magnum] Proposing Kai Qiang Wu (Kennan) for Core for Magnum

2015-06-06 Thread Steven Dake (stdake)
Kennan, Welcome to the magnum-core team! Regards -steve From: Steven Dake mailto:std...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Saturday, May 30, 2015 at 10:56 PM To: "OpenStack Development Mailing Li

Re: [openstack-dev] [puppet] Change abandonment policy

2015-06-06 Thread Emilien Macchi
On 06/02/2015 02:39 PM, Colleen Murphy wrote: > In today's meeting we discussed implementing a policy for whether and > when core reviewers should abandon old patches whose author's were > inactive. (This doesn't apply to authors that want to abandon their own > changes, only for core reviewers t

[openstack-dev] [Fuel] 6.1 RC ready, Hard Code Freeze to be announced on Monday, June 8th

2015-06-06 Thread Eugene Bogdanov
Good news everyone, our internal tests have completed successfully and we now have RC build. Fuel DevOps team members are unavailable during the weekend, so we will create stable/6.1 branches for our repos on Monday, June 8th. Once created, we will officially declare Hard Code Freeze status and

Re: [openstack-dev] [app-catalog][infra] Stale entries

2015-06-06 Thread Jeremy Stanley
On 2015-06-06 17:04:14 + (+), Fox, Kevin M wrote: > Should we start requiring an extra field for maintainer contact > email address? Well, the contact info is per Zuul pipeline. If you wanted to have the job conditionally send to various E-mail addresses that's not really going to work. Mo

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

2015-06-06 Thread Ian Cordasco
On 6/6/15, 02:03, "Alan Pevec" wrote: >2015-06-05 15:16 GMT+02:00 Jeremy Stanley : >> On 2015-06-05 14:56:30 +0200 (+0200), Thierry Carrez wrote: >> [...] >>> I was wondering if we could switch to post-versioning on stable >>> branches, and basically generate: >>> >>> "2015.1.0.post38" >> [...]

Re: [openstack-dev] [app-catalog][infra] Stale entries

2015-06-06 Thread Fox, Kevin M
That would be awesome. Should we start requiring an extra field for maintainer contact email address? Thanks, Kevin From: Georgy Okrokvertskhov Sent: Saturday, June 06, 2015 7:15:45 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

Re: [openstack-dev] [opnfv-tech-discuss] [Tricircle] Polling for weekly team meeting

2015-06-06 Thread Zhipeng Huang
100 percent agree with you Daniel, let's work on it next week :) On Sat, Jun 6, 2015 at 9:35 PM, Daniel Smith wrote: > +1 as well.. Mesos was the subject of quite a bit of discussion in Van > as well. > > > > We should maybe think about coming up with a wiki page for “wanted to try > experiment

Re: [openstack-dev] [app-catalog][infra] Stale entries

2015-06-06 Thread Georgy Okrokvertskhov
On Sat, Jun 6, 2015 at 4:56 AM, Jeremy Stanley wrote: > On 2015-06-05 22:04:05 -0700 (-0700), Georgy Okrokvertskhov wrote: > > +1 for the periodic job. I don't know how it fits to the current > > OpenStack infrastructure, but we definitely need this. As I know > > there is a place for 3rd party g

Re: [openstack-dev] [opnfv-tech-discuss] [Tricircle] Polling for weekly team meeting

2015-06-06 Thread joehuang
Hi, Iben, You are correct, Tricircle mainly focuses on use of APIs of OpenStack services, for example, all APIs pass the DefCore test, so that different infrastructure (like different hypervisor, different SDN controller, etc) in underclouds can work together in multisite cloud. Tricircle

Re: [openstack-dev] [Glance][Keystone] Glance and trusts

2015-06-06 Thread Morgan Fainberg
> On Jun 5, 2015, at 19:25, Bhandaru, Malini K > wrote: > > Continuing with David’s example and the need to control access to a Swift > object that Adam points out, > > How about using the Glance token from glance-API service to glance-registry > but carry along extra data in the call, nam

Re: [openstack-dev] [opnfv-tech-discuss] [Tricircle] Polling for weekly team meeting

2015-06-06 Thread Zhipeng Huang
Good Ideas, we could also try Mesos with k8Ns On Jun 6, 2015 8:44 PM, "Zhipeng Huang" wrote: > Hi Daniel , > > Definitely interested in it :) Tricircle & Ironic & Containers is also > something we've been wanting to try out for a long time :) > > On Sat, Jun 6, 2015 at 6:07 PM, Daniel Smith > wr

Re: [openstack-dev] [opnfv-tech-discuss] [Tricircle] Polling for weekly team meeting

2015-06-06 Thread Zhipeng Huang
Hi Daniel , Definitely interested in it :) Tricircle & Ironic & Containers is also something we've been wanting to try out for a long time :) On Sat, Jun 6, 2015 at 6:07 PM, Daniel Smith wrote: > Hello there. > > > > Fatih and I were discussing TripleO the other day and were thinking about > s

Re: [openstack-dev] [opnfv-tech-discuss] [Tricircle] Polling for weekly team meeting

2015-06-06 Thread Zhipeng Huang
Hi Fatih, Definitely interested in it :) Tricircle & Ironic & Containers is also something we've been wanting to try out for a long time :) On Sat, Jun 6, 2015 at 6:07 PM, Daniel Smith wrote: > Hello there. > > > > Fatih and I were discussing TripleO the other day and were thinking about > sta

Re: [openstack-dev] [opnfv-tech-discuss] [Tricircle] Polling for weekly team meeting

2015-06-06 Thread Zhipeng Huang
Hi Fatih, Definitely interested in it :) Tricircle & Ironic & Containers is also something we've been wanting to try out for a long time :) On Sat, Jun 6, 2015 at 6:07 PM, Daniel Smith wrote: > Hello there. > > > > Fatih and I were discussing TripleO the other day and were thinking about > sta

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

2015-06-06 Thread Jeremy Stanley
On 2015-06-06 09:03:13 +0200 (+0200), Alan Pevec wrote: > 2015-06-05 15:16 GMT+02:00 Jeremy Stanley : [...] > > I think the recommendation from the PyPI maintainers is to not use > > .postN suffixes since they are intended to indicate non-code > > changes. > > So that's PBR bug then and it should

Re: [openstack-dev] [app-catalog][infra] Stale entries

2015-06-06 Thread Jeremy Stanley
On 2015-06-05 22:04:05 -0700 (-0700), Georgy Okrokvertskhov wrote: > +1 for the periodic job. I don't know how it fits to the current > OpenStack infrastructure, but we definitely need this. As I know > there is a place for 3rd party gates and CI\CD systems, so > probably, the best way to do this f

Re: [openstack-dev] [Nova] Follow up actions from the Summit: please help

2015-06-06 Thread Kashyap Chamarthy
On Fri, Jun 05, 2015 at 10:47:31AM +0100, John Garbutt wrote: > Hi, > > So in the interests of filling up your inbox yet further... > > We have lots of etherpads from the summit: > https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads#Nova > > I have extracted all the action items here

Re: [openstack-dev] [keystone][reseller] New way to get a project scoped token by name

2015-06-06 Thread David Chadwick
On 06/06/2015 00:24, Adam Young wrote: > On 06/05/2015 01:15 PM, Henry Nash wrote: >> I am sure I have missed something along the way, but can someone >> explain to me why we need this at all. Project names are unique >> within a domain, with the exception of the project that is acting as >> its

Re: [openstack-dev] [Glance][Keystone] Glance and trusts

2015-06-06 Thread David Chadwick
In order to do this fully, you will need to work out what all the possible supply chains are in OpenStack, so that when any customer starts any chain of events, there is sufficient information in the message passed to the supplier that allows that supplier to order from its supplier. This has to be

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

2015-06-06 Thread Alan Pevec
2015-06-05 15:16 GMT+02:00 Jeremy Stanley : > On 2015-06-05 14:56:30 +0200 (+0200), Thierry Carrez wrote: > [...] >> I was wondering if we could switch to post-versioning on stable >> branches, and basically generate: >> >> "2015.1.0.post38" > [...] > > I think the recommendation from the PyPI main

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

2015-06-06 Thread Alan Pevec
> Finally, I don't think this is still costly in terms of herding cats, > because we have very few cats actually grazing in the stable branch > pastures. I suggest that stable branch maintainers simply get used to > releasing on a weekly basis if there are new commits, and use that as > an opportun