[openstack-dev] [Mistral] Action context passed to all action executions by default

2014-12-08 Thread W Chan
Renat, Is there any reason why Mistral do not pass action context such as workflow ID, execution ID, task ID, and etc to all of the action executions? I think it makes a lot of sense for that information to be made available by default. The action can then decide what to do with the information.

Re: [openstack-dev] [neutron][lbaas] Shared Objects in LBaaS - Use Cases that led us to adopt this.

2014-12-08 Thread Samuel Bercovici
Hi, I agree that the most important thing is to conclude how status properties are being managed and handled so it will remain consistent as we move along. I am fine with starting with a simple model and expending as need to be. The L7 implementation is ready waiting for the rest of the model to

Re: [openstack-dev] [neutron] Changes to the core team

2014-12-08 Thread Gariganti, Sudhakar Babu
Congrats Kevin and Henry ☺. From: Kyle Mestery [mailto:mest...@mestery.com] Sent: Monday, December 08, 2014 11:32 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] Changes to the core team On Tue, Dec 2, 2014 at 9:59 AM, Kyle Mestery mailt

[openstack-dev] [Ironic] How to get past pxelinux.0 bootloader?

2014-12-08 Thread Peeyush Gupta
Hi all, So, I have set up a devstack ironic setup for baremetal deployment. I have been able to deploy a baremetal node successfully using pxe_ipmitool driver. Now, I am trying to boot a server where I already have a bootloader i.e. I don't need pxelinux to go and fetch kernel and initrd images fo

[openstack-dev] [Ironic] Some questions about Ironic service

2014-12-08 Thread xianchaobo
Hello, all I'm trying to install and configure Ironic service, something confused me. I create two neutron networks, public network and private network. Private network is used to deploy physical machines Public network is used to provide floating ip. (1) Private network type can be VLAN or

Re: [openstack-dev] [api] Using query string or request body to pass parameter

2014-12-08 Thread Alex Xu
Kevin, thanks for the info! I agree with you. RFC is the authority. use payload in the DELETE isn't good way. 2014-12-09 7:58 GMT+08:00 Kevin L. Mitchell : > On Tue, 2014-12-09 at 07:38 +0800, Alex Xu wrote: > > Not sure all, nova is limited > > at > https://github.com/openstack/nova/blob/master/

[openstack-dev] [Mistral] Query on creating multiple resources

2014-12-08 Thread Sushma Korati
Hi, Thank you guys. Yes I am able to do this with heat, but I faced issues while trying the same with mistral. As suggested will try with the latest mistral branch. Thank you once again. Regards, Sushma From: Georgy Okrokvertskhov [mailto:gokrokvertsk.

[openstack-dev] [Neutron][OVS] ovs-ofctl-to-python blueprint

2014-12-08 Thread YAMAMOTO Takashi
hi, here's a blueprint to make OVS agent use Ryu to talk with OVS. https://blueprints.launchpad.net/neutron/+spec/ovs-ofctl-to-python https://review.openstack.org/#/c/138980/ (kilo spec) given that ML2/OVS is one of the most popular plugins and the proposal has a few possible controvers

Re: [openstack-dev] [neutron] Changes to the core team

2014-12-08 Thread trinath.soman...@freescale.com
Congratulation Kevin and Henry ☺ -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Kyle Mestery [mailto:mest...@mestery.com] Sent: Monday, December 08, 2014 11:32 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron

Re: [openstack-dev] [Neutron] [RFC] Floating IP idea solicitation and collaboration

2014-12-08 Thread A, Keshava
Stephen, Interesting to know what is “ACTIVE-ACTIVE topology of load balancing VMs”. What is the scenario is it Service-VM (of NFV) or Tennant VM ? Curious to know the background of this thoughts . keshava From: Stephen Balukoff [mailto:sbaluk...@bluebox.net] Sent: Tuesday, December 09, 2014 7:

[openstack-dev] [Mistral] Query on creating multiple resources

2014-12-08 Thread Sushma Korati
Hello All, Can we create multiple resources using a single task, like multiple keypairs or security-groups or networks etc? I am trying to extend the existing "create_vm" workflow, such that it accepts a list of security groups. In the workflow, before create_vm I am trying to create the sec

[openstack-dev] [gantt] Scheduler sub-group meeting agenda 12/9

2014-12-08 Thread Dugger, Donald D
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST) 1) Status on cleanup work - https://wiki.openstack.org/wiki/Gantt/kilo -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 ___ OpenStack-dev mail

Re: [openstack-dev] [oslo.messaging] ZeroMQ driver maintenance next steps

2014-12-08 Thread Li Ma
Hi all, I tried to deploy zeromq by devstack and it definitely failed with lots of problems, like dependencies, topics, matchmaker setup, etc. I've already registered a blueprint for devstack-zeromq [1]. Besides, I suggest to build a wiki page in order to trace all the workitems related with Z

Re: [openstack-dev] [Compute][Nova] Mid-cycle meetup details for kilo

