Re: [openstack-dev] [all] cross project communication: Return request-id to caller

Did you get to talk with anyone in the LogWG ( https://wiki.openstack.org/wiki/LogWorkingGroup )? In wonder what kind of recommendations, standards we can come up with while adopting a cross project solution. If our logs follow certain prefix and or suffix style across projects, that would help a l

Re: [openstack-dev] [neutron] [fwaas] - Collecting use cases for API improvements

Hello All, The session talk was mainly about merging the Security Group API and the FWaaS API to the same one or to keep them separate, Which i don't think we reached agreement (or did we? :) ) I personally think (And few people approached us in the summit to express that they feel the same) that

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

Oh, on the wiki page I read that "The liaison should be a core reviewer for the project, but does not need to be the PTL.". I'm not a core reviewer for nova. Is it an issue? On the wiki page, I see that John Villalovos (happycamp) is the Nova liaison for Oslo, not Joe Goron. I don't understand

Re: [openstack-dev] [nova] "correct" API for getting image metadata for an instance ?

On Wed, May 27, 2015 at 02:59:10PM +0100, Daniel P. Berrange wrote: > As part of the work to object-ify the image metadata dicts, I'm looking > at the current way the libvirt driver fetches image metadata for an > instance, in cases where the compute manager hasn't already passed it > into the virt

Re: [openstack-dev] [new][app-catalog] App Catalog next steps

On Wed, May 27, 2015 at 5:33 PM, Joe Gordon wrote: > > > On Wed, May 27, 2015 at 4:27 PM, Fox, Kevin M wrote: > >> I'd say, tools that utilize OpenStack, like the knife openstack plugin, >> are not something that you would probably go to the catalog to find. And >> also, the recipes that you wo

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

On 28/05/15 09:20 +0200, Victor Stinner wrote: Oh, on the wiki page I read that "The liaison should be a core reviewer for the project, but does not need to be the PTL.". I'm not a core reviewer for nova. Is it an issue? This was more like a general recommendation, I guess. I don't think the l

Re: [openstack-dev] [TripleO] [Puppet] Package updates strategy

On 05/28/2015 01:10 AM, Steve Baker wrote: On 28/05/15 10:54, Richard Raseley wrote: Zane Bitter wrote: Steve is working on a patch to allow package-based updates of overcloud nodes[1] using the distro's package manager (yum in the case of RDO, but conceivable apt in others). Note we're talking

Re: [openstack-dev] [all] cross project communication: Return request-id to caller

Hi Nikhil, Thanks for the opinion, actually I was in different time-zone and was not aware about this LogWG. I will certainly approach them in next meeting. Thank you, Abhishek Kekane -Original Message- From: Nikhil Komawar [mailto:[email protected]] Sent: 28 May 2015 12:34 To: op

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

Victor, reproducing John 's liason message. Copied John. -Original Message- From: John Garbutt [mailto:[email protected]] Sent: Saturday, May 09, 2015 3:10 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova][Ironic] Large number of iro

[openstack-dev] [Fuel] 6.1 Release - new dates for HCF and GA

Hello everyone, We keep putting our best efforts to hit Hard Code Freeze goals. Latest test results are 68% pass rate for Ubuntu and 65% for CentOS. Once the remaining bugs are closed, we will be able to hit 70% target for sure. Based on the feedback from Engineering leads, with current incom

[openstack-dev] [neutron] Impressions from Vancouver Neutron Design Summits

Hello All, I wanted to very briefly share my thoughts and a suggestion regarding the Neutron design summits (maybe only for the next one, but still..) I would first like to say that i was amazed by the number of people that attended the summit, it was really great to see it and it was very nice m

Re: [openstack-dev] [neutron] [fwaas] - Collecting use cases for PI improvements

Hi! ;) On Thursday, 28 de May de 2015 at 9:03, Gal Sagie wrote: > Hello All, > > The session talk was mainly about merging the Security Group API and the > FWaaS API to the same one or to keep them separate, > Which i don't think we reached agreement (or did we? :) ) I can’t tell either ;)

Re: [openstack-dev] [TripleO] [Puppet] Package updates strategy

