Re: [openstack-dev] os-ansible-deplpoyment has released Kilo

Hi Dani, To touch on the provisioining we presently have no plans to introduce baremetal provisioning via a PXE, Razor, djeep, etc… Our present thinking is to allow people to use whatever they want to provision the hosts and then come in with OSAD, post the OS deployment, to install OpenStack.

Re: [openstack-dev] [Fuel] Speed Up RabbitMQ Recovering

> On 5 May 2015, at 2:31 pm, Zhou Zheng Sheng / 周征晟 > wrote: > > Thank you Bogdan for clearing the pacemaker promotion process for me. > > on 2015/05/05 10:32, Andrew Beekhof wrote: >>> On 29 Apr 2015, at 5:38 pm, Zhou Zheng Sheng / 周征晟 >>> wrote: >> [snip] >> >>> Batch is a pacemaker conce

Re: [openstack-dev] [PKG-Openstack-devel][horizon][xstatic] XStatic-Angular-Bootstrap in violation of the MIT/Expat license (forwarded from: python-xstatic-angular-bootstrap_0.11.0.2-1_amd64.changes R

On 05/05/15 05:29, Robert Collins wrote: Probably, but it's legally wrong (ie: worst case, you can be sued) to leave a package which is in direct violation of the license of things it contains. So,we shouldn't use angular at all then, because as a js framework its distributed to users when the

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

On 2015-05-05 1:25 AM, Monty Taylor wrote: > On 05/04/2015 08:47 PM, Emilien Macchi wrote: > > >> On 05/04/2015 10:37 PM, Rich Megginson wrote: >>> On 05/04/2015 07:52 PM, Mathieu Gagné wrote: On 2015-05-04 9:15 PM, Rich Megginson wrote: > On 05/04/2015 06:03 PM, Mathieu Gagné wrote: >>>

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/04/2015 08:47 PM, Emilien Macchi wrote: > > > On 05/04/2015 10:37 PM, Rich Megginson wrote: >> On 05/04/2015 07:52 PM, Mathieu Gagné wrote: >>> On 2015-05-04 9:15 PM, Rich Megginson wrote: On 05/04/2015 06:03 PM, Mathieu Gagné wrote: >>>

Re: [openstack-dev] [neutron][lbaas][octavia] what are the main differences between the two

Thanks a bunch Doug, very clear & helpful info. so with that said those who run IceHouse or Juno are (more or less :) ) dead in the water as the only option is v1 ...hmm Dani On Mon, May 4, 2015 at 10:21 PM, Doug Wiegley wrote: > lbaas v1: > > This is the original Neutron LBaaS, and what you s

Re: [openstack-dev] [Fuel] Speed Up RabbitMQ Recovering

Thank you Bogdan for clearing the pacemaker promotion process for me. on 2015/05/05 10:32, Andrew Beekhof wrote: >> On 29 Apr 2015, at 5:38 pm, Zhou Zheng Sheng / 周征晟 >> wrote: > [snip] > >> Batch is a pacemaker concept I found when I was reading its >> documentation and code. There is a "batch-