2014-12-08 Thread Michael Still
Wow, now we're up to 75% "sold" in just five hours. So... If you're stalling on registering please don't, as it sounds like I might need to ask the venue for more seats. Thanks, Michael On Tue, Dec 9, 2014 at 9:10 AM, Michael Still wrote: > Just a reminder that registration for the Nova mid-cycl

Re: [openstack-dev] [qa] How to delete a VM which is in ERROR state?

2014-12-08 Thread Danny Choi (dannchoi)
Both “delete” and “force-delete” did not work for me; they failed to remove the VM. Danny Date: Sun, 7 Dec 2014 21:17:30 +0530 From: foss geek mailto:thefossg...@gmail.com>> To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Subject: Re

Re: [openstack-dev] [Mistral] Event Subscription

2014-12-08 Thread W Chan
Renat, On sending events to an "exchange", I mean an exchange on the transport (i.e. rabbitMQ exchange https://www.rabbitmq.com/tutorials/amqp-concepts.html). On implementation we can probably explore the notification feature in oslo.messaging. But on second thought, this would limit the consume

Re: [openstack-dev] [Neutron] [RFC] Floating IP idea solicitation and collaboration

2014-12-08 Thread Stephen Balukoff
For what it's worth, I know that the Octavia project will need something which can do more advanced layer-3 networking in order to deliver and ACTIVE-ACTIVE topology of load balancing VMs / containers / machines. That's still a "down the road" feature for us, but it would be great to be able to do

[openstack-dev] [keystone][all] Max Complexity Check Considered Harmful

2014-12-08 Thread Brant Knudson
Not too long ago projects added a maximum complexity check to tox.ini, for example keystone has "max-complexity=24". Seemed like a good idea at the time, but in a recent attempt to lower the maximum complexity check in keystone[1][2], I found that the maximum complexity check can actually lead to l

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-08 Thread Jim Rollenhagen
On December 8, 2014 2:23:58 PM PST, Devananda van der Veen wrote: >I'd like to raise this topic for a wider discussion outside of the >hallway >track and code reviews, where it has thus far mostly remained. > >In previous discussions, my understanding has been that the Fuel team >sought to use

Re: [openstack-dev] [nova] Adding temporary code to nova to work around bugs in system utilities

2014-12-08 Thread Tony Breeds
On Mon, Dec 08, 2014 at 03:19:40PM -0500, Jay Pipes wrote: > I reviewed the patch. I don't mind the idea of a [workarounds] section of > configuration options, but I had an issue with where that code was executed. Thanks. Replied. > I think it would be fine to have a [workarounds] config sec

Re: [openstack-dev] [neutron] services split starting today

2014-12-08 Thread Kyle Mestery
Reminder: Neutron is still frozen for commits while we work through the services split. We hope to be have this done tomorrow sometime so we can un-freeze neutron. Thanks! Kyle On Mon, Dec 8, 2014 at 10:19 AM, Doug Wiegley wrote: > To all neutron cores, > > Please do not approve any gerrit revi

Re: [openstack-dev] [Mistral] Query on creating multiple resources

2014-12-08 Thread Georgy Okrokvertskhov
Hi Sushma, Did you explore Heat templates? As Zane mentioned you can do this via Heat template without writing any workflows. Do you have any specific use cases which you can't solve with Heat template? Create VM workflow was a demo example. Mistral potentially can be used by Heat or other orches

Re: [openstack-dev] [api] Using query string or request body to pass parameter

2014-12-08 Thread Kevin L. Mitchell
On Tue, 2014-12-09 at 07:38 +0800, Alex Xu wrote: > Not sure all, nova is limited > at > https://github.com/openstack/nova/blob/master/nova/api/openstack/wsgi.py#L79 > That under our control. It is, but the client frameworks aren't, and some of them prohibit sending a body with a DELETE request.

Re: [openstack-dev] Where should Schema files live?

2014-12-08 Thread Anne Gentle
On Mon, Dec 8, 2014 at 1:06 PM, Adam Young wrote: > Isn't this what the API repos are for? Should EG the Keystone schemes be > served from > > https://github.com/openstack/identity-api/ > > > The -api repos will go away once we have the merges completed for replacing with the -specs repo info.

Re: [openstack-dev] [api] Using query string or request body to pass parameter

2014-12-08 Thread Alex Xu
Not sure all, nova is limited at https://github.com/openstack/nova/blob/master/nova/api/openstack/wsgi.py#L79 That under our control. Maybe not just ask question for delete, also for other method. 2014-12-09 1:11 GMT+08:00 Kevin L. Mitchell : > On Mon, 2014-12-08 at 14:07 +0800, Eli Qiao wrote:

Re: [openstack-dev] [Keystone] OSAAA-Policy

2014-12-08 Thread Morgan Fainberg
As a quick note, the OpenStack Identity Program was not renamed to AAA (based upon the discussion with the TC) but increased scope to adopt Audit on top of the already included scope of Authorization and Authentication. Cheers, Morgan --  Morgan Fainberg On December 8, 2014 at 5:05:51 PM, Morga

Re: [openstack-dev] [Keystone] Mid-Cycle Meetup Dates/Time/Location

2014-12-08 Thread Morgan Fainberg
As promised, we have an update for venue, recommended hotels, and an RSVP form. I want to thank Geekdom and Rackspace for helping to put together and host the Keystone Midcycle. All updated information can be found at:  https://www.morganfainberg.com/blog/2014/11/18/keystone-hackathon-kilo/ Che

[openstack-dev] [neutron] mid-cycle arrival time Tuesday 12-9-2014

2014-12-08 Thread Kyle Mestery
Folks, per a request from Jun, for tomorrow's mid-cycle, if you could all arrive no earlier than 8:45, that would be great. Since we're in the smaller meeting rooms and/or cafeteria area tomorrow, this will allow Jun and the other Adobe hosts to arrive in time and set up for us. Thanks! Kyle _

Re: [openstack-dev] [Keystone] OSAAA-Policy

2014-12-08 Thread Morgan Fainberg
I agree that this library should not have “Keystone” in the name. This is more along the lines of pycadf, something that is housed under the OpenStack Identity Program but it is more interesting for general use-case than exclusively something that is tied to Keystone specifically. Cheers, Morga

[openstack-dev] [neutron] Abandoned patches for neutron and python-neutronclient

2014-12-08 Thread Kyle Mestery
As part of a broader cleanup I've been doing today, I went and abandoned a bunch of patches in both the neutron and python-neutronclient gerrit queues today. All of these were more than 2 months old. If you plan to continue working on these, please activate them again and propose new changes. But t

[openstack-dev] [Keystone] OSAAA-Policy

2014-12-08 Thread Adam Young
The Policy libraray has been nominated for promotion from Oslo incubator. The Keystone team was formally known as the Identity Program, but now is Authentication, Authorization, and Audit, or AAA. Does the prefeix OSAAA for the library make sense? It should not be Keystone-policy.

[openstack-dev] [Telco Work Group][Ecosystem & Collateral Team] Meeting information

2014-12-08 Thread Barrett, Carol L
The Ecosystem and Collateral team of the Telco Work Group is meeting on Tuesday 12/9 at 8:00 Pacific Time. If you're interested in collaborating to accelerate Telco adoption of OpenStack through ecosystem engagements and development of collateral (case studies, reference architectures, etc), pl

Re: [openstack-dev] [nova] bug 1334398 and libvirt live snapshot support

2014-12-08 Thread Kashyap Chamarthy
On Mon, Dec 08, 2014 at 09:12:24PM +, Jeremy Stanley wrote: > On 2014-12-08 11:45:36 +0100 (+0100), Kashyap Chamarthy wrote: > > As Dan Berrangé noted, it's nearly impossible to reproduce this issue > > independently outside of OpenStack Gating environment. I brought this up > > at the recently

Re: [openstack-dev] [cinder] HA issues

2014-12-08 Thread John Griffith
On Mon, Dec 8, 2014 at 8:18 AM, Dulko, Michal wrote: > Hi all! > > > > At the summit during crossproject HA session there were multiple Cinder > issues mentioned. These can be found in this etherpad: > https://etherpad.openstack.org/p/kilo-crossproject-ha-integration > > > > Is there any ongoing e

[openstack-dev] [Ironic] Fuel agent proposal

2014-12-08 Thread Devananda van der Veen
I'd like to raise this topic for a wider discussion outside of the hallway track and code reviews, where it has thus far mostly remained. In previous discussions, my understanding has been that the Fuel team sought to use Ironic to manage "pets" rather than "cattle" - and doing so required extendi

Re: [openstack-dev] [neutron][lbaas] Shared Objects in LBaaS - Use Cases that led us to adopt this.

2014-12-08 Thread Stephen Balukoff
So... I should probably note that I see the case where a user actually shares object as being the exception. I expect that 90% of deployments will never need to share objects, except for a few cases-- those cases (of 1:N) relationships are: * Loadbalancers must be able to have many Listeners * W

Re: [openstack-dev] [Cinder] Listing of backends

2014-12-08 Thread John Griffith
On Sun, Dec 7, 2014 at 5:35 AM, Pradip Mukhopadhyay wrote: > Thanks! > > One more question. > > Is there any equivalent API to add keys to the volume-type? I understand we > have APIs for creating volume-type? But how about adding key-value pair (say > I want to add-key to the volume-type as backe

Re: [openstack-dev] [Cinder]

2014-12-08 Thread John Griffith
cinder service-list will show all the backends Cinder knows about and their status. On Sun, Dec 7, 2014 at 2:52 AM, Pradip Mukhopadhyay wrote: > Hi, > > > Is there a way to find out/list down the backends discovered for Cinder? > > > There is, I guess, no API for get the list of backends. > > > >

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

2014-12-08 Thread Zane Bitter
On 08/12/14 07:00, Murugan, Visnusaran wrote: Hi Zane & Michael, Please have a look @ https://etherpad.openstack.org/p/execution-stream-and-aggregator-based-convergence Updated with a combined approach which does not require persisting graph and backup stack removal. Well, we still have to

Re: [openstack-dev] [Compute][Nova] Mid-cycle meetup details for kilo

2014-12-08 Thread Michael Still
Just a reminder that registration for the Nova mid-cycle is now open. We're currently 50% "sold", so early signup will help us work out if we need to add more seats or not. https://www.eventbrite.com.au/e/openstack-nova-kilo-mid-cycle-developer-meetup-tickets-14767182039 Thanks, Michael On Thu,

Re: [openstack-dev] [nova] bug 1334398 and libvirt live snapshot support

2014-12-08 Thread melanie witt
On Dec 8, 2014, at 13:12, Jeremy Stanley wrote: > I'm dubious of this as it basically says "we know this breaks > sometimes, so we're going to stop testing that it works at all and > possibly let it get even more broken, but you should be safe to rely > on it anyway." +1, it seems bad to enable

Re: [openstack-dev] [Neutron] Core/Vendor code decomposition

2014-12-08 Thread Maru Newby
On Dec 7, 2014, at 10:51 AM, Gary Kotton wrote: > Hi Kyle, > I am not missing the point. I understand the proposal. I just think that it > has some shortcomings (unless I misunderstand, which will certainly not be > the first time and most definitely not the last). The thinning out is to have

Re: [openstack-dev] [nova] bug 1334398 and libvirt live snapshot support

2014-12-08 Thread Jeremy Stanley
On 2014-12-08 11:45:36 +0100 (+0100), Kashyap Chamarthy wrote: > As Dan Berrangé noted, it's nearly impossible to reproduce this issue > independently outside of OpenStack Gating environment. I brought this up > at the recently concluded KVM Forum earlier this October. To debug this > any further,

[openstack-dev] [oslo] interesting problem with config filter

2014-12-08 Thread Doug Hellmann
As we’ve discussed a few times, we want to isolate applications from the configuration options defined by libraries. One way we have of doing that is the ConfigFilter class in oslo.config. When a regular ConfigOpts instance is wrapped with a filter, a library can register new options on the filt

[openstack-dev] [neutron] FYI: I just abandoned a large pile of specs

2014-12-08 Thread Kyle Mestery
Folks, not only is today Spec Proposal Deadline (SPD), I also made it "clear out all old specs" day. I went in and abandoned all specs which were still out there against Juno. If your spec was abandoned and you were miraculously going to propose a new version today during SPD, please do so. Otherwi

Re: [openstack-dev] [nova] Adding temporary code to nova to work around bugs in system utilities

2014-12-08 Thread Jay Pipes
On 12/03/2014 04:00 AM, Tony Breeds wrote: Hi All, I'd like to accomplish 2 things with this message: 1) Unblock (one way or another) https://review.openstack.org/#/c/123957 2) Create some form of consensus on when it's okay to add temporary code to nova to work around bugs in external u

Re: [openstack-dev] [Neutron] Neutron documentation to update about new vendor plugin, but without code in repository?

2014-12-08 Thread Vadivel Poonathan
Hi Anne, I provided my comment in the review itself.. and pasted below for your quick view. Thanks, Vad -- Vadivel Poonathan12:05 PM I understand the "other drivers" mean the external drivers which are not part of the official openstack repository. So the reference drivers which are part of the

Re: [openstack-dev] [Neutron] [RFC] Floating IP idea solicitation and collaboration

2014-12-08 Thread Carl Baldwin
Ryan, I'll be traveling around the time of the L3 meeting this week. My flight leaves 40 minutes after the meeting and I might have trouble attending. It might be best to put it off a week or to plan another time -- maybe Friday -- when we could discuss it in IRC or in a Hangout. Carl On Mon,

Re: [openstack-dev] Where should Schema files live?

2014-12-08 Thread Lance Bragstad
Keystone also has API documentation in the keystone-spec repo [1], which went in with [2] and [3]. [1] https://github.com/openstack/keystone-specs/tree/master/api [2] https://review.openstack.org/#/c/128712/ [3] https://review.openstack.org/#/c/130577/ On Mon, Dec 8, 2014 at 1:06 PM, Adam Young

Re: [openstack-dev] Where should Schema files live?

2014-12-08 Thread Adam Young
Isn't this what the API repos are for? Should EG the Keystone schemes be served from https://github.com/openstack/identity-api/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/opens

Re: [openstack-dev] [neutron] Changes to the core team

2014-12-08 Thread Paul Michali (pcm)
Way to go Kevin and Henry! PCM (Paul Michali) MAIL …..…. p...@cisco.com IRC ……..… pc_m (irc.freenode.com) TW ………... @pmichali GPG Key … 4525ECC253E31A83 Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83 On Dec 8, 2014, at 11:02 AM, Kyle Mestery wrote: > On Tue, Dec 2, 2014

Re: [openstack-dev] [third-party] Third-party CI account creation is now self-serve

2014-12-08 Thread Anita Kuno
On 12/08/2014 09:33 AM, Jay Pipes wrote: > On 12/03/2014 03:56 PM, Anita Kuno wrote: >> As of now third-party CI account creation is now self-serve. I think >> this makes everybody happy. >> >> What does this mean? >> >> Well for a new third-party account this means you follow the new >> process, o

Re: [openstack-dev] [neutron] Changes to the core team

2014-12-08 Thread Kyle Mestery
On Tue, Dec 2, 2014 at 9:59 AM, Kyle Mestery wrote: > Now that we're in the thick of working hard on Kilo deliverables, I'd > like to make some changes to the neutron core team. Reviews are the > most important part of being a core reviewer, so we need to ensure > cores are doing reviews. The sta

Re: [openstack-dev] [neutron] services split starting today

2014-12-08 Thread Kyle Mestery
Copying the operators list here to gain additional visibility for trunk chasers. On Mon, Dec 8, 2014 at 10:19 AM, Doug Wiegley wrote: > To all neutron cores, > > Please do not approve any gerrit reviews for advanced services code for > the next few days. We will post again when those reviews ca

Re: [openstack-dev] Where should Schema files live?

2014-12-08 Thread Eoghan Glynn
> >From: Sandy Walsh [sandy.wa...@rackspace.com] Monday, December 01, 2014 9:29 > >AM > > > >>From: Duncan Thomas [duncan.tho...@gmail.com] > >>Sent: Sunday, November 30, 2014 5:40 AM > >>To: OpenStack Development Mailing List > >>Subject: Re: [openstack-dev] Where should Schema files live? > >>

Re: [openstack-dev] [api] Using query string or request body to pass parameter

2014-12-08 Thread Kevin L. Mitchell
On Mon, 2014-12-08 at 14:07 +0800, Eli Qiao wrote: > I wonder if we can use body in delete, currently , there isn't any > case used in v2/v3 api. No, many frameworks raise an error if you try to include a body with a DELETE request. -- Kevin L. Mitchell Rackspace __

[openstack-dev] [mistral] Team meeting minutes/log 12/08/2014

2014-12-08 Thread Nikolay Makhotkin
Thanks for joining our team meeting today! * Meeting minutes: *http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-12-08-16.04.log.html * * Meeting log: *http://eavesdrop.openstack.org/meetings/

[openstack-dev] [Neutron] Freeze on L3 agent

2014-12-08 Thread Carl Baldwin
For the next few weeks, we'll be tackling L3 agent restructuring [1] in earnest. This will require some heavy lifting, especially initially, in the l3_agent.py file. Because of this, I'd like to ask that we not approve any non-critical changes to the L3 agent that are unrelated to this restructur

[openstack-dev] Remove XML support from Nova API

2014-12-08 Thread Davanum Srinivas
Hi Team, We currently have disabled XML support when https://review.openstack.org/#/c/134332/ merged. I've prepared a followup patch series to entirely remove XML support [1] soon after we ship K1. I've marked it as WIP for now though all tests are working fine. Looking forward to your feedback.

Re: [openstack-dev] [third-party] Third-party CI account creation is now self-serve

2014-12-08 Thread Jay Pipes
On 12/03/2014 03:56 PM, Anita Kuno wrote: As of now third-party CI account creation is now self-serve. I think this makes everybody happy. What does this mean? Well for a new third-party account this means you follow the new process, outlined here: http://ci.openstack.org/third_party.html#creat

Re: [openstack-dev] [neutron] services split starting today

2014-12-08 Thread Doug Wiegley
To all neutron cores, Please do not approve any gerrit reviews for advanced services code for the next few days. We will post again when those reviews can resume. Thanks, Doug On 12/8/14, 8:49 AM, "Doug Wiegley" wrote: >Hi all, > >The neutron advanced services split is starting today at 9am

Re: [openstack-dev] [Mistral] Query on creating multiple resources

2014-12-08 Thread Nikolay Makhotkin
Hi, Sushma! Can we create multiple resources using a single task, like multiple > keypairs or security-groups or networks etc? Yes, we can. This feature is in the development now and it is considered as experimental - https://blueprints.launchpad.net/mistral/+spec/mistral-dataflow-collections J

[openstack-dev] [neutron] services split starting today

2014-12-08 Thread Doug Wiegley
Hi all, The neutron advanced services split is starting today at 9am PDT, as described here: https://review.openstack.org/#/c/136835/ .. The remove change from neutron can be seen here: https://review.openstack.org/#/c/139901/ .. While the new repos are being sorted out, advanced services wi

[openstack-dev] Fwd: [Horizon] drag and drop widget in horizon.

2014-12-08 Thread uday bhaskar
We are looking for documentation for the widget used launch instance form of the horizon, where on the network tab, you are able to select networks in a particular order. How is this implemented? is there any widget available to reuse? any help is appreciated. Thanks Uday Bhaskar

Re: [openstack-dev] [Neutron] [RFC] Floating IP idea solicitation and collaboration

2014-12-08 Thread Ryan Clevenger
Thanks for getting back Carl. I think we may be able to make this weeks meeting. Jason Kölker is the engineer doing all of the lifting on this side. Let me get with him to review what you all have so far and check our availability. Ryan Clevenger Manag

Re: [openstack-dev] [Mistral] Query on creating multiple resources

2014-12-08 Thread Zane Bitter
On 08/12/14 09:41, Sushma Korati wrote: Can we create multiple resources using a single task, like multiple keypairs or security-groups or networks etc? Define them in a Heat template and create the Heat stack as a single task. - ZB ___ OpenStack-de

Re: [openstack-dev] [TripleO] CI report : 1/11/2014 - 4/12/2014

2014-12-08 Thread Derek Higgins
On 04/12/14 13:37, Dan Prince wrote: > On Thu, 2014-12-04 at 11:51 +, Derek Higgins wrote: >> A month since my last update, sorry my bad >> >> since the last email we've had 5 incidents causing ci failures >> >> 26/11/2014 : Lots of ubuntu jobs failed over 24 hours (maybe half) >> - We seem to

[openstack-dev] [Infra] Meeting Tuesday December 9th at 19:00 UTC

2014-12-08 Thread Elizabeth K. Joseph
Hi everyone, The OpenStack Infrastructure (Infra) team is hosting our weekly meeting on Tuesday December 9th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone interested

[openstack-dev] [cinder] HA issues

2014-12-08 Thread Dulko, Michal
Hi all! At the summit during crossproject HA session there were multiple Cinder issues mentioned. These can be found in this etherpad: https://etherpad.openstack.org/p/kilo-crossproject-ha-integration Is there any ongoing effort to fix these issues? Is there an idea how to approach any of them

[openstack-dev] [MagnetoDB][api] Hello from the API WG

2014-12-08 Thread Everett Toews
Hello MagnetoDB! During the latest meeting [1] of the API Working Group (WG) we noticed that MagnetoDB made use of the APIImpact flag [2]. That’s excellent and exactly how we were hoping the use of flag as a discovery mechanism would work! We were wondering if the MagentoDB team would like to d

Re: [openstack-dev] [Fuel][Nailgun] Web framework

2014-12-08 Thread Ryan Petrello
Feel free to ask any questions you have in #pecanpy on IRC; I can answer a lot more quickly than researching docs, and if you have a special need, I can usually accommodate with changes to Pecan (I've done so with several OpenStack projects in the past). On 12/08/14 02:10 PM, Nikolay Markov wrote:

[openstack-dev] [Mistral] Query on creating multiple resources

2014-12-08 Thread Sushma Korati
Hello All, Can we create multiple resources using a single task, like multiple keypairs or security-groups or networks etc? I am trying to extend the existing "create_vm" workflow, such that it accepts a list of security groups. In the workflow, before create_vm I am trying to create the sec

Re: [openstack-dev] [nova] Host health monitoring

2014-12-08 Thread Roman Dobosz
On Wed, 3 Dec 2014 08:44:57 +0100 Roman Dobosz wrote: > I've just started to work on the topic of detection if host is alive or > not: https://blueprints.launchpad.net/nova/+spec/host-health-monitoring > > I'll appreciate any comments :) I've submitted another blueprint, which is closely bounde

Re: [openstack-dev] Where should Schema files live?

2014-12-08 Thread Sandy Walsh
>From: Sandy Walsh [sandy.wa...@rackspace.com] Monday, December 01, 2014 9:29 AM > >>From: Duncan Thomas [duncan.tho...@gmail.com] >>Sent: Sunday, November 30, 2014 5:40 AM >>To: OpenStack Development Mailing List >>Subject: Re: [openstack-dev] Where should Schema files live? >> >>Duncan Thomas >>

Re: [openstack-dev] [OpenStack-Infra][ThirdPartyCI] Need help setting up CI

2014-12-08 Thread Eduard Matei
Resending this to dev ML as it seems i get quicker response :) I created a job in Jenkins, added as Build Trigger: "Gerrit Event: Patchset Created", chose as server the configured Gerrit server that was previously tested, then added the project openstack-dev/sandbox and saved. I made a change on d

