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

For the moment Manila does following: - creates Neutron port, consider "reserves" network info. - then calls its own share driver that supports network handling and that driver does binding on its backend. - Neutron does not have info about real usage of a port and its info. So, it is correct to s

[openstack-dev] [nova] Should we cleanup migration from virt drivers?

hello Nova hackers I see in some of virt drivers (see belows links) 's confirm_resize/revert_resize(or something like that) passing a parameter 'migration', but it is not used at all in virt layer drivers, I wonder why we still keep them (to reserved for future usage)? can we do a cleanup? IMO

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

Hi, all, I don't know why I clone an old version of devstack, which hasn't been influenced by the patch. Hence, I install devstack in two nodes successfully. I think I know how to fix it. BTW, Zhiyuan's solution to solving the problem in my last mail works. Thank you for your help. Best regards,

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

On 29/02/16 17: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 pa

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

There seems to be different concerns, so it would be helpful to consider them separately: Ability to accommodate different distros How to support given limited resources: gate tests, developers From the discussion at the midcycle, I think we do have agreement that Magnum must be able to

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

On Tue, Mar 1, 2016 at 12:23 AM, Matt Riedemann wrote: > > > 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', >

[openstack-dev] [all][log] Ideas to log request-ids in cross-projects

Hi Devs, Considering return request-id to caller specs [1] is implemented in python-*client, I would like to begin discussion on how these request-ids will be logged in cross-projects. In logging work-group meeting (11-Nov-2015) [2] there was a discussion about how to log request-id in the log mes

[openstack-dev] [tacker] Weekly meeting agenda - Mar 1, 2016

Here is the agenda for this week's weekly meeting, https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Mar_1.2C_2016 1700 UTC Tuesday #openstack-meeting-4 * Announcements * TOSCA parser integration ** Basic parser integration ** Auto Resource Creation ** Enhanced VNF placement * Mitaka fit a

[openstack-dev] [ceilometer] Unable to get ceilometer events for instances running for demo project

I have a single node configuration for devstack liberty working and I want to record all the *ceilometer events* like compute.instance.start, compute.instance.end, compute.instance.update etc occurred recently. I am unable to get any event occurred for instances running for demo project i.e when I

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

>This seems gross and backwards. It makes sense as a short term hack but given that we have time to design this correctly I'd prefer to get this information in a more straighforward way. Well it depends on what is happening here. If Manilla is wiring up a specific VLAN for a port, that makes it pa

[openstack-dev] [nova] Nova API sub-team meeting

We have weekly Nova API meeting today. The meeting is being held Tuesday UTC1200. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks __

Re: [openstack-dev] [Zaqar] Nominating Eva Balycheva for Zaqar core

Thank you, it's a great honor for me to become core reviewer! And responsibility... Don't forget also these areas: 5. Zaqar server (most of my patches are for the server) 6. Contributor docs 7. Bug reporting (here I'm really effective) On 03/01/2016 03:47 AM, Fei Long Wang wrote: Hi all, I wo

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

Hi, All, Let's move the discussion to #openstack-tricircle in IRC. BR Zhiyuan On 1 March 2016 at 11:07, Yipei Niu wrote: > Hi, all, > > The bug of deploying devstack with two-node configuration is already > fixed. According to the official document, I have already installed > devstack in two n

[openstack-dev] [cross-project] Meeting SKIPPED, Tue March 1st, 21:00 UTC

Hi all! We will be skipping the cross-project meeting since I have not been able to confirm with the owners of the specs we would've discussed will be available for the meeting: * Event message format [1] * Instance auto evacuation [2] We will try again next week! Also cross-project spec liaiso

Re: [openstack-dev] [Zaqar] Nominating Eva Balycheva for Zaqar core

Very glad to +1 for Eva, she is a very good reviewer and coder! 2016-03-01 11:00 GMT+08:00 Victoria Martínez de la Cruz : > A huge +1 for this proposal. > > Eva has joined as an Outreachy intern for this round and she impacted the > Zaqar project in a truly positive way. > > Thanks for all your co

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

Hi, all, The bug of deploying devstack with two-node configuration is already fixed. According to the official document, I have already installed devstack in two nodes successfully. Moreover, I am still trying to play tricircle in two nodes. When installing tricircle to node1, I still encounter t

Re: [openstack-dev] [Zaqar] Nominating Eva Balycheva for Zaqar core

A huge +1 for this proposal. Eva has joined as an Outreachy intern for this round and she impacted the Zaqar project in a truly positive way. Thanks for all your contributions Eva, you totally deserve this. 2016-02-29 21:47 GMT-03:00 Fei Long Wang : > Hi all, > > I would like to propose adding

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

Hi, Yipei, The issue is that the OS_REGION_NAME should be “Pod2” for the Node2 for Nova,Cinder, Neutron endpoint registration in KeyStone, but when creating endpoint in Keystone, devstack will use command like “openstack endpoint create” to access KeyStone, the OS_REGION_NAME should be the regi

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

I think users need the support for multiple OS choices. Users may want to modify the OS by themselves to meet the requirement of their business. If Magnum only supports a single OS distro, we should have a convenient way to change one OS distro to another. But the OSes are so different, the work i

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

On 02/29/2016 05:58 PM, Mike Spreitzer wrote: > 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 > > > > > > > ___

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

On Mon, Feb 29, 2016, at 01:38 PM, Sam Yaple wrote: > 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 rebase

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

On Mon, Feb 29, 2016 at 01:19:29PM +0300, Vladimir Kuklin wrote: > 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. I don't think "h

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

http://docs.openstack.org/developer/devstack/guides/neutron.html#using-linux-bridge-instead-of-open-vswitch Does this work for you? -- Brian Stajkowski Manager, Software Development - US m: 702.575.7890 irc: ski e: brian.stajkow...@rackspace.com From: Mike Spreitzer mailto:mspre...@us.ibm.com>>

[openstack-dev] Mitaka IP Availability [Urgent]

All, We just need 1 more +2 and the workflow completed for ip availability to make it into Mitaka. Is it possible we can get this reviewed and merged. Any help is appreciated. https://review.openstack.org/#/c/212955/ Thanks! -- Brian Stajkowski Manager, Software Development - US m: 702.575.7

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

On 02/29/2016 04:38 PM, Kevin Benton wrote: 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. I believe Newton is the

Re: [openstack-dev] pci_alias

Hi, Beliveau, Ludovic currently the alias define as a multiple string option item. this make the code look this configure option is a array, but user define it multiple times instead of a array. pci_alias_opt = cfg.MultiStrOpt Yongli He 在 2015年10月27日 23:44, Beliveau, Ludovic 写道: Hi, I'm c

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

Okay, Figured out the issue.When debugging, I was trying to create lb and barbican clients with different users. Thanks guys! On Mon, Feb 29, 2016 at 2:07 PM, Phillip Toohill < phillip.tooh...@rackspace.com> wrote: > Is the create LB happening on a different user than the one that created > the b

[openstack-dev] [Zaqar] Nominating Eva Balycheva for Zaqar core

Hi all, I would like to propose adding Eva Balycheva(Eva-i) for the Zaqar core team. Eva has been an awesome contributor since joining the Zaqar team. She is currently the most active non-core reviewer on Zaqar projects for the last 90 days[1]. During this time, she's been contributing to many dif

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

As Adam stated, it could be any of those reasons. Mainly look for the credentials defined under [service_auth] section of lbaas conf file. Most importantly the credentials, tenant (or project) name should be the same as the user that created the container. This is assuming you aren't using ACLs'.

[openstack-dev] Limits on volume read throughput?

I have need to benchmark volume-read performance of an application running in an instance, assuming extremely fast storage. To simulate fast storage, I have an AIO install of OpenStack, with local flash disks. Cinder LVM volumes are striped across three flash drives (what I have in the present set

[openstack-dev] [ironic] weekly subteam status report

Hi, We are happy to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 22.02.2016): - Ironic: 162 bugs (+6) + 178 wishlist items (+3). 16 new (+2), 123 in progress (+5), 0

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

On 2016/03/01 9:00, Armando M. wrote: On 29 February 2016 at 15:34, Hirofumi Ichihara > wrote: Hi Armando, I didn't know and I have such patch now. Thank you for your message. I have seen that neutron spec has the flag in the Commit

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

On 29 February 2016 at 15:34, Hirofumi Ichihara < ichihara.hirof...@lab.ntt.co.jp> wrote: > Hi Armando, > > I didn't know and I have such patch now. > Thank you for your message. > > I have seen that neutron spec has the flag in the Commit Message. > In such case, we don't need to add the flag int

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

Hi Armando, I didn't know and I have such patch now. Thank you for your message. I have seen that neutron spec has the flag in the Commit Message. In such case, we don't need to add the flag into the implementation patch, do we? Thanks, Hirofumi On 2016/03/01 7:18, Armando M. wrote: Hi Neut

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

On 02/29/2016 06:17 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

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 redu

Re: [openstack-dev] Vlan Tenant network

That is a great guide. Cheers, On Mon, Feb 29, 2016 at 5:20 PM, Andreas Scheuring wrote: > 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, fla

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

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

[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

[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

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

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] [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 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] [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

[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] [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

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 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

[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: jason.t.cl...@hpe.com H: 919.341.4670 M: 919.345.11

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

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] [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][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] [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] [magnum] Discussion of supporting single/multiple OS distro

From: Adrian Otto [mailto:adrian.o...@rackspace.com] 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] [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] [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

[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] 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 < victo...@vmartinezdelacruz.com> wrote: > Updates on this topic. Unfortunately we didn't make it for this year. > We'll apply next year again, thanks all f

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)

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 < victo...@vmartinezdelacruz.com>: > Friendly reminder, we are still looking for mentors and int

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] [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

[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] [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

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] [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/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] [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] [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

[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 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

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] [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] [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] [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] [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?

> 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] [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?

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/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

[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/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

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] 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] [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] 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

[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] [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

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] [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] [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

[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 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

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

[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?

> 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

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

  1   2   >