Re: [openstack-dev] Requests + urllib3 + distro packages

> On 14 Oct 2015, at 23:23, Thomas Goirand wrote: > I do understand that you don't like being called this way, though this > is still the reality. Vendorizing still inflicting some major pain to a > lot of your users: > - This thread one of the demonstration of it. > - You

Re: [openstack-dev] [tc][senlin] Request to senlin project to big tent

On 10/15/2015 05:13 AM, Qiming Teng wrote: > Dear TC members, > > Your reviews on the proposal are highly appreciated. > > Subject: Add senlin project to big tent > Link: https://review.openstack.org/#/c/235172/ > > Regards, > Qiming Great. Just as an FYI, it's 3 weeks until the next TC

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

On 10/14/2015 08:22 PM, Ian Wienand wrote: > On 10/14/2015 11:08 AM, Zaro wrote: >> We are soliciting feedback so please let us know what you think. > > Since you asked :) > > Mostly it's just different which is fine. Two things I noticed when > playing around, shown in [1] > > When reviewing,

[openstack-dev] [oslo] Require documenting changes with versionadded and versionchanged

Hi, I propose that changes must now be documented in Oslo libraries. If a change is not documented, it must *not* be approved. IMHO it's very important to document all changes. Otherwise, it becomes really hard to guess if a specific parameter or a specific function can be used just by

Re: [openstack-dev] [all][stable][release] 2015.1.2

2015-10-14 10:59 GMT+02:00 Thierry Carrez : > Sean Dague wrote: >> I think that whoever sets the tag should also push those fixes. We had >> some kilo content bogging down the gate today because of this kind of >> failure. Better to time this as close as possible with the

[openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

hi, i'm looking in fwaas tempest tests and have a question about code location. currently, - fwaas api tests and its rest client are in neutron repo - there are no fwaas scenario tests eventually, - fwaas api tests should be moved into neutron-fwaas repo - fwaaa scenario tests should be in

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

Gilles Dubreuil writes: > On 08/10/15 03:40, Rich Megginson wrote: >> On 10/07/2015 09:08 AM, Sofer Athlan-Guyot wrote: >>> Rich Megginson writes: >>> On 10/06/2015 02:36 PM, Sofer Athlan-Guyot wrote: > Rich Megginson

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

Gilles, 5xx errors like 503 and 502/504 could always be intermittent operational issues. E.g. when you access your keystone backends through some proxy and there is a connectivity issue between the proxy and backends which disappears in 10 seconds, you do not need to rerun the puppet completely -

Re: [openstack-dev] [puppet][ec2api] - First version of puppet module

Hello Marcos, I've look through on your module and it looks cool. Some code issues inline. May be just only one nitpick from my side: can you add link to the documentation in README file? Like it done in puppet-openstack modules. Also thank you for caring of that and keeping in consistent with

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

On Thu, Oct 15, 2015 at 7:25 AM, Takashi Yamamoto wrote: > hi, > > i'm looking in fwaas tempest tests and have a question about code location. > > currently, > > - fwaas api tests and its rest client are in neutron repo > - there are no fwaas scenario tests > > eventually,

[openstack-dev] [Neutron] Neutron Meetup in Tokyo Summit

hi, we are planing to have a social meetup for neutron developers on Thursday evening. anyone who are interested in neutron development are welcome. the place is not fixed yet. we want to estimate how many people want to go. please fill in the following RSVP if you are interested. sooner is

[openstack-dev] [app-catalog] [glance] [murano] Data Assets API for App Catalog

Hi folks, I’ve noticed that the Community Application Catalog has begun to implement its own API, and it seems to me that we are going to have some significant duplication of efforts with the code which has already been implemented in Glance as Artifact Repository initiative (also known as Glance

Re: [openstack-dev] [Keystone] [Horizon] Pagination support for Identity dashboard entities

Hey, As I see, we decided to go the way of limiting and filtering of the list. Bugreport https://bugs.launchpad.net/keystone/+bug/1501698 was opened about this issue. I've coded a chain of patches to fix the bug, please review: https://review.openstack.org/#/c/234849/ On Friday 14 August 2015

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi all, The spec is now available here: https://review.openstack.org/#/c/235169/ Please help to review. Thanks. On 10/14/2015 10:05 AM, Tang Chen wrote: Hi, all, Please help to review this BP. https://blueprints.launchpad.net/nova/+spec/live-migration-state-machine Currently, the

Re: [openstack-dev] Requests + urllib3 + distro packages

On 10/15/2015 12:18 AM, Robert Collins wrote: On 15 October 2015 at 11:11, Thomas Goirand wrote: One major pain point is unfortunately something ridiculously easy to fix, but which nobody seems to care about: the long & short descriptions format. These are usually buried into

[openstack-dev] [tc][senlin] Request to senlin project to big tent

Dear TC members, Your reviews on the proposal are highly appreciated. Subject: Add senlin project to big tent Link: https://review.openstack.org/#/c/235172/ Regards, Qiming __ OpenStack Development Mailing List (not for

[openstack-dev] [Nova] Host maintenance mode proposal.

Hi all, I tried to implement a common host maintenance mode handling in nova compute. BP: https://blueprints.launchpad.net/nova/+spec/host-maintenance-mode spec: https://review.openstack.org/#/c/228689/ patches: https://review.openstack.org/#/q/topic:bp/host-maintenance-mode,n,z But according

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

On 15/10/15 12:42, Matt Fischer wrote: > > > On Thu, Oct 8, 2015 at 5:38 AM, Vladimir Kuklin > wrote: > > Hi, folks > > * Intro > > Per our discussion at Meeting #54 [0] I would like to propose the > uniform approach of

Re: [openstack-dev] [Nova] Host maintenance mode proposal.

On 10/15/2015 05:23 PM, John Garbutt wrote: On 15 October 2015 at 10:08, Tang Chen wrote: Hi all, I tried to implement a common host maintenance mode handling in nova compute. BP: https://blueprints.launchpad.net/nova/+spec/host-maintenance-mode spec:

Re: [openstack-dev] Requests + urllib3 + distro packages

On 10/15/2015 12:18 AM, Robert Collins wrote: > On 15 October 2015 at 11:11, Thomas Goirand wrote: >> >> One major pain point is unfortunately something ridiculously easy to >> fix, but which nobody seems to care about: the long & short descriptions >> format. These are usually

[openstack-dev] [puppet][ec2api] - First version of puppet module

Hi all, I would like to report to all of you that a first version of OpenStack EC2 API puppet module is available in order to get your feedback. This is the link https://github.com/cernops/puppet-ec2api Please feel free to contribute to this puppet module. All contributions and feedback are

Re: [openstack-dev] [neutron] Neutron rolling upgrade - are we there yet?

Thanks a lot for bringing up this theme! I'm interested in working on online data migration in Mitaka. 3. Database migration a. Online schema migration was done in Liberty release, any work left to do? The work here is finished. The only thing is that I'm aware of is some extra tests

Re: [openstack-dev] [nova-compute][nova][libvirt] Extending Nova-Compute for image prefetching

On 10 October 2015 at 09:35, Alberto Geniola wrote: > Hi Michael, > > and thank you for your answer. > > Indeed, what I want to do is to add methods to the ImageCache.py module > (listing, adding, deleting). So far, this module only takes care of image > deletion: this

Re: [openstack-dev] [Nova] Host maintenance mode proposal.

On 15 October 2015 at 10:08, Tang Chen wrote: > Hi all, > > I tried to implement a common host maintenance mode handling > in nova compute. > > BP: https://blueprints.launchpad.net/nova/+spec/host-maintenance-mode > spec: https://review.openstack.org/#/c/228689/ >

Re: [openstack-dev] [oslo] Require documenting changes with versionadded and versionchanged

On Thu, Oct 15, 2015 at 5:52 AM, Victor Stinner wrote: > Hi, > > I propose that changes must now be documented in Oslo libraries. If a > change is not documented, it must *not* be approved. > > IMHO it's very important to document all changes. Otherwise, it becomes > really

[openstack-dev] [Tacker] Proposing Bob Haddleton to core team

I would like to nominate Bob Haddleton to the Tacker core team. In the current Liberty cycle Bob made significant, across the board contributions to Tacker [1]. Starting with many usability enhancements and squashing bugs Bob has shown commitment and consistently produced high quality code. To

Re: [openstack-dev] [Sender Auth Failure] Re: [neutron] Neutron rolling upgrade - are we there yet?

On Oct 15, 2015, at 11:23 AM, Ihar Hrachyshka > wrote: I also feel that upgrades are in lots of ways not only a technical issue, but a cultural one too. You should have reviewers being aware of all the moving parts, and how a seemingly innocent

[openstack-dev] [puppet] new kilo release: 6.1.0

We're happy to announce the release of: * puppet-ceilometer 6.1.0 * puppet-cinder 6.1.0 * puppet-designate 6.1.0 * puppet-glance 6.1.0 * puppet-heat 6.1.0 * puppet-horizon6.1.0 * puppet-ironic 6.1.0 * puppet-keystone 6.1.0 * puppet-manila

[openstack-dev] [fuel] OpenStack versioning in Fuel

Hello, I would like to highlight a problem that we are now going to have in Fuel regarding versioning of OpenStack. As you know, with introduction of the Big Tent policy it was decided that since Liberty dev cycle versioning schema of the whole project changes. Year-based versions won't be

Re: [openstack-dev] [oslo] Require documenting changes with versionadded and versionchanged

Brant Knudson wrote: On Thu, Oct 15, 2015 at 5:52 AM, Victor Stinner > wrote: Hi, I propose that changes must now be documented in Oslo libraries. If a change is not documented, it must *not* be approved. IMHO it's very

Re: [openstack-dev] [oslo] Require documenting changes with versionadded and versionchanged

Le 15/10/2015 12:52, Victor Stinner a écrit : I started to do this for the oslo.config library: https://review.openstack.org/#/c/235232/ More changes. oslo.concurrency: https://review.openstack.org/#/c/235416/ oslo.serialization: https://review.openstack.org/#/c/235297/ oslo.utils:

Re: [openstack-dev] [neutron] Neutron rolling upgrade - are we there yet?

Hi Artur, thanks a lot for caring about upgrades! There are a lot of good points below. As you noted, surprisingly, we seem to have rolling upgrades working for RPC layer. Before we go into complicating database workflow by doing oslo.versionedobjects transition heavy-lifting, I would like us

Re: [openstack-dev] [oslo] Require documenting changes with versionadded and versionchanged

Le 15/10/2015 16:34, Brant Knudson a écrit : Submitters don't know what release their change is going to get into. They might submit the review when version 1.1.0 is current so they mark it with added in 1.2.0, but then the change doesn't get merged until after 1.4.0 is tagged. Also, the

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

Zaro wrote: > We are soliciting feedback so please let us know what you think. For spotting possible trivial bug fixes the new query option "delta" will be useful. For example: "status:open delta:<100" Would it be possible to create a "prio" label to help sorting out stuff? If I understand [1]

[openstack-dev] [Ironic] Driver documentation in Ironic

Hi All, This mail is related to driver-specific documentation in Ironic. First a bit of context. I work on iLO drivers in Ironic. Our team would like to document both Ironic driver related stuff (which is related to Ironic) and hardware related stuff like tested platforms, firmware information,

Re: [openstack-dev] [puppet][ec2api] - First version of puppet module

Hi Marcos, On 10/15/2015 03:49 AM, Marcos Fermin Lobo wrote: > Hi all, > > I would like to report to all of you that a first version of OpenStack > EC2 API puppet module is available in order to get your feedback. > > This is the link https://github.com/cernops/puppet-ec2api > > Please feel

[openstack-dev] cinder authentication with authtoken

Hi, I need a way to access cinder apis using auth-token. I used below API to get the cinder client and tried getting the availability zones. cinder_client = cc.Client(1, auth_token=self.ctxt.auth_token, project_id=self.ctxt.tenant,

Re: [openstack-dev] [neutron] pypi packages for networking sub-projects

On 02/10/15 12:33, Neil Jerram wrote: > On 02/10/15 11:42, Neil Jerram wrote: >> Thanks Kyle! I'm looking at this now for networking-calico. > Done, please see https://pypi.python.org/pypi/networking-calico. > > When you release, how will the version number be decided? [...] Excitingly, I

Re: [openstack-dev] [sahara] Proposing Vitaly Gridnev to core reviewer team

Congrats Vitaly!! On Thu, Oct 15, 2015 at 11:40 AM Sergey Lukjanov wrote: > I think we have a quorum. > > Vitaly, congrats! > > On Tue, Oct 13, 2015 at 6:39 PM, Matthew Farrellee > wrote: > >> +1! >> >> On 10/12/2015 07:19 AM, Sergey Lukjanov wrote: >>

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

Matt > You are right, it probably won't. At that point you are using puppet to work around some fundamental issues in your OpenStack deployment. Actually, as you know, with Fuel we are shipping our code to people who have their own infrastructure. We do not have any control over that

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

On Thu, Oct 15, 2015 at 4:10 AM, Vladimir Kuklin wrote: > Gilles, > > 5xx errors like 503 and 502/504 could always be intermittent operational > issues. E.g. when you access your keystone backends through some proxy and > there is a connectivity issue between the proxy and

Re: [openstack-dev] [sahara] Proposing Vitaly Gridnev to core reviewer team

congrats Vitaly! On 10/15/2015 10:38 AM, Sergey Lukjanov wrote: I think we have a quorum. Vitaly, congrats! On Tue, Oct 13, 2015 at 6:39 PM, Matthew Farrellee > wrote: +1! On 10/12/2015 07:19 AM, Sergey Lukjanov wrote: Hi folks,

Re: [openstack-dev] [sahara] Proposing Vitaly Gridnev to core reviewer team

Thank you! I'm very happy to be a part of sahara core team. On Thu, Oct 15, 2015 at 5:38 PM, Sergey Lukjanov wrote: > I think we have a quorum. > > Vitaly, congrats! > > On Tue, Oct 13, 2015 at 6:39 PM, Matthew Farrellee > wrote: > >> +1! >> >> On

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

This thread is really huge and only 3 people are talking. Why don't you continue on an etherpad and do some brainstorm on it? If you do so, please share the link here. It would be much more effective in my opinion. On 10/15/2015 08:26 AM, Sofer Athlan-Guyot wrote: > Gilles Dubreuil

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

On Thu, Oct 15, 2015 at 08:25:40PM +0900, Takashi Yamamoto wrote: > hi, > > i'm looking in fwaas tempest tests and have a question about code location. > > currently, > > - fwaas api tests and its rest client are in neutron repo This is a bad situation because it means that we're directly

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

On Thu, Oct 15, 2015 at 09:02:22AM -0400, Assaf Muller wrote: > On Thu, Oct 15, 2015 at 7:25 AM, Takashi Yamamoto > wrote: > > > hi, > > > > i'm looking in fwaas tempest tests and have a question about code location. > > > > currently, > > > > - fwaas api tests and its

Re: [openstack-dev] [sahara] Proposing Vitaly Gridnev to core reviewer team

I think we have a quorum. Vitaly, congrats! On Tue, Oct 13, 2015 at 6:39 PM, Matthew Farrellee wrote: > +1! > > On 10/12/2015 07:19 AM, Sergey Lukjanov wrote: > >> Hi folks, >> >> I'd like to propose Vitaly Gridnev as a member of the Sahara core >> reviewer team. >> >> Vitaly

Re: [openstack-dev] Requests + urllib3 + distro packages

On 10/15/2015 02:53 AM, Thomas Goirand wrote: On 10/15/2015 12:18 AM, Robert Collins wrote: On 15 October 2015 at 11:11, Thomas Goirand wrote: One major pain point is unfortunately something ridiculously easy to fix, but which nobody seems to care about: the long & short

Re: [openstack-dev] Requests + urllib3 + distro packages

On 10/15/2015 03:59 PM, Monty Taylor wrote: > On 10/15/2015 02:53 AM, Thomas Goirand wrote: >> Well, having the changlog (and other stuff) of packages merged into the >> long description is not helpful, not for Debian, nor for upstream Python >> packages. > > I actually have gotten multiple

Re: [openstack-dev] getting rid of tablib completely (Requests + urllib3 + distro packages)

On 10/15/2015 07:35 PM, Doug Hellmann wrote: > Excerpts from Thomas Goirand's message of 2015-10-15 00:31:44 +0200: > I wasn't clear. The reason cliff-tablib exists is because of earlier > complaints (maybe from you?) about tablib. I didn't have time to > rewrite the formatters, so I pulled them

Re: [openstack-dev] [Product] [fuel] Life cycle management use cases

Hi All, in regards to lifecycle management I've just submitted blueprint covering security assessment of OpenStack clouds [0]. Note that it doesn't aim to intersect with Congress project. Congress is focused on 'overlay' or cloud security policy. Nessus integration is 100% oriented towards cloud

Re: [openstack-dev] [packaging] liberty doesn't have caps on deps

... >> Now there is an explicit list of what works. >> >> Isn't that *better* ? >> > Yes, it's good to know what works, does that show multiple versions of > the same package when multiple are known to work? It shows the highest version we know to work. So you could in principle take any version

Re: [openstack-dev] [packaging] liberty doesn't have caps on deps

On 16 October 2015 at 12:09, Matthew Thode wrote: > On 10/15/2015 06:00 PM, Robert Collins wrote: > Thanks for the replies, I think I have a way forward (using upper-reqs > as a cap). I might need to make a tool that munges the (test-)reqs.txt > to generate one as an

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

On 15/10/15 21:10, Vladimir Kuklin wrote: > Gilles, > > 5xx errors like 503 and 502/504 could always be intermittent operational > issues. E.g. when you access your keystone backends through some proxy > and there is a connectivity issue between the proxy and backends which > disappears in 10

Re: [openstack-dev] [puppet] Proposing Denis Egorenko core

On 10/15/2015 02:44 PM, Dmitry Borodaenko wrote: Congratulations Denis, keep it up! On behalf of Fuel team, I'd like to thank Puppet OpenStack team for inviting, welcoming, and enabling the massive expansion of collaboration between our projects. We have gone a great distance from a monolithic

Re: [openstack-dev] [Product] [fuel] Life cycle management use cases

Hi Shamail, thank you for letting me know. I didn't come through the page when I was googling. We are collecting use cases though for underlay, so it's more relevant for such projects as Fuel, TripleO, Puppet OpenStack; than for VM, DB, etc. related management. If you have any work started on

Re: [openstack-dev] [Neutron] Revision of the RFE/blueprint submission process

A follow-up... On 13 October 2015 at 18:38, Armando M. wrote: > Hi neutrinos, > > From last cycle, the team has introduced the concept of RFE bugs [0]. I > have suggested a number of refinements over the past few days [1,2,3] to > streamline/clarify the process a bit further,

Re: [openstack-dev] [Neutron] Revision of the RFE/blueprint submission process

On 14 October 2015 at 00:17, Flavio Percoco wrote: > On 13/10/15 18:38 -0700, Armando M. wrote: > >> Hi neutrinos, >> >> From last cycle, the team has introduced the concept of RFE bugs [0]. I >> have >> suggested a number of refinements over the past few days [1,2,3] to >>

Re: [openstack-dev] Requests + urllib3 + distro packages

On 10/15/2015 12:08 PM, Cory Benfield wrote: >> On 14 Oct 2015, at 23:23, Thomas Goirand wrote: >> Though you could have avoid all of this pain if you were not bundling. >> Isn't all of this make you re-think your vendorizing policy? Or still >> not? I'm asking because I still

Re: [openstack-dev] [packaging] liberty doesn't have caps on deps

Excerpts from Matthew Thode's message of 2015-10-15 14:35:08 -0500: > On 10/15/2015 02:17 PM, Matt Riedemann wrote: > > > > > > On 10/15/2015 2:10 PM, Matthew Thode wrote: > >> On 10/15/2015 02:04 PM, Robert Collins wrote: > >>> On 16 October 2015 at 08:01, Matthew Thode > >>>

Re: [openstack-dev] [release] opening stable/liberty

On Thu, Oct 15, 2015 at 02:30:23PM -0400, Doug Hellmann wrote: > One of the first steps for opening stable/liberty is to update the > version settings in the branches to no longer use pre-versioning. > Thierry submitted a bunch of patches to projects [0], and some are > merging now. > > Others

Re: [openstack-dev] Do all OpenStack daemons support sd_notify?

On 12/16/2014 11:59 AM, Alan Pevec wrote: > There's one issue with Type=notify that Dan Prince discovered and > where Type=simple works better for his use-case: > if service startup takes more than DefaultTimeoutStartSec (90s by > default) and systemd does not get notification from the service, it

[openstack-dev] [Large Deployment Team] Action/Work Items Ahead of Summit, please review

During our meeting [1] today we discussed our agenda [2] and action items for the LDT working session [3] at the summit. We’ve compiled a list of a few things folks can be working on before getting to Tokyo to ensure this session is productive: 1. Neutron Segmented/Routed Networks: *

Re: [openstack-dev] [packaging] liberty doesn't have caps on deps

Excerpts from Doug Hellmann's message of 2015-10-15 15:57:20 -0400: > Excerpts from Matthew Thode's message of 2015-10-15 14:35:08 -0500: > > On 10/15/2015 02:17 PM, Matt Riedemann wrote: > > > > > > > > > On 10/15/2015 2:10 PM, Matthew Thode wrote: > > >> On 10/15/2015 02:04 PM, Robert Collins

[openstack-dev] [OSSN 0057] DoS attack on Glance service can lead to interruption or disruption

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 DoS attack on Glance service can lead to interruption or disruption - --- ### Summary ### The typical Glance workflow allows authenticated users to create an image and upload the image content in a separate step. This can be abused by malicious

Re: [openstack-dev] [packaging] liberty doesn't have caps on deps

On 10/15/2015 05:29 PM, Robert Collins wrote: > On 16 October 2015 at 11:21, Matthew Thode wrote: >> On 10/15/2015 05:12 PM, Robert Collins wrote: >>> On 16 October 2015 at 08:10, Matthew Thode >>> wrote: On 10/15/2015 02:04 PM, Robert

Re: [openstack-dev] Requests + urllib3 + distro packages

On 10/15/2015 11:20 AM, Dmitry Tantsur wrote: > On 10/15/2015 12:18 AM, Robert Collins wrote: >> On 15 October 2015 at 11:11, Thomas Goirand wrote: >>> >>> One major pain point is unfortunately something ridiculously easy to >>> fix, but which nobody seems to care about: the long

[openstack-dev] [puppet] puppet-neutron + vswitch gates are broken

ubuntu broke openvswitch last night because of: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887 I reached them on IRC and they are working on a new release with a fix. We should expect our CI back later tonight or tomorrow morning. -- Emilien Macchi signature.asc

Re: [openstack-dev] Do all OpenStack daemons support sd_notify?

Thanks for responding, does this make it longest by time duration thread ever? :) 2015-10-15 22:44 GMT+02:00 Thomas Goirand : > On 12/16/2014 11:59 AM, Alan Pevec wrote: ... >> Current implementation in oslo service sends notification only just >> before entering the wait loop,

Re: [openstack-dev] [packaging] liberty doesn't have caps on deps

On 16 October 2015 at 08:10, Matthew Thode wrote: > On 10/15/2015 02:04 PM, Robert Collins wrote: ... >>> Where are my caps? >> >> The known good versions of dependencies for liberty are >>

Re: [openstack-dev] [packaging] liberty doesn't have caps on deps

On 16 October 2015 at 11:21, Matthew Thode wrote: > On 10/15/2015 05:12 PM, Robert Collins wrote: >> On 16 October 2015 at 08:10, Matthew Thode wrote: >>> On 10/15/2015 02:04 PM, Robert Collins wrote: >> ... > Where are my caps?

Re: [openstack-dev] [release] establishing release liaisons for mitaka

Excerpts from Sergey Lukjanov's message of 2015-10-15 22:34:21 +0300: > Doug, just to confirm - for Sahara I'll continue being release liaison. Thanks, Sergey. __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] Do all OpenStack daemons support sd_notify?

On 12/15/2014 04:21 PM, Ihar Hrachyshka wrote: > On 14/12/14 09:45, Thomas Goirand wrote: >> Hi, > >> As I am slowing fixing all systemd issues for the daemons of >> OpenStack in Debian (and hopefully, have this ready before the >> freeze of Jessie), I was wondering what kind of Type= directive

Re: [openstack-dev] [packaging] liberty doesn't have caps on deps

On 10/15/2015 05:12 PM, Robert Collins wrote: > On 16 October 2015 at 08:10, Matthew Thode wrote: >> On 10/15/2015 02:04 PM, Robert Collins wrote: > ... Where are my caps? >>> >>> The known good versions of dependencies for liberty are >>>

Re: [openstack-dev] [packaging] liberty doesn't have caps on deps

On 16 October 2015 at 08:57, Doug Hellmann wrote: > Excerpts from Matthew Thode's message of 2015-10-15 14:35:08 -0500: >> On 10/15/2015 02:17 PM, Matt Riedemann wrote: >> > > > We're going to try to cover it in >

Re: [openstack-dev] Scheduler proposal

Ed Leafe wrote: Wow, I seem to have unleashed a bunch of pent-up frustration in the community! It's great to see everyone coming forward with their ideas and insights for improving the way Nova (and, by extension, all of OpenStack) can potentially scale. I do have a few comments on the

Re: [openstack-dev] [Nova] Host maintenance mode proposal.

Hi all, I have update the spec. https://review.openstack.org/#/c/228689/ I think implement it on nova client side may be better. Please help to review. Thanks. On 10/15/2015 05:08 PM, Tang Chen wrote: Hi all, I tried to implement a common host maintenance mode handling in nova compute.

Re: [openstack-dev] [Cinder][Horizon] Cinder v2 endpoint name: volumev2 is required? volume is okay?

Hi Akihiro, Cinder itself doesn't care what keystone endpoint name is configured for it. python-cinderclient uses cinderv2 for service name [1], [2] by default. AFAIK, some other components like Rally expects "volumev2" endpoint for API v2. "volume" is used for Tempest by default. [1]

Re: [openstack-dev] ERROR : openstack Forbidden (HTTP 403)

/var/tmp/packstack/20151015-212559-xwC1zD/manifests/10.16.37.221_keystone.pp.log Could someone please help me with this? On Mon, Oct 12, 2015 at 5:16 PM, Dhvanan Shah <dhva...@gmail.com> wrote: > Resolved it. > The no_proxy env var needs to be set if your computer is located behind a

[openstack-dev] [QA] Design Summit Schedule

Hi Everyone, I just pushed up the QA schedule for design summit: https://mitakadesignsummit.sched.org/overview/type/qa Let me know if there are any big schedule conflicts or other issues, so we can work through the problem. Thanks, Matt Treinish signature.asc Description: PGP signature

Re: [openstack-dev] [Tacker] Proposing Bob Haddleton to core team

+1 - Stephen On Thu, Oct 15, 2015 at 8:47 AM, Sridhar Ramaswamy wrote: > I would like to nominate Bob Haddleton to the Tacker core team. > > In the current Liberty cycle Bob made significant, across the board > contributions to Tacker [1]. Starting with many usability

Re: [openstack-dev] [Tacker] Proposing Bob Haddleton to core team

+1 -Bharath T On Thu, Oct 15, 2015 at 10:36 PM, Stephen Wong wrote: > +1 > > - Stephen > > On Thu, Oct 15, 2015 at 8:47 AM, Sridhar Ramaswamy > wrote: > >> I would like to nominate Bob Haddleton to the Tacker core team. >> >> In the current

Re: [openstack-dev] [Tacker] Proposing Bob Haddleton to core team

+1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [puppet] Proposing Denis Egorenko core

On 10/13/2015 04:29 PM, Emilien Macchi wrote: > Denis Egorenko (degorenko) is working on Puppet OpenStack modules for > quite some time now. > > Some statistics [1] about his contributions (last 6 months): > * 270 reviews > * 49 negative reviews > * 216 positive reviews > * 36 disagreements > *

Re: [openstack-dev] [puppet] Proposing Denis Egorenko core

Thank you! I will do my best! 2015-10-15 19:27 GMT+03:00 Emilien Macchi : > > > On 10/13/2015 04:29 PM, Emilien Macchi wrote: > > Denis Egorenko (degorenko) is working on Puppet OpenStack modules for > > quite some time now. > > > > Some statistics [1] about his contributions

[openstack-dev] [Heat] Mitaka design summit schedule

Hi folks, I glad to inform you about final version of Heat schedule for design summit. Online version is available here: - http://mitakadesignsummit.sched.org/type/Heat#.Vh_V7NSlyko It will be useful for understanding rooms and time. If you want to look on description and etherpad for each

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

On Thu, Oct 15, 2015 at 10:13 AM, Assaf Muller wrote: > > > On Thu, Oct 15, 2015 at 10:22 AM, Matthew Treinish > wrote: > >> On Thu, Oct 15, 2015 at 09:02:22AM -0400, Assaf Muller wrote: >> > On Thu, Oct 15, 2015 at 7:25 AM, Takashi Yamamoto < >>

Re: [openstack-dev] [neutron] pypi packages for networking sub-projects

On Thu, Oct 15, 2015 at 7:03 AM, Neil Jerram wrote: > On 02/10/15 12:33, Neil Jerram wrote: > > On 02/10/15 11:42, Neil Jerram wrote: > >> Thanks Kyle! I'm looking at this now for networking-calico. > > Done, please see https://pypi.python.org/pypi/networking-calico.

Re: [openstack-dev] getting rid of tablib completely (Requests + urllib3 + distro packages)

Excerpts from Thomas Goirand's message of 2015-10-15 00:31:44 +0200: > On 10/13/2015 05:14 PM, Doug Hellmann wrote: > > Excerpts from Thomas Goirand's message of 2015-10-13 12:38:00 +0200: > >> On 10/12/2015 11:09 PM, Steve Baker wrote: > >>> On 13/10/15 02:05, Thomas Goirand wrote: > >

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

I would love to see this! It would really help review priorities and could easily be worked into review dashboards. --John On 15 Oct 2015, at 8:42, Markus Zoeller wrote: > Zaro wrote: >> We are soliciting feedback so please let us know what you think. > > For spotting possible trivial bug

Re: [openstack-dev] [Tacker] Proposing Bob Haddleton to core team

+1 ☺ -Sripriya From: Sridhar Ramaswamy [mailto:sric...@gmail.com] Sent: Thursday, October 15, 2015 8:47 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Tacker] Proposing Bob Haddleton to core team I would like

