Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

Steve, this was exactly the point I wanted to make and the reason I chose the verbiage of "reasonably accessible" since I believe that this would classify as such. However, as Thierry pointed out in his response to the review that wasn't his primary focus. Rather, he didn't want a project to

Re: [openstack-dev] [charms] Re-licensing OpenStack charms under Apache 2.0

Hi James, No problem on my side. This is a welcome change! Regards, Gabriel Samfira Cloudbase Solutions SRL On Mi, 2016-06-08 at 10:20 +, James Page wrote: > Hi > > We're currently blocked on becoming an OpenStack project under the > big-tent by the licensing of the 26 OpenStack charms

Re: [openstack-dev] [nova][cinder] Integration testing for Nova API os-assisted-volume-snapshots

On 6/17/2016 2:44 AM, Silvan Kaiser wrote: I'd be happy to help, too. Please drop e.g. a bug link in this thread we can use to follow up on things, that would be great. Best Silvan 2016-06-15 22:44 GMT+02:00 Sean McGinnis >: On Wed, Jun

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On 15 June 2016 at 02:37, Sean Dague wrote: > On 06/14/2016 07:28 PM, Monty Taylor wrote: >> >> On 06/14/2016 05:42 PM, Doug Hellmann wrote: > > >> >> I think this is the most important thing to me as it relates to this. >> I'm obviously a huge proponent of clouds behaving more

Re: [openstack-dev] [UX] [TripleO] TripleO UI Initial Wireframes

On Thu, Jun 16, 2016 at 11:27 AM, Dan Prince wrote: > I left some comments on the wireframes themselves. One general concept > I would like to see capture is to make sure that things across the UI > and CLI have parity. > > Specifically things like if I register nodes on the

[openstack-dev] [fuel] Containerized OpenStack on Kubernetes experimental project proposal

Hi, I'd like to share proposal on running the experimental project under the Fuel umbrella for running OpenStack in containers on top of Kubernetes, codename "Fuel CCP". Here is a specification in Fuel: https://review.openstack.org/331139 CCP is the initiative to package OpenStack services in

Re: [openstack-dev] [murano] Nominating Alexander Tivelkov and Zhu Rong for murano cores

+1, agree with this proposition On Thu, Jun 16, 2016 at 3:08 PM, Victor Ryzhenkin wrote: > It’s great to see this happen! > +1 for adding both! Well deserved, folks! > > Also agreed to remove Steve from murano-core. > > -- > Victor Ryzhenkin > Quality Assurance Engineer

Re: [openstack-dev] [OpenStack-Infra] Upcoming changes now that Jenkins has retired

We can update those without any trouble. We just need to also update the tests that check the usernames. You should be able to make all of the changes (as per your first patchset) and then find where the tests also need changing. Happy to help you on the review if you need more guidance. To

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

On 16 June 2016 at 09:58, Thierry Carrez wrote: > Project team requirements are just guidelines, which are interpreted by > humans. In the end, the TC members vote and use human judgment rather than > blind 'rules'. I just want (1) to state that a level playing field is an

Re: [openstack-dev] [nova] Using image metadata to sanity check supplied authentication data at nova 'create' or 'recreate' time?

On 7 June 2016 at 17:41, Jim Rollenhagen wrote: > On Tue, Jun 07, 2016 at 03:10:24PM +0100, Daniel P. Berrange wrote: >> On Tue, Jun 07, 2016 at 09:37:25AM -0400, Jim Rollenhagen wrote: >> > Right, so that's a third case. How I'd see this working is maybe an >> > image

Re: [openstack-dev] [tc] Re: [fuel] [kolla] Containerized OpenStack on Kubernetes experimental project proposal

Ah. I didn't make it that far through the spec. Thanks for pointing that out. It seems premature to me though to start proposing a new project when discussion of reusing of an existing project has just started. Only since yesterday as far as I can gather. Yes, if there ends up being a

Re: [openstack-dev] [tc] Re: [fuel] [kolla] Containerized OpenStack on Kubernetes experimental project proposal

On 2016-06-17 18:04:25 + (+), Steven Dake (stdake) wrote: [...] > The technical committee has set precedent that competition is > acceptable in the "outer ring" of services (i.e. The TC doesn't > want Big Tent projects competing with nova for example but > deployment is fair game). I agree

Re: [openstack-dev] [networking-ovn] provider networks

Provider networks should operate the same whether using the conventional L3 agent (q-l3) or native L3 support in OVN. Provider networks only operate at layer-2 and rely on a physical router on the same layer-2 segment to provide layer-3 services such as a gateway. On Fri, Jun 17, 2016 at 12:37

Re: [openstack-dev] [ironic] Proposing two new cores

On Thu, Jun 16, 2016 at 11:12 AM, Jim Rollenhagen wrote: > Hi all, > > I'd like to propose Jay Faulkner (JayF) and Sam Betts (sambetts) for the > ironic-core team. > > +2 to both. :) -Julia __

Re: [openstack-dev] [Neutron][IPAM] Anyone using builtin pluggable IPAM driver?

Doesn't look like anyone sets it. I don't see any references to it in the provisioning tools (puppet, ansible, salt). http://codesearch.openstack.org/?q=ipam_driver=nope== So probably only very advanced users have done anything with it since it would require manual configuration? -- Sean M.

[openstack-dev] [Ironic] Grenade non-voting test results

TL;DR: In my opinion Grenade job is performing reliably. Using the table at: http://ci-watch.tintri.com/project?project=ironic=7+days Note: Unable to extract the data out of the web page to do more thorough data evaluation. The Grenade job appears to be performing successfully. On Thursday

[openstack-dev] [tc] Re: [fuel] [kolla] Containerized OpenStack on Kubernetes experimental project proposal

Kevin, Why have one snowflake when you can have two? Snarky comments aside :) Sergey did answer that question in the specification he linked (rest quoted): " Alternatives This spec is actually describes an alternative experimental approach for OpenStack deployment,

Re: [openstack-dev] [networking-ovn] provider networks

I think for provider networks we have to disable OVN_L3. Because devstack setup for neutron is creating a default router in the standard setup and conflicts with external router. On Fri, Jun 17, 2016 at 10:57 AM, Ryan Moats wrote: > Murali R wrote on

Re: [openstack-dev] [networking-ovn] provider networks

Murali R wrote on 06/17/2016 12:33:09 PM: > From: Murali R > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff , discuss > Date: 06/17/2016 12:33 PM > Subject: Re: [ovs-discuss] [ovn] provider networks > > > Your

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

Hi Ricardo, Thanks for sharing it. Result seems great and we will surely try to fix the issue. Cheers! Regards, Madhuri -Original Message- From: Ricardo Rocha [mailto:rocha.po...@gmail.com] Sent: Friday, June 17, 2016 8:44 PM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [tc] Re: [fuel] [kolla] Containerized OpenStack on Kubernetes experimental project proposal

On 6/17/16, 11:38 AM, "Jeremy Stanley" wrote: >On 2016-06-17 18:04:25 + (+), Steven Dake (stdake) wrote: >[...] >> The technical committee has set precedent that competition is >> acceptable in the "outer ring" of services (i.e. The TC doesn't >> want Big Tent

Re: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team

+1. Kanagaraj will be a great addition to the team. Bob On 6/16/2016 1:45 PM, Karthik Natarajan wrote: +1. Thanks Kanagaraj for making such a great impact during the Newton cycle. *From:*Sripriya Seetharam [mailto:ssee...@brocade.com] *Sent:* Thursday, June 16, 2016 10:35 AM *To:*

Re: [openstack-dev] [Ironic] Grenade non-voting test results

+1 lets get it voting. Feel free to add me as a reviewer to the project-config patch to make the change if you want me to vote officially :). Thanks, Jay From: Villalovos, John L Sent: Friday, June 17, 2016 10:49:32 AM To:

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

John McDowall wrote on 06/17/2016 04:07:38 PM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: discuss , Na Zhu , > "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On Fri, Jun 17, 2016 at 04:26:49PM -0700, Mike Perez wrote: > On 15:12 Jun 14, Matthew Treinish wrote: > > On Tue, Jun 14, 2016 at 02:41:10PM -0400, Doug Hellmann wrote: > > > Excerpts from Matthew Treinish's message of 2016-06-14 14:21:27 -0400: > > > > On Tue, Jun 14, 2016 at 10:57:05AM -0700,

[openstack-dev] [kolla] our 3 voting processes in detail

Hey core reviewers, I was speaking with one of the core reviewers of Kolla today who said "only you can nominate people for core reviewer". By you, he meant me :) This is absolutely not true and I'd like to set the record straight on our three voting processes we have developed over the last

Re: [openstack-dev] [kolla] our 3 voting processes in detail

Thanks Steve, Very useful. Would be great if for future reference we would only need to pint people to an URL on the Wiki for instance... what do you think? regards, Gerard __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [kolla] our 3 voting processes in detail

On Sat, Jun 18, 2016 at 9:49 AM, Assaf Muller wrote: > I would recommend in-tree policies .rsts instead of Wiki entries. > There is a higher cost to make changes, but they have to go through > the review process, and the content will survive as long as the .git > repo does.

Re: [openstack-dev] [kolla] our 3 voting processes in detail

Thanks for the suggestion. I think it merits further work to write our policies down in git. I wanted to get this out a little more quickly since these are our foundational policies and there is some confusion among the cores about them - even though we have been using them for the better part

[openstack-dev] [neutron] No Neutron Common Flow Classifier meeting on 6/21 UTC 1700

Hi everyone, Since we have had the meeting discussion on Common Flow classifier on 6/14/2016, we will not have another meeting on 6/21/2016. We will have our next meeting on 7/5/2016 and then have one every odd week. Here is the link to the feature wiki page.

Re: [openstack-dev] [kolla] our 3 voting processes in detail

On Fri, Jun 17, 2016 at 9:41 PM, Gerard Braad wrote: > Thanks Steve, > > > Very useful. Would be great if for future reference we would only need > to pint people to an URL on the Wiki for instance... what do you > think? I would recommend in-tree policies .rsts instead of Wiki

[openstack-dev] OpenStack Developer Mailing List Digest May 14 to June 17

HTML render: http://www.openstack.org/blog/2016/06/openstack-developer-mailing-list-digest-20160617/ SuccessBot Says === * Qiming: Senlin has completed API migration from WADL. * Mugsie: Kiall Fixed the gate - development can now continue!!! * notmyname: exactly 6 years ago today

[openstack-dev] [all] Proposal: Architecture Working Group

ar·chi·tec·ture ˈärkəˌtek(t)SHər/ noun noun: architecture 1. the art or practice of designing and constructing buildings. synonyms:building design, building style, planning, building, construction; formalarchitectonics "modern architecture" the style in which a

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

Le 17/06/2016 18:11, Dean Troyer a écrit : On Fri, Jun 17, 2016 at 10:23 AM, Sylvain Bauza > wrote: In the review, you explain why you don't trust Routes and I respect that. That said, are those issues logged as real problems for our

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Ryan, See inline Regards John From: Ryan Moats > Date: Friday, June 17, 2016 at 7:26 AM To: John McDowall > Cc: discuss >,

Re: [openstack-dev] [tacker][nfv][midcycle] Straw poll on F2F vs Virtual midcycle meetup

Thanks for all those who responded. The poll is closed now. It was a unanimous pick for a Virtual midcycle meetup. I'll send out another doodle poll to pick date & time in late July for the meetup. - Sridhar On Tue, Jun 7, 2016 at 5:15 PM, Sridhar Ramaswamy wrote: > Tackers,

Re: [openstack-dev] [nova] Question about redundant API samples tests for microversions

On Fri, Jun 17, 2016, at 04:16 PM, Matt Riedemann wrote: > I was reviewing this today: > > https://review.openstack.org/#/c/326940/ > > And I said to myself, 'self, do we really need to subclass the API > samples functional tests for this microversion given this change doesn't > modify the

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Ryan, In-line below. Regards John From: Ryan Moats > Date: Friday, June 17, 2016 at 7:35 AM To: John McDowall > Cc: Na Zhu >, Srilatha

Re: [openstack-dev] [Neutron][LBaaS][Octavia]In amphora plugin_vip(), why cidr and gateway are required but not used?

Here is a bug for that - https://bugs.launchpad.net/octavia/+bug/1585804 You’re more than welcome to fix this issue. Lubosz Kosnik Cloud Software Engineer OSIC lubosz.kos...@intel.com On Jun 17, 2016, at 6:37 PM, Jiahao Liang

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

Ricardo, Thanks for sharing. It is good to hear that Magnum works well with a 200 nodes cluster. Best regards, Hongbin > -Original Message- > From: Ricardo Rocha [mailto:rocha.po...@gmail.com] > Sent: June-17-16 11:14 AM > To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [requirements][all] VOTE to expand the Requirements Team

Sure. +1 On 17 June 2016 at 02:44, Davanum Srinivas wrote: > Folks, > > At Austin the Release Management team reached a consensus to spin off > with some new volunteers to take care of the requirements process and > repository [1]. The following folks showed up and worked with

Re: [openstack-dev] [manila]: questions on update-access() changes

Ramana, I think your questions got answered in a channel discussion last week, but I just wanted to double check that you weren't still expecting any answers here. If you were, please reply and we'll keep this thread going. On June 2, 2016 9:30:39 AM Ramana Raja wrote:

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

Ricardo, As one of the original authors of Magnum, I'm super pleased to hear Magnum works at this scale with a kubernetes bay. I don't think it would have done that when I finished working on Magnum - a testament to the great community around Magnum. Regards -steve From: Ton Ngo

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Thanks for getting this started Clint, I'm happy and excited to be involved in helping try to guide the whole ecosystem together (it's also why I like being in oslo) to a architecture that is more cohesive (and is more of something that we can say to our current or future children that we

Re: [openstack-dev] [OpenStack-Infra] Upcoming changes now that Jenkins has retired

On 6/16/16, 6:13 PM, "James E. Blair" wrote: >Now that we have retired Jenkins, we have some upcoming changes: > >* Console logs are now available via TCP > > The status page now has "telnet" protocol links to running jobs. If > you connect to the host and port

[openstack-dev] [nova] Question about redundant API samples tests for microversions

I was reviewing this today: https://review.openstack.org/#/c/326940/ And I said to myself, 'self, do we really need to subclass the API samples functional tests for this microversion given this change doesn't modify the request/response body, it's only adding paging support?'.

[openstack-dev] [nova] Do we need a config option for use_usb_tablet/pointer_model?

I was reviewing the last change in this blueprint series today: https://review.openstack.org/#/c/174854/ And started to question why we even have a config option for this anymore. The blueprint didn't have a spec but there are some details in the description about the use cases:

[openstack-dev] [Neutron][LBaaS][Octavia]In amphora plugin_vip(), why cidr and gateway are required but not used?

Added more related topics to the original email. -- Forwarded message -- From: Jiahao Liang (Frankie) Date: Fri, Jun 17, 2016 at 4:30 PM Subject: [openstack-dev][Octavia]In amphora plugin_vip(), why cidr and gateway are required but not used? To:

Re: [openstack-dev] [nova] Initial oslo.privsep conversion?

On 6/9/2016 6:51 PM, Tony Breeds wrote: On Fri, Jun 10, 2016 at 08:24:34AM +1000, Michael Still wrote: On Fri, Jun 10, 2016 at 7:18 AM, Tony Breeds wrote: On Wed, Jun 08, 2016 at 08:10:47PM -0500, Matt Riedemann wrote: Agreed, but it's the worked example part that

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

It's nice to hear about HTTP API. I'm quite new in nova and openstack and don't grasp all that rpc things yet and can miss something but anyway I have several thoughts about API. Boring standpoint. First to choose some technology I think we can look at how widely it's adopted and how many people

Re: [openstack-dev] [requirements][all] VOTE to expand the Requirements Team

On 06/16/2016 09:44 AM, Davanum Srinivas wrote: > Folks, > > At Austin the Release Management team reached a consensus to spin off > with some new volunteers to take care of the requirements process and > repository [1]. The following folks showed up and worked with me on > getting familiar with

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Apologies for being delayed on replying and in-line back as well Ryan John McDowall wrote on 06/15/2016 05:58:35 PM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Na Zhu , Srilatha Tangirala/San

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

On 06/17/2016 12:00 AM, Wang, Shane wrote: > Anita, sorry about replying to you slowly. Because we are a committee from a > couple of companies, and need discussion, which causes slowness. > I am not the only decision maker. Thanks Anita;) > > Regards. > -- > Shane No apology necessary, thank

Re: [openstack-dev] [murano] [murano-apps] Murano apps core changes

Done,  Sergey, feel free to add whoever you consider necessary in the group. --  Kirill Zaitsev Software Engineer Mirantis, Inc On 14 June 2016 at 14:21:18, Kirill Zaitsev (kzait...@mirantis.com) wrote: Last week a patch [1] has been landed, that added murano-apps-core group, responsible for

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

Thanks Ricardo for sharing the data, this is really encouraging! Ton, From: Ricardo Rocha To: "OpenStack Development Mailing List (not for usage questions)" Date: 06/17/2016 08:16 AM Subject:[openstack-dev]

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

On Fri, Jun 17, 2016 at 10:23 AM, Sylvain Bauza wrote: > > In the review, you explain why you don't trust Routes and I respect that. > That said, are those issues logged as real problems for our API consumers, > which are mostly client libraries that we own and other projects

Re: [openstack-dev] [fuel] [kolla] Containerized OpenStack on Kubernetes experimental project proposal

Um, why try and reimplement Kolla from scratch rather then use the existing Kolla system and make it available via Fuel? There is already a project do deploy OpenStack containers in Kubernetes: http://docs.openstack.org/developer/kolla-kubernetes/ https://review.openstack.org/#/c/304182/ Lets

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

On Fri, 17 Jun 2016, Sylvain Bauza wrote: In the review, you explain why you don't trust Routes and I respect that. That said, are those issues logged as real problems for our API consumers, which are mostly client libraries that we own and other projects we know, like Horizon ? The

Re: [openstack-dev] [Magnum] The Magnum Midcycle

On Jun 14, 2016, at 3:37 PM, Anita Kuno wrote: > > What other projects would make sense for you to host mid-cycles for > should the opportunity arise? I can keep my ears open. Nova! Nova! Nova! -- Ed Leafe (really wants to see the LHC!)

[openstack-dev] [nova][scheduler] Next Scheduler Sub-team Meeting: Monday June 20 at @1400 UTC

The meeting will be held in #openstack-meeting-alt at 1400 UTC. We’ll be discussing the state of reviews and specs as in previous meetings. If you have something in particular that you’d like to make sure we discuss, please add it to the agenda:

Re: [openstack-dev] [ironic] Proposing two new cores

Big +2 for both here. -Chris On Thu, Jun 16, 2016 at 8:12 AM, Jim Rollenhagen wrote: > Hi all, > > I'd like to propose Jay Faulkner (JayF) and Sam Betts (sambetts) for the > ironic-core team. > > Jay has been in the community as long as I have, has been IPA and >

Re: [openstack-dev] [murano] Nominating Alexander Tivelkov and Zhu Rong for murano cores

Thanks everyone. Changes have been implemented. --  Kirill Zaitsev Software Engineer Mirantis, Inc On 17 June 2016 at 10:13:22, Omar Shykhkerimov (oshykhkeri...@mirantis.com) wrote: +1, agree with this proposition On Thu, Jun 16, 2016 at 3:08 PM, Victor Ryzhenkin

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

Le 17/06/2016 12:55, Chris Dent a écrit : tl;dr: Have a look at https://review.openstack.org/#/c/329386/ to help move some placement API decisions along. Not really that long, do read: As part of the generic resource pools spec[1] a new, independent of the rest of nova, API is being

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

On Fri, 17 Jun 2016, Andrey Volkov wrote: IMHO selector is too young in terms of version (0.1) and too old in terms of updates (3 years ago). It's 0.10. When I contacted the author (see the comments on https://review.openstack.org/#/c/329386/ ) he said the reason there were no recent

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

In-line below "discuss" wrote on 06/15/2016 05:51:20 PM: > From: John McDowall > To: Na Zhu > Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack > Development Mailing List \(not for usage questions\)"

[openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

Hi. Just thought the Magnum team would be happy to hear :) We had access to some hardware the last couple days, and tried some tests with Magnum and Kubernetes - following an original blog post from the kubernetes team. Got a 200 node kubernetes bay (800 cores) reaching 2 million requests /

[openstack-dev] [puppet] Action parameter missing in generated stonith fence manifests

Greetings, I was directed here from #puppet-openstack to submit an e-mail. Noted here, there is an 'action' parameter defined for fence_ifmib: https://github.com/openstack/puppet-pacemaker/blob/f62805f678f6fd8a260118279f6e0dbb05bff3d1/agent_generator/src_xml/fence_ifmib.xml#L83 However, in the

[openstack-dev] [nova] ability to set metadata on instances (but config drive is not updated)

Hi folks, I was noticing that its possible to do something like: $ nova meta josh-testr3 set "e=f" Then inside the VM I can do the following to eventually see that this changes shows up in the instance metadata exposed at the following: $ curl -s

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On 15:12 Jun 14, Matthew Treinish wrote: > On Tue, Jun 14, 2016 at 02:41:10PM -0400, Doug Hellmann wrote: > > Excerpts from Matthew Treinish's message of 2016-06-14 14:21:27 -0400: > > > On Tue, Jun 14, 2016 at 10:57:05AM -0700, Chris Hoge wrote: > > We have basically three options. > > > > 1.

[openstack-dev] Version header for OpenStack microversion support

Hi We are currently in the process of implementing microversion support in keystone - and are obviously trying to follow the cross-projec spec for this (http://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html

Re: [openstack-dev] Version header for OpenStack microversion support

On Jun 17, 2016, at 11:29 AM, Henry Nash wrote: > We are currently in the process of implementing microversion support in > keystone - and are obviously trying to follow the cross-projec spec for this >

Re: [openstack-dev] [nova][cinder] Integration testing for Nova API os-assisted-volume-snapshots

I'd be happy to help, too. Please drop e.g. a bug link in this thread we can use to follow up on things, that would be great. Best Silvan 2016-06-15 22:44 GMT+02:00 Sean McGinnis : > On Wed, Jun 15, 2016 at 07:01:17PM +0200, Jordan Pittier wrote: > > On Wed, Jun 15, 2016

Re: [openstack-dev] [TripleO] Proposed TripleO core changes

Excerpts from Steven Hardy's message of 2016-06-09 15:03:51 +0100: > Also, while reviewing the core group[2] I noticed the following members who > are no longer active and should probably be removed: > > - Radomir Dopieralski > - Martyn Taylor > - Clint Byrum > > I know Clint is still involved

Re: [openstack-dev] Upcoming changes now that Jenkins has retired

Hi James, I submitted a fix to openstack-infra/zuul via https://review.openstack.org/#/c/330853/. I found that username could not be changed from 'jenkins' to 'zuul' like https://github.com/openstack-infra/zuul/blob/master/tests/fixtures/layouts/good_require_approvals.yaml#L11 review_gerrit: -

[openstack-dev] [nova] [api] [placement] strategy for placement api structure

tl;dr: Have a look at https://review.openstack.org/#/c/329386/ to help move some placement API decisions along. Not really that long, do read: As part of the generic resource pools spec[1] a new, independent of the rest of nova, API is being developed called the "Placement API". The API will

Re: [openstack-dev] [requirements][all] VOTE to expand the Requirements Team

Davanum Srinivas wrote: Matthew Thode (prometheanfire) Dirk Mueller (dirk) Swapnil Kulkarni (coolsvap) Tony Breeds (tonyb) Thomas Bechtold (tbechtold) +1 -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not

Re: [openstack-dev] [tripleo] Zaqar messages standardization

On 05/26/2016 12:18 PM, Thomas Herve wrote: On Thu, May 26, 2016 at 11:48 AM, Jiri Tomasek wrote: On 05/25/2016 08:08 PM, Thomas Herve wrote: Sorry for not responding earlier, but I have some inputs. In Heat we publish events on Zaqar queue, and we defined this format: