[openstack-dev] Android App to Manage OpenStack - Code Available to Fork

I started to develop an android app with material design to manage OpenStack services and instances but had to stop working on it due to lack of time and other reasons. I made it available on GitHub in case anyone wants to continue working on it. You can check it on http://stackerz.com or https://g

Re: [openstack-dev] Android App to Manage OpenStack - Code Available to Fork

On Fri, Feb 26, 2016 at 4:30 PM, Ed Lima wrote: > I started to develop an android app Hi, Thanks. Looks promising... Efforts towards a mobile optimized version of Horizon would work for both Android, iOS and/or other mobile platforms. Part of the user interface could be cached, but an active c

Re: [openstack-dev] [devstack] stack.sh keeps failing with RTNETLINK answers: Network is unreachable

Sean Don't think unstack failed, when I manually create the device ( sudo ovs-vsctl --no-wait -- --may-exist add-br br-ex) unstack.sh removes it. sudo ip route show default via 172.18.20.1 dev eth0 169.254.169.254 via 172.18.20.2 dev eth0 172.18.20.0/24 dev eth0 proto kernel scope link src

Re: [openstack-dev] [Fuel][Fuel-Library] Nominating Matthew Mosesohn for Fuel Library Core

+1 Aleksey Kasatkin On Thu, Feb 25, 2016 at 11:59 PM, Sergey Vasilenko wrote: > +1 > > > /sv > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org

[openstack-dev] [Horizon] Blueprints for Outreachy internship

Hello, I am looking for some blueprints in horizon that can be set aside for the Outreachy Internship program. If anyone has any blueprints in mind which are not needed anytime soon as well as not so difficult to implement please let me know so we can inc

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

> On 26 Feb 2016, at 02:38, Sean McGinnis wrote: > > On Thu, Feb 25, 2016 at 04:13:56PM +0800, Qiming Teng wrote: >> Hi, All, >> >> After reading through all the +1's and -1's, we realized how difficult >> it is to come up with a proposal that makes everyone happy. When we are >> discussing thi

Re: [openstack-dev] [Fuel][Fuel-Library] Nominating Matthew Mosesohn for Fuel Library Core

+1 On Fri, Feb 26, 2016 at 12:31 PM, Aleksey Kasatkin wrote: > +1 > > > Aleksey Kasatkin > > > On Thu, Feb 25, 2016 at 11:59 PM, Sergey Vasilenko < > svasile...@mirantis.com> wrote: > >> +1 >> >> >> /sv >> >> >> __ >> OpenSt

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

Hello, Fuelers! Yesterday we've faced an issue which came from puppet-neutron module: LP #1549934 . Fix was prepared very fast: https://review.openstack.org/#/c/284882/ (thanks Sergey for this). So, If CI is red on your patch please re-base it on top o

Re: [openstack-dev] [openstack-ansible] Installing networking-* pythonclient extensions to multiple locations

That makes sense Kevin. I don't have a use case in mind that would require access to the additional clients, so we can address that if/when it ever comes up. For now the utility container getting the extensions installed should suffice. As OSA is integrating with more types of plugins moving forwar

Re: [openstack-dev] [Fuel] Question about Feature Freeze Exceptions for non-invasive features

Hi Dmitry, The thing is it may not require changes in Fuel for 10.0 too, ideally we would like to add a couple of new gates to OpenStack infra, so they will be enabled for external extensions when there are any. Thanks, On Thu, Feb 25, 2016 at 8:55 PM, Dmitry Borodaenko wrote: > If the spec is

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

On Fri, Feb 26, 2016 at 10:44 AM, Miguel Angel Ajo Pelayo wrote: > >> On 26 Feb 2016, at 02:38, Sean McGinnis wrote: >> >> On Thu, Feb 25, 2016 at 04:13:56PM +0800, Qiming Teng wrote: >>> Hi, All, >>> >>> After reading through all the +1's and -1's, we realized how difficult >>> it is to come up

