Re: [openstack-dev] [magnum] Streamline adoption of Magnum

  -Original Message- From: Monty Taylor <mord...@inaugust.com> Reply: Monty Taylor <mord...@inaugust.com> Date: March 23, 2016 at 16:52:52 To: Ian Cordasco <sigmaviru...@gmail.com>, OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.o

Re: [openstack-dev] [magnum] Streamline adoption of Magnum

fragmentation and disaster. > > Agree. Perhaps, if the problem is less that two new services is problematic and the real problem is one (or some combination) of: - Magnum and Barbican's dependency is poorly (if at all) documented - Magnum and Barbican don't have documentation

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

run into problems upgrading. That said, I think my team is the only team doing this. (Or at least, none of the other active members of the IRC channel talk about doing this.) So it might not be anything more than a "nice to have" especially since no one else from the project has chimed i

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

This affects other OpenStack projects like the OpenStack Ansible project which builds from trunk and does periodic upgrades from the latest stable branch to whatever is running on master. Further they're using pip and this

Re: [openstack-dev] [magnum] High Availability

bican. Users will use their > OpenStack credentials > to log into Kubernetes. This seems perfectly fine but I don't think this should be an alternative to using TLS to talk to Kubernetes. Personally, I want everything to use TLS so if my option is Keystone or TLS, I'm not going to be sat

Re: [openstack-dev] [oslo][all] What would you like changed/fixed/new in oslo??

penStack Ansible project already does this. I'd be surprised if the other deployment projects aren't already doing this. Besides I'm not certain this is something that oslo/oslo.messaging can enforce. > 3. We desperately need a CA story. Like Anchor (https://wiki.openstack.org/wiki/

Re: [openstack-dev] [all] Maintaining httplib2 python library

ot interested in adding maintainers after all. Either way, it's likely a dying project and not one we should hold onto. But I mean, ignoring that it's dying, it's a great piece of software. -- Ian Cordasco __ OpenStac

Re: [openstack-dev] [magnum] High Availability

excluding it from the VMT until this code is fixed/removed). You're solving for a demographic that doesn't seem to be represented here. This feature needs far more justification in the way of *real* user stories for magnum where they cannot or will not de

Re: [openstack-dev] [all] Maintaining httplib2 python library

t;openstack-dev@lists.openstack.org> Subject:  Re: [openstack-dev] [all] Maintaining httplib2 python library > On Mon, 14 Mar 2016, Ian Cordasco wrote: > > > To be transparent, I've also reached out to Joe to help. My main > > motivation, though, is to bring it to the point where the &g

Re: [openstack-dev] [all] Maintaining httplib2 python library

t;openstack-dev@lists.openstack.org> Subject:  Re: [openstack-dev] [all] Maintaining httplib2 python library > On Mon, 14 Mar 2016, Sean Dague wrote: > > On 03/14/2016 10:24 AM, Ian Cordasco wrote: > >> And then we can (and should) also ask "Why have we been using this? &

Re: [openstack-dev] [all] Maintaining httplib2 python library

t:  Re: [openstack-dev] [all] Maintaining httplib2 python library > On 03/14/2016 10:24 AM, Ian Cordasco wrote: > > > > > > -Original Message- > > From: Davanum Srinivas > > Reply: OpenStack Development Mailing List (not for usage questions) >

Re: [openstack-dev] [all] Maintaining httplib2 python library

uot; And then we can (and should) also ask "Why have we been using this? How much work do cores think it would be to remove this from our global requirements?" -- Ian Cordasco __ OpenStack Development Mail

Re: [openstack-dev] [glance]Why vm boots from the cirros image so slow?

