[openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup

Hi, I have a 4 node openstack setup (1 controller, 1 network, 2 compute nodes). I want to install kuryr in liberty version. I cannot find a package in ubuntu repo. -How do i install kuryr? - what are the components that need to be installed on the respective nodes? - Do i need to install magnum

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

Hi Armando Pls see below [UE] Thx Uri (“Oo-Ree”) C: 949-378-7568 From: Armando M. [mailto:arma...@gmail.com] Sent: Friday, May 20, 2016 9:08 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] support

Re: [openstack-dev] [ironic][nova][horizon] Serial console support for ironic instances

Hi! Hironori, Lucas, thank you for bringing this topic up! Yes, as Lucas says, our latest spec is https://review.openstack.org/#/c/319505 I and Tien, Hironori, Akira discussed and merged our idea. And new Nova spec is here: https://review.openstack.org/#/c/319507 As you guys know, Nova

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

Hi Tim Sorry for the delay due to travel... This note is very helpful! We are in agreement that the team including the individuals cited below are supportive. We also agree that SFC belongs in the networking-SFC project (with proper API adjustment) It seems networking-sfc still holds the

Re: [openstack-dev] [ironic][neutron] bonding?

Excerpts from Jim Rollenhagen's message of 2016-05-24 07:51:21 -0400: > Hi, > > There's rumors floating around about Neutron having a bonding model in > the near future. Are there any solid plans for that? > > For context, as part of the multitenant networking work, ironic has a > portgroup

[openstack-dev] [docs][install-guide] Install Guide Naming

Hi everyone, As part of the massive Install Guide changes the docs team are implementing in Newton, we need to come up with a name for what *was* the Install Guide. We need to emphasise the fact that it should be used for learning purposes only, not for installing a production cloud. So go

Re: [openstack-dev] [Mistral][Zaqar][Ceilometer][Searchlight] Triggering Mistral workflows from Zaqar messages

On 25/05/16 07:52, Zane Bitter wrote: > On 22/05/16 22:38, Lingxian Kong wrote: >> Hi, Zane, I think you must be interested in this: >> https://review.openstack.org/#/c/308664/ > > Oh! Yes that is very interesting. I'm glad that other people are > thinking about these kinds of problems also. > >

Re: [openstack-dev] [Swift3] improve multi-delete performance

Hello kirubakaran, Thanks for contributing Swift3, that sounds great. I wonder if you could push the diff as a patch to gerrit code review which is the review system for openstack and openstack related projects. The entry point for "how to contribute for openstack" is here,

Re: [openstack-dev] [aodh] Tempest gate not working

Hi Tony, That 'gate_hook.sh' is not good for tempest jobs. DEVSTACK_GATE_TEMPEST is set 0 in that script, and default one seems better (devstack-gate/devstack-vm-gate.sh) . https://review.openstack.org/#/c/320770/ BR, Ryota > -Original Message- > From: Tony Breeds

Re: [openstack-dev] [aodh] Tempest gate not working

On Tue, May 24, 2016 at 04:50:21PM +0200, Julien Danjou wrote: > Hi, > > So it turns out we tried (especially Ryota) to add Tempest support via > https://review.openstack.org/#/c/303921/ for Aodh's gate, but it does > not actually run Tempest. Your gate scripts didn't like tempest as an enabled

[openstack-dev] [Solum] Proposal to change weekly IRC meeting time

Hi team, In today's IRC meeting [1], we discussed about changing our weekly IRC meeting time from current time of 1700 UTC to 1400 UTC to allow our team members from Germany, India, and China to participate regularly. I have submitted a WIP patch [2] to make this change. Please provide your

Re: [openstack-dev] [magnum] Need helps to implement the full baremetals support

