Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Fox, Kevin M
https://blueprints.launchpad.net/nova/+spec/instance-users Please see the above spec. Nova, Keystone and Barbican have been working together on it this cycle and are hoping to implement it in Mitaka The problem of secrets from the secret store is not isolated to just Magnum. Thanks, Kevin

Re: [openstack-dev] [nova][ceilometer] cputime value resets on restart/shutdown

2015-09-01 Thread gord chung
On 01/09/2015 12:10 PM, Julien Danjou wrote: On Tue, Sep 01 2015, gord chung wrote: but if it's not actually cumulative in Ceilometer (pre-storage), should we really be tagging it as such? We only have 3 meters type, and the cumulative definition I wrote somewhere back in 2012 states that

Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Adrian Otto
John and Robert, On Sep 1, 2015, at 10:03 AM, John Dennis > wrote: On 09/01/2015 10:57 AM, Clark, Robert Graham wrote: The reason that is compelling is that you can have Barbican generate, sign, and store a keypair without transmitting the private

Re: [openstack-dev] [trove] [heat] Multi region support

2015-09-01 Thread Zane Bitter
On 01/09/15 11:41, Lowery, Mathew wrote: This is a Trove question but including Heat as they seem to have solved this problem. Summary: Today, it seems that Trove is not capable of creating a cluster spanning multiple regions. Is that the case and, if so, are there any plans to work on that?

[openstack-dev] [trove] Anyone using containers?

2015-09-01 Thread Lowery, Mathew
Just curious if anyone is using containers in their deployments. If so, in what capacity? What are the advantages, gotchas, and pain points? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

2015-09-01 Thread gord chung
On 28/08/2015 5:18 PM, Alec Hothan (ahothan) wrote: On 8/28/15, 11:39 AM, "gord chung" wrote: i should start by saying i re-read my subject line and it arguably comes off aggressive -- i should probably have dropped 'explain' :) On 28/08/15 01:47 PM, Alec Hothan (ahothan)

Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Douglas Mendizábal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Added a few comments inline. - - Douglas Mendizábal On 9/1/15 12:03 PM, John Dennis wrote: > On 09/01/2015 10:57 AM, Clark, Robert Graham wrote: >> >>> The reason that is compelling is that you can have Barbican >>> generate, sign, and store a

Re: [openstack-dev] [puppet][keystone] Keystone resource naming with domain support - no '::domain' if 'Default'

2015-09-01 Thread Rich Megginson
To close this thread: http://lists.openstack.org/pipermail/openstack-dev/2015-August/072878.html puppet-openstack will support Keystone domain scoped resource names without a '::domain' in the name, only if the 'default_domain_id' parameter in Keystone has _not_ been set. That is, if the

Re: [openstack-dev] [Heat] convergence rally test results (so far)

2015-09-01 Thread Clint Byrum
Excerpts from Anant Patil's message of 2015-08-30 23:01:29 -0700: > Hi Angus, > > Thanks for doing the tests with convergence. We are now assured that > convergence has not impacted the performance in a negative way. Given > that, in convergence, a stack provisioning process goes through a lot of

Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread John Dennis
On 09/01/2015 10:57 AM, Clark, Robert Graham wrote: The reason that is compelling is that you can have Barbican generate, sign, and store a keypair without transmitting the private key over the network to the client that originates the signing request. It can be directly stored, and made

[openstack-dev] [all] Criteria for applying vulnerability:managed tag

2015-09-01 Thread Jeremy Stanley
Bringing OpenStack vulnerability management processes to the Big Top started a couple months ago with creation of a deliverable tag called vulnerability:managed, the definition of which can be found at: http://governance.openstack.org/reference/tags/vulnerability_managed.html Its initial

Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Tim Bell
> -Original Message- > From: Adrian Otto [mailto:adrian.o...@rackspace.com] > Sent: 01 September 2015 07:03 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [magnum] Difference between certs stored in >

[openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Vikas Choudhary
Is it like keystone authenticating between magnum-client and magnum conductor, and barbican certs will be used b/w conductor and k8s/swarm? Thanks Vikas Choudhary _ Simply put, Keystone is designed to generate tokens that are to be

Re: [openstack-dev] [puppet] [security] applying for vulnerability:managed tag

2015-09-01 Thread Thierry Carrez
Emilien Macchi wrote: > I would like the feedback from the community about applying (or not) to > the vulnerability:managed tag [1]. > Being part of OpenStack ecosystem and the big tent, Puppet OpenStack > project might want to follow some other projects in order to be > consistent in Security

[openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Vikas Choudhary
Thanks Adrian for description. If i could understand correctly,magnum clients will be use barbican for authentication as coes dont support keystone for operations like pod-creation etc and for rest of the project clients like nova/glance pythonclients, keystone will continue to serve. Please

Re: [openstack-dev] [murano] Proposing Nikolai Starodubtsev for core

2015-09-01 Thread Dmitro Dovbii
+1 2015-09-01 2:24 GMT+03:00 Serg Melikyan : > +1 > > On Mon, Aug 31, 2015 at 3:45 PM, Kirill Zaitsev > wrote: > >> I’m pleased to nominate Nikolai for Murano core. >> >> He’s been actively participating in development of murano during liberty >>

[openstack-dev] [murano] Let's minimaze the list of pylint exceptions

2015-09-01 Thread Dmitro Dovbii
Hi folks! We have a long list of pylint exceptions in code of Murano (please see example ). I would like to propose you to take a part in refactoring of code and minimization of this list. I've created blueprint

Re: [openstack-dev] [murano] Let's minimaze the list of pylint exceptions

2015-09-01 Thread Nikolay Starodubtsev
+1, good initiative Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2015-09-01 10:30 GMT+03:00 Dmitro Dovbii : > Hi folks! > > We have a long list of pylint exceptions in code of Murano (please see > example >

Re: [openstack-dev] [Neutron] Netaddr 0.7.16 and gate breakage

2015-09-01 Thread Sachi King
On Tue, Sep 1, 2015 at 3:15 AM, Carl Baldwin wrote: > On Mon, Aug 31, 2015 at 11:02 AM, Armando M. wrote: >> On 31 August 2015 at 09:53, Jeremy Stanley wrote: >>> On 2015-08-31 10:33:07 -0600 (-0600), Carl Baldwin wrote: >>> > I was

Re: [openstack-dev] [neutron] subnetallocation is in core resource, while there is a extension for it?

2015-09-01 Thread Tidwell, Ryan
This was a compromise we made toward the end of Kilo. The subnetpools resource was implemented as a core resource, but for purposes of Horizon interaction and a lack of another method for evolving the Neutron API we deliberately added a shim extension. I believe this was done with a couple

Re: [openstack-dev] [Heat] convergence rally test results (so far)

2015-09-01 Thread Fox, Kevin M
You can default it to the number of cores, but please make it configurable. Some ops cram lots of services onto one node, and one service doesn't get to monopolize all cores. Thanks, Kevin From: Angus Salkeld [asalk...@mirantis.com] Sent: Tuesday, September 01,

Re: [openstack-dev] [api][keystone][openstackclient] Standards for object name attributes and filtering

2015-09-01 Thread Dolph Mathews
Does anyone have an example of an API outside of OpenStack that would return 400 in this situation (arbitrary query string parameters)? Based on my past experience, I'd expect them to be ignored, but I can't think of a reason why a 400 would be a bad idea (but I suspect there's some prior art /

Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Clark, Robert Graham
I’ve requested several Security Project slots on the summit timetable, I’d be happy to dedicate a fishbowl session to this on the security track. -Rob On 01/09/2015 14:31, "Fox, Kevin M" wrote: >Awesome. Thanks. :) > >Are there any plans for the summit yet? I think we

Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Fox, Kevin M
Nice. Thank you. Kevin From: Clark, Robert Graham [robert.cl...@hp.com] Sent: Tuesday, September 01, 2015 3:16 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Difference between certs stored in

Re: [openstack-dev] [trove] [heat] Multi region support

2015-09-01 Thread Angus Salkeld
On Wed, Sep 2, 2015 at 8:30 AM Lowery, Mathew wrote: > Thank you Zane for the clarifications! > > I misunderstood #2 and that led to the other misunderstandings. > > Further questions: > * Are nested stacks aware of their nested-ness? In other words, given any > nested stack

[openstack-dev] [oslo.messaging]

2015-09-01 Thread Nader Lahouti
Hi, I am considering to use oslo.messaging to read messages from a rabbit queue. The messages are put into the queue by an external process. In order to do that I need to specify routing_key in addition to other parameters (i.e. exchange and queue,... name) for accessing the queue. I was looking

Re: [openstack-dev] [Heat] convergence rally test results (so far)

2015-09-01 Thread Angus Salkeld
On Tue, Sep 1, 2015 at 10:45 PM Steven Hardy wrote: > On Fri, Aug 28, 2015 at 01:35:52AM +, Angus Salkeld wrote: > >Hi > >I have been running some rally tests against convergence and our > existing > >implementation to compare. > >So far I have done the

[openstack-dev] correction: Re: [puppet][keystone] Keystone resource naming with domain support - no '::domain' if 'Default'

2015-09-01 Thread Rich Megginson
Slight correction below: On 09/01/2015 10:56 AM, Rich Megginson wrote: To close this thread: http://lists.openstack.org/pipermail/openstack-dev/2015-August/072878.html puppet-openstack will support Keystone domain scoped resource names without a '::domain' in the name, only if the

Re: [openstack-dev] [horizon] URL Sanity

2015-09-01 Thread Richard Jones
Interesting idea, and in general I'm for consistency. I can't speak directly to the network/port question, though it seems to me that if ports must be attached to networks then it makes sense for the URL to reflect that. On the other hand, some could argue that the django URL routing is ...

Re: [openstack-dev] [Fuel] Code review process in Fuel and related issues

2015-09-01 Thread Tomasz Napierala
> On 01 Sep 2015, at 03:43, Igor Kalnitsky wrote: > > Hi folks, > > So basically.. > > * core reviewers won't be feature leads anymore > * core reviewers won't be assigned to features (or at least not full-time) > * core reviewers will spend time doing review and

Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Clark, Robert Graham
On 01/09/2015 11:38, "Douglas Mendizábal" wrote: This turned into exactly what I was trying to avoid, I probably shouldn’t have mentioned Anchor, but as I started us down this road (where really I was just expressing some concerns over certificate lifecycle)

Re: [openstack-dev] [Ironic] Command structure for OSC plugin

2015-09-01 Thread Dean Troyer
[late catch-up] On Mon, Aug 24, 2015 at 2:56 PM, Doug Hellmann wrote: > Excerpts from Brad P. Crochet's message of 2015-08-24 15:35:59 -0400: > > On 24/08/15 18:19 +, Tim Bell wrote: > > > > > >From a user perspective, where bare metal and VMs are just different >

Re: [openstack-dev] [Murano] Documentation on how to Start Contributing

2015-09-01 Thread Vahid S Hashemian
Hi Jeremy, Thanks for sharing these tips. What is your advice on debugging a PyPi package? I'm modifying the code for python-muranoclient and would like to be able to debug using eclipse (in which I'm coding) or any other convenient means. Regards, --Vahid

Re: [openstack-dev] [Blazar] Anyone interested?

2015-09-01 Thread Ildikó Váncsa
Hi, I'm glad to see the interest and I also support the idea of using the IRC channel that is already set up for further communication. Should we aim for a meeting/discussion there around the end of this week or during next week? @Nikolay, Sylvain: Thanks for support and bringing together a

Re: [openstack-dev] [Nova] Placing VMs based on multiple criteria

2015-09-01 Thread Sourabh Patwardhan
Hi Sundar, Have you considered writing your own custom filter for hosts as described in [1] ? Thanks, Sourabh [1] http://docs.openstack.org/developer/nova/devref/filter_scheduler.html On Mon, Aug 31, 2015 at 9:58 AM, Sundar Nadathur wrote: > Hi all, > > I’d

Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Clark, Robert Graham
Extremely interesting. This is something that we are looking at during the Security mid-cycle (happening this week) see "Secure communications between control plane and tenant plane” under https://etherpad.openstack.org/p/security-liberty-midcycle This is problem for a lot of different projects,

Re: [openstack-dev] [Tacker][NFV] Heads up: switch over to master

2015-09-01 Thread Sridhar Ramaswamy
The switch over to master is now complete. Please follow the updated (and a bit easier) Installation steps here, https://wiki.openstack.org/wiki/Tacker/Installation On Mon, Aug 31, 2015 at 1:32 PM, Sridhar Ramaswamy wrote: > Tacker dev & user teams: > > This shouldn't be a

Re: [openstack-dev] [Blazar] Anyone interested?

2015-09-01 Thread Shamail
Hi everyone, Is the information on the wiki still up to date? https://wiki.openstack.org/wiki/Blazar I have copied the Product WG mailing list as well since one of the user stories[1] being discussed in that forum has to do with capacity management and resource reservation. [1]

Re: [openstack-dev] [Blazar] Anyone interested?

2015-09-01 Thread Sylvain Bauza
Le 01/09/2015 22:31, Ildikó Váncsa a écrit : Hi, I'm glad to see the interest and I also support the idea of using the IRC channel that is already set up for further communication. Should we aim for a meeting/discussion there around the end of this week or during next week? @Nikolay,

Re: [openstack-dev] [trove] [heat] Multi region support

2015-09-01 Thread Lowery, Mathew
Thank you Zane for the clarifications! I misunderstood #2 and that led to the other misunderstandings. Further questions: * Are nested stacks aware of their nested-ness? In other words, given any nested stack (colocated with parent stack or not), can I trace it back to the parent stack? (On a

Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Fox, Kevin M
Awesome. Thanks. :) Are there any plans for the summit yet? I think we should all get together and talk about it. Thanks, Kevin From: Clark, Robert Graham [robert.cl...@hp.com] Sent: Tuesday, September 01, 2015 1:35 PM To: OpenStack Development Mailing

Re: [openstack-dev] [murano] Proposing Nikolai Starodubtsev for core

2015-09-01 Thread Ekaterina Chernova
+1 On Tue, Sep 1, 2015 at 10:03 AM, Dmitro Dovbii wrote: > +1 > > 2015-09-01 2:24 GMT+03:00 Serg Melikyan : > >> +1 >> >> On Mon, Aug 31, 2015 at 3:45 PM, Kirill Zaitsev >> wrote: >> >>> I’m pleased to nominate Nikolai for

[openstack-dev] Re keystone to keystone federation

2015-09-01 Thread sreeja kannagundla
Hi I am working on keystone2keystone federatoin and using kilo version for both keystone-sp and keystone idp After configuring keystone-sp and keystone-idp I am trying to use the command : openstack federation project list -os-auth-type v3unscopedsaml --os-identity-provider k2k --os-auth-url

Re: [openstack-dev] [nova] ProviderFirewallRules still available?

2015-09-01 Thread Hans Lindgren
Some drivers (libvirt, xen) still query the database and try to set up provider rules. However, there is no api for this feature as the mail thread you link points out and therefore no way to add/remove any rules. Due to this the setup of provider rules that is done today will effectively do

Re: [openstack-dev] [Fuel] Number of IP addresses in a public network

2015-09-01 Thread Igor Kalnitsky
Hello, My 5 cents on it. I don't think it's really a High or Critical bug for 7.0. If there's not enough IPs the CheckBeforeDeploymentTask will fail. And that's actually Ok, it may fail by different reason without starting actual deployment (sending message to Astute). But I agree it's kinda

Re: [openstack-dev] [Blazar] Anyone interested?

2015-09-01 Thread Sylvain Bauza
Le 01/09/2015 06:52, Nikolay Starodubtsev a écrit : All, I'd like to propose use of #openstack-blazar for further communication and coordination. +2 to that. That's the first step of any communication. The channel logs are also recorded here, for async communication :

Re: [openstack-dev] [Blazar] Anyone interested?

2015-09-01 Thread Nikolay Starodubtsev
Sylvain, First of all we need to reanimate blazar gate-jobs, or we can't merge anything. I tried to do it a year ago, but can't get the point of the tests, so better decision can be to rewrite them from scratch. Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1

Re: [openstack-dev] Intel PCI CI down today due to testing scripts bug

2015-09-01 Thread Anita Kuno
On 08/31/2015 10:29 PM, He, Yongli wrote: > Hello OpenStackers! > > The Intel PCI CI, due to test scripts bug( recently added) is failing to > report results to OpenStack Jenkins third-party tests. > > We had identify this bug and the scripts had rolled back to verified version. > Now we are

[openstack-dev] [third-party][CI] Third-party oses in devstack-gate

2015-09-01 Thread Evgeny Antyshev
Hello! This letter I address to those third-party CI maintainers who needs to amend the upstream devstack-gate to satisfy their environment. Some folks that I know use inline patching at job level, some make private forks of devstack-gate (I even saw one on github). There have been a few

[openstack-dev] [nova][vmware] compute log files are flooded with unnecessary data

2015-09-01 Thread Gary Kotton
Hi, The commit https://github.com/openstack/nova/commit/bcc002809894f39c84dca5c46034468ed0469c2b results in a ton of data in log files. An example is that a tempest runs is about 80G of data in the nova compute log file. This makes debugging issues terribly difficult. I have proposed a revert

Re: [openstack-dev] [neutron][db] reviewers: please mind the branch a script belongs to

2015-09-01 Thread Miguel Angel Ajo
Good reminder, I believe automation will help us most of the time. But we need to have a good eye on contract/expand branches, Ihar Hrachyshka wrote: Hi reviewers, several days ago, a semantically expand-only migration script was merged into contract branch [1]. This is not a disaster,

Re: [openstack-dev] [nova][bugs] more specific tags?

2015-09-01 Thread Markus Zoeller
Matt Riedemann wrote on 08/31/2015 10:16:23 PM: > From: Matt Riedemann > To: openstack-dev@lists.openstack.org > Date: 08/31/2015 10:21 PM > Subject: Re: [openstack-dev] [nova][bugs] more specific tags? > > > > On 8/28/2015 10:37 AM,

Re: [openstack-dev] [murano] Proposing Nikolai Starodubtsev for core

2015-09-01 Thread GERSHENZON, Michal (Michal)
+1 From: Dmitro Dovbii [mailto:ddov...@mirantis.com] Sent: Tuesday, September 01, 2015 10:03 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [murano] Proposing Nikolai Starodubtsev for core +1 2015-09-01 2:24 GMT+03:00 Serg Melikyan

[openstack-dev] [neutron][db] reviewers: please mind the branch a script belongs to

2015-09-01 Thread Ihar Hrachyshka
Hi reviewers, several days ago, a semantically expand-only migration script was merged into contract branch [1]. This is not a disaster, though it would be a tiny one if a contract-only migration script would be merged into expand branch. Please make sure you know the new migration strategy

Re: [openstack-dev] [nova] periodic task

2015-09-01 Thread Gary Kotton
On 8/31/15, 9:22 PM, "Matt Riedemann" wrote: > > >On 8/27/2015 1:22 AM, Gary Kotton wrote: >> >> >> On 8/25/15, 2:43 PM, "Andrew Laski" wrote: >> >>> On 08/25/15 at 06:08pm, Gary Kotton wrote: On 8/25/15, 9:10 AM, "Matt

Re: [openstack-dev] [api] [wsme] [ceilometer] Replacing WSME with _____ ?

2015-09-01 Thread Chris Dent
On Fri, 28 Aug 2015, Chris Dent wrote: The problem with the spec is that it doesn't know what to replace WSME with. Thanks to everyone who provided some input. The summary is: A lot of support for Flask. A fair bit of support for the idea of using JSONSchema and publishing it. Since this

Re: [openstack-dev] [ironic] 100% failure in pxe_ssh job

2015-09-01 Thread Lucas Alvares Gomes
Hi, > The current failure rate for the ironic pxe_ssh job is 100% - >

[openstack-dev] Debug tool for neutron

2015-09-01 Thread bharath thiruveedula
Hi, We have some troubleshooting guides for openstack neutron. But many people who are new to neutron find it difficult to follow the guides, as they are not aware of what is happening behind the scenes. So is there any tool which tracks the packet flow from the VM to debug issues like why the

Re: [openstack-dev] [ironic] 100% failure in pxe_ssh job

2015-09-01 Thread Sergey Nikitin
Maybe problem in ubuntu hash sums. I tried to compare hash sums of images from here http://cloud-images.ubuntu.com/trusty/current/ but image names in file with sums SHA256SUMS differ from actual images names. pxe_ssh job failing with + grep trusty-server-cloudimg-amd64-root.tar.gz

Re: [openstack-dev] [murano] Proposing Nikolai Starodubtsev for core

2015-09-01 Thread Victor Ryzhenkin
+1 from me ;) --  Victor Ryzhenkin Junior QA Engeneer freerunner on #freenode Включено 1 сентября 2015 г. в 12:18:19, Ekaterina Chernova (efedor...@mirantis.com) написал: +1 On Tue, Sep 1, 2015 at 10:03 AM, Dmitro Dovbii wrote: +1 2015-09-01 2:24 GMT+03:00 Serg

