[openstack-dev] [Neuton][ml2][Manila] API to query segments used during port binding

Hi Neutron team, I am currently working on a feature for hierarchical port binding support in Manila [1] [2]. Just to give some context: In the current implementation Manila creates a neutron port but let it unbound (state DOWN). Therefore Manila uses the port create only retrieve an IP address an

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Hi Pengfei, It's expected that there's no port for 100.0.0.1 since what we attach to router are 100.0.0.2 and 100.0.0.3. Try to ping 10.0.2.1 in vm1 and to ping 10.0.1.1 in vm2 to see if you can get reply. There may be security group rules that prevent vm to be accessed. The check if all the pro

Re: [openstack-dev] Vlan Tenant network

Hi Pratti, yes, this is working! For Openvswitch ml2 driver just configure on the neutron server in the ml2 configuration file [1][2] [ml2] tenant_network_types = flat type_drivers = local, flat, vlan, gre, vxlan [ml2_type_vlan] network_vlan_ranges = physnet1:30:40 #where 30-40 is the range of

Re: [openstack-dev] [devstack] stack.sh keeps failing with RTNETLINK answers: Network is unreachable

Sean I do stack.sh, it aborts with this error then I do unstack.sh and that runs fine and try stack.sh again, it seems to fail every time! Paul Carlton Software Engineer Cloud Services Hewlett Packard Enterprise BUK03:T242 Longdown Avenue Stoke Gifford Bristol BS34 8QZ Mobile:+44 (0)7768

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

On Sat, Feb 27, 2016 at 08:12:25AM +1300, Robert Collins wrote: > On 27 February 2016 at 01:34, Thomas Bechtold wrote: > > On Fri, Feb 26, 2016 at 06:52:03AM -0500, Doug Hellmann wrote: > >> Excerpts from Neil Jerram's message of 2016-02-26 11:27:05 +: > >> > On 26/02/16 11:16, Neil Jerram wro

[openstack-dev] [all][i18n] Liaisons for I18n

Hello,Mitaka translation will start soon, from this week.In Mitaka translation, IBM full time translators will join thetranslation team and work with community translators.With their help, I18n team is able to cover more projects.So I need liaisons from dev projects who can help I18n team to workco

Re: [openstack-dev] [tricircle] playing tricircle with devstack under two-region configuration

Oh, I think out another reason for the problem. If you are using Vmware Vcenter, you need to enable "Promiscuous Mode" and set "MAC Address Changes" to "Accept". Here is a reference in Chinese: http://www.net130.com/CMS/Pub/special/special_virtual/special_virtual_js/2012_06_26_28741.htm BR Zhiyua

[openstack-dev] [mistral] Team meeting - 02/29/2016

Hi, This is a reminder that we’ll have a team meeting today at #openstack-meeting at 16.00 UTC. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Review M-3 BPs and bugs Define what else we need to squeeze into M-3 Open discussion Renat Akhmerov @ Miranti

Re: [openstack-dev] [TripleO] Show TripleO: A terminal dashboard

On 28 February 2016 at 22:41, Steve Baker wrote: > On 27/02/16 09:06, Ben Nemec wrote: > >> Interesting! So this could conceivably be another consumer of the API, >> right? A sort of CLI UI? >> >> On 02/25/2016 01:10 PM, Dougal Matthews wrote: >> >>> Hi all, >>> >>> Over the past couple of week

Re: [openstack-dev] [all] A proposal to separate the design summit

Honestly, it took me a while before having an opinion on that subject. Le 26/02/2016 18:08, Thierry Carrez a écrit : Thierry Carrez wrote: 1. "Two trips instead of one" There is a section of attendees which benefited from a single event: in-between people who do not generally go to any midcycl

Re: [openstack-dev] [all][i18n] Liaisons for I18n

Just noticed the previous mail is not in good format. Send again for your reading easily. Sorry for the inconveniency. --- Hello, Mitaka translation will start soon, from this week. In Mitaka translation, IBM full time translators will join the translation team and work with community translator

Re: [openstack-dev] [all] A proposal to separate the design summit

