Re: [openstack-dev] [oslo][oslo.versionedobjects] Is it possible to make changes to oslo repos?

> On Jan 28, 2016, at 5:01 PM, Dan Smith wrote: > >> I know we have some projects (heat, I think?) that don't have UUIDs at >> all. Are they using oslo.versionedobjects? I suppose we could move them >> to a string field instead of a UUID field, instead of flipping the >>

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

Excerpts from Davanum Srinivas (dims)'s message of 2016-01-29 06:17:39 -0600: > Matt, > > yes, that's a concern for sure. We work closely with all the new Oslo > cores to defer to experts first and learn. This goes into the debate > about the right mixture of Generalists and Specialists in the

Re: [openstack-dev] [mistral] Promoting Anastasia Kuznetsova to core reviewers

Folks, I'm not a core reviewer, but if I was, I'd definitely vote with +1. Good job, Anastasia! Keep going! Regards, Igor Marnat On Fri, Jan 29, 2016 at 10:23 AM, Elisha, Moshe (Nokia - IL) < moshe.eli...@nokia.com> wrote: > A very big +1 > > From:

Re: [openstack-dev] [Fuel] Overriding and removing VIPs from plugins

I would not check that. We are not talking about installing browser plugins when users may not know what they want. Putting extra checks will create a more fool-proof but less configurable software. I’d vote for letting users shoot their feet using their plugins but making Fuel more flexible.

Re: [openstack-dev] [ceilometer] :Regarding wild card configuration in pipeline.yaml

I have a meter subscription m1.* for publisher p1 and I need a subset of m1.* notifications for ex:m1.xyz.* for publisher p2. If we add p2 to already exisiting sink along with p1, p2 will get other notification's along with m1.xyz.* which are not needed for p2. To avoid this we had the

Re: [openstack-dev] [bug-smash] Global OpenStack Bug Smash Mitaka

Excerpts from Wang, Shane's message of 2016-01-28 09:11:36 +: > Save the Date: > Global OpenStack Bug Smash > Wednesday-Friday, March 2-4, 2016 > RSVP by Friday, February 19 > > How can you help make the OpenStack Mitaka release stable and bug-free while > having fun with your peers? Join

Re: [openstack-dev] [Fuel] Overriding and removing VIPs from plugins

Roman P. wrote: > Putting extra checks will create a more fool-proof but less configurable > software. I’d vote for letting users shoot their feet using their plugins > but making Fuel more flexible. I won't agree here. You see, what if two plugins wants to override the core network role?

[openstack-dev] [glance] Virtual Mid-Cycle meeting next week

Greetings, As promissed (although I promissed it yday), here's the link to vote for the days you'd like the Glance Virtual Midcycle to happen. We'll be meeting just for 2 days and at maximum for 3 hours. The 2 days with more votes are the ones that will be picked. Since there's such a short

Re: [openstack-dev] [Fuel] Overriding and removing VIPs from plugins

> jsonpatch There were +1's regarding overriding VIPs above. I'd stick with that. It is done for tasks now. But we will need to check conflicts between plugins there (as for tasks). Aleksey Kasatkin On Fri, Jan 29, 2016 at 1:23 PM, Roman Prykhodchenko wrote: > Frankly, I

Re: [openstack-dev] [stable][ceilometer][all] stable/kilo 2015.1.3 delayed

On 28/01/2016 3:37 PM, Jeremy Stanley wrote: > On 2016-01-28 19:40:20 + (+), Dave Walker wrote: > [...] >> However, pip 8 was released around the same time as the tarballs were >> attempted to be generated. Most of the projects are OK with this, but >> ceilometer declares

[openstack-dev] [Fuel] [Fuel UI] UI text guidelines

Good Friday to everyone! This is just to inform you that UI text guidelines are now available in the Contributor Guide: http://docs.openstack.org/contributor-guide/ui-text-guidelines.html This will be interesting for designers and developers, as well as reviewers, who works on OpenStack user

[openstack-dev] [nova][API]what's the purpose of fping in nova API?

In doing some API work on http://developer.openstack.org/api-ref-compute-v2.1.htmlnoticed that fping was [1] and try to ping the instance to check whether it's pingable or not..but this is running on API service host which mostly have no access to instance with private IP?Just curious about it

Re: [openstack-dev] [Fuel] [Fuel UI] UI text guidelines