Hi, Hongbin, Spyros. I’m also interesting this work. I have workaround patch to support ironic. (but currently conflict with master. Is it helpful to upload it for initial step of the implementation? Thanks -yuanying 2016年5月25日(水) 6:52 Hongbin Lu : > Hi all, > > > > One

Re: [openstack-dev] [higgins] Continued discussion from the last team meeting

Hi, Hongbing, thanks a lot for the summary! The following is my thoughts on those two questions left: About container composition, it is a really useful and important feature for enduser. But based on my understanding, user can actually achieve the same goal by leveraging other high level

Re: [openstack-dev] [aodh] Tempest gate not working

Julien, Thank you for the heads up. I'll check aodh tempest tests, and also drop tempest full tests in ceilometer since the code for ceilometer was removed from tempest. BR, Ryota > -Original Message- > From: Julien Danjou [mailto:jul...@danjou.info] > Sent: Tuesday, May 24, 2016

Re: [openstack-dev] Fwd: keystone federation user story

On 05/24/2016 10:30 PM, Adam Young wrote: On 05/24/2016 01:55 PM, Alexander Makarov wrote: Colleagues, here is an actual use case for shadow users assignments, let's discuss possible solutions: all suggestions are appreciated. -- Forwarded message -- From: *Andrey

Re: [openstack-dev] Fwd: keystone federation user story

On 05/24/2016 01:55 PM, Alexander Makarov wrote: Colleagues, here is an actual use case for shadow users assignments, let's discuss possible solutions: all suggestions are appreciated. -- Forwarded message -- From: *Andrey Grebennikov*

Re: [openstack-dev] [aodh] Tempest gate not working

Hi, Thanks for this mail, I also noticed that yesterday, and I am trying to fix it by https://review.openstack.org/#/c/320378/ cheers, Liusheng 在 2016/5/24 22:50, Julien Danjou 写道: Hi, So it turns out we tried (especially Ryota) to add Tempest support via

Re: [openstack-dev] [higgins] Continued discussion from the last team meeting

On Tue, May 24, 2016 at 08:55:28PM +, Hongbin Lu wrote: > Hi all, > > At the last team meeting, we tried to define the scope of the Higgins > project. In general, we agreed to focus on the following features as an > initial start: > > * Build a container abstraction and use docker

Re: [openstack-dev] [PTLs][all][mentoring] Mentors needed in specific technical areas

>> On 12:54 May 24, Augustina Ragwitz wrote: >> Hi Emily, >> >> I'm the Nova Mentoring Czar and we have a Wiki page with a list of >> projects that would be good for new contributors: >> https://wiki.openstack.org/wiki/Nova/Mentoring >> >> For Nova, I'd encourage potential contributors to get

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

Ryan, Thanks for getting back to me and pointing me in a more OVS like direction. What you say makes sense, let me hack something together. I have been a little distracted getting some use cases together. The other area is how to better map the flow-classifier I have been thinking about it a

Re: [openstack-dev] [craton] meeting notes

I missed that bi-weekly all four meeting slot are taken at 14:30 UTC Mondays. I am going to move the meeting to 15:00 UTC. Speak up if that doesn't work for you. On Mon, May 23, 2016 at 11:45 AM, sean roberts wrote: > Hello project team members. We have one week until

Re: [openstack-dev] [cinder] A friendly reminder about reviews

Cinder is definitely lacking reviewing force. I remember 2 years ago comparing with today and I can tell that patches are taking a lot longer to get reviewed. This link is also very useful to triage incoming patches: https://review.openstack.org/#/dashboard/?foreach=project:^openstack/.*cinder.*

[openstack-dev] [new][oslo] taskflow 2.0.0 release (newton)

We are delighted to announce the release of: taskflow 2.0.0: Taskflow structured state management library. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/taskflow With package available at:

[openstack-dev] [new][oslo] oslo.vmware 2.7.0 release (newton)

We are excited to announce the release of: oslo.vmware 2.7.0: Oslo VMware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.vmware With package available at: https://pypi.python.org/pypi/oslo.vmware

[openstack-dev] [new][oslo] tooz 1.37.0 release (newton)

We are pleased to announce the release of: tooz 1.37.0: Coordination library for distributed systems. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/tooz With package available at: https://pypi.python.org/pypi/tooz

[openstack-dev] [new][oslo] stevedore 1.14.0 release (newton)

We are pleased to announce the release of: stevedore 1.14.0: Manage dynamic plugins for Python applications This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/stevedore With package available at:

[openstack-dev] [new][oslo] oslo.log 3.8.0 release (newton)

We are gleeful to announce the release of: oslo.log 3.8.0: oslo.log library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.log With package available at: https://pypi.python.org/pypi/oslo.log Please report

[openstack-dev] [new][oslo] oslosphinx 4.4.0 release (newton)

We are eager to announce the release of: oslosphinx 4.4.0: OpenStack Sphinx Extensions and Theme This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslosphinx With package available at:

[openstack-dev] [new][oslo] oslo.utils 3.11.0 release (newton)

We are happy to announce the release of: oslo.utils 3.11.0: Oslo Utility library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.utils With package available at: https://pypi.python.org/pypi/oslo.utils Please

[openstack-dev] [new][oslo] oslo.serialization 2.7.0 release (newton)

We are amped to announce the release of: oslo.serialization 2.7.0: Oslo Serialization library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.serialization With package available at:

[openstack-dev] [new][oslo] oslo.service 1.11.0 release (newton)

We are overjoyed to announce the release of: oslo.service 1.11.0: oslo.service library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.service With package available at:

Re: [openstack-dev] [magnum][kuryr] Nested containers networking

Hi Gal, Ton Ngo is the Magnum liaison for Kuryr [1]. Ton will sync up Kuryr liaison in weekly basis and provide status update at the Magnum team meeting. Please feel free to let Ton or me know if anything we can help. I am looking forward to collaborating with Kuryr team to move the

[openstack-dev] [new][oslo] oslo.policy 1.8.0 release (newton)

We are happy to announce the release of: oslo.policy 1.8.0: Oslo Policy library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.policy With package available at: https://pypi.python.org/pypi/oslo.policy Please

[openstack-dev] [new][oslo] oslo.config 3.10.0 release (newton)

We are glad to announce the release of: oslo.config 3.10.0: Oslo Configuration API This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.config With package available at: https://pypi.python.org/pypi/oslo.config

[openstack-dev] [new][oslo] oslo.reports 1.9.0 release (newton)

We are psyched to announce the release of: oslo.reports 1.9.0: oslo.reports library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.reports With package available at: https://pypi.python.org/pypi/oslo.reports

[openstack-dev] [new][oslo] oslo.middleware 3.11.0 release (newton)

We are glad to announce the release of: oslo.middleware 3.11.0: Oslo Middleware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.middleware With package available at:

[openstack-dev] [new][oslo] oslo.concurrency 3.9.0 release (newton)

We are pumped to announce the release of: oslo.concurrency 3.9.0: Oslo Concurrency library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.concurrency With package available at:

[openstack-dev] [new][oslo] oslo.cache 1.8.0 release (newton)

We are gleeful to announce the release of: oslo.cache 1.8.0: Cache storage for Openstack projects. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.cache With package available at:

[openstack-dev] [new][oslo] oslo.context 2.4.0 release (newton)

We are stoked to announce the release of: oslo.context 2.4.0: Oslo Context library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.context With package available at: https://pypi.python.org/pypi/oslo.context

[openstack-dev] [magnum] Need helps to implement the full baremetals support

Hi all, One of the most important feature that Magnum team wants to deliver in Newton is the full baremetal support. There is a blueprint [1] created for that and the blueprint was marked as "essential" (that is the highest priority). Spyros is the owner of the blueprint and he is looking for

Re: [openstack-dev] [PTLs][all][mentoring] Mentors needed in specific technical areas

On 12:54 May 24, Augustina Ragwitz wrote: > Hi Emily, > > I'm the Nova Mentoring Czar and we have a Wiki page with a list of > projects that would be good for new contributors: > https://wiki.openstack.org/wiki/Nova/Mentoring > > For Nova, I'd encourage potential contributors to get involved

Re: [openstack-dev] [nova][neutron][cloud-init] Questions around 'network_data.json'

On Tue, May 24, 2016 at 4:20 PM, Joshua Harlow wrote: > Hi there all, > > I am working through code/refactoring in cloud-init to enable translation > of the network_data.json file[1] provided by openstack (via nova via > neutron?) into the equivalent sysconfig files

Re: [openstack-dev] [nova][neutron][cloud-init] Questions around 'network_data.json'

I think there is an implementation error. The spec mentions that link type can be "vif", "phy" or (future) "bond". Nova passes the "raw" Neutron VIF type instead. IMO, "bridge" should be "vif" as per spec. -- Mathieu On Tue, May 24, 2016 at 5:20 PM, Joshua Harlow wrote: >

Re: [openstack-dev] [nova] Xvisor support

On Tue, May 24, 2016 at 11:42 PM, Muneeb Ahmad wrote: > If not, can I add it's support? any ideas how can I do that? > > On Sat, May 21, 2016 at 10:23 PM, Muneeb Ahmad > wrote: > >> Hey guys, >> >> Does OpenStack support Xvisor? >> > So,

[openstack-dev] [nova][neutron][cloud-init] Questions around 'network_data.json'

Hi there all, I am working through code/refactoring in cloud-init to enable translation of the network_data.json file[1] provided by openstack (via nova via neutron?) into the equivalent sysconfig files (ubuntu files should already *mostly* work and systemd files are underway as well). Code

Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

Thanks guys, it's a privilege to be part of team. :) 2016-05-24 17:02 GMT-03:00 Steven Dake (stdake) : > From: Steven Dake > Reply-To: "openstack-dev@lists.openstack.org" < > openstack-dev@lists.openstack.org> > Date: Tuesday, May 17, 2016 at 12:00 PM > To:

[openstack-dev] [higgins] Continued discussion from the last team meeting

Hi all, At the last team meeting, we tried to define the scope of the Higgins project. In general, we agreed to focus on the following features as an initial start: * Build a container abstraction and use docker as the first implementation. * Focus on basic container

Re: [openstack-dev] update congress

Hi Yue, That version of Congress definitely doesn't have the Push driver. The Push driver code was implemented only in the latest release (Mitaka). Here are the upgrade instructions. They SHOULD work, but let us know if you run into problems, both so we can help you and so we can correct the

[openstack-dev] [vitrage] Vitrage meeting on May 25 - SKIPPED

Hi, Vitrage weekly meeting on May 25 will be skipped, as many Vitrage developers won't be able to attend. We will meet next week as usual. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

From: Steven Dake > Reply-To: "openstack-dev@lists.openstack.org" > Date: Tuesday, May 17, 2016 at 12:00 PM To:

Re: [openstack-dev] [all][oslo_config] Improving Config Option Help Texts

On 24 May 2016 at 19:03, Ian Cordasco wrote: > -Original Message- > From: Erno Kuvaja > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: May 24, 2016 at 06:06:14 > To: OpenStack

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

> On May 24, 2016, at 12:09 PM, Mike Perez wrote: > > On 12:24 May 24, Thierry Carrez wrote: >> Morgan Fainberg wrote: >>> [...] If we are accepting golang, I want it to be clearly >>> documented that the expectation is it is used exclusively where there is >>> a

Re: [openstack-dev] [PTLs][all][mentoring] Mentors needed in specific technical areas

Hi Emily, I'm the Nova Mentoring Czar and we have a Wiki page with a list of projects that would be good for new contributors: https://wiki.openstack.org/wiki/Nova/Mentoring For Nova, I'd encourage potential contributors to get involved with a specific project so that mentoring can happen

Re: [openstack-dev] [ironic][neutron] bonding?

The only thing I am remotely aware of that is relevant is: https://bugs.launchpad.net/bugs/1558626 But that's really just in one agent. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Mistral][Zaqar][Ceilometer][Searchlight] Triggering Mistral workflows from Zaqar messages

On 22/05/16 22:38, Lingxian Kong wrote: Hi, Zane, I think you must be interested in this: https://review.openstack.org/#/c/308664/ Oh! Yes that is very interesting. I'm glad that other people are thinking about these kinds of problems also. My blueprint has a different focus, in that it's

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Frankly, this is one of the major negatives we've felt from the Big Tent idea... OpenStack use to be more of a product then it is now. When there were common problems to be solved, there was pressure applied to solve them in a way everyone (OpenStack Project, OpenStack Users, and Openstack

Re: [openstack-dev] [all][oslo_config] Improving Config Option Help Texts

+1 to what Ian said. We had an Ops session at the Austin summit on this and we didn't hear any concerns about the clutter from what I can recall. Some notes from that session are here [0]. May be the clutter is not a problem after all? At least, not yet. If it does become a problem down the

Re: [openstack-dev] [ironic][neutron] bonding?

On 24 May 2016 at 04:51, Jim Rollenhagen wrote: > Hi, > > There's rumors floating around about Neutron having a bonding model in > the near future. Are there any solid plans for that? > Who spreads these rumors :)? To the best of my knowledge I have not seen any RFE

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

-Original Message- From: Jay Pipes Reply: OpenStack Development Mailing List (not for usage questions) Date: May 24, 2016 at 11:35:42 To: openstack-dev@lists.openstack.org Subject:  Re:

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On 12:24 May 24, Thierry Carrez wrote: > Morgan Fainberg wrote: > >[...] If we are accepting golang, I want it to be clearly > >documented that the expectation is it is used exclusively where there is > >a demonstrable case (such as with swift) and not a carte blanche to use > >it

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Ok, probably should be chopped out of the oslo lib list then ;) I'll do that, since it seems to be really not the right name for what it is :) Ian Cordasco wrote: -Original Message- From: Joshua Harlow Reply: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [oslo] Log spool in the context