On 05/28/2015 09:35 AM, Jan Provaznik wrote: On 05/28/2015 01:10 AM, Steve Baker wrote: On 28/05/15 10:54, Richard Raseley wrote: Zane Bitter wrote: One solution proposed was to do a yum update first but specifically exclude any packages that Puppet knows about (the --excludes flag appears

Re: [openstack-dev] [fuel][plugin][astute][UI] DSL restrictions with an action: "none" to display a message?

Many thanks Julia for the quick fix! Is it possible to update my fuel master to test this patch? w/o download a new ISO and avoid to reinstall my env ? On Wed, May 27, 2015 at 6:04 PM, Julia Aranovich wrote: > Hi, > > That's an issue of course. Settings definitely should support 'none' > actio

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

Victor -- error on my part for filling wrong table. I put your name instead of John's. Thanks to Tan Lin for pointing out my error. All the best. Regards Malini -Original Message- From: Bhandaru, Malini K [mailto:[email protected]] Sent: Thursday, May 28, 2015 1:05 AM To: Flavio

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

Derek, Thanks for what you wrote. On 05/27/2015 11:26 PM, Derek Higgins wrote: >> 4. For deb packages you can create new repositories along side the >> rdorpm-* repositories My intention is to use deb-* as prefix, if Canonical team agrees. >> 5. Add deb support to delorean, I know of at least

Re: [openstack-dev] [TripleO] [Puppet] Package updates strategy

On 05/28/2015 10:25 AM, Martin Mágr wrote: On 05/28/2015 09:35 AM, Jan Provaznik wrote: On 05/28/2015 01:10 AM, Steve Baker wrote: On 28/05/15 10:54, Richard Raseley wrote: Zane Bitter wrote: One solution proposed was to do a yum update first but specifically exclude any packages that Pupp

Re: [openstack-dev] oslo.vmware release 0.13.0 (liberty)

Hi, We have reverted the problematic patch (I suggest that you all add the word balagan to your lexicons). Anyways, the plan forwards is as follows: 1. To update the nova code to use the correct exceptions and to ensure that it will not break moving forwards 2. To clean up the exceptions i

Re: [openstack-dev] [neutron] Impressions from Vancouver Neutron Design Summits

Thanks for the feedback. What to discuss at the summit has always been an issue. The only issue I see with your proposal is that you assume we can agree on high-level things on the mailing list. One of the reasons to discuss high-level things at the summit is that its a great place to get operator

[openstack-dev] Nodepool: puppet fails to create image

Hi, We had some issues with jenkins/devstack so i updated both the jenkins version and the devstack. When starting nodepool it tries to create a new image but it fails after ~5 minutes: 2015-05-28 10:49:21,509 ERROR nodepool.image.build.local_01.d-p-c: + sudo puppet apply --detailed-exitcodes --m

Re: [openstack-dev] [nova] "correct" API for getting image metadata for an instance ?

+1 But we should answer the following question before switching libvirt to utils.get_image_from_system_metadata. Some differences of utils.get_image_from_system_metadata from compute.utils.get_image_metadata are: 1) Instance metadata has a restriction of property length: long data is stripped to 2

Re: [openstack-dev] [nova] "correct" API for getting image metadata for an instance ?

On Thu, May 28, 2015 at 11:55:59AM +0300, Feodor Tersin wrote: > +1 > But we should answer the following question before switching libvirt to > utils.get_image_from_system_metadata. > > Some differences of utils.get_image_from_system_metadata from > compute.utils.get_image_metadata are: > 1) Insta

Re: [openstack-dev] [TripleO] [Puppet] Package updates strategy

On 05/28/2015 10:47 AM, Jan Provaznik wrote: On 05/28/2015 10:25 AM, Martin Mágr wrote: On 05/28/2015 09:35 AM, Jan Provaznik wrote: On 05/28/2015 01:10 AM, Steve Baker wrote: On 28/05/15 10:54, Richard Raseley wrote: Zane Bitter wrote: One solution proposed was to do a yum update first

Re: [openstack-dev] [neutron] Impressions from Vancouver Neutron Design Summits

Hi Kevin, The main idea that i tried to express, is we need a course of action after the discussions, i understand that we want to discuss high level points but we still need to decide on a follow up plan, because otherwise this is all wasted. What i was suggesting is that we apply action items i

Re: [openstack-dev] [fuel][plugin][astute][UI] DSL restrictions with an action: "none" to display a message?

You can setting up fake dev environment [1] based on the latest master, run 'npm install && gulp bower' from fuel-web/nailgun directory to load uncompressed ui and its dependencies and replace nailgun/static dir with compressed ui on your master node by the static dir from fake environment. But th