Olga, That's awesome! This document will help us a lot. Thanks for your work! 2016-01-29 17:01 GMT+03:00 Olga Gusarenko : > Good Friday to everyone! > > This is just to inform you that UI text guidelines are now available in > the Contributor Guide: > >

Re: [openstack-dev] [Nova][Neutron] Scheduling with routed networks

On 29 January 2016 at 12:16, Jay Pipes wrote: > On 01/28/2016 09:15 PM, Carl Baldwin wrote: > >> Hi Nova and Neutron, >> >> It was a pleasure to attend the Nova mid-cycle in Bristol this week. >> > > Indeed, I thought the mid-cycle was super-productive. Yup, I always

Re: [openstack-dev] Any chances to backport port_security_enabled support into Heat for Kilo 2015.1.3?

Oh, that's okay... Thanks guys!:) On 29 January 2016 at 06:39, Sergey Kraynev wrote: > Sean, thank you for the spotting. > > Martinx, According to the information mentioned by Sean, we unfortunately > can not do it :( > > On 29 January 2016 at 10:45, Sean M. Collins

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

What motivates me every day and every night, is to provide the most advanced solution for a set a problems to solve, Open Source and in OpenStack. What motivates me is to work with brilliant people like minded, capable of doing great things working together. It is not the competition and It is not

Re: [openstack-dev] [tripleo] use mitaka CI tested repo

On Fri, 2016-01-29 at 08:17 -0500, Emilien Macchi wrote: > Hi, > > I'm wondering why don't we use Mitaka CI tested repository [1]. > IIRC, TripleO is currently using a snapshot which is updated > asynchronously by TripleO CI folks. > The problem is that we're not consistent with what RDO CI is

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

On 29.01.2016 13:35, Vladimir Kuklin wrote: >> We removed role as abstraction from library. It's very very artificial >> abstraction. Instead we use tasks, grouping them to different >> combinations. That allows plugin developers to adjust reference >> architecture to their needs. I only replied

[openstack-dev] [Rally] Failure running rally unit tests

Hi, I am running the rally test https://github.com/openstack/rally/blob/master/tests/unit/test_osclients.py#L87 there is a function "test_create_keystone_client_v2" when i am testing that function i am getting an error i.e:

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

Sergii, Just to clarify: we rely on a role 'limits' attribute [1] to define is role required for deployment ('min' limit presented in the role description) or recommended for deployment ('recommended' limit). Roles without 'min' or 'recommended' limit are considered as optional for basic

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

On 1/28/2016 10:05 PM, Doug Hellmann wrote: I am nominating Alexis Lee (lxsli) for oslo-core. Alexis has been working on adding configuration file reloading to oslo.config this cycle. The work isn't complete, but at this point he probably knows as much or more about the internals of that

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

On 1/29/2016 11:33 AM, Davanum Srinivas wrote: Matt, yes, Nomination is for oslo-core. We would like to expand the core group as well in addition to subject matter experts (example Dmitry Uklhov for Oslo.Messaging core yesterday). The hope and expectation is that Alexis would expand his

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

On 29.01.2016 10:58, Sergii Golovatiuk wrote: > Hi, > > > On Fri, Jan 29, 2016 at 9:55 AM, Julia Aranovich > > wrote: > > Hi folks, > > Our team has started a redesign of node roles panel [1] on Add > Nodes/Edit Roles screens

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

Matt, yes, that's a concern for sure. We work closely with all the new Oslo cores to defer to experts first and learn. This goes into the debate about the right mixture of Generalists and Specialists in the project as well. Thanks, Dims On Fri, Jan 29, 2016 at 5:42 AM, Matt Riedemann

Re: [openstack-dev] [Nova][Neutron] Scheduling with routed networks

On 01/28/2016 09:15 PM, Carl Baldwin wrote: Hi Nova and Neutron, It was a pleasure to attend the Nova mid-cycle in Bristol this week. Indeed, I thought the mid-cycle was super-productive. I think we made a lot of progress. I spent a little time capturing the highlights of what we discussed

[openstack-dev] [tripleo] use mitaka CI tested repo

Hi, I'm wondering why don't we use Mitaka CI tested repository [1]. IIRC, TripleO is currently using a snapshot which is updated asynchronously by TripleO CI folks. The problem is that we're not consistent with what RDO CI is testing. In my memory and tell me if I'm wrong but it happens we're

Re: [openstack-dev] [Fuel] Overriding and removing VIPs from plugins