Excerpts from Sean Dague's message of 2016-05-24 14:16:13 -0400: > On 05/24/2016 01:18 PM, Doug Hellmann wrote: > > Excerpts from Alexis Lee's message of 2016-05-24 09:34:36 +0100: > >> Hi, > >> > >> I have a spec: https://review.openstack.org/227766 > >> and implementation:

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

-Original Message- From: Joshua Harlow Reply: OpenStack Development Mailing List (not for usage questions) Date: May 23, 2016 at 15:23:32 To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [keystone] New Core Reviewer (sent on behalf of Steve Martinelli)

I want to welcome Rodrigo Duarte (rodrigods) to the keystone core team. Rodrigo has been a consistent contributor to keystone and has been instrumental in the federation implementations. Over the last cycle he has shown an understanding of the code base and contributed quality reviews. I am super

Re: [openstack-dev] [ironic] usage of ironic-lib

Thanks for the feedback everyone. Lucas has submitted a patch to ironic-lib¹s README to clarify this: https://review.openstack.org/#/c/319251/. --ruby On 2016-05-20, 8:46 AM, "Jim Rollenhagen" wrote: >On Thu, May 19, 2016 at 01:21:35PM -0700, Devananda van der Veen

Re: [openstack-dev] [oslo] Log spool in the context