Re: [openstack-dev] [PKG-Openstack-devel][horizon][xstatic] XStatic-Angular-Bootstrap in violation of the MIT/Expat license (forwarded from: python-xstatic-angular-bootstrap_0.11.0.2-1_amd64.changes R

On 5 May 2015 at 11:13, Thomas Goirand wrote: > On 05/05/2015 12:15 AM, Ian Cordasco wrote: >> >> For what it’s worth Thomas and Maxime, removing the old versions from PyPI >> is likely to be a bad idea. > > > Probably, but it's legally wrong (ie: worst case, you can be sued) to leave > a package

Re: [openstack-dev] [Fuel] Speed Up RabbitMQ Recovering

Thank you Andrew. on 2015/05/05 08:03, Andrew Beekhof wrote: >> On 28 Apr 2015, at 11:15 pm, Bogdan Dobrelya wrote: >> >>> Hello, >> Hello, Zhou >> >>> I using Fuel 6.0.1 and find that RabbitMQ recover time is long after >>> power failure. I have a running HA environment, then I reset power of >>

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

On 05/04/2015 10:37 PM, Rich Megginson wrote: > On 05/04/2015 07:52 PM, Mathieu Gagné wrote: >> On 2015-05-04 9:15 PM, Rich Megginson wrote: >>> On 05/04/2015 06:03 PM, Mathieu Gagné wrote: On 2015-05-04 7:35 PM, Rich Megginson wrote: > The way authentication works with the Icehouse bran

[openstack-dev] [Sahara][oslo]Error in Log.debug

Hi all, I just upgrade my devstack and re-installed. My sahara keep reporting errors: 2015-05-05 10:42:00.453 DEBUG sahara.openstack.common.loopingcall [-] Dynamic looping call > sleeping for 35.91 seconds from (pid=5361) _inner /opt/stack/sahara/sahara/openstack/common/loopingcall.py:132 201

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

On 05/04/2015 07:52 PM, Mathieu Gagné wrote: On 2015-05-04 9:15 PM, Rich Megginson wrote: On 05/04/2015 06:03 PM, Mathieu Gagné wrote: On 2015-05-04 7:35 PM, Rich Megginson wrote: The way authentication works with the Icehouse branch is that puppet-keystone reads the admin_token and admin_endp

Re: [openstack-dev] [PKG-Openstack-devel][horizon][xstatic] XStatic-Angular-Bootstrap in violation of the MIT/Expat license (forwarded from: python-xstatic-angular-bootstrap_0.11.0.2-1_amd64.changes R

On 5/4/15, 18:13, "Thomas Goirand" wrote: >On 05/05/2015 12:15 AM, Ian Cordasco wrote: >> For what it’s worth Thomas and Maxime, removing the old versions from >>PyPI >> is likely to be a bad idea. > >Probably, but it's legally wrong (ie: worst case, you can be sued) to >leave a package which is

Re: [openstack-dev] [Fuel] Speed Up RabbitMQ Recovering

> On 29 Apr 2015, at 5:38 pm, Zhou Zheng Sheng / 周征晟 > wrote: [snip] > Batch is a pacemaker concept I found when I was reading its > documentation and code. There is a "batch-limit: 30" in the output of > "pcs property list --all". The pacemaker official documentation > explanation is that it'

[openstack-dev] [neutron] IPv4 transition/interoperation with IPv6

Does Neutron support any of the 4/6 interoperation/transition techniques? I wear an operator's hat nowadays, and want to make IPv6 as useful and easy to use as possible for my tenants. I think the interoperation/transition techniques will play a big role in this. Thanks, Mike__

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

On 2015-05-04 9:15 PM, Rich Megginson wrote: > On 05/04/2015 06:03 PM, Mathieu Gagné wrote: >> On 2015-05-04 7:35 PM, Rich Megginson wrote: >>> The way authentication works with the Icehouse branch is that >>> puppet-keystone reads the admin_token and admin_endpoint from >>> /etc/keystone/keystone.

Re: [openstack-dev] [Neutron] Success of the IPv6 Subteam - Proposal to disband

On Mon, May 4, 2015 at 7:37 PM, Sean M. Collins wrote: > It is a bittersweet moment - I am proposing that due to the amazing > success that we have had as a subteam, that because we have > accomplished so much, that it makes sense for our team to > disband and re-integrate with other subteams (th

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

On 05/04/2015 06:03 PM, Mathieu Gagné wrote: On 2015-05-04 7:35 PM, Rich Megginson wrote: The way authentication works with the Icehouse branch is that puppet-keystone reads the admin_token and admin_endpoint from /etc/keystone/keystone.conf and passes these to the keystone command via the OS_SE

[openstack-dev] [Neutron] Success of the IPv6 Subteam - Proposal to disband

It is a bittersweet moment - I am proposing that due to the amazing success that we have had as a subteam, that because we have accomplished so much, that it makes sense for our team to disband and re-integrate with other subteams (the L3 subteam comes to mind) or have items in the on-demand agenda

Re: [openstack-dev] [TC][Keystone] Rehashing the Pecan/Falcon/other WSGI debate

Hi all, To be clear, both Pecan and Falcon are actively maintained and have healthy communities. In any case, I tend to point OpenStack projects toward Pecan as the default choice, since that lets you take advantage of all the benefits standardization has to offer. Of course, you need to quantify

Re: [openstack-dev] [all][oslo][clients] Let's speed up start of OpenStack libs and clients by optimizing imports with profimp

On 7 April 2015 at 10:43, Robert Collins wrote: >> $ time openstack -h >> >> real0m2.491s >> user0m2.378s >> sys 0m0.111s > > > pbr should be snappy - taking 100ms to get the version is wrong. I've now tested this. With an egg-info present in a git tree: python -m timeit -n 1 -r 1 -

Re: [openstack-dev] [Fuel] Speed Up RabbitMQ Recovering

> On 28 Apr 2015, at 11:15 pm, Bogdan Dobrelya wrote: > >> Hello, > > Hello, Zhou > >> >> I using Fuel 6.0.1 and find that RabbitMQ recover time is long after >> power failure. I have a running HA environment, then I reset power of >> all the machines at the same time. I observe that after re

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

On 2015-05-04 7:35 PM, Rich Megginson wrote: > > The way authentication works with the Icehouse branch is that > puppet-keystone reads the admin_token and admin_endpoint from > /etc/keystone/keystone.conf and passes these to the keystone command via > the OS_SERVICE_TOKEN env. var. and the --os-en

Re: [openstack-dev] [pbr] pbr-release includes oslo-core?

On 5 May 2015 at 11:48, Davanum Srinivas wrote: > Not sure about the history, but +1 to remove oslo-core from that group. Done. If its a terrible mistake we can add it back easily enough. -Rob -- Robert Collins Distinguished Technologist HP Converged Cloud __

Re: [openstack-dev] [pbr] pbr-release includes oslo-core?

Not sure about the history, but +1 to remove oslo-core from that group. -- dims On Mon, May 4, 2015 at 6:59 PM, Robert Collins wrote: > Clark and I spotted this when releasing 0.11 - pbr-release, the group > of folk that can cut a release, includes oslo-release (expected) and > also unexpectedly

[openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

I'm currently working on Keystone v3 support in the openstack puppet modules. The way authentication works with the Icehouse branch is that puppet-keystone reads the admin_token and admin_endpoint from /etc/keystone/keystone.conf and passes these to the keystone command via the OS_SERVICE_TOK

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

Hi Dave :) On 5 May 2015 at 10:37, Dave Walker wrote: ... > Hey, > > As someone that did track master PBR Master for internal cross-project > builds during the SemanticVersioning ping-pong, I have to agree that > having a core tool that should be pretty static in feature deliverable > be a regula

Re: [openstack-dev] [PKG-Openstack-devel][horizon][xstatic] XStatic-Angular-Bootstrap in violation of the MIT/Expat license (forwarded from: python-xstatic-angular-bootstrap_0.11.0.2-1_amd64.changes R

On 05/05/2015 12:15 AM, Ian Cordasco wrote: For what it’s worth Thomas and Maxime, removing the old versions from PyPI is likely to be a bad idea. Probably, but it's legally wrong (ie: worst case, you can be sued) to leave a package which is in direct violation of the license of things it con

[openstack-dev] [pbr] pbr-release includes oslo-core?

Clark and I spotted this when releasing 0.11 - pbr-release, the group of folk that can cut a release, includes oslo-release (expected) and also unexpectedly oslo-core. https://review.openstack.org/#/admin/groups/387,members This means that folk that are olso-core, but can't release regular librari

[openstack-dev] [Infra] Meeting Tuesday May 5th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday May 5th[0], at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone interest

Re: [openstack-dev] [all] Replace mysql-python with mysqlclient

On 04/30/2015 07:48 PM, Mike Bayer wrote: On 4/30/15 11:00 AM, Victor Stinner wrote: Hi, I propose to replace mysql-python with mysqlclient in OpenStack applications to get Python 3 support, bug fixes and some new features (support MariaDB's libmysqlclient.so, support microsecond in TIME co

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

On 4 May 2015 at 23:01, Jeremy Stanley wrote: > On 2015-05-05 07:53:20 +1200 (+1200), Robert Collins wrote: > [...] >> release weekly > [...] > > I'm fine with releasing weekly when there's something to release, > but as PBR is somewhat stabilized and relatively tightly scoped I > _hope_ that we g

Re: [openstack-dev] [all] cross project communication: periodic developer newsletter?

Thanks Joe for bringing this up. I have always tried to find topics worth being covered in the weekly newsletter. I assemble that newsletter thinking of developers and operators as the main targets, I'd like both audiences to have one place to look at weekly and skim rapidly to see if they missed s

Re: [openstack-dev] [PKG-Openstack-devel][horizon][xstatic] XStatic-Angular-Bootstrap in violation of the MIT/Expat license (forwarded from: python-xstatic-angular-bootstrap_0.11.0.2-1_amd64.changes R

On 5/3/15, 11:46, "Thomas Goirand" wrote: >Hi, > >According to Paul Tagliamonte, who is from the Debian FTP master team >(which peer-reviews NEW packages in Debian before they reach the >archive) python-xstatic-angular-bootstrap cannot be uploaded as-is to >Debian because it doesn't include an

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

On 2015-05-05 07:53:20 +1200 (+1200), Robert Collins wrote: [...] > release weekly [...] I'm fine with releasing weekly when there's something to release, but as PBR is somewhat stabilized and relatively tightly scoped I _hope_ that we get to the point where we don't have bugs or new features in P

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

On 2015-05-04 10:25:10 -0700 (-0700), Adam Lawson wrote: [...] > it's pretty rare to see project teams led and governed by only > developers. [...] Not sure what other free software projects you've worked on/with before but not only is it not rare, it's the vast majority of them. -- Jeremy Stanle

Re: [openstack-dev] [neutron][lbaas][octavia] what are the main differences between the two

lbaas v1: This is the original Neutron LBaaS, and what you see in Horizon or in the neutron CLI as “lb-*”. It has an haproxy backend, and a few vendors supporting it. Feature-wise, it’s basically a byte pump. lbaas v2: This is the “new” Neutron LBaaS, and is in the neutron CLI as “lbaas-*” (i

Re: [openstack-dev] [Neutron] _get_subnet() in OpenContrail tests results in port deletion

I think the first workaround is the solution we're looking for as it better reflects the fact that opencontrail is a db-less plugin. I hope it will be the easier too, but you can never be too sure with neutron unit tests. Salvatore On 4 May 2015 at 12:56, Pavel Bondar wrote: > Hi Kevin, > > Tha

[openstack-dev] [neutron][lbaas][octavia] what are the main differences between the two

Hi all, I'm trying to gather more info about the differences between Neutron LBaaS v1 Neutron LBaaS v2 Octavia I know Octavia is still not marked production but on the other hand i keep hearing inside my organization that Neutron LBaaS is missing few critical "pieces" so i'd very much appreciate

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

Thanks Alex! On Mon, May 4, 2015 at 11:38 AM, Alex Meade wrote: > Hey Erlon, > > The summit etherpad is here: > https://etherpad.openstack.org/p/liberty-cinder-async-reporting > > It links to what we discussed in Paris. I will be filling it out this > week. Also note, I have submitted this topic

Re: [openstack-dev] os-ansible-deplpoyment has released Kilo

Hey Kevin, Let me add more info: 1) trying to understand if there is any support for baremetal provisioning (e.g setup the UCS manager if using UCS blades etc, dump the OS on it). I don't care if is Ironic or PXE/ Kickstart or Foreman etc 2) deployments on baremetal without the use of LXC contain

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

On 05/04/2015 04:15 PM, Robert Collins wrote: > On 5 May 2015 at 08:12, Monty Taylor wrote: >> On 05/04/2015 03:53 PM, Robert Collins wrote: > >> I'm fine with that in principle - I tend to release personal libraries >> pretty much as soon as something interesting hits them. I have no >> personal

Re: [openstack-dev] [all] cross project communication: periodic developer newsletter?

On Mon, May 4, 2015 at 12:27 PM, Robert Collins wrote: > On 5 May 2015 at 07:03, Joe Gordon wrote: > > Before going any further, I am proposing something to make it easier for > the > > developer community to keep track of what other projects are working on. > I > > am not proposing anything to

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

On 5 May 2015 at 08:12, Monty Taylor wrote: > On 05/04/2015 03:53 PM, Robert Collins wrote: > I'm fine with that in principle - I tend to release personal libraries > pretty much as soon as something interesting hits them. I have no > personal fear of high release counts. > > I'm not sure I 100%

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

On 05/04/2015 03:53 PM, Robert Collins wrote: > Hi, I'd like to talk about how often we can and should release pbr, > and what criteria we should use for 1.0. > > tl;dr: release weekly [outside of organisation-wide-freezes], do a 1.0 > immediately. > > pbr, like all our libraries affects everythi

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

On 5 May 2015 at 08:04, Clark Boylan wrote: > > > On Mon, May 4, 2015, at 12:53 PM, Robert Collins wrote: > I don't understand what you mean by "zero real world testing of master". > We test that pbr can make sdists and install packages on every change to > master before merging those changes. Th

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

+1 to call the current master as 1.0 +1 to more frequent releases (not sure if it should be every monday though!) -- dims On Mon, May 4, 2015 at 3:53 PM, Robert Collins wrote: > Hi, I'd like to talk about how often we can and should release pbr, > and what criteria we should use for 1.0. > > tl;

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

On Mon, May 4, 2015, at 12:53 PM, Robert Collins wrote: > Hi, I'd like to talk about how often we can and should release pbr, > and what criteria we should use for 1.0. > > tl;dr: release weekly [outside of organisation-wide-freezes], do a 1.0 > immediately. > > pbr, like all our libraries affe

[openstack-dev] [neutron] Lightning Talks for the Design Summit

As most of you know, the Neutron team used one of it's design summit slots in Paris for Lightning Talks. The format was so successful we decided to replicate this again in Vancouver. Thanks to those who submitted ideas. We ended up with seven Lightning Talk submissions, which means all seven were a

[openstack-dev] [pbr] regular releases, and path to 1.0

Hi, I'd like to talk about how often we can and should release pbr, and what criteria we should use for 1.0. tl;dr: release weekly [outside of organisation-wide-freezes], do a 1.0 immediately. pbr, like all our libraries affects everything when its released, but unlike everything else in oslo, it

Re: [openstack-dev] [nova-scheduler] Scheduler sub-group (gantt) meeting 5/5

Le 04/05/2015 20:15, Dugger, Donald D a écrit : I will not be able to make the meeting tomorrow but the IRC channel will be available for anyone who wants to get together. For an agenda I would suggest: 1) Liberty specs (tracking page - https://wiki.openstack.org/wiki/Gantt/liberty

Re: [openstack-dev] [all] cross project communication: periodic developer newsletter?

On 5 May 2015 at 07:03, Joe Gordon wrote: > Before going any further, I am proposing something to make it easier for the > developer community to keep track of what other projects are working on. I > am not proposing anything to directly help operators or users, that is a > separate problem space.

Re: [openstack-dev] [all] cross project communication: periodic developer newsletter?

This is a really nice idea. I feel the same, that we can offload some of the work from the liaisons and reduce the number of syncs that need to happen. This can be a good source of asynchronous communication however, I still feel that we need to keep a good balance of both. Also, I like the pr

[openstack-dev] [Glance] Next weekly meeting cancelled.

Hi all, In the event of a conflict with Glance virtual mini-summit-first-session [1] this Thursday May 7th UTC 1400 onwards, we are cancelling the weekly meeting. Please look for updates on the next meeting in the weekly meeting etherpad [2]. [1] https://etherpad.openstack.org/p/liberty-glance-

[openstack-dev] [all] cross project communication: periodic developer newsletter?

Before going any further, I am proposing something to make it easier for the developer community to keep track of what other projects are working on. I am not proposing anything to directly help operators or users, that is a separate problem space. In Mark McClain's TC candidacy email he brought

Re: [openstack-dev] Help: help resolve Depends-On for review

On Mon, May 04, 2015 at 10:05:03PM +0800, Yu Xing YX Wang wrote: > > Hi, > > I have a review(https://review.openstack.org/#/c/178561/) which is depend > on another review(https://review.openstack.org/#/c/178546/) > This Depends-On makes the first review's build failure. who can help me > resolve

[openstack-dev] [oslo][release] oslo.middleware 1.2.0

We are overjoyed to announce the release of: oslo.middleware 1.2.0: Oslo Middleware library For more details, please see the git log history below and: http://launchpad.net/oslo.middleware/+milestone/1.2.0 Please report issues through launchpad: http://bugs.launchpad.net/oslo.middlewar

[openstack-dev] [nova-scheduler] Scheduler sub-group (gantt) meeting 5/5

I will not be able to make the meeting tomorrow but the IRC channel will be available for anyone who wants to get together. For an agenda I would suggest: 1) Liberty specs (tracking page - https://wiki.openstack.org/wiki/Gantt/liberty ) 2) Vancouver design summit - more thoughts? 3) Opens -

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

On 05/04/2015 01:11 PM, Doug Hellmann wrote: > Excerpts from Maish Saidel-Keesing's message of 2015-05-04 17:46:21 +0300: >> On 05/04/15 17:07, Anita Kuno wrote: >>> I'd like to go back to the beginning to clarify something. >>> >>> On 04/29/2015 02:34 PM, Adam Lawson wrote: So I started reply

[openstack-dev] [Neutron][IPAM] Do we need migrate script for neutron IPAM now?

Hi, During fixing failures in db_base_plugin_v2.py with new IPAM[1] I faced to check-grenade-dsvm-neutron failures[2]. check-grenade-dsvm-neutron installs stable/kilo, creates networks/subnets and upgrades to patched master. So it validates that migrations passes fine and installation is works fin

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

So Thierry I agree. Developers are required to make it happen. I would say however that acknowledging the importance of developer contributions and selecting leadership from the development community is really half the battle as it's pretty rare to see project teams led and governed by only develop

Re: [openstack-dev] [swift] Go! Swift!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/04/2015 11:42 AM, Flavio Percoco wrote: >> Using something different isn't innovating. >> >> Finding a way to do something significantly better is >> innovating. > > FWIW, I didn't say using something different is innovating. It's > what you

[openstack-dev] [puppet] Introducing puppet-swift support for dedicated replication networks in swift.

Hello puppet-openstack, I am writing to introduce and explain my motivation behind https://review.openstack.org/#/c/177037/ Additionally I am looking for code review to help land this feature. I work on the openstack team at TWC. Recently we have made a move away from another product to manage

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

Excerpts from Maish Saidel-Keesing's message of 2015-05-04 17:46:21 +0300: > On 05/04/15 17:07, Anita Kuno wrote: > > I'd like to go back to the beginning to clarify something. > > > > On 04/29/2015 02:34 PM, Adam Lawson wrote: > >> So I started replying to Doug's email in a different thread but di

Re: [openstack-dev] [oslo][heat] Versioned objects backporting

In the discussion of N nodes in version V, needing to get upgraded to V+1, I do not see the issue of loss of HA. These N nodes are the servers. The clients are the ones still at version V. Does it not make sense to upgrade all the servers to V+1. (need to cross check against database that all serv

Re: [openstack-dev] [Neutron][LBaaS] Clarification required

Thanks Brandon for clearing the confusion. On Mon, May 4, 2015 at 9:52 AM, Brandon Logan wrote: > Hi Madhu,​ > > You won't see any pool details from a GET of a loadbalancer. For every > entity, you'll only be shown minor information from their parent (if one > exists) and their children (if an

Re: [openstack-dev] [Neutron][LBaaS] Clarification required

Hi Madhu,? You won't see any pool details from a GET of a loadbalancer. For every entity, you'll only be shown minor information from their parent (if one exists) and their children (if any exist). We may one day have a call to just show everything under a loadbalancer, but thats not there ye

Re: [openstack-dev] [neutron][lbaas][tempest] Data-driven testing (DDT) samples

Thanks Salvatore and Tom for your response. Yes, we were able to write data driven tests in two ways: (1) using ddt package - needs to be installed separately and invoke the module when writing the tests (2) using testscenarios package - this package is already installed and being used in neutron

Re: [openstack-dev] [swift] Go! Swift!

On 04/05/15 11:33 -0500, Ed Leafe wrote: On May 4, 2015, at 7:26 AM, Flavio Percoco wrote: TBH, I'm a bit torn. I'm always cheering for innovation, for using the right tool, etc, but I also agree with Monty, the linked post and some of the arguments that have been made in this thread. Using

[openstack-dev] [neutron]Anyone looking at support for VLAN-aware VMs in Liberty?

VLAN-transparent or VLAN-trunking networks have landed in Kilo, but I don't see any work on VLAN-aware VMs for Liberty. There is a blueprint[1] and specs[2] which was deferred from Kilo - is this something anyone is looking at as a Liberty candidate? I looked but didn't find any recent work - is

Re: [openstack-dev] [swift] Go! Swift!

On May 4, 2015, at 7:26 AM, Flavio Percoco wrote: > TBH, I'm a bit torn. I'm always cheering for innovation, for using the > right tool, etc, but I also agree with Monty, the linked post and some > of the arguments that have been made in this thread. Using something different isn't innovating.

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

Maish Saidel-Keesing wrote: > A three point triangle. I like the idea! Anita I assume that you are > talking about the TC[3], the board [1] and the user committee [2]. > > I honestly do not see this at the moment as an equally weighted triangle. > Should they be? Perhaps not, maybe yes. > > It co

Re: [openstack-dev] [nova] What happened with the "Hyper-V generation 2 VMs" spec?

On 5/4/2015 11:12 AM, Alessandro Pilotti wrote: Hi Matt, We originally proposed a Juno spec for this blueprint, but it got postponed to Kilo where it has been approved without a spec together with other hypervisor specific blueprints (the so called “trivial” case). The BP itself is complete

Re: [openstack-dev] [TC][Keystone] Rehashing the Pecan/Falcon/other WSGI debate

On 02/05/15 12:02 -0700, Morgan Fainberg wrote: On May 2, 2015, at 10:28, Monty Taylor wrote: On 05/01/2015 09:16 PM, Jamie Lennox wrote: Hi all, At around the time Barbican was applying for incubation there was a discussion about "supported" WSGI frameworks. From memory the decision at th

Re: [openstack-dev] [nova] What happened with the "Hyper-V generation 2 VMs" spec?

Hi Matt, We originally proposed a Juno spec for this blueprint, but it got postponed to Kilo where it has been approved without a spec together with other hypervisor specific blueprints (the so called “trivial” case). The BP itself is completed and marked accordingly on launchpad. Patches ref

Re: [openstack-dev] [neutron][vpnaas] On-demand VPNaaS IRC meeting

Re: https://wiki.openstack.org/wiki/Meetings/VPNaaS On Mon, May 4, 2015 at 12:03 PM Paul Michali wrote: > Since it has been a while, I decided to plan for a VPN meeting in our time > slot of Tuesday, 1600 UTC, for tomorrow the 5th of May. > > Please join in! > > Paul Michali (pc_m) > __

[openstack-dev] [neutron][vpnaas] On-demand VPNaaS IRC meeting

Since it has been a while, I decided to plan for a VPN meeting in our time slot of Tuesday, 1600 UTC, for tomorrow the 5th of May. Please join in! Paul Michali (pc_m) __ OpenStack Development Mailing List (not for usage quest

[openstack-dev] [nova] What happened with the "Hyper-V generation 2 VMs" spec?

This spec was never approved [1] but the code was merged in Kilo [2]. The blueprint is marked complete in launchpad [3] and it's referenced as a new feature in the hyper-v driver in the kilo release notes [4], but there is no spec published for consumers that detail the feature [5]. Also, the

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

On 05/04/2015 10:46 AM, Maish Saidel-Keesing wrote: > On 05/04/15 17:07, Anita Kuno wrote: >> I'd like to go back to the beginning to clarify something. >> >> On 04/29/2015 02:34 PM, Adam Lawson wrote: >>> So I started replying to Doug's email in a different thread but >>> didn't want >>> to hi-jac

Re: [openstack-dev] Mellanox request for permission for Nova CI

Thanks Matt, We will start Nova non-voting commenting. Lenny Verkhovsky SW Engineer, Mellanox Technologies www.mellanox.com Office:+972 74 712 9244 Mobile:  +972 54 554 0233 Fax:+972 72 257 9400 -Original Message- From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] S

Re: [openstack-dev] [swift] Go! Swift!

> On May 4, 2015, at 5:26 AM, Flavio Percoco wrote: > > On 04/05/15 12:17 +0200, Thierry Carrez wrote: >> Monty Taylor wrote: >>> On 04/30/2015 08:06 PM, John Dickinson wrote: >> What advantages does a compiled-language object server bring, >> and do they outweigh the costs of using a di

Re: [openstack-dev] Mellanox request for permission for Nova CI

On 5/3/2015 10:32 AM, Lenny Verkhovsky wrote: Hi Dan and the team, Here you can see full logs and tempest.conf http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_PORT_20150503_1854/ ( suspend-resume test is skipped and we are checking this issue ) Except of running Tempest A

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

On 05/04/15 17:07, Anita Kuno wrote: I'd like to go back to the beginning to clarify something. On 04/29/2015 02:34 PM, Adam Lawson wrote: So I started replying to Doug's email in a different thread but didn't want to hi-jack that so I figured I'd present my question as a more general question

Re: [openstack-dev] [cinder] Is there any way to put the driver backend error message to the horizon

Hey Erlon, The summit etherpad is here: https://etherpad.openstack.org/p/liberty-cinder-async-reporting It links to what we discussed in Paris. I will be filling it out this week. Also note, I have submitted this topic for a cross-project session: https://docs.google.com/spreadsheets/d/1vCTZBJKCM

Re: [openstack-dev] [neutron] replace external ip monitor

On 05/04/2015 02:58 PM, Assaf Muller wrote: errata, should be read as: … also has more than 200 functional tests in the regression testing cycle. pardonnez-moi, multiple editions of the mail sometimes lead to mistakes. -- Peter V. Saveliev _

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

I'd like to go back to the beginning to clarify something. On 04/29/2015 02:34 PM, Adam Lawson wrote: > So I started replying to Doug's email in a different thread but didn't want > to hi-jack that so I figured I'd present my question as a more general > question about how voting is handled for th

Re: [openstack-dev] [neutron] replace external ip monitor

On 05/04/2015 02:58 PM, Assaf Muller wrote: How's packaging looking on all supported platforms? It is packaged already for Fedora, RHEL, Debian, Ubuntu, Gentoo as soon as I know. Maybe for some other platforms. Pypi is provided as well. On a related note, ip_monitor.py is 87 lines of co

[openstack-dev] Help: help resolve Depends-On for review

Hi, I have a review(https://review.openstack.org/#/c/178561/) which is depend on another review(https://review.openstack.org/#/c/178546/) This Depends-On makes the first review's build failure. who can help me resolve it? fixes Bug1448217 Closes-Bug: 1448217 Depends-On: I86bf157f1bdb44f5fc579dc5

Re: [openstack-dev] os-ansible-deplpoyment has released Kilo

Hey Dani, Are you looking for support for Ironic for baremetal provisioning or for deployments on baremetal without the use of LXC containers? — Kevin > On May 3, 2015, at 06:45, Daniel Comnea wrote: > > Great job Kevin & co !! > > Are there any plans in supporting configure the baremetal a

Re: [openstack-dev] [neutron] replace external ip monitor

On 05/04/2015 03:25 PM, Miguel Ángel Ajo wrote: Does the library require root privileges to work for the operations you’re planning to do? Nope. Only the network stack changes need CAP_NET_ADMIN (add/del address, interface, route, traffic queue etc), and netns operations need the root acce

Re: [openstack-dev] [neutron] replace external ip monitor

Does the library require root privileges to work for the operations you’re planning to do? That would be a stopper, since all the agents run unprivileged, and all the operations are filtered by the oslo root wrap daemon or cmdline tool. Best, Miguel Ángel. Miguel Ángel Ajo On Monday, 4 de May

Re: [openstack-dev] [neutron] replace external ip monitor

. - Original Message - > … > > Hello. > > I would like to discuss the possibility to replace external ip monitor > in the neutron code [1] with an internal native Python code [2] > > The issues of the current implementation: > * an external process management > * text output parsing (po

[openstack-dev] [all] Sign up for oslo liaisons for liberty cycle

[ re-sending an almost identical email from Doug sent just before kilo cycle :) ] The Oslo team is responsible for managing code shared between projects. There are a LOT more projects than Oslo team members, so we created the liaison program at the beginning of the Juno cycle, asking each team tha

Re: [openstack-dev] [SOLVED] [Nova] gate-nova-python27 failure

We actually isolated from requests a little more in this review instead - https://review.openstack.org/#/c/179757/ -Sean On 05/04/2015 06:23 AM, Deepak Shetty wrote: > https://bugs.launchpad.net/nova/+bug/1451389 and the associated bugfix @ > https://review.openstack.org/179746 should sol

[openstack-dev] [puppet] Weekly meeting #34

Hi, Tomorrow is our weekly meeting. Please look at the agenda [1]. Feel free to bring new topics and reviews/bugs if needed. Also, if you had any action, make sure you can give a status during the meeting or in the etherpad directly. See you tomorrow, [1] https://etherpad.openstack.org/p/puppet

[openstack-dev] [neutron] replace external ip monitor

… Hello. I would like to discuss the possibility to replace external ip monitor in the neutron code [1] with an internal native Python code [2] The issues of the current implementation: * an external process management * text output parsing (possibly buffered) The proposed library: * pure Py

Re: [openstack-dev] [swift] Go! Swift!

On 04/05/15 12:17 +0200, Thierry Carrez wrote: Monty Taylor wrote: On 04/30/2015 08:06 PM, John Dickinson wrote: What advantages does a compiled-language object server bring, and do they outweigh the costs of using a different language? Of course, there are a ton of things we need to explore o

Re: [openstack-dev] [swift] Go! Swift!

On 30/04/15 10:54 -0700, Clint Byrum wrote: * +1 for compiled languages that are less-daunting than say C++, but still help find problems early. Anybody up for a Rust version too? ;-) /me is always up for some Rust -- @flaper87 Flavio Percoco pgpe5UOvbPWsd.pgp Description: PGP signature ___

Re: [openstack-dev] [Neutron] _get_subnet() in OpenContrail tests results in port deletion

Hi Kevin, Thanks for your answer, that is what I was looking for! I'll check with you in irc to decide which workaround is better: 1. Mocking NeutronDbSubnet fetch_subnet for opencontrail tests. 2. Using session.query() directly in NeutronDbSubnet fetch_subnet. - Pavel Bondar On 30.04.2015 22:46

Re: [openstack-dev] [oslo][heat] Versioned objects backporting

W dniu 5/4/2015 o 11:50 AM, Angus Salkeld pisze:> On Mon, May 4, 2015 at 6:33 PM, Jastrzebski, Michal > mailto:michal.jastrzeb...@intel.com>> wrote: > > W dniu 5/4/2015 o 8:21 AM, Angus Salkeld pisze:> On Thu, Apr 30, > 2015 at 9:25 PM, Jastrzebski, Michal > >

  1   2   >