Re: [openstack-dev] [nova] "correct" API for getting image metadata for an instance ?

I mean the case: - an image has long property AAA and non inheritable property BBB; - an instance based on the image stores truncated AAA and full BBB; - utils.get_image_from_system_metadata returns truncated AAA but not BBB; - compute.utils.get_image_metadata updates the result of utils.get_image_

Re: [openstack-dev] [nova] "correct" API for getting image metadata for an instance ?

On Thu, May 28, 2015 at 12:22:59PM +0300, Feodor Tersin wrote: > I mean the case: > - an image has long property AAA and non inheritable property BBB; > - an instance based on the image stores truncated AAA and full BBB; > - utils.get_image_from_system_metadata returns truncated AAA but not BBB; >

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

That's right. The oslo team is OK with the liaison to other teams not being a core reviewer. -- dims On Thu, May 28, 2015 at 3:35 AM, Flavio Percoco wrote: > On 28/05/15 09:20 +0200, Victor Stinner wrote: >> >> Oh, on the wiki page I read that "The liaison should be a core reviewer >> for the pr

Re: [openstack-dev] [Manila] Expected Manila behavior for creation of share from snapshot

Isn't this similar to what cinder transfer-* cmds are for ? Ability to transfer cinder volume across tenants So Manila should be implementing the transfer-* cmds, after which admin/user can create a clone then initiate a transfer to a diff tenant ? On Wed, May 27, 2015 at 6:08 PM, Valeriy Ponomar

Re: [openstack-dev] [neutron] Impressions from Vancouver Neutron Design Summits

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've heard that other projects come up with actual action lists and work assignments. I've heard Nova, Ironic, Oslo do it, and I witnessed just that in those Oslo sessions I had a chance to visit. So Neutron can be special in this regard and may not

Re: [openstack-dev] [oslo] Updates from the Summit

On Wed, May 27, 2015 at 08:47:42AM -0400, Davanum Srinivas wrote: > Hi Team, > > Here are the etherpads from the summit[1]. I remember that in Taskflow's Fishbowl session we discussed not only pause/yield option but abort/cancel for long running tasks as well, but reviewing the Etherpad now I don

Re: [openstack-dev] [oslo] Updates from the Summit

Please add it Gorka. thanks, dims On Thu, May 28, 2015 at 6:23 AM, Gorka Eguileor wrote: > On Wed, May 27, 2015 at 08:47:42AM -0400, Davanum Srinivas wrote: >> Hi Team, >> >> Here are the etherpads from the summit[1]. > > I remember that in Taskflow's Fishbowl session we discussed not only > pau

[openstack-dev] [Fuel][Plugins] Instructions on plugin versioning

Hi to all, The Fuel Plugins wiki page now contains instructions on versioning [1]. Feel free to review&ask questions. [1] https://wiki.openstack.org/wiki/Fuel/Plugins#Plugin_versioning_system -- Best regards, Irina PI Te

[openstack-dev] [Fuel] [Plugins] type available

Hi folks, is there anyway in the environment_config.yaml file of the plugin to define some attrobutes as title (something similar to the the metadata in the openstack.yaml of fuel-web). I would like to add somes titles in the plugin config in order to define section into the ui for the plugin and

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

Hi Thomas, Delorean is a tool to build rpm packages from master branches (maybe any branch?) of OpenStack projects. Check out here: https://www.rdoproject.org/packaging/rdo-packaging.html#master-pkg-guide Regards, On Thu, 28 May 2015 10:40, Thomas Goirand wrote: > Derek, > > Thanks for what y

Re: [openstack-dev] [oslo] Updates from the Summit

