Re: [openstack-dev] I want to consult ironic problems

the mirror have ramdisk and kernel and image, I want to know what do these images are used ironic python agent on ramdisk, he is how to run up in the machine after the deployment is complete, ironic python agent will run it? On Fri, Jul 29, 2016 at 6:00 PM, paul schlacter wrote: > I want to cons

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

Nova-spec is submitted: https://review.openstack.org/345138, welcome review and comments! 2016-07-11 19:08 GMT+08:00 Alex Xu : > This propose is about using ResourceProviderTags as a solution to manage > Capabilities (Qualitative) in ResourceProvider. > The ResourceProviderTags is to describe the

Re: [openstack-dev] [nova] [container] [docker] [magnum] [zun] nova-docker alternatives ?

mark wangli...@chinac.com From: yasemin Date: 2016-08-01 01:40 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] [container] [docker] [magnum] [zun] nova-docker alternatives ? that is docker swarm bay ?? On Jul 31, 2016, at 8:40 AM, Ton Ngo

Re: [openstack-dev] Priority Spec for Libvirt Storage Pools

Matt, could you review https://review.openstack.org/#/c/310505 and https://review.openstack.org/#/c/310538/ please, hoping to get them approved by end of week deadline Thanks Paul Carlton Software Engineer Cloud Services Hewlett Packard Enterprise BUK03:T242 Longdown Avenue Stoke Gifford B

Re: [openstack-dev] [tc] persistently single-vendor projects

Steven Dake (stdake) wrote: > On 7/31/16, 11:29 AM, "Doug Hellmann" wrote: >> [...] >> To be clear, I'm suggesting that projects with team:single-vendor be >> given enough time to lose that tag. That does not require them to grow >> diverse enough to get team:diverse-affiliation. > > That makes s

Re: [openstack-dev] [tc] persistently single-vendor projects

On Mon, Aug 1, 2016 at 1:09 PM, Thierry Carrez wrote: > Steven Dake (stdake) wrote: >> On 7/31/16, 11:29 AM, "Doug Hellmann" wrote: >>> [...] >>> To be clear, I'm suggesting that projects with team:single-vendor be >>> given enough time to lose that tag. That does not require them to grow >>> div

[openstack-dev] [neutron] [searchlight] What do we need in notification payload?

Hi, I'm trying to solve a issue[1, 2] which doesn't send a notification when Tag is updated. I'm worried about the payload. My solution just outputs added tag, resource type, and resource id as payload. However, there was a comment which mentioned the payload should have more information. I

Re: [openstack-dev] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core

Hi, Thanks everyone for you support, it's appreciated. Now, let's +2 something :) Emilien Macchi writes: > You might not know who Sofer is but he's actually "chem" on IRC. > He's the guy who will find the root cause of insane bugs, in OpenStack > in general but also in Puppet OpenStack modules

Re: [openstack-dev] [mistral] Promoting Dawid Deja to core reviewers

Thank you all! I'll do my best to provide good reviews and make Mistral better. Regards, Dawid Deja On Mon, 2016-08-01 at 11:05 +0700, Renat Akhmerov wrote: Team, thank you for your support! Dawid, welcome to the Mistral core team :) You now can vote +2 and approve patches. Use them wisely! Re

[openstack-dev] [vitrage] Vitrage Mascot Selection

Hi, According to the poll we had, Vitrage mascot will be a Giraffe - it's skin looks like a vitrage, and it sees everything from above. Now we should think of how we would like to illustrate it. Should we color the entire Giraffe like a Vitrage? Maybe just part of it? other ideas? (an external

Re: [openstack-dev] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

The entire core team has voted for the nomination so I’m putting it to power. Let’s all welcome Vitalii as a new core reviewer. Congratulations! > 1 серп. 2016 р. о 08:55 Aleksey Kasatkin написав(ла): > > +1 > > > Aleksey Kasatkin > > > On Mon, Jul 25, 2016 at 7:46 PM, Igor Kalnitsky

