Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

Jeremy Stanley wrote: > It's an option of last resort, I think. The next consistent flavor > up in most of the providers donating resources is double the one > we're using (which is a fairly typical pattern in public clouds). As > aggregate memory constraints are our primary quota limit, this

Re: [openstack-dev] [api-wg] restarting service-types-authority / service catalog work

2017-01-07 4:10 GMT+09:00 Sean Dague : > It's a new year, and in anticipation of having a productive time in > Atlanta around the service catalog, I refreshed the set of patches from > last year around starting to stub out a service-types-authority - >

Re: [openstack-dev] [ironic] New mascot design

+100 On 06/02/2017, 12:32, "Dmitry Tantsur" wrote: On 02/06/2017 12:49 PM, Miles Gould wrote: > On 01/02/17 21:38, Lucas Alvares Gomes wrote: >> But, let me ask something, what the foundation really wants to achieve >> with this ? Cause I think we are

Re: [openstack-dev] [horizon] [neutron] Horizon support for Neutron Trunks - PTL approval needed

Well the UIs for the extensions inside the main Neutron repo are in the main horizon repo so far (e.g. routers, floating IPs, security groups, etc). LBaaS is a separate repo with separate devs so it makes sense to me that it would have its own UI repo. Trunks would be the the first extension that

[openstack-dev] Developer's deepdive of SRIOV Passthrough for Neutron

Hi Folks, We are trying to understand what happens when we launch an instance on a compute running SRIOV agent. By "what happens" I mean, 1) how the request from the Neutron-server ends up on the targeted Compute node that runs the SRIOV agent? 2) What all steps does the sriov agent in the

Re: [openstack-dev] [horizon] [neutron] Horizon support for Neutron Trunks - PTL approval needed

I have the same opinion as Kevin, UI support for a feature in the neutron repo should be in the main horizon repo. I believe this improves usability too. If I have a neutron deployment (it is a typical deployment now), I would like to use neutron feature support only after installing the main

Re: [openstack-dev] [horizon] [neutron] Horizon support for Neutron Trunks - PTL approval needed

Core Neutron features should be within Horizon, with extensions outside. This is a little hazy since even the default behaviour in Neutron is still a plugin, but thats the general idea. There are already some features outside, like the lbaas dashboard. Personally, I’d keep them in their own

Re: [openstack-dev] [QA] Announcing my candidacy for PTL of the Pike cycle

Hi gmann, Thanks for your candidacy. Let me ask one question if it's not too late. What's the role of the QA team when it comes to API change ? I have in mind the recent Glance change related to private vs shared image status. Someone in our community asked : * "I need to get an official decision

[openstack-dev] [tripleo][ui] Now with translations :)

Hi folks, You may have noticed a new type of patch in our queue this morning [1]. There's a nice link in the commit message [2][3] that describes what to do with it (TL;DR: check the structure is correct, merge it quickly - most projects have a single core approval policy for these as well, which

Re: [openstack-dev] [qa] PTL Candidacy for Pike

Hi Andrea, Thanks for your candidacy. Let me ask one question if it's not too late. What's the role of the QA team when it comes to API change ? I have in mind the recent Glance change related to private vs shared image status. Someone in our community asked : * "I need to get an official

Re: [openstack-dev] [all][api] POST /api-wg/news

On Fri, Feb 3, 2017 at 7:51 PM, Ken'ichi Ohmichi wrote: > 2017-02-03 9:56 GMT-08:00 Chris Dent : > > On Thu, 2 Feb 2017, Ken'ichi Ohmichi wrote: > >>> > >>> In today's meeting [0] after briefly covering old business we spent > >>> nearly > >>> 50

Re: [openstack-dev] [horizon] [neutron] Horizon support for Neutron Trunks - PTL approval needed

Just caught up with Kevin on IRC. If this is inside the Neutron tree, then support should live in the Horizon repo; similar to routers, floating ips etc. My initial, incorrect understanding was that it was more akin to lbaas or vpnaas. Rob On 6 February 2017 at 10:50, Kevin Benton

Re: [openstack-dev] [ironic] New mascot design

On 02/06/2017 12:49 PM, Miles Gould wrote: On 01/02/17 21:38, Lucas Alvares Gomes wrote: But, let me ask something, what the foundation really wants to achieve with this ? Cause I think we are conflating two things here: A logo (or brand) and a mascot. I think this is an excellent point. The