Re: [openstack-dev] [oslo] Require documenting changes with versionadded and versionchanged

Excerpts from Joshua Harlow's message of 2015-10-15 08:54:47 -0700: > Brant Knudson wrote: > > > > > > On Thu, Oct 15, 2015 at 5:52 AM, Victor Stinner > > wrote: > > > > Hi, > > > > I propose that changes must now be documented in Oslo

Re: [openstack-dev] [Tacker] Proposing Bob Haddleton to core team

+1 From: Sridhar Ramaswamy [mailto:sric...@gmail.com] Sent: Thursday, October 15, 2015 8:47 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Tacker] Proposing Bob Haddleton to core team I would like to nominate Bob Haddleton to the Tacker core team.

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

On Thu, Oct 15, 2015 at 10:22 AM, Matthew Treinish wrote: > On Thu, Oct 15, 2015 at 09:02:22AM -0400, Assaf Muller wrote: > > On Thu, Oct 15, 2015 at 7:25 AM, Takashi Yamamoto > > > wrote: > > > > > hi, > > > > > > i'm looking in fwaas tempest tests

Re: [openstack-dev] [release] establishing release liaisons for mitaka

Doug, just to confirm - for Sahara I'll continue being release liaison. On Thu, Oct 15, 2015 at 3:40 AM, Lana Brindley wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 15/10/15 01:25, Doug Hellmann wrote: > > As with the other cross-project teams,

