Re: [openstack-dev] [Fuel][Plugins] differenciate node with the same role - the spec is available

Hi, First, thank you all for your contributions on that topic (I don't know what it has been split in two thread but let reply on this one) Igor : the problem I try to solve is the following, I would like to be able to : 1/decide on which compute node I want to deploy a plugin. for the example of

[openstack-dev] Jenkins check failed on gate-glance_store-python34

Hi all, I am a new contributor for openstack. the following url is my code review for glance_store https://review.openstack.org/#/c/193403/ Jenkins check failed on gate-glance_store-python34 Referring to the console info, I have never changed the code mentioned. have any suggestions

Re: [openstack-dev] Jenkins check failed on gate-glance_store-python34

Hi, The gate is 'non-voting' so it actually doesn't block the merge. But in console I see such errors: TypeError: Unicode-objects must be encoded before hashing which means py34 compatibility is broken in code (not by you maybe, but it is). If you will fix it in your next patches your team

Re: [openstack-dev] Jenkins check failed on gate-glance_store-python34

Hi, Le 26/06/2015 09:17, 孙明达 a écrit : I am a new contributor for openstack. the following url is my code review for glance_store https://review.openstack.org/#/c/193403/ Jenkins check failed on gate-glance_store-python34 Referring to the console info, I have never changed the code me

[openstack-dev] [cinder][glance][nova] Python 3 coming!

Hi, The Python 3.4 gate (py34) of cinder, glance and nova just became voting. You now have to write Python code compatible with Python 2.7 and 3.4. If the py34 check job fails on your patch, you may try to rebase it to get the new tox.ini and updated requirements. You can find information

Re: [openstack-dev] [openstack-infra][Infra][Neutron] Nominating intel-networking-ci for voting rights

Thanks Kyle. Yes, I’d wait with further processing of this request till we have a consensus on the thread. From: Kyle Mestery [mailto:mest...@mestery.com] Sent: Thursday, June 25, 2015 8:11 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [openstac

Re: [openstack-dev] [Mistral][Murano] What's the latest/greatest on YAQL?

The plan is to move to yaql 1.0 this release. Please do not merge yaql 1.0 into Mistral yet. Migration is going to happen really soon Sincerely yours, Stan Lagun Principal Software Engineer @ Mirantis On Fri, Jun 26, 2015 at 8:17 AM, Renat Akhmerov wrote: > Yes, it’s a pretty important thing

[openstack-dev] Recall: [Nova] [Liberty] Approval dates for non-priority specs

Kekane, Abhishek would like to recall the message, "[Nova] [Liberty] Approval dates for non-priority specs ". __ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and ma

[openstack-dev] [Nova] Approval dates for non-priority specs

Hi Nova Devs, I have submitted a nova spec [1] for improving unshelve api performance. It's not listed under the liberty priorities, in spec also I have set project priority as None and in Launchpad blueprint [2] also milestone target is None. As per nova liberty schedule, June 23-25, 2015 were

[openstack-dev] [Nova] [Liberty] Approval dates for non-priority specs

Hi Nova Devs, I have submitted a nova spec [1] for improving unshelve api performance. It's not listed under the liberty priorities, in spec also I have set project priority as None and in Launchpad blueprint [2] also milestone target is None. As per nova liberty schedule, June 23-25, 2015 were

[openstack-dev] Recall: [Nova] [Liberty] Approval dates for non-priority specs

Kekane, Abhishek would like to recall the message, "[Nova] [Liberty] Approval dates for non-priority specs ". __ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and ma

[openstack-dev] [neutron] QoS code sprint

Hi everybody, Next week, from Tue (Jul 29th) to Thu (Jun 2nd), a few of us will be physically [1] attending the neutron QoS coding sprint in Ra'anana (Israel) @ the Red Hat office. And a few others have expressed their will to join us remotely (Thanks!!) :) I guess a reasonabl

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/25/2015 09:46 PM, Joe Gordon wrote: > On Thu, Jun 25, 2015 at 1:39 AM, Nikola Đipanov > > > > As someone who does a lot of spec reviews, I take +1s from the right > > people (not always nova-cores) to mean a lot, so much that I regularly > > will simply skim the spec myself b

[openstack-dev] [Fuel] Fuel for Openstack 6.1 released

Hello everyone, I am glad to inform you that Fuel for Openstack 6.1 is out now. Feel free to download the new release from https://www.fuel-infra.org. Thanks to all contributors for making this release happen. -- EugeneB __

[openstack-dev] [all] Any other downstream developers having problems with pbr?

I wrote this: https://review.openstack.org/#/c/195983/1/tools/de-pbr.py,cm Ideally we'd fix PBR, but this seems to be expected behaviour. Thoughts? Matt -- Matthew Booth Red Hat Engineering, Virtualisation Team Phone: +442070094448 (UK) GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600

[openstack-dev] [Neutron] What are problems of Distributed SNAT?

Hi all, I'm Takanori Miyagishi. I and Yushiro Furukawa, my co-worker, are planning to implement Distributed SNAT in Liberty cycle. So, I looking for information about Distributed SNAT implementation. For now, I got some information from openstack-dev ML[1][2][3] and etherpad[4]. Would you please

[openstack-dev] [Nova] Liberty-1 Spec Freeze (and the exception process)

Hi, Liberty-1 has been tagged and release, as such we have hit the promised Spec Freeze. https://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule We discussed this at the nova-meeting yesterday, but here are more specifics on how we try to track this process. A) Liberty Priority Specs not f

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On 06/16/2015 09:51 AM, Dmitry Tantsur wrote: > On 06/16/2015 08:56 AM, Dmitry Tantsur wrote: >> To sum this long post up, I'm seeing that hiding new features based on >> microversions brings much more problems, than it solves (I'm not aware >> of the latter at all). I'm very opposed to continuing

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 26 June 2015 at 11:19, Nikola Đipanov wrote: > On 06/25/2015 09:46 PM, Joe Gordon wrote: >> On Thu, Jun 25, 2015 at 1:39 AM, Nikola Đipanov > >> >> >> > As someone who does a lot of spec reviews, I take +1s from the right >> > people (not always nova-cores) to mean a lot, so much that I

Re: [openstack-dev] [all] Any other downstream developers having problems with pbr?

On Fri, Jun 26, 2015, at 04:01 AM, Matthew Booth wrote: > I wrote this: > > https://review.openstack.org/#/c/195983/1/tools/de-pbr.py,cm > > Ideally we'd fix PBR, but this seems to be expected behaviour. Thoughts? > Use the PBR_VERSION env var [1], it exists so that downstreams can assert a spec

[openstack-dev] [mistral] Liberty 1 milestone is released

Hi all, Liberty 1 milestone for Mistral server and Mistral client 0.3.0 have been released! Visit corresponding release pages to see information on fixed bugs and implemented blueprints: https://launchpad.net/mistral/liberty/liberty-1 https://l

[openstack-dev] [horizon] [docs] AngularJS in Horizon Docs

Hi all, Had another pass of the AngularJS documentation: https://review.openstack.org/#/c/182243/ My hope here is to merge soon, noting those sections that may change, and update as they do change. This may potentially mean short periods of inaccuracy between the docs and reality, but otherwise

Re: [openstack-dev] [cinder][glance][nova] Python 3 coming!

On 06/26/2015 04:26 AM, Victor Stinner wrote: > Hi, > > The Python 3.4 gate (py34) of cinder, glance and nova just became > voting. You now have to write Python code compatible with Python 2.7 and > 3.4. WOOHOO! Well done! > If the py34 check job fails on your patch, you may try to rebase it to

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On 06/26/2015 01:14 PM, Sean Dague wrote: On 06/16/2015 09:51 AM, Dmitry Tantsur wrote: On 06/16/2015 08:56 AM, Dmitry Tantsur wrote: To sum this long post up, I'm seeing that hiding new features based on microversions brings much more problems, than it solves (I'm not aware of the latter at al

Re: [openstack-dev] [all] Any other downstream developers having problems with pbr?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/26/2015 01:01 PM, Matthew Booth wrote: > I wrote this: > > https://review.openstack.org/#/c/195983/1/tools/de-pbr.py,cm > > Ideally we'd fix PBR, but this seems to be expected behaviour. > Thoughts? > > Matt > You either use an older pbr v

Re: [openstack-dev] [all] Any other downstream developers having problems with pbr?

On 06/26/2015 07:24 AM, Clark Boylan wrote: > On Fri, Jun 26, 2015, at 04:01 AM, Matthew Booth wrote: >> I wrote this: >> >> https://review.openstack.org/#/c/195983/1/tools/de-pbr.py,cm >> >> Ideally we'd fix PBR, but this seems to be expected behaviour. Thoughts? >> > Use the PBR_VERSION env var [

Re: [openstack-dev] [oslo] About app-agnostic-logging-parameters

Excerpts from Lingxian Kong's message of 2015-06-26 12:14:57 +0800: > On Fri, Jun 26, 2015 at 12:03 AM, Doug Hellmann wrote: > > > > > The goal is to set up the default log format string to be the same in > > all projects, and have the context class provide application-specific > > values. So nov

Re: [openstack-dev] [oslo] About app-agnostic-logging-parameters

Hi, Lingxian Kong, Thank you for your reply. > -Original Message- > From: Lingxian Kong [mailto:anlin.k...@gmail.com] > Sent: Thursday, June 25, 2015 7:59 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [oslo] About app-agnostic-logging

Re: [openstack-dev] [Sahara] Why Sahara request user to give username/password for accessing the job binary in Swift ?

On 06/25/2015 09:54 PM, Li, Chen wrote: Thanks for the reply. My puzzle here is : I create containers & objects by my own, why other users can access them ? As mentioned in your article[1], the domain " sahara_proxy" is created by user "admin" in project "openstack". But I'm working u

Re: [openstack-dev] [oslo] About app-agnostic-logging-parameters

Hi, Doug Hellmann, Thank you for your reply. > -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Friday, June 26, 2015 1:04 AM > To: openstack-dev > Subject: Re: [openstack-dev] [oslo] About app-agnostic-logging-parameters > > Excerpts from Fujita, Daisuke's

[openstack-dev] [neutron] enriching port binding extension API dictionaries with key-values

Hi together, for a new ml2 plugin I would like to pass over some data from neutron to nova on port creation and update (exploiting port binding extension [1]). For my prototype I thought of using one of the following response dictionaries to add my information: - binding:vif_details - binding:pro

[openstack-dev] [Nova] Let's set instance.root_gb=0 for volume-backed instances

There are several problems in algorithms which calculate size of host local disk space consumed by a volume-backed instance [1]. Obviously the volume-backed instance does not use the host local disk for the root volume. But these algorithms use root_gb, min_size, size whic

Re: [openstack-dev] [cinder][glance][nova] Python 3 coming!

On Fri, Jun 26, 2015 at 5:43 AM, Monty Taylor wrote: > On 06/26/2015 04:26 AM, Victor Stinner wrote: > > Hi, > > > > The Python 3.4 gate (py34) of cinder, glance and nova just became > > voting. You now have to write Python code compatible with Python 2.7 and > > 3.4. > > WOOHOO! Well done! > > >

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On 06/26/2015 07:43 AM, Dmitry Tantsur wrote: > On 06/26/2015 01:14 PM, Sean Dague wrote: >> On 06/16/2015 09:51 AM, Dmitry Tantsur wrote: >>> On 06/16/2015 08:56 AM, Dmitry Tantsur wrote: To sum this long post up, I'm seeing that hiding new features based on microversions brings much mor

Re: [openstack-dev] [Nova] Let's set instance.root_gb=0 forvolume-backed instances

I agree! A positive root_gb of volume-backed instances which has different volume size is confusing! Last week I submit a patch to correct disk filter(https://review.openstack.org/#/c/194059/). But if we set instance.root_gb=0 for volume-backed instances, such problems could be solved fundamen

Re: [openstack-dev] [neutron] enriching port binding extension API dictionaries with key-values

Hi Andreas, On 26/06/15 14:04, Andreas Scheuring wrote: Hi together, for a new ml2 plugin I would like to pass over some data from neutron to nova on port creation and update (exploiting port binding extension [1]). For my prototype I thought of using one of the following response dictionaries t

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On 06/26/2015 04:08 PM, Sean Dague wrote: On 06/26/2015 07:43 AM, Dmitry Tantsur wrote: On 06/26/2015 01:14 PM, Sean Dague wrote: On 06/16/2015 09:51 AM, Dmitry Tantsur wrote: On 06/16/2015 08:56 AM, Dmitry Tantsur wrote: To sum this long post up, I'm seeing that hiding new features based on

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 2015-06-25 16:39:56 + (+), Tim Bell wrote: [...] > One of the problems that I’ve seen is with specs etiquette where > people -1 because they have a question. This is a question of > education rather than a fundamental issue with the process. http://docs.openstack.org/infra/manual/develo

[openstack-dev] [Fuel][Plugins] Separating services from controller role update

Hi fellow Fuelers and Stackers, I'm writing to you with an update on the project I am working on regarding separating one or more services from a Fuel controller node. The scope of this project is limited at this point to separation of database, keystone, RabbitMQ, and horizon from the default con

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On Fri, Jun 26, 2015 at 7:39 AM, Dmitry Tantsur wrote: > On 06/26/2015 04:08 PM, Sean Dague wrote: > >> On 06/26/2015 07:43 AM, Dmitry Tantsur wrote: >> >>> On 06/26/2015 01:14 PM, Sean Dague wrote: >>> On 06/16/2015 09:51 AM, Dmitry Tantsur wrote: > On 06/16/2015 08:56 AM, Dmitry T

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

Dmitry, Feature strings won't work. It only makes things more complex, without addressing the underlying issue. What happens when we change, even in a small way, the API surface exposed by an existing feature? How is that change exposed -- unless we include a version number along with your featur

[openstack-dev] [ceilometer][all] the max length of an id

hi, recently we added a change in Ceilometer to lower the size of our id fields in our storage model[1]. the reason we did this was because the original size of varchar(255) we assigned to ids were so large that if we wanted to generate some of our larger constraint requirements, it would hit

[openstack-dev] [ceilometer] virtual mid-cycle planning

Ceilometer contributors and other interested parties, This cycle, due to all the usual constraints, the Ceilometer project is going to have a virtual mid-cycle. In order to make this a success we need to be extra good at planning and keeping to an effective agenda. To help us do that we need to

Re: [openstack-dev] [ceilometer] virtual mid-cycle planning

On Fri, 26 Jun 2015, Chris Dent wrote: Please provide your input soon. We will close the voting at the end of Wednesday, July 3rd and will be posting a proposed schedule soon thereafter. Note that due to time constraints the mid-cycle could happen as soon as the following Monday, July 6th. Sig

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On 06/26/2015 04:57 PM, Joe Gordon wrote: On Fri, Jun 26, 2015 at 7:39 AM, Dmitry Tantsur mailto:dtant...@redhat.com>> wrote: On 06/26/2015 04:08 PM, Sean Dague wrote: On 06/26/2015 07:43 AM, Dmitry Tantsur wrote: On 06/26/2015 01:14 PM, Sean Dague wrote:

Re: [openstack-dev] [api] [Nova] [Ironic] [Magnum] Microversion guideline in API-WG

On 06/26/2015 04:58 PM, Devananda van der Veen wrote: Dmitry, Feature strings won't work. It only makes things more complex, without addressing the underlying issue. What happens when we change, even in a small way, the API surface exposed by an existing feature? How is that change exposed -- u

[openstack-dev] [TripleO] Splitting out dib-core

Hello TripleOers, At the last mid-cycle we briefly discussed whether we should have separate groups for tripleo and DIB core and decided it wasn't necessary. I would like to revisit that topic. It seems clear to me that we have some existing tripleo cores who are becoming less familiar with the t

Re: [openstack-dev] [all] Any other downstream developers having problems with pbr?

Matthew Booth wrote: I wrote this: https://review.openstack.org/#/c/195983/1/tools/de-pbr.py,cm Ideally we'd fix PBR, but this seems to be expected behaviour. Thoughts? +1 to doing the ideal and fixing PBR (if it needs fixing) :-) Matt

[openstack-dev] [puppet] introducing upgrade testing jobs

Hi, In case you've missed it, we have now voting functional testing jobs. For example, if you submit a patch in puppet-keystone, it will deploy keystone on both Ubuntu Trusty & CentOS7, and test that it works, by using Beaker framework [1]. [1] https://github.com/puppetlabs/beaker-rspec We would

Re: [openstack-dev] [TripleO] package based overcloud upgrades

> +1 such a blog post would be great and would really help other projects > align/reuse where appropriate :) Hot off the presses: http://www.danplanet.com/blog/2015/06/26/upgrading-nova-to-kilo-with-minimal-downtime/ --Dan

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 06/25/2015 05:39 PM, Tim Bell wrote: > > > On 25/06/15 09:49, "Thierry Carrez" wrote: > >> Maxim Nestratov wrote: >>> 24.06.2015 20:21, Daniel P. Berrange пишет: On Wed, Jun 24, 2015 at 04:46:57PM +, Michael Krotscheck wrote: > First: Overhead > - 1 week for vacation > -

Re: [openstack-dev] [grenade] future direction on partial upgrade support

On Wed, Jun 24, 2015 at 11:44 AM, Joe Gordon wrote: > > > On Wed, Jun 24, 2015 at 11:03 AM, Sean Dague wrote: > >> On 06/24/2015 01:41 PM, Russell Bryant wrote: >> > On 06/24/2015 01:31 PM, Joe Gordon wrote: >> >> >> >> >> >> On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague > >>

Re: [openstack-dev] [neutron] enriching port binding extension API dictionaries with key-values

That bug is about adding things that the user can pass to the port. I think Andreas is just talking about passing data to Nova that his ML2 plugin generates. The key difference would be that adding key/value pairs to the port API that the user populates would be exposing implementation details to u

Re: [openstack-dev] [TripleO] Splitting out dib-core

Excerpts from Gregory Haynes's message of 2015-06-26 08:17:36 -0700: > Hello TripleOers, > > At the last mid-cycle we briefly discussed whether we should have > separate groups for tripleo and DIB core and decided it wasn't > necessary. I would like to revisit that topic. > > It seems clear to me

[openstack-dev] [Oslo][Futurist] Proposal for new core reviewer (dtantsur)

Greetings all stackers, I propose that we add Dmitry Tantsur[1] to the futurist-core team. Dmitry has been actively contributing to futurist[2] for a while now, both in helping make futurist better by helping with the review load when he can and also by starting to help integrate it into ironi

[openstack-dev] [nova][cinder][qa] encrypted volumes tests don't actually test encrypted volumes for most backends

Tempest has the TestEncryptedCinderVolumes scenario test [1] which creates an encrypted volume type, creates a volume from that volume type, boots a server instance and then attaches/detaches the 'encrypted' volume to/from the server instance. This works fine in the integrated gate because LVM

Re: [openstack-dev] [Oslo][Futurist] Proposal for new core reviewer (dtantsur)

Welcome Dmitry! -- dims On Fri, Jun 26, 2015 at 1:24 PM, Joshua Harlow wrote: > Greetings all stackers, > > I propose that we add Dmitry Tantsur[1] to the futurist-core team. > > Dmitry has been actively contributing to futurist[2] for a while now, both > in helping make futurist better by helpi

Re: [openstack-dev] [ceilometer][all] the max length of an id

On 06/26/2015 11:00 AM, gordon chung wrote: hi, recently we added a change in Ceilometer to lower the size of our id fields in our storage model[1]. the reason we did this was because the original size of varchar(255) we assigned to ids were so large that if we wanted to generate some of our lar

Re: [openstack-dev] [TripleO] Splitting out dib-core

Excerpts from Clint Byrum's message of 2015-06-26 17:21:29 +: > Excerpts from Gregory Haynes's message of 2015-06-26 08:17:36 -0700: > > Hello TripleOers, > > > > At the last mid-cycle we briefly discussed whether we should have > > separate groups for tripleo and DIB core and decided it wasn'

[openstack-dev] [all][api] New API Guidelines ready for cross project review

hi all, we have 1 API guideline that is ready for final review 1. Adds clarifications on state-conflicting requests https://review.openstack.org/#/c/180094 if the API working group hasn't received any further feedback, we'll merge this on July 3. regards, mike __

Re: [openstack-dev] [TripleO] Splitting out dib-core

On Fri, Jun 26, 2015 at 8:17 AM, Gregory Haynes wrote: > Hello TripleOers, > > At the last mid-cycle we briefly discussed whether we should have > separate groups for tripleo and DIB core and decided it wasn't > necessary. I would like to revisit that topic. > > It seems clear to me that we have s

Re: [openstack-dev] [openstack-infra] [neutron] Third Party CI Voting

Totally agreed! Edgar From: Salvatore Orlando Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, June 25, 2015 at 3:44 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [openstack-infra] [neutron] Third Party C

Re: [openstack-dev] [TripleO][Heat] Tuskar v. Heat responsibilities

On Thu, Jun 25, 2015 at 5:40 PM, Steven Hardy wrote: > On Tue, Jun 23, 2015 at 04:05:08PM -0400, Jay Dobies wrote: >> On top of that, only certain templates can be used to fulfill certain >> resource types. For instance, you can't point CinderBackend to >> rhel-registration.yaml. That information

[openstack-dev] [heat] Question about retrieving resource_list from ResourceGroup

Hi team, I would like to start my question by using a sample template: heat_template_version: 2014-10-16 parameters: count: type: number default: 5 removal_list: type: comma_delimited_list default: [] resources: sample_group: type: OS::Heat::ResourceGroup properties:

Re: [openstack-dev] [TripleO] Splitting out dib-core

On Fri, Jun 26, 2015 at 1:21 PM, Clint Byrum wrote: > Excerpts from Gregory Haynes's message of 2015-06-26 08:17:36 -0700: >> Hello TripleOers, >> >> At the last mid-cycle we briefly discussed whether we should have >> separate groups for tripleo and DIB core and decided it wasn't >> necessary. I

Re: [openstack-dev] [Nova] The unbearable lightness of specs

> -Original Message- > From: Nikola Đipanov [mailto:ndipa...@redhat.com] > Sent: 26 June 2015 18:34 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] The unbearable lightness of specs > > On 06/25/2015 05:39 PM, Tim Bell wrote: > > > > > > On 25/06/15 09:49, "Th