pect someone who actually works on the CirrOS project would know better (https://launchpad.net/cirros). -- Ian Cordasco __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lis

Re: [openstack-dev] [glance]one more use case for Image Import Refactor from OPNFV

und to working on image cloning. I suspect Newton will be much the same as we continue to work on image import (which I expect will be our main focus for Newton). Maybe after we have image import nailed down and implemented and Nova using v2, we can then focus on image cloning and Glare

Re: [openstack-dev] [api][all] api variation release by release

: > https://dague.net/2015/06/05/the-nova-api-in-kilo-and-beyond-2/ > > The idea is people can deploy any commit of Nova in production. > So to work out what is supported you just look at this API: > http://developer.openstack.org/api-ref-compute-v2.1.html#listVersionsv2.1 >

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

-Original Message- From: Mike Perez <thin...@gmail.com> Reply: Mike Perez <thin...@gmail.com> Date: February 22, 2016 at 11:51:39 To: Ian Cordasco <sigmaviru...@gmail.com>, OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openst

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

light Poppy being different from the rest of OpenStack. Would third-party integration CI not be satisfactory? -- Ian Cordasco __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@

Re: [openstack-dev] [glance]one more use case for Image Import Refactor from OPNFV

h Jay. What you might prefer is a way to get something akin to Swift's TempURL so you could give that as a location to your other Glance instance. We don't support that though and there doesn't seem any use case that we would like t

Re: [openstack-dev] [openstack-ansible] network question and documentation

iners and inet should be set > to manual". > > I think it will be good (but i may be wrong ;-) ) that in chapter 3 of the > "install guide: configuring > the network on target host", you p

Re: [openstack-dev] Questions regarding image "location" and glanceclient behaviour ...

ere Glance download the images by itself, > on demand. > > How to do this with V2 ? You can use glance image-create without passing it any image data. You should then be able to use location-add and I believe Glance will download the image

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

anything, a consumer of OpenStack would probably like the freedom that poppy will provide in being able to swap out existing CDN providers while consuming the same API. But that's just my two cents as a non-TC community member. -- Ian Cordasco _

Re: [openstack-dev] [Openstack-operators] How are consumers/operators new to openstack supposed to know about upper-constraints?

On Feb 16, 2016 11:04 AM, "Sean Dague" <s...@dague.net> wrote: > > On 02/16/2016 11:48 AM, Ian Cordasco wrote: > > > > > > -Original Message- > > From: Matt Riedemann <mrie...@linux.vnet.ibm.com> > > Reply: Matt Riedemann <mrie..

Re: [openstack-dev] [Nova][Glance]Glance v2 api support in Nova

On Fri, Feb 12, 2016 at 9:24 AM, Mikhail Fedosin wrote: > Hello! > > In late December I wrote several messages about glance v2 support in Nova > and Nova's xen plugin. Many things have been done after that and now I'm > happy to announce that there we have a set of commits

Re: [openstack-dev] [swift] Plan to add Python 3 support to Swift

t;openstack-dev@lists.openstack.org> Subject:  Re: [openstack-dev] [swift] Plan to add Python 3 support to Swift > Le 12/02/2016 15:12, Ian Cordasco a écrit : > > Just to interject here, RFC 2616 is the one you're talking about. That > > encoding requirement was dropped when HTTP/1.1

Re: [openstack-dev] [glance] Glance Core team additions/removals

; To all other members of the community. Please, provide your feedback. > > Unless someone objects, the above will be effective next Tuesday. We're definitely suffering by losing those Fei Long and Alex but it only makes sense, and I hope when they have time to resume their responsibilities th

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

t;openstack-dev@lists.openstack.org> Subject:  Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward > On 01/21/2016 02:38 AM, Ian Cordasco wrote: > > That said, I'd like to see a different release cadence for cycles that are > > "sta

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

o backport a lot of work to the X.0 series and while we could support X.0 series with specific backports, it would avoid stressing our already small stable teams. My release strategy, however, may cause more stress for downstream packages though. It'll cause them to have to decide what and when

Re: [openstack-dev] [API] [Glance] New v2 Image Import Specification Discussion

-Original Message- From: Ian Cordasco <ian.corda...@rackspace.com> Reply: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Date: January 8, 2016 at 11:16:35 To: OpenStack Development Mailing List (not for usage questions) &l

[openstack-dev] [API] [Glance] New v2 Image Import Specification Discussion

but not yet processed data. That's an important question to have, but I don't have an easy answer for it though. I hope someone else does. References: [1]  https://specs.openstack.org/openstack/glance-specs/specs/mitaka/approved/image-impor

Re: [openstack-dev] [all] re-introducing twisted to global-requirements

How is the interface created? It > seems like it would be possible for the mocked API to not match the actual > API. I agree. It's very easy for servers intending to mimic APIs and their behaviour to fall out of synchro

Re: [openstack-dev] [stable] kilo and liberty is blocked on bug 1532048

in kilo which breaks kilo jobs and grenade jobs > in liberty. > > The cap in stable/kilo g-r is here: > > https://review.openstack.org/#/c/265025/ > > I'll babysit the reqs sync to horizon in kilo tonight which should then > free things up again.

Re: [openstack-dev] [openstack][glance] add new property to image

On 12/31/15, 01:36, "suresh knv" wrote: >Hi, > >I am trying to run Openstack on ARM64 architecture. ARM64 architecture >with KVM hypervisor needs GIC version(generic interrupt controller) >as a property for the image when we are creating/uploading an image. I >would

Re: [openstack-dev] [api] - WSGI 2.0 Call for Interest

On 1/4/16, 09:28, "Hayes, Graham" wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >I saw this [0] float by in an IRC room this morning - >is this something the API WG / OpenStack should be thinking of >participating in? > >0 -

Re: [openstack-dev] [stable] meeting time proposal

On 12/16/15, 16:41, "Tony Breeds" wrote: >On Wed, Dec 16, 2015 at 01:12:13PM -0600, Matt Riedemann wrote: >> I'm not entirely sure what the geo distribution is for everyone that >>works >> on stable, but I know we have people in Europe and some people in >>Australia.

Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API

On 12/14/15, 02:18, "Kuvaja, Erno" wrote: >> -Original Message- >> From: McLellan, Steven >> Sent: Friday, December 11, 2015 6:37 PM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service

Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API

On 12/11/15, 12:25, "Alexander Tivelkov" wrote: >Hi folks! > > >As it was decided during the Mitaka design summit, we are separating the >experimental Artifact Repository API from the main Glance API. This API >will have a versioning sequence independent from the main

Re: [openstack-dev] [all][glance] Add Sabari Kumar Murugesan <smuruge...@vmware.com>

On 11/23/15, 14:20, "Flavio Percoco" wrote: >Greetings, > >I'd like to propose adding Sabari Kumar Murugesan to the glance-core >team. Sabari has been contributing for quite a bit to the project with >great reviews and he's also been providing great feedback in matters

Re: [openstack-dev] [infra][glance] How do we fix the glance_store git > glance-store LP mapping?

On 11/19/15, 10:00, "Matt Riedemann" wrote: >Patches in Gerrit aren't syncing status to the glance-store project in >launchpad b/c the project in launchpad is called glance-store and in git >it's glance_store. > >Looking at the project creators guide it says to

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

Does that mean that https://review.openstack.org/177397 will be updated to fully address the API-WG and Defcore feedback? How soon can we expect the spec to reflect that feedback and the code will be updated for it? On 10/30/15, 18:54, "Alexander Tivelkov" wrote: >Hi

[openstack-dev] [bandit] [glance] [openstack-ansible] [searchlight] Resigning from core reviewers teams

Hi everyone, Today I'm removing myself from the core reviewer (and driver) teams for the following projects: - Bandit (bandit-core and

Re: [openstack-dev] [bandit] [glance] [openstack-ansible] [searchlight] Resigning from core reviewers teams

Apologies for whatever happened with the formatting the first time I sent this. I've tried to ensure that doesn't happen again: Hi everyone, Today I'm removing myself from the core reviewer (and driver) teams for the following projects: - Bandit - Glance - OpenStack Ansible - Searchlight

Re: [openstack-dev] [openstack-ansible] To NTP, or not to NTP, that is the question

On 9/18/15, 08:03, "Major Hayden" wrote: >Hey there, > >I start working on a bug[1] last night about adding a managed NTP >configuration to openstack-ansible hosts. My patch[2] gets chrony up and >running with configurable NTP servers, but I'm still struggling to meet >the

Re: [openstack-dev] [Glance] glance core rotation part 1

e > Arnaud Legendre > Mark Washenberger > Iccha Sethi I think these are overdue > Zhi Yan Liu (Limited activity in Kilo and absent in Liberty) Sad to see Zhi Yan Liu's activity drop off. > Please vote +1 or -1 and w

Re: [openstack-dev] Weekly Meeting on Sep 1

On 8/31/15, 13:59, "Serg Melikyan" wrote: >Hi folks, > > >I want to let you know that I would not be able to chair tomorrow's >weekly meeting, Nikolai Starodubtsev is going to temporary replace me on >this meeting. > > >-- >Serg Melikyan, Senior Software Engineer at

Re: [openstack-dev] [hacking] [style] multi-line imports PEP 0328

On 8/25/15, 10:58, Clay Gerrard clay.gerr...@gmail.com wrote: On Tue, Aug 25, 2015 at 8:45 AM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Mon, 2015-08-24 at 22:53 -0700, Clay Gerrard wrote: So, I know that hacking has H301 (one import per line) - but say maybe you wanted to

Re: [openstack-dev] [packaging] asks from the ops meetup

Questions in-line, but I'd appreciate a better summary On 8/19/15, 17:50, Matthew Thode prometheanf...@gentoo.org wrote: I'll start by giving this out, but I'll also summarize the asks we had from upstream. https://etherpad.openstack.org/p/PAO-ops-packaging General services: - gate check on

Re: [openstack-dev] [Glance] glance_store and glance

On 8/7/15, 07:19, Nicolas Trangez nicolas.tran...@scality.com wrote: On Fri, 2015-08-07 at 01:21 -0400, Nikhil Komawar wrote: 3. ease of addition of newer drivers for the developers -- drivers are only being removed since. The OpenStack team at Scality developed a Glance Store driver for

Re: [openstack-dev] [Security] Would people see a value in the cve-check-tool? (Reshetova, Elena)

On 8/5/15, 08:14, McPeak, Travis travis.mcp...@hp.com wrote: (Merging thread from security ML) Bandit probably isn¹t the correct integration point for this - cve-check has its own analysis procedures while Bandit uses Python AST. Also I see the use workflows being different. For Bandit a

Re: [openstack-dev] Would people see a value in the cve-check-tool?

On 8/4/15, 13:17, Clark, Robert Graham robert.cl...@hp.com wrote: Hi Elena, This is interesting work, thanks for posting it (and for posting it here on openstack-dev, we are trying to wind down the security ML) though maybe use the [Security] tag in the subject line next time. I think this

Re: [openstack-dev] [pbr] [stable] [infra] How to generate .Z version increments on stable/liberty commits

On 8/3/15, 11:11, Thierry Carrez thie...@openstack.org wrote: Jeremy Stanley wrote: On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote: [...] In order to make this work, it looks like we'd require: * pbr changes so that it supports a mode where every commit on the branch

Re: [openstack-dev] [openstack-ansible] [os-ansible-deployment] Kilo - Liberty Upgrade Problems

On 7/31/15, 07:40, Jesse Pretorius jesse.pretor...@gmail.com wrote: I'm adding openstack-operators too as this is a discussion that I think it would be useful to have their input for. I've removed them from the CC since I don't think we're supposed to cross-post. So what would the resulting

[openstack-dev] [openstack-ansible] [os-ansible-deployment] Kilo - Liberty Upgrade Problems

Hey all, As you may have seen elsewhere on openstack-dev, OpenStack is changing the versioning for the service projects. This means our previous upgrade solution will not continue to work. For context, one of our project's goals is to have in-place upgrades be a reality. Previously, using our

Re: [openstack-dev] [glance] Removing python-swiftclient from requirements.txt

On 7/29/15, 13:27, William M Edmonds edmon...@us.ibm.com wrote: From: Doug Hellmann d...@doughellmann.com To: openstack-dev openstack-dev@lists.openstack.org Date: 07/28/2015 07:59 PM Subject: Re: [openstack-dev] [glance] Removing python-swiftclient from requirements.txt snip I

Re: [openstack-dev] [Openstack-operators] [glance] Removal of Catalog Index Service from Glance

On 7/27/15, 11:29, Louis Taylor lo...@kragniz.eu wrote: On Fri, Jul 17, 2015 at 07:50:55PM +0100, Louis Taylor wrote: Hi operators, In Kilo, we added the Catalog Index Service as an experimental API in Glance. It soon became apparent this would be better suited as a separate project, so

Re: [openstack-dev] [glance][api] Response when a illegal body is sent

On 7/23/15, 19:38, michael mccune m...@redhat.com wrote: On 07/23/2015 12:43 PM, Ryan Brown wrote: On 07/23/2015 12:13 PM, Jay Pipes wrote: On 07/23/2015 10:53 AM, Bunting, Niall wrote: Hi, Currently when a body is passed to an API operation that explicitly does not allow bodies Glance

[openstack-dev] [os-ansible-deployment] [openstack-ansible] [Searchlight] Specs for Liberty (v12.0.0)

Hey all, It looks like we've started accepting specifications for Liberty development. Is this accurate? If so, I'd like to start writing one to add Searchlight. Anyone experimenting with Glance's Catalog Index Search in Kilo will want Searchlight in Liberty. Cheers, Ian

Re: [openstack-dev] [glance][api] Response when a illegal body is sent

On 7/24/15, 13:16, Clint Byrum cl...@fewbar.com wrote: Excerpts from Ian Cordasco's message of 2015-07-24 08:58:06 -0700: On 7/23/15, 19:38, michael mccune m...@redhat.com wrote: On 07/23/2015 12:43 PM, Ryan Brown wrote: On 07/23/2015 12:13 PM, Jay Pipes wrote: On 07/23/2015 10:53 AM,

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

On 7/14/15, 10:41, Monty Taylor mord...@inaugust.com wrote: On 07/14/2015 11:08 AM, Ian Cordasco wrote: On 7/13/15, 16:19, Joshua Harlow harlo...@outlook.com wrote: Ian Cordasco wrote: On 7/13/15, 15:09, Dave Walkerem...@daviey.com wrote: On 13 Jul 2015 8:52 pm, Ian

Re: [openstack-dev] [os-ansible-deployment] Core nomination for Matt Kassawara (sam-i-am)

On 7/20/15, 05:16, Jesse Pretorius jesse.pretor...@gmail.com wrote: On 17 July 2015 at 16:14, Kevin Carter kevin.car...@rackspace.com wrote: I would like to nominate Matt Kassawara (IRC: sam-i-am) to the OpenStack Ansible deployment core team. Matt has been instrumental in building out our

[openstack-dev] [os-ansible-deployment] [openstack-ansible] Using commit flags appropriately

Hey everyone, Now that the project is starting to grow and has some amount of documentation. We should really start using flags in our commits more appropriately, e.g., UpgradeImpact, DocImpact, etc. For example, my own recent change to upgrade our keystone module to use v3 should have also had

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

On 7/13/15, 16:19, Joshua Harlow harlo...@outlook.com wrote: Ian Cordasco wrote: On 7/13/15, 15:09, Dave Walkerem...@daviey.com wrote: On 13 Jul 2015 8:52 pm, Ian Cordascoian.corda...@rackspace.com wrote: On 7/13/15, 03:38, Thierry Carrezthie...@openstack.org wrote: SNIP By counter

Re: [openstack-dev] OpenStack Mitaka (三鷹) - Our next release name has been selected

On 7/14/15, 13:47, Monty Taylor mord...@inaugust.com wrote: Hi everybody! Ok. There is nothing more actually useful I can say that isn't in the subject line. As I mentioned previously, the preliminary results from our name election are here:

Re: [openstack-dev] [glance] Additions and removals for the glance-drivers team

On 7/9/15, 13:37, Flavio Percoco fla...@redhat.com wrote: Greetings, I'd like to propose Stuart Mclaren for the glance-drivers team. Stuart has a huge amount of knowledge about Glance's history, he knows the Glance codebase well and he also has experience in deploying and maintaning Glance

Re: [openstack-dev] [glance] The sorry state of our spec process

On 7/3/15, 05:35, Kuvaja, Erno kuv...@hp.com wrote: First of all, Thanks Flavio for bring this open to the daylight! I agree. More of these discussions need to happen on the mailing list. I have been really frustrated about the Glance spec process since the beginning and as glance core tried

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

On 7/13/15, 03:38, Thierry Carrez thie...@openstack.org wrote: Ian Cordasco wrote: On 7/10/15, 03:44, Thierry Carrez thie...@openstack.org wrote: Also you'll find that the various distros use different epoch values for the same software, because epoch are also used to cover local blunders

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

On 7/13/15, 15:09, Dave Walker em...@daviey.com wrote: On 13 Jul 2015 8:52 pm, Ian Cordasco ian.corda...@rackspace.com wrote: On 7/13/15, 03:38, Thierry Carrez thie...@openstack.org wrote: SNIP By counter-productive, I meant: likely to generate more confusion than clarity. If you provide

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

On 7/10/15, 03:44, Thierry Carrez thie...@openstack.org wrote: Joshua Harlow wrote: Hi all, I was thinking about those who are packaging with venvs (and using the version of a project in the venv file name); like what anvil[1] is now capable of (and does this in the gate now[2]) or

Re: [openstack-dev] [testing] moving testrepository *outside* the tox venv

On 7/10/15, 18:34, Monty Taylor mord...@inaugust.com wrote: On 07/10/2015 07:19 PM, Robert Collins wrote: On 10 July 2015 at 01:59, Morgan Fainberg morgan.fainb...@gmail.com wrote: Or a database per python major version (or at least gracefully handle the incompatibility). So that would

Re: [openstack-dev] [kolla][release] Announcing Liberty-1 release of Kolla

and repeatable). Are there places where you've found osad to be not consistent or repeatable? On Tue, Jun 30, 2015 at 2:28 PM, Ian Cordasco ian.corda...@rackspace.com wrote: On 6/29/15, 23:59, Steven Dake (stdake) std...@cisco.com wrote: The Kolla community is pleased to announce the release