[openstack-dev] How do I calculate the semantic version prior to a release?

I understand the semantic versioning algorithm for calculating a new version. But what do I run, in a git repository, to do that calculation for me, and output: - the new semantic version that would be used if I asked for a formal release to PyPI - the corresponding Debian version - the corr

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

On 2016-02-26 11:13:52 + (+), Neil Jerram wrote: > I understand the semantic versioning algorithm for calculating a new > version. But what do I run, in a git repository, to do that calculation > for me, and output: > > - the new semantic version that would be used if I asked for a formal

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

On 26/02/16 11:16, Neil Jerram wrote: > I understand the semantic versioning algorithm for calculating a new > version. But what do I run, in a git repository, to do that calculation > for me, and output: > > - the new semantic version that would be used if I asked for a formal > release to PyPI >

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

Excerpts from Neil Jerram's message of 2016-02-26 11:13:52 +: > I understand the semantic versioning algorithm for calculating a new > version. But what do I run, in a git repository, to do that calculation > for me, and output: > > - the new semantic version that would be used if I asked f

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

Excerpts from Neil Jerram's message of 2016-02-26 11:27:05 +: > On 26/02/16 11:16, Neil Jerram wrote: > > I understand the semantic versioning algorithm for calculating a new > > version. But what do I run, in a git repository, to do that calculation > > for me, and output: > > > > - the new s

[openstack-dev] [devstack]what is different of stack-volumes-default and stack-volumes-lvmdriver-1

Hi I try to install devstack and enable cinder service. before , would create a volume for cinder. but now I found the devstack would create two VG:stack-volumes-lvmdriver-1 and stack-volumes-default. I check the cat /etc/cinder/cinder.conf and found the setting [lvmdriver-1] lvm_type = defa

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

On Fri, Feb 26, 2016 at 06:52:03AM -0500, Doug Hellmann wrote: > Excerpts from Neil Jerram's message of 2016-02-26 11:27:05 +: > > On 26/02/16 11:16, Neil Jerram wrote: [snipped] > > v = version.VersionInfo('networking-calico').semantic_version() > > print v.release_string() > > print v.brief_s

[openstack-dev] [all] audience for release notes

I've had a few conversations recently about "appropriate" content for release notes, so I thought it was worth starting a separate thread here to clarify. We have 3 potential audiences for release notes: 1. Developers consuming libraries or other code directly. 2. Deployers and operators. 3. End-

[openstack-dev] [murano] Berkshelf/Chef/Puppet installation on Murano images

Hi all, Some months ago, I started to work on a Murano integration with Berkshelf [1] to manage Chef cookbooks dependencies when Murano deploys a Chef cookbook (cf spec [2]). The main work is in murano-agent and was merged in last November [3]. However, I still haven't finalize the work with the

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