Re: [openstack-dev] [nova][ceilometer] proposal to send bulk hypervisor stats data in periodic notifications

On 6/22/2015 4:55 AM, Daniel P. Berrange wrote: On Sun, Jun 21, 2015 at 11:14:00AM -0500, Matt Riedemann wrote: On 6/20/2015 3:35 PM, Daniel P. Berrange wrote: On Sat, Jun 20, 2015 at 01:50:53PM -0500, Matt Riedemann wrote: Waking up from a rare nap opportunity on a Saturday, this is what

Re: [openstack-dev] [Nova] The unbearable lightness of specs

> -Original Message- > From: Jeremy Stanley [mailto:fu...@yuggoth.org] > Sent: 26 June 2015 16:42 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Nova] The unbearable lightness of specs > > On 2015-06-25 16:39:56 + (+), Tim Bell wr

Re: [openstack-dev] [ceilometer][all] the max length of an id

On 26/06/2015 1:42 PM, Jay Pipes wrote: On 06/26/2015 11:00 AM, gordon chung wrote: hi, recently we added a change in Ceilometer to lower the size of our id fields in our storage model[1]. the reason we did this was because the original size of varchar(255) we assigned to ids were so large th

Re: [openstack-dev] [nova][ceilometer] proposal to send bulk hypervisor stats data in periodic notifications