Re: [openstack-dev] [all][packaging] Adding files to /etc in a package

On 7/1/15, 09:13, Jeremy Stanley fu...@yuggoth.org wrote: On 2015-07-01 12:08:46 +1000 (+1000), Tony Breeds wrote: Okay so I take you point no problem, but I'm not running distro packages and I still want completions. There must be a way to package the file to at least make it easier to

Re: [openstack-dev] Python 2.6 failed jobs for SQLA-Migrate

On 7/1/15, 09:03, Mike Bayer mba...@redhat.com wrote: On 6/30/15 9:51 PM, Thomas Goirand wrote: Hi, Mike nicely tried to help me to get sqla-migrate to work with sqlalchemy 1.0.6 which is now in Debian. But there's some failures in Python 2.6: https://review.openstack.org/#/c/197144/

Re: [openstack-dev] [kolla][release] Announcing Liberty-1 release of Kolla

30, 2015 at 8:28 PM, Ian Cordasco ian.corda...@rackspace.com wrote: On 6/29/15, 23:59, Steven Dake (stdake) std...@cisco.com wrote: The Kolla community is pleased to announce the release of the Kolla Liberty 1 milestone. This release fixes 56 bugs and implements 14 blueprints! Our community

Re: [openstack-dev] [kolla][release] Announcing Liberty-1 release of Kolla