Re: [openstack-dev] [ironic] New mascot design

On 01/02/17 21:38, Lucas Alvares Gomes wrote: But, let me ask something, what the foundation really wants to achieve with this ? Cause I think we are conflating two things here: A logo (or brand) and a mascot. I think this is an excellent point. The constraints on logos make a lot of sense

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

On Wed, Feb 1, 2017 at 9:51 AM, Takashi Yamamoto wrote: > hi, > >>> That's great to hear Yamamoto. Since you are already a neutron-core I assume >>> you are already intimate with the work required to strengthen the VPNaaS >>> project. I have added you to [4] and you can

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 8th February

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 8th February in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

[openstack-dev] Refstack - final mascot

Hello RefStack team, Please see RefStack mascot in Heidi's note below. Catherine Diep - Forwarded by Catherine Cuong Diep/San Jose/IBM on 02/06/2017 04:18 PM - From: Heidi Joy Tretheway To: Catherine Cuong Diep/San Jose/IBM@IBMUS Date: 02/02/2017 11:42

[openstack-dev] [FFE][requirements][murano][murano-pkg-check]pdate constraint for murano-pkg-check to new release 0.3.0

Hi, all Now murano-pkg-check 0.2.0 leads the error: Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. Are you sure that git is installed? murano-pkg-check 0.3.0 will fix the incorrect package name bug. This also block the murano

Re: [openstack-dev] [requirements] [Horizon][Karbor][Magnum] Requesting FFE for xstatic packages

On Tue, Feb 07, 2017 at 10:39:41AM +1100, Richard Jones wrote: > Hi requirements team, > > We've had a downstream packager come to us with issues packaging the > Horizon RC as described in this bug report: > > https://bugs.launchpad.net/horizon/+bug/1662180 > > The issues stems from the

Re: [openstack-dev] [QA] Announcing my candidacy for PTL of the Pike cycle

Hi Jordan, Thanks for bring it up. I know we had both side of argument on those changes. IMO in general, its all QA team responsibility to verify the requirement very strictly and make sure no changes break existing released version and so users. Many times QA team does not agree to development

[openstack-dev] [heat] Meeting time changed.

Dear Team Without any further opposition, let's move our meeting time to *Wednesday 1500 UTC in #openstack-meeting-5 weekly*. Start from this week, so don't forget to attend:) Please add any item for meeting: https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-02-08_1500_UTC.29

[openstack-dev] [nova][bugs] Nova Bugs Team Meeting this Tuesday

The next meeting will be Tuesday, February 7, 2017 at 1800UTC in #openstack-meeting-4. I've updated the meeting agenda: https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam -- Augustina Ragwitz Señora Software Engineer --- Waiting for your change to get through the gate? Clean up some

Re: [openstack-dev] [FFE][requirements][murano][murano-pkg-check]pdate constraint for murano-pkg-check to new release 0.3.0

The Bot Gerrit link is: https://review.openstack.org/#/c/428200/ update constraint for murano-pkg-check to new release 0.3.0 Change-Id: I4d8cbf55525c90efd5d46f4659b57197f4c6f9f3 meta:version: 0.3.0 meta:diff-start: -

Re: [openstack-dev] [FFE][requirements][murano][murano-pkg-check]pdate constraint for murano-pkg-check to new release 0.3.0

On Tue, Feb 07, 2017 at 11:32:28AM +0800, Rong Zhu wrote: > The Bot Gerrit link is: https://review.openstack.org/#/c/428200/ > > update constraint for murano-pkg-check to new release 0.3.0 Change-Id: > I4d8cbf55525c90efd5d46f4659b57197f4c6f9f3 >

[openstack-dev] [ansible]Octavia ansible script

Hello German / All, Can we know the status of octavia ansible script ? Link :- https://blueprints.launchpad.net/~german-eichberger Is there any version available for beta testing. Can you provide us link? or time line of availability. Thank you, Santhosh

[openstack-dev] [telemetry][panko] status of pankoclient

Hi folks, As we have moved events related APIs to Panko and deprecated Ceilometer's API, the Panko will be the unique entry of event data. But I cannot find pankoclient in git.openstack.org and launchpad, instead, there is a pankoclient package in Pypi[1]. I am not sure who is the maintainer of

