[openstack-dev] [Murano] Nominating Kirill Zaitsev for murano-core

I'd like to propose Kirill Zaitsev to core members of Murano team. Kirill Zaitsev is active member of our community, he implemented several blueprint in Kilo and fixed number of bugs, he maintains a really good score as contributor: http://stackal

[openstack-dev] [Murano] Nominating Filip Blaha for murano-core

Folks, I'd like to propose Filip Blaha to core members of Murano team. Filip is active member of our community and he maintains a good score as contributor: http://stackalytics.com/report/users/filip-blaha Existing Murano cores, please vote +1/-1 for the addition of Filip to the murano-core. --

Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel

-1. I disagree. I am not convinced that requiring names is a good idea. I've asked several times why there is a desire to require names, and I'm not seeing any persuasive arguments that are not already addressed by UUIDs. We have UUID values to allow for acting upon an individual resource. Name

Re: [openstack-dev] [Neutron] virtual machine can not get DHCP lease due packet has no checksum

I would propose a back-port of it and then continue the discussion on the patch. I don't see any major blockers for back-porting it. On Mon, Jun 1, 2015 at 7:01 PM, Tidwell, Ryan wrote: > Not seeing this on Kilo, we're seeing this on Juno builds (that's > expected). I'm interested in a Juno bac

[openstack-dev] [Fuel] Hard Code Freeze status update - Just 1st 8PM PDT

Hello everyone, We keep fixing bugs with a decent pace, but we received 2 critical and 10+ high new bugs from QA today. All manageable, but we need 1 more day to close them out and do smoke testing. So, ETA for HardCodeFreeze is June 3rd. Today's stats: Bugs left: 7 bugs + 17 incomplete. A

Re: [openstack-dev] [murano] oslo namespace changes and murano-dashboard

Hi Doug, sorry for the late response, I was traveling a little bit after the summit. I've released python-muranoclient 0.6.0 with requirements changes made by you. We use new release policy for libraries, so versions >=0.5.6,<0.6.0 correspond to Kilo release, and >=0.6 correspond to the Liberty:

[openstack-dev] Scheduler sub-group (gantt) meeting 6/2

Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT) 1) Liberty summit recap - https://etherpad.openstack.org/p/YVR-nova-scheduler-in-liberty 2) Updating concept of resource - Ed Leafe's email thread 3) Opens -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 _

Re: [openstack-dev] [all] upcoming oslo releases

Doug, Here's the updated tip of the trees that i have tested by hand against at least Nova. 0.5.0 8f4100a debtcollector 1.10.0 9a963a9 oslo.concurrency 1.12.0 cc9940f oslo.config 0.4.0 23f81ea oslo.context 1.10.0 42dc936 oslo.db 1.7.0 7935c3f oslo.i18n 1.3.0 1d64c91 oslo.log 1.12.0 5181361 os

Re: [openstack-dev] [Neutron] virtual machine can not get DHCP lease due packet has no checksum

Not seeing this on Kilo, we're seeing this on Juno builds (that's expected). I'm interested in a Juno backport, but mainly wanted to be see if others had confidence in the fix. The discussion in the bug report also seemed to indicate there were other alternative solutions others might be looki

Re: [openstack-dev] [cinder] Consider using Explicit type casts on filters

Not a DB expert but looks like a valid bug. Do you mind file a bug on this? On Mon, Jun 1, 2015 at 5:43 PM, Vasco Rodrigues wrote: > Running Cinder on postgresql, i get the following error: > > 2015-06-02 01:21:27.471 32698 DEBUG cinder.api.v2.volumes > [req-a0a15e07-2a86-4f98-a371-2f7203706b9f

Re: [openstack-dev] [Neutron][LBaaS] No LBaaS agent?

Hi Wanjing We at PayPal/eBay have integrated with a multi-vendor solution. One of the vendor solution is agent less and off loads all the business logic to a vendor controller that manages the devices. Regards Kunal > On Jun 1, 2015, at 4:52 PM, Wanjing Xu wrote: > > Is there a way to add a

Re: [openstack-dev] [Neutron][LBaaS] No LBaaS agent?

I missed the part about wanting to do your own event handling. Brandon is right, the right thing to do is to make yourself a driver. You can start with the noop_driver in this review, though some of the import paths will need fixing up: https://review.openstack.org/#/c/56187/

Re: [openstack-dev] [Neutron] virtual machine can not get DHCP lease due packet has no checksum

> On Jun 1, 2015, at 7:26 PM, Tidwell, Ryan wrote: > > I see a fix for https://bugs.launchpad.net/neutron/+bug/1244589 merged during > Kilo. I'm wondering if we think we have identified a root cause and have > merged an appropriate long-term fix, or if > https://review.openstack.org/148718 w

[openstack-dev] [all] error codes design conclusion?

Hey guys, I remember there was a session in design summit talking about openstack error codes. What's the current status? or is there any conclusion yet? Kun __ OpenStack Development Mailing List (not for usage questions) Uns

Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel

+1 about Jay option. BTW, as nova and glance all allow same name for instance or image, So name seems not need to be unique, it is OK I think. Thanks Best Wishes, Kai Qiang Wu (吴开强 Kennan） IBM China System and Te

Re: [openstack-dev] [Neutron][LBaaS] No LBaaS agent?

For v2 there is the logging noop driver that does not use an agent and just logs. v1 sits not have this though. I do wonder why you don't just build a simple driver to do what you are currently doing when acting upon events in the notification queue. On Jun 1, 2015 7:09 PM, "Fox, Kevin M" wr

Re: [openstack-dev] [DevStack][Neutron] PHYSICAL_NETWORK vs. PUBLIC_PHYSICAL_NETWORK - rant

> Thanks for the clarification. Do you think that there are cases where > the value for PHYSICAL_NETWORK and PUBLIC_PHYSICAL_NETWORK will be different? No, I cannot find the cases. I think it’s traditional something. > Perhaps we can change the default value for PUBLIC_PHYSICAL_NETWORK from > "p

[openstack-dev] [cinder] Consider using Explicit type casts on filters

Running Cinder on postgresql, i get the following error: 2015-06-02 01:21:27.471 32698 DEBUG cinder.api.v2.volumes [req-a0a15e07-2a86-4f98-a371-2f7203706b9f e8bd9bfef65c4def9d3977993c56b9b0 9dbebc529a0a469cb4574c3f9c0d86f7 - - -] Could not evaluate value 1, assuming string _get_volumes /usr/lib/py

Re: [openstack-dev] [cinder] Spec for volume migration improvement

Hi Vincent, >>@Mitsuhiro Tanino, I believe you can submit another spec for the efficient >>migration as well. Yup, I posted a SPEC and got some positive feedbacks. https://review.openstack.org/#/c/186209/ Also I posted some comments for your spec. Waiting your next update for the spec. Thanks,

Re: [openstack-dev] [Neutron][LBaaS] No LBaaS agent?

Have a look here: http://git.openstack.org/cgit/openstack/neutron-lbaas/tree/neutron_lbaas/drivers Thanks, Kevin From: Wanjing Xu [wanjing...@hotmail.com] Sent: Monday, June 01, 2015 4:52 PM To: OpenStack Development Mailing List not for usage questions Subject: [o

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

fyi, the spec for zeromq driver in oslo.messaging is here: https://review.openstack.org/#/c/187338/1/specs/liberty/zmq-patterns-usage.rst,unified -- dims On Thu, May 28, 2015 at 1:07 PM, Alec Hothan (ahothan) wrote: > Hi Oleksii, > > Thanks for putting together the slides, they are well done and

Re: [openstack-dev] [Neutron][LBaaS] No LBaaS agent?

The reference implemenation for lbaas (using haproxy with namespaces) requires the agent. There are vendor implementations that are agent-less, but not the reference. There is a non-agent ref driver for lbaas v2, but there is no horizon support for v2, and that driver is unsupported beyond dev

[openstack-dev] [Neutron][LBaaS] No LBaaS agent?

Is there a way to add an LBaaS service without having to use neutron plugin/agent framework? I want to add a LBaaS service without an LBaaS agent running and still want to have lb cli and horizon. When the user configure loadbalance via cli or horizon, neutron will send the events(pool, member

[openstack-dev] [Neutron] virtual machine can not get DHCP lease due packet has no checksum

I see a fix for https://bugs.launchpad.net/neutron/+bug/1244589 merged during Kilo. I'm wondering if we think we have identified a root cause and have merged an appropriate long-term fix, or if https://review.openstack.org/148718 was merged just so there's at least a fix available while we inve

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

On 28 May 2015 at 15:55, Jim Rollenhagen wrote: > ... > I also put an informational spec about this change up in the > ironic-specs repo: https://review.openstack.org/#/c/185171/. My goal was > to discuss this in the spec, but the mailing list is fine too. There are > some unanswered questions in

Re: [openstack-dev] [Magnum] Discuss mesos-bay-type Blueprint

Hi Jay, For your question “what is the mesos object that we want to manage”, the short answer is it depends. There are two options I can think of: 1. Don’t manage any object from Marathon directly. Instead, we can focus on the existing Magnum objects (i.e. container), and implements them

Re: [openstack-dev] [all] upcoming oslo releases

Matt, we are reverting that change - https://review.openstack.org/#/c/187306/ - so no need for any caps. that change will go to a feature branch for later. We can decide version numbers etc later and add caps if needed at that time. -- dims On Mon, Jun 1, 2015 at 5:38 PM, Matt Riedemann wrote:

Re: [openstack-dev] [release][manila] python-manilaclient 1.2.0

On 06/01/2015 10:47 AM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2015-06-01 10:27:38 -0400: We are thrilled to announce the release of: python-manilaclient 1.2.0: Client library for OpenStack Manila API. With source available at: http://git.openstack.org/cgit/opensta

Re: [openstack-dev] [all] upcoming oslo releases

On 6/1/2015 12:04 PM, Doug Hellmann wrote: We have a bunch of Oslo libraries ready for releases tomorrow, Tuesday 2 June. I will be releasing: 0.5.0 8685171 debtcollector 1.10.0 9a963a9 oslo.concurrency 1.12.0 02a86d2 oslo.config 0.4.0 4c9b37d oslo.context 1.10.0 42dc936 oslo.db 1.7.0 a02d901

[openstack-dev] [Neutron] service chaining feature development meeting at 1800 UTC June 4th

Hello everyone, I have set up the weekly IRC meeting for the OpenStack service chain feature development. Following is the meeting info: Weekly on Thursday at 1800 UTC in #openstack-meeting-4 You can also find the meet

Re: [openstack-dev] [nova] Progressing/tracking work on libvirt / vif drivers

Hi Neil, First of all thank for organizing this. Both Infiniband SR-IOV VIF type and Removal of mlnx_direct VIF type are ready for core review. -Original Message- From: Neil Jerram [mailto:neil.jer...@metaswitch.com] Sent: Monday, June 01, 2015 8:38 PM To: openstack-dev@list

[openstack-dev] [cognitive] any meeting details yet?

I was interested in the announcement of Cognitive. Are there any details on the upcoming meetings? Will details be announced on this mailing list? Thanks! __ OpenStack Development Mailing List (not for usage questions) Uns

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

Thanks for the summary Devananda. Lots of juicy features to sink our teeth into :-) There was a session with Nova, to discuss HA of nova compute nodes (and Nova's resource model) as it pertains to Ironic. What does a potential future look like? --ruby _

Re: [openstack-dev] [nova] Mellanox CI Issues

Hi Dan, I disabled Mellanox Nova CI from commenting and will check this issue first thing tomorrow morning. Thanks and my deepest apologies. Lenny Verkhovsky -Original Message- From: Dan Smith [mailto:d...@danplanet.com] Sent: Monday, June 01, 2015 7:41 PM To: OpenStack Development Mai

Re: [openstack-dev] [Fuel] [Plugins] modification disk configuration

Samuel, I cases like glance, and nova, you will likely want the volumes still because they are still used in some cases as cache(glance), operational files(nova-compute), or even interim storage(nova-compute) of snapshots. We keep them around even when we use Ceph. In the case of cinder, I'm assu

[openstack-dev] [neutron] Reminder: meeting tomorrow

We've had a few weeks off, but tomorrow we'll re-start the Neutron meeting [1]. It's at 1400 UTC in #openstack-meeting. See you all there! Thanks, Kyle [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Develop

[openstack-dev] [puppet] Weekly meeting #36

Hi everyone, Here's an initial agenda for our weekly meeting tomorrow at 1500 UTC in #openstack-meeting-4: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150602 Please add additional items you'd like to discuss. Colleen ___

Re: [openstack-dev] [nova] Add new VIF Type

On 06/01/2015 11:13 AM, Andreas Scheuring wrote: Hi, what are the prereqs to get a spec for a new nova VIF type approved? In my case I'm planning for a new neutron ml2 driver and agent (on stackforge) that adds general support for macvtap to neutron. I've not yet published anything regarding the

Re: [openstack-dev] [release][neutron] python-neutronclient 2.6.0

Excerpts from Ihar Hrachyshka's message of 2015-06-01 16:43:36 +0200: > I have a suggestion... Since it's not obvious now which stable branch > a release corresponds to, can we add that info into release note email > body somewhere for the sake of those who may closely track stable > updates but no

Re: [openstack-dev] [DevStack][Neutron] PHYSICAL_NETWORK vs. PUBLIC_PHYSICAL_NETWORK - rant

On Thu, May 28, 2015 at 09:40:12PM EDT, Hirofumi Ichihara wrote: > Hi Sean, > > > We have a *lot* of configuration knobs in DevStack for Neutron. I am not > > a smart man, so I think we may need to wrap our arms around this and > > simplify. > I agree with you. I want to fix the confused configure

Re: [openstack-dev] [nova] Progressing/tracking work on libvirt / vif drivers

On 01/06/15 17:45, Neil Jerram wrote: Many thanks, John & Dan. I'll start by drafting a summary of the work that I'm aware of in this area, at https://etherpad.openstack.org/p/liberty-nova-libvirt-vif-work. OK, my first draft of this is now there at [1]. Please could folk with VIF-related w

[openstack-dev] [chef] OpenStack-Chef client-cookbook hacking

://etherpad.openstack.org/p/openstack-chef-meeting-20150601 <https://etherpad.openstack.org/p/openstack-chef-meeting-20150601> [2]: http://doodle.com/gvn3v2t76czewwg6 [3]: https://github.com/stackforge/cookbook-openstack-client <https://github.com/stackforge/cookbook-opensta

Re: [openstack-dev] [Manila] Midcycle meetup dates

Week of July 27-31 works better for me. I'd vote for Wed-Thu, but other days should work. From: Ben Swartzlander [b...@swartzlander.org] Sent: Saturday, May 30, 2015 7:11 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [opens

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

On 2015-06-01 14:55:06 +0200 (+0200), Thomas Goirand wrote: [...] > So, should I start writing a script to build an image for package > building (ie: an image with sbuild, git-buildpackage, and so on...)? [...] Probably what we'd want to do is something like debootstrap/rpmstrap a chroot for each

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

On June 1, 2015 at 1:03:08 PM, Jeremy Stanley (fu...@yuggoth.org) wrote: > > Since pip treats .postN in strange ways, it's not entirely safe to > rely on the old PBR behavior which would have made this > 2.25.0.post8. In particular, if we were to ever upload that to PyPI > (terrible idea I know

[openstack-dev] [all] upcoming oslo releases

We have a bunch of Oslo libraries ready for releases tomorrow, Tuesday 2 June. I will be releasing: 0.5.0 8685171 debtcollector 1.10.0 9a963a9 oslo.concurrency 1.12.0 02a86d2 oslo.config 0.4.0 4c9b37d oslo.context 1.10.0 42dc936 oslo.db 1.7.0 a02d901 oslo.i18n 1.3.0 6754d13 oslo.log 1.12.0 27efb3

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

On 2015-06-01 08:53:41 -0400 (-0400), Doug Hellmann wrote: [...] > pbr generates versions like x.y.z.postN on each commit now, indicating N > commits since the x.y.z tag. So I think we're OK with version numbers > without having to do any tagging explicitly. [...] Well, technically x.y.(z+1).devN

Re: [openstack-dev] [nova] Progressing/tracking work on libvirt / vif drivers

On 01/06/15 14:23, Daniel P. Berrange wrote: On Mon, Jun 01, 2015 at 09:44:24AM +0100, John Garbutt wrote: On 29 May 2015 at 18:32, Neil Jerram wrote: Hi all, Per yesterday's IRC meeting [1], and discussion in Vancouver, Nova work is being somewhat driven by the etherpad at [2]. But this eth

Re: [openstack-dev] Barbican : Regarding the API support for Order and Consumer Resource

Thanks a lot John for your response :) On Mon, Jun 1, 2015 at 3:02 AM, John Vrbanac wrote: > Asha, > > We haven't removed anything. Unfortunately, no one has had the chance to > port those resources over from the old github wiki page and into the new > sphinx format yet. Also, yes they are stil

Re: [openstack-dev] [Glance] [all] Liberty summit: Updates in Glance

On Monday, June 1, 2015 05:30, John Garbutt wrote: On 1 June 2015 at 13:10, Flavio Percoco wrote: >> AFAIK, the biggest issue right now is "changed-since" which is >> something Glance doesn't have in v2 but it's exposed throught Nova's >> image API. > > Thats the big unanswered question that nee

[openstack-dev] [nova] Mellanox CI Issues

Hi, Mellanox CI has been broken for a while now. Test runs are reported as "successful" after an impossibly short less-than-a-minute run. Could the owners of this please take a look and address the problem? At least disabling commenting while working on the issue would be helpful. Also, on succes

Re: [openstack-dev] [akanda] meeting time change

Note that the 11am PDT meeting has moved to the #openstack-meeting channel On Sun, May 31, 2015 at 2:20 PM, sean roberts wrote: > Starting tomorrow, the akanda project will be meeting on > #openstack-meeting at 11:00 PDT. Agenda is in the usual place > https://wiki.openstack.org/wiki/Meetings/ak

[openstack-dev] [neutron][vnaas] IRC Meeting scheduled for June 2nd...

Since we had a bunch of interest at the Summit in VPN, we'll hold a meeting at our time-slot, Tuesday, 1600 UTC, openstack-meeting-3, tomorrow on June 2nd. I updated the agenda. If you have other updates, please add them to the wiki page: https://wiki.openstack.org/wiki/Meetings/VPNaaS Regards,

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2015-06-01 10:30:33 +0200: >> Doug Hellmann wrote: >>> Please let me know if you think I missed any details, or misunderstood >>> something as agreed to. Or, of course, if you weren’t there and see >>> something wrong with the plan

[openstack-dev] [Infra] Meeting Tuesday June 2nd at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday June 2nd, 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

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 2015-06-01 15:57:17 + (+), Jeremy Stanley wrote: [...] > The biggest hurdle is that we'd need a separate upload job name > for those since the current version of Zuul lacks a way to run a > particular job for different branches in different pipelines (we'd > want to do versioned uploads

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 2015-06-01 12:20:22 +0100 (+0100), Dimitri John Ledkov wrote: [...] > If the stable tarball snapshots had stable, ever increasing names, I > would switch to using those straight away. (Out of which $ git > describe --tags satisfies said requirement) Current PBR releases already create monotonic

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 2015-06-01 17:32:03 +0200 (+0200), Alan Pevec wrote: [...] > and *Plan D* would be to start doing automatic per-project > micro-versions on each commit: e.g. 2015.1.N where N is increased on > each commit. There's just TBD item how to provide source tarballs for > this. [...] That would happen

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 2015-06-01 12:04:34 +0200 (+0200), Thierry Carrez wrote: > Thierry Carrez wrote: [...] > > 2. it would be difficult to get proper release notes > > > > If we don't have point releases anymore, we don't have release notes > > anymore. Release notes contain various types of information: the list

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

2015-06-01 17:32 GMT+02:00 Alan Pevec : >> *Plan C* would be to just let projects tag stable point releases from >> time to time. That would solve all the original stated problems. And >> that would solve objections 2 and 3, which I think are the most valid ones. > > and *Plan D* would be to start

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 6/1/15, 06:20, "Dimitri John Ledkov" wrote: >On 29 May 2015 at 14:41, Thierry Carrez wrote: >> Hi everyone, >> >> TL;DR: >> - We propose to stop tagging coordinated point releases (like 2015.1.1) >> - We continue maintaining stable branches as a trusted source of stable >> updates for all p

Re: [openstack-dev] [qa] Need volunteers for tempest bug triage

On 05/30/2015 09:15 AM, Kashyap Chamarthy wrote: On Sat, May 30, 2015 at 03:52:02PM +0300, Yaroslav Lobankov wrote: Hi everyone, Is it possible for other people (not only core reviewers) to participate in bug triage? I would like to help in doing this. Absolutely. There's no such silly rule th

Re: [openstack-dev] [Neutron][bgpvpn] IRC meetings on BGP VPN interconnection API

Hi, We confirm this meeting for tomorrow Tuesday 2nd @15:00 UTC on #openstack-meeting-alt . We'll discuss tomorrow what we want to do for future IRC meetings (day, time, periodicity, etc.). (Everyone is encouraged to also follow the VPNaaS meeting that will follow) Best, -Thomas 2015-05-2

Re: [openstack-dev] [Neutron][bgpvpn] IRC meetings on BGP VPN interconnection API

Hi Paul, all, Yes, it's good to have a discussion on BGP VPN and edge VPN proposals during the VPNaaS meeting. At least Mathieu and I will participate to see how we can help. To avoid confusion we think it's good to keep separate the discussion on the details of the work around the networking

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

On Jun 1, 2015, at 8:26 AM, Andrew Laski wrote: >> In any case, even if we wanted to deprecate it (and I think an argument >> could be made for that) we still have to decide what the "correct" behaviour >> should be for the API as it exists today. In my view the current behaviour >> doesn't m

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

> *Plan C* would be to just let projects tag stable point releases from > time to time. That would solve all the original stated problems. And > that would solve objections 2 and 3, which I think are the most valid ones. and *Plan D* would be to start doing automatic per-project micro-versions on

Re: [openstack-dev] [release] WSME 0.7.0

Thank you!! Hopefully this release will be the starting point for a small rebirth of the WSME project. Many bugs still need fixes, the code needs improvements and probably some standardisation towards the OpenStack guidelines. It would be very useful to receive some feedback from the projects who

[openstack-dev] [nova] Add new VIF Type

Hi, what are the prereqs to get a spec for a new nova VIF type approved? In my case I'm planning for a new neutron ml2 driver and agent (on stackforge) that adds general support for macvtap to neutron. I've not yet published anything regarding the neutron part so far - but this will happen in the

Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel

2015-06-01 21:54 GMT+08:00 Jay Pipes : > On 05/31/2015 05:38 PM, Jay Lau wrote: > >> Just want to use ML to trigger more discussion here. There are now >> bugs/patches tracing this, but seems more discussions are needed before >> we come to a conclusion. >> >> https://bugs.launchpad.net/magnum/+bu

Re: [openstack-dev] [release][cinder] os-brick 0.2.0

Excerpts from Doug Hellmann's message of 2015-06-01 10:29:32 -0400: > We are jubilant to announce the release of: > > os-brick 0.2.0: OpenStack Cinder brick library for managing local > volume attaches > > With source available at: > > http://git.openstack.org/cgit/openstack/os-brick > > Fo

Re: [openstack-dev] [release][tripleo] os-collect-config 0.1.35

Excerpts from Doug Hellmann's message of 2015-06-01 10:31:36 -0400: > We are excited to announce the release of: > > os-collect-config 0.1.35: Collect and cache metadata, run hooks on > changes. > > For more details, please see the git log history below. > > > Changes in os-collect-config 0.1.3

Re: [openstack-dev] [release][neutron] python-neutronclient 2.6.0

Excerpts from Doug Hellmann's message of 2015-06-01 10:27:41 -0400: > We are thrilled to announce the release of: > > python-neutronclient 2.6.0: CLI and Client Library for OpenStack > Networking > > With source available at: > > http://git.openstack.org/cgit/openstack/python-neutronclient >

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

Hi Ryan and Flavio, Thanks for the quick response and the pointers, I will check out the reviews to catch up. Best Regards, Ildikó > -Original Message- > From: Ryan Brown [mailto:rybr...@redhat.com] > Sent: June 01, 2015 16:34 > To: openstack-dev@lists.openstack.org > Subject: Re: [open

[openstack-dev] [release][oslo] oslo.middleware 1.3.0

We are delighted to announce the release of: oslo.middleware 1.3.0: Oslo Middleware library With source available at: http://git.openstack.org/cgit/openstack/oslo.middleware For more details, please see the git log history below and: http://launchpad.net/oslo.middleware/+milestone/1.3.

Re: [openstack-dev] [release][manila] python-manilaclient 1.2.0

Excerpts from Doug Hellmann's message of 2015-06-01 10:27:38 -0400: > We are thrilled to announce the release of: > > python-manilaclient 1.2.0: Client library for OpenStack Manila API. > > With source available at: > > http://git.openstack.org/cgit/openstack/python-manilaclient > > For mor

Re: [openstack-dev] [release][neutron] python-neutronclient 2.6.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I have a suggestion... Since it's not obvious now which stable branch a release corresponds to, can we add that info into release note email body somewhere for the sake of those who may closely track stable updates but not so much those in-developmen

Re: [openstack-dev] [kolla] gate failing sporadically

On Sat, May 30, 2015 at 03:00:04AM +, Steven Dake (stdake) wrote: Hey Folks, I noticed the Kolla functional gate is failing sporadically. It seems that sometimes an image doesn’t build. http://logs.openstack.org/75/186475/1/check/check-kolla-functional-f21/8f23913/console.html (For the r

[openstack-dev] [release][tripleo] os-collect-config 0.1.35

We are excited to announce the release of: os-collect-config 0.1.35: Collect and cache metadata, run hooks on changes. For more details, please see the git log history below. Changes in os-collect-config 0.1.34..0.1.35 --- 4a41f0b Drop use of 'oslo' name

[openstack-dev] [release][trove] python-troveclient 1.2.0

We are delighted to announce the release of: python-troveclient 1.2.0: Client library for OpenStack DBaaS API With source available at: http://git.openstack.org/cgit/openstack/python-troveclient For more details, please see the git log history below and: http://launchpad.net/python-tro

[openstack-dev] [release][manila] python-manilaclient 1.2.0

We are thrilled to announce the release of: python-manilaclient 1.2.0: Client library for OpenStack Manila API. With source available at: http://git.openstack.org/cgit/openstack/python-manilaclient For more details, please see the git log history below and: http://launchpad.net/python-

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

On 06/01/2015 04:34 AM, Flavio Percoco wrote: > On 31/05/15 18:12 +, Ildikó Váncsa wrote: >> Hi All, >> >> I would like to ask about the user-facing notifications part of the >> list. Do you have a roadmap for this? Is this driven by the Zaqar >> team? What are the next steps? > > Hey, > > Th

[openstack-dev] [release][neutron] python-neutronclient 2.6.0

We are thrilled to announce the release of: python-neutronclient 2.6.0: CLI and Client Library for OpenStack Networking With source available at: http://git.openstack.org/cgit/openstack/python-neutronclient For more details, please see the git log history below and: http://launchpad.ne

[openstack-dev] [release][cinder] os-brick 0.2.0

We are jubilant to announce the release of: os-brick 0.2.0: OpenStack Cinder brick library for managing local volume attaches With source available at: http://git.openstack.org/cgit/openstack/os-brick For more details, please see the git log history below and: http://launchpad.net/os-b

[openstack-dev] [release][ironic] python-ironicclient 0.7.0

We are thrilled to announce the release of: python-ironicclient 0.7.0: OpenStack Bare Metal Provisioning API Client Library With source available at: http://git.openstack.org/cgit/openstack/python-ironicclient For more details, please see the git log history below and: http://launchpad

Re: [openstack-dev] [Fuel] Pre-5.1 and master builds ISO are available for download

Hi, Are we going to add this feature to 7.0? There are some customers who tried Fuel from nightly or technical previews builds. However, they don't want to install fuel master node once again. There are several reasons for that. As a sample it's dev environment, though production environment shoul

[openstack-dev] [release][barbican] python-barbicanclient 3.2.0

We are happy to announce the release of: python-barbicanclient 3.2.0: Client Library for OpenStack Barbican Key Management API With source available at: http://git.openstack.org/cgit/openstack/python-barbicanclient For more details, please see the git log history below and: http://laun

[openstack-dev] [all] Project Team Guide workgroup planning a virtual sprint Jun 18-19

Hi everyone, In an attempt to document shared understandings and "the OpenStack way", the Technical Committee created a workgroup around the idea of a "Project Team Guide". This group is however open to anyone who would like to contribute. The current outline for the guide lives here: https://eth

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

There is a spec to get this work started. It's currently a Heat spec: https://review.openstack.org/#/c/186436/ That spec is for defining a basic schema to start with. -Alex On Mon, Jun 1, 2015 at 4:48 AM, Flavio Percoco wrote: > On 28/05/15 16:48 +0100, Gordon Sim wrote: > >> On 05/27/2015 05:

Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel

On 05/31/2015 05:38 PM, Jay Lau wrote: Just want to use ML to trigger more discussion here. There are now bugs/patches tracing this, but seems more discussions are needed before we come to a conclusion. https://bugs.launchpad.net/magnum/+bug/1453732 https://review.openstack.org/#/c/181839/ https

Re: [openstack-dev] [Glance] [all] Liberty summit: Updates in Glance

On 06/01/2015 08:30 AM, John Garbutt wrote: On 1 June 2015 at 13:10, Flavio Percoco wrote: On 01/06/15 11:57 +0100, John Garbutt wrote: On 26/05/15 13:54 -0400, Nikhil Komawar wrote: FWIW, moving Nova from glance v1 to glance v2, without breaking Nova's public API, will require someone gettin

Re: [openstack-dev] [cinder] Some Changes to Cinder Core

Well deserved, and hope you had a nice break. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailm

Re: [openstack-dev] [cinder] Some Changes to Cinder Core

Finally back after a few days offline. Thanks everyone. Just glad to be part of this great group. Thank you for all the positive comments from cores and non-cores alike. Sean On 05/26/2015 04:42 PM, Ivan Kolodyazhny wrote: +1, Welcome to the team, Sean. Regards, Ivan Kolodyazhny On Wed, M

Re: [openstack-dev] [nova] Progressing/tracking work on libvirt / vif drivers

On Mon, Jun 01, 2015 at 09:44:24AM +0100, John Garbutt wrote: > On 29 May 2015 at 18:32, Neil Jerram wrote: > > Hi all, > > > > Per yesterday's IRC meeting [1], and discussion in Vancouver, Nova work is > > being somewhat driven by the etherpad at [2]. But this etherpad doesn't > > have a section

[openstack-dev] [release] WSME 0.7.0

We are jubilant to announce the release of: wsme 0.7.0: Simplify the writing of REST APIs, and extend them with additional protocols. With source available at: http://git.openstack.org/cgit/stackforge/wsme For more details, please see the git log history below and: https://launchpad.ne

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

On 05/27/15 at 07:38pm, Chris Friesen wrote: On 05/27/2015 05:09 PM, Fox, Kevin M wrote: If the current behavior is broken, and the behavior is causing problems with things like fixing quota's, should it just be deprecated and pushed off to orchestration rather then change it? Is this causing

Re: [openstack-dev] [neutron] - dnsmasq 'dhcp-authoritative' option broke multiple DHCP servers

Thanks! I'll reconsider about this. 2015-06-01 16:54 GMT+08:00 Kevin Benton : > >But I don't know that does NAK matters? > > Yes, some clients will honor it and re-request, so they end up in a loop. > I believe the dhcp client in the Cirros image does this. > > >"dhcp-authoritative" is really a s

Re: [openstack-dev] [nova] Progressing/tracking work on libvirt / vif drivers

On Fri, May 29, 2015 at 06:32:18PM +0100, Neil Jerram wrote: > Hi all, > > Per yesterday's IRC meeting [1], and discussion in Vancouver, Nova work is > being somewhat driven by the etherpad at [2]. But this etherpad doesn't > have a section for libvirt / vif driver changes. The log at [1] briefl

[openstack-dev] [mistral] Team meeting - 2015/06/01

Hi Mistral team, This is just a reminder that we’ll have a team meeting today at #openstack-meeting at 16.00 UTC (not 16.20 like it was during a couple of months!) Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Liberty Roadmap Add seconds granularity in

Re: [openstack-dev] [Glance] [all] Liberty summit: Updates in Glance

On 01/06/15 13:30 +0100, John Garbutt wrote: On 1 June 2015 at 13:10, Flavio Percoco wrote: On 01/06/15 11:57 +0100, John Garbutt wrote: On 26/05/15 13:54 -0400, Nikhil Komawar wrote: On 5/26/15 12:57 PM, Jesse Cook wrote: We also had some hallway talk about putting the v1 and v2 APIs on

Re: [openstack-dev] [nova][scheduler] Updating Our Concept of Resources

On Jun 1, 2015, at 7:49 AM, Sylvain Bauza wrote: > Long story short : > https://blueprints.launchpad.net/nova/+spec/resource-objects > > Until we get this, it's difficult to discuss on different resources within > Nova. Let's work by small steps and provide a versioned resource system > before

  1   2   >