Re: [openstack-dev] [packaging] liberty doesn't have caps on deps

On 10/15/2015 02:17 PM, Matt Riedemann wrote: > > > On 10/15/2015 2:10 PM, Matthew Thode wrote: >> On 10/15/2015 02:04 PM, Robert Collins wrote: >>> On 16 October 2015 at 08:01, Matthew Thode >>> wrote: So, this is my perspective in packing liberty for Gentoo.

[openstack-dev] [openstack-ansible] Mitaka Summit Schedule

Hi everyone, I've added the final details for the summit sessions to the etherpad: https://etherpad.openstack.org/p/openstack-ansible-mitaka-summit Our sessions are open to anyone with an interest in deploying OpenStack with Ansible. Note that our two primary topics for discussion are:

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

On Wed, Oct 14, 2015 at 3:08 AM Zaro wrote: > Hello All, > > The openstack-infra team would like to upgrade from our Gerrit 2.8 to > Gerrit 2.11. We are proposing to do the upgrade shortly after the > Mitaka summit. The main motivation behind the upgrade is to allow us > to

[openstack-dev] [release] opening stable/liberty

One of the first steps for opening stable/liberty is to update the version settings in the branches to no longer use pre-versioning. Thierry submitted a bunch of patches to projects [0], and some are merging now. Others are running into test failures, though, and need attention from project

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

Thanks for the suggestion Markus. I think the path for those types of suggestions would be thru a spec: http://specs.openstack.org/openstack-infra/infra-specs/ Thanks for reporting these Yuriy. I've created a checklist[1] to track things to verify before we actually do anything. I think at

  1   2   >