On 6/29/15, 23:59, Steven Dake (stdake) std...@cisco.com wrote: The Kolla community is pleased to announce the release of the Kolla Liberty 1 milestone. This release fixes 56 bugs and implements 14 blueprints! Our community developed the following notable features: * A start at

Re: [openstack-dev] [api] [all] To changes-since or not to changes-since

On 6/19/15, 14:39, Ian Cordasco ian.corda...@rackspace.com wrote: On 6/19/15, 14:26, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Fri, 2015-06-19 at 10:07 +0100, Chris Dent wrote: * Are there additional relevant pros and cons for the two proposals? * Are there additional

Re: [openstack-dev] [os-ansible-deployment] Core team nomination

Thanks everyone! On 6/19/15, 11:52, Kevin Carter kevin.car...@rackspace.com wrote: Please join me in welcoming Ian Cordasco to the `os-ansible-deployment` core team! ​​ -- Kevin Carter From: Hugh Saunders h...@wherenow.org Sent: Thursday, June 18

Re: [openstack-dev] [api] [all] To changes-since or not to changes-since

On 6/19/15, 14:26, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Fri, 2015-06-19 at 10:07 +0100, Chris Dent wrote: * Are there additional relevant pros and cons for the two proposals? * Are there additional proposals which can address the shortcomings in either? On the latter

