Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Jeremy Stanley's message of 2016-04-19 15:00:24 +: > On 2016-04-19 09:10:11 -0400 (-0400), Doug Hellmann wrote: > [...] > > We have the global list and the upper constraints list, and both > > are intended to be used to signal to packaging folks what we think > > ought to be

[openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

Sorry, it is too late to adjust the schedule now, but I don't mind to have a pre-discussion here. If you have opinions/ideas on this topic but cannot attend the session [1], we'd like to have you inputs in this ML or in the etherpad [2]. This will help to set the stage for the session. For

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On Tue, Apr 19, 2016 at 09:57:56AM -0500, Dean Troyer wrote: > On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: > > > I wonder how much of that is Token caching. In a typical CLI use patter, > > a new token is created each time a client is called, with no passing of a > >

Re: [openstack-dev] [nova] Nova commands

On Tue, 19 Apr 2016 19:31:04 +0800, Kenny Ji-work wrote: I have installed openstack mitaka, when I execute any nova's commands with the result displayed below: [root@devstack scripts]# nova list *ERROR (AttributeError): 'unicode' object has no attribute 'get'* I installed openstack as the

Re: [openstack-dev] [Congress]Authorization mechanisms for each user

Hi Yuki, Sounds good. The Congress team will be at Austin next week at the summit. Most of the team will be at most of the events that you find by searching for "Congress". Let us know if you want to meet face-to-face to discuss further.

Re: [openstack-dev] [Neutron] L3 HA testing on scale

Is there any session presenting these results during the Summit? It will be awesome to have a session on this. I could extend the invite to the Ops Meet-up. We have a section on lighting talks where the team will be very intesreted in learning from your testing. Edgar From: Anna Kamyshnikova

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/19/2016 11:30 AM, Ian Cordasco wrote: >> On 2016-04-19 14:59:19 +0200 (+0200), Thomas Goirand wrote: >>> On 04/19/2016 01:01 PM, Chris Dent wrote: On Tue, 19 Apr 2016, Thomas Goirand wrote: >> [...] > Most users are consuming packages from distributions. Also, if > you're using

Re: [openstack-dev] [Vitrage] questions about "relationships"

Hi Tony, Glad to help :) . Regarding your questions from the last two emails: 1. Yes, the Entity Graph (what you called the global graph), is generated regardless of what templates were defined. You can get this graph using the CLI command "vitrage topology show", and we are currently

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

  -Original Message- From: Jeremy Stanley Reply: OpenStack Development Mailing List (not for usage questions) Date: April 19, 2016 at 09:50:27 To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [keystone] Problem with WSGI on keystone

Hi All, Recently, I've been having trouble running stack.sh from scratch. With the default configuration I've been using for a while, I get the following error in /opt/stack/logs/key.log: 2016-04-19 16:05:26.630 22047 DEBUG keystone.common.controller [req-3d384c1f-8b9a-4ff0-aa30-a4aad73963fb

Re: [openstack-dev] [Magnum]Cache docker images

why not just allow a prefix to be added to the container name? you can then have a container named: foo/mycontainer and the prefix could be set to mylocalserver.org:8080: mylocalserver.org:8080/foo/mycontainer Then if the site needs local only containers, they can set up a local repo. Be it a

Re: [openstack-dev] [nova] [neutron] the nova network facade that isn't

On 04/18/2016 04:48 PM, Matt Riedemann wrote: > > I guess at a high level my thinking was always, if nova-network isn't > deprecated, and these APIs are broken when using Neutron, it's (mostly) > trivial to add a proxy to fill those gaps (like my spec for > os-virtual-interfaces). So then when

Re: [openstack-dev] [Vitrage] questions about "relationships"

Hi Elisha, Thanks for your quick response. I think I got your points. To double confirm, further questions are coming :): 1. Regardless if there is template definition, Vitrage constructs a graph based on the data from plugins defined in datasources conf. Let's call it "global graph". Is

[openstack-dev] [release][oslo] osprofiler 1.3.0 release (newton)

We are overjoyed to announce the release of: osprofiler 1.3.0: OpenStack Profiler Library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/osprofiler With package available at: https://pypi.python.org/pypi/osprofiler

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On Tue, Apr 19, 2016, at 08:14 AM, Doug Hellmann wrote: > Excerpts from Jeremy Stanley's message of 2016-04-19 15:00:24 +: > > On 2016-04-19 09:10:11 -0400 (-0400), Doug Hellmann wrote: > > [...] > > > We have the global list and the upper constraints list, and both > > > are intended to be

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

