Re: [openstack-dev] [Doc] place to add API reference

On Fri, Apr 15, 2016 at 11:17:40AM -0500, Anne Gentle wrote: > Sean and I are collaborating on a cross project spec to talk about at the > Summit. Can you talk about concerns or cons to this approach so we can put it > in the spec? > > Thanks, > Anne Thanks Anne. No concerns at the moment. I

Re: [openstack-dev] [Doc] place to add API reference

Sean and I are collaborating on a cross project spec to talk about at the Summit. Can you talk about concerns or cons to this approach so we can put it in the spec? Thanks, Anne > On Apr 15, 2016, at 11:02 AM, Sean McGinnis wrote: > >> On Fri, Apr 15, 2016 at

[openstack-dev] [ptl][release] newton release management communication

PTLs, As we did for the Mitaka cycle, I want to start this cycle by making sure the expectations for communications with the release team are clear to everyone so there is no confusion or miscommunication about any of the process or deadlines for Newton. This email is being sent to the

[openstack-dev] [Neutron] Operator Pain Points

I'm cross-posting this to the dev and operators mailing lists. In the upcoming design summit in Austin, I'll be hosting a session [1] to discuss how to prioritize operator pain points around Neutron, find owners, and plan them for Newton. In preparation for that discussion, I have performed a

[openstack-dev] [lbaas][octavia] Queries on octavia features

Hi, I am trying to use lbaas v2 for loadbalancing in openstack. I have few queries. I don't know whether I should directly ask you guys or not. If you can answer, then that would be great. - Is the v1 of octavia released? The documentation details the v0.5 design and under v1 project specs, there

Re: [openstack-dev] [nova] [glance] Getting the ball rolling on glance v2 in nova in newton cycle

On 04/01/2016 06:45 AM, Sean Dague wrote: #2 - move discover major version back to glanceclient - https://github.com/openstack/nova/blob/3cdaa30566c17a2add5d9163a0693c97dc1d065b/nova/image/glance.py#L108 I don't understand why this was ever in nova. This really should be

Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing?

> From: Dean Troyer > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 04/14/2016 08:18 PM > Subject: Re: [openstack-dev] [all] [devstack] Adding example > "local.conf" files for testing? > > On Thu, Apr 14,

[openstack-dev] [release] no team meeting 22 April

In celebration of Earth Day (and travel to the summit), I propose that we skip the release team meeting on 22 April. Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [nova] Launchpad bug spring cleaning day Monday 4/18

A short reminder that this is happening next Monday 04/18 A few stats are at: http://45.55.105.55:8082/bugs-stats.html Regards, Markus Zoeller (markus_z) > From: Matt Riedemann > To: "OpenStack Development Mailing List (not for usage questions)" >

Re: [openstack-dev] [Doc] place to add API reference

On Fri, Apr 15, 2016 at 09:38:20AM +0200, Andreas Jaeger wrote: > On 04/15/2016 08:14 AM, Masahito MUROI wrote: > >Hi Doc team folks, > > > >Congress team plans to add API reference into [1] instead of [2] to > >follow official documentation project. But I found the design session > >about a API

Re: [openstack-dev] [ceilometer][horizon] metric-list not complete and show metrics in horizon dashboard

> From: gordon chung [mailto:g...@live.ca] > Sent: Tuesday, April 12, 2016 8:00 AM > > On 12/04/2016 7:47 AM, Safka, JaroslavX wrote: > > > * > > And my question is: How is connected the database table meter and the > command metric-list? > > i assume you mean meter-list. it uses a

Re: [openstack-dev] [nova] [glance] Getting the ball rolling on glance v2 in nova in newton cycle

On 04/15/2016 10:42 AM, Jay Pipes wrote: > On 04/01/2016 06:45 AM, Sean Dague wrote: >> #2 - move discover major version back to glanceclient - >> https://github.com/openstack/nova/blob/3cdaa30566c17a2add5d9163a0693c97dc1d065b/nova/image/glance.py#L108 >> >> >> I don't understand why this was ever

[openstack-dev] [ptl][release] newton release management communication

PTLs, As we did for the Mitaka cycle, I want to start this cycle by making sure the expectations for communications with the release team are clear to everyone so there is no confusion or miscommunication about any of the process or deadlines for Newton. This email is being sent to the

Re: [openstack-dev] [nova] [glance] Getting the ball rolling on glance v2 in nova in newton cycle

comment inline On 4/15/16 11:08 AM, Sean Dague wrote: > On 04/15/2016 10:42 AM, Jay Pipes wrote: >> On 04/01/2016 06:45 AM, Sean Dague wrote: >>> #2 - move discover major version back to glanceclient - >>>

Re: [openstack-dev] [nova] Proposing Andrey Kurilin for python-novaclient core