Re: [openstack-dev] Debian already using Python 3.5: please gate on that

On 6/18/15, 08:44, Thomas Goirand z...@debian.org wrote: Hi! tl;dr: skip this message, the subject line is enough! :) As per the subject line, we already have Python 3.5 in Debian (AFAICT, from Debian Experimental, in version beta 2). As a consequence, we're already running (unit) tests using

Re: [openstack-dev] [all] setup.py executable bit

On 6/17/15, 13:53, Jeremy Stanley fu...@yuggoth.org wrote: On 2015-06-17 14:47:48 -0400 (-0400), Doug Hellmann wrote: +1 both to using -x and to removing the shebang. Agreed. We don't want anyone directly invoking this file as an executable script in PBR-based packages, so I'm strongly in

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 6/15/15, 09:24, Thomas Goirand z...@debian.org wrote: On 06/08/2015 01:55 PM, Kuvaja, Erno wrote: One thing I like about plan D is that it would give also indicator how much the stable branch has moved in each individual project. The only indication you will get is how many patches it has.

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 6/15/15, 16:24, Thomas Goirand z...@debian.org wrote: On 06/15/2015 05:19 PM, Ian Cordasco wrote: On 6/15/15, 09:24, Thomas Goirand z...@debian.org wrote: On 06/08/2015 01:55 PM, Kuvaja, Erno wrote: One thing I like about plan D is that it would give also indicator how much the stable