Re: [openstack-dev] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

Congratulations Vitalii! -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Mon, Aug 1, 2016 at 11:54 AM, Roman Prykhodchenko wrote: > The entire core team has voted for the nomination so I’m putting it to > power. Let’s all welcome Vitalii as a new core reviewer. Congratulation

[openstack-dev] [ironic] How should ironic and related project names be written?

Its official OpenStack policy that project names be written in lower case, for example Ironic must always be written as ironic, however I was recently writing a spec for IPA, and was unsure how to approach writing IPAs name in full. Discussing this with Dmitry on IRC, we decided it would be best

[openstack-dev] [Glance][Glare] External locations design

Hello all, I would like to start to describe some design decisions we made in Glare code (https://review.openstack.org/#/q/topic:bp/glare-api+status:open). If you are not familiar with Glare I suggest you to read the following spec: https://github.com/openstack/glance-specs/blob/master/specs/new

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 07/31/2016 10:03 PM, Alex Xu wrote: 2016-07-28 22:31 GMT+08:00 Jay Pipes mailto:jaypi...@gmail.com>>: On 07/20/2016 11:25 PM, Alex Xu wrote: One more for end users: Capabilities Discovery API, it should be 'GET /resource_providers/tags'. Or a proxy API from nova t

Re: [openstack-dev] [tc] persistently single-vendor projects

On 07/31/2016 02:29 PM, Doug Hellmann wrote: > Excerpts from Steven Dake (stdake)'s message of 2016-07-31 18:17:28 +: >> Kevin, >> >> Just assessing your numbers, the team:diverse-affiliation tag covers what >> is required to maintain that tag. It covers more then core reviewers - >> also cove

[openstack-dev] [ironic] network_interface, defaults, and explicitness

Hey all, Our nova patch for networking[0] got stuck for a bit, because Nova needs to know which network interface is in use for the node, in order to properly set up the port. The code landed for network_interface follows the following order for what is actually used for the node: 1) node.network

Re: [openstack-dev] [ironic] network_interface, defaults, and explicitness

On 2016-08-01 8:10 AM, Jim Rollenhagen wrote: Hey all, I propose that if a network_interface is not sent in the node-create call, we write whatever the current default is, so that it is always set and not using an implicit value that could change. Works for me and ensures an easier path

Re: [openstack-dev] [ironic] network_interface, defaults, and explicitness

On 01/08/2016 13:10, "Jim Rollenhagen" wrote: >Hey all, > >Our nova patch for networking[0] got stuck for a bit, because Nova needs >to know which network interface is in use for the node, in order to >properly set up the port. > >The code landed for network_interface follows the following order

Re: [openstack-dev] [all][tc] establishing project-wide goals

On 07/29/2016 04:55 PM, Doug Hellmann wrote: > One of the outcomes of the discussion at the leadership training > session earlier this year was the idea that the TC should set some > community-wide goals for accomplishing specific technical tasks to > get the projects synced up and moving in the sa

Re: [openstack-dev] [TripleO] [UI] Version

On 27.7.2016 15:18, Steven Hardy wrote: On Wed, Jul 27, 2016 at 08:41:32AM -0300, Honza Pokorny wrote: Hello folks, As the tripleo-ui project is quickly maturing, it might be time to start versioning our code. As of now, the version is set to 0.0.1 and that hardly reflects the state of the p

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Monday, August 1, 2016 1:09 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage > Capabilities with ResourceProvider > > On 07/31/2016 10:03 PM, Ale

Re: [openstack-dev] [all][tc] establishing project-wide goals

Excerpts from Sean Dague's message of 2016-08-01 08:33:06 -0400: > On 07/29/2016 04:55 PM, Doug Hellmann wrote: > > One of the outcomes of the discussion at the leadership training > > session earlier this year was the idea that the TC should set some > > community-wide goals for accomplishing spec

Re: [openstack-dev] [tc] persistently single-vendor projects

