Re: [openstack-dev] [neutron][tc] Neutron stadium evolution from Austin

Armando has submitted the proposal on Gerrit [1]. Let's take the discussion there. [1] https://review.openstack.org/#/c/312199/7 Fawad Khaliq On Tue, May 3, 2016 at 2:37 AM, Doug Wiegley wrote: > Were we looking at the same etherpad? I think the ‘inclusion

Re: [openstack-dev] [tricircle] Easy Way to Test Tricircle North-South L3 Networking

Hi Team, If a main problem is a number of network interfaces (I guess it's a problem), here is more eco solution. In side your linux box, you can add virtual network interfaces with multiple subnets. It's not related to this project. But it may be better to show the followings for someone who are

Re: [openstack-dev] [app-catalog] [glare] [murano] [mistral] Austin summit summary: Community App Catalog

> On 06 May 2016, at 03:00, Christopher Aedo wrote: > > On Wed, May 4, 2016 at 9:15 PM, Renat Akhmerov > wrote: > > Cool, feel free to communicate with us on adding Mistral assets into the > > catalog. > > Of course! We started a blueprint for the

Re: [openstack-dev] [Congress] Austin recap

Thanks for the summary, Tim. Very productive summit! I¹ve added more notes and a diagram to the HA ether pad. Is that the best way to continue the discussion? https://etherpad.openstack.org/p/newton-congress-availability From: Tim Hinrichs Reply-To: "OpenStack Development

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Got it with thanks. Best regards, Yipei On Fri, May 6, 2016 at 9:48 AM, joehuang wrote: > Hi, Yipei, > > Shinobu is correct, this should be taken into consideration in the design > of dynamic pod binding. > > How to schedule pod, you can refer to host-aggregate scheduling

Re: [openstack-dev] [neutron][FWaaS] __init__ arguments issue status

This break is almost certainly because of the following neutron change, to unwind the incestuous inheritance that was in neutron (dependency arrow was circular): https://review.openstack.org/#/c/223343/ I don’t expect there will be a lot of appetite

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Hi, Yipei, Shinobu is correct, this should be taken into consideration in the design of dynamic pod binding. How to schedule pod, you can refer to host-aggregate scheduling with flavor, the difference is that the scheduling granularity is on pod level. By the tag in flavor extra-spec and

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

+1, Michal has been contributing good quality code and reivew since he got involved with Cinder. It's great to have him as core. On May 6, 2016 8:56 AM, "Alex Meade" wrote: +1 I thought he was already! which is usually a good sign. On Thu, May 5, 2016 at 1:39 PM, Mike

Re: [openstack-dev] [neutron][FWaaS] __init__ arguments issue status

Hi Doug. The old and new MROs are both pretty complicated, and it’s not entirely clear to me yet why the original one worked. (The MROs are included below for reading pleasure; they're embellished to show the incoming args to self’s init and outgoing args to super’s init in each case.) I’m

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

+1 I thought he was already! which is usually a good sign. On Thu, May 5, 2016 at 1:39 PM, Mike Perez wrote: > On 13:16 May 03, Sean McGinnis wrote: > > Hey everyone, > > > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > > contributions with both

[openstack-dev] [nova] Austin summit priorities session recap

There are still a few design summit sessions from the summit that I'll recap but I wanted to get the priorities session recap out as early as possible. We held that session in the last slot on Thursday. The full etherpad is here [1]. The first part of the session was mostly going over

[openstack-dev] [Cloudlet] Need help in creating RST file for specs

Hi all, Bit rusty returning after Havana to OpenStack for Dev issues. Goal : Need help in creating a new proposal for Cloudlet...Any takers please respond. Am sure with knowledgeable folks like we have in OpenStack dev,  all I need to say is this like a Data Center at the Edge in a VM or

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Hi Yipei, On Thu, May 5, 2016 at 9:54 PM, Yipei Niu wrote: > Hi, all, > > For dynamic pod binding, I have some questions. > [snip] > 3. How is Tricircle aware of what type of resource wanted by tenants? For > example, a tenant wants to boot VMs for CAD modelling with

Re: [openstack-dev] [Keystone][Nova] Any Code Examples of Other Services Using Keystone Policy?

On 05/05/2016 05:54 PM, Dolph Mathews wrote: My understanding from the summit session was that we should have a specific role defined in keystone's policy.json here: https://github.com/openstack/keystone/blob/a16287af5b7761c8453b2a8e278d78652497377c/etc/policy.json#L37 Which grants access to

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On Thu, May 05, 2016 at 02:35:46PM -0400, Doug Hellmann wrote: > This has been a lively thread, and the summit session was similarly > animated. I'm glad to see so much interest in managing our dependencies! > > As we discussed at the summit, my primary objective with dependency > management

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On Thu, May 05, 2016 at 04:18:08PM -0400, Davanum Srinivas wrote: > prometheanfire, > > I'll get the ball rolling next week. i.e, schedule a meeting, get > started on writing down what we do usually for vetting requirements > changes etc. Please try to set this for a time that isn't terrible for

Re: [openstack-dev] [nova][live migration] Request to merge initial storage pool patches

On Fri, May 6, 2016 at 12:50 AM, Matthew Booth wrote: > I mentioned in the meeting last Tuesday that there are now 2 of us working > on the persistent storage metadata patches: myself and Diana Clarke. I've > also been talking to Paul Carlton today trying to work out how he

Re: [openstack-dev] [neutron][FWaaS] __init__ arguments issue status

Excerpts from Nate Johnston's message of 2016-05-05 17:40:13 -0400: > FWaaS team, > > After a day of looking at the tests currently failing in the FWaaS repo, I > believe I have the issue narrowed down considerably. First, to restate what > is going on. If you check out the neutron-fwaas

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

Hi everyone, We had a discussion on the two topics during the summit. Here is the etherpad link for the discussion. https://etherpad.openstack.org/p/Neutron-FC-OVSAgentExt-Austin-Summit We agreed to continue the discussion on Neutron channel on a weekly basis. It seems UTC 1700 ~ UTC 1800

Re: [openstack-dev] cross-OpenStack L2 Networking spec review

Hi Joe, Thank you for your message. I've CCed dev list since we are still seeking more awesome contributors to accelerate and improve this project. And I believe that this topic you wrote up in your previous message is one of interesting topics. Cheers, Shinobu On Thu, May 5, 2016 at 6:29 PM,

Re: [openstack-dev] Requirements for becoming approved official project

Thank you for suggestions. At this stage, we are just trying to become an official project. Cheers, S On Fri, May 6, 2016 at 2:50 AM, Doug Hellmann wrote: > Excerpts from Mike Perez's message of 2016-05-05 09:59:58 -0700: >> On 14:40 Apr 30, Shinobu Kinjo wrote: >> > Hi

Re: [openstack-dev] [Keystone][Nova] Any Code Examples of Other Services Using Keystone Policy?

> I'm currently working on the spec for Project ID Validation in Nova > using Keystone. The outcome of the Design Summit Session was that the > Nova service user would use the Keystone policy to establish whether the > requester had access to the project at all to verify the id. I was > wondering

Re: [openstack-dev] [Keystone][Nova] Any Code Examples of Other Services Using Keystone Policy?

My understanding from the summit session was that we should have a specific role defined in keystone's policy.json here: https://github.com/openstack/keystone/blob/a16287af5b7761c8453b2a8e278d78652497377c/etc/policy.json#L37 Which grants access to nothing in keystone beyond that check. So, the

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Ian Cordasco's message of 2016-05-05 16:10:09 -0500: >   > > -Original Message- > From: Haïkel > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: May 5, 2016 at 15:25:08 > To: 

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Davanum Srinivas (dims)'s message of 2016-05-05 16:18:08 -0400: > prometheanfire, > > I'll get the ball rolling next week. i.e, schedule a meeting, get > started on writing down what we do usually for vetting requirements > changes etc. Thanks, Dims! Doug > > Thanks, > Dims > >

[openstack-dev] [neutron][FWaaS] __init__ arguments issue status

FWaaS team, After a day of looking at the tests currently failing in the FWaaS repo, I believe I have the issue narrowed down considerably. First, to restate what is going on. If you check out the neutron-fwaas repository and run `tox -e py27` in it, you will get six errors all in the

Re: [openstack-dev] [Manila] Any updates on share groups?

Hi, John. In the Friday session, the community agreed that groups would support multiple share types in the same group, that they would be called ‘share groups’, and that a higher-level, multi-backend grouping construct to be discussed later would be more flexible if based on something like

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

  -Original Message- From: Haïkel Reply: OpenStack Development Mailing List (not for usage questions) Date: May 5, 2016 at 15:25:08 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [neutron][devstack] State of the refactor

On 5 May 2016 at 11:31, Sean M. Collins wrote: > Sean M. Collins wrote: > > Here is the patch I'm using to test the refactor against the Neutron > > CI jobs. > > > > https://review.openstack.org/#/c/278417/ > > > > Here's the test patch to make sure anything that is using the

Re: [openstack-dev] [neutron][devstack] State of the refactor

Where do I propose my new option NEUTRON_MAYBE_L3_MTU_VXLAN_AGENTMODE_FLOATINGIPS ? On Thu, May 5, 2016 at 11:31 AM, Sean M. Collins wrote: > Sean M. Collins wrote: > > Here is the patch I'm using to test the refactor against the Neutron > > CI jobs. > > > >

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

Another few related things: * We tend to build our images in vm's. so if libguestfs has to spawn in a vm nested in that vm, it may have some performance issues. DIB doesn't have that problem. * We used to build our centos 6 images without grub a while back, but the first yum upgrade that

Re: [openstack-dev] [tc] License for specs repo

On 05/05/2016 04:01 PM, Davanum Srinivas wrote: Ben, Have you seen this yet? http://lists.openstack.org/pipermail/legal-discuss/2014-March/000201.html https://wiki.openstack.org/wiki/Governance/Foundation/15Oct2012BoardMinutes#Approval_of_the_CCBY_License_for_Documentation. No I hadn't seen

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Well, I'm more in favor having it as a sub-team of release mgmt team. H, __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 05/05/2016 03:18 PM, Davanum Srinivas wrote: > prometheanfire, > > I'll get the ball rolling next week. i.e, schedule a meeting, get > started on writing down what we do usually for vetting requirements > changes etc. > > Thanks, > Dims Thanks, it's nice to have just from a planning

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

prometheanfire, I'll get the ball rolling next week. i.e, schedule a meeting, get started on writing down what we do usually for vetting requirements changes etc. Thanks, Dims On Thu, May 5, 2016 at 4:13 PM, Matthew Thode wrote: > On 05/05/2016 01:35 PM, Doug

[openstack-dev] [UX] OpenStack UX core nomination

I would like to nominate Shamail Tahir as a core for the OpenStack UX project. Shamail has been central to developing a set of personas for the overall community and providing his significant expertise with customers. In some ways, he has also been our focal to the other community projects.

Re: [openstack-dev] [app-catalog] [glare] [murano] [mistral] Austin summit summary: Community App Catalog

On Wed, May 4, 2016 at 9:15 PM, Renat Akhmerov wrote:> Cool, feel free to communicate with us on adding Mistral assets into the> catalog.Of course!  We started a blueprint for the related tasks[1] and hopefully myself or someone from the Mistral team will be able to take

[openstack-dev] [Keystone][Nova] Any Code Examples of Other Services Using Keystone Policy?

I'm currently working on the spec for Project ID Validation in Nova using Keystone. The outcome of the Design Summit Session was that the Nova service user would use the Keystone policy to establish whether the requester had access to the project at all to verify the id. I was wondering if there

Re: [openstack-dev] [tc] License for specs repo

Ben, Have you seen this yet? http://lists.openstack.org/pipermail/legal-discuss/2014-March/000201.html https://wiki.openstack.org/wiki/Governance/Foundation/15Oct2012BoardMinutes#Approval_of_the_CCBY_License_for_Documentation. Thanks, Dims On Thu, May 5, 2016 at 3:44 PM, Ben Swartzlander

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

Thanks Peter, that is very helpful. I’ve added your comments to the etherpad (https://etherpad.openstack.org/p/image-generation-in-openstack) -amrith From: Nordquist, Peter L [mailto:peter.nordqu...@pnnl.gov] Sent: Thursday, May 05, 2016 12:29 PM To: OpenStack Development Mailing List (not for

Re: [openstack-dev] [tc] License for specs repo

On 05/05/2016 03:24 PM, Jeremy Stanley wrote: On 2016-05-05 12:03:38 -0400 (-0400), Ben Swartzlander wrote: It appears that many of the existing specs repos contain a confusing mixture of Apache 2.0 licensed code and Creative Commons licensed docs. [...] Recollection is that the prose was

Re: [openstack-dev] [tc] License for specs repo

On 2016-05-05 12:03:38 -0400 (-0400), Ben Swartzlander wrote: > It appears that many of the existing specs repos contain a > confusing mixture of Apache 2.0 licensed code and Creative Commons > licensed docs. [...] Recollection is that the prose was intended to be under CC Attrib. in line with

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

Pete, please clarify … I was going to push the dib elements that we currently have and you were writing CentOS elements. Is that right? Seems like there are some crossed wires here. -amrith From: Victoria Martínez de la Cruz [mailto:victo...@vmartinezdelacruz.com] Sent: Thursday, May 05, 2016

Re: [openstack-dev] [neutron][devstack] State of the refactor

On 2016-05-05 15:57:22 + (+), Sean M. Collins wrote: [...] > So we did. > > https://review.openstack.org/168438 [...] Remind me to buy you and Dean beer the next time I see you. It's like you flipped the Etch A Sketch upside down and shook vigorously. <> -- Jeremy Stanley

Re: [openstack-dev] [nova][cinder] Austin summit nova/cinder cross-project session recap

Hi All, First of all thanks Matt for the detailed summary about last week. As a continuation I would like to add the meeting minutes I captured today on the Hangout referred below. As an overall summary, the most important step for today was to move back a little from multi-attach and try to

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Doug Hellmann's message of 2016-04-17 11:13:15 -0400: > I am organizing a summit session for the cross-project track to > (re)consider how we manage our list of global dependencies [1]. > Some of the changes I propose would have a big impact, and so I > want to ensure everyone doing

Re: [openstack-dev] [neutron][devstack] State of the refactor

Sean M. Collins wrote: > Here is the patch I'm using to test the refactor against the Neutron > CI jobs. > > https://review.openstack.org/#/c/278417/ > Here's the test patch to make sure anything that is using the neutron-legacy file isn't disrupted: https://review.openstack.org/#/c/313049/

Re: [openstack-dev] [neutron][fwaas][vpnaas][lbaas][octavia] summit summary - future of the advanced services

Hi All: Doug, thanks for the update and agree. On fwaas - we have some new contributors who are enthusiastic to make things happen in N. But if contributor priorities change and we struggle - will reach out to expedite the removal. Thanks Sridar On 5/5/16, 9:56 AM, "Doug Wiegley"

Re: [openstack-dev] [tc] Swift api compat. Was: supporting Go

I strongly disagree. Would we be happy if we stripped out all of the code out of nova for non kvm and said, "if you want vmware or xen, support you have to reimplement nova from scratch in an api compatible way out of tree"? "And on top of that, we won't ever test compatibility for anything

[openstack-dev] [kolla] Ironic broken on Ubuntu

Hi, Trying to setup an Ironic environment on Ubuntu. CONTAINER IDIMAGECOMMAND CREATED STATUS PORTSNAMES 0838b01dcd34 192.168.32.203:4000/kollaglue/ubuntu-source-ironic-inspector:2.0.0 "kolla_start"

Re: [openstack-dev] Requirements for becoming approved official project

Excerpts from Mike Perez's message of 2016-05-05 09:59:58 -0700: > On 14:40 Apr 30, Shinobu Kinjo wrote: > > Hi Tom, > > > > First sorry for bothering you -; > > > > We are trying to make the tricircle project [1] one of the opnestack > > official projects. And we are referring to project team

[openstack-dev] [release] Release countdown for week R-21, May 9-13

Welcome back from summit! As we did last cycle, the release team will be sending reminder emails as we count down toward the Newton release. If all goes as planned, these emails will be sent just before the week mentioned in the subject (on my Thursday, but some of you live in the future).

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

On 13:16 May 03, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > contributions with both code reviews [0] and code contributions [1] have > been significant for some time now. +1 welcome! -- Mike Perez

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

In a chat on the Infra channel there was a suggestion that we create an etherpad to track issues with DIB. https://etherpad.openstack.org/p/image-generation-in-openstack I’ve created an etherpad above and populated it with some information that I have. I’ll post the etherpad on the infra IRC

Re: [openstack-dev] [nova][live migration] Request to merge initial storage pool patches

On 5/5/2016 10:20 AM, Jay Pipes wrote: On 05/05/2016 10:50 AM, Matthew Booth wrote: TL;DR Core reviewers: please review the first 5 patches listed above. There will be cake. I only accept payment in cookies. -jay __

Re: [openstack-dev] [neutron][devstack] State of the refactor

Terrific decision! Thank a lot for all this great work. Edgar On 5/5/16, 9:12 AM, "Monty Taylor" wrote: >On 05/05/2016 10:57 AM, Sean M. Collins wrote: >> During the Austin summit, there was a discussion in the QA meetings >> about the future of Neutron's support in

Re: [openstack-dev] Requirements for becoming approved official project

On 14:40 Apr 30, Shinobu Kinjo wrote: > Hi Tom, > > First sorry for bothering you -; > > We are trying to make the tricircle project [1] one of the opnestack > official projects. And we are referring to project team guide to make > sure what are requirements. [2]. Reading this guide, what we

[openstack-dev] [neutron][fwaas][vpnaas][lbaas][octavia] summit summary - future of the advanced services

Egads, that’s a long subject prefix. Anyways, we had a design session on the future of the advanced services: https://etherpad.openstack.org/p/newton-neutron-future-adv-services In a nutshell, vpn and fw are critically lacking active contributors at present. Again. A proposal was made to

Re: [openstack-dev] [tc] supporting Go

Excerpts from Hayes, Graham's message of 2016-05-05 07:26:26 -0700: > On 04/05/2016 00:32, Hayes, Graham wrote: > > On 03/05/2016 17:03, John Dickinson wrote: > >> TC, > >> > >> In reference to > >> http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html > >> and Thierry's reply,

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

Just to chime in from an Octavia perspective as we were added to the subject. We have not had issues with DIB. There are things about the elements that could be improved, and we have been working on those over time. Currently we build the image with DIB for our scenario test runs and devstack.

Re: [openstack-dev] [tc] Swift api compat. Was: supporting Go

On Wed, 4 May 2016 21:52:49 + "Fox, Kevin M" wrote: > Swift is in a strange place where the api is implemented in a way to > favor one particular vendor backend implementation. Sorry, but I disagree with the above assessement. There is no one particular vendor like that,

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

Hello all, I’m an Operator that has worked with DIB here for the last few months to get some working images for our Private Cloud. The only major issue I could come up with at the summit was the way grub 0.97 is treated in the bootloader element. For Centos 6, I had to find an element that

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

In the scenario of Trove supporting both tools what do you expect the requirements for adding support for new databases will be? Are we expecting to have to support both tools for approval from the community? Cheers, Matt On May 5, 2016, at 10:43 AM, Mariam John

Re: [openstack-dev] [neutron][devstack] State of the refactor

On Thu, May 5, 2016 at 11:12 AM, Monty Taylor wrote: > On 05/05/2016 10:57 AM, Sean M. Collins wrote: >> >> During the Austin summit, there was a discussion in the QA meetings >> about the future of Neutron's support in DevStack. It's been an ongoing >> effort, and I'd like

Re: [openstack-dev] [tc] License for specs repo

On Thu, May 05, 2016 at 12:03:38PM -0400, Ben Swartzlander wrote: > It appears that many of the existing specs repos contain a confusing mixture > of Apache 2.0 licensed code and Creative Commons licensed docs. > > The official cookie-cutter for creating new specs repos [1] appears to also >

Re: [openstack-dev] [neutron][devstack] State of the refactor

> On May 5, 2016, at 8:57 AM, Sean M. Collins wrote: > > During the Austin summit, there was a discussion in the QA meetings > about the future of Neutron's support in DevStack. It's been an ongoing > effort, and I'd like to step back and give everyone a view of the Big >

Re: [openstack-dev] [neutron][devstack] State of the refactor

Yeah, seriously, thanks a million for this. You are making developers lives wa better! 2016-05-05 18:12 GMT+02:00 Monty Taylor : > On 05/05/2016 10:57 AM, Sean M. Collins wrote: > >> During the Austin summit, there was a discussion in the QA meetings >> about the future

Re: [openstack-dev] [neutron][devstack] State of the refactor

On 05/05/2016 10:57 AM, Sean M. Collins wrote: During the Austin summit, there was a discussion in the QA meetings about the future of Neutron's support in DevStack. It's been an ongoing effort, and I'd like to step back and give everyone a view of the Big Picture.

[openstack-dev] [neutron][devstack] State of the refactor

During the Austin summit, there was a discussion in the QA meetings about the future of Neutron's support in DevStack. It's been an ongoing effort, and I'd like to step back and give everyone a view of the Big Picture. https://etherpad.openstack.org/p/newton-qa-devstack-roadmap A year ago at the

[openstack-dev] [tc] License for specs repo

It appears that many of the existing specs repos contain a confusing mixture of Apache 2.0 licensed code and Creative Commons licensed docs. The official cookie-cutter for creating new specs repos [1] appears to also contain a mixture of the two licenses, although it's even more confusing

Re: [openstack-dev] [neutron][devstack] State of the refactor

Here is the patch I'm using to test the refactor against the Neutron CI jobs. https://review.openstack.org/#/c/278417/ There is still some work to be done, and it shows. -- Sean M. Collins __ OpenStack Development Mailing

Re: [openstack-dev] [nova][live migration] Request to merge initial storage pool patches

On 05/05/2016 10:50 AM, Matthew Booth wrote: TL;DR Core reviewers: please review the first 5 patches listed above. There will be cake. I only accept payment in cookies. -jay __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [Infra][Kuryr] - Sub repositories

On 05/05/2016 01:17 PM, Gal Sagie wrote: Hello all, Following the summit discussions and after summit checking we decided its better for us to try a sub repositories model for Kuryr (better for packaging and requirement/dependencies management). What do you mean with sub repositories? We

Re: [openstack-dev] [horizon] Angular form framework

This feels like a thing for AngularJS projects only, yes? What about projects like Fuel that use React? Michael On Wed, May 4, 2016 at 9:00 PM Tripp, Travis S wrote: > Hello everybody, > > I sent a message about this direclty to a couple of people for their quick >

[openstack-dev] [nova][live migration] Request to merge initial storage pool patches

I mentioned in the meeting last Tuesday that there are now 2 of us working on the persistent storage metadata patches: myself and Diana Clarke. I've also been talking to Paul Carlton today trying to work out how he can get moving with the subsequent libvirt storage pools work without a huge amount

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

From: Victoria Martínez de la Cruz To: "OpenStack Development Mailing List (not for usage questions)" Date: 05/05/2016 08:12 AM Subject:Re: [openstack-dev] [trove][sahara][infra][Octavia][manila]

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

We agreed during the summit that we were going to amend the spec to reflect latest discussions with regards to having DIB as a primary implementation and adding support for libguestfs in parallel. The spec blueprint is named "Trove image builder" and it's about building images and not about which

Re: [openstack-dev] [tc] supporting Go

On 04/05/2016 00:32, Hayes, Graham wrote: > On 03/05/2016 17:03, John Dickinson wrote: >> TC, >> >> In reference to >> http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html and >> Thierry's reply, I'm currently drafting a TC resolution to update >>

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

From: Victoria Martínez de la Cruz [mailto:victo...@vmartinezdelacruz.com] Sent: Thursday, May 05, 2016 9:00 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

> -Original Message- > From: Edward Leafe [mailto:e...@leafe.com] > Sent: 05 May 2016 04:32 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [nova][osc] Use of openstack client for admin > commands >

[openstack-dev] [Fuel] Meeting for May 5 Cancled

Due to the empty agenda, and many people on holiday this week, We will cancel today's meeting. Meetings will resume on May 12 with their regularly scheduled programming -- -- Andrew Woodward Mirantis Fuel Community Ambassador Ceph Community

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

> > The approach being proposed by Pete is something that is equally > applicable to DIB, I think. I believe that he makes a valid observation > and our current element design may in fact be bad. > > The invocation of DIB[1] is > > ${PATH_DISKIMAGEBUILDER}/bin/disk-image-create -a amd64

Re: [openstack-dev] [ironic] API docs now publishing from our tree

On Wed, May 04, 2016 at 05:22:05PM -0400, Ruby Loo wrote: > Sweet. Thanks Jim (and everyone else that made this happen). > > I do want to make sure there is one "source of truth" to the API > documentation. We are already generating REST API documentation at >

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

Hi all, A few things: - I agree that moving from DIB to libguestfs is a bold move and that we should try to avoid changing tools unless highly necessary. The downsides we found for DIB are detailed in this spec [0] and Ethan (in this same thread) also added valid points on the Sahara case. My

[openstack-dev] [tricircle] About the dynamic pod binding

Hi, all, For dynamic pod binding, I have some questions. 1. Do we need to store historical pod binding records in the pod binding table? Why? 2. How do we manage pod binding filters, store them in DB? 3. How is Tricircle aware of what type of resource wanted by tenants? For example, a tenant

Re: [openstack-dev] [Nova] Live Migration: Austin summit update

We've tested live migration of instances under load for following features: - Auto-converge - XBZRLE compression Tests were done against qemu 2.5. Instances had 2GB ram and stress tool was used to emulate load: $ stress -m 1 --vm-bytes 200M --vm-keep None of them could be called silver-bullet

Re: [openstack-dev] [kolla] better solution for the non-ini format configure file

TL;DR keep globals.yml to a minimum, customise configs via host_vars/group_vars It seems right now the "best" approach may be to tokenise variables as required. This is the approach we currently use in Oracle. There are two other approaches I can think of available to us: 1) The overwrite

[openstack-dev] [Fuel][Plugins][SDK] How to create a plugin-specific Launchpad project

Hi to everyone, as the follow-up to my previous email [1],I'm providing the URLs to assist with plugin-specific LP project setup: 1) guidelines on how to make it happen [2] 2) list of already existing LP projects [3] if you already have a project, please add it into the list to let everyone

[openstack-dev] [mistral] Blueprints based on the Austin Summit discussions

Hi, Here’s a list of new/revisited blueprints that reflect what we were able to discuss and decide at the summit: https://blueprints.launchpad.net/mistral/+spec/event-notification-trigger

[openstack-dev] [Cinder] gate-cinder-tox-db-functional job faulires and non-voting jobs

Hi team, It's pretty sad to me, but it seems that nobody cares about non-voting jobs :(. Cinder functional tests job is broken about 5 days [1] and I didn't see any comments on it in the reviews. As decided at summit, we're going to make this job voting. Stats from [1] proves that it's stable

[openstack-dev] [Infra][Kuryr] - Sub repositories

Hello all, Following the summit discussions and after summit checking we decided its better for us to try a sub repositories model for Kuryr (better for packaging and requirement/dependencies management). We would like to create additional sub repositories under Kuryr and i was wondering if the

Re: [openstack-dev] [QA][RFC] Skip this week meeting

Hi Masayuki, Sorry for late response. That is nice because we had much conversation at the summit. Next QA meeting is May 12th 1700UTC. I put the agenda for the next meeting on https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_May_12th_2016_.281700_UTC.29 It is nice to add more

Re: [openstack-dev] [heat][qa] devstack plugin

Hi dixiaoli Thanks for raising your hand for this work. I put your name on https://etherpad.openstack.org/p/newton-qa-newton-priorities Thanks --- 2016-05-05 2:13 GMT-07:00 dixiaoli <13051592...@163.com>: > Hi, Ken Omichi > > Thanks for point out this. > I would like to help to do the devstack

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

On 05/03/2016 11:24 PM, Joshua Harlow wrote: Howdy folks, So I meet up with *some* of the mistral folks during friday last week at the summit and I was wondering if we as a group can find a path to help that project move forward in their desire to have some kind of process than ack (vs the

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

On 05/04/2016 08:21 AM, Mehdi Abaakouk wrote: Hi, That said, I agree with Mehdi that *most* RPC calls throughout OpenStack, not being idempotent, should not use process-then-ack. That why I think we must not call this RPC. And the new API should be clear the expected idempotent of the

Re: [openstack-dev] [heat][qa] devstack plugin

Hi, Ken Omichi Thanks for point out this. I would like to help to do the devstack plugin in heat if there is no one is doing it now. Thanks dixiaoli At 2016-04-30 05:30:02, "Ken'ichi Ohmichi" wrote: >Hi Heat-team, > >Thanks for talking the topic of devstack

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

On 04/05/16 22:53, Jay Pipes wrote: On 05/04/2016 01:08 PM, Chris Dent wrote: The plans for generic resource pools[1] include a suite of new commands for creating and updating resource pools. In today's Nova API meeting[2] and afterwards in #openstack-nova[3] we discussed two issues: * Since

Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

Definitely a +1 from me. --Matt On Wed, May 4, 2016 at 9:18 PM, Kevin Carter wrote: > +1 for me too. > > > -- > > Kevin Carter > IRC: cloudnull > > > > From: Matthew Thode > Sent: Tuesday, May 3,

[openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

Hi to all Vitrage and Congress contributors, We had a good introduction meeting in Austin and we (Vitrage) think that we can have a good collaboration between the projects. Vitrage, as an Openstack Root Cause Analysis (RCA) Engine, builds a topology graph of all the entities in the system

[openstack-dev] [openstack-operators] [glance] Austin summit summary: Rolling upgrades

Hello everyone, Just wanted to send a brief summary of the discussions at the summit. This list is not holistic however, it covers the relevant aspects that various stakeholders need to be aware of. * The intent is that we want operators to be able to upgrade from one Glance release to the

  1   2   >