On 6/26/2015 2:17 PM, Matt Riedemann wrote: On 6/22/2015 4:55 AM, Daniel P. Berrange wrote: On Sun, Jun 21, 2015 at 11:14:00AM -0500, Matt Riedemann wrote: On 6/20/2015 3:35 PM, Daniel P. Berrange wrote: On Sat, Jun 20, 2015 at 01:50:53PM -0500, Matt Riedemann wrote: Waking up from a ra

Re: [openstack-dev] [neutron] enriching port binding extension API dictionaries with key-values

On Fri, Jun 26, 2015 at 8:14 AM, Neil Jerram wrote: > Hi Andreas, > > On 26/06/15 14:04, Andreas Scheuring wrote: > >> Hi together, >> for a new ml2 plugin I would like to pass over some data from neutron to >> nova on port creation and update (exploiting port binding extension >> [1]). For my pr

[openstack-dev] [openstack-operators][chef] Pre-Release of knife-openstack is out (1.3.0.rc.1)

> > On Jun 25, 2015, at 2:58 PM, JJ Asghar wrote: > > I have released the 1.3.0.rc.0 version of the knife-openstack[1] gem. I have bumped the rc.1 and pushed the gem to rubygems.org. I added the initial floating_ip ability to list the floating_ip(s) from the knife plugin. We should be able to