Excerpts from Thomas Bechtold's message of 2016-02-26 13:34:03 +0100: > On Fri, Feb 26, 2016 at 06:52:03AM -0500, Doug Hellmann wrote: > > Excerpts from Neil Jerram's message of 2016-02-26 11:27:05 +: > > > On 26/02/16 11:16, Neil Jerram wrote: > [snipped] > > > v = version.VersionInfo('network

[openstack-dev] [Fuel] UI code freeze

Dear colleagues, We are ready for moving UI javascript code to a separate git repository. Since now all review requests for fuel-web@master that are related to UI must be marked -2 and later abandoned. Once new project fuel-ui is created those changes should be backported to this new repository.

Re: [openstack-dev] [Fuel][Fuel-Library] Nominating Matthew Mosesohn for Fuel Library Core

Finally! +2 ! On Fri, Feb 26, 2016 at 9:08 PM, Roman Vyalov wrote: > +1 > > On Fri, Feb 26, 2016 at 12:31 PM, Aleksey Kasatkin > wrote: > >> +1 >> >> >> Aleksey Kasatkin >> >> >> On Thu, Feb 25, 2016 at 11:59 PM, Sergey Vasilenko < >> svasile...@mirantis.com> wrote: >> >>> +1 >>> >>> >>> /sv >>

Re: [openstack-dev] [puppet] how to run rspec tests? r10k issue

Hi Matt, Matt Fischer writes: > I ended up symlinking the r10k binary I have installed to the place it > wants it to be and it worked. I do have that in my Gemfile. Question > is, can we make this work without manual steps? Well, I was thinking I had a smart way to fix as it was working on my e

[openstack-dev] [Fuel][Solar] Integration in 9.0

As you may now we should integrate solar with fuel in 9.0. Integration in 9.0 will be very experimental and it will not affect fuel except: spec [](https:// review.openstack.org/283600)[https://review.openstack.org/283600](https://revi ew.openstack.org/283600) and [https://review.openstack.org/#/c/

[openstack-dev] [api][neutron] question on putting an existing tag

Hi API-WG, Neutron is implementing tag support for network resource [0]. The implementation follows 'Tags' guideline defined by API-WG [1]. I have a questions on the guideline. We can create a tag by PUT'ing an individual tag: What status code should be returned if a requested tag already e

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

On 02/23/2016 12:33 AM, Jay Pipes wrote: > OpenStack Conference <-- The main event. > OpenStack:How <-- The developer planning event. > > :) > > -jay Probably I'm dumb, but I still don't understand what's wrong with the name "design summit" for the developer planning event. Like most free softw

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

Alright, I have a first sample patch up for what was discussed in this thread here: (Keystone) https://review.openstack.org/#/c/285308/ The noted TODO on that is the cors middleware should (eventually) provide its own set_defaults method, so that CORS_OPTS isn't exposed publicly. However, dhellma

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

On 26/02/16 22:02, Thomas Goirand wrote: On 02/23/2016 12:33 AM, Jay Pipes wrote: OpenStack Conference <-- The main event. OpenStack:How <-- The developer planning event. :) -jay Probably I'm dumb, but I still don't understand what's wrong with the name "design summit" for the developer pl

Re: [openstack-dev] [Fuel][Solar] Integration in 9.0

Hi Jedrzej, >> Maybe instead blueprint in 1st step should we create full blown fuel-spec? If there is anything to be discussed in implementation, or there are different options to do it, it's better to have blueprint and spec, so everybody will be able to see what the integration looks like. Tha

Re: [openstack-dev] [Fuel][Solar] Integration in 9.0

> On 26 Feb 2016, at 14:40, Jedrzej Nowak wrote: > > 3. describe this everything in fuel docs > > Maybe instead blueprint in 1st step should we create full blown fuel-spec ? > That spec obviously will not require any QA activities. If we actually need feedback, then we need spec. I would go

[openstack-dev] [Nova] Re-booting the SR-IOV meeting

Hello folks, We are closing in on Mitaka-3 and it would be good to have a meeting and see which SR-IOV related bugfixes we want to try to land for Mitaka. The next meeting slot is next week on Tuesday (March 1st) at 13:00 UTC, so if there are any bugs you would like to discuss - that would be a g

Re: [openstack-dev] [all] audience for release notes

On Fri, Feb 26, 2016 at 6:34 AM, Doug Hellmann wrote: > I've had a few conversations recently about "appropriate" content for > release notes, so I thought it was worth starting a separate thread here > to clarify. > > We have 3 potential audiences for release notes: > > 1. Developers consuming l

Re: [openstack-dev] [all] audience for release notes

On Fri, Feb 26, 2016 at 09:03:49AM -0600, Brant Knudson wrote: > On Fri, Feb 26, 2016 at 6:34 AM, Doug Hellmann > wrote: > > > I've had a few conversations recently about "appropriate" content for > > release notes, so I thought it was worth starting a separate thread here > > to clarify. > > > >

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