On 4/13/2016 12:53 PM, Matt Riedemann wrote: I'd like to propose that we make Andrey Kurilin core on python-novaclient. He's been doing a lot of the maintenance the last several months and a lot of times is the first to jump on any major issue, does a lot of the microversion work, and is also

Re: [openstack-dev] [nova] Proposing Andrey Kurilin for python-novaclient core

I am glad to have joined the Team! On Fri, Apr 15, 2016 at 6:00 PM, Matt Riedemann wrote: > > > On 4/13/2016 12:53 PM, Matt Riedemann wrote: > >> I'd like to propose that we make Andrey Kurilin core on python-novaclient. >> >> He's been doing a lot of the maintenance

Re: [openstack-dev] [nova] [glance] Getting the ball rolling on glance v2 in nova in newton cycle

Thanks for the update, Jay. (My memories of Mitaka have been faint.) I guess a commitment of this has been made so it needs to be hold and since it's been delayed, I guess it makes it a higher priority. I will work on a plan to get this done. On 4/15/16 10:42 AM, Jay Pipes wrote: > On 04/01/2016

Re: [openstack-dev] [heat] convergence cancel messages

On 14-Apr-16 23:09, Zane Bitter wrote: > On 11/04/16 04:51, Anant Patil wrote: >> On 14-Mar-16 14:40, Anant Patil wrote: >>> On 24-Feb-16 22:48, Clint Byrum wrote: Excerpts from Anant Patil's message of 2016-02-23 23:08:31 -0800: > Hi, > > I would like the discuss various

Re: [openstack-dev] [Congress]Authorization mechanisms for each user

Hi Yuki, As Masahito mentioned, the usual way to authorize API calls in OpenStack is through policy.json. If I remember right, you can make a decision about whether an API call is permitted using (i) all the values in the API call and (ii) the Keystone role of the user making the request. I'm

[openstack-dev] [release][ptl] establishing liaisons with the release team for Newton

PTLs, As with the other cross-project teams, the release management team relies on liaisons from each project to be available for coordination of work across all teams. It's the start of a new cycle, so it's time to find those liaison volunteers. We are working on updating the release

Re: [openstack-dev] [lbaas][octavia] Queries on octavia features

Hi Akshay! In response to your questions: The Mitaka release of Octavia is version 0.8. It's got most of the features of 1.0, but since the development path didn't exactly follow the road map (since nobody is prescient 18 months in advance) most of us felt more comfortable calling this release

[openstack-dev] [keystone] newton design summit schedule

Hello fellow keystoners! Please see the design session times[1] and etherpads[2] for the keystone design sessions. Feel free to start creating content in the etherpads. See you all in Austin! [1] https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Keystone%3A [2]

Re: [openstack-dev] Nova quota statistics counting issue