Re: [openstack-dev] [Nova] The unbearable lightness of specs

+1 From: Tim Bell [tim.b...@cern.ch] Sent: Friday, June 26, 2015 12:26 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] The unbearable lightness of specs > -Original Message- > From: Jeremy Stan

[openstack-dev] [Manila] State of 3rd party CI

Liberty-1 has passed and many exciting things are going on in Manila, and lots of exciting new features have merged or are being worked on but we cannot forget the slightly less-exciting topic of CI systems. Just before the summit I proposed a plan for CI and we agreed to it. The original threa

[openstack-dev] [all] approving python 3 integration testing spec

I would like to put the cross-project spec for python 3 integration testing [1] before the TC for approval. Before I do that, it would be nice to have sign-off from a representative of most of the projects that will be participating in the initial porting effort, the QA PTL, and someone on the infr

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On 2015-06-26 19:26:57 + (+), Tim Bell wrote: > I also feel that stackalytics should credit people of a 0 review > comment on specs. Currently, I think that only non-zero reviews > are considered as a contribution. My understanding of the workflow > is that a 0 is in many cases is the const

[openstack-dev] [Fuel][Fuel-Library] Nominate Aleksandr Didenko for fuel-library core

Folks I am thrilled to nominate Aleksandr Didenko as a new core reviewer for Fuel Library. Sasha has been working on FL for almost three years. He is a rather strict reviewer (20% of '-1s') #4 in the list (3 others are already core reviewers) for the last year and #4 contributor by commits with