From: Adam Young [ayo...@redhat.com] Sent: Tuesday, April 19, 2016 7:06 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service On 04/18/2016 09:19 AM, Daniel P. Berrange wrote: There have

Re: [openstack-dev] [keystone][barbican][designate][murano][fuel][ironic][cue][ceilometer][astara][gce-api][kiloeyes] keystoneclient 3.0.0 release - no more CLI!

On 04/18/2016 10:05 PM, Steve Martinelli wrote: Everyone, I sent out a note about this on Friday [1], but I'll repeat it here and tag individual projects. The keystone team *will* be releasing a new version of keystoneclient on *Thursday* that will not include a CLI. A quick codesearch showed

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Thomas Goirand's message of 2016-04-19 00:19:03 +0200: > Hi Doug, > > I very much welcome opening such a thread before the discussion at the > summit, as often, sessions are too short. Taking the time to write > things down first also helps having a more constructive discussion.

Re: [openstack-dev] [Magnum] duplicate scripts in different coes

I made a first attempt to factor out the configuration of different storage drivers in this change [1]. Spyros [1] https://review.openstack.org/#/c/284720/ On 19 April 2016 at 05:45, Eli Qiao wrote: > Sure that is the things I want to cleanup long time before. > I

Re: [openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

Excerpts from Ian Wienand's message of 2016-04-19 12:11:35 +1000: > Hi, > > diskimage-builder has fallen under the "centralised release tagging" > mechanism [1], presumably because it is under tripleo. I'd like to > propose that we don't do that. Yes, we've set up all official projects to use

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

On 2016-04-18 19:42, Joshua Harlow wrote: > Andreas Jaeger wrote: >> On 04/17/2016 09:15 PM, Davanum Srinivas wrote: >>> Hi Oslo folks, Andreas and others, >>> >>> Over the weekend oslo.log 3.4.0 was released. This broke keystone CI >>> jobs [2], even though the 3.4.0 was not specified in

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 2016-04-19 09:10:11 -0400 (-0400), Doug Hellmann wrote: [...] > We have the global list and the upper constraints list, and both > are intended to be used to signal to packaging folks what we think > ought to be used. I'm glad that signaling is working, and maybe > that means you're right that

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/18/2016 09:19 AM, Daniel P. Berrange wrote: There have been threads in the past about the slowness of the "openstack" client tool such as this one by Sean last year: http://lists.openstack.org/pipermail/openstack-dev/2015-April/061317.html Sean mentioned a 1.5s fixed overhead on

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Excerpts from Andreas Jaeger's message of 2016-04-19 08:34:53 +0200: > On 2016-04-18 22:34, Davanum Srinivas wrote: > > On Mon, Apr 18, 2016 at 4:28 PM, Joshua Harlow > > wrote: > >> Okie, the following reviews are up: > >> > >> https://review.openstack.org/307461

[openstack-dev] [tosca-parser] [heat-translator] No weekly meeting on April 21 and 28

Hello Team, Considering OpenStack Austin Summit and preparation, there will be no IRC weekly meetings for next two weeks for the tosca-parser and heat-translator projects. Safe travels. See you in Austin! Thanks! Regards, Sahdev Zala

Re: [openstack-dev] [keystone][barbican][designate][murano][fuel][ironic][cue][ceilometer][astara][gce-api][kiloeyes] keystoneclient 3.0.0 release - no more CLI!

On 04/19/2016 04:34 PM, Dmitry Tantsur wrote: On 04/18/2016 10:05 PM, Steve Martinelli wrote: Everyone, I sent out a note about this on Friday [1], but I'll repeat it here and tag individual projects. The keystone team *will* be releasing a new version of keystoneclient on *Thursday* that will

[openstack-dev] [tosca-parser] [heat-translator] Collaboration with [Tacker] project at the Austin Summit

Hi Team, We will be having a collaborative session with Tacker project at the summit. The following Tacker working session will be focused on it, Tacker Developer Track: April 28, 2016 : 3:10 - 3:50pm / MR 415A: Working Session If you are at the summit, please join. Safe travels. See you in

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 2016-04-19 14:59:19 +0200 (+0200), Thomas Goirand wrote: > On 04/19/2016 01:01 PM, Chris Dent wrote: > > On Tue, 19 Apr 2016, Thomas Goirand wrote: [...] > > > Most users are consuming packages from distributions. Also, if > > > you're using containers, probably you will also prefer using > > >

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: > I wonder how much of that is Token caching. In a typical CLI use patter, > a new token is created each time a client is called, with no passing of a > token between services. Using a session can greatly decrease the number

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Doug, The right thing to add in projects is a dependency on oslo.i18n, which will then transitively pull in a good version of Babel. So when we do want to throw exceptions or log messages, we should add oslo.i18n and not Babel directly. Thanks, Dims On Tue, Apr 19, 2016 at 9:17 AM, Doug

Re: [openstack-dev] [Vitrage] questions about "relationships"

One more question, I suppose "EvaluatorEventTransformer" is used to handle events sent by ScenarioEvaluator, and add/delete vertex/edge to the "global graph" triggered by Actions. Is it right? From: EXT Wang, Tony T (Nokia - CN) [mailto:tony_t.w...@nokia.com] Sent: Tuesday, April 19, 2016 10:01

[openstack-dev] Manila manage share problem

Hello, I am trying to use OpenStack Manila to manage custom standalone shared file system that supports NFS protocol. Is there any way to use Manila Generic Driver with standalone NFS server? I tried to execute manila manage devstack@generic1#GENERIC1 nfs :/folder --name my_share

Re: [openstack-dev] [keystone] Problem with WSGI on keystone

On Tue, Apr 19, 2016 at 11:57 AM, Rosensweig, Elisha (Nokia - IL) < elisha.rosensw...@nokia.com> wrote: > Hi All, > > Recently, I've been having trouble running stack.sh from scratch. With the > default configuration I've been using for a while, I get the following > error in

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/19/2016 12:44 PM, Clint Byrum wrote: > Excerpts from Michał Jastrzębski's message of 2016-04-18 10:29:20 -0700: >> What I meant is if you have liberty Nova and liberty Cinder, and you >> want to upgrade Nova to Mitaka, you also upgrade Oslo to Mitaka and >> Cinder which was liberty either

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/19/2016 10:16 AM, Daniel P. Berrange wrote: On Tue, Apr 19, 2016 at 09:57:56AM -0500, Dean Troyer wrote: On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: I wonder how much of that is Token caching. In a typical CLI use patter, a new token is created each time a

[openstack-dev] [Neutron] meeting topics for 4/21/2016 networking-sfc project IRC meeting

Hi everyone, Here are some topics I have for this week's project meeting discussion(The meeting time is not changed, still UTC 1700 Thursday). Feel free to add more. You can also find the meeting topics in the project wiki page.

Re: [openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

Excerpts from Jeremy Stanley's message of 2016-04-19 15:41:26 +: > On 2016-04-19 09:22:57 -0400 (-0400), Doug Hellmann wrote: > > Excerpts from Ian Wienand's message of 2016-04-19 12:11:35 +1000: > [...] > > > I don't expect the stable release team to be involved with all this; > > > but if we

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Matthew Thode's message of 2016-04-18 11:22:38 -0700: > On 04/18/2016 12:33 PM, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2016-04-18 10:23:37 -0500: > >> On 04/18/2016 08:24 AM, Hayes, Graham wrote: > >>> On 18/04/2016 13:51, Sean Dague wrote: > On

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

From: Ian Cordasco [sigmaviru...@gmail.com] Sent: Tuesday, April 19, 2016 11:11 AM To: Perry, Sean; OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

What Dan sees WRT a persistent client process, though, is a combination of those two things: saving the Python loading and the Keystone round trips. If I replace the import of openstack.shell with a main that just returns 0 in the OSC entry point and time it the result floats around 0.030s on

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

  -Original Message- From: Perry, Sean Reply: OpenStack Development Mailing List (not for usage questions) Date: April 19, 2016 at 12:41:02 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Michał Jastrzębski's message of 2016-04-18 10:29:20 -0700: > What I meant is if you have liberty Nova and liberty Cinder, and you > want to upgrade Nova to Mitaka, you also upgrade Oslo to Mitaka and > Cinder which was liberty either needs to be upgraded or is broken, > therefore

Re: [openstack-dev] Manila manage share problem

Hello, Grigoriy One or more of following requirements are not met in your case: 1) Generic driver should be configured to use "driver_handles_share_servers=False" mode. 2) Share type "my_share_type" should contain extra spec "driver_handles_share_servers=False", same as for (1) 3) Your NFS

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