Hi everyone, Summarizing the thread so far... The proposal was generally well-received, with negative feedback concentrated along the following themes: 1. "Two trips instead of one" There is a section of attendees which benefited from a single event: in-between people who do not generally g

Re: [openstack-dev] [api][neutron] question on putting an existing tag

On 02/26/2016 09:02 AM, Akihiro Motoki wrote: Hi API-WG, Neutron is implementing tag support for network resource [0]. The implementation follows 'Tags' guideline defined by API-WG [1]. I have a questions on the guideline. We can create a tag by PUT'ing an individual tag: What status code

Re: [openstack-dev] [murano] Berkshelf/Chef/Puppet installation on Murano images

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2/26/16 6:35 AM, Olivier Lemasle wrote: > Hi all, Hi! > Some months ago, I started to work on a Murano integration with > Berkshelf [1] to manage Chef cookbooks dependencies when Murano deploys > a Chef cookbook (cf spec [2]). This is awesome!

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

On 02/22/2016 10:14 AM, Thierry Carrez wrote: > Hi everyone, > > TL;DR: Let's split the events, starting after Barcelona. > > > > Comments, thoughts ? Thierry (and Jay, who wrote a similar note much earlier in February, and Lauren, who added more clarity over on the marketing list, and t

Re: [openstack-dev] [magnum] Failed to create trustee %(username) in domain $(domain_id)

Agreed. Every new features should be introduced in a backward-compatible way if possible. If new change will break existing version, it should be properly versioned and/or follow the corresponding deprecation process. Please feel free to ask for clarification if the procedure is unclear. Best

Re: [openstack-dev] [all] audience for release notes

On Fri, Feb 26, 2016 at 11:17 AM, Sean McGinnis wrote: > On Fri, Feb 26, 2016 at 09:03:49AM -0600, Brant Knudson wrote: > > On Fri, Feb 26, 2016 at 6:34 AM, Doug Hellmann > > wrote: > > > > > I've had a few conversations recently about "appropriate" content for > > > release notes, so I thought

Re: [openstack-dev] [api][neutron] question on putting an existing tag

On Fri, 26 Feb 2016, Jay Pipes wrote: On 02/26/2016 09:02 AM, Akihiro Motoki wrote: We can create a tag by PUT'ing an individual tag: What status code should be returned if a requested tag already exists? PUT /servers/1234567890/tags/qux The guideline defines 201 (+ Location header) on success

Re: [openstack-dev] [api][neutron] question on putting an existing tag

Hi, Jay, an explanation would be appreciated as it seems 409 doesn't match HTTP RFC[1] [1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html Cédric/ZZelle On Fri, Feb 26, 2016 at 4:36 PM, Jay Pipes wrote: > On 02/26/2016 09:02 AM, Akihiro Motoki wrote: > >> Hi API-WG, >> >> Neutron is i

Re: [openstack-dev] [api][neutron] question on putting an existing tag

Thanks Jay. I will send an update to api-wg repo as well. 2016-02-27 0:36 GMT+09:00 Jay Pipes : > On 02/26/2016 09:02 AM, Akihiro Motoki wrote: >> >> Hi API-WG, >> >> Neutron is implementing tag support for network resource [0]. >> The implementation follows 'Tags' guideline defined by API-WG [1].

Re: [openstack-dev] [api][neutron] question on putting an existing tag

On 02/26/2016 10:52 AM, Chris Dent wrote: > On Fri, 26 Feb 2016, Jay Pipes wrote: >> On 02/26/2016 09:02 AM, Akihiro Motoki wrote: >>> We can create a tag by PUT'ing an individual tag: >>> What status code should be returned if a requested tag already exists? >>> >>> PUT /servers/1234567890/tags/qu

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