Re: [openstack-dev] [Fuel][Fuel-Library] Nominate Aleksandr Didenko for fuel-library core

+1 For reference, fuel-library stats for 90 days: http://stackalytics.com/report/contribution/fuel-library/90 On Fri, Jun 26, 2015 at 2:51 PM Vladimir Kuklin wrote: > Folks > > I am thrilled to nominate Aleksandr Didenko as a new core reviewer for > Fuel Library. > > Sasha has been working on F

Re: [openstack-dev] [Manila] State of 3rd party CI

Friendly reminder that there are 3rd party CI weekly meetings [1] for us to come together and work out issues and find ways to make it easier to setup and maintain a 3rd party ci system. [1] https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings Ramy -Original Me

Re: [openstack-dev] [grenade] future direction on partial upgrade support

No On Fri, Jun 26, 2015 at 10:15 AM, Joe Gordon wrote: > > > On Wed, Jun 24, 2015 at 11:44 AM, Joe Gordon > wrote: > >> >> >> On Wed, Jun 24, 2015 at 11:03 AM, Sean Dague wrote: >> >>> On 06/24/2015 01:41 PM, Russell Bryant wrote: >>> > On 06/24/2015 01:31 PM, Joe Gordon wrote: >>> >> >>> >> >

Re: [openstack-dev] [Fuel][Fuel-Library] Nominate Aleksandr Didenko for fuel-library core