Re: [openstack-dev] [murano] Proposing Nikolai Starodubtsev for core

2015-09-01 Thread Alexander Tivelkov
+1. Well deserved. -- Regards, Alexander Tivelkov On Tue, Sep 1, 2015 at 2:47 PM, Victor Ryzhenkin wrote: > +1 from me ;) > > -- > Victor Ryzhenkin > Junior QA Engeneer > freerunner on #freenode > > Включено 1 сентября 2015 г. в 12:18:19, Ekaterina Chernova ( >

[openstack-dev] [ironic] 100% failure in pxe_ssh job

2015-09-01 Thread Sean Dague
The current failure rate for the ironic pxe_ssh job is 100% -

Re: [openstack-dev] FW: [cinder] Microsoft CI Still Disabled

2015-09-01 Thread Duncan Thomas
Mike is on vacation at the moment, somebody else will evaluate in his stead as reply here shortly On 1 September 2015 at 14:20, Octavian Ciuhandu < ociuha...@cloudbasesolutions.com> wrote: > Hi Mike, > > I think the first mail was sent only on openstack-dev. We have had already > over > a week

Re: [openstack-dev] FW: [cinder] Microsoft CI Still Disabled

2015-09-01 Thread Duncan Thomas
Mike is on vacation at the moment, somebody else will evaluate in his stead Hi Mike, I think the first mail was sent only on openstack-dev. We have had already over a week of reliable results on the Microsoft Cinder CI on all three jobs, we have an updated set of results available at [1]. Please

Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread John Dennis
On 09/01/2015 02:49 AM, Tim Bell wrote: Will it also be possible to use a different CA ? In some environments, there is already a corporate certificate authority server. This would ensure compliance with site security standards. A configurable CA was one of the original design goals when the