Frankly, I have not though about how to deal with multiple plugins yet. However, what I think is that we must not restrict this too much and let users configure it more flexibly even if it allows to shoot one’s foot. Perhaps we can add a per-cluster priority for enabled plugins which users can

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

> On 22 Jan 2016, at 20:01, Dan Prince wrote: > > https://github.com/dprince/tripleo-common/tree/mistral Just a couple of cosmetic notes: * this example can be slightly simplified by removing “type: direct” since by default workflows are of “direct” type. * action params

[openstack-dev] [neutron] upgrades/objects code sprint in Brno

Hi neutrinos, as per latest Neutron upgrades subteam discussion, we start to plan for a code sprint to push forward remaining M/early N bits for upgrades story. The main topic of the sprint will be the objectification of the core codebase (ports, networks, subnets…) though other upgrade

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

Bogdan I do no think that this is confusing as we should have actually a place where we tie roles to particular tasks. How do you expect our orchestrator to generate a graph without knowing which tasks to execute on which node? On Fri, Jan 29, 2016 at 2:59 PM, Bogdan Dobrelya

Re: [openstack-dev] [mistral] how to split mistral log files

> On 19 Jan 2016, at 13:05, SHTILMAN, Tomer (Tomer) > wrote: > > Thanks > Not sure that duplicating mistral.conf three times will be the best in this > case , will make things very hard to manage > > > -Original Message- > From: EXT Lingxian Kong

Re: [openstack-dev] [mistral] db deadlock in task execution

Hi, We’re aware that some of that stuff happens once in a while. Please file a ticket, we’ll assign someone to get it investigated. Renat Akhmerov @ Mirantis Inc. > On 27 Jan 2016, at 19:30, Shtilman, Tomer (Nokia - IL) > wrote: > > Hi > We are seeing an error

Re: [openstack-dev] [Rally] Failure running rally unit tests

Hi The problem is definitely in mock - some part of keystoneclient package is actually called (having a real api request) but it should be mocked instead. Unit test expects that keystoneclient.v2_0 is discovered, but we have something else instead. In latest rally version this unit test works

Re: [openstack-dev] [oslo][oslo.versionedobjects] Is it possible to make changes to oslo repos?

On 1/28/2016 11:01 PM, Dan Smith wrote: I know we have some projects (heat, I think?) that don't have UUIDs at all. Are they using oslo.versionedobjects? I suppose we could move them to a string field instead of a UUID field, instead of flipping the enforcement flag on. Alternately, if we add

Re: [openstack-dev] [mistral] Promoting Anastasia Kuznetsova to core reviewers

+1 from me, welcome Anastasia! On Fri, Jan 29, 2016 at 9:00 PM, Igor Marnat wrote: > Folks, > I'm not a core reviewer, but if I was, I'd definitely vote with +1. > > Good job, Anastasia! Keep going! > > Regards, > Igor Marnat > > On Fri, Jan 29, 2016 at 10:23 AM, Elisha,

Re: [openstack-dev] [TripleO] spec-lite process for tripleo

On 27 January 2016 at 16:21, Derek Higgins wrote: > Hi All, > > We briefly discussed feature tracking in this weeks tripleo meeting. I > would like to provide a way for downstream consumers (and ourselves) to > track new features as they get implemented. The main things that

Re: [openstack-dev] [openstack-ansible][designate] : Ansible Designate Role : NoEndpointFound error

Swati, It seems this is a known issue with keystone tool when there are changes to it. Have a look at below links for your problem to resolve temporarily ie., set endpoint for -os-endpoint : http://eavesdrop.openstack.org/irclogs/%23openstack-dns/%23openstack-dns.2015-06-17.log.html

Re: [openstack-dev] Any chances to backport port_security_enabled support into Heat for Kilo 2015.1.3?

Sean, thank you for the spotting. Martinx, According to the information mentioned by Sean, we unfortunately can not do it :( On 29 January 2016 at 10:45, Sean M. Collins wrote: > Kilo is in the "security supported" stage of the lifecycle. So no, > that's not going to get

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

Hi, On Fri, Jan 29, 2016 at 9:55 AM, Julia Aranovich wrote: > Hi folks, > > Our team has started a redesign of node roles panel [1] on Add Nodes/Edit > Roles screens in Fuel UI. > Currently, node roles panel takes a big part of the screen and User have > to scroll down

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

Sergii I disagree with you here a little bit. Role abstraction is a useful thing from high-level standpoint. I would suggest that this list of roles grouping, e.g. which roles are mandatory and which are configured within which group can be specified: 1) in global settings of Nailgun 2)