On Fri, Feb 26, 2016 at 10:39:08AM -0500, Rich Bowen wrote: > > > On 02/22/2016 10:14 AM, Thierry Carrez wrote: > > Hi everyone, > > > > TL;DR: Let's split the events, starting after Barcelona. > > > > > > > > Comments, thoughts ? > > Thierry (and Jay, who wrote a similar note much earli

Re: [openstack-dev] [i18n][stackalytics] Translations metrics

2016-02-25 13:42 GMT+03:00 Ying Chun Guo : > Is it possible to link two IDs with email ? > > The link is possible by adding user profile into Stackalytics default_data.json. The patch needs to be similar to https://review.openstack.org/#/c/284638/1/etc/default_data.json. Basically it lists all use

Re: [openstack-dev] [openstack-ansible] Installing networking-* pythonclient extensions to multiple locations

?++ I think it'd be great to get that nailed down because, like you've mentioned, its likely we'll see a bit more of this as we widen our scope. -- Kevin Carter IRC: cloudnull From: Javeria Khan Sent: Friday, February 26, 2016 4:34 AM To: OpenStack Development

Re: [openstack-dev] [Fuel][murano][fuel-plugins] Move Murano to plugin from Fuel box

Igor, I've discussed this matter with Dmitry Borodaenko, and we agreed that much better way would be to not remove Murano from Fuel 9.0, but rather announce it deprecated once we will have a first version of plugin released. Additionally we can develop plugin in a way that it will disable checkbox

Re: [openstack-dev] [all] audience for release notes

Excerpts from Flavio Percoco's message of 2016-02-26 11:43:09 -0400: > On Fri, Feb 26, 2016 at 11:17 AM, Sean McGinnis > wrote: > > > On Fri, Feb 26, 2016 at 09:03:49AM -0600, Brant Knudson wrote: > > > On Fri, Feb 26, 2016 at 6:34 AM, Doug Hellmann > > > wrote: > > > > > > > I've had a few conv

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

On Fri, 2016-02-26 at 16:03 +, Daniel P. Berrange wrote: > On Fri, Feb 26, 2016 at 10:39:08AM -0500, Rich Bowen wrote: > > > > > > On 02/22/2016 10:14 AM, Thierry Carrez wrote: > > > Hi everyone, > > > > > > TL;DR: Let's split the events, starting after Barcelona. > > > > > > > > > >

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

On Fri, Feb 26, 2016 at 12:03 PM, Daniel P. Berrange wrote: > On Fri, Feb 26, 2016 at 10:39:08AM -0500, Rich Bowen wrote: >> >> >> On 02/22/2016 10:14 AM, Thierry Carrez wrote: >> > Hi everyone, >> > >> > TL;DR: Let's split the events, starting after Barcelona. >> > >> > >> > >> > Comments, t

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

On 02/26/2016 04:44 AM, Doug Hellmann wrote: Excerpts from Thomas Bechtold's message of 2016-02-26 13:34:03 +0100: On Fri, Feb 26, 2016 at 06:52:03AM -0500, Doug Hellmann wrote: Excerpts from Neil Jerram's message of 2016-02-26 11:27:05 +: On 26/02/16 11:16, Neil Jerram wrote: [snipped]

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

Thierry Carrez wrote: 1. "Two trips instead of one" There is a section of attendees which benefited from a single event: in-between people who do not generally go to any midcycle events and successfully split their attention between the design summit and the main conference when they were overla

Re: [openstack-dev] [all] audience for release notes

On 02/26/2016 10:41 AM, Doug Hellmann wrote: Excerpts from Flavio Percoco's message of 2016-02-26 11:43:09 -0400: On Fri, Feb 26, 2016 at 11:17 AM, Sean McGinnis wrote: On Fri, Feb 26, 2016 at 09:03:49AM -0600, Brant Knudson wrote: On Fri, Feb 26, 2016 at 6:34 AM, Doug Hellmann wrote: I'v

Re: [openstack-dev] [api][neutron] question on putting an existing tag