Re: [openstack-dev] Looking for help getting git-review to work over https

On 6/12/15, 14:46, KARR, DAVID dk0...@att.com wrote: -Original Message- From: Kevin L. Mitchell [mailto:kevin.mitch...@rackspace.com] Sent: Friday, June 12, 2015 12:05 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Looking for help getting git-review to work

Re: [openstack-dev] Looking for help getting git-review to work over https

/) - What you get when you do `python -c 'import setuptools; print(setuptools.__version__)'` - Output of python -V On 6/12/15, 12:08, KARR, DAVID dk0...@att.com wrote: -Original Message- From: Ian Cordasco [mailto:ian.corda...@rackspace.com] Sent: Friday, June 12, 2015 9:57 AM To: OpenStack

Re: [openstack-dev] Looking for help getting git-review to work over https

Python has generally awful support for doing HTTPS over an HTTPS proxy. Can you try doing: # pip install --proxy http://one.proxy.att.com:appropriate-port Cheers, Ian On 6/12/15, 10:26, KARR, DAVID dk0...@att.com wrote: As I apparently have to sudo this, it would likely be more effective, if

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

On 6/10/15, 09:12, Thomas Goirand z...@debian.org wrote: On 06/10/2015 12:25 PM, Dave Walker wrote: The initial core reviewers was seeded by representatives of distro's and vendors to get their input on viability in distro's. Really? James, were you made core on the requirements? I once