Excerpts from Fox, Kevin M's message of 2016-07-31 15:59:56 +: > This sounds good to me. > > What about making it iterative but with a delayed start. Something like: > > There is a grace period of 1 year for projects that newly join the big tent. > After which, the following criteria will be

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On Mon, Aug 1, 2016, at 08:08 AM, Jay Pipes wrote: > On 07/31/2016 10:03 PM, Alex Xu wrote: > > 2016-07-28 22:31 GMT+08:00 Jay Pipes > >: > > > > On 07/20/2016 11:25 PM, Alex Xu wrote: > > > > One more for end users: Capabilities Discovery API, it should be

Re: [openstack-dev] [tc] persistently single-vendor projects

On 08/01/2016 03:39 AM, Thierry Carrez wrote: Steven Dake (stdake) wrote: On 7/31/16, 11:29 AM, "Doug Hellmann" wrote: [...] To be clear, I'm suggesting that projects with team:single-vendor be given enough time to lose that tag. That does not require them to grow diverse enough to get team:di

Re: [openstack-dev] [tc] persistently single-vendor projects

Thierry, Ben, Doug, How can we distinguish between. "Project is doing the right thing, but others are not joining" vs "Project is actively trying to keep people out"? Thanks, Dims On Mon, Aug 1, 2016 at 9:32 AM, Ben Swartzlander wrote: > On 08/01/2016 03:39 AM, Thierry Carrez wrote: >> >> Steve