2016-02-27 1:02 GMT+09:00 Sean Dague : > On 02/26/2016 10:52 AM, Chris Dent wrote: >> On Fri, 26 Feb 2016, Jay Pipes wrote: >>> On 02/26/2016 09:02 AM, Akihiro Motoki wrote: We can create a tag by PUT'ing an individual tag: What status code should be returned if a requested tag already ex

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

On Fri, Feb 26, 2016 at 08:55:52AM -0800, James Bottomley wrote: > On Fri, 2016-02-26 at 16:03 +, Daniel P. Berrange wrote: > > On Fri, Feb 26, 2016 at 10:39:08AM -0500, Rich Bowen wrote: > > > > > > > > > On 02/22/2016 10:14 AM, Thierry Carrez wrote: > > > > Hi everyone, > > > > > > > > TL;

Re: [openstack-dev] [all] audience for release notes

On Fri, Feb 26, 2016 at 1:07 PM, Monty Taylor wrote: > On 02/26/2016 10:41 AM, Doug Hellmann wrote: >> >> Excerpts from Flavio Percoco's message of 2016-02-26 11:43:09 -0400: >>> >>> On Fri, Feb 26, 2016 at 11:17 AM, Sean McGinnis >>> wrote: >>> On Fri, Feb 26, 2016 at 09:03:49AM -0600, Bran

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

On 26/02/16 18:08, "Thierry Carrez" wrote: >> >> 2. Community split >> >> There is fear that the contributor-specific event will separate the >> community into two groups, with developers skipping the main event and >> non-developers not providing any feedback to the contributor-specific >> e

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

On Fri, 2016-02-26 at 17:24 +, Daniel P. Berrange wrote: > On Fri, Feb 26, 2016 at 08:55:52AM -0800, James Bottomley wrote: > > On Fri, 2016-02-26 at 16:03 +, Daniel P. Berrange wrote: > > > On Fri, Feb 26, 2016 at 10:39:08AM -0500, Rich Bowen wrote: > > > > > > > > > > > > On 02/22/2016

Re: [openstack-dev] [Neutron] Gate failure

This has merged, so you can resume your previously scheduled mad-merge-for-Mitaka and break it all again. Thanks, doug > On Feb 25, 2016, at 2:46 PM, Armando M. wrote: > > Folks, > > The API job recent breakage prevents us from merging code. Please refrain > from pushing patches to the merge

[openstack-dev] [Cinder] [nova] Work flow for detaching a volume

I want to confirm the correct work flow for detaching a volume, Both nova and cinder (unpublished, available through cinder.volumes.detach) provides detach volume API. Only nova seems to have correct work flow in terms of detaching a volume i.e. 1) detaches the volume from the VM (libvirt.volum

Re: [openstack-dev] [Fuel] Question about Feature Freeze Exceptions for non-invasive features

I understand that, but your question was about requesting an FFE for this spec, which you wouldn't need to do if you just targeted it to 10.0. On Fri, Feb 26, 2016 at 01:39:08PM +0300, Evgeniy L wrote: > Hi Dmitry, > > The thing is it may not require changes in Fuel for 10.0 too, ideally we > wou

Re: [openstack-dev] [Neutron] Gate failure

On 26 February 2016 at 11:43, Doug Wiegley wrote: > This has merged, so you can resume your previously scheduled > mad-merge-for-Mitaka and break it all again. > Assume this is the default behavior unless told otherwise. So, yes go nuts! Cheers, Armando > > Thanks, > doug > > On Feb 25, 2016,

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

On 27 February 2016 at 00:13, Neil Jerram wrote: > I understand the semantic versioning algorithm for calculating a new > version. But what do I run, in a git repository, to do that calculation > for me, and output: pbr does that automatically, generating a pre-release version. The regular part

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

On 27 February 2016 at 00:24, Jeremy Stanley wrote: > On 2016-02-26 11:13:52 + (+), Neil Jerram wrote: >> I understand the semantic versioning algorithm for calculating a new >> version. But what do I run, in a git repository, to do that calculation >> for me, and output: >> >> - the new

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

On 27 February 2016 at 00:52, Doug Hellmann wrote: > Excerpts from Neil Jerram's message of 2016-02-26 11:27:05 +: >> On 26/02/16 11:16, Neil Jerram wrote: >> > I understand the semantic versioning algorithm for calculating a new >> > version. But what do I run, in a git repository, to do tha

Re: [openstack-dev] How do I calculate the semantic version prior to a release?

On 27 February 2016 at 01:34, Thomas Bechtold wrote: > On Fri, Feb 26, 2016 at 06:52:03AM -0500, Doug Hellmann wrote: >> Excerpts from Neil Jerram's message of 2016-02-26 11:27:05 +: >> > On 26/02/16 11:16, Neil Jerram wrote: > [snipped] >> > v = version.VersionInfo('networking-calico').semant

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

-Original Message- From: James Bottomley [mailto:james.bottom...@hansenpartnership.com] Sent: February-26-16 12:38 PM To: Daniel P. Berrange Cc: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] A proposal to separate the design summit On Fr