+1 On Fri 26 Jun 2015 at 18:18 Dmitry Borodaenko wrote: > +1 > > For reference, fuel-library stats for 90 days: > http://stackalytics.com/report/contribution/fuel-library/90 > > On Fri, Jun 26, 2015 at 2:51 PM Vladimir Kuklin > wrote: > >> Folks >> >> I am thrilled to nominate Aleksandr Didenko

Re: [openstack-dev] [Fuel][Fuel-Library] Nominate Aleksandr Didenko for fuel-library core

+1. Alex's work on increasing quality in fuel-library is very valuable. On Fri, Jun 26, 2015 at 3:59 PM, Sergii Golovatiuk wrote: > +1 > > On Fri 26 Jun 2015 at 18:18 Dmitry Borodaenko > wrote: > >> +1 >> >> For reference, fuel-library stats for 90 days: >> http://stackalytics.com/report/contri

Re: [openstack-dev] Why doesn't Swift cache object data?

> On Jun 25, 2015, at 7:35 PM, 杨苏立 Yang Su Li wrote: > > Thanks a lot for your answer. > > I guess that is an excellent answer on "why does swift explicitly disable > object data caching at the page cache level". But my question is a bit > different "Why doesn't swift use memcached to cache o

[openstack-dev] [Congress] IRC on 6/30 canceled