Re: [openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

On 07/31/2016 06:27 AM, huangdenghui wrote: Hi Now we have spec named subnet service types, which provides a capability of allowing different port of a network to allocate ip address from different subnet. In current implementation of DVR, fip also is distributed on every compute node, floatin

Re: [openstack-dev] [tc] persistently single-vendor projects

On 08/01/2016 09:58 AM, Davanum Srinivas wrote: > Thierry, Ben, Doug, > > How can we distinguish between. "Project is doing the right thing, but > others are not joining" vs "Project is actively trying to keep people > out"? I think at some level, it's not really that different. If we treat them

Re: [openstack-dev] [all][tc] establishing project-wide goals

On 08/01/2016 08:33 AM, Sean Dague wrote: On 07/29/2016 04:55 PM, Doug Hellmann wrote: One of the outcomes of the discussion at the leadership training session earlier this year was the idea that the TC should set some community-wide goals for accomplishing specific technical tasks to get the pr

Re: [openstack-dev] [tc] persistently single-vendor projects

Sean, So we will programatically test the metrics (if we are not doing that already) to apply/remove "team:single-vendor" tag: https://governance.openstack.org/reference/tags/team_single-vendor.html And trigger exit when the tag is present for more than 3 cycles in a row (say as of release date?

Re: [openstack-dev] [neutron] [searchlight] What do we need in notification payload?

In our (Searchlight's) ideal world, every notification about a resource would contain the full representation of that resource (for instance, equivalent to the API response for a resource), because it means that each notification on its own can be treated as the current state at that time without h

Re: [openstack-dev] [tc] persistently single-vendor projects

On 08/01/2016 10:28 AM, Davanum Srinivas wrote: > Sean, > > So we will programatically test the metrics (if we are not doing that > already) to apply/remove "team:single-vendor" tag: > > https://governance.openstack.org/reference/tags/team_single-vendor.html > > And trigger exit when the tag is

Re: [openstack-dev] [all][tc] establishing project-wide goals

On Mon, Aug 1, 2016 at 7:58 AM, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2016-08-01 08:33:06 -0400: > > On 07/29/2016 04:55 PM, Doug Hellmann wrote: > > > One of the outcomes of the discussion at the leadership training > > > session earlier this year was the idea that the TC

Re: [openstack-dev] [sahara][heat][infra] breakage of Sahara gate and images from openstack.org

On 29/07/16 13:12, Luigi Toscano wrote: Hi all, the Sahara jobs on the gate run the scenario tests (from sahara-tests) using the fake plugin, so no real Hadoop/Spark/BigData operations are performed, but other the other expected operations are executed on the image. In order to do this we used fo

Re: [openstack-dev] [sahara][heat][infra] breakage of Sahara gate and images from openstack.org

On Monday, 1 August 2016 10:56:21 CEST Zane Bitter wrote: > On 29/07/16 13:12, Luigi Toscano wrote: > > Hi all, > > the Sahara jobs on the gate run the scenario tests (from sahara-tests) > > using the fake plugin, so no real Hadoop/Spark/BigData operations are > > performed, but other the other exp

Re: [openstack-dev] [tc] persistently single-vendor projects

I am struggling to understand why we would want to remove projects from our big tent at all, as long as they are being actively developed under the principles of "four opens". It seems to me that working to disqualify such projects sends an alarming signal to our ecosystem. The reason we made th

Re: [openstack-dev] [tc] persistently single-vendor projects

Excerpts from Sean Dague's message of 2016-08-01 10:31:44 -0400: > On 08/01/2016 10:28 AM, Davanum Srinivas wrote: > > Sean, > > > > So we will programatically test the metrics (if we are not doing that > > already) to apply/remove "team:single-vendor" tag: > > > > https://governance.openstack.or

Re: [openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

Yes, as Brian says this will be covered by the follow-up patch to [2] which I¹m currently working on. Thanks for the question. John On 8/1/16, 3:17 PM, "Brian Haley" wrote: >On 07/31/2016 06:27 AM, huangdenghui wrote: >> Hi >>Now we have spec named subnet service types, which provides a >>

Re: [openstack-dev] [tc] persistently single-vendor projects

Excerpts from Adrian Otto's message of 2016-08-01 15:14:48 +: > I am struggling to understand why we would want to remove projects from our > big tent at all, as long as they are being actively developed under the > principles of "four opens". It seems to me that working to disqualify such >

Re: [openstack-dev] [all][tc] establishing project-wide goals

Excerpts from Shamail Tahir's message of 2016-08-01 09:49:35 -0500: > On Mon, Aug 1, 2016 at 7:58 AM, Doug Hellmann wrote: > > > Excerpts from Sean Dague's message of 2016-08-01 08:33:06 -0400: > > > On 07/29/2016 04:55 PM, Doug Hellmann wrote: > > > > One of the outcomes of the discussion at the

[openstack-dev] [all][infra] NOT_REGISTERED to be or not to be

Hi, Currently in some cases[1] CI sets a comment on the patch set as NOT_REGISTERED. Those comments are very hard to monitor for CI operators and have noisy value for the developers. Maybe a better solution is not commenting in such cases at all as discussed in [2]. If a developer is missing

Re: [openstack-dev] [all][tc] establishing project-wide goals

Excerpts from Jay Pipes's message of 2016-08-01 10:23:57 -0400: > On 08/01/2016 08:33 AM, Sean Dague wrote: > > On 07/29/2016 04:55 PM, Doug Hellmann wrote: > >> One of the outcomes of the discussion at the leadership training > >> session earlier this year was the idea that the TC should set some

Re: [openstack-dev] [tc] persistently single-vendor projects

FYI- I'm totally in favor of eviction. But... On Mon, Aug 1, 2016 at 8:42 AM Doug Hellmann wrote: > > I'm interested in hearing other reasons that we should keep these > sorts of projects, though. I'm not yet ready to propose the change > to the policy myself. ...if the social consequences res

[openstack-dev] Changing the repo descriptions in the github mirrors

Hey everybody! Recently some of us in Infra land were browsing through the upstream git source code, and happened to notice their repo description in github: https://github.com/git//git "Git Source Code Mirror - This is a publish-only repository and all pull requests are ignored. Please follow D

Re: [openstack-dev] [tc] persistently single-vendor projects

Excerpts from Michael Krotscheck's message of 2016-08-01 16:06:45 +: > FYI- I'm totally in favor of eviction. But... > > On Mon, Aug 1, 2016 at 8:42 AM Doug Hellmann wrote: > > > > > I'm interested in hearing other reasons that we should keep these > > sorts of projects, though. I'm not yet

Re: [openstack-dev] [tc] persistently single-vendor projects

On Mon, 2016-08-01 at 11:38 -0400, Doug Hellmann wrote: > Excerpts from Adrian Otto's message of 2016-08-01 15:14:48 +: > > I am struggling to understand why we would want to remove projects > > from our big tent at all, as long as they are being actively > > developed under the principles of "

[openstack-dev] [Infra] Meeting Tuesday August 2nd at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday August 2nd, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agenda i

[openstack-dev] [HA] weekly High Availability meetings on IRC: change of time

Hi everyone, I have proposed moving the weekly High Availability IRC meetings one hour later, back to the original time of 0900 UTC every Monday. https://review.openstack.org/#/c/349601/ Everyone is welcome to attend these meetings, so if you think you are likely to regularly attend, feel free

Re: [openstack-dev] [ironic] network_interface, defaults, and explicitness

On Mon, Aug 01, 2016 at 08:10:18AM -0400, Jim Rollenhagen wrote: > Hey all, > > Our nova patch for networking[0] got stuck for a bit, because Nova needs > to know which network interface is in use for the node, in order to > properly set up the port. > > The code landed for network_interface foll

Re: [openstack-dev] [all][infra] NOT_REGISTERED to be or not to be

Thanks starting the discussion, Lenny. I thought about a way to accomplish that, and came up with few options: - Pre-register all possible jenkins jobs with gearman. This only avoids not registered errors due to gearman server restart, not if you misconfigured your system; - Add option to zuul

Re: [openstack-dev] [tc] persistently single-vendor projects

On 08/01/2016 12:24 PM, James Bottomley wrote: > On Mon, 2016-08-01 at 11:38 -0400, Doug Hellmann wrote: >> Excerpts from Adrian Otto's message of 2016-08-01 15:14:48 +: >>> I am struggling to understand why we would want to remove projects >>> from our big tent at all, as long as they are bein

[openstack-dev] [HA] RFC: High Availability track at future Design Summits

Hi all, I doubt anyone would dispute that High Availability is a really important topic within OpenStack, yet none of the OpenStack conferences or Design Summits so far have provided an "official" track or similar dedicated space for discussion on HA topics. This is becoming increasingly problema

Re: [openstack-dev] [tc] persistently single-vendor projects

On Aug 1, 2016, at 10:14 AM, Adrian Otto wrote: > I am struggling to understand why we would want to remove projects from our > big tent at all, as long as they are being actively developed under the > principles of "four opens". It seems to me that working to disqualify such > projects sends

Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission

>-Original Message- >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] >Sent: Friday, July 29, 2016 6:37 PM >To: openstack-dev@lists.openstack.org >Subject: Re: [openstack-dev] [nova] [infra] Intel NFV CI voting permission > >On 7/29/2016 10:47 AM, Znoinski, Waldemar wrote:

[openstack-dev] [tripleo] HA NG status

Hi all, just wanted to give a short status on the work around the HA architecture described in the SPEC here: https://review.openstack.org/299628 (blueprint here [1]) The last chunk of the work is currently contained in these two reviews: https://review.openstack.org/#/c/342650/ - cinder volume c

Re: [openstack-dev] [nova] os-virtual-interfaces isn't deprecated in 2.36

2016-07-29 10:32 GMT-07:00 Sean Dague : > On 07/28/2016 05:38 PM, Matt Riedemann wrote: >> On 7/28/2016 3:55 PM, Matt Riedemann wrote: >>> For os-attach-interfaces, we need that to attach/detach interfaces to a >>> server, so those actions don't go away with 2.36. We can also list and >>> show inte

Re: [openstack-dev] [tc] persistently single-vendor projects

On Mon, 2016-08-01 at 13:43 -0400, Sean Dague wrote: > On 08/01/2016 12:24 PM, James Bottomley wrote: > > Making no judgments about the particular exemplars here, I would > > just like to point out that one reason why projects exist with very > > little diversity is that they "just work". Usually

Re: [openstack-dev] [all][infra] NOT_REGISTERED to be or not to be

On Mon, Aug 01, 2016 at 03:53:12PM +, Lenny Verkhovsky wrote: > Hi, > > Currently in some cases[1] CI sets a comment on the patch set as > NOT_REGISTERED. > > Those comments are very hard to monitor for CI operators and have noisy value > for the developers. > > Maybe a better solution is

[openstack-dev] [ironic] Driver composition defaults call

Greetings! As discussed in our meeting today[0], we would like to try and schedule a time for a VoIP call so we can discuss driver composition[1] defaults with the goal of reaching a consensus on defaults. Given that there are several facets, and multiple people in multiple timezones who need to

[openstack-dev] [Neutron][IPAM] Pluggable IPAM rollback issue

Hi all, Last Thursday, I spent the afternoon looking in to a bug with pluggable IPAM [1] which is preventing me from deciding to pull the trigger on finally switching from the old non-pluggable reference implementation. I'd *really* like to get this in shape for Newton but time is running out. I'

[openstack-dev] [puppet] weekly meeting #89

Hi Puppeteers! We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting-4. Here's a first agenda: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160802 Feel free to add topics, and any outstanding bug and patch. See you tomorrow! Thanks, -- Emilien Macchi __

[openstack-dev] [docker] [magnum] Magnum account on Docker Hub

Hi everyone, At the last IRC meeting, the team discussed the need for hosting some container images on Docker Hub to facilitate development. There is currently a Magnum account on Docker Hub, but this is not owned by anyone on the team, so we would like to find who the owner is and whether t

Re: [openstack-dev] [nova] os-virtual-interfaces isn't deprecated in 2.36

On 8/1/2016 1:39 PM, Ken'ichi Ohmichi wrote: 2016-07-29 10:32 GMT-07:00 Sean Dague : On 07/28/2016 05:38 PM, Matt Riedemann wrote: On 7/28/2016 3:55 PM, Matt Riedemann wrote: For os-attach-interfaces, we need that to attach/detach interfaces to a server, so those actions don't go away with 2.3

Re: [openstack-dev] [Neutron][IPAM] Pluggable IPAM rollback issue

>We still want the exception to rollback the entire API operation and stopping it with a nested operation I think would mess that up. Well I think you would want to start a nested transaction, capture the duplicate, call the ipam delete methods, then throw a retryrequest. The exception will still

Re: [openstack-dev] [TripleO] [UI] Version

On Mon, Aug 1, 2016 at 8:36 AM, Jiri Tomasek wrote: > > > On 27.7.2016 15:18, Steven Hardy wrote: > >> On Wed, Jul 27, 2016 at 08:41:32AM -0300, Honza Pokorny wrote: >> >>> Hello folks, >>> >>> As the tripleo-ui project is quickly maturing, it might be time to start >>> versioning our code. As o

Re: [openstack-dev] [OpenStack-Infra] Announcing Gertty 1.4.0

Masayuki Igawa writes: > Hi! > > On Wed, Jul 27, 2016 at 11:50 PM, James E. Blair wrote: >> Michał Dulko writes: >> >>> Just wondering - were there tries to implement syntax highlighting in >>> diff view? I think that's the only thing that keeps me from switching to >>> Gertty. >> >> I don't kn

Re: [openstack-dev] [OpenStack-Infra] Announcing Gertty 1.4.0

On 2016-08-01 14:00:12 -0700 (-0700), James E. Blair wrote: [...] > We essentially have two channels of information that we want to > represent with color -- the diff, and the syntax. They can sometimes > overlap. [...] One option that probably wouldn't bug me too much is if it could be toggled o

[openstack-dev] [nova][ironic] A couple feature freeze exception requests

Yes, I know this is stupid late for these. I'd like to request two exceptions to the non-priority feature freeze, for a couple of features in the Ironic driver. These were not requested at the normal time as I thought they were nowhere near ready. Multitenant networking == I

[openstack-dev] [nova] Belated nova newton midcycle recap

It's a little late but I wanted to get a high level recap of the nova newton midcycle written up for those that didn't make it. First off, thanks again to Intel for hosting and especially to Cindy Sirianni at Intel for making sure we were taken care of. We had about 40 people each day in a sin

Re: [openstack-dev] [nova] Belated nova newton midcycle recap

On 8/1/2016 4:19 PM, Matt Riedemann wrote: It's a little late but I wanted to get a high level recap of the nova newton midcycle written up for those that didn't make it. First off, thanks again to Intel for hosting and especially to Cindy Sirianni at Intel for making sure we were taken care of.

Re: [openstack-dev] [sahara][heat][infra] breakage of Sahara gate and images from openstack.org

On 02/08/16 03:11, Luigi Toscano wrote: On Monday, 1 August 2016 10:56:21 CEST Zane Bitter wrote: On 29/07/16 13:12, Luigi Toscano wrote: Hi all, the Sahara jobs on the gate run the scenario tests (from sahara-tests) using the fake plugin, so no real Hadoop/Spark/BigData operations are performe

Re: [openstack-dev] Announcing Gertty 1.4.0

For some reason I installed the newer version but still the version string reports Gertty version: 1.1.1.dev24 -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-req

Re: [openstack-dev] [OpenStack-Infra] Announcing Gertty 1.4.0

On Mon, Aug 1, 2016 at 4:00 PM, James E. Blair wrote: > Masayuki Igawa writes: > >> Hi! >> >> On Wed, Jul 27, 2016 at 11:50 PM, James E. Blair wrote: >>> Michał Dulko writes: >>> Just wondering - were there tries to implement syntax highlighting in diff view? I think that's the only t

Re: [openstack-dev] [OpenStack-Infra] Announcing Gertty 1.4.0

On 2016-08-01 17:38:59 -0500 (-0500), Mikhail Medvedev wrote: > In theory it is possible split diff and syntax spatially, so there > would be no need to mix diff and syntax colors. Mockup > http://i.imgur.com/gAD9x9v.png That's not too bad on the eyes, though as an avid user of the unified diff vi

Re: [openstack-dev] Announcing Gertty 1.4.0

"Sean M. Collins" writes: > For some reason I installed the newer version but still the version > string reports > > Gertty version: 1.1.1.dev24 When I install it from pypi via pip in a new virtualenv, I see: Gertty version: 1.4.0 Maybe you have an older copy installed from a git repo as edi

Re: [openstack-dev] [OpenStack-Infra] Announcing Gertty 1.4.0

Mikhail Medvedev writes: > > In theory it is possible split diff and syntax spatially, so there > would be no need to mix diff and syntax colors. Mockup > http://i.imgur.com/gAD9x9v.png True, though I should have clarified my comments as applying particularly to the intra-line diff, where not on

Re: [openstack-dev] [octavia]redirection and barbican config

Hi Michael, Thanks. I have few more queries: - Is it possible to create multiple VIPs on one amphora? -I created a LB 2 days back. I created all the objects loadbalancer, listener, pool and members. The curl was successful for the vip. Today I added one more listener listening on port 443 (Termina

Re: [openstack-dev] [nova][ironic] A couple feature freeze exception requests

On 08/01/2016 05:20 PM, Jim Rollenhagen wrote: Yes, I know this is stupid late for these. I'd like to request two exceptions to the non-priority feature freeze, for a couple of features in the Ironic driver. These were not requested at the normal time as I thought they were nowhere near ready.

Re: [openstack-dev] [Networking-vSphere]

On 07/14/2016 09:28 AM, Igor Gajsin wrote: Thanks for quick reply. Likewise, apologies for the delayed response! :( Let's restore the context. I develop plugin for Fuel that uses Networking-vSphere as the network driver. Next release of Fuel, 9.1 and maybe 9.X will based on mitaka. Understo

Re: [openstack-dev] [Neutron][IPAM] Pluggable IPAM rollback issue

On Mon, Aug 1, 2016 at 2:29 PM, Kevin Benton wrote: > >We still want the exception to rollback the entire API operation and > stopping it with a nested operation I think would mess that up. > > Well I think you would want to start a nested transaction, capture the > duplicate, call the ipam delet

[openstack-dev] [tacker] Weekly meeting Aug, 2, 2016 cancelled

Tackers, Since we just met last Wed & Thurs for our midcycle meetup and, there is no solid agenda item, I'm cancelling tomorrow's Tacker weekly meeting. Please use the extra time to continue to review and push patchsets for Newton features like, VNF-FFG VNF Scaling Event Audit Support Alarm Moni

[openstack-dev] [nova] Belated nova newton midcycle recap (part 2)

Starting from where I accidentally left off: * Vendor metadata reboot We agreed that we still wanted mikal to keep working on this so we can keep a timeline for removing the deprecated dynamic vendor data classloader. The API change was merged last week: https://review.openstack.org/#/c/3177

Re: [openstack-dev] [heat][requirements] Re: [Openstack-stable-maint] Stable check of openstack/heat failed

Hi Tony, patch https://review.openstack.org/#/c/347634/ for master branch is merged, patch for mitaka https://review.openstack.org/#/c/347637/ and for liberty https://review.openstack.org/#/c/347639/ are be

Re: [openstack-dev] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core

A great number of positive votes, thanks for your feedback. Thanks Sofer, and keep rocking! On Mon, Aug 1, 2016 at 5:05 AM, Sofer Athlan-Guyot wrote: > Hi, > > Thanks everyone for you support, it's appreciated. Now, let's +2 > something :) > > Emilien Macchi writes: > >> You might not know who

Re: [openstack-dev] [all][tc] establishing project-wide goals

Thanks Doug, > On Aug 1, 2016, at 10:44 AM, Doug Hellmann wrote: > > Excerpts from Shamail Tahir's message of 2016-08-01 09:49:35 -0500: >>> On Mon, Aug 1, 2016 at 7:58 AM, Doug Hellmann wrote: >>> >>> Excerpts from Sean Dague's message of 2016-08-01 08:33:06 -0400: > On 07/29/2016 04:55 P

[openstack-dev] [gnocchi] Support for other drivers - influxdb

Hi Gnocchi Devs, We have been using gnocchi for a while now with the influxDB driver and are keen to get the influxdb driver back into upstream. However looking into the code and how it’s arranged it looks like there are a lot of assumptions that the backend storage driver is carbonara based.

Re: [openstack-dev] [OpenStack-Infra] Announcing Gertty 1.4.0

On Mon, 1 Aug 2016 17:38:59 -0500 Mikhail Medvedev wrote: > > We essentially have two channels of information that we want to > > represent with color -- the diff, and the syntax. They can sometimes > > overlap. > > > > Perhaps we could use a 256 color (or even RGB) terminal for this > > feature

[openstack-dev] [Nova] Does this api modification need Microversion?

patchset url: https://review.openstack.org/#/c/334747/ Allow "revert_resize" to recover error instance after resize/migrate. When resize/migrate instance, if error occurs on source compute node, instance state can rollback to active currently. But if error occurs in "finish_resize" function

Re: [openstack-dev] [ironic] network_interface, defaults, and explicitness

The proposed approach is reasonable. Just a small adding. I think for a longterm concept it would be good to avoid setting binding_host_id in ironic virt_driver. We should force users to set it when 'binding_profile' is updated. It looks weird that we telling Neutron to bind port at one place and a