On 05/24/2016 01:18 PM, Doug Hellmann wrote: > Excerpts from Alexis Lee's message of 2016-05-24 09:34:36 +0100: >> Hi, >> >> I have a spec: https://review.openstack.org/227766 >> and implementation: https://review.openstack.org/316162 >> for adding a spooling logger to oslo.log. Neither is merged

[openstack-dev] [ironic] weekly sub team status report

Hi, We are rambunctious to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 16 May 2016) - Ironic: 192 bugs (+2) + 178 wishlist items (+1). 0 new, 138 in progress

Re: [openstack-dev] [all][oslo_config] Improving Config Option Help Texts

-Original Message- From: Erno Kuvaja Reply: OpenStack Development Mailing List (not for usage questions) Date: May 24, 2016 at 06:06:14 To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

The team working on live migration testing started with an experimental job on Ubuntu 16.04 to try to be using the latest and greatest libvirt + qemu under the assumption that a set of issues we were seeing are solved. The short answer is, it doesn't look like this is going to work. We run tests

[openstack-dev] Fwd: keystone federation user story

Colleagues, here is an actual use case for shadow users assignments, let's discuss possible solutions: all suggestions are appreciated. -- Forwarded message -- From: Andrey Grebennikov Date: Tue, May 24, 2016 at 9:43 AM Subject: keystone federation

Re: [openstack-dev] Plans to converge on one ldap client?

On Tue, May 24, 2016 at 1:23 PM, Morgan Fainberg wrote: > > > On Tue, May 24, 2016 at 8:55 AM, Corey Bryant > wrote: > >> >> >> On Tue, May 24, 2016 at 11:11 AM, Morgan Fainberg < >> morgan.fainb...@gmail.com> wrote: >> >>> >>> >>> On Tue,

[openstack-dev] Fw: [glance] [defcore] [interop] Proposal for a virtual sync dedicated to Import Refactor May 26th

+1 - Catheine Diep - Forwarded by Catherine Cuong Diep/San Jose/IBM on 05/24/2016 10:31 AM - From: Brian Rosmaita To: "OpenStack Development Mailing List (not for usage questions)" Date: 05/24/2016

Re: [openstack-dev] Plans to converge on one ldap client?

On Tue, May 24, 2016 at 8:55 AM, Corey Bryant wrote: > > > On Tue, May 24, 2016 at 11:11 AM, Morgan Fainberg < > morgan.fainb...@gmail.com> wrote: > >> >> >> On Tue, May 24, 2016 at 5:53 AM, Corey Bryant > > wrote: >> >>> Hi All, >>> >>>

Re: [openstack-dev] [glance] [defcore] [interop] Proposal for a virtual sync dedicated to Import Refactor May 26th

+1 On 5/24/16, 11:11 AM, "Chris Hoge" wrote: >+1 > >> On May 23, 2016, at 8:25 PM, Mike Perez wrote: >> >>> On 18:00 May 20, Nikhil Komawar wrote: >>> Hello all, >>> >>> >>> I want to propose having a dedicated virtual sync next week Thursday >>>May

[openstack-dev] Summit evolution online town halls

Hi everyone, You might have seen the FAQ we posted last week about the continuing work on evolving the format and structure of the Summits: http://www.openstack.org/blog/2016/05/faq-evolving-the-openstack-design-summit/ I wanted to send a reminder note out to highlight that Thierry and I

Re: [openstack-dev] [oslo] Log spool in the context

Excerpts from Alexis Lee's message of 2016-05-24 09:34:36 +0100: > Hi, > > I have a spec: https://review.openstack.org/227766 > and implementation: https://review.openstack.org/316162 > for adding a spooling logger to oslo.log. Neither is merged yet, reviews > welcome. > > Looking at how I'd

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

Excerpts from Markus Zoeller's message of 2016-05-24 11:00:35 +0200: > On 24.05.2016 09:34, Duncan Thomas wrote: > > Cinder bugs list was far more manageable once this had been done. > > > > It is worth sharing the tool for this? I realise it's fairly trivial to > > write one, but some

Re: [openstack-dev] [nova] [infra] resolving issues with Intel NFV CI

The issue is now resolved. Apparently the job wasn't registered with gearman server as there weren't any slaves available in Jenkins to run it at the time of zuul restart (as some old nodepool nodes were left over and no new VMs were spawned). From: Znoinski, Waldemar

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

On 05/24/2016 11:54 AM, Dan Smith wrote: >> I like the idea of checking the md5 matches before each boot, as it >> mirrors the check we do after downloading from glance. Its possible >> thats very unlikely to spot anything that shouldn't already be worried >> about by something else. It may just

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On 05/24/2016 06:19 AM, Thierry Carrez wrote: Chris Dent wrote: [...] I don't really know. I'm firmly in the camp that OpenStack needs to be smaller and more tightly focused if a unitary thing called OpenStack expects to be any good. So I'm curious about and interested in strategies for

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

On 05/24/2016 11:17 AM, Ihar Hrachyshka wrote: On 17 May 2016, at 13:07, Ihar Hrachyshka wrote: Hi stable-maint-core and all, I would like to propose Brian for neutron specific stable team. His stats for neutron stable branches are (last 120 days): mitaka: 19 reviews;

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

OpenStack is more then the sum of its various pieces. Often features need to cross more then one project. Cross project work is already extremely hard without having to change languages between. Language change should be done very carefully and deliberately. Thanks, Kevin

[openstack-dev] [kolla][security] Finishing the job on threat analysis for Kolla

Rob and Doug, At Summit we had 4 hours of highly productive work producing a list of "things" that can be "threatened". We have about 4 or 5 common patterns where we follow the principle of least privilege. On Friday of Summit we produced a list of all the things (in this case deployed

Re: [openstack-dev] [ironic][nova][horizon] Serial console support for ironic instances

Hi, > I'm working with Tien who is a submitter of one[1] of console specs. > I joined the console session in Austin. > > In the session, we got the following consensus. > - focus on serial console in Newton > - use nova-serial proxy as is > > We also got some requirements[2] for this feature in

Re: [openstack-dev] Plans to converge on one ldap client?

On Tue, May 24, 2016 at 11:11 AM, Morgan Fainberg wrote: > > > On Tue, May 24, 2016 at 5:53 AM, Corey Bryant > wrote: > >> Hi All, >> >> Are there any plans to converge on one ldap client across projects? Some >> projects have moved to

Re: [openstack-dev] [puppet] weekly meeting #82

On Mon, May 23, 2016 at 1:24 PM, Emilien Macchi <emil...@redhat.com> wrote: > 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-20

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

> I like the idea of checking the md5 matches before each boot, as it > mirrors the check we do after downloading from glance. Its possible > thats very unlikely to spot anything that shouldn't already be worried > about by something else. It may just be my love of symmetry that makes > me like

Re: [openstack-dev] [fuel] release version numbers: let's use semvers

The only thing I would like to mention here is that scripts for making automatic releases on PyPi using OpenStack Infra won’t work, if the version is not formatted according to semver. - romcheg > 24 трав. 2016 р. о 14:34 Igor Kalnitsky написав(ла): > > Hey Zigo, >

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On 05/24/2016 11:13 AM, Dean Troyer wrote: > On Tue, May 24, 2016 at 8:20 AM, Flavio Percoco > wrote: > > So, just to make sure I'm making myself clear, I believe we should > go with > option #2 in Thierry's comment from May 23 11:3 on

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

The incorporation of tooz and Neutron is being discussed as part of https://bugs.launchpad.net/neutron/+bug/1552680 as an RFE for Newton. Hopefully I'll have some news to break in on this matter in the upcoming days (and if I do I'll update on the launchpad to eliminate duplicity). On Tue, May

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

> On 17 May 2016, at 13:07, Ihar Hrachyshka wrote: > > Hi stable-maint-core and all, > > I would like to propose Brian for neutron specific stable team. > > His stats for neutron stable branches are (last 120 days): > > mitaka: 19 reviews; liberty: 68 reviews (3rd place

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On Tue, May 24, 2016 at 8:20 AM, Flavio Percoco wrote: > > So, just to make sure I'm making myself clear, I believe we should go with > option #2 in Thierry's comment from May 23 11:3 on this[0] review. While > I'm not > entirely opposed to #1 I think #2 is better for us at

Re: [openstack-dev] Plans to converge on one ldap client?

On Tue, May 24, 2016 at 5:53 AM, Corey Bryant wrote: > Hi All, > > Are there any plans to converge on one ldap client across projects? Some > projects have moved to ldap3 and others are using pyldap (both are in > global requirements). > > The issue we're running

Re: [openstack-dev] [glance] [defcore] [interop] Proposal for a virtual sync dedicated to Import Refactor May 26th

+1 > On May 23, 2016, at 8:25 PM, Mike Perez wrote: > >> On 18:00 May 20, Nikhil Komawar wrote: >> Hello all, >> >> >> I want to propose having a dedicated virtual sync next week Thursday May >> 26th at 1500UTC for one hour on the Import Refactor work [1] ongoing in >>

Re: [openstack-dev] [openstack-operators][cinder] max_concurrent_builds in Cinder

On 05/24/2016 04:38 PM, Gorka Eguileor wrote: > On 23/05, Ivan Kolodyazhny wrote: >> Hi developers and operators, >> I would like to get any feedback from you about my idea before I'll start >> work on spec. >> >> In Nova, we've got max_concurrent_builds option [1] to set 'Maximum number >> of

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

On Tue, May 24, 2016 at 1:15 PM, Fichter, Dane G. wrote: > Hi John and Matt, > > I actually have a spec and patch up for review addressing some of what > you’re referring to below. > > https://review.openstack.org/#/c/314222/ > https://review.openstack.org/#/c/312210/ >

Re: [openstack-dev] [nova] Stable disk device instance rescue reviews for libvirt and possible implementation by other virt drivers

Hi Lee, I'll try to get to these reviews later this afternoon. Thanks for your patience. Best, -jay On 05/24/2016 08:53 AM, Lee Yarwood wrote: Hello all, https://review.openstack.org/#/q/topic:bp/virt-rescue-stable-disk-devices I've been aimlessly pushing my patches around for this spec

[openstack-dev] [aodh] Tempest gate not working

Hi, So it turns out we tried (especially Ryota) to add Tempest support via https://review.openstack.org/#/c/303921/ for Aodh's gate, but it does not actually run Tempest. Otherwise, we would have notice something wrong in https://review.openstack.org/#/c/318052/. As EmilienM noticed in Puppet

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On 23/05/16 21:57 +0100, Chris Dent wrote: [snip] So, yet another way to frame the original question (in a loaded way) may be: Are we trying to come up with a way of defining the community that lets us carry on doing what we've been doing, haphazardly, or are we trying to get the process of

  1   2   >