Hi all, Since almost all the cores are on vacation next week, we're canceling the IRC meeting on 6/30. Expect slow responses for reviews and email all next week. Tim __ OpenStack Development Mailing List (not for usage quest

Re: [openstack-dev] [ceilometer][all] the max length of an id

On Fri, Jun 26, 2015 at 12:27 PM, gordon chung wrote: > > > On 26/06/2015 1:42 PM, Jay Pipes wrote: > >> On 06/26/2015 11:00 AM, gordon chung wrote: >> >>> hi, >>> >>> recently we added a change in Ceilometer to lower the size of our id >>> fields in our storage model[1]. the reason we did this w

[openstack-dev] [Tricircle] Ubernetes and Tricirle

Hi Team, We should definitely look into this https://github.com/GoogleCloudPlatform/kubernetes/blob/8813c955182e3c9daae68a8257365e02cd871c65/release-0.19.0/docs/proposals/federation.md, it would be fantastic if Tricircle could provide support for this feature -- Zhipeng (Howard) Huang Standard

Re: [openstack-dev] Why doesn't Swift cache object data?

Excerpts from 杨苏立 Yang Su Li's message of 2015-06-25 17:35:18 -0700: > Thanks a lot for your answer. > > I guess that is an excellent answer on "why does swift explicitly disable > object data caching at the page cache level". But my question is a bit > different "Why doesn't swift use memcached t