Re: [openstack-dev] [all] Switching to SQLAlchemy 1.0.x

I think it would first require a version of oslo.db to be released inside stable/kilo's bounds that uncapped SQLAlchemy first since the requirement in the version of oslo.db installed is what you see here http://logs.openstack.org/62/190062/2/check/check-tempest-dsvm-neutron-full

Re: [openstack-dev] [Security] [Bandit] Using multiprocessing/threading to speed up analysis

On 6/8/15, 12:17, Finnigan, Jamie jamie.finni...@hp.com wrote: On 6/8/15, 8:26 AM, Ian Cordasco ian.corda...@rackspace.com wrote: Hey everyone, I drew up a blueprint (https://blueprints.launchpad.net/bandit/+spec/use-threading-when-running - c hecks) to add the ability to use multiprocessing

Re: [openstack-dev] [Security] [Bandit] Using multiprocessing/threading to speed up analysis

to make a few options mutually exclusive. For example, if you use pep8's diff capabilities then multiprocessing is turned off by default. It's unlikely that you'll need it either. -Rob On 08/06/2015 08:26, Ian Cordasco ian.corda...@rackspace.com wrote: Hey everyone, I drew up a blueprint (https

[openstack-dev] [Security] [Bandit] Using multiprocessing/threading to speed up analysis

Hey everyone, I drew up a blueprint (https://blueprints.launchpad.net/bandit/+spec/use-threading-when-running-c hecks) to add the ability to use multiprocessing (or threading) to Bandit. This essentially means that each thread will be fed a file and analyze it and return the results. (A file will

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 6/7/15, 03:41, Thomas Goirand z...@debian.org wrote: On 05/29/2015 09:23 PM, Ian Cordasco wrote: Could you explain this as well? Do you mean fragmentation between what distros are offering? In other words, Ubuntu is packaging Kilo @ SHA1 and RHEL is at SHA2. I'm not entirely certain that's

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 6/7/15, 03:47, Thomas Goirand z...@debian.org wrote: On 05/29/2015 09:36 PM, Dave Walker wrote: Responses inline. On 29 May 2015 6:15 pm, Haïkel hgue...@fedoraproject.org mailto:hgue...@fedoraproject.org wrote: 2015-05-29 15:41 GMT+02:00 Thierry Carrez thie...@openstack.org

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 6/6/15, 02:03, Alan Pevec ape...@gmail.com wrote: 2015-06-05 15:16 GMT+02:00 Jeremy Stanley fu...@yuggoth.org: On 2015-06-05 14:56:30 +0200 (+0200), Thierry Carrez wrote: [...] I was wondering if we could switch to post-versioning on stable branches, and basically generate:

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

On 6/2/15, 16:24, Boris Pavlovic bo...@pavlovic.me wrote: Hi stackers, Issue --- Projects are becoming bigger and bigger overtime. More and more people would like to contribute code and usually core reviewers team can't scale enough. It's very hard to find people that understand full

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

On 6/2/15, 04:45, Boris Bobrov bbob...@mirantis.com wrote: On Tuesday 02 June 2015 09:32:45 Chenhong Liu wrote: There is keystone/exception.py which contains Exceptions defined and used inside keystone provide 4xx and 5xx status code. And we can use it like: exception.Forbidden.code,

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 6/1/15, 06:20, Dimitri John Ledkov dimitri.j.led...@intel.com wrote: On 29 May 2015 at 14:41, Thierry Carrez thie...@openstack.org wrote: Hi everyone, TL;DR: - We propose to stop tagging coordinated point releases (like 2015.1.1) - We continue maintaining stable branches as a trusted

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 5/29/15, 12:14, Haïkel hgue...@fedoraproject.org wrote: 2015-05-29 15:41 GMT+02:00 Thierry Carrez thie...@openstack.org: Hi everyone, TL;DR: - We propose to stop tagging coordinated point releases (like 2015.1.1) - We continue maintaining stable branches as a trusted source of stable

Re: [openstack-dev] Nominating Serge van Ginderachter to the os-ansible-deployment core team

On 5/28/15, 18:01, Kevin Carter kevin.car...@rackspace.com wrote: Hello, I would like to nominate Serge (svg on IRC) for the os-ansible-deployment-core team. Serge has been involved with the greater Ansible community for some time and has been working with the OSAD project for the last couple of

Re: [openstack-dev] [all] cross project communication: Return request-id to caller

On 5/27/15, 10:15, Doug Hellmann d...@doughellmann.com wrote: Excerpts from Kekane, Abhishek's message of 2015-05-27 07:06:56 +: Hi Devs, Each OpenStack service sends a request ID header with HTTP responses. This request ID can be useful for tracking down problems in the logs. However,

Re: [openstack-dev] [heat][python-heatclient] Does python-heatclient works with keystone sessions?

On 5/7/15, 14:43, Jay Reslock jresl...@gmail.com wrote: Hi, This is my first mail to the group. I hope I set the subject correctly and that this hasn't been asked already. I searched archives and did not see this question asked or answered previously. I am working on a client thing that

Re: [openstack-dev] [PKG-Openstack-devel][horizon][xstatic] XStatic-Angular-Bootstrap in violation of the MIT/Expat license (forwarded from: python-xstatic-angular-bootstrap_0.11.0.2-1_amd64.changes R

On 5/3/15, 11:46, Thomas Goirand z...@debian.org wrote: Hi, According to Paul Tagliamonte, who is from the Debian FTP master team (which peer-reviews NEW packages in Debian before they reach the archive) python-xstatic-angular-bootstrap cannot be uploaded as-is to Debian because it doesn't

Re: [openstack-dev] [PKG-Openstack-devel][horizon][xstatic] XStatic-Angular-Bootstrap in violation of the MIT/Expat license (forwarded from: python-xstatic-angular-bootstrap_0.11.0.2-1_amd64.changes R

On 5/4/15, 18:13, Thomas Goirand z...@debian.org wrote: On 05/05/2015 12:15 AM, Ian Cordasco wrote: For what it’s worth Thomas and Maxime, removing the old versions from PyPI is likely to be a bad idea. Probably, but it's legally wrong (ie: worst case, you can be sued) to leave a package which

<    1   2   3   4   >