On 27/05/15 10:24 -0700, Joshua Harlow wrote: Thanks dims! indeed, thanks. [snip] Also for the pika one, I'd really like to understand why not kombu. I don't know enough of the background, but from that session it looks like we need to do some comparative analysis (and imho get feedback f

Re: [openstack-dev] [Manila] [Cinder] About how to hide the dummy destination record during migration

This manilla feature is essentially the same as the admin metadata already attached to the volume in cinder, but with a slightly nicer internal API. It could be used for migration, though the fields essentially map onto almost all of the fields already in a volume; that isn't necessarily a problem,

Re: [openstack-dev] [Manila] Expected Manila behavior for creation of share from snapshot

On 28 May 2015 at 13:03, Deepak Shetty wrote: > Isn't this similar to what cinder transfer-* cmds are for ? Ability to > transfer cinder volume across tenants > So Manila should be implementing the transfer-* cmds, after which > admin/user can create a clone > then initiate a transfer to a diff t

Re: [openstack-dev] [oslo] Updates from the Summit

Flavio, PIka is an unknown quantity at the moment as none of us have touched it. It was brought up by rabbitmq folks. So someone should look at it. We don't have have enough info either to say we should use Pika by itself or as a kombu driver. We may have to make that determination at some point i

Re: [openstack-dev] [new][app-catalog] App Catalog next steps

Hi folks, I believe that at least part of the filtering we are discussing here may be done at the client side if the client is sophisticated enough to be aware about the capabilities of the local cloud. And by "sophisticated client" I mean "Glance V3" (previously known as "Artifact Repository"), w

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/28/2015 01:07 PM, Jaume Devesa wrote: > Hi Thomas, > > Delorean is a tool to build rpm packages from master branches > (maybe any branch?) of OpenStack projects. It's now also used for stable/kilo. I suspect all supported branches starting fr

Re: [openstack-dev] [Fuel] [Plugins] type available

Hello Samuel, AFAIK there is no such feature yet. The schema validators are here [1] [2]. BR, Simon [1] https://github.com/stackforge/fuel-plugins/blob/master/fuel_plugin_builder/fuel_plugin_builder/validators/schemas/base.py [1] https://github.com/stackforge/fuel-plugins/blob/master/fuel_plugin_b

Re: [openstack-dev] [all] IRC meetings agenda is now driven from Gerrit !

On Wed, May 27, 2015 at 04:53:38PM +0200, Thierry Carrez wrote: > Hi everyone, > > TL;DR: > IRC meetings list now lives at http://eavesdrop.openstack.org > ical file with meetings is now at > http://eavesdrop.openstack.org/irc-meetings.ical This is very nice work indeed - must better than the wik

[openstack-dev] [ceilometer] today's meeting cancelled

‎Hi,Just a reminder, since a few people are still on vacation from the summit, we'll skip today's meeting. We'll continue our regularly scheduled meetings on June 4‎.Please check out the roundup email and current specs to see what is planned going forward.For any urgent items, please post to the l

Re: [openstack-dev] [all] IRC meetings agenda is now driven from Gerrit !

Daniel P. Berrange wrote: > There are a huge number of openstack meetings now, but I think that > each individual person will only be interested in a handful of them. > Adding the irc-meetings.ical to a calendar app really pollutes your > personal schedule, and calendar apps I've seen don't make it

[openstack-dev] [Fuel] [Plugins] type available

Samuel, Could you please report a bug in Fuel project [1] and provide more details? Thanks a lot! [1] https://bugs.launchpad.net/fuel/+filebug -- Best regards, Irina PI Team Technical Writer skype: ira_live Trello board: https://trello.com/b/3nxd5wFq/irina-povolotskaya-tasks-tracking-board _

[openstack-dev] [Fuel][Plugins] Bug triage recommendations were updated

Hi to all, Please, note that bug triage recommendations were updated with more specific examples [1]. Feel free to review&comment. [1] https://wiki.openstack.org/wiki/Fuel/Plugins#Bugs -- Best regards, Irina PI Team Technical Writer skype: ira_live Trello board: https://trello.com/b/3nxd5wFq/

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

On 28/05/15 12:07, Jaume Devesa wrote: Hi Thomas, Delorean is a tool to build rpm packages from master branches (maybe any branch?) of OpenStack projects. Check out here: https://www.rdoproject.org/packaging/rdo-packaging.html#master-pkg-guide Following those instructions you'll notice that

Re: [openstack-dev] [neutron] [fwaas] - Collecting use cases for PI improvements

On Thu, May 28, 2015 at 3:13 AM, Miguel Ángel Ajo wrote: > Hi! ;) > > On Thursday, 28 de May de 2015 at 9:03, Gal Sagie wrote: > > Hello All, > > The session talk was mainly about merging the Security Group API and the > FWaaS API to the same one or to keep them separate, > Which i don't think we

Re: [openstack-dev] [nova] Availability of device names for operations with volumes and BDM and other features.

Nikola, thank you for the explanation. So here is what we have problems with now (I might not be completely correct in some facts and guesses though): The following review made it worse for us initially: https://review.openstack.org/#/c/59034/25 As I understand in this review you replaced sto

