Re: [openstack-dev] [nova] [api] Nova currently handles list with limit=0 quite different for different objects.

Hi, Alex, Thanks for the information, I was unable to join the conference yesterday. Then lets get the dicision done before fix it. BR, Zheng On Wed, Sep 23, 2015 at 12:56 PM, Alex Xu wrote: > Hi, Zhengyu, > > We discussed this in yesterday Nova API meeting. We think it should get > consisten

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Hi Russell, Is there any material to explain how OVN parent port work? Thanks, Tony -Original Message- From: WANG, Ming Hao (Tony T) Sent: Wednesday, September 23, 2015 10:02 AM To: OpenStack Development Mailing List (not for usage questions) Subject: RE: [openstack-dev] [neutron] Does

Re: [openstack-dev] [nova] [api] Nova currently handles list with limit=0 quite different for different objects.

Hi, Zhengyu, We discussed this in yesterday Nova API meeting. We think it should get consistent in API-WG. And there already have patch for pagination guideline https://review.openstack.org/190743 , and there also have some discussion on limits. So we are

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

Chris Friesen wrote: On 09/22/2015 05:48 PM, Joshua Harlow wrote: A present: >>> import contextlib >>> import os >>> >>> @contextlib.contextmanager ... def synced_file(path, mode='wb'): ... with open(path, mode) as fh: ... yield fh ... os.fdatasync(fh.fileno()) ... >>> with synced_file("/tmp/b.

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

What you think about separating both of them with the name as Doug mentioned. In future if we want to get rid of the v1 we can just remove that namespace. Everything will be clean. Thanks Banashankar On Tue, Sep 22, 2015 at 6:01 PM, Fox, Kevin M wrote: > As I understand it, loadbalancer in v2

[openstack-dev] [magnum] Unit Tests Objects from Bay

Hi All, As discussed in today's weekly meeting sending the list of Unit Tests that need to be modified as part of "Objects from Bay" feature[1]. Right now after the switch to k8s v1 api yesterday, the changes for Replication Controller are up [2] will update the patches for Service object and Pod

[openstack-dev] [nova] About availability zones

Hi, all I have a question about availability zones when performing live-migration. Currently, when performing live-migration the AZ of the instance didn't update. In usecase like this: Instance_1 is in host1 which is in az1, we live-migrate it to host2 (provide host2 in API request) which is in a

Re: [openstack-dev] [neutron] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Russell, Thanks for your info. If I want to assign multiple interfaces to a container on different neutron networks(for example, netA and netB), is it mandatory to let the VM hosting containers have network interfaces in netA and netB, and ovn will help to direct the container traffic to its co

Re: [openstack-dev] [nova] [api] Nova currently handles list with limit=0 quite different for different objects.

Any thoughts on this? On Mon, Sep 14, 2015 at 11:53 AM, Zhenyu Zheng wrote: > Hi, Thanks for your reply, after check again and I agree with you. I think > we should come up with a conclusion about how we should treat this limit=0 > across nova. And that's also why I sent out this mail. I will re

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

As I understand it, loadbalancer in v2 is more like pool was in v1. Can we make it such that if you are using the loadbalancer resource and have the mandatory v2 properties that it tries to use v2 api, otherwise its a v1 resource? PoolMember should be ok being the same. It just needs to call v1

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

So for the API v1s api is of the structure: /lb/(vip|pool|member|health_monitor) V2s is: /lbaas/(loadbalancer|listener|pool|healthmonitor) member is a child of pool, so it would go down one level. The only difference is the lb for v1 and lbaas for v2. Not sure if that is enough of a different.

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

I do like Doug's suggestion of namespace change. One day lbaas will no longer be an extension of neutron (at least that is my hope and it seems to be going in that direction), and thus the only reason to be considered part of neutron is just a logical grouping of networking services. Cutting the

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

On Tue, Sep 22, 2015 at 6:17 PM, John Griffith wrote: > > > On Tue, Sep 22, 2015 at 5:48 PM, Joshua Harlow > wrote: > >> A present: >> >> >>> import contextlib >> >>> import os >> >>> >> >>> @contextlib.contextmanager >> ... def synced_file(path, mode='wb'): >> ... with open(path, mode) as fh:

Re: [openstack-dev] [puppet] service default value functions

Alex Schultz wrote: > Hey puppet folks, > > Based on the meeting yesterday[0], I had proposed creating a parser > function called is_service_default[1] to validate if a variable matched > our agreed upon value of ''. This got me thinking > about how can we maybe not use the arbitrary string throu

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

On Tue, Sep 22, 2015 at 5:48 PM, Joshua Harlow wrote: > A present: > > >>> import contextlib > >>> import os > >>> > >>> @contextlib.contextmanager > ... def synced_file(path, mode='wb'): > ... with open(path, mode) as fh: > ... yield fh > ... os.fdatasync(fh.fileno()) > ... > >>> wit

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Ugg, That's news to me. :/ Hopefully there's a way around it. A different namespace sounds reasonable as a workaround. Also consider the use case where you have a newer heat then neutron. During upgrade there may be a time when we very well may want to support one different then the other. So t

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

On 09/22/2015 05:48 PM, Joshua Harlow wrote: A present: >>> import contextlib >>> import os >>> >>> @contextlib.contextmanager ... def synced_file(path, mode='wb'): ... with open(path, mode) as fh: ... yield fh ... os.fdatasync(fh.fileno()) ... >>> with synced_file("/tmp/b.txt")

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

But whatever it is, I think we can't run the current heat template as it is for v2, those things must be ported no matter what. So I think our main concern here is coexistence of v1 and v2 heat support. Please correct me if I am wrong. Thanks Banashankar On Tue, Sep 22, 2015 at 4:53 PM, Doug W

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Resource I mean, the resource type as highlighted. description: A simple lb pool test heat_template_version: '2015-04-30' resources: my_listener: type: OS::Neutron::*ListenerV2* properties: protocol_port: 88 protocol: HTTP loadbalancer_id: e3e0b1d2-12b2-4855-a5cb-6faf121

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

The other option would be to change the namespace. (Os::Lbaas instead of Os::Neutron). The neutron CLI does something similar with neutron-lb-* versus neutron-lbaas-*, e.g. One wrinkle with heat supporting both is that neutron doesn’t support both running at the same time, which certainly hur

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Thats the problem. :/ I can't think of a way to have them coexist without: breaking old templates, including v2 in the name, or having a flag on the resource saying the version is v2. And as an app developer I'd rather not have my existing templates break. I haven't compared the api's at all, b

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Forgive my ignorance on this, but by resources are we talking about API resources? If so I would hate V2 to be in the names because backwards compatibility means keeping that around. If they're not API resources, then if we named appended the resources with V2 right now, will we be able to remove

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

A present: >>> import contextlib >>> import os >>> >>> @contextlib.contextmanager ... def synced_file(path, mode='wb'): ... with open(path, mode) as fh: ... yield fh ... os.fdatasync(fh.fileno()) ... >>> with synced_file("/tmp/b.txt") as fh: ...fh.write("b") ... Have fun :-P -Jo

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Ok, sounds good. So now the question is how should we name the new V2 resources ? Thanks Banashankar On Tue, Sep 22, 2015 at 4:33 PM, Fox, Kevin M wrote: > Yes, hence the need to support the v2 resources as seperate things. Then I > can rewrite the templates to include the new resources rathe

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Yes, hence the need to support the v2 resources as seperate things. Then I can rewrite the templates to include the new resources rather then the old resources as appropriate. IE, it will be a porting effort to rewrite them. Then do a heat update on the stack to migrate it from lbv1 to lbv2. Sin

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

But I think, V2 has introduced some new components and whole association of the resources with each other is changed, we should be still able to do what Kevin has mentioned ? Thanks Banashankar On Tue, Sep 22, 2015 at 3:39 PM, Fox, Kevin M wrote: > There needs to be a way to have both v1 and v

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On Tue, Sep 22, 2015 at 05:30:36PM -0400, Mathieu Gagné wrote: > On 2015-09-22 4:52 PM, Sean Dague wrote: > > On 09/22/2015 03:16 PM, Mathieu Gagné wrote: > >> > >> The oslo_middleware.ssl middleware looks to offer little overhead and > >> offer the maximum flexibility. I appreciate the wish to use

Re: [openstack-dev] [neutron][lbaas] Proposing Michael Johnson for neutron-lbaas core team

Thank you team. I look forward to contributing to neutron-LBaaS! Michael On Mon, Sep 21, 2015 at 4:27 PM, wrote: > Congrats Michael. It is well deserved > > Susanne > > Sent from my iPhone > > On Sep 21, 2015, at 6:48 PM, Doug Wiegley > wrote: > > HI all, > > Since all cores have responded, t

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

On 23 September 2015 at 09:52, Chris Friesen wrote: > Hi, > > I recently had an issue with one file out of a dozen or so in > "/opt/cgcs/cinder/data/volumes/" being present but of size zero. I'm > running stable/kilo if it makes a difference. > > Looking at the code in volume.targets.tgt.TgtAdm.c

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

So if that's the case, I think we can just remove the old V1 resources implementation and just have support for the V2 as. OS::Neutron::LoadBalancer OS::Neutron::Listener OS::Neutron::Pool OS::Neutron::PoolMember OS::Neutron::HealthMonitor Need input of Heat experts :) . Thanks Banashankar On

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

There needs to be a way to have both v1 and v2 supported in one engine Say I have templates that use v1 already in existence (I do), and I want to be able to heat stack update on them one at a time to v2. This will replace the v1 lb with v2, migrating the floating ip from the v1 lb to the v2

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Well I'd hate to have the V2 postfix on it because V1 will be deprecated and removed, which means the V2 being there would be lame. Is there any kind of precedent set for for how to handle this? Thanks, Brandon On Tue, 2015-09-22 at 14:49 -0700, Banashankar KV wrote: > So are we thinking of makin

Re: [openstack-dev] New PyCharm License

On 2015-09-22 17:43:28 + (+), Andrew Melton wrote: [...] > I've had to invalidate the old link. If you still need a PyCharm > License, please reach out to me with your launchpad-id and I'll > get you the updated link. [...] Further, please reply to Andrew directly, not to this mailing list

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

So are we thinking of making it as ? OS::Neutron::LoadBalancerV2 OS::Neutron::ListenerV2 OS::Neutron::PoolV2 OS::Neutron::PoolMemberV2 OS::Neutron::HealthMonitorV2 and add all those into the loadbalancer.py of heat engine ? Thanks Banashankar On Tue, Sep 22, 2015 at 12:52 PM, Sergey Kraynev wr

[openstack-dev] [cinder] should we use fsync when writing iscsi config file?

Hi, I recently had an issue with one file out of a dozen or so in "/opt/cgcs/cinder/data/volumes/" being present but of size zero. I'm running stable/kilo if it makes a difference. Looking at the code in volume.targets.tgt.TgtAdm.create_iscsi_target(), I'm wondering if we should do a fsync(

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 2015-09-22 4:52 PM, Sean Dague wrote: > On 09/22/2015 03:16 PM, Mathieu Gagné wrote: >> >> The oslo_middleware.ssl middleware looks to offer little overhead and >> offer the maximum flexibility. I appreciate the wish to use the Keystone >> catalog but I don't feel this is the right answer. >> >>

Re: [openstack-dev] [releases] semver and dependency changes

Excerpts from Robert Collins's message of 2015-09-23 06:40:19 +1200: > On 23 September 2015 at 00:43, Doug Hellmann wrote: > > Excerpts from Robert Collins's message of 2015-09-22 15:16:26 +1200: > >> Currently we don't provide specific guidance on what should happen > >> when the only changes in

[openstack-dev] [Keystone] [Manila] Liberty RC1 available

Hello everyone, Manila and Keystone are the first projects to produce a release candidate for the end of the Liberty cycle! The RC1 tarballs, as well as a list of last-minute features and fixed bugs since liberty-1 are available at: https://launchpad.net/manila/liberty/liberty-rc1 https://launchp

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 09/22/2015 03:16 PM, Mathieu Gagné wrote: > On 2015-09-22 1:46 PM, Sean Dague wrote: >> On 09/22/2015 12:12 PM, Mathieu Gagné wrote: >>> On 2015-09-22 7:00 AM, Sean Dague wrote: My feeling on this one is that we've got this thing in OpenStack... the Service Catalog. It definitivel

Re: [openstack-dev] [Horizon] [Cinder] [Keystone] Showing Cinder quotas for non-admin users in Horizon

If I understand correctly, the issue has been properly fixed with the Ivan's patch [1]. Thanks, Ivan! [1] https://review.openstack.org/#/c/225891/ On Wed, Sep 16, 2015 at 2:53 PM Ivan Kolodyazhny wrote: > Hi Timur, > > To get quotas we need to retrieve project information from the > Keystone.

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Brandon. As I understand we v1 and v2 have differences also in list of objects and also in relationships between them. So I don't think that it will be easy to upgrade old resources (unfortunately). I'd agree with second Kevin's suggestion about implementation new resources in this case. I see, t

Re: [openstack-dev] [release][ptl][all] creating stable/liberty branches for non-oslo libraries today

Excerpts from Doug Hellmann's message of 2015-09-21 16:02:50 -0400: > Excerpts from Doug Hellmann's message of 2015-09-21 09:44:06 -0400: > > > > All, > > > > We are doing final releases, contraints updates, and creating > > stable/liberty branches for all of the non-Oslo libraries (clients > > a

Re: [openstack-dev] [networking-ovn] Neutron-DVR feature on OVN/L3

On 09/22/2015 02:35 PM, Carl Baldwin wrote: > On Tue, Sep 22, 2015 at 10:42 AM, Russell Bryant wrote: >> The Neutron L3 agent is only used with networking-ovn temporarily while >> we work through the L3 design and implementation in OVN itself. OVN >> will not use the L3 agent (or DVR) quite soon.

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

There is some overlap, but there was some incompatible differences when we started designing v2. I'm sure the same issues will arise this time around so new resources sounds like the path to go. However, I do not know much about Heat and the resources so I'm speaking on a very uneducated level he

Re: [openstack-dev] [Neutron] ImportError: cannot import name access

Ran in this same situation a week or two ago. I updated to the latest code from the icehouse-eol branch and then pinned the client libraries to an earlier release level. After that, tox ran fine. The version levels that I pinned are: python-neutronclient==2.3.4 python-keystoneclient==0.

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 2015-09-22 1:46 PM, Sean Dague wrote: > On 09/22/2015 12:12 PM, Mathieu Gagné wrote: >> On 2015-09-22 7:00 AM, Sean Dague wrote: >>> >>> My feeling on this one is that we've got this thing in OpenStack... the >>> Service Catalog. It definitively tells the world what the service >>> addresses are

Re: [openstack-dev] [murano] [app-catalog] versions for murano assets in the catalog

Hi Chris, concern regarding assets versioning in Community App Catalog indeed affects Murano because we are constantly improving our language and adding new features, e.g. we added ability to select existing Neutron network for particular application in Liberty and if user wants to use this featur

[openstack-dev] [Neutron] ImportError: cannot import name access

Hi Folks, I'm trying to run using tox some unit tests on the latest Neutron stable/icehouse, and things pretty much grind to a halt with a series of errors arounf "cannot import name access: File "/Users/wdec/Downloads/openstack/neutron/.tox/py27/lib/python2.7/site-packages/keystoneclient/__ini

Re: [openstack-dev] [releases] semver and dependency changes

On 23 September 2015 at 02:03, Thierry Carrez wrote: > Robert Collins wrote: >> [...] >> So, one answer we can use is "The version impact of a requirements >> change is never less than the largest version change in the change." >> That is: >> nothing -> a requirement -> major version change > > Th

Re: [openstack-dev] [releases] semver and dependency changes

On 23 September 2015 at 02:48, Jeremy Stanley wrote: > On 2015-09-22 15:16:26 +1200 (+1200), Robert Collins wrote: > [...] >> 'Is this requirements change an API break' or 'is this requirements >> change feature work' or 'is this requirements change a bugfix'. > [...] > > It may also be worth cons

Re: [openstack-dev] [releases] semver and dependency changes

On 23 September 2015 at 00:43, Doug Hellmann wrote: > Excerpts from Robert Collins's message of 2015-09-22 15:16:26 +1200: >> Currently we don't provide specific guidance on what should happen >> when the only changes in a project are dependency changes and a >> release is made. >> >> The releases

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

We're using the v1 resources... If the v2 ones are compatible and can seamlessly upgrade, great Otherwise, make new ones please. Thanks, Kevin From: Banashankar KV [banvee...@gmail.com] Sent: Tuesday, September 22, 2015 10:07 AM To: OpenStack Development Mailing

Re: [openstack-dev] [networking-ovn] Neutron-DVR feature on OVN/L3

On Tue, Sep 22, 2015 at 10:42 AM, Russell Bryant wrote: > The Neutron L3 agent is only used with networking-ovn temporarily while > we work through the L3 design and implementation in OVN itself. OVN > will not use the L3 agent (or DVR) quite soon. Some initial L3 design > notes are being discus

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 09/22/2015 12:12 PM, Mathieu Gagné wrote: > On 2015-09-22 7:00 AM, Sean Dague wrote: >> >> My feeling on this one is that we've got this thing in OpenStack... the >> Service Catalog. It definitively tells the world what the service >> addresses are. >> >> We should use that in the services thems

Re: [openstack-dev] New PyCharm License

Hey Devs, Reply-All strikes again... I've had to invalidate the old link. If you still need a PyCharm License, please reach out to me with your launchpad-id and I'll get you the updated link. I'm also working on a WebStorm license. I'll let the list know when I have it. --Andrew __

Re: [openstack-dev] Patches coming for .coveragerc

It's the same number of patches. On 23 Sep 2015 4:42 am, "Matt Riedemann" wrote: > > > On 9/22/2015 4:59 AM, Alan Pevec wrote: > >> 2015-09-21 16:12 GMT+02:00 Monty Taylor : >> >>> We're running a script right now to submit a change to every project with >>> this change. The topic will be coverag

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 09/22/2015 11:34 AM, Ben Nemec wrote: > On 09/22/2015 06:00 AM, Sean Dague wrote: >> On 09/18/2015 02:30 PM, Ben Nemec wrote: >>> I've been dealing with this issue lately myself, so here's my two cents: >>> >>> It seems to me that solving this at the service level is actually kind >>> of wrong.

Re: [openstack-dev] [neutron] [floatingip] Selecting router for floatingip when subnet is connected to multiple routers

On Sep 21, 2015 9:21 AM, "Venkata Anil" wrote: > > Hi All > > I need your opinion on selecting router for floatingip when subnet is connected to multiple routers. > > When multiple routers connected to a subnet, vm on that subnet will only send packets destined for external network to the router w

Re: [openstack-dev] [Neutron] Port Forwarding API

Interesting, I'll have a look. We should get this on the neutron drivers' agenda. The drivers team has been dormant for a couple of weeks but I'm sure it will pick up again very soon. Carl On Sep 20, 2015 12:28 AM, "Gal Sagie" wrote: > Hello All, > > I have sent a spec [1] to resume the work o

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Hi Brandon, Work in progress, but need some input on the way we want them, like replace the existing lbaasv1 or we still need to support them ? Thanks Banashankar On Tue, Sep 22, 2015 at 9:18 AM, Brandon Logan wrote: > Hi Banashankar, > I think it'd be great if you got this going. One of t

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Hi Banashankar, I think it'd be great if you got this going. One of those things we want to have and people ask for but has always gotten a lower priority due to the critical things needed. Thanks, Brandon On Mon, 2015-09-21 at 17:57 -0700, Banashankar KV wrote: > Hi All, > I was thinking of star

Re: [openstack-dev] [neutron] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 09/22/2015 08:08 AM, WANG, Ming Hao (Tony T) wrote: > Dear all, > > For neutron ovn plugin supports containers in one VM, My understanding is one > container can't be assigned two network interfaces in different neutron > networks. Is it right? > The reason: > 1. One host VM only has one netw

Re: [openstack-dev] [networking-ovn] Neutron-DVR feature on OVN/L3

On 09/21/2015 04:47 PM, Sisir Chowdhury wrote: > Hi All - > > I have some proposal regarding ovn-networking project within Open-Stack. > > #1. Making Neutron-DVR feature intelligent enough so that we can > completely remove Network Node(NN). > > Right now even with DVR, the egress

Re: [openstack-dev] Patches coming for .coveragerc

On 9/22/2015 4:59 AM, Alan Pevec wrote: 2015-09-21 16:12 GMT+02:00 Monty Taylor : We're running a script right now to submit a change to every project with this change. The topic will be coverage-v4 stable/kilo has uncapped coverage>=3.6 do we patch-spam it or cap coverage? stable/juno has c

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

On 09/21/2015 08:44 AM, Emilien Macchi wrote: > Hello! > > Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC > in #openstack-meeting-4: > > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150922 > > Feel free to add any a

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 2015-09-22 7:00 AM, Sean Dague wrote: > > My feeling on this one is that we've got this thing in OpenStack... the > Service Catalog. It definitively tells the world what the service > addresses are. > > We should use that in the services themselves to reflect back their > canonical addresses.

Re: [openstack-dev] [release][all]Release help needed - we are incompatible with ourselves

On 2015-09-22 12:19:47 + (+), Neil Jerram wrote: > FWIW - this email is tagged [all], and asks for help, but I don't > understand it. Even though I've been fairly heavily engaged with > OpenStack for more than a cycle now. [...] > So, please, if you really mean [all], say what you're sayin

Re: [openstack-dev] Patches coming for .coveragerc

On Tue, Sep 22, 2015, at 02:59 AM, Alan Pevec wrote: > 2015-09-21 16:12 GMT+02:00 Monty Taylor : > > We're running a script right now to submit a change to every project with > > this change. The topic will be coverage-v4 > > stable/kilo has uncapped coverage>=3.6 do we patch-spam it or cap > cove

Re: [openstack-dev] Patches coming for .coveragerc

On 2015-09-22 11:59:44 +0200 (+0200), Alan Pevec wrote: > stable/kilo has uncapped coverage>=3.6 do we patch-spam it or cap coverage? > stable/juno has coverage>=3.6,<=3.7.1 There's nothing wrong with updating it there, but unless we're actively running coverage jobs on those branches I'm not conv

Re: [openstack-dev] [nova] live migration in Mitaka

On Tue, Sep 22, 2015 at 09:29:46AM -0600, Chris Friesen wrote: > >>There is also work on post-copy migration in QEMU. Normally with live > >>migration, the guest doesn't start executing on the target host until > >>migration has transferred all data. There are many workloads where that > >>doesn't

Re: [openstack-dev] [nova] live migration in Mitaka

Apologies for the indirect quote, some of the earlier posts got deleted before I noticed the thread. On 09/21/2015 03:43 AM, Koniszewski, Pawel wrote: -Original Message- From: Daniel P. Berrange [mailto:berra...@redhat.com] There was a proposal to nova to allow the 'pause' operation

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 09/22/2015 06:00 AM, Sean Dague wrote: > On 09/18/2015 02:30 PM, Ben Nemec wrote: >> I've been dealing with this issue lately myself, so here's my two cents: >> >> It seems to me that solving this at the service level is actually kind >> of wrong. As you've discovered, that requires changes in

Re: [openstack-dev] [nova] live migration in Mitaka

On Tue, Sep 22, 2015 at 09:05:11AM -0600, Chris Friesen wrote: > On 09/21/2015 02:56 AM, Daniel P. Berrange wrote: > >On Fri, Sep 18, 2015 at 05:47:31PM +, Carlton, Paul (Cloud Services) > >wrote: > >>However the most significant impediment we encountered was customer > >>complaints about perf

Re: [openstack-dev] [nova] live migration in Mitaka

On 09/21/2015 02:56 AM, Daniel P. Berrange wrote: On Fri, Sep 18, 2015 at 05:47:31PM +, Carlton, Paul (Cloud Services) wrote: However the most significant impediment we encountered was customer complaints about performance of instances during migration. We did a little bit of work to identi

Re: [openstack-dev] [releases] semver and dependency changes

On 2015-09-22 15:16:26 +1200 (+1200), Robert Collins wrote: [...] > 'Is this requirements change an API break' or 'is this requirements > change feature work' or 'is this requirements change a bugfix'. [...] It may also be worth considering whether this logic only applies to increasing minimums (a

Re: [openstack-dev] [Large Deployments Team][Performance Team] New informal working group suggestion

To help kick off this topic, the Neutron team has been tracking some performance profiling in this etherpad. https://etherpad.openstack.org/p/router-scheduling-performance -- Sean M. Collins __ OpenStack Development Mailing

[openstack-dev] [Fuel][UI] Bower is gone

Hi folks, We used Bower to manage client-side dependencies of Fuel UI, but since today they are managed by NPM which is already used to manage server-side dependencies. This change reduces complexity of Fuel UI and is also a preparation for some important changes. For those who use fake mode for

Re: [openstack-dev] [releases] semver and dependency changes

Robert Collins wrote: > [...] > So, one answer we can use is "The version impact of a requirements > change is never less than the largest version change in the change." > That is: > nothing -> a requirement -> major version change That feels a bit too much. In a lot of cases, the added requiremen

Re: [openstack-dev] [Outreachy]New coordinator announcement and list of current applicants and mentors

On 21/09/15 20:31, Victoria Mart?nez de la Cruz wrote: Hi all, I'm glad to announce that Mahati Chamarthy (mahatic) will join the current coordination efforts for the Outreachy internships. Thanks Mahati! Also, I wanted to share this Etherpad [0]with you the current list of applicants and mento

Re: [openstack-dev] [Large Deployments Team][Performance Team] New informal working group suggestion

Thanks, Dina! For context to the rest of the LDT folks, Dina reached out to me about working on this under our umbrella for now. It made sense until we understand if it's a large enough thing to live as its own working group because most of us have various performance concerns too. So, like P

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

Hi Rich, I've got the hang of it. It boils down to this: for a property of a puppet resource to be taken into account as a key of the resource it has to be a parameter, not a property: For the code to work you change newproperty(:domain) do to newparam(:domain) do As a side note, the tes

[openstack-dev] Cross-Project meeting, Tue Sept 22nd, 21:00 UTC

Dear PTLs, cross-project liaisons and anyone else interested, We'll have a cross-project meeting today at 21:00 UTC, with the following agenda: * Review past action items * Team announcements (horizontal, vertical, diagonal) * Open discussion If you're from a horizontal team (Release management,

[openstack-dev] [Large Deployments Team][Performance Team] New informal working group suggestion

Hey, OpenStackers! I'm writing to propose to organise new informal team to work specifically on the OpenStack performance issues. This will be a sub team in already existing Large Deployments Team, and I suppose it will be a good idea to gather people interested in OpenStack performance in one roo

Re: [openstack-dev] [releases] semver and dependency changes

Excerpts from Robert Collins's message of 2015-09-22 15:16:26 +1200: > Currently we don't provide specific guidance on what should happen > when the only changes in a project are dependency changes and a > release is made. > > The releases team has been treating a dependency change as 'feature' >

Re: [openstack-dev] [release][all]Release help needed - we are incompatible with ourselves

Neil, The effort is to spread the knowledge and skills beyond the "small group of people who already understand all this" :) Let me explain a bit. working backwards from what we see. Most of us have seen the Proposal bot update reviews that get logged periodically that updates the requirements.t

Re: [openstack-dev] [neutron] Neutron debugging tool

There was a presentation on DON at the Vancouver summit. Here is the link: https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/don-diagnosing-ovs-in-neutron From: Salvatore Orlando [mailto:salv.orla...@gmail.com] Sent: Tuesday, September 22, 2015 3:51 AM To: OpenStack Deve

Re: [openstack-dev] [release][all]Release help needed - we are incompatible with ourselves

To most people who write on this list about requirements, constraints and gate deadlocks, not just Robert... FWIW - this email is tagged [all], and asks for help, but I don't understand it. Even though I've been fairly heavily engaged with OpenStack for more than a cycle now. Obviously we can't

[openstack-dev] [neutron] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Dear all, For neutron ovn plugin supports containers in one VM, My understanding is one container can't be assigned two network interfaces in different neutron networks. Is it right? The reason: 1. One host VM only has one network interface. 2. all the VLAN tags are stripped out when the packet

Re: [openstack-dev] [openstack-ansible] To NTP, or not to NTP, that is the question

On 22 September 2015 at 01:45, Major Hayden wrote: > On 09/21/2015 07:14 PM, Sergii Golovatiuk wrote: > > Are any chance to configure chrony instead of ntpd? It acts more > predictable on virtual environments. > > That's my plan, if I can find an upstream Ansible galaxy role to use. ;) > Now tha

[openstack-dev] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Dear all, For neutron ovn plugin supports containers in one VM, My understanding is one container can't be assigned two network interfaces in different neutron networks. Is it right? The reason: 1. One host VM only has one network interface. 2. all the VLAN tags are stripped out when the packet

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 09/18/2015 02:30 PM, Ben Nemec wrote: > I've been dealing with this issue lately myself, so here's my two cents: > > It seems to me that solving this at the service level is actually kind > of wrong. As you've discovered, that requires changes in a bunch of > different places to address what i

Re: [openstack-dev] Patches coming for .coveragerc

2015-09-21 16:12 GMT+02:00 Monty Taylor : > We're running a script right now to submit a change to every project with > this change. The topic will be coverage-v4 stable/kilo has uncapped coverage>=3.6 do we patch-spam it or cap coverage? stable/juno has coverage>=3.6,<=3.7.1 Cheers, Alan __

Re: [openstack-dev] [openstack-operators][tc][tags] Rally tags

As for me two ideal candidates for tags are "works-in-rally" and "covered-by-rally". Other sound ugly. But this two are meaningful and ingenious names. On Mon, Sep 21, 2015 at 11:13 PM, Boris Pavlovic wrote: > Thierry, > > Okay great I will propose patches. > > Best regards, > Boris Pavlovic >

Re: [openstack-dev] [nova] live migration in Mitaka

Hi all, > Please respond to this post if you have an interest in this and what you > would like to see done. Include anything you are already getting on with so > we get a clear picture. I have put a new spec about "allow more instance actions during the live migration" [0]. Please note that

Re: [openstack-dev] [neutron] What semantics are expected when booting a VM on an external network?

There is no guarantee that two separate external networks will have routing connectivity to each other. It seems like your (b) statement implies that. On Sep 19, 2015 3:12 PM, "Neil Jerram" wrote: > On 17/09/15 19:38, Kevin Benton wrote: > > router:external only affects the behavior of Neutron ro

Re: [openstack-dev] [neutron] What semantics are expected when booting a VM on an external network?

Great. I'll try to review as soon as possible since these will be big changes. On Sep 17, 2015 12:44 PM, "Carl Baldwin" wrote: > On Thu, Sep 17, 2015 at 10:26 AM, Kevin Benton wrote: > > Yes, the L2 semantics apply to the external network as well (at least > with > > ML2). > > This is true and s

Re: [openstack-dev] [neutron] Neutron debugging tool

Thanks Ganesh! I did not know about this tool. I also quite like the network visualization bits, though I wonder how practical that would be when one debugs very large deployments. I think it won't be a bad idea to list these tools in the networking guide or in neutron's devref, or both. Salvato

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Hi Ethan, Oh thats cool, I didn't see that BP. Sure we can work together on it. As there will be no support for LBaasV1 in Liberty and upcoming releases, I think we can stick to the first approach that you mentioned. But need to discuss whether to have the type named as OS::Neutron::[lb_elements]V

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Hi Banashankar, There's a BP for this https://blueprints.launchpad.net/heat/+spec/support-neutron-lb-v2-model-definition . And I plan to submit a spec for it but I haven't figure out how to implement it. Maybe we can work together with huangtianhua. There are two choices to implement it: 1. A