Re: [openstack-dev] [Cinder] [nova] Work flow for detaching a volume

On Fri, Feb 26, 2016 at 06:11:15PM +, Srinivas Sakhamuri wrote: > I want to confirm the correct work flow for detaching a volume, Both nova > and cinder (unpublished, available through cinder.volumes.detach) provides > detach volume API. Only nova seems to have correct work flow in terms of > d

Re: [openstack-dev] [TripleO] Show TripleO: A terminal dashboard

Interesting! So this could conceivably be another consumer of the API, right? A sort of CLI UI? On 02/25/2016 01:10 PM, Dougal Matthews wrote: > Hi all, > > Over the past couple of weeks in my spare time I put together a basic > Python urwid dashboard for TripleO. You can see the usage and some

[openstack-dev] [cross-project] Introducing Cross project Quotas WG meetings

Hello everyone, A few days back there has been some interest spurred again in the cross-project initiatives around Quotas. A few of the projects are trying to implement quotas in great detail and the ecosystem would greatly benefit from knowledge sharing and common guidelines. So, we would like t

Re: [openstack-dev] [Cinder] [nova] Work flow for detaching a volume

On Fri, Feb 26, 2016 at 12:47 PM, Sean McGinnis wrote: > On Fri, Feb 26, 2016 at 06:11:15PM +, Srinivas Sakhamuri wrote: > > I want to confirm the correct work flow for detaching a volume, Both nova > > and cinder (unpublished, available through cinder.volumes.detach) > provides > > detach vo

Re: [openstack-dev] [all] audience for release notes

Excerpts from Monty Taylor's message of 2016-02-26 11:07:29 -0600: > On 02/26/2016 10:41 AM, Doug Hellmann wrote: > > Excerpts from Flavio Percoco's message of 2016-02-26 11:43:09 -0400: > >> On Fri, Feb 26, 2016 at 11:17 AM, Sean McGinnis > >> wrote: > >> > >>> On Fri, Feb 26, 2016 at 09:03:49AM

Re: [openstack-dev] [devstack] stack.sh keeps failing with RTNETLINK answers: Network is unreachable

Paul Carlton wrote: > Sean > > Don't think unstack failed, when I manually create the device ( sudo > ovs-vsctl --no-wait -- --may-exist add-br br-ex) unstack.sh removes it. > > sudo ip route show > default via 172.18.20.1 dev eth0 > 169.254.169.254 via 172.18.20.2 dev eth0 > 172.18.20.0/24 dev e

Re: [openstack-dev] [Nova] Re-booting the SR-IOV meeting

Hello, Thank you for your message. Is there any list of only SR-IOV related bugfixes? If there is any pointer, that would be very useful. Cheers, Shinobu On Fri, Feb 26, 2016 at 11:58 PM, Nikola Đipanov wrote: > Hello folks, > > We are closing in on Mitaka-3 and it would be good to have a meet