Re: [openstack-dev] [oslo] Updates from the Summit

Flavio, yay! :) -- dims On Thu, May 28, 2015 at 9:24 AM, Flavio Percoco wrote: > On 28/05/15 07:34 -0400, Davanum Srinivas wrote: >> >> Flavio, >> >> PIka is an unknown quantity at the moment as none of us have touched >> it. It was brought up by rabbitmq folks. So someone should look at it. >>

Re: [openstack-dev] [oslo] Updates from the Summit

On 28/05/15 07:34 -0400, Davanum Srinivas wrote: Flavio, PIka is an unknown quantity at the moment as none of us have touched it. It was brought up by rabbitmq folks. So someone should look at it. We don't have have enough info either to say we should use Pika by itself or as a kombu driver. We

Re: [openstack-dev] [openstackclient] About my blueprint every-time-record-log-in-file

Dear Dean Troyer, and openstackclient team members, Thank you for your review with Takanori Miyagishi at OSC's meetup session in Vancouver! So, I reflected the indications of the review in the blueprint. https://blueprints.launchpad.net/python-openstackclient/+spec/every-time-record-log-in-fil

[openstack-dev] [neutron] Proposing Assaf Muller for the Neutron Core Reviewer Team

Folks, I'd like to propose Assaf Muller to be a member of the Neutron core reviewer team. Assaf has been a long time contributor in Neutron, and he's also recently become my testing Lieutenant. His influence and knowledge in testing will be critical to the team in Liberty and beyond. In addition to

Re: [openstack-dev] [nova] "correct" API for getting image metadata for an instance ?

Yes, my mistake. I missed that utils.get_image_from_system_metadata just converts a passed metadata, but do not get metadata from the instance. So non-inhertable properties are omitted in both result sets. But compute.utils.get_image_metadata returns not trucated long properties. It reads truncate

[openstack-dev] [neutron] The new Lieutenant system in Neutron

As part of the team's continuing effort to scale development in Neutron, we have officially merged the Lieutenant patch [1]. As the codebase continues to grow, this is an attempt to scale the code review load so we can grow new core reviewers while maintaining the model of trust required to success

Re: [openstack-dev] [neutron] Proposing Assaf Muller for the Neutron Core Reviewer Team

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 +1 and more! On 05/28/2015 03:42 PM, Kyle Mestery wrote: > Folks, I'd like to propose Assaf Muller to be a member of the > Neutron core reviewer team. Assaf has been a long time contributor > in Neutron, and he's also recently become my testing Lieu

Re: [openstack-dev] [neutron] Proposing Assaf Muller for the Neutron Core Reviewer Team

+1 On Thu, May 28, 2015, Kyle Mestery wrote: > Folks, I'd like to propose Assaf Muller to be a member of the Neutron core > reviewer team. Assaf has been a long time contributor in Neutron, and he's > also recently become my testing Lieutenant. His influence and knowledge in > testing will be cri

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

Excerpts from Davanum Srinivas (dims)'s message of 2015-05-28 06:02:24 -0400: > That's right. The oslo team is OK with the liaison to other teams not > being a core reviewer. I've updated the wiki to reflect that. Doug __ Op

Re: [openstack-dev] [Ironic][oslo] Stepping down from oslo-ironic liaison

Thanks Doug! On Thu, May 28, 2015 at 10:10 AM, Doug Hellmann wrote: > Excerpts from Davanum Srinivas (dims)'s message of 2015-05-28 06:02:24 -0400: >> That's right. The oslo team is OK with the liaison to other teams not >> being a core reviewer. > > I've updated the wiki to reflect that. > > Dou

Re: [openstack-dev] [neutron] Proposing Assaf Muller for the Neutron Core Reviewer Team

+1 On Thu, May 28, 2015 at 5:01 PM, Henry Gessau wrote: > +1 > > On Thu, May 28, 2015, Kyle Mestery wrote: > > Folks, I'd like to propose Assaf Muller to be a member of the Neutron > core > > reviewer team. Assaf has been a long time contributor in Neutron, and > he's > > also recently become m

Re: [openstack-dev] [neutron] Proposing Assaf Muller for the Neutron Core Reviewer Team

+1 Great addition to the team! Yeah! Edgar From: Kyle Mestery mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]>> Date: Thursday, May 28, 2015 at 6:42 AM To: "OpenStack Development Mailing List (not f

Re: [openstack-dev] [neutron] Proposing Assaf Muller for the Neutron Core Reviewer Team

+1 From: Oleg Bondarev mailto:[email protected]>> Reply-To: OpenStack List mailto:[email protected]>> Date: Thursday, May 28, 2015 at 5:31 PM To: OpenStack List mailto:[email protected]>> Subject: Re: [openstack-dev] [neutron] Proposing Assaf Muller for the N

[openstack-dev] [Javascript] Summit Conversation Continued

Hey everyone! We had an _excellent_ discussion in Vancouver, but with only 40 minutes to discuss things we didn't reach consensus on many topics that we really needed to hash out. In order to make sure that the rest of this list is addressed, I'm including a summary of the discussion here and will

Re: [openstack-dev] [Nova] Using depends-on for patches which require an approved spec

On 5/27/2015 7:21 PM, John Griffith wrote: On Wed, May 27, 2015 at 12:15 PM, Joe Gordon mailto:[email protected]>> wrote: On Tue, May 26, 2015 at 8:45 AM, Daniel P. Berrange mailto:[email protected]>> wrote: On Fri, May 22, 2015 at 02:57:23PM -0700, Michael Still wro

Re: [openstack-dev] [nova] I think nova behaves poorly when booting multiple instances

I know there were discussions during the summit on how to fix quota bugs, and in particular the multi instance code was making the solution harder. I agree with you though, if the api is to stay, the current behavior seems broken. Thanks, Kevin From: Chr

Re: [openstack-dev] [TripleO] [Puppet] Package updates strategy

On Thu, May 28, 2015 at 5:02 AM, Martin Mágr wrote: > > On 05/28/2015 10:47 AM, Jan Provaznik wrote: >> >> On 05/28/2015 10:25 AM, Martin Mágr wrote: >>> >>> >>> On 05/28/2015 09:35 AM, Jan Provaznik wrote: On 05/28/2015 01:10 AM, Steve Baker wrote: > > On 28/05/15 10:54, Richard

Re: [openstack-dev] Nodepool: puppet fails to create image

On 2015-05-28 11:58:43 +0300 (+0300), Eduard Matei wrote: > We had some issues with jenkins/devstack so i updated both the jenkins > version and the devstack. > When starting nodepool it tries to create a new image but it fails after ~5 > minutes: > > 2015-05-28 10:49:21,509 ERROR nodepool.image.b

Re: [openstack-dev] [neutron] Proposing Assaf Muller for the Neutron Core Reviewer Team

+1 Doug > On May 28, 2015, at 7:42 AM, Kyle Mestery wrote: > > Folks, I'd like to propose Assaf Muller to be a member of the Neutron core > reviewer team. Assaf has been a long time contributor in Neutron, and he's > also recently become my testing Lieutenant. His influence and knowledge in

Re: [openstack-dev] [Zaqar][all] Zaqar will stay... Lots of work ahead

On 05/27/2015 05:08 PM, Hayes, Graham wrote: It was agreed that Zaqar would look at a oslo_messaging driver for the services that did not agree with the 3 options presented. Another option there would be to add amqp 1.0 support to zaqar, and then you could use the amqp 1.0 driver with zaqar as

[openstack-dev] [all] Liberty release management and tracking

Hi everyone, TL;DR: - In an effort to reduce useless work, in Liberty we'll switch from trying to accurately predict what will end up in milestones to reporting what actually landed. - We'll also replace weekly release management 1:1 sync points with office hours. - For Liberty we'll have two r

Re: [openstack-dev] [oslo] Updates from the Summit

Feel free to add it, or open a blueprint, or make a spec to :) Any of the above are ok with me. I did start prototyping something @ https://review.openstack.org/#/c/184663/ (external cancellation) but it might be going in the wrong direction (or a different direction); so feel free to comment

[openstack-dev] [heat] Heat Template Cookbook

[This was originally posted to [email protected] by accident. Reposting it to openstack-dev.] Calling all Heat neophytes, aficionados, and everyone in between ... I've often thought it would be helpful to add a Heat Template Cookbook to the developer documentation. Like any helping

Re: [openstack-dev] [Zaqar][all] Zaqar will stay... Lots of work ahead

Thats like saying you should implement a sql engine inside of Berkeley DB since so many folks like sql... Not a good fit. If you want AMQP, get an AMQP server. Zaqar's intentionally lighter weight then that. Hardly any OpenStack services use but a fraction of AMQP though, so getting oslo.messagi