Original Message - > From: "Zhipeng Huang" > To: "OpenStack Development Mailing List (not for usage questions)" > > > Thanks Hongbin, > > Actually we have a new project called Fuxi that sorta like Kuryr for > storage, would be

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Thomas Goirand's message of 2016-04-19 05:59:19 -0700: > On 04/19/2016 01:01 PM, Chris Dent wrote: > > We also, however, need to consider what the future might look like and > > at least for some people and situations > > I agree. > > > the future does not involve > > debs or rpms

Re: [openstack-dev] [Magnum]Cache docker images

Yes, that is an alternative. The complication is how to secure the communication between Magnum bays and the standalone docker registry. I assume we needs some custom logic to setup the communication channel (i.e. install the TLS credential). One way to support it is to add a configuration hook

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

A pluginless CLI that simply used REST calls rather than the python-clientlibs should be able to launch in get to the business of doing work in 0.2 seconds - counting time to load and parse clouds.yaml. That time could be reduced - the time spent in occ parsing vendor json files is not strictly

Re: [openstack-dev] [oslo][keystone][documentation][gate] Babel dependency for oslo.log

Your wish has been delivered ;) https://review.openstack.org/#/c/307983/ -Josh Andreas Jaeger wrote: On 2016-04-18 19:42, Joshua Harlow wrote: Andreas Jaeger wrote: On 04/17/2016 09:15 PM, Davanum Srinivas wrote: Hi Oslo folks, Andreas and others, Over the weekend oslo.log 3.4.0 was

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On Tue, 19 Apr 2016, Thomas Goirand wrote: On 04/19/2016 01:01 PM, Chris Dent wrote: Do I expect it all to happen like I want? No. Do I hope that my concerns will be integrated in the discussion? Yes. I fail to see what kind of concerns you have with the current situation. Could you attempt