[openstack-dev] [cinder] L3 low pri review queue starvation

2015-09-01 Thread Tom Barron
[Yesterday while discussing the following issue on IRC, jgriffith suggested that I post to the dev list in preparation for a discussion in Wednesday's cinder meeting.] Please take a look at the 10 "Low" priority reviews in the cinder Liberty 3 etherpad that were punted to Mitaka yesterday. [1]

Re: [openstack-dev] [Heat] convergence rally test results (so far)

2015-09-01 Thread Steven Hardy
On Fri, Aug 28, 2015 at 01:35:52AM +, Angus Salkeld wrote: >Hi >I have been running some rally tests against convergence and our existing >implementation to compare. >So far I have done the following: > 1. defined a template with a resource >groupA >

[openstack-dev] [ec2api][puppet] EC2 api puppet module

2015-09-01 Thread Marcos Fermin Lobo
Hi all, The standalone EC2 api project https://github.com/stackforge/ec2-api does not have puppet module yet. I want to develop this puppet module and my idea is start in a public Github repo and get feedback from the community. All feedback and collaborations will be very welcome. I would

Re: [openstack-dev] [Ironic] Command structure for OSC plugin

2015-09-01 Thread Tim Bell
That would be great to have plugins on the commands which are relevant to multiple projects… avoiding exposing all of the underlying projects as prefixes and getting more consistency would be very appreciated by the users. Tim From: Dean Troyer [mailto:dtro...@gmail.com] Sent: 01 September

Re: [openstack-dev] [Heat] convergence rally test results (so far)

2015-09-01 Thread Anant Patil
When the stack fails, it is marked as FAILED and all the sync points that are needed to trigger the next set of resources are deleted. The resources at same level in the graph, like here, they are suppose to timeout or fail for an exception. Many DB hits means that the cache data we were

Re: [openstack-dev] [Heat] convergence rally test results (so far)

2015-09-01 Thread Robert Collins
On 2 September 2015 at 11:53, Angus Salkeld wrote: > 1. limit the number of resource actions in parallel (maybe base on the > number of cores) I'm having trouble mapping that back to 'and heat-engine is running on 3 separate servers'. -Rob -- Robert Collins

Re: [openstack-dev] [mistral] Displaying wf hierarchy in CLI

2015-09-01 Thread Lingxian Kong
Hi, Renat, Actually, I have the same idea months ago, but what I thought is to provide task dependencies information in a workflow definition, since as a workflow designer, I have no idea about how my workflow 'looks like', unless I create an execution with that, especially when there are a lot

Re: [openstack-dev] [ec2api][puppet] EC2 api puppet module

2015-09-01 Thread Alex Schultz
Hey Marcos, On Tue, Sep 1, 2015 at 7:50 AM, Marcos Fermin Lobo < marcos.fermin.l...@cern.ch> wrote: > Hi all, > > The standalone EC2 api project https://github.com/stackforge/ec2-api does > not have puppet module yet. I want to develop this puppet module and my > idea is start in a public Github

[openstack-dev] [horizon] URL Sanity

2015-09-01 Thread Rob Cresswell (rcresswe)
Hi all, I recently started looking into properly implementing breadcrumbs to make navigation clearer, especially around nested resources (Subnets Detail page, for example). The idea is to use the request.path to form a logical breadcrumb that isn’t dependent on browser history (

Re: [openstack-dev] [ec2api][puppet] EC2 api puppet module

2015-09-01 Thread Emilien Macchi
On 09/01/2015 08:50 AM, Marcos Fermin Lobo wrote: > Hi all, > > The standalone EC2 api project https://github.com/stackforge/ec2-api > does not have puppet module yet. I want to develop this puppet module > and my idea is start in a public Github repo and get feedback from the > community. All

Re: [openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

2015-09-01 Thread Clark, Robert Graham
>The reason that is compelling is that you can have Barbican generate, >sign, and store a keypair without transmitting the private key over the >network to the client that originates the signing request. It can be >directly stored, and made available only to the clients that need access >to it.

[openstack-dev] [nova][vmware][qa] vmware nsx CI appears gone

2015-09-01 Thread Matt Riedemann
I haven't seen the vmware nsx CI reporting on anything in awhile but don't see any outage events here: https://wiki.openstack.org/wiki/NovaVMware/Minesweeper/Status Is there some status? -- Thanks, Matt Riedemann __

Re: [openstack-dev] [ironic] 100% failure in pxe_ssh job

2015-09-01 Thread Jim Rollenhagen
On Tue, Sep 01, 2015 at 07:17:56AM -0400, Sean Dague wrote: > The current failure rate for the ironic pxe_ssh job is 100% - >

Re: [openstack-dev] [ironic] 100% failure in pxe_ssh job

2015-09-01 Thread Julia Kreger
On Tue, Sep 1, 2015 at 9:17 AM, Jim Rollenhagen wrote: > > > > On Sep 1, 2015, at 04:32, Lucas Alvares Gomes > wrote: > > > > Hi, > > > >> The current failure rate for the ironic pxe_ssh job is 100% - > >> >

Re: [openstack-dev] FW: [cinder] Microsoft CI Still Disabled

2015-09-01 Thread Octavian Ciuhandu
Thank you for your help on this, Octavian. From: Duncan Thomas Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, 1 September 2015 14:48 To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] FW: [cinder] Microsoft CI

Re: [openstack-dev] [ironic] 100% failure in pxe_ssh job

2015-09-01 Thread Jim Rollenhagen
> On Sep 1, 2015, at 04:32, Lucas Alvares Gomes wrote: > > Hi, > >> The current failure rate for the ironic pxe_ssh job is 100% - >>

Re: [openstack-dev] [ironic] 100% failure in pxe_ssh job

2015-09-01 Thread Sean Dague
On 09/01/2015 09:21 AM, Julia Kreger wrote: > > On Tue, Sep 1, 2015 at 9:17 AM, Jim Rollenhagen > wrote: > > Why don't we just use the pre-built agent ramdisks we already > publish? AFAIK we already have a job for it, just need

Re: [openstack-dev] [ironic] 100% failure in pxe_ssh job

2015-09-01 Thread Jim Rollenhagen
On Tue, Sep 01, 2015 at 09:21:39AM -0400, Julia Kreger wrote: > On Tue, Sep 1, 2015 at 9:17 AM, Jim Rollenhagen > wrote: > > > > > Why don't we just use the pre-built agent ramdisks we already publish? > > AFAIK we already have a job for it, just need to switch the name

Re: [openstack-dev] Debug tool for neutron

2015-09-01 Thread Jay Pipes
Check out https://github.com/yeasy/easyOVS for OVS-based setups. Best, -jay On 09/01/2015 07:50 AM, bharath thiruveedula wrote: Hi, We have some troubleshooting guides for openstack neutron. But many people who are new to neutron find it difficult to follow the guides, as they are not aware

Re: [openstack-dev] [Fuel] Number of IP addresses in a public network

2015-09-01 Thread Andrey Danin
+1 to Igor. It's definitely not a High bug. The biggest problem I see here is a confusing error message with a wrong number of required IPs. AFAIU we cannot fix it easily now so let's postpone it to 8.0 but change a message itself [0] in 7.0. [0]

Re: [openstack-dev] [Blazar] Anyone interested?

2015-09-01 Thread Nikolay Starodubtsev
Also, if we decided to continue development we should add blazar here [1] according to the email [2] So, my suggestion is to setup some timeframe on this week or next week and hold some kind of meeting. [1]: https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement [2]:

Re: [openstack-dev] [Blazar] Anyone interested?

2015-09-01 Thread Sylvain Bauza
Le 01/09/2015 15:46, Nikolay Starodubtsev a écrit : Also, if we decided to continue development we should add blazar here [1] according to the email [2] So, my suggestion is to setup some timeframe on this week or next week and hold some kind of meeting. [1]:

Re: [openstack-dev] [cinder] L3 low pri review queue starvation

2015-09-01 Thread John Griffith
On Tue, Sep 1, 2015 at 5:57 AM, Tom Barron wrote: > [Yesterday while discussing the following issue on IRC, jgriffith > suggested that I post to the dev list in preparation for a discussion in > Wednesday's cinder meeting.] > > Please take a look at the 10 "Low" priority

[openstack-dev] [Swift] Swift 2.4.0 release

2015-09-01 Thread John Dickinson
I'm pleased to announce that Swift 2.4.0 is available. As always, you can upgrade to this version with no end-user downtime. This release has several very nice features, so I recommend that you upgrade as soon as possible. You can find the release at:

[openstack-dev] [trove] [heat] Multi region support

2015-09-01 Thread Lowery, Mathew
This is a Trove question but including Heat as they seem to have solved this problem. Summary: Today, it seems that Trove is not capable of creating a cluster spanning multiple regions. Is that the case and, if so, are there any plans to work on that? Also, are we aware of any precedent

Re: [openstack-dev] [nova][ceilometer] cputime value resets on restart/shutdown

2015-09-01 Thread gord chung
On 31/08/2015 3:36 PM, Julien Danjou wrote: On Mon, Aug 31 2015, gord chung wrote: i'm not sure Gnocchi is where we should be fixing this as it really only (potentially) fixes it for Gnocchi and not for any of the other ways Ceilometer data can be consumed. The ideal way is to send the data

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

2015-09-01 Thread Emilien Macchi
On 08/31/2015 08:40 AM, Emilien Macchi wrote: > Hello, > > Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC > in #openstack-meeting-4: > > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150901 > > Please add additional ite

Re: [openstack-dev] [nova][ceilometer] cputime value resets on restart/shutdown

2015-09-01 Thread Julien Danjou
On Tue, Sep 01 2015, gord chung wrote: > but if it's not actually cumulative in Ceilometer (pre-storage), should we > really be tagging it as such? We only have 3 meters type, and the cumulative definition I wrote somewhere back in 2012 states that it can reset to 0. Sorry. :-) > so i was

[openstack-dev] FW: [cinder] Microsoft CI Still Disabled

2015-09-01 Thread Octavian Ciuhandu
Hi Mike, I think the first mail was sent only on openstack-dev. We have had already over a week of reliable results on the Microsoft Cinder CI on all three jobs, we have an updated set of results available at [1]. Please re-evaluate the activity of our CI and re-enable the gerrit account.