Tim Bell wrote: On 26/02/16 18:08, "Thierry Carrez" wrote: 2. Community split There is fear that the contributor-specific event will separate the community into two groups, with developers skipping the main event and non-developers not providing any feedback to the contributor-specific event

Re: [openstack-dev] [Fuel][Fuel-Library] Fuel CI issues

Hi Ivan Thanks for bringing this up. Frankly, I think that we hurried a little bit by making our integration with upstream puppet manifests too continuous. I would suppose that we used a little bit different technique. First of all, we need to have a set of stable Fuel commits against which the c

[openstack-dev] [openstack][keystone] What is the difference between auth_url and auth_uri?

Hi all, There are two config parameters (auth_uri and auth_url) in keystone_authtoken group. I want to know what is the difference between them. Can I use only one of them? Best Regards, Wanghua __ OpenStack Development Mail

Re: [openstack-dev] [Horizon] Blueprints for Outreachy internship

Hi Matthias, Thanks for the links to the blueprints. I in fact did checkout the list of bps earlier but I found many of them have not been approved yet. I can give you a list of bps I would like to mentor for, from which we could perhaps select one or two for the internship program depending on wh

Re: [openstack-dev] [openstack][keystone] What is the difference between auth_url and auth_uri?

Uri and url are different but sometime they might be same. Well ,you can see it from http://www.ietf.org/rfc/rfc3986.txt BR, Eli(Li Yong)Qiao From: 王华 [mailto:[email protected]] Sent: Monday, February 29, 2016 7:04 PM To: OpenStack Development Mailing List (not for usage questions) Subje

[openstack-dev] [Fuel] [Ci] New 'fuel-ostf' gate job

Hi to all, please be informed that starting from today we're launching gate job [1] for 'fuel-ostf' package [2] Mentioned job will be triggered on each commit and will perform steps: - build a package from the commit - run system tests scenario [3] with using created package - vote in a patchset

Re: [openstack-dev] [fuel][plugins][lma]

Hello Shubham, In the coming version of LMA (0.9), we've already ensured that the the Puppet modules configuring the different components of the LMA toolchain can be used without Fuel and we're in the process of documenting all of them as well as how they can be used outside of Fuel. Eventually it

Re: [openstack-dev] [all] A proposal to separate the design summit

On Mon, Feb 29, 2016 at 4:32 AM, Thierry Carrez wrote: > That was considered... and I would not necessarily be against it, but I > would like to understand what the benefit would be. Tom advocated for > keeping it as a separate event (or a set of regional separated events) that > would be ops-bran

[openstack-dev] [puppet] weekly meeting #72

Hi, We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting4. https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack As usual, free free to bring topics in this etherpad: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160301 We'll also have open discussion

Re: [openstack-dev] [Magnum][Kuryr] Kuryr-Magnum integration (nested containers)

Folks, A friendly reminder to review the updated spec [1] https://review.openstack.org/#/c/269039/ Thank you, Fawad Khaliq On Wed, Feb 24, 2016 at 8:50 PM, Fawad Khaliq wrote: > Folks, > > Thanks for the reviews. The spec [1] has been updated after the latest > feedback. > > [1] https://revi

Re: [openstack-dev] [all] audience for release notes

Excerpts from Thomas Goirand's message of 2016-02-29 15:15:10 +0800: > Hi Doug, > > Thanks for your reply, it's much appreciated! > > On 02/28/2016 11:40 PM, Doug Hellmann wrote: > > Excerpts from Thomas Goirand's message of 2016-02-28 22:56:51 +0800: > >>> I believe Thomas is referring to: > >>>

Re: [openstack-dev] [Neutron][ml2][Manila] API to query segments used during port binding

Fixed neutron tag in the subject. Marc wrote: Hi Neutron team, I am currently working on a feature for hierarchical port binding support in Manila [1] [2]. Just to give some context: In the current implementation Manila creates a neutron port but let it unbound (state DOWN). Therefore Man

[openstack-dev] FW: [magnum][magnum-ui] Liaisons for I18n

Hi team, FYI, I18n team needs liaisons from magnum-ui. Please contact the i18n team if you interest in this role. Best regards, Hongbin From: Ying Chun Guo [mailto:[email protected]] Sent: February-29-16 3:48 AM To: [email protected] Subject: [openstack-dev] [all][i18n] Liaiso

Re: [openstack-dev] [nova][cinder] volumes stuck detaching attaching and force detach

On 2/22/2016 4:08 PM, Walter A. Boring IV wrote: On 02/22/2016 11:24 AM, John Garbutt wrote: Hi, Just came up on IRC, when nova-compute gets killed half way through a volume attach (i.e. no graceful shutdown), things get stuck in a bad state, like volumes stuck in the attaching state. This l

[openstack-dev] [api] service types authority initial reviews

I started some initial reviews for the service-types-authority repository under the assumption that we're going to work on some fundamentals here and figure this out as we go along - https://review.openstack.org/#/q/project:openstack/service-types-authority For those new to things, part of the Ser

[openstack-dev] [TripleO] core members for tripleo-ui

There is a new projects for the ui called tripleo-ui. As most of the existing TripleO core members aren't going to be reviewing UI specific patches is seems reasonable that we might add a few review candidates who can focus specifically on UI specific patches. I'd like to proposed we add Jiri Toma

Re: [openstack-dev] [Nova] Re-booting the SR-IOV meeting

On 02/26/2016 10:35 PM, Shinobu Kinjo wrote: > Hello, > > Thank you for your message. > Is there any list of only SR-IOV related bugfixes? If there is any > pointer, that would be very useful. > Hi - so I think that one of the main goals of the meeting tomorrow will be to figure out a list of fi

Re: [openstack-dev] [api][neutron] question on putting an existing tag

I'm considering the tag implementation in neutron. Although I proposed server returns 409 in tag existing case, on the basis of the above discussion, server should return the same response code. I will change current implementation to returning 201. Thanks, Hirofumi On 2016/02/27 2:24, Akihiro

Re: [openstack-dev] [TripleO] core members for tripleo-ui

+1 On 02/29/2016 10:27 AM, Dan Prince wrote: There is a new projects for the ui called tripleo-ui. As most of the existing TripleO core members aren't going to be reviewing UI specific patches is seems reasonable that we might add a few review candidates who can focus specifically on UI specific

Re: [openstack-dev] [all][i18n] Liaisons for I18n

Have just updated myself as a murano liaison. Would be happy to help with i18n’ing murano-dashboard! --  Kirill Zaitsev Murano team Software Engineer Mirantis, Inc On 29 February 2016 at 12:29:15, Ying Chun Guo ([email protected]) wrote: Just noticed the previous mail is not in good format. S

Re: [openstack-dev] [all] A proposal to separate the design summit

On 29/02/16 10:32, "Thierry Carrez" wrote: >Tim Bell wrote: >> >> On 26/02/16 18:08, "Thierry Carrez" wrote: 2. Community split There is fear that the contributor-specific event will separate the community into two groups, with developers skipping the main event and >>

[openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

Hi team, This is a continued discussion from a review [1]. Corey O'Brien suggested to have Magnum support a single OS distro (Atomic). I disagreed. I think we should bring the discussion to here to get broader set of inputs. Corey O'Brien >From the midcycle, we decided we weren't going to conti

Re: [openstack-dev] [TripleO] core members for tripleo-ui

+1 On 29.2.2016 16:27, Dan Prince wrote: There is a new projects for the ui called tripleo-ui. As most of the existing TripleO core members aren't going to be reviewing UI specific patches is seems reasonable that we might add a few review candidates who can focus specifically on UI specific pat

[openstack-dev] [neutron]Ports not binding correctly after restart

Hi all. I'm facing a problem with "Neutron/OVS/DVR" in "Liberty". With 3 network/compute nodes I created, successfully, 100 tenants, 100 networks (1 per tenants), 3 DHCP agents per network and 100 routers (1 per network), 100 VM (1 per tenant) and 1 FIP per VM. All working and responding. The pro

[openstack-dev] [nova] nova hooks - document & test or deprecate?

The nova/hooks.py infrastructure has been with us since early Nova. It's currently only annotated on a few locations - 'build_instance', 'create_instance', 'delete_instance', and 'instance_network_info'. It's got a couple of unit tests on it, but nothing that actually tests real behavior of the hoo

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

One of the main reasons for moving to a "bay driver” model was to allow us to focus our efforts. We talked about focusing our support to the distros with a religion around them, e.g. Ubuntu and a Red Hat derivative. Being frank, I do not see much benefit in supporting a small distro if we have sup

Re: [openstack-dev] [kolla] unblocking the gate

On 2/29/16, 12:26 AM, "Andreas Jaeger" wrote: >On 2016-02-29 06:59, Steven Dake (stdake) wrote: >> Hey folks, >> >> It should be obvious that commiters should be testing their changes, but >> unfortunately this is not always the case. With the recent state of the >> gate relating to the intro

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

> In our continued quest on being more explicit about plug points it feels > like we should other document the interface (which means creating > stability on the hook parameters) or we should deprecate this construct > as part of a bygone era. > > I lean on deprecation because it feels like a thin

[openstack-dev] [Fuel] Feature Freeze Exception Request - switching to CentOS-7.2

I'd like to ask for a feature freeze exception for switching to CentOS-7.2 feature [0]. CentOS-7.2 ISO's have been tested periodically since the beginning of the year, and all major issues were addressed / fixed at the moment. During the last weekend I've made 70 BVT runs to verify that the solut

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

Well, I do feel that the hooks have been pretty painful (having tried to use them and having stumbled upon that bug). However, even as undocumented as they were, that seems to be the only way of doing actions in nova when instances are spawned or deleted, while also having some awareness of what's

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On Mon, Feb 29, 2016 at 11:59:06AM -0500, Sean Dague wrote: > The nova/hooks.py infrastructure has been with us since early Nova. It's > currently only annotated on a few locations - 'build_instance', > 'create_instance', 'delete_instance', and 'instance_network_info'. It's > got a couple of unit t

[openstack-dev] [Fuel][FFE] API must allow VIP to be manually set to ANY valid IP address

Colleagues, I would like to request a feature freeze exception for 'API must allow VIP to be manually set to ANY valid IP address' [1]. There are three patches still under the review process [2][3][4]. [2][3] are blocked by merge freeze for UI changes due to separation of fuel-ui and fuel-web rep

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On Mon, Feb 29, 2016, at 12:12 PM, Dan Smith wrote: > > In our continued quest on being more explicit about plug points it feels > > like we should other document the interface (which means creating > > stability on the hook parameters) or we should deprecate this construct > > as part of a bygon

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/26/2016 10:13 PM, Tom Fifield wrote: > > > On 26/02/16 22:02, Thomas Goirand wrote: >> On 02/23/2016 12:33 AM, Jay Pipes wrote: >>> OpenStack Conference <-- The main event. >>> OpenStack:How <-- The developer planning event. >>> >>> :) >>> >>> -jay >> >> Probably I'm dumb, but I still don't

Re: [openstack-dev] [TripleO] core members for tripleo-ui

On Mon, Feb 29, 2016 at 4:27 PM, Dan Prince wrote: > There is a new projects for the ui called tripleo-ui. As most of the > existing TripleO core members aren't going to be reviewing UI specific > patches is seems reasonable that we might add a few review candidates > who can focus specifically on

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On Mon, Feb 29, 2016 at 12:23:09PM -0500, Andrew Laski wrote: > > > On Mon, Feb 29, 2016, at 12:12 PM, Dan Smith wrote: > > > In our continued quest on being more explicit about plug points it feels > > > like we should other document the interface (which means creating > > > stability on the hoo

[openstack-dev] [freezer] Freezer midclycle meetup

Hi, The Freezer team is excited to announce that we're hosting our midcycle meetup on 15th and 16th of March, 2016. The event is free and will happen in Galway, Ireland and be hosted by Hewlett Packard Enterprise. Logistic is being managed here: https://etherpad.openstack.org/p/freezer_midcycl

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/22/2016 11:06 AM, Dmitry Tantsur wrote: > I agree with Daniel + a couple more comments inline. > > On 02/22/2016 04:49 PM, Daniel P. Berrange wrote: >> On Mon, Feb 22, 2016 at 04:14:06PM +0100, Thierry Carrez wrote: >>> Hi everyone, >>> >>> TL;DR: Let's split the events, starting after Barce

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/22/2016 01:51 PM, Tim Bell wrote: > > > > > > On 22/02/16 17:27, "John Garbutt" wrote: > >> On 22 February 2016 at 15:31, Monty Taylor wrote: >>> On 02/22/2016 07:24 AM, Russell Bryant wrote: On Mon, Feb 22, 2016 at 10:14 AM, Thierry Carrez > wr

Re: [openstack-dev] [all] audience for release notes

On 02/29/2016 10:31 PM, Doug Hellmann wrote: >>> Give this a try and see if it works any better: >>> https://review.openstack.org/285812 >> >> Oh, thanks so much! I'll try and give feedback on review.d.o. Is the >> issue around the (missed) use of --debug-quick-random? >> >> Why do we need Reno uni

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

Andrew Laski wrote: > > > On Mon, Feb 29, 2016, at 12:12 PM, Dan Smith wrote: >>> In our continued quest on being more explicit about plug points it feels >>> like we should other document the interface (which means creating >>> stability on the hook parameters) or we should deprecate this constr

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/22/2016 06:49 PM, Matt Fischer wrote: > On Mon, Feb 22, 2016 at 11:51 AM, Tim Bell wrote: > >> >> >> >> >> >> On 22/02/16 17:27, "John Garbutt" wrote: >> >>> On 22 February 2016 at 15:31, Monty Taylor wrote: On 02/22/2016 07:24 AM, Russell Bryant wrote: > On Mon, Feb 22, 2016 at

[openstack-dev] [Infra] Meeting Tuesday March 1st at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday March 1st, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agenda it

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/23/2016 04:26 AM, Thierry Carrez wrote: > Tim Bell wrote: >> On 22/02/16 17:27, "John Garbutt" wrote: >>> [...] >>> I am sure there are more questions that will pop up. Like I assume >>> this means there is no ATC free pass to the summit? And I guess a >>> small nominal fee for the contribut

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On 2/29/2016 11:23 AM, Andrew Laski wrote: On Mon, Feb 29, 2016, at 12:12 PM, Dan Smith wrote: In our continued quest on being more explicit about plug points it feels like we should other document the interface (which means creating stability on the hook parameters) or we should deprecate t

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/22/2016 12:35 PM, Thierry Carrez wrote: > Clayton O'Neill wrote: >> Is the expectation that the ops mid-cycle would continue separately, >> or be held with the meeting formerly known as the Design Summit? >> >> Personally I’d prefer they be held together, but scheduled with the >> thought tha

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

> Forgive my ignorance or for playing devil's advocate, but wouldn't the > main difference between notifications and hooks be that notifications > are asynchronous and hooks aren't? The main difference is that notifications are external and intended to be stable (especially with the versioned noti

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On Mon, Feb 29, 2016 at 12:03:00PM -0600, Matt Riedemann wrote: > > > On 2/29/2016 11:23 AM, Andrew Laski wrote: > > > > > >On Mon, Feb 29, 2016, at 12:12 PM, Dan Smith wrote: > >>>In our continued quest on being more explicit about plug points it feels > >>>like we should other document the inte

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On Mon, Feb 29, 2016, at 12:53 PM, Rob Crittenden wrote: > Andrew Laski wrote: > > > > > > On Mon, Feb 29, 2016, at 12:12 PM, Dan Smith wrote: > >>> In our continued quest on being more explicit about plug points it feels > >>> like we should other document the interface (which means creating >

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

Consider this: Which OS runs on the bay nodes is not important to end users. What matters to users is the environments their containers execute in, which has only one thing in common with the bay node OS: the kernel. The linux syscall interface is stable enough that the various linux distributio

Re: [openstack-dev] [devstack] stack.sh keeps failing with RTNETLINK answers: Network is unreachable

On 02/26/2016 03:48 AM, Paul Carlton wrote: Sean Don't think unstack failed, when I manually create the device ( sudo ovs-vsctl --no-wait -- --may-exist add-br br-ex) unstack.sh removes it. sudo ip route show default via 172.18.20.1 dev eth0 169.254.169.254 via 172.18.20.2 dev eth0 172.18.20.0/

Re: [openstack-dev] [kolla] unblocking the gate

On Mon, Feb 29, 2016, at 09:09 AM, Steven Dake (stdake) wrote: > > > On 2/29/16, 12:26 AM, "Andreas Jaeger" wrote: > >This is not needed, the CI system always rebases if you run tests. To > >get current tests, a simple "recheck" is enough. > > > >Also, we test in the gate before merging - again

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On 02/29/2016 01:33 PM, Andrew Laski wrote: > > > On Mon, Feb 29, 2016, at 12:53 PM, Rob Crittenden wrote: >> Andrew Laski wrote: >>> >>> >>> On Mon, Feb 29, 2016, at 12:12 PM, Dan Smith wrote: > In our continued quest on being more explicit about plug points it feels > like we should oth

[openstack-dev] [all][release] releases are not automatic, please check for review comments

We have several release requests in the queue right now that have comments and -1 votes asking for more details. Please check back if you've filed a request so we don't miss the window to process the request this week. Doug _

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On Mon, Feb 29, 2016, at 01:18 PM, Dan Smith wrote: > > Forgive my ignorance or for playing devil's advocate, but wouldn't the > > main difference between notifications and hooks be that notifications > > are asynchronous and hooks aren't? > > The main difference is that notifications are extern

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

From: Adrian Otto Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Monday 29 February 2016 at 19:36 To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro Cons

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/29/2016 03:19 AM, Sylvain Bauza wrote: >>> 3. Losing the main summit as an excuse to fund devs travel >>> >>> Some developers are sent to the Design Summit only because the main >>> summit is happening at the same time and wouldn't get funding to attend >>> a specific event. >> >> If you hav

Re: [openstack-dev] [TripleO] core members for tripleo-ui

On Mon, Feb 29, 2016 at 12:32 PM, Ana Krivokapic wrote: > On Mon, Feb 29, 2016 at 4:27 PM, Dan Prince wrote: >> There is a new projects for the ui called tripleo-ui. As most of the >> existing TripleO core members aren't going to be reviewing UI specific >> patches is seems reasonable that we mig

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/22/2016 10:49 AM, Daniel P. Berrange wrote: > On Mon, Feb 22, 2016 at 04:14:06PM +0100, Thierry Carrez wrote: >> Hi everyone, >> >> TL;DR: Let's split the events, starting after Barcelona. > > Yes, please. Your proposal addresses the big issue I have with current > summits which is the reall

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On 02/29/2016 12:22 PM, Daniel P. Berrange wrote: There's three core scenarios for hooks 1. Modifying some aspect of the Nova operation 2. Triggering an external action synchronously to some Nova operation 3. Triggering an external action asynchronously to some Nova operation The Rdo exa

[openstack-dev] [Neutron] Team meeting this Tue at 1400 UTC

Hi neutrinos, A kind reminder for this week's meeting. More on the agenda [1]. Cheers, Ihar [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development M

Re: [openstack-dev] [neutron]Ports not binding correctly after restart

There was an issue with the order of the agents starting up that led to some issues with L3 HA that was fixed with a systemd notification here: https://review.openstack.org/#/c/254920/ However, I assume there had to be a corresponding packaging patch that would make the the other agents wait for th

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On 02/29/2016 12:19 PM, Chris Friesen wrote: On 02/29/2016 12:22 PM, Daniel P. Berrange wrote: There's three core scenarios for hooks 1. Modifying some aspect of the Nova operation 2. Triggering an external action synchronously to some Nova operation 3. Triggering an external action asyn

Re: [openstack-dev] Google Sumer of Code 2016 - Call for ideas and mentors (deadline 19/02/2016)

Updates on this topic. Unfortunately we didn't make it for this year. We'll apply next year again, thanks all for your support. Best, Victoria 2016-02-15 16:55 GMT-03:00 Victoria Martínez de la Cruz < [email protected]>: > Friendly reminder, we are still looking for mentors and int

Re: [openstack-dev] [all] A proposal to separate the design summit

> > Current thinking would be to give preferential rates to access the main > > summit to people who are present to other events (like this new > > separated contributors-oriented event, or Ops midcycle(s)). That would > > allow for a wider definition of "active community member" and reduce > > ga

Re: [openstack-dev] Google Sumer of Code 2016 - Call for ideas and mentors (deadline 19/02/2016)

Thanks for putting in the effort, Victoria! We learn each year we apply. Anne On Mon, Feb 29, 2016 at 2:02 PM, Victoria Martínez de la Cruz < [email protected]> wrote: > Updates on this topic. Unfortunately we didn't make it for this year. > We'll apply next year again, thanks all f

[openstack-dev] [Manila] NFS and root squash

We haven't spent much time (as a community) discussing root squashing, but Rodrigo's migration work has made it clear that we need clearer definitions around NFS permissions, and root squashing in particular. I hope it's obvious to everyone that an NFS share with root squash for ALL HOSTS is p

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On 02/29/2016 11:59 AM, Sean Dague wrote: > The nova/hooks.py infrastructure has been with us since early Nova. It's > currently only annotated on a few locations - 'build_instance', > 'create_instance', 'delete_instance', and 'instance_network_info'. It's > got a couple of unit tests on it, but no

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/29/2016 03:10 PM, Eoghan Glynn wrote: > >>> Current thinking would be to give preferential rates to access the main >>> summit to people who are present to other events (like this new >>> separated contributors-oriented event, or Ops midcycle(s)). That would >>> allow for a wider definition

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

From: Adrian Otto [mailto:[email protected]] Sent: February-29-16 1:36 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro Consider this: Which OS runs on the bay nodes is not import

Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container could not be found

Wondering, have you guys figured out this issue? I am seeing the same problem that Jiahao is getting. On Thu, Feb 4, 2016 at 9:53 AM, Adam Harwell wrote: > Could you provide your neutron-lbaas.conf? Depending on what version > you're using, barbican may not be the default secret backend (I belie

Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container could not be found

We could use some more information. Phillip V. Toohill III Software Developer [http://600a2794aa4ab5bae6bd-8d3014ab8e4d12d3346853d589a26319.r53.cf1.rackcdn.com/signatures/images/rackspace_logo.png] phone: 210-312-4366 mobile: 210-440-8374 From: Madhusudhan Kand

Re: [openstack-dev] [kolla] unblocking the gate

On Mon, Feb 29, 2016 at 6:42 PM, Clark Boylan wrote: > On Mon, Feb 29, 2016, at 09:09 AM, Steven Dake (stdake) wrote: > > > > > > On 2/29/16, 12:26 AM, "Andreas Jaeger" wrote: > > >This is not needed, the CI system always rebases if you run tests. To > > >get current tests, a simple "recheck" is

Re: [openstack-dev] [Neutron][ml2][Manila] API to query segments used during port binding

You're correct. Right now there is no way via the HTTP API to find which segments a port is bound to. This is something we can certainly consider adding, but it will need an RFE so it wouldn't land until Newton at the earliest. Have you considered writing an ML2 driver that just notifies Manilla o

Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container could not be found

To further my thoughts, as Adam mentioned, it could be a user issue, which to me is what it sounds like. So being able to view the config and have other information is pertinent to solving the issue. Phillip V. Toohill III Software Developer [http://600a2794aa4ab5bae6bd-8d3014ab8e4d12d3346853d5

[openstack-dev] [salt] Team meeting this Tuesday

Hi Saltstackers, A kind reminder for this week's #openstack-salt meeting. More on the agenda [1]. [1]. https://wiki.openstack.org/wiki/Meetings/openstack-salt Regards, Jay Clark Sr. OpenStack Deployment Engineer E: [email protected] H: 919.341.4670 M: 919.345.11

Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container could not be found

Is what I can see the error logs in barbican svc screen while I create TLS listener like this: http://paste.openstack.org/show/xVl9iuJtGW03fCGetDm3/ 2016-02-29 13:42:55.222 INFO barbican.api.middleware.context [req-65fd0f08-4c1e-4b2f-9cbd-64f186365077 afaa5d797f3543369d05e370a543ef9d c141e106a7424

Re: [openstack-dev] [Nova] Re-booting the SR-IOV meeting

> Hi - so I think that one of the main goals of the meeting tomorrow will > be to figure out a list of fixes we want to have reviewed and hopefully > merged in Mitaka. Understood. > > I don't there is a straightforward and exhaustive way to find these (one > trick I use is to look for changes th

Re: [openstack-dev] [Neutron][LBaaS][barbican]TLS container could not be found

Is the create LB happening on a different user than the one that created the barbican container? Maybe im not looking at it right, but cant tell from this. Phillip V. Toohill III Software Developer [http://600a2794aa4ab5bae6bd-8d3014ab8e4d12d3346853d589a26319.r53.cf1.rackcdn.com/signatures/image

[openstack-dev] [Neutron] DocImpact flag: a kind reminder

Hi Neutrinos, Please remember that what you decorate a commit message with DocImpact, this must be followed by a brief description of the documentation impact [1]. Also, please be aware that currently, as soon as the patch merges, a bug report is filed against the Launchpad project of the targeted

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On 2/29/2016 2:54 PM, Sean Dague wrote: On 02/29/2016 11:59 AM, Sean Dague wrote: The nova/hooks.py infrastructure has been with us since early Nova. It's currently only annotated on a few locations - 'build_instance', 'create_instance', 'delete_instance', and 'instance_network_info'. It's got

Re: [openstack-dev] [all] A proposal to separate the design summit

On Mon, 2016-02-29 at 15:57 -0500, Anita Kuno wrote: > On 02/29/2016 03:10 PM, Eoghan Glynn wrote: > > > > > > Current thinking would be to give preferential rates to access > > > > the main summit to people who are present to other events (like > > > > this new separated contributors-oriented e

Re: [openstack-dev] [Neutron][ml2][Manila] API to query segments used during port binding

Is Manila actually connecting (i.e. binding) something it controls to a Neutron port, similar to how a Neutron L3 or DHCP agent connects a network namespace to a port? Or does it just need to know the details about a port bound for a VM (or a service)? If the former, it should probably be usin

Re: [openstack-dev] [all] A proposal to separate the design summit

On 02/29/2016 05:34 PM, James Bottomley wrote: > On Mon, 2016-02-29 at 15:57 -0500, Anita Kuno wrote: >> On 02/29/2016 03:10 PM, Eoghan Glynn wrote: >>> > Current thinking would be to give preferential rates to access > the main summit to people who are present to other events (like >

Re: [openstack-dev] [fuel] Fuel plugins: lets have some rules

On Mon, Feb 29, 2016 at 08:21:18AM +0100, Andreas Jaeger wrote: > > Yes, they will officially become a part of Fuel project. First such > > example is likely to be the Murano plugin [0], so we can use it a the > > guinea pig to try out this process. > > > > [0] https://review.openstack.org/269567

[openstack-dev] [Neutron][L3] Routed Networks Meeting Tomorrow

Since I accidentally missed the meeting last week, I thought I'd send out a message reminding of the meeting tomorrow. It will be right after the Neutron meeting in #openstack-meeting [1]. The meeting alternates each week due to various bi-weekly conflicts and trying to allow folks in JST to join

[openstack-dev] [devstack] [neutron] How to ask for linuxbridge instead of openvswitch

How would I modify the recipe at http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-a-single-interface to get linuxbridge instead of openvswitch? Thanks, Mike __ OpenStack Development Mai

Re: [openstack-dev] [all] A proposal to separate the design summit

On Mon, 2016-02-29 at 17:48 -0500, Anita Kuno wrote: > On 02/29/2016 05:34 PM, James Bottomley wrote: [...] > > While I accept there is potentially a gaming problem in all forms > > of Open Source (we see this in the kernel with the attempt to boost > > patch counts with trivial changes), I'd be h

Re: [openstack-dev] [nova] solving API case sensitivity issues

On Feb 25, 2016, at 8:35, Michał Dulko wrote: > We've faced similar issues in Cinder and as solution we've moved > filtering to Python code. Like in for example [1] or [2]. But no, we > haven't had UNIQUE constraint on the DB column in these cases, only on IDs. This is an interesting option. I

  1   2   >