Re: [openstack-dev] [puppet] weekly meeting #79

wrote: > Hi, > > We'll have our weekly meeting tomorrow at 3pm UTC on > #openstack-meeting4. > > https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack > > As usual, free free to bring topics in this etherpad: > https://etherpad.openstack.org/p/puppet-openstack-weekl

Re: [openstack-dev] [Horizon][stable] proposing Rob Cresswell for Horizon stable core

On 4/12/2016 5:06 AM, Matthias Runge wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/04/16 05:12, Tony Breeds wrote: On Thu, Apr 07, 2016 at 12:01:31PM +0200, Matthias Runge wrote: Hello, I'm proposing Rob Cresswell to become stable core for Horizon. I thought, in the past all

Re: [openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

On 2016-04-19 09:22:57 -0400 (-0400), Doug Hellmann wrote: > Excerpts from Ian Wienand's message of 2016-04-19 12:11:35 +1000: [...] > > I don't expect the stable release team to be involved with all this; > > but if we miss windows then we're left either going to efforts getting > > one of a

Re: [openstack-dev] [all] Removal of in progress console log access

Sean Dague writes: > Yes, that would let you see the results of an individual experimental > run that is complete before they all return and post to the change. Once > they are all done, they are listed on the change, so that's good enough. We'll need a Zuul restart for this, so

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

Jay, Mesosphere open sourced DC/OS today under Apache 2 license  https://mesosphere.com/blog/2016/04/19/open-source-dcos/ --- Egor From: Jay Lau To: OpenStack Development Mailing List (not for usage questions) Sent: Friday,

[openstack-dev] [release][nova] python-novaclient 4.0.0 release (newton)

We are psyched to announce the release of: python-novaclient 4.0.0: Client library for OpenStack Compute API This release is part of the newton release series. With source available at: https://git.openstack.org/cgit/openstack/python-novaclient With package available at:

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On Tue, Apr 19, 2016 at 7:57 AM, Dean Troyer wrote: > On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: > >> I wonder how much of that is Token caching. In a typical CLI use patter, >> a new token is created each time a client is called, with no passing

[openstack-dev] [Fuel][Plugins] One plugin - one Launchpad project

Hi to everyone, as you possibly know (at least, those dev. teams working on their Fuel plugins) we have a fuel-plugins Launchpad project [1] which serves as all-in-one entry point for filing bugs, related to plugin-specific problems. nevertheless, this single project is a bad idea in terms of

Re: [openstack-dev] [heat] convergence cancel messages

On 17/04/16 00:44, Anant Patil wrote: I think it is a good idea, but I see that a resource can be marked unhealthy only after it is done. Currently, yes. The idea would be to change that so that if it finds the resource IN_PROGRESS then it kills the thread and makes

Re: [openstack-dev] [all] Removal of in progress console log access

On 04/19/2016 12:05 PM, James E. Blair wrote: > Sean Dague writes: > >> Yes, that would let you see the results of an individual experimental >> run that is complete before they all return and post to the change. Once >> they are all done, they are listed on the change, so that's

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On Tue, 19 Apr 2016, Jeremy Stanley wrote: Could just be that my beard has gotten a little too grey, but I still very much prefer using stabilized software packaged by traditional Linux distributions or similar Unix derivatives and covered under security patched backports. My hope has always

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

  -Original Message- From: Thomas Goirand Reply: OpenStack Development Mailing List (not for usage questions) Date: April 18, 2016 at 17:21:36 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 04/19/2016 04:48 AM, Thierry Carrez wrote: > Thomas Goirand wrote: >> [...] >> Remember that in distros, there's only a single version of a library at >> any given time, at the exception of transitions (yes, in Red Hat it's >> technically possible to install multiple versions, but the policy >>

Re: [openstack-dev] [Magnum]Cache docker images

Eli, The approach of pre-pulling docker images has a problem. It only works for specific docker storage driver. In comparison, the tar file approach is portable across different storage drivers. Best regards, Hongbin From: taget [mailto:qiaoliy...@gmail.com] Sent: April-19-16 4:26 AM To:

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/19/2016 02:17 PM, Monty Taylor wrote: Rather than ditching python for something like go, I'd rather put together a CLI with no plugins and that only depended on keystoneauth and os-client-config as libraries. No? Bingo. -jay

Re: [openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

On Tue, Apr 19, 2016 at 1:25 PM, Doug Hellmann wrote: > It's not just about control, it's also about communication. One of > the most frequent refrains we hear is "what is OpenStack", and one > way we're trying to answer that is to publicize all of the things > we release

Re: [openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

On Tue, Apr 19, 2016 at 11:41 AM, Jeremy Stanley wrote: > DIB is an unfortunate combination of a mostly stable framework and a > large pre-written set of scripts and declarative data which is > constantly evolving for widespread use outside the OpenStack > ecosystem (so most of

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

What about a plugin cache like feature? if no cache, or cache older then 24 hours, dump all discovered plugins into a python file that loads them more statically. if the cache is valid, just use it. and a hook in rpms/debs to remove the cache on plugin install/uninstall. Thanks, Kevin

[openstack-dev] [ironic] upgrade support between which versions of ironic?

Hi, Currently, ironic doesn't support ("live", "online", "rolling", or minimal-downtime) upgrades between named versions of ironic. (Where "named version" is the final release or stable release that is associated with a development cycle). So for example, Liberty -> Mitaka release. We've been

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

Or make use of openstacksdk instead of pulling in all the clients stevemar From: Jay Pipes To: openstack-dev@lists.openstack.org Date: 2016/04/19 03:11 PM Subject:Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

Re: [openstack-dev] [packaging-deb] [infra] publishing built packages for others to depend on

On 2016-04-19 11:30:35 +0200 (+0200), Thomas Goirand wrote: [...] > Which direction does the infra team believe I should take? Aside from a little bit of feedback I provided in #openstack-infra today, I don't have a bunch of time to dig into this before next week but it looks like the packaging

Re: [openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

On 04/20/2016 06:09 AM, Fox, Kevin M wrote: I've seen dib updated and broken things. I've seen dib elements updated and things broke (centos6 removal in particular hurt.) By the time it gets to a release, however, anything we've broken is already baked in. Any changes in there have already

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On Tue, Apr 19, 2016 at 12:17 PM, Monty Taylor wrote: > On 04/19/2016 10:16 AM, Daniel P. Berrange wrote: > >> On Tue, Apr 19, 2016 at 09:57:56AM -0500, Dean Troyer wrote: >> >>> On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: >>> >>> I wonder how

Re: [openstack-dev] [nova] [neutron] the nova network facade that isn't

I've got scripts I use nova floating ip subcommands to attach/detach floating ips occasionally because it was easier to write then using the equiv neutron commands even though I'm using neutron. I'd think some folks will be doing the same. That being said, we'll have to rewrite all that code

Re: [openstack-dev] [ironic] upgrade support between which versions of ironic?

Thanks for starting the thread, Ruby. We need to first establish a grenade job to test "cold upgrades" and assert the supports-upgrade tag. I believe Ironic meets all the criteria for that tag except: - having a job that tests it (so, you know, it might be broken and I might be wrong) - having

Re: [openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

As an Op, I've been bitten by both sides of this I've seen dib updated and broken things. I've seen dib elements updated and things broke (centos6 removal in particular hurt.) I've appreciated dib elements getting fixed quickly at times because distro's changed, and the element needed

Re: [openstack-dev] [nova] [neutron] the nova network facade that isn't

On 04/18/2016 05:41 PM, Jay Pipes wrote: On 04/18/2016 04:33 PM, Sean Dague wrote: When doing bug triage this morning a few bugs popped up: - https://bugs.launchpad.net/nova/+bug/1456899 - nova absolute-limits Security groups count incorrect when using Neutron -

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/19/2016 03:24 PM, Steve Martinelli wrote: Or make use of openstacksdk instead of pulling in all the clients This would be a good thing, yes. -jay __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Cinder] API features discoverability

On 04/18/2016 09:17 AM, Ramakrishna, Deepti wrote: > Hi Michal, > > This seemed like a good idea when I first read it. What more, the server code > for extension listing [1] does not do any authorization, so it can be used > for any logged in user. > > However, I don't know if requiring the

Re: [openstack-dev] [Magnum]Cache docker images

I'm kind of uncomfortable as an op with the prebundled stuff. how do you upgrade things when needed if there is no way to pull updated images from a central place? Thanks, Kevin From: Hongbin Lu [hongbin...@huawei.com] Sent: Tuesday, April 19, 2016 11:56 AM To:

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

From: Fox, Kevin M [kevin@pnnl.gov] Sent: Tuesday, April 19, 2016 12:59 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service What about a plugin

Re: [openstack-dev] [puppet] Stepping down from puppet-openstack-core

On Mon, Apr 18, 2016 at 8:37 AM, Sebastien Badia wrote: > Hello here, > > I would like to ask to be removed from the core reviewers team on the > Puppet for OpenStack project. > > I lack dedicated time to contribute on my spare time to the project. And I > don't work anymore on

Re: [openstack-dev] [Magnum]Cache docker images

If they have a valid CA signed cert for the docker registry, it should 'Just work (TM)' :) Self signing is a different issue. Maybe just an additional option in addition to the prefix option to pass a CA to add to the root trust chain? Thanks, Kevin From:

Re: [openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

On Tue, Apr 19, 2016, at 10:25 AM, Doug Hellmann wrote: > Excerpts from Jeremy Stanley's message of 2016-04-19 15:41:26 +: > > On 2016-04-19 09:22:57 -0400 (-0400), Doug Hellmann wrote: > > > Excerpts from Ian Wienand's message of 2016-04-19 12:11:35 +1000: > > [...] > > > > I don't expect the

Re: [openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

On 04/20/2016 03:25 AM, Doug Hellmann wrote: It's not just about control, it's also about communication. One of the most frequent refrains we hear is "what is OpenStack", and one way we're trying to answer that is to publicize all of the things we release through releases.openstack.org. So for

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Tuesday, April 19, 2016 8:10 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [devstack] openstack client slowness / > client-as-a-service > > On 04/19/2016 02:17 PM, Monty Taylor wrote: >

Re: [openstack-dev] [nova] [neutron] the nova network facade that isn't

On Tue, 19 Apr 2016 10:02:46 -0400, Sean Dague wrote: Right, I think in the Havana timeframe, things were very different. Part of the rationale for full parity was that applications would be written against nova-network, and smoothly transition to neutron. But with over 90% neutron, assuming

Re: [openstack-dev] [Fuel] snapshot tool

Hello, I've got a couple of questions: - What about this tool using non-root accounts to connect to OpenStack nodes? Currently, it seems to assume that it always is going to use "root" for SSH. - Shouldn't it sanitize all sensitive information (user names, host names, passwords, tokens, keys

Re: [openstack-dev] [nova] [neutron] the nova network facade that isn't

On 4/19/2016 5:56 PM, Armando M. wrote: On 19 April 2016 at 07:02, Sean Dague > wrote: On 04/18/2016 04:48 PM, Matt Riedemann wrote: > > I guess at a high level my thinking was always, if nova-network isn't > deprecated, and these

[openstack-dev] [kolla] let the liberty backport begin

Hey folks, Thanks to the release team and infrastructure team, we have a stable/liberty branch that is equivalent as of this afternoon to each other. Michal is free to submit his backport patch to stable/liberty now. In the process I was required to abandon all changes against stable/liberty.

Re: [openstack-dev] [tosca-parser] [heat-translator] Collaboration with [Tacker] project at the Austin Summit

Hi Sahdev, Could parser team also be part of the joint session ? On Tue, Apr 19, 2016 at 9:55 PM, Sahdev P Zala wrote: > Hi Team, > > We will be having a collaborative session with Tacker project at the > summit. The following Tacker working session will be focused on it, >

Re: [openstack-dev] [Neutron] meeting topics for 4/21/2016 networking-sfc project IRC meeting

Hi John, Thanks for the note. Great that you already have a skeleton OVN driver for networking-sfc. The next step is to contribute to the detail driver specification and then work out the edges and details on the coding side as well as unit test and integration test (still a lot of work down

Re: [openstack-dev] [tripleo][heat] Summit session clashes

On Wed, Apr 20, 2016 at 3:26 AM, Zane Bitter wrote: > Umm, I thought that was the idea. > > I need to be at both of those Heat ones anyway, so this doesn't really help > me. I'd rather have the DLM session in this slot instead. (The only sessions > I can really skip are the

Re: [openstack-dev] [keystone] Problem with WSGI on keystone

On Tue, Apr 19, 2016 at 11:57 AM, Rosensweig, Elisha (Nokia - IL) < elisha.rosensw...@nokia.com> wrote: > Hi All, > > Recently, I've been having trouble running stack.sh from scratch. With the > default configuration I've been using for a while, I get the following > error in

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 20/04/16 06:17, Monty Taylor wrote: On 04/19/2016 10:16 AM, Daniel P. Berrange wrote: On Tue, Apr 19, 2016 at 09:57:56AM -0500, Dean Troyer wrote: On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: I wonder how much of that is Token caching. In a typical CLI use

Re: [openstack-dev] [Swift] Erasure coding and geo replication

Hi, Has the release of 2.7 significantly changed the assessment here? Thanks Mark On 15/02/16 23:29, Kota TSUYUZAKI wrote: Hello Mark, AFAIK, a few reasons for that we still are in working progress for erasure code + geo replication. and expect to survive a region outage... With that I

[openstack-dev] [keystone] Keystone commands

Hi all, I have installed openstack mitaka, when I execute any keystone's commands with the result displayed below: But I execute `openstack role list`, the result is succeed. [root@devstack scripts]# keystone --debug role-list /usr/lib/python2.7/site-packages/keystoneclient/shell.py:64:

Re: [openstack-dev] [ironic] upgrade support between which versions of ironic?

I agree this is reasonable to support all these cases in “cold upgrades” but in supports-rolling-upgrade (live upgrade in another word) case it is different and complicated and not necessary, During rolling upgrade, we will have old/new services co-existed, and we need to make services

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

Sure… I can clarify with a few additional thoughts: .1) I wouldn’t recommend that it be required for the operator to offer this API. Representing a view of both providing managed services for private cloud customer-on-premise installations of upstream OpenStack and as a business owner with

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

On 04/19/2016 11:03 PM, Dean Troyer wrote: On Tue, Apr 19, 2016 at 8:17 PM, Adam Young > wrote: Maybe it is time to revamp Devstack. Is there some way that, without a major rewrite, it could take better advantage of the CLI? Could we

[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: openstack-dev] [vitrage] vitrage alarms list

Hi, Thanks for your response. There is no error about the request of alarms list in vitrage-graph log. Here is the vitrage-api log about the alarms error. Thank you for your help~ :) 2016-04-20 09:45:34.599585 2016-04-20 09:45:34.599 3700 DEBUG vitrage.service [-] static_physical.transformer

  1   2   >