On 4/14/2016 3:07 PM, Andrew Laski wrote: On Wed, Apr 13, 2016, at 12:27 PM, Dmitry Stepanenko wrote: Hi Team, I worked on nova quota statistics issue (https://bugs.launchpad.net/nova/+bug/1284424) happenning when nova-* processes are restarted during removing instances and was able to

Re: [openstack-dev] [heat] convergence cancel messages

On 15/04/16 10:58, Anant Patil wrote: On 14-Apr-16 23:09, Zane Bitter wrote: On 11/04/16 04:51, Anant Patil wrote: After lot of ping-pong in my head, I have taken a different approach to implement stack-update-cancel when convergence is on. Polling for traversal update in each heat engine

Re: [openstack-dev] [refstack]Proposing Andrey Pavlov (andrey-mp) for RefStack core

+1 for Andrey.   - Paul     - Original message -From: Catherine Cuong Diep/San Jose/IBM@IBMUSTo: openstack-dev@lists.openstack.orgCc:Subject: [openstack-dev] [refstack]Proposing Andrey Pavlov (andrey-mp) for RefStack coreDate: Fri, Apr 15, 2016 12:14 PM  Hi,I would like to propose adding

[openstack-dev] [release][neutron] neutron-lib 0.1.0 release (newton)

We are delighted to announce the release of: neutron-lib 0.1.0: Neutron shared routines and utilities This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/neutron-lib With package available at:

[openstack-dev] [keystone] keystoneclient 3.0.0 release (no more CLI and apiclient package)

This is a heads up that the keystone team will be releasing python-keystoneclient 3.0.0 soon ( https://review.openstack.org/#/c/306587/1 ), it will be the first client release of the Newton cycle. This is a major version upgrade because and may affect other development teams, as we are removing

Re: [openstack-dev] [neutron][kilo] - vxlan's max bandwidth

On 04/14/2016 07:10 PM, Kenny Ji-work wrote: Hi all, In the environment of openstack kilo, I test the bandwidth in the scene which VxLan being used. The result show that the vxlan can only support up to 1 gbits bandwidth. Is this a bug or any else issue, or is there some hotfix to solve the

Re: [openstack-dev] [Doc] place to add API reference

On Fri, Apr 15, 2016 at 12:04 PM, Sean McGinnis wrote: > On Fri, Apr 15, 2016 at 11:17:40AM -0500, Anne Gentle wrote: > > Sean and I are collaborating on a cross project spec to talk about at > the Summit. Can you talk about concerns or cons to this approach so we can >

[openstack-dev] [refstack]Proposing Andrey Pavlov (andrey-mp) for RefStack core

Hi, I would like to propose adding Andrey Pavlov (andrey-mp) to the RefStack core reviewer team. Andrey has been a highly valuable developer to RefStack for the past few months. His contribution has been focusing on adding the vendor and product registration features to RefStack. Equally

[openstack-dev] [Keystone] State of Fernet Token deployment

We all want Fernet to be a reality. We ain't there yet (Except for mfish who has no patience) but we are getting closer. The goal is to get Fernet as the default token provider as soon as possible. The review to do this has uncovered a few details that need to be fixed before we can do this.

[openstack-dev] [all] Removal of in progress console log access

tl;dr Effective immediately we've put firewalls in front of the Jenkins servers removing in-progress console log streaming access Longer version Recently some potential security issues have come to our attention with Jenkins [1] and the way we run it that are non-trivial to fix. As a

[openstack-dev] [Neutron] Meetings schedule: an update

Hi Neutrinos, This is a reminder of meetings [1,2] and their schedule for the next few weeks: Week R24: - Apr 18: Team meeting at 2100UTC - Apr 21: Drivers meeting cancelled Week R23: - Apr 26: Team meeting cancelled - Apr 27: Drivers meeting cancelled Week R22: - May 2: Team

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi Reedip, Sure will include you in the discussion. Let me know if there are other Tap-as-a-Service members who would like to join this initiative. Cathy From: reedip banerjee [mailto:reedi...@gmail.com] Sent: Thursday, April 14, 2016 7:03 PM To: OpenStack Development Mailing List (not for

Re: [openstack-dev] [oslo] Removing Nova specifics from oslo.log

On 4/15/2016 3:11 AM, Julien Danjou wrote: On Thu, Apr 14 2016, Joshua Harlow wrote: Well not entirely IMHO. I think oslo should obviously be easy to use inside openstack and as well outside, with preference to inside openstack (especially for libraries that start with 'oslo.*'). When we can

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Hi Ihar, My replies are inline. Thanks, Cathy -Original Message- From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] Sent: Thursday, April 14, 2016 4:45 PM To: Cathy Zhang Cc: OpenStack Development Mailing List (not for usage questions); Vikram Choudhary; Sean M. Collins; Haim Daniel;

Re: [openstack-dev] [Congress] Issues with Tox testing

Bryan, Check out refstack.openstack.org and https://github.com/openstack/refstack The refstack project provides a client which enables anyone to run tempest tests on their own clouds. It is flexible, with options for selecting all or specific test sets, or specific tests and also has an

[openstack-dev] [release][kolla] Release of kolla 2.0.0.0rc4

Hey folks, We had originally planned to release 2.0.0 today but there are a few more bugs left to resolve before our final tag. Hence, we made a decision to move the final 2.0.0 release to Thursday, April 21st. I am super pleased to announce the release of 2.0.0.0 rc4 which fixes 37 bugs,

Re: [openstack-dev] [Keystone] State of Fernet Token deployment

On Fri, Apr 15, 2016 at 8:04 PM, Adam Young wrote: > We all want Fernet to be a reality. We ain't there yet (Except for mfish > who has no patience) but we are getting closer. The goal is to get Fernet > as the default token provider as soon as possible. The review to do

Re: [openstack-dev] [Congress]Authorization mechanisms for each user

Hi Yuki, This sounds interesting. AFAIK, there is no similar use-case you mentioned. On 2016/04/15 10:13, Yuki Nisiwaki wrote: Hi openstacker working on congress. I want to implement the authorization mechanisms for each user, not role base. For example, User A can change security group, But

Re: [openstack-dev] [Doc] place to add API reference

Thanks Andreas, I'll check the work and do that. best regards, Masahito On 2016/04/15 16:38, Andreas Jaeger wrote: On 04/15/2016 08:14 AM, Masahito MUROI wrote: Hi Doc team folks, Congress team plans to add API reference into [1] instead of [2] to follow official documentation project. But I

Re: [openstack-dev] [oslo] Removing Nova specifics from oslo.log

On Thu, Apr 14 2016, Joshua Harlow wrote: > Well not entirely IMHO. I think oslo should obviously be easy to use inside > openstack and as well outside, with preference to inside openstack (especially > for libraries that start with 'oslo.*'). When we can make it more useable > outside openstack

Re: [openstack-dev] [Neutron] Proposing Hirofumi Ichihara to Neutron Core Reviewer Team

Congrats Hirofumi! On Apr 15, 2016 11:12 AM, "reedip banerjee" wrote: > Congratulations Hirofumi :) > > On Fri, Apr 15, 2016 at 8:52 AM, Takashi Yamamoto > wrote: > >> welcome, hirofumi! >> >> On Fri, Apr 15, 2016 at 11:40 AM, Akihiro Motoki

[openstack-dev] [Doc] place to add API reference

Hi Doc team folks, Congress team plans to add API reference into [1] instead of [2] to follow official documentation project. But I found the design session about a API docs style[3]. For now, is it ok to add API reference [1], or should we wait the decision about style of API reference

Re: [openstack-dev] [Neutron] OVS flow modification performance

On Fri, Apr 15, 2016 at 7:32 AM, IWAMOTO Toshihiro wrote: > At Mon, 11 Apr 2016 14:42:59 +0200, > Miguel Angel Ajo Pelayo wrote: >> >> On Mon, Apr 11, 2016 at 11:40 AM, IWAMOTO Toshihiro >> wrote: >> > At Fri, 8 Apr 2016 12:21:21 +0200, >> > Miguel

[openstack-dev] [watcher] Api and Decision Engine integration - design question

Hi guys, I'm implementing the Watcher Scoring Module. As part of that, I need to expose the information about Scoring Engines through the API/Python CLI. The scoring engine list might be quite dynamic. Although the scoring engines will be pluggable through the stevedore plug-in model, a single

[openstack-dev] [all] -The lifecycle of deploying openstack on production environment

Hi all, We wanner to deploy openstack to the production environment, so what's the recommended way to complete it? By using puppet-openstack or any else tool? Secondly, we want to add custom codes into the openstack's. So the problem is that if new version of openstack is released, the

Re: [openstack-dev] [fuel] [fuelclient] Pre-release versions of fuelclient for testing purposes

On 04/14/2016 06:30 PM, Jeremy Stanley wrote: On 2016-04-14 12:57:38 +0300 (+0300), Oleg Gelbukh wrote: The thread I'm referring to in the prev message is: http://lists.openstack.org/pipermail/openstack-infra/2014-January/000624.html At this point it's probably no longer a concern. We don't

Re: [openstack-dev] [all] -The lifecycle of deploying openstack on production environment

You should probably try openstack-operators mailing list next time, as openstack-dev is more developer oriented. But anyway: On 04/15/2016 08:53 AM, Kenny Ji-work wrote: > Hi all, > > We wanner to deploy openstack to the production environment, so what's > the recommended way to complete it? By

Re: [openstack-dev] [all] -The lifecycle of deploying openstack on production environment

On 15 April 2016 at 07:53, Kenny Ji-work wrote: > > We wanner to deploy openstack to the production environment, so what's the > recommended way to complete it? By using *puppet-openstack *or any else > tool? > *Secondly*, we want to add *custom codes* into the openstack's.

Re: [openstack-dev] [fuel] [fuelclient] Pre-release versions of fuelclient for testing purposes

Jeremy, thank you, that's excellent news. The Infra team is doing awesome work to improve the processes in all possible ways. Andreas, I will take a closer look, but it seems to be exactly what I had in mind. Thanks for sharing! -- Best regards, Oleg Gelbukh On Fri, Apr 15, 2016 at 10:29 AM,

Re: [openstack-dev] [Doc] place to add API reference

On Fri, Apr 15, 2016 at 1:14 AM, Masahito MUROI < muroi.masah...@lab.ntt.co.jp> wrote: > Hi Doc team folks, > > Congress team plans to add API reference into [1] instead of [2] to > follow official documentation project. But I found the design session > about a API docs style[3]. > > For now, is

Re: [openstack-dev] [Doc] place to add API reference

On 04/15/2016 08:14 AM, Masahito MUROI wrote: Hi Doc team folks, Congress team plans to add API reference into [1] instead of [2] to follow official documentation project. But I found the design session about a API docs style[3]. For now, is it ok to add API reference [1], or should we wait

[openstack-dev] [ironic] Summit sessions are up!

Hi y'all, A bit late, but the ironic summit sessions are up at https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Ironic%3A (due to the way the schedule search works, there's also a talk in there, sorry) Please let me know ASAP if this schedule has a conflict or

Re: [openstack-dev] [sahara] Newton summit draft schedule

Hi folks, it's a friendly reminder about our schedule. If you have some issues regarding that please let me know about that ASAP. On Fri, Apr 8, 2016 at 7:19 PM, Vitaly Gridnev wrote: > Hi Sahara team, > > Here [0] is the proposed schedule for our summit work sessions and