Re: [openstack-dev] [tc][election][ec2-api][winstackers][stable] status of teams without PTL candidates

On 12:50 Mar 21, Tony Breeds wrote: > On Sun, Mar 20, 2016 at 12:48:43PM -0400, Doug Hellmann wrote: > > I won't be able to make the TC meeting this week because of travel, > > so I wanted to lay out my thoughts on the three PTL-less projects > > based on the outcome of the recent election

Re: [openstack-dev] [kolla][release] Announcement of release of Mitaka rc1!

For sure. Regards, Daneyon On Mar 19, 2016, at 1:52 PM, Steven Dake (stdake) > wrote: Thanks - although it wasn't me that made it happen, it was the team. Regards, -steve From: "Daneyon Hansen (danehans)"

[openstack-dev] [release][stable][glance] glance_store 0.9.2 release (liberty)

We are content to announce the release of: glance_store 0.9.2: OpenStack Image Service Store Library This release is part of the liberty stable release series. With source available at: http://git.openstack.org/cgit/openstack/glance_store With package available at:

[openstack-dev] Visa Invitation Letter doesn't contain attachment

hi, guys. I received Visa Invitation Letter a few days ago. But the letter doesn't contain attachment. What should I do? Thanks Zhi Chang__ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [tc][election][ec2-api][winstackers][stable] status of teams without PTL candidates

> Just clarifying: > For Nova: Yes. Matt's the only candidate I think that's a preety save > assumption. Sorry, I meant for Nova. I guess since the nomination period is over (right), I'm not sure how it's not more than an assumption...but okay :) --Dan

Re: [openstack-dev] [tc][election][ec2-api][winstackers][stable] status of teams without PTL candidates

On Sun, Mar 20, 2016 at 04:14:02PM -0700, Dan Smith wrote: > > The EC2-API project doesn't appear to be very actively worked on. > > There is one very recent commit from an Oslo team member, another > > couple from a few days before, and then the next one is almost a > > month old. Given the lack

Re: [openstack-dev] [tc][election][ec2-api][winstackers][stable] status of teams without PTL candidates

On Sun, Mar 20, 2016 at 12:48:43PM -0400, Doug Hellmann wrote: > I won't be able to make the TC meeting this week because of travel, > so I wanted to lay out my thoughts on the three PTL-less projects > based on the outcome of the recent election (EC2-API, Winstackers, > and Stable Maintenance). >

[openstack-dev] [Sahara][QA] Notes about the move of the Sahara Tempest API test to sahara-tests

Hi, as discussed in the last (two) Sahara meetings, I'm working on moving the Tempest API tests from the Tempest repository to the new sahara-tests repository, which contains only (non-tempest) scenario tests and it's branchless as well. The move is a natural consequence of the Tempest focus

Re: [openstack-dev] [Openstack-stable-maint][stable/liberty][trove] stable/liberty changes in Trove that are ready for merge

On Sun, Mar 20, 2016 at 08:00:07PM -0400, Luigi Toscano wrote: > No one said that there will be other backports, at this time. It would have > made sense if the reviews would have been merged when they have been > proposed. It would be nice thought to backports one or two other patches for > the

Re: [openstack-dev] [Openstack-stable-maint][stable/liberty][trove] stable/liberty changes in Trove that are ready for merge

- Original Message - > On 03/19/2016 01:43 AM, Tony Breeds wrote: > > On Sun, Mar 13, 2016 at 12:15:23PM +, Amrith Kumar wrote: > >> Hi, > >> > >> Sorry for the blast mail, this is targeted at the stable-maint team. The > >> following five changes are now ready to merge. Two of them

Re: [openstack-dev] [TripleO] propose EmilienM for core

+1 Original message From: Dan Prince Date: 03/20/2016 12:23 PM (GMT-07:00) To: openstack-dev Subject: [openstack-dev] [TripleO] propose EmilienM for core I'd like to propose that we add Emilien Macchi to the

Re: [openstack-dev] [tc][election][ec2-api][winstackers][stable] status of teams without PTL candidates

> The EC2-API project doesn't appear to be very actively worked on. > There is one very recent commit from an Oslo team member, another > couple from a few days before, and then the next one is almost a > month old. Given the lack of activity, if no team member has > volunteered to be PTL I think

Re: [openstack-dev] [tc][ec2-api] EC2 API Future

Hello, First of all, let me apologize for answering on Alex Levine's behalf, but it's late night/early morning in Moscow, so I'm taking the liberty. Second, Alex Levine was recently made PTL of the EC2-API project when it was formally accepted as an official project, but failed to

Re: [openstack-dev] [magnum] High Availability

The Magnum team discussed Anchor several times (in the design summit/midcycle). According to what I remembered, the conclusion is to leverage Anchor though Barbican (presumably there is an Anchor backend for Barbican). Is Anchor support in Barbican still in the roadmap? Best regards, Hongbin

Re: [openstack-dev] [magnum] High Availability

Thanks for your inputs. It sounds like we have no other option besides Barbican as long as we need to store credentials in Magnum. Then I have a new proposal: switch to an alternative authentication mechanism that doesn't require to store credentials in Magnum. For example, the following

Re: [openstack-dev] [oslo][all] What would you like changed/fixed/new in oslo??

On 03/20/2016 10:00 AM, Adam Young wrote: I started with a blog post here: http://adam.younglogic.com/2016/03/what-can-talk-to-what-on-the-openstack-message-broker/ and did a brief spike here: http://adam.younglogic.com/2016/03/tie-your-rabbit-down/ We made the mistake of pursuing HMAC back

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On Sun, Mar 20, 2016 at 1:26 PM, Richard Jones wrote: > Unfortunately none of this discussion solves the substantive issue which is > that we cannot release an xstatic package without breaking the gate. > > We currently have one solution that's a close to viable as we've

Re: [openstack-dev] [TripleO] propose EmilienM for core

+1 On 20 Mar 2016 20:27, "Dan Prince" wrote: > I'd like to propose that we add Emilien Macchi to the TripleO core > review team. Emilien has been getting more involved with TripleO during > this last release. In addition to help with various Puppet things he > also has

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

Unfortunately none of this discussion solves the substantive issue which is that we cannot release an xstatic package without breaking the gate. We currently have one solution that's a close to viable as we've been able to get: move the version pinning for xstatic packages out of

Re: [openstack-dev] [TripleO] propose EmilienM for core

+1 On Sunday, March 20, 2016, Dan Prince wrote: > I'd like to propose that we add Emilien Macchi to the TripleO core > review team. Emilien has been getting more involved with TripleO during > this last release. In addition to help with various Puppet things he > also has

Re: [openstack-dev] [TripleO] propose EmilienM for core

On 03/20/2016 02:22 PM, Dan Prince wrote: I'd like to propose that we add Emilien Macchi to the TripleO core review team. Emilien has been getting more involved with TripleO during this last release. In addition to help with various Puppet things he also has experience in building OpenStack

Re: [openstack-dev] [tc][ec2-api] EC2 API Future

Doug, Given that the EC2 functionality is currently in use by at least 1/6th of production clouds (https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf page 34), this is a worrying situation. The EC2 functionality was recently deprecated from Nova on the grounds that the

[openstack-dev] [TripleO] propose trown for core

I'd like to propose that we add John Trowbridge to the TripleO core review team. John has become one of the goto guys in helping to chase down upstream trunk chasing issues. He has contributed a lot to helping keep general CI issues running and been involved with several new features over the past

[openstack-dev] [TripleO] propose EmilienM for core

I'd like to propose that we add Emilien Macchi to the TripleO core review team. Emilien has been getting more involved with TripleO during this last release. In addition to help with various Puppet things he also has experience in building OpenStack installation tooling, upgrades, and would be a

Re: [openstack-dev] [nova] working on bug reports; what blocks you?

On Fri, Mar 18, 2016 at 07:01:34PM +0100, Markus Zoeller wrote: > Kashyap Chamarthy wrote on 03/18/2016 07:28:09 AM: [...] > > Writing a thoughtful report is hard and time-taking. > > Yeah, and I assume that's the reason many bug reports lack that > information. I have the

Re: [openstack-dev] [neutron] report from Brno code sprint, Mar 14-16

Ihar Hrachyshka wrote: > > One thing that we discussed on the event is updating networking-guide with > detailed description of the upgrade process for neutron. We already have > some pieces scattered there [f.e. we have some coverage for > neutron-db-manage tool] but it’s nothing complete or

Re: [openstack-dev] [oslo][all] What would you like changed/fixed/new in oslo??

On 03/19/2016 11:33 PM, Joshua Harlow wrote: Howday all, Just to start some conversation for the next cycle, I wanted to start thinking about what folks may like to see in oslo (or yes, even what u dislike in any of the oslo libraries). For those who don't know, oslo[1] is a lot of

[openstack-dev] [tc][election][ec2-api][winstackers][stable] status of teams without PTL candidates

I won't be able to make the TC meeting this week because of travel, so I wanted to lay out my thoughts on the three PTL-less projects based on the outcome of the recent election (EC2-API, Winstackers, and Stable Maintenance). The EC2-API project doesn't appear to be very actively worked on. There

Re: [openstack-dev] [TaskFlow] TaskFlow persistence

Lingxian Kong wrote: Kanthi, sorry for chiming in, I suggest you may have a chance to take a look at Mistral[1], which is the workflow as a service in OpenStack(or without OpenStack). Out of curiosity, why? Seems the ML post was about 'TaskFlow persistence' not mistral, just saying (unsure

[openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

The following proposed API guidelines are available for broader review by interested parties. * https://review.openstack.org/#/c/281511/ Delete multiple metadata items with a single request * https://review.openstack.org/#/c/260292/ Add unexpected attribute guideline *

[openstack-dev] [release][manila] Manila Mitaka RC1 available

Hello everyone, The release candidate for Manila for the end of the Mitaka cycle is available! You can find the RC1 source code tarball at: https://tarballs.openstack.org/manila/manila-2.0.0.0rc1.tar.gz Unless release-critical issues are found that warrant a release candidate respin, this RC1

[openstack-dev] [release][telemetry] Aodh Mitaka RC1 available

Hello everyone, The Telemetry team's release candidate for Aodh for the end of the Mitaka cycle is available! You can find the RC1 source code tarball at: https://tarballs.openstack.org/aodh/aodh-2.0.0.0rc1.tar.gz Unless release-critical issues are found that warrant a release candidate

[openstack-dev] [release][telemetry] Ceilometer Mitaka RC1 available

Hello everyone, The Telemetry team's release candidate for Ceilometer for the end of the Mitaka cycle is available! You can find the RC1 source code tarball at: https://tarballs.openstack.org/ceilometer/ceilometer-6.0.0.0rc1.tar.gz Unless release-critical issues are found that warrant a

[openstack-dev] [Fuel] Packaging CI for Fuel

Hi, everyone, we'd like to announce Packaging CI for Fuel. For now there are no extended tests, just package builds. Package-based test will be added later in Newton development cycle. Current workflow: * for every request we build a package and publish it to temporary repository, which you

Re: [openstack-dev] [QA][all] Propose to remove negative tests from Tempest

Also curious about this. It seems weird to separate the 'positive' and the 'negative' ones, assuming those patches are mostly contributed by the same group of developers. Yeah, agree. This approach leads to situation when I need to look at two places to observe test coverage for each component.

[openstack-dev] [trove] We're open for business on Newton

This morning, Craig tagged RC1 on trove[1] and a short while ago I tagged RC1 on trove-dashboard[2]. The python-troveclient for Mitaka was tagged some days ago[3]. At this point, changes merged into master will be headed for Newton. Any changes that are required for Mitaka RC2 will have to be

Re: [openstack-dev] [tc] Question about electorate for project without gerrit contribution

On 16/03/2016 04:47, Tony Breeds wrote: > On Tue, Mar 15, 2016 at 09:41:41PM +, Hayes, Graham wrote: >> I do not see the time frame for defining an electorate there. >> >> PTL seats are completely renewed every 6 months. A separate election is >> run for >> each project team. These elections

Re: [openstack-dev] [all] purplerbot irc bot for logs and transclusion

On Fri, 18 Mar 2016, Anita Kuno wrote: On 03/16/2016 10:45 AM, Paul Belanger wrote: I would like to see it added to openstack-infra so we can properly manage it. I agree with Paul here. purpler (which includes the bot) is now packaged and on pypi: https://pypi.python.org/pypi/purpler

Re: [openstack-dev] [stable] Proposing Tony Breeds for stable-maint-core

+1 From: Dave Walker > Reply-To: OpenStack List > Date: Sunday, March 20, 2016 at 12:27 PM To: OpenStack List

Re: [openstack-dev] [manila] FFE for update_access implementation for Ganesha lib and GlusterFS

Excerpts from Csaba Henk's message of 2016-03-16 15:02:40 +0100: > Hi, > > I'm asking for a Feature Free Exception for the update_access code for > Ganesha library and the two GlusterFS drivers (glusterfs, glusterfs-native). > > This benefits the whole project in terms of getting closer to the

Re: [openstack-dev] [Heat][Neutron] Mitaka RC1 available

On 18 March 2016 at 00:16, Jeremy Stanley wrote: > On 2016-03-17 09:44:59 +0530 (+0530), Armando M. wrote: > > Unfortunately, Neutron is also going to need an RC2 due to > > upstream CI issues triggered by infra change [1] that merged right > > about the same time RC1 was

[openstack-dev] [Magnum] COE drivers spec

Hi all, I'm writing the spec for the COE drivers, and I wanted some feedback about what it should include. I'm trying to reconstruct some of the discussion that was had at the mid-cycle meet-up, but since I wasn't there I need to rely on people who were :) >From my perspective, the spec

Re: [openstack-dev] [stable] Proposing Tony Breeds for stable-maint-core

On 18 Mar 2016 20:11, "Matt Riedemann" wrote: > > I'd like to propose tonyb for stable-maint-core. > Please respond with ack/nack. +1, Great work Tony. -- Kind Regards, Dave Walker __ OpenStack

Re: [openstack-dev] [stable] Proposing Tony Breeds for stable-maint-core

Matt Riedemann wrote: I'd like to propose tonyb for stable-maint-core. Tony is pretty much my day to day guy on stable, he's generally in every stable team meeting (which is not attended well so I appreciate it), and he's as proactive as ever on staying on top

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

As an Op, I've seen quota's in the db get out of sync all the time I'm sure some of my clouds right now have some stuff out of sync :/ With my dev hat on: The code is really hard to get right. There are also a lot of places quota's are missing. quota's per host aggregate, quota's for

[openstack-dev] [neutron] Upgrading from Kilo to Liberty, missing database entries

Hello, Recently when testing neutron upgrades for openstack-ansible, I ran into an existing bug [1] where the networksecuritybindings and portsecuritybindings tables were not populated after an upgrade from Kilo to Liberty. Updating the table manually resolved the issue, as mentioned in the

Re: [openstack-dev] [TaskFlow] TaskFlow persistence

Kanthi, sorry for chiming in, I suggest you may have a chance to take a look at Mistral[1], which is the workflow as a service in OpenStack(or without OpenStack). [1]: http://docs.openstack.org/developer/mistral/ On Sun, Mar 20, 2016 at 5:35 AM, pnkk wrote: > Filed it at

Re: [openstack-dev] [QA][all] Propose to remove negative tests from Tempest

On Thu, Mar 17, 2016 at 3:24 PM, Kairat Kushaev wrote: > > Also curious about this. It seems weird to separate the 'positive' and > the 'negative' ones, assuming those patches are mostly contributed by > the same group of developers. > > > Yeah, agree. This approach leads

Re: [openstack-dev] [nova] Wishlist bugs == (trivial) blueprint?

On 3/17/2016 1:26 PM, Tim Bell wrote: On 17/03/16 18:29, "Sean Dague" wrote: On 03/17/2016 11:57 AM, Markus Zoeller wrote: Suggested action items: 1. I close the open wish list items older than 6 months (=138 reports) and explain in the closing comment that they are

Re: [openstack-dev] [cross-project] [all] Quotas -- service vs. library

On Wed, 16 Mar 2016, Salvatore Orlando wrote: - Looking at quotas it is worth distinguishing between management (eg:: resource limits per tenant and/or users), and enforcement (eg.: can the bakery service give me 4 cookies or did I already eat too many?) While for the reasons listed throughout

Re: [openstack-dev] [Heat] Nomination Oleksii Chuprykov to Heat core reviewer

+1! 2016-03-16 20:13 GMT+08:00 Pavlo Shchelokovskyy < pshchelokovs...@mirantis.com>: > +1 :) > > Dr. Pavlo Shchelokovskyy > Senior Software Engineer > Mirantis Inc > www.mirantis.com > > On Wed, Mar 16, 2016 at 1:18 PM, Rabi Mishra wrote: > >> > Hi Heaters, >> > >> > The

Re: [openstack-dev] [Fuel] [FFE] LCM readiness for all deployment tasks

Hi, Feature has been merged. QA is in progress. Thanks, Szymon On 4 March, 2016 at 1:31:55, Dmitry Borodaenko (dborodae...@mirantis.com) wrote: Granted, merge deadline March 15. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 05:03:11PM +0100, Szymon Banka wrote: > Hi All, > > I’d like to

[openstack-dev] [Neutron] PTL Candidacy

I would like to propose my candidacy for the Neutron PTL. I have been the Neutron PTL for the Mitaka release, and I would like to continue the journey on which I have embarked upon a little over six months ago. Back then, I had a number of objectives which I wanted to achieve with the help of

Re: [openstack-dev] [neutron] Upgrading from Kilo to Liberty, missing database entries

Nolan Brubaker wrote: Hello, Recently when testing neutron upgrades for openstack-ansible, I ran into an existing bug [1] where the networksecuritybindings and portsecuritybindings tables were not populated after an upgrade from Kilo to Liberty. Updating

Re: [openstack-dev] [magnum] High Availability

At the risk of muddying the waters further, I recently chatted with some of you about Anchor, it's an ephemeral PKI system setup to provide private community PKI - certificate services for internal systems, a lot like k8 pods. An overview of why revocation doesn't work very well in many cases