[openstack-dev] [cinder] cinder 10.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for cinder for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/cinder/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

[openstack-dev] [requirements] [Horizon] Requesting FFE for xstatic packages

Hi requirements team, We've had a downstream packager come to us with issues packaging the Horizon RC as described in this bug report: https://bugs.launchpad.net/horizon/+bug/1662180 The issues stems from the requirements file having several xstatic package minimum versions specified that are

[openstack-dev] [kolla] pip install kolla-ansible 4.0.0b3+ broken

Hey folks, Pip install kolla-ansible is busted. I’d take ownership of this bug myself, however, I am personally swamped. This is a DOA deliverable issue and as such is higher priority than “critical”. Can someone in the community take a look?

Re: [openstack-dev] [all][api] POST /api-wg/news

On 2/6/17 5:51 AM, Jordan Pittier wrote: [super-enormous snip -- Chris, Ken, and Jordan make good points, I encourage you to read the entire thread; I just want to concentrate on one point] > > I would say we should make compromise, not solve dilemma. I can live in a > world where we sometimes

Re: [openstack-dev] [tripleo][ui] Now with translations :)

On 02/06/2017 05:38 AM, Julie Pichon wrote: Hi folks, You may have noticed a new type of patch in our queue this morning [1]. There's a nice link in the commit message [2][3] that describes what to do with it (TL;DR: check the structure is correct, merge it quickly - most projects have a

Re: [openstack-dev] [all][api] POST /api-wg/news

On 02/06/2017 08:45 AM, Brian Rosmaita wrote: > On 2/6/17 5:51 AM, Jordan Pittier wrote: > [super-enormous snip -- Chris, Ken, and Jordan make good points, I > encourage you to read the entire thread; I just want to concentrate on > one point] >> >> I would say we should make compromise, not solve

[openstack-dev] [tripleo] TripleO Ocata release blockers

I found useful to share the reasons why we didn't release TripleO RC1 last week and what are the remaining blockers. - Nova from trunk doesn't work for TripleO. We have to pin Nova to ocata-3 if we want to continue the promotions in our CI. Some work is in progress to solve this problem, you can

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

On 02/03/2017 11:59 AM, Octave J. Orgeron wrote: Hi Mike, Comments below.. Thanks, Octave On 2/3/2017 7:41 AM, Mike Bayer wrote: On 02/02/2017 05:28 PM, Octave J. Orgeron wrote: That refers to the total length of the row. InnoDB has a limit of 65k and NDB is limited to 14k. A simple

Re: [openstack-dev] [ux] Future of the OpenStack UX team

On 2017-02-03 17:07:51 -0500 (-0500), Shamail wrote: [...] > I'll send a doodle poll next week to determine a new meeting time > and who's interested in participating. I was originally going to recommend that the previous meeting time[*] be included as one of the options in the poll for those who

Re: [openstack-dev] [Congress][olso][oslo.messaging] Dynamically Determine Rabbit Transport URL?

Excerpts from Aimee Ukasick's message of 2017-02-06 12:57:28 -0600: > Hi everyone - from the Congress standalone installation guide > (http://docs.openstack.org/developer/congress/README.html#installing-congress): > > --- > To use RabbitMQ with Congress, set the transport_url in the “From >

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Excerpts from Roman Podoliaka's message of 2017-02-03 17:16:36 +0200: > On Fri, Feb 3, 2017 at 4:41 PM, Mike Bayer wrote: > > Not sure if people on the list are seeing that we are simultaneously talking > > about getting rid of Postgresql in the efforts to support only "one > >

Re: [openstack-dev] [Oslo][all] Pike PTG idea & discussion

Not sure how much time it would require at the PTG - but I'd really like to discuss the ability to add in-code descriptions of oslo.policy objects, and eventually whatever we need to advertise new defaults. I'm hoping this will help OpenStack as a whole move towards providing better policy

Re: [openstack-dev] [horizon] [neutron] Horizon support for Neutron Trunks - PTL approval needed

> If this is inside the Neutron tree, then support should live in the Horizon > repo This sounds like a conclusion. So I have abandoned the requests on gerrit for the new repo. Instead I just uploaded a Horizon blueprint draft for Pike:

Re: [openstack-dev] Developer's deepdive of SRIOV Passthrough for Neutron

pranab boruah wrote: > Hi Folks, > We are trying to understand what happens when we launch an instance on > a compute running SRIOV agent. By "what happens" I mean, > 1) how the request from the Neutron-server ends up on the targeted > Compute node that runs the SRIOV agent? > 2) What all steps

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

On Thu, Feb 2, 2017 at 2:28 PM, Octave J. Orgeron wrote: > That refers to the total length of the row. InnoDB has a limit of 65k and > NDB is limited to 14k. > > A simple example would be the volumes table in Cinder where the row length > goes beyond 14k. So in the IF

[openstack-dev] [release] preparing to branch requirements and open pike

We have 4 cycle-with-milestone projects without any release candidates: - cinder - manila - searchlight - zaqar We're waiting to have those candidates tagged before we go ahead with the next step and branch the requirements, devstack, and grenade to let us open the pike development cycle. It

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are freewheeling to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. Continue

Re: [openstack-dev] [openstack-ansible] Propose Marc Gariepy as core reviewer

+1 On Fri, 3 Feb 2017 at 19:50 Steve Lewis wrote: > On Fri, Feb 3, 2017 at 5:33 AM, Jesse Pretorius < > jesse.pretor...@rackspace.co.uk> wrote: > > I’d like to propose Marc Gariepy [1] as a core reviewer for > OpenStack-Ansible. > > > +1. > -- > SteveL >

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Hi Mike, I've had a chance to look through the links you provided. I do think this is a rather heavy solution that would be more suited if there were actually significant dialect features to override from MySQL. MySQL and NDB use the same dialect and the differences really just come down to

[openstack-dev] [Congress][olso][oslo.messaging] Dynamically Determine Rabbit Transport URL?

Hi everyone - from the Congress standalone installation guide (http://docs.openstack.org/developer/congress/README.html#installing-congress): --- To use RabbitMQ with Congress, set the transport_url in the “From oslo.messaging” section according to your setup: transport_url =

Re: [openstack-dev] [Openstack-operators] Large Contributing OpenStack Operators working group?

Just responding to the openstack-dev@ ML thread... On 02/06/2017 11:37 AM, Steven Dake (stdake) wrote: Jay, I don’t see a reference to the wiki page in your email and don’t immediately see the LCOO working group wiki. From what you describe this working group is not working within the

Re: [openstack-dev] [ironic] New mascot design

Just thinking – horns seem pretty metal, what do you think about goat-like horned bear? :) Joanna On 2/6/17, 5:26 AM, "Sam Betts (sambetts)" wrote: +100 On 06/02/2017, 12:32, "Dmitry Tantsur" wrote: On 02/06/2017 12:49 PM,

Re: [openstack-dev] Large Contributing OpenStack Operators working group?

Jay, I don’t see a reference to the wiki page in your email and don’t immediately see the LCOO working group wiki. From what you describe this working group is not working within the framework of the 4 opens which is one of OpenStack’s fundamental philosophies. Thanks for bringing up your

Re: [openstack-dev] [horizon] [neutron] Horizon support for Neutron Trunks - PTL approval needed

My opinion is separate UI repo for just a feature would be hard to maintain, I like the idea to either create entire neutron-UI but that again raise the question will there be enough contributors or maintainers ? so horizon is the best place To have the UI part. -Manjeet From: Akihiro Motoki

Re: [openstack-dev] [ux] Future of the OpenStack UX team

> On Feb 6, 2017, at 10:43 AM, Jeremy Stanley wrote: > >> On 2017-02-03 17:07:51 -0500 (-0500), Shamail wrote: >> [...] >> I'll send a doodle poll next week to determine a new meeting time >> and who's interested in participating. > > I was originally going to recommend

Re: [openstack-dev] [all][api] POST /api-wg/news

2017-02-06 6:45 GMT-08:00 Brian Rosmaita : > On 2/6/17 5:51 AM, Jordan Pittier wrote: > [super-enormous snip -- Chris, Ken, and Jordan make good points, I > encourage you to read the entire thread; I just want to concentrate on > one point] >> >> I would say we should

[openstack-dev] [searchlight] searchlight 2.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for searchlight for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/searchlight/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will

Re: [openstack-dev] [Congress][olso][oslo.messaging] Dynamically Determine Rabbit Transport URL?

Thanks, Clint, for your quick response. Questions inline. On 02/06/2017 01:32 PM, Clint Byrum wrote: > Excerpts from Aimee Ukasick's message of 2017-02-06 12:57:28 -0600: >> Hi everyone - from the Congress standalone installation guide >>

Re: [openstack-dev] [all][api] POST /api-wg/news

2017-02-06 2:51 GMT-08:00 Jordan Pittier : >> >> >> If we change the success status code (200 ->204) without any version >> >> bumps, OpenStack clouds return different status codes on the same API >> >> operations. >> >> That will break OpenStack interoperability and

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

On 02/06/2017 01:28 PM, Octave J. Orgeron wrote: Hi Mike, I've had a chance to look through the links you provided. I do think this is a rather heavy solution that would be more suited if there were actually significant dialect features to override from MySQL. MySQL and NDB use the same

[openstack-dev] [all][elections] Last day to elect your PTL for Ironic, Keystone, Neutron, Stable Branch Maintenance and Quality_Assurance

Hello Ironic, Keystone, Neutron, Stable Branch and Quality Assurance contributors, Just a quick reminder that elections are closing soon, if you haven't already you should use your right to vote and pick your favorite candidate! Thanks for your time! -Tristan signature.asc Description:

Re: [openstack-dev] [Congress][olso][oslo.messaging] Dynamically Determine Rabbit Transport URL?

On 02/06/2017 04:09 PM, Aimee Ukasick wrote: Thanks, Clint, for your quick response. Questions inline. On 02/06/2017 01:32 PM, Clint Byrum wrote: Excerpts from Aimee Ukasick's message of 2017-02-06 12:57:28 -0600: Hi everyone - from the Congress standalone installation guide

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Hi Morgan, Comments below.. Thanks, Octave On 2/6/2017 1:04 PM, Morgan Fainberg wrote: On Thu, Feb 2, 2017 at 2:28 PM, Octave J. Orgeron > wrote: That refers to the total length of the row. InnoDB has a limit of 65k and

[openstack-dev] [zaqar] zaqar 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for zaqar for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/zaqar/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

Re: [openstack-dev] [Congress][olso][oslo.messaging] Dynamically Determine Rabbit Transport URL?

Excerpts from Jay Pipes's message of 2017-02-06 16:23:51 -0500: > On 02/06/2017 04:09 PM, Aimee Ukasick wrote: > > Thanks, Clint, for your quick response. Questions inline. > > On 02/06/2017 01:32 PM, Clint Byrum wrote: > >> Excerpts from Aimee Ukasick's message of 2017-02-06 12:57:28 -0600: > >>>

Re: [openstack-dev] [kolla] pip install kolla-ansible 4.0.0b3+ broken

This is caused by legacy issue during split kolla and kolla-ansible. this[0] line should be changed to ​​ version_info = pbr.version.VersionInfo('kolla-ansible') A dirty quick fix is install kolla along with kolla-ansible with the same version. [0]

[openstack-dev] [senlin] senlin 3.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for senlin for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/senlin/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

[openstack-dev] [Oslo][all] Pike PTG idea & discussion

Hi folks, Oslo, as OpenStack project shared common libraries need more ideas and suggestiion to make these libraries more useful. PTG is good event to collect ideas and solve problems, so please take your ideas, requirements or problem to the PTG, and feel free to edit

[openstack-dev] [karbor] Karbor Mascot draft

Hello everybody, We received the following draft for our Karbor mascot (which is a beaver, as you all surely recall). Option 1: [cid:1c17dc92-cacb-4723-8bec-cfe9b3e24b1c] Option 2: [cid:05b3a652-3127-478d-bc0d-43129125888f] Please send your thoughts here, or on IRC the meeting tomorrow.

Re: [openstack-dev] [karbor] Karbor Mascot draft

Option 1 is very cool for Karbor:) Best Regards, xiangxinyong -- Original -- From: "Yuval Brik";; Date: Mon, Feb 6, 2017 05:27 PM To: "openstack-dev@lists.openstack.org"; Subject: