[openstack-dev] [Horizon][DataTables] how to generate a confirmation dialog

Hi all - I don't see a better forum anywhere for this post - please correct me if I'm wrong. I have a django/horizon application. On one page users may delete objects. I'd like to display a modal dialog confirming the delete before submit. Can anyone tell me if there's a way to tie a

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

I’ll be completely honest in that I do not know what precisely a strategy plugin is. Perhaps we should have an irc discussion on the topic so you can educate me ;) That said, I assume Ansible loads the strategy plugin. We already hide Ansible behind a network service (popen). Is the issue

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

I read what you say Steven;) strategy plugin is not module, we don't use popen there. Also it will require importing GPL code from Ansible itself. Clint is right in this context. Writing it from scratch is not an option to (way to complex than docker stuff we did). Imho only option will be to

[openstack-dev] [nova][ironic] Instance can "migrate" to another node?

Message: 7 Date: Thu, 3 Nov 2016 16:50:54 + From: Jay Faulkner > To: "OpenStack Development Mailing List (not for usage questions)" > Subject: Re: [openstack-dev]

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

Michal, Have you read nothing I’ve said? If its new code, write it as ASL2.0. The fact that it plugs in or uses GPLv3 code is totally irrelevant since it is isolated by a network layer (specifically popen). Regards -steve From: Michał Jastrzębski Reply-To: "OpenStack

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

Clint, I disagree that modules (which are really plugins) must be licensed under GPLv3. You may license any module code as you like (i.e. ASL2.0) and include it in a GPLv3 project via Ansible modules because the modules act as plugins. The ASL2.0 license does taint, however, it does not

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

So as Clint mentioned, strategy plugins probably will be tainted by GPL. One of alternatives would be to create separate project for this single plugin, but I'd rather avoid that. Any other alternatives comes to mind? On Nov 4, 2016 5:18 PM, "Fox, Kevin M" wrote: > Must be

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

Must be gplv3 compatible. not necessarily gpl. apache license is compatible. Thanks, Kevin From: Clint Byrum [cl...@fewbar.com] Sent: Friday, November 04, 2016 4:38 PM To: openstack-dev Subject: Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

[openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

The keystone team has a new spec being proposed for the Ocata release, it essentially boils down to adding properties / metadata for projects (for now) [1]. We have somewhat had support for this, we have an "extras" column defined in our database schema, whatever a user puts in a request that

Re: [openstack-dev] [tc][solum] is solum-infra-guestagent an unmaintained project?

bump, still hoping to get feedback on this On Fri, Oct 28, 2016 at 1:23 AM, Steve Martinelli wrote: > When reviewing the projects necessary for the ocata community-wide goal, > (to remove old oslo-incubator code [1]) I noticed that solum-infra-guest > agent has had

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

Excerpts from Jeremy Stanley's message of 2016-11-04 23:05:54 +: > On 2016-11-04 22:50:10 + (+), Jeremy Stanley wrote: > [...] > > As I understand it, the challenge here is that plugins for Ansible > > will by definition be derivative works of Ansible and thus inherit > > their license

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

Cool. I didn’t even know ansible had a BSD licensed example module. As we have a module expertise in our community already, I suspect we will start from zero code rather than introduce a BSD license addendum to the Kolla repo. Regards -steve From: Jeremy Stanley

Re: [openstack-dev] [oslo] New and next-gen libraries (a BCN followup)

On 4 Nov 2016, at 7:50, Jim Rollenhagen wrote: > On Thu, Nov 3, 2016 at 3:04 PM, Joshua Harlow wrote: >> Jay Faulkner wrote: On Nov 3, 2016, at 11:27 AM, Joshua Harlow wrote: Just as a followup from the summit, One of

[openstack-dev] OpenStack Developer Mailing List Digest October 29 to November 4

HTML version: http://www.openstack.org/blog/2016/11/openstack-developer-mailing-list-digest-20161104/ Cross Project Proprietary Driver Code Recap === * At the Barcelona design summit there was a cross-project session on the challenge we’re running where

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

On 2016-11-04 23:06:05 + (+), Steven Dake (stdake) wrote: [...] > The correct answer here is simply to develop an ASL2.0 module that > works with Ansible. The GPLv3 does not require us to implement > Ansible modules in GPLv3 – we may use whatever license we like (in > this case ASL2.0

[openstack-dev] [nova] A note to contributors - bug triage ftw!

There was a lot of discussion at the Ocata summit about new contributors and not so new contributors and what they can do. Well, bug triage is a pretty simple but very effective way to help out and also be productive. At about 4:30pm CST today (Friday), I was perusing the untriaged nova bug

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

On 2016-11-04 22:50:10 + (+), Jeremy Stanley wrote: [...] > As I understand it, the challenge here is that plugins for Ansible > will by definition be derivative works of Ansible and thus inherit > their license choice. No amount of "clean room reimplementation" > will solve that unless

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

Jeremy Apologies for top post – lookout broken again. Since Kolla uses popen to launch Ansible, and the module loads into GPLv3 code, the GPLv3 license ends at the Ansible end of the popen call. Transitive dependencies are not a thing with network services (popen creates a network service).

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

Swapnil, If you feel someone is lazy with not filing bugs for backports or feature request, with a monster feature request or something that requires a backport, simply -1 the review and add a polite comment “Please add a bug ID or blueprint”. Regards, -steve From: Swapnil Kulkarni

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

Paul, I’ll take your request as a request for a vote of the core reviewers. My vote is +1 in favor of removing the requirement for TrivialFix. As per our standard policy, the voting window is open for 7 days beginning November 3rd, and finishing (in 7 days) on November 11th. Regards -steve

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

On 2016-11-04 22:22:47 + (+), Steven Dake (stdake) wrote: [...] > The first file I examine in any repository is the LICENSE file – > if its GPLv3, I look no further. I recommend everyone that has > signed the CLA follow the same pattern to keep OpenStack in good > legal health. As I

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

Andreas, Agree. Asked and answered. If Michal has some differing viewpoint, that’s his prerogative as the PTL of Kolla, however, I would have serious concerns with that model, and would request a vote of the core reviewers to solidify our processes to match the OpenStack way. Regards -steve

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

Define “touching GPLv3 code”. If you mean using someone else’s work which creates a derived work, that is a big no-no. This would cause your CL If it’s a fresh implementation, then USE ASL2.0. This creates a transitive dependency that taints the module on instantiation, however, since we use

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

Jeremy, Kolla doesn’t want to be a special snowflake WRT patches. TrivialFix was introduced to help core reviewers identify what bugs need backports vs which changes do not or are feature changes (which we also don’t backport). We don’t always get backport tracking correctly, but I think we

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

The general rule I follow (and would propose we stick to) is is as follows: If it requires a backport – it requires a bug id. (This is to facilitate the tracking of backports to make sure we do the job correctly) If it doesn’t require a backport but is a feature submission, it should include a

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

Wrong answer. The correct answer is all software in the Kolla repository should be ASL2.0 licensed. See legal list for a more thorough explanation based upon the historical discussions I’ve been through with the TC and BOD on this question. If it is GPLv3 licensed code, it should be

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

On 04/11/16 12:51, Jeremy Stanley wrote: On 2016-11-04 11:42:25 -0500 (-0500), Michał Jastrzębski wrote: [...] Kolla is licensed as Apache v2 all across the board today. To implement one of highly requested features we would need to develop so-called strategy plugin for ansible, and I can't see

[openstack-dev] [nova] ocata summit unconference session recap

We had a single unconference session this time at the Ocata summit. The full etherpad is here: https://etherpad.openstack.org/p/ocata-nova-summit-unconference We spent most of the session talking about three newly proposed virt drivers. IBM PowerVM --- The PowerVM driver has been

[openstack-dev] Can openstack/jacket be removed now?

The jacket project was added to project-config several months ago: https://review.openstack.org/#/c/263500/ To date it's more wiki: https://wiki.openstack.org/wiki/Jacket Than code: https://github.com/openstack/jacket/commits/master Given the platform9/omni [1] stuff demo'ed at the Ocata

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

On 11/04/2016 06:40 PM, Emilien Macchi wrote: > MIchele Baldessari (bandini on IRC) has consistently demonstrated high > levels of contributions in TripleO projects, specifically in High > Availability area where's he's for us a guru (I still don't understand > how pacemaker works, but hopefully

[openstack-dev] [nova] API work for ocata summit session recap

John Garbutt led a session at the summit focusing on some of the API work items for Ocata. The full etherpad is here: https://etherpad.openstack.org/p/ocata-nova-summit-api API capabilities We talked a bit about the cross-project discoverable API spec. There was also a xp

[openstack-dev] [nova] Reminder to get started on code for approved blueprints

This is just a general observation and reminder. Spec freeze is November 17th. We already have a lot of blueprints approved for Ocata: https://blueprints.launchpad.net/nova/ocata And several of those don't have code posted yet. Some of them are small enough that they can probably be done in a

Re: [openstack-dev] [nova] Nova-MultiJob CI (non-voting) request to comment

On 11/4/2016 2:04 AM, Lenny Verkhovsky wrote: It uses 2 physical servers with 2 compute nodes And runs migration tests only. Other Mellanox CI jobs run on a single allinone server, thus migration tests are skipped. I think this was mentioned at the summit. In general we have a major gap in

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

+1 Awesome!!! On Fri, Nov 4, 2016 at 7:49 PM, Brent Eagles wrote: > > > On Fri, Nov 4, 2016 at 3:10 PM, Emilien Macchi wrote: >> >> MIchele Baldessari (bandini on IRC) has consistently demonstrated high >> levels of contributions in TripleO projects,

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

On Fri, Nov 4, 2016 at 3:10 PM, Emilien Macchi wrote: > MIchele Baldessari (bandini on IRC) has consistently demonstrated high > levels of contributions in TripleO projects, specifically in High > Availability area where's he's for us a guru (I still don't understand > how

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

+1! On Fri, Nov 4, 2016 at 2:34 PM, Juan Antonio Osorio wrote: > +1 :D > > > On 4 Nov 2016 20:16, "Jiří Stránský" wrote: >> >> +1, Michele does great reviews, and his contributions around HA and >> upgrades have been crucial. >> >> On 4.11.2016 18:40,

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

On Fri, Nov 4, 2016 at 1:40 PM, Emilien Macchi wrote: > MIchele Baldessari (bandini on IRC) has consistently demonstrated high > levels of contributions in TripleO projects, specifically in High > Availability area where's he's for us a guru (I still don't understand > how

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

+1 :D On 4 Nov 2016 20:16, "Jiří Stránský" wrote: > +1, Michele does great reviews, and his contributions around HA and > upgrades have been crucial. > > On 4.11.2016 18:40, Emilien Macchi wrote: > >> MIchele Baldessari (bandini on IRC) has consistently demonstrated high >>

Re: [openstack-dev] [Congress] Restart Congress server

Hi Ruben, Awesome to hear about your progress! The error seems to be independent of adding a new driver. Could you try using the unchanged congress.conf and restarting again to see if the same problem shows up? Also, could you give the command you¹re using the launch congress-server? Mainly I

[openstack-dev] Proposing Maxime Cottret as core for cloudkitty

Hello developer mailing list folks, I'd like to propose that we add Maxime Cottret (aolwas) as an OpenStack cloudkitty core reviewer. He has been a member of our community for a few months. Working mainly on the stabilisation/bug fixing of our project he really showed some great

[openstack-dev] Proposing Zhang Guoqing as core for cloudkitty

Hello developer mailing list folks, I'd like to propose that we add Zhang Guoqing (zhangguoqing) as an OpenStack cloudkitty core reviewer. He has been a member of our community for many months, contributing very seriously in cloudkitty and cloudkitty-dashboard. He also provided many reviews

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

+1, Michele does great reviews, and his contributions around HA and upgrades have been crucial. On 4.11.2016 18:40, Emilien Macchi wrote: MIchele Baldessari (bandini on IRC) has consistently demonstrated high levels of contributions in TripleO projects, specifically in High Availability area

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

On 04/11/16 19:40, Emilien Macchi wrote: > MIchele Baldessari (bandini on IRC) has consistently demonstrated high > levels of contributions in TripleO projects, specifically in High > Availability area where's he's for us a guru (I still don't understand > how pacemaker works, but hopefully he

Re: [openstack-dev] [packstack] Proposal to add Alfredo Moralejo as core reviewer

So after a week we have three +2, one +1, and noone against. Alfredo, welcome to the core team! Javier - Original Message - > Hi all, > > I'd like to propose Alfredo Moralejo (amoralej in #Freenode) as a core > reviewer for Packstack. > > Alfredo has been providing consistent and

Re: [openstack-dev] [networking-sfc][devstack][mitaka] Chain doesn't work

Hi Alioune, SFC is working fine. Your problem is with configuration of your specific Service Function. AFAIK, Farhad has responded to your question before. https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg95199.html Thanks, Cathy From: Alioune [mailto:baliou...@gmail.com]

Re: [openstack-dev] [manila] Barcelona Design Summit summary

Ben Swartzlander wrote: Thanks to gouthamr for doing these writeups and for recording! We had a great turn out at the manila Fishbowl and working sessions. Important notes and Action Items are below: === Fishbowl 1: Race Conditions === Thursday

Re: [openstack-dev] Nova-MultiJob CI (non-voting) request to comment

On 11/03/2016 02:45 AM, Lenny Verkhovsky wrote: Hi, We would like Mellanox[1] MultiNode CI job to start commenting as ‘non voting’ job on partial nova[2] and tempest[3] code. This Job runs few migration tests[4] and an example of its run can be seen here[5]. [1]

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

On Fri, Nov 4, 2016 at 10:01 PM, Jeremy Stanley wrote: > On 2016-11-04 15:42:17 + (+), Paul Bourke wrote: >> We have no desire to do this, that's not what is being discussed >> here. On the contrary we're looking to reduce the barrier to entry >> for committers. Also

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

On Fri, Nov 4, 2016 at 9:12 PM, Paul Bourke wrote: > Hi Jeremy, > >> All I ask is that if the Kolla team wants to differentiate itself >> from the review requirements of most OpenStack projects, please make > > We have no desire to do this, that's not what is being

[openstack-dev] [tripleo] proposing Michele Baldessari part of core team

MIchele Baldessari (bandini on IRC) has consistently demonstrated high levels of contributions in TripleO projects, specifically in High Availability area where's he's for us a guru (I still don't understand how pacemaker works, but hopefully he does). He has done incredible work on composable

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

Yeah, I'll cross-post there, thanks Fungi. Anyone knows of any other openstack project with more than 1 license in their codebase? On 4 November 2016 at 11:51, Jeremy Stanley wrote: > On 2016-11-04 11:42:25 -0500 (-0500), Michał Jastrzębski wrote: > [...] >> Kolla is licensed

[openstack-dev] SIG-OpenStack @ Kubernetes

Folks, fyi, there's a bunch of Stackers working on Kubernetes. http://blog.kubernetes.io/2016/04/introducing-kubernetes-openstack-sig.html In Kubernetes, work is organized around Special Interest Groups: https://github.com/kubernetes/community/blob/master/README.md#special-interest-groups-sig

Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3

On 2016-11-04 11:42:25 -0500 (-0500), Michał Jastrzębski wrote: [...] > Kolla is licensed as Apache v2 all across the board today. To > implement one of highly requested features we would need to develop > so-called strategy plugin for ansible, and I can't see any reasonable > way to do it without

[openstack-dev] [tc][kolla] Ansible module with GPLv3

Hello, As you could see in [1], ansible is notorious with it's GPL v3 license. I have question about having single module in Kolla-ansible project that will be GPL v3. Kolla is licensed as Apache v2 all across the board today. To implement one of highly requested features we would need to

[openstack-dev] [release] git-upstream 0.12.1 release

Pleased to announce the 0.12.1 release of git-upstream. Main reason to ensure the man page is installed by default. With source available at: http://git.openstack.org/cgit/openstack/git-upstream Please report any issues through launchpad: https://bugs.launchpad.net/git-upstream git-upstream

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

On 2016-11-04 15:42:17 + (+), Paul Bourke wrote: > We have no desire to do this, that's not what is being discussed > here. On the contrary we're looking to reduce the barrier to entry > for committers. Also the team is aware that cross project efforts > should not be nit picked. That's

[openstack-dev] [freezer] Proposing Timothy Buckley to Freezer-core

Hi everyone, I would like to propose that we promote Tim Buckley (timothyb89) core. He has been a highly valuable developper for the past few month. His work can be found here: [1] And his stackalitics profile here: [2] If you agree with this change, please approve with a +1 answer or

Re: [openstack-dev] [neutron][routed-network] Host doesn't connected any segments when creating port

Hi Zhi, Both L2 provider networks and routed networks can have one or many segments. In the case of a L2 provider network, all the segments in it constitute a contiguous L2 domain. In contrast, in routed networks, each segment in it is a separate L2 domain. One consequence of this is that in L2

Re: [openstack-dev] Splitting notifications from rpc (and questions + work around this)

On Fri, 2016-11-04 at 10:45 -0400, Ken Giusti wrote: > On Wed, Nov 2, 2016 at 8:11 PM, Joshua Harlow > wrote: > > > > Hi folks, > > > > There was a bunch of chatter at the summit about how there are > > really two > > different types of (oslo) messaging usage that exist

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

Hi Jeremy, > All I ask is that if the Kolla team wants to differentiate itself > from the review requirements of most OpenStack projects, please make We have no desire to do this, that's not what is being discussed here. On the contrary we're looking to reduce the barrier to entry for

Re: [openstack-dev] [oslo] New and next-gen libraries (a BCN followup)

Excerpts from Jim Rollenhagen's message of 2016-11-04 10:50:34 -0400: > On Thu, Nov 3, 2016 at 3:04 PM, Joshua Harlow wrote: > > Jay Faulkner wrote: > >>> > >>> On Nov 3, 2016, at 11:27 AM, Joshua Harlow wrote: > >>> > >>> Just as a followup from the

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

On 11/04/2016 04:25 PM, Jeremy Stanley wrote: > On 2016-11-04 18:18:49 +0530 (+0530), Swapnil Kulkarni wrote: >> I feel TrivialFix is consistently used by people just to avoid going >> to lanuchpad and filing a bug. It should only be used only if the "Fix >> is Trivial" >> This has been well

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

On 2016-11-04 18:18:49 +0530 (+0530), Swapnil Kulkarni wrote: > I feel TrivialFix is consistently used by people just to avoid going > to lanuchpad and filing a bug. It should only be used only if the "Fix > is Trivial" > This has been well documented in the contributing doc [1] and this > should

Re: [openstack-dev] [Zun] Propose a change of Zun core team

Hi all, Thanks for your votes. According to the feedback, the proposal was approved. Welcome Shubham to join the core team. Best regards, Hongbin > -Original Message- > From: Fei Long Wang [mailto:feil...@catalyst.net.nz] > Sent: October-20-16 8:31 PM > To:

[openstack-dev] [glance] rolling upgrade demo and virtual design session

As discussed at the Summit and at yesterday's Glance meeting, Alex Bashmakov and Hemanth Makkapati will present a virtual design session (including a demo!) of the work they're doing toward zero downtime rolling upgrades on Friday, 11 November 2016. Please fill in your availability on a doodle

Re: [openstack-dev] [monasca] License for monasca-statsd

On 2016-11-03 15:03:44 -0400 (-0400), Chuck Short wrote: > I was looking at packaging monasca-statsd since it is a dependency for > designate, however when I look at the license for it,it says Apache-2. > However the LICENSE file included in the source is that the software is > provided as

Re: [openstack-dev] [monasca] License for monasca-statsd

Excerpts from Chuck Short's message of 2016-11-03 15:03:44 -0400: > Hi, > > I was looking at packaging monasca-statsd since it is a dependency for > designate, however when I look at the license for it,it says Apache-2. > However the LICENSE file included in the source is that the software is >

Re: [openstack-dev] [openstack][ironic] Event processing for async task improvement

I agree with the strategy Yuriy outlined. This has the added benefit of mitigating potential future bugs related to callbacks in the task manager since state "rollback" behavior will be implicitly built into the task manager. Details on the potential race condition with provision state change

Re: [openstack-dev] [all][dev][python] constructing a deterministic representation of a python data structure

Absolutely, the default would be disabled and those who want it can enable it. There will be a cost; hashing and signing aren't cheap and we shouldn't have to pay the cost when we don't have to. -amrith > -Original Message- > From: gordon chung [mailto:g...@live.ca] > Sent: Friday,

Re: [openstack-dev] [oslo] New and next-gen libraries (a BCN followup)

On Thu, Nov 3, 2016 at 3:04 PM, Joshua Harlow wrote: > Jay Faulkner wrote: >>> >>> On Nov 3, 2016, at 11:27 AM, Joshua Harlow wrote: >>> >>> Just as a followup from the summit, >>> >>> One of the sessions (the new lib one) had a few proposals: >>>

Re: [openstack-dev] Splitting notifications from rpc (and questions + work around this)

On Wed, Nov 2, 2016 at 8:11 PM, Joshua Harlow wrote: > Hi folks, > > There was a bunch of chatter at the summit about how there are really two > different types of (oslo) messaging usage that exist in openstack and how > they need not be backed by the same solution type

Re: [openstack-dev] [Openstack-operators] [puppet][fuel][packstack][tripleo] puppet 3 end of life

Just a bit of feedback on our side: We have been using Puppet 4 for quite sometime from the Puppetlabs repos without any issues. The OpenStack modules all work fine for us and I haven't ran into any issues around other modules having any major Puppet 4 compatibility issues. Sent from my

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

+1 2016-11-04 13:32 GMT+00:00 Jeffrey Zhang : > +1 > > On Fri, Nov 4, 2016 at 8:51 PM, Ryan Hallisey wrote: > >> +1 >> >> -Ryan >> >> - Original Message - >> From: "Swapnil Kulkarni" >> To: "OpenStack Development

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

+1 On Fri, Nov 4, 2016 at 8:51 PM, Ryan Hallisey wrote: > +1 > > -Ryan > > - Original Message - > From: "Swapnil Kulkarni" > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Sent:

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

+1 -Ryan - Original Message - From: "Swapnil Kulkarni" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Friday, November 4, 2016 8:48:49 AM Subject: Re: [openstack-dev] [kolla] Propose removal of TrivialFix

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

On Thu, Nov 3, 2016 at 6:51 PM, Paul Bourke wrote: > Kolleagues, > > How do people feel above removing the requirement of having TrivialFix in > commit messages where a bug/bp is not required? > > I'm seeing a lot of valid and important commits being held up because of >

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

Yeah I was thinking of it myself. +1 from me On 3 November 2016 at 09:08, Christian Berendt wrote: > >> On 3 Nov 2016, at 14:33, Mauricio Lima wrote: >> >> I Agree. +1 > > +1 > >

Re: [openstack-dev] [all][dev][python] constructing a deterministic representation of a python data structure

On 04/11/16 08:02 AM, Amrith Kumar wrote: > [Amrith Kumar] I wasn't sure I'd be able to do this before (the only place > where this model will work is in oslo.messaging) but thanks to the links > that Dims forwarded, there may be a chance to make this part of oslo! if you do this in

[openstack-dev] [requirements][infra] Fwd: [TIP] new tox-dev mailing list on python

At the summit last week there were some discussions about limitations of tox and how they affect our use of constraints. It looks like contributing to tox may be getting easier, so it's possible that some of the ideas floated at the summit (like adding separate install commands or a "prepare

Re: [openstack-dev] [all][dev][python] constructing a deterministic representation of a python data structure

> -Original Message- > From: Clint Byrum [mailto:cl...@fewbar.com] > Sent: Thursday, November 3, 2016 6:04 PM > To: openstack-dev > Subject: Re: [openstack-dev] [all][dev][python] constructing a deterministic > representation of a python data structure

[openstack-dev] [Congress] Restart Congress server

Hi everyone, I've tried to write a datasource driver for Magnum and the unit test for it. So I've add this datasource driver in /opt/stack/congress/congress/datasources/ and the unit test in /opt/stack/congress/congress/tests/datasources/ to test it. Moreover, I've add the driver to

Re: [openstack-dev] [oslo] New and next-gen libraries (a BCN followup)

Le 2016-11-03 19:27, Joshua Harlow a écrit : *Next-gen oslo.service replacement* This one may require a little more of a plan on how to make it work, but the gist is that medhi (and others) has created https://github.com/sileht/cotyledon which is a nice replacement for oslo.service that

[openstack-dev] [daisycloud-core] Meeting minutes for IRC meeting 0800UTC Nov. 4 2016

Minutes: http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-11-04-08.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-11-04-08.00.txt Log:

[openstack-dev] [infra]multi-region devstack gate job

Hello, Is multi-region devstack gate job supported in openstack-infra? Devstack itself supports multi-region setup, i.e, multiple OpenStack clouds with shared KeyStone[1]. Tricircle wants to add multi-region gate job for cross Neutron networking automation, but did not find some example on how

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Nov. 4 2016

1) Roll Call 2) OPNFV: Escalator Support 3) OPNFV: Daisy4nfv CI Framework Progress 4) Core Code Abstraction B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [nova] Nova-MultiJob CI (non-voting) request to comment

It uses 2 physical servers with 2 compute nodes And runs migration tests only. Other Mellanox CI jobs run on a single allinone server, thus migration tests are skipped. > -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Friday, November 04, 2016 1:45

Re: [openstack-dev] [Openstack-operators] [puppet][fuel][packstack][tripleo] puppet 3 end of life

On 4 Nov 2016, at 06:31, Sam Morrison > wrote: On 4 Nov. 2016, at 1:33 pm, Emilien Macchi > wrote: On Thu, Nov 3, 2016 at 9:10 PM, Sam Morrison > wrote:

[openstack-dev] [new][neutron] neutron-lib 1.0.0 release (ocata)

We are ecstatic to announce the release of: neutron-lib 1.0.0: Neutron shared routines and utilities This release is part of the ocata release series. The source is available from: http://git.openstack.org/cgit/openstack/neutron-lib Download the package from:

Re: [openstack-dev] [neutron] proposal to resolve a rootwrap problem for XenServer

Thanks Ihar, Thierry and Bob. I think we've agreed to go with the 1st option - "Get Neutron to call XenAPI directly rather than trying to use a daemon". I will refine the POC patch to make it ready for the formal review. R.g.t the test, I did some basic test in a real lab manually and it worked