Re: [openstack-dev] [nova] V3 API support

2014-12-08 Thread Sergey Nikitin
Thank you guys for helpful information. Alex, I'll remove v2 schema and add v2.1 support 2014-12-08 8:01 GMT+03:00 Alex Xu : > I think Chris is on vacation. We move V3 API to V2.1. V2.1 have some > improvement compare to V2. You can find more detail at > http://specs.openstack.org/openstack/nova-

Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for Additional Meeting for third-party

2014-12-08 Thread trinath.soman...@freescale.com
With Kurt Taylor. +1 Very nice idea to start with. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Kurt Taylor [mailto:kurt.r.tay...@gmail.com] Sent: Friday, December 05, 2014 8:39 PM To: OpenStack Development Mailing List (not for usage questions); openstack-in..

Re: [openstack-dev] [nova][neutron] Boundary between Nova and Neutron involvement in network setup?

2014-12-08 Thread Neil Jerram
Hi Wu, As I've also written in a comment at https://review.openstack.org/#/c/130732/6, it appears that VIF_TYPE_VHOSTUSER is already covered by the approved spec at https://review.openstack.org/#/c/96138/. Given that, is there any reason to consider adding VIF_TYPE_VHOSTUSER into the VIF_TYPE_TAP

Re: [openstack-dev] [nova] Fixing the console.log grows forever bug.

2014-12-08 Thread Daniel P. Berrange
On Mon, Dec 08, 2014 at 01:20:19PM +, Dave Walker wrote: > On 8 December 2014 at 10:33, Daniel P. Berrange wrote: > > On Sat, Dec 06, 2014 at 04:38:52PM +1100, Tony Breeds wrote: > >> Hi All, > >> In the most recent team meeting we briefly discussed: [1] where the > >> console.log grows in

Re: [openstack-dev] [nova] Fixing the console.log grows forever bug.

2014-12-08 Thread Dave Walker
On 8 December 2014 at 10:33, Daniel P. Berrange wrote: > On Sat, Dec 06, 2014 at 04:38:52PM +1100, Tony Breeds wrote: >> Hi All, >> In the most recent team meeting we briefly discussed: [1] where the >> console.log grows indefinitely, eventually causing guest stalls. I mentioned >> that I was

Re: [openstack-dev] [Nova] Spring cleaning nova-core

2014-12-08 Thread Sean Dague
On 12/07/2014 12:02 PM, Jay Pipes wrote: > On 12/07/2014 04:19 AM, Michael Still wrote: >> On Sun, Dec 7, 2014 at 7:03 PM, Gary Kotton wrote: >>> On 12/6/14, 7:42 PM, "Jay Pipes" wrote: >> >> [snip] >> -1 on pixelbeat, since he's been active in reviews on various things AFAICT in the la

Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for Additional Meeting for third-party

2014-12-08 Thread Erlon Cruz
I agree that 2 meetings per week will mess things up. 1+ for alternating meetings. On Fri, Dec 5, 2014 at 1:08 PM, Kurt Taylor wrote: > In my opinion, further discussion is needed. The proposal on the table is > to have 2 weekly meetings, one at the existing time of 1800UTC on Monday > and, also

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

2014-12-08 Thread Murugan, Visnusaran
Hi Zane & Michael, Please have a look @ https://etherpad.openstack.org/p/execution-stream-and-aggregator-based-convergence Updated with a combined approach which does not require persisting graph and backup stack removal. This approach reduces DB queries by waiting for completion notification

Re: [openstack-dev] [nova] bug 1334398 and libvirt live snapshot support

2014-12-08 Thread Kashyap Chamarthy
On Fri, Dec 05, 2014 at 02:12:44PM -0600, Matt Riedemann wrote: > > > On 12/5/2014 1:32 PM, Sean Dague wrote: > >On 12/05/2014 01:50 PM, Matt Riedemann wrote: > >>In Juno we effectively disabled live snapshots with libvirt due to bug > >>1334398 [1] failing the gate about 25% of the time. > >> >

Re: [openstack-dev] [nova] Fixing the console.log grows forever bug.

2014-12-08 Thread Daniel P. Berrange
On Sat, Dec 06, 2014 at 04:38:52PM +1100, Tony Breeds wrote: > Hi All, > In the most recent team meeting we briefly discussed: [1] where the > console.log grows indefinitely, eventually causing guest stalls. I mentioned > that I was working on a spec to fix this issue. > > My original plan wa