Re: [openstack-dev] [fuel] Fuel plugins: lets have some rules

Yes, this is a reasonable way to handle repo creation requests, and we should update our wiki to reflect this: https://wiki.openstack.org/wiki/Fuel/Plugins#Repo On Mon, Feb 15, 2016 at 05:01:39PM +0100, Mateusz Matuszkowiak wrote: > Dmitry, > > So this changes the workflow for the devopses, the f

Re: [openstack-dev] [fuel] Fuel plugins: lets have some rules

On Thu, Feb 25, 2016 at 08:31:26AM +0100, Andreas Jaeger wrote: > On 2016-02-03 03:27, Dmitry Borodaenko wrote: > > [...] > > Level 1. Plugin is actively supported by Fuel team > > > > As we expand plugin capabilities and move more functionality from Fuel > > core into plugins, we will inevitably

Re: [openstack-dev] [fuel] Fuel plugins: lets have some rules

Excellent point, and also a good reminder that we should fix our system tests documentation, at the moment it's slightly too short: https://docs.fuel-infra.org/fuel-dev/develop/system_tests/tree.html The most relevant docuement I could find was this spec: https://specs.openstack.org/openstack/fu

Re: [openstack-dev] [Fuel][Plugins] Rules for Fuel Plugins: short-term perspective action plan

Irina, Thanks for putting this plan together. Looks good to me with a few minor corrections :) On Wed, Feb 24, 2016 at 05:32:01PM +0300, Irina Povolotskaya wrote: > Hi Dmitry, > > I wanted to follow-up on the 'let's have some rules' email. > For now, there are many requests on repo creation for

[openstack-dev] [Neutron] Mid-cycle report

Hi Neutrinos, For those of you who couldn't join in person, please find a few notes below to capture some of the highlights of the event. I would like to thank everyone one who helped me put this report together, and everyone who helped make this mid-cycle a fruitful one. I would also like to th

[openstack-dev] [dragonflow] db consistency progress

2016年2月24日星期三，Gal Sagie > 写道： > Hi Li Ma, > > Great job on this! > > I think Rally is the correct way to test something like that, what you > could use to check the end to end > solution is try to restart the DF DB server for timeouts during API > configurations. > > At this point of time, i think

[openstack-dev] OpenStack Developer Mailing List Digest Feb 20-26

HTML rendered version: http://www.openstack.org/blog/2016/02/openstack-developer-mailing-list-digest-20160226/ Audience for Release Notes == * We have 3 potential audiences for release notes: - Developers consuming libraries or other code directly. - Deployers and

Re: [openstack-dev] [puppet] how to run rspec tests? r10k issue

This worked great. Thanks for this and the upstream fix. On Fri, Feb 26, 2016 at 6:25 AM, Sofer Athlan-Guyot wrote: > Hi Matt, > > Matt Fischer writes: > > > I ended up symlinking the r10k binary I have installed to the place it > > wants it to be and it worked. I do have that in my Gemfile. Qu

Re: [openstack-dev] [TripleO] Show TripleO: A terminal dashboard

That's pretty much interesting and fantastic to me. To use the dashboard, is it good enough to activate ironic in devstack? Cheers, Shinobu On Sat, Feb 27, 2016 at 5:06 AM, Ben Nemec wrote: > Interesting! So this could conceivably be another consumer of the API, > right? A sort of CLI UI? > >

Re: [openstack-dev] [Magnum] API service won't work if conductor down?

Hi all, I want to allow magnum-api to access DB, so that magnum-api can work even if magnum-conductor is down. Best Regards, Wanghua On Thu, Feb 4, 2016 at 3:42 PM, 王华 wrote: > I think we should allow magnum-api to access DB directly like nova-api. > > As describe in [1], nova may have many co