Re: [openstack-dev] [Horizon] Recent integration tests failures

Can confirm, had the same issue locally, was fixed after a downgrade to selenium 2.48. Good catch! Itxaka On 01/28/2016 10:08 PM, Timur Sufiev wrote: According to the results at https://review.openstack.org/#/c/273697/1 capping Selenium to be not greater than 2.49 fixes broken tests. Patch

[openstack-dev] [Fuel] [Fuel UI] Node role list grouping

Hi folks, Our team has started a redesign of node roles panel [1] on Add Nodes/Edit Roles screens in Fuel UI. Currently, node roles panel takes a big part of the screen and User have to scroll down to node list to check nodes and then scroll up again to check roles. This becomes more actual for

Re: [openstack-dev] [Fuel] Relieving CI/gate jenkins bottleneck

On 28.01.2016 17:48, Alex Schultz wrote: Please let's continue discussion here [0]. [0] http://lists.openstack.org/pipermail/openstack-dev/2016-January/085310.html > On Thu, Jan 28, 2016 at 9:31 AM, Sergii Golovatiuk > wrote: >> Hi, >> >> I disagree with Bogdan. We

[openstack-dev] [Fuel][library] relax downstream policy for puppet modules managed by librarian

This is a continuation of the forked discussion [0]. The idea is to relax Fuel-library downstream policy and implement a "lazy downstreaming", which is to not create a downstream fork of a puppet module referenced in the librarian Puppetfile unless we have to do so. The relaxed policy would

Re: [openstack-dev] [murano] Nominate Victor Ryzhenkin to Murano Core

Congratulations, Victor! Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2016-01-28 17:26 GMT+03:00 Dmytro Dovbii : > Congratulations, Victor! =) > > 2016-01-28 16:20 GMT+02:00 Victor Ryzhenkin : > >> Thank you,

Re: [openstack-dev] [openstack-ansible][designate] : Ansible Designate Role : NoEndpointFound error

Hi Venkata, Thanks for your prompt response. We are using designate 1.5.0 >From the below links, I have added the code from >https://review.openstack.org/#/c/199067/1/designateclient/shell.py as well. Also, in the link --publicurl is mentioned as  http://controller.dmgweb.es:9001/v1 . But,

[openstack-dev] [puppet][ec2api] - Official EC2 puppet module repo