Re: [openstack-dev] [heat] Heat Template Cookbook

+1 I've been placing mine out at: https://github.com/EMSL-MSC/heat-templates/tree/master/cfn I've split common patterns into a reusable library under: https://github.com/EMSL-MSC/heat-templates/tree/master/cfn so that users don't have to reimplement any of those things themselves. They aren't p

[openstack-dev] [Ironic] [TC] Discussion: changing Ironic's release model

Hi all, tl;dr; At the summit, the Ironic team discussed the challenges we've had with the current release model and came up with some ideas to address them. I had a brief follow-up conversation with Doug and Thierry, but I'd like this to be discussed more openly and for us (the Ironic dev communi

Re: [openstack-dev] [Fuel] vxlan support

VxLAN support cannot be made as a plugin because plugins cannot modify the initial networking wizard (based on conversations I've had in #fuel-dev) where the choices between Neutron VLAN, Neutron GRE, and nova-network are shown to the user. I am currently working on this blueprint and have a WIP p

Re: [openstack-dev] [Ironic] [TC] Discussion: changing Ironic's release model

On 05/28/2015 12:41 PM, Devananda van der Veen wrote: > Hi all, > > tl;dr; > > At the summit, the Ironic team discussed the challenges we've had with > the current release model and came up with some ideas to address them. > I had a brief follow-up conversation with Doug and Thierry, but I'd > li

Re: [openstack-dev] [Zaqar][all] Zaqar will stay... Lots of work ahead

On 05/28/2015 05:14 PM, Fox, Kevin M wrote: Thats like saying you should implement a sql engine inside of Berkeley DB since so many folks like sql... Not a good fit. If you want AMQP, get an AMQP server. Zaqar's intentionally lighter weight then that. Hardly any OpenStack services use but a fract

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

Hi Oleksii, Thanks for putting together the slides, they are well done and extremely useful! I find this 0MQ driver redesign proposal a much needed improvement over the current design. However it is worth debating the need to keep the proxy server and I would be interested to hear from others a

Re: [openstack-dev] [Manila] [Cinder] About how to hide the dummy destination record during migration

For Share Migration, I am looking into integrating it with "Private Driver Storage" as Valeriy mentioned. The purpose is in fact different than not displaying the volume being migrated to the user, we are attempting to not use a temporary DB entry at all. I am not sure how this will play out, espec

Re: [openstack-dev] [puppet] OpenStack Puppet modules boilerplate

This is great work guys. Can we add it to the wiki too? Also +2 on the name from Emilien. On Fri, May 22, 2015 at 6:12 PM, Emilien Macchi wrote: > > > On 05/22/2015 04:53 PM, Sebastien Badia wrote: > > Hi, > > > > During the Puppet session (during the Vancouver summit), we talked about > > a bo

Re: [openstack-dev] [Ironic] [TC] Discussion: changing Ironic's release model

> On May 28, 2015, at 9:54 AM, Monty Taylor wrote: > > On 05/28/2015 12:41 PM, Devananda van der Veen wrote: >> Hi all, >> >> tl;dr; >> >> At the summit, the Ironic team discussed the challenges we've had with >> the current release model and came up with some ideas to address them. >> I had a

Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support

Hi Kunal, I would like to participate as well. Mon-Fri morning US Pacific time works for me. Thanks, Rakesh Saha On Tue, May 26, 2015 at 8:45 PM, Vijay Venkatachalam < [email protected]> wrote: > We would like to participate as well. > > > > Monday-Friday Morning US time works for

[openstack-dev] [merlin] [horizon] [heat] [mistral] Merlin & HotBuilder - what's next?

Hello there! First, for those of you who hadn't been at Horizon design session where I was telling & showing the Merlin framework, here is the related etherpad [1] and the demo slides themselves [2]. Merlin wasn't the only thing shown at that design session, I hope that some video of HotBuilder de

Re: [openstack-dev] [oslo] Updates from the Summit

Btw, if u *do not* want to do a spec (using [1]) or blueprint let me know and I'll probably make a spec so that we can ensure (and agree on) the semantics of this because the specifics of what 'cancel' or 'abort' means start to matter. [1] https://github.com/openstack/oslo-specs/blob/master/sp

Re: [openstack-dev] [Manila] [Cinder] About how to hide the dummy destination record during migration

On 05/28/2015 01:14 PM, Rodrigo Barbieri wrote: For Share Migration, I am looking into integrating it with "Private Driver Storage" as Valeriy mentioned. The purpose is in fact different than not displaying the volume being migrated to the user, we are attempting to not use a temporary DB entry

Re: [openstack-dev] taskflow usage

ESWAR RAO wrote: Hi All, I am looking into taskflow userguide and examples. http://www.giantflyingsaucer.com/blog/?p=4896 I also started aggregating these on: https://wiki.openstack.org/wiki/TaskFlow#Blogs.2Ftutorials If people know of more/others please add :-) Thanks! Can anyone pleas

Re: [openstack-dev] [Zaqar][all] Zaqar will stay... Lots of work ahead

I don't know AMQP very well. At the protocol level, are Exchanges, Queues, etc things? Are fanout, durability, and other things required or optional to be implemented? Thanks, Kevin From: Gordon Sim [[email protected]] Sent: Thursday, May 28, 2015 10:05 AM

Re: [openstack-dev] [TripleO] [Puppet] Package updates strategy

On 28/05/15 03:35, Jan Provaznik wrote: On 05/28/2015 01:10 AM, Steve Baker wrote: On 28/05/15 10:54, Richard Raseley wrote: Zane Bitter wrote: Steve is working on a patch to allow package-based updates of overcloud nodes[1] using the distro's package manager (yum in the case of RDO, but conce

Re: [openstack-dev] [all] Liberty release management and tracking

Comments/praise in-line. On 5/28/15 11:54 AM, Thierry Carrez wrote: > Hi everyone, > > TL;DR: > > - In an effort to reduce useless work, in Liberty we'll switch from > trying to accurately predict what will end up in milestones to reporting > what actually landed. Glad to hear. > - We'll also repl

Re: [openstack-dev] [new][app-catalog] App Catalog next steps

Makes sense to me. Has the Glance Artifact Repository implemented enough bits to have Heat and/or Murano artefacts yet? Also, has there been any work on Exporting/Importing them through some defined format (tarball?) that doesn't depend on the artefact type? I've been talking with the Heat folk

Re: [openstack-dev] [nova] "correct" API for getting image metadata for an instance ?

> As part of the work to object-ify the image metadata dicts, I'm looking > at the current way the libvirt driver fetches image metadata for an > instance, in cases where the compute manager hasn't already passed it > into the virt driver API. I see 2 methods that libvirt uses to get the > image me

Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support

I haven’t seen any responses from my team yet, but I know we’d be interested as well — we have done quite a bit of work on this in the past, including dealing with the Designate team on this very subject. We can be available most hours between 9am-6pm Monday-Friday CST. --Adam https://keybase.

Re: [openstack-dev] [TripleO] [Puppet] Package updates strategy

while more effort, you could write a script that took a package name, and gave back the whole set of rpm/versions that it depended on, then write that to a file. If the list of rpm/versions from the previous run changes, then have puppet kick the process? Thanks, Kevin _

[openstack-dev] [Glance] [all] glance_store release 0.6.0

The glance_store release management team is pleased to announce: Release of glance_store version 0.6.0 Please find the details related to the release at: https://launchpad.net/glance-store/liberty/0.6.0 Please report the issues through launchpad: https://bugs.launchpad.net/glance-s

Re: [openstack-dev] [neutron] Impressions from Vancouver Neutron Design Summits

On 28 May 2015 at 03:09, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > I've heard that other projects come up with actual action lists and > work assignments. I've heard Nova, Ironic, Oslo do it, and I witnessed > just that in those Oslo sessions I had a chance to

Re: [openstack-dev] [kolla] Add core approver Sam Yaple

+1 From: "Steven Dake (stdake)" mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]>> Date: Monday, May 25, 2015 at 11:59 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:opensta

Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support

On 28/05/15 19:38, Adam Harwell wrote: > I haven’t seen any responses from my team yet, but I know we’d be > interested as well — we have done quite a bit of work on this in the > past, including dealing with the Designate team on this very subject. We > can be available most hours between 9am-6pm

Re: [openstack-dev] [Fuel] vxlan support

Hi, Sean, A plugin cannot modify Fuel UI but it actually can change a segmentation type after deployment. On UI it's still GRE but in fact it will be VxLAN. I know, it's ugly, but should work. On Thu, May 28, 2015 at 7:47 PM, Sean M. Collins wrote: > VxLAN support cannot be made as a plugin bec

  1   2   >