Re: [openstack-dev] [nova] bug 1334398 and libvirt live snapshot support

2014-12-08 Thread Daniel P. Berrange
On Fri, Dec 05, 2014 at 12:50:37PM -0600, Matt Riedemann wrote: > In Juno we effectively disabled live snapshots with libvirt due to bug > 1334398 [1] failing the gate about 25% of the time. > > I was going through the Juno release notes today and saw this as a known > issue, which reminded me of

Re: [openstack-dev] [Nova] Spring cleaning nova-core

2014-12-08 Thread Daniel P. Berrange
On Sun, Dec 07, 2014 at 08:19:54PM +1100, Michael Still wrote: > On Sun, Dec 7, 2014 at 7:03 PM, Gary Kotton wrote: > > On 12/6/14, 7:42 PM, "Jay Pipes" wrote: > > [snip] > > >>-1 on pixelbeat, since he's been active in reviews on > >>various things AFAICT in the last 60-90 days and seems to be

Re: [openstack-dev] [MagnetoDB] Intercycle release package versioning

2014-12-08 Thread isviridov
Hello Aleksei, Thanks for rising it. I'm ok with it and let me clarify the source code repo state for each to releases. 1:2014.2-0ubuntu1 tag: 2014.2 fixes in stable/juno 1:2014.2~rc2-0ubuntu1 tag: 2014.2.rc2 fixes in master 1:2014.2~b2-0ubuntu1 tag: 2014.2.b2 fixed in master 1:2014

Re: [openstack-dev] [Nova] Spring cleaning nova-core

2014-12-08 Thread Daniel P. Berrange
On Sat, Dec 06, 2014 at 07:56:21AM +1100, Michael Still wrote: > I used Russell's 60 day stats in making this decision. I can't find a > documented historical precedent on what period the stats should be > generated over, however 60 days seems entirely reasonable to me. > > 2014-12-05 15:41:11.212

Re: [openstack-dev] [Fuel][Nailgun] Web framework

2014-12-08 Thread Nikolay Markov
> Yes, and it's been 4 days since last message in this thread and no > objections, so it seems > that Pecan in now our framework-of-choice for Nailgun and future > apps/projects. We still need some research to do about technical issues and how easy we can move to Pecan. Thanks to Ryan, we now have

Re: [openstack-dev] [Nova] Spring cleaning nova-core

2014-12-08 Thread Nikola Đipanov
On 12/07/2014 08:52 PM, Michael Still wrote: > > You know what makes me really sad? No one has suggested that perhaps > Padraig could just pick up his review rate a little. I've repeatedly > said we can re-add reviewers if that happens. > This is of course not true - everybody *but* the people o

Re: [openstack-dev] [git] Rebase failed

2014-12-08 Thread Eduard Matei
Indeed, it started again the review process. Thanks for your input. Eduard On Mon, Dec 8, 2014 at 10:56 AM, Gary Kotton wrote: > Hi, > The whole review process starts again from scratch :). You can feel free > to reach out the guys who originally reviewed and then go from there. Good > luck! >

Re: [openstack-dev] [git] Rebase failed

2014-12-08 Thread Jan Kundrát
On Monday, 8 December 2014 09:57:15 CEST, Jan Kundrát wrote: On Monday, 8 December 2014 09:25:43 CEST, Eduard Matei wrote: So i removed it locally (git rm ... ) and now rebase worked, but now i had an extra patchset. Will this be merged automatically or does it need again reviewers ? Make sure

Re: [openstack-dev] [git] Rebase failed

2014-12-08 Thread Gary Kotton
Hi, The whole review process starts again from scratch :). You can feel free to reach out the guys who originally reviewed and then go from there. Good luck! Thanks Gary From: Eduard Matei mailto:eduard.ma...@cloudfounders.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>

Re: [openstack-dev] [git] Rebase failed

2014-12-08 Thread Jan Kundrát
On Monday, 8 December 2014 09:25:43 CEST, Eduard Matei wrote: So i removed it locally (git rm ... ) and now rebase worked, but now i had an extra patchset. Will this be merged automatically or does it need again reviewers ? Make sure you have a single commit which includes both the `git rm` and

Re: [openstack-dev] [nova] Fixing the console.log grows forever bug.

2014-12-08 Thread Thierry Carrez
Tony Breeds wrote: > [...] > So if that timeline is approximately correct: > > - Can we wait this long to fix the bug? As opposed to having it squashed in > Kilo. > - What do we do in nova for the next ~12 months while know there isn't a qemu > to fix this? > - Then once there is a qemu that fi

Re: [openstack-dev] [git] Rebase failed

2014-12-08 Thread Eduard Matei
Thanks guys, It seems one of the files i was trying to merge was actually removed by remote (?). So i removed it locally (git rm ... ) and now rebase worked, but now i had an extra patchset. Will this be merged automatically or does it need again reviewers ? Thanks, Eduard On Mon, Dec 8, 2014 at

Re: [openstack-dev] [Nova] Spring cleaning nova-core

2014-12-08 Thread Gary Kotton
Hi, I would expect that if a core does not understand a piece of code then he/she would not approve it they can always give a +1 and be honest that it is not part of the code base that they understand. That is legitimate in such a complex and large project. We all make mistakes, it is the only w

Re: [openstack-dev] [git] Rebase failed

2014-12-08 Thread Sylvain Bauza
Le 08/12/2014 09:13, Eli Qiao a écrit : 在 2014年12月08日 16:05, Eduard Matei 写道: Hi, My review got approved and it was ready to merge but automatic merge failed. I tried to rebase manually but it still fails. I'm not very familiar with git, can someone give a hand? git rebase -i master error

Re: [openstack-dev] [git] Rebase failed

2014-12-08 Thread Gary Kotton
Hi, I do the following: 1. Go to master branch. git checkout master 2. Get latest master code: git pull 3. Checkout you code: git checkout yourbranchname 4. Rebase this on the laster master: git rebase -i master 5. Resolve conflicts: git status (this will show conflicts) 6. Resol

  1   2   >