Re: [openstack-dev] Why doesn't Swift cache object data?

On Thu, Jun 25, 2015 at 7:35 PM, 杨苏立 Yang Su Li wrote: > I guess that is an excellent answer on "why does swift explicitly disable > object data caching at the page cache level". But my question is a bit > different "Why doesn't swift use memcached to cache object data?" Not that > it is a bit di

[openstack-dev] [cinder][oslo] Locks for create from volume/snapshot

Hi folks, Currently we use a lockfile to protect the create operations from concurrent delete the source volume/snapshot, we use exclusive locks on both delete and create sides which will ensure that: 1. If a create of VolA from snap/VolB is in progress, any delete requests for snap/VolB

Re: [openstack-dev] [Tricircle] Ubernetes and Tricirle

The idea is quite like what Tricircle want to do on OpenStack. Interesting. Tricicle provides OS provisioning across-OpenStack cloud, Magnum which work above OpenStack can make kubernetes being able to deliver these container on provisioned distributed OS cluster. Best Regards Chaoyi Huang ( J

Re: [openstack-dev] [Nova] Approval dates for non-priority specs

I have same question about this. My spec and blueprint: https://review.openstack.org/#/c/169638/ https://blueprints.launchpad.net/nova/+spec/selecting-subnet-when-creating-vm 2015-06-26 17:56 GMT+08:00 Kekane, Abhishek : > Hi Nova Devs, > > > > I have submitted a nova spec [1] for improving

Re: [openstack-dev] [Magnum] Python 3 support

Re python 3 sounds fantastic. Re changing around python client, lets hold off on that until we have a concrete plan for getting a python client in an operational state in the proper repository. Regards -steve From: Tom Cammann mailto:tom.camm...@hp.com>> Reply-To: "OpenStack Development Maili

Re: [openstack-dev] [Nova] Approval dates for non-priority specs

Hi, Rui, Abhishek, There is email can answer your question: http://lists.openstack.org/pipermail/openstack-dev/2015-June/068079.html Thanks Alex 2015-06-27 11:33 GMT+08:00 Rui Chen : > I have same question about this. > > My spec and blueprint: > > https://review.openstack.org/#/c/169638/ > > h