Hi, Since I finished to "apply" for puppet-ec2api module as official puppet module in OpenStack (see https://review.openstack.org/#/c/252959/ and https://review.openstack.org/#/c/251857/), I saw that the puppet module repository is created https://github.com/openstack/puppet-ec2api But the

Re: [openstack-dev] [tripleo] use mitaka CI tested repo

On 01/29/2016 09:40 AM, Dan Prince wrote: > On Fri, 2016-01-29 at 08:17 -0500, Emilien Macchi wrote: >> Hi, >> >> I'm wondering why don't we use Mitaka CI tested repository [1]. >> IIRC, TripleO is currently using a snapshot which is updated >> asynchronously by TripleO CI folks. >> The problem

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

> So, metrics are grouped by the type of resource they use, and each metric has > to be listed. > Grouping isn't a problem, but creating an exhaustive list might be, > since there are 100+ plugins [1] in collectd which can provide > statistics, although not all of these are useful, and some

Re: [openstack-dev] [infra] Gate is broken

Hello, everyone! The broken images have been deleted, and our jenkins slaves should revert back to the previous (good) image. It's safe to submit patches again! Michael On Fri, Jan 29, 2016 at 7:52 AM Paul Michali wrote: > Thanks for hopping on it quickly! > > > > On Fri,

Re: [openstack-dev] [Fuel][Plugins] Tasks ordering between plugins

Hey folks, Simon P. wrote: > 1. Run task X for plugin A (if installed). > 2. Run task Y for plugin B (if installed). > 3. Run task Z for plugin A (if installed). Simon, could you please explain do you need this at the first place? I can imagine this case only if your two plugins are kinda

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

On 29/01/2016 10:48 AM, Foley, Emma L wrote: >> So, metrics are grouped by the type of resource they use, and each metric >> has to be listed. >> Grouping isn't a problem, but creating an exhaustive list might be, >> since there are 100+ plugins [1] in collectd which can provide >> statistics,

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

On 28/01/2016 2:32 AM, Foley, Emma L wrote: > So, metrics are grouped by the type of resource they use, and each metric has > to be listed. > Grouping isn't a problem, but creating an exhaustive list might be, since > there are 100+ plugins [1] in collectd which can provide statistics,

Re: [openstack-dev] [Fuel][library] relax downstream policy for puppet modules managed by librarian

Hi, one of cons: there might be delay in time when we need to apply a patch to upstream project and thus fork some project (needs some time to prepare patch to projects, get reviews and approves, etc). Having said that I vote for "lazy downstreaming". Regards, Alex On Fri, Jan 29, 2016 at 10:12

Re: [openstack-dev] [Fuel][Plugins] Tasks ordering between plugins

On Fri, Jan 29, 2016 at 4:27 PM, Igor Kalnitsky wrote: > Hey folks, > > Simon P. wrote: > > 1. Run task X for plugin A (if installed). > > 2. Run task Y for plugin B (if installed). > > 3. Run task Z for plugin A (if installed). > > Simon, could you please explain do you

[openstack-dev] [infra] Gate is broken

Hey everyone! Since the summit submission deadline is this weekend, we (the infra team) have decided that it's an excellent time to break all of our slaves, so you can go and submit your talks for Austin! That certainly sounds better than "We misconfigured pip.conf and now none of our nodes know

Re: [openstack-dev] [infra] Gate is broken

Thanks for hopping on it quickly! On Fri, Jan 29, 2016 at 10:41 AM Michael Krotscheck wrote: > Hey everyone! > > Since the summit submission deadline is this weekend, we (the infra team) > have decided that it's an excellent time to break all of our slaves, so you > can

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

On 29/01/16 10:08 -0500, Doug Hellmann wrote: Excerpts from Davanum Srinivas (dims)'s message of 2016-01-29 06:17:39 -0600: Matt, yes, that's a concern for sure. We work closely with all the new Oslo cores to defer to experts first and learn. This goes into the debate about the right mixture

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

On Fri, Jan 29 2016, Foley, Emma L wrote: > Supporting statsd would require some more investigation, as collectd's > statsd plugin supports reading stats from the system, but not writing > them. I'm not sure what that means? https://collectd.org/wiki/index.php/Plugin:StatsD seems to indicate it

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

On Fri, Jan 29 2016, Doug Hellmann wrote: > Right. I trust everyone on the team to exercise judgment when > choosing which patches to review, and how to review them. I proposed > Alexis for oslo-core rather than oslo-config-core because his general > approach and collaboration on the config work

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

Le 29 janv. 2016 18:45, "Julien Danjou" a écrit : > > On Fri, Jan 29 2016, Doug Hellmann wrote: > > > Right. I trust everyone on the team to exercise judgment when > > choosing which patches to review, and how to review them. I proposed > > Alexis for oslo-core rather than

Re: [openstack-dev] [Fuel][library] relax downstream policy for puppet modules managed by librarian

On Fri, Jan 29, 2016 at 2:12 AM, Bogdan Dobrelya wrote: > This is a continuation of the forked discussion [0]. > > The idea is to relax Fuel-library downstream policy and implement a > "lazy downstreaming", which is to not create a downstream fork of a > puppet module

Re: [openstack-dev] [openstack-ansible] Helion HLM on GitHub and what next?

Thanks Bailey for the update. I intend to look over more of what you folks have published really soon. Thanks again for putting all of this out there and I hope to work with you and the team soon on more of the convergence pieces. I don't know if you or any of your team are headed to the OPS

[openstack-dev] [Cinder] Nominating Patrick East to Cinder Core

Patrick has been a strong contributor to Cinder over the last few releases, both with great code submissions and useful reviews. He also participates regularly on IRC helping answer questions and providing valuable feedback. I would like to add Patrick to the core reviewers for Cinder. Per our

[openstack-dev] [Neutron][LBaaS][Octavia] Using nova interface extension instead of networks extension

All, In a recent patch [1] Bharath and I proposed to replace the call to the nova os-networks extension with a call to the nova-interface extension. Apparently os-networks is geared towards nova networks and us being neutron I see no reason to continue to support it. I have taken to the ML to

Re: [openstack-dev] [Neutron] OVS flow modification performance

By our testing, ryu openflow has greatly improved the performance, with 500 port vxlan flow table, from 15s to 2.5s, 6 times better. From: IWAMOTO Toshihiro [iwam...@valinux.co.jp] Sent: Monday, January 25, 2016 5:08 PM To: OpenStack Development Mailing

Re: [openstack-dev] [cinder] Testing Cinder upgrades - c-bak upgrade

On 01/20/2016 09:11 PM, Li, Xiaoyan wrote: > @ DuncanT and @dule: > > I noticed from IRC log that you are discussing about c-bak upgrade, and I am > working on this, please see following message. Hope I don't miss anything. > > As you know, currently c-bak and c-vol are in same nodes. c-bak

Re: [openstack-dev] [stable][ceilometer][all] stable/kilo 2015.1.3 delayed

On 2016-01-29 14:14:48 + (+), gordon chung wrote: > trying to understand the situation here. isn't this all managed by > global-reqs? an incompatible pip and pbr were release so now we > can't build? were we the only project using downloadcache (i don't > recall us doing anything unique in

Re: [openstack-dev] [openstack-ansible][designate] : Ansible Designate Role : NoEndpointFound error

Hi Swati, It looks designate_service_setup.yml is not currently included in your role's main play, so the keystone service, user, and endpoint are not

[openstack-dev] [openstack-ansible] Helion HLM on GitHub and what next?

Hi, Those present at some of the Ansible collaboration sessions at Tokyo may recall a mention about Helion Lifecycle Manager (HLM), which constituted a collection of ansible playbooks and particular patterns used by the HPE Helion OS 2.0 release to deploy clouds. We promised at the time that

Re: [openstack-dev] [oslo] nominating Alexis Lee for oslo-core

Julien Danjou wrote: On Fri, Jan 29 2016, Doug Hellmann wrote: Right. I trust everyone on the team to exercise judgment when choosing which patches to review, and how to review them. I proposed Alexis for oslo-core rather than oslo-config-core because his general approach and collaboration on

[openstack-dev] [nova][API] Question about HTTPNotImplementError

In reading some API guide line doc [1] seems we should not return 501 to clientbut nova still doing so at API layer [2], any discussion before about this can be referred ?

Re: [openstack-dev] [puppet][ec2api] - Official EC2 puppet module repo

On 01/29/2016 10:35 AM, Marcos Fermin Lobo wrote: > Hi, > > Since I finished to "apply" for puppet-ec2api module as official puppet > module in OpenStack (see https://review.openstack.org/#/c/252959/ and > https://review.openstack.org/#/c/251857/), I saw that the puppet module > repository is

Re: [openstack-dev] [stable][ceilometer][all] stable/kilo 2015.1.3 delayed

On 29/01/2016 1:27 PM, Jeremy Stanley wrote: > On 2016-01-29 14:14:48 + (+), gordon chung wrote: >> trying to understand the situation here. isn't this all managed by >> global-reqs? an incompatible pip and pbr were release so now we >> can't build? were we the only project using

Re: [openstack-dev] [tripleo] use mitaka CI tested repo

+1 for aligning efforts between Triple-O and RDO Manager around CI. There's been a *lot* of work (trown++) towards RDO Manager CI and it'd be great if Triple O could benefit from that. Like Emilien said, our test coverage for promoting a set of packages to "current-passed-ci" is huge already and

Re: [openstack-dev] [stable][ceilometer][all] stable/kilo 2015.1.3 delayed

On 2016-01-29 18:27:18 + (+), Jeremy Stanley wrote: [...] > Due to unfortunate timing, the last commit on stable/liberty was > tested with pip 7 and merged, but the 2015.1.2 tag for that commit > was pushed after pip 8 was released and so tox was no longer able > to work with the tagged

Re: [openstack-dev] [stable][ceilometer][all] stable/kilo 2015.1.3 delayed

On 2016-01-29 19:34:01 + (+), gordon chung wrote: > hmm.. that's unfortunate... anything we need to update so this doesn't > happen again? or just a matter of lesson learned, let's keep an eye out > next time? Well, I backported the downloadcache removal to the stable/kilo branch after

Re: [openstack-dev] [oslo] nominating Ronald Bradford for oslo-core

I'm not a voting member of the Oslo team, but a BIG +1 >From me. --Rocky -Original Message- From: Joshua Harlow [mailto:harlo...@fastmail.com] Sent: Thursday, January 28, 2016 11:38 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [oslo]