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

after RC WAS Re: How do I calculate the semantic version prior to a release? > On 24 March 2016 at 10:36, Ian Cordasco wrote: > > > > > > > The project will build wheels first. The wheels generated tend to look > > something like > 13.0.0.0rc2.dev10 when they&#x

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

  -Original Message- From: Monty Taylor Reply: Monty Taylor Date: March 23, 2016 at 16:52:52 To: Ian Cordasco , OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [magnum] Streamline adoption of Magnum > On 03/23/2016 04:45 PM, Ian Corda

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

oblem 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 to deploy the services - Magnum should support a variety of servi

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

.0.0rc2.dev10 when they're built because of pbr. If someone is doing CD with the openstack-ansible project and they deploy mitaka once it has a final tag, then they decide to upgrade to run master, they could run into problems upgrading. That

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

unk and does periodic upgrades from the latest stable branch to whatever is running on master. Further they're using pip and this will absolutely cause headaches upgrading that. -- Ian Cordasco __ OpenStack Developme

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

> 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 satisfied. > I am going to send another ML to describ

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

d 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/Security/Projects/Anchor,  https://git.opensta

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

s for the > discussion. Unrelatedly, the author hasn't responded to either email or twitter. I've offered to help keep it on life support but they've not responded. So perhaps they're not interested in adding maintainers after all. Either way, it's likely

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

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 deploy Barbican. -- Ian Cordasco __

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

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 > > recommendation is to use something that is not httplib2 eventually. > > Not every library ne

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

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? > >> How much work do cores think it would be to remove this from our > >> global requirements?" >

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

-Original Message- From: Sean Dague Reply: OpenStack Development Mailing List (not for usage questions) Date: March 14, 2016 at 09:41:02 To: openstack-dev@lists.openstack.org Subject:  Re: [openstack-dev] [all] Maintaining httplib2 python library > On 03/14/2016 10:24 AM, Ian Corda

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

think it would be to remove this from our global requirements?" -- Ian Cordasco __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib

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

ier today and some versions of the cirros image attempt to generate a random number which can cause it to hang. > Besides, could someone tell me the history of the image name "cirros"? I suspect someone who actually works on the Cir

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

inue 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 better. -- Ian Cordasco __ 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] [api][all] api variation release by release

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 > > You can consult the docs to see what that specific version gives yo

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

-Original Message- From: Mike Perez Reply: Mike Perez Date: February 22, 2016 at 11:51:39 To: Ian Cordasco , OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [all] [tc] "No Open Core" in 2016 > On 02/22/2016 07:19 AM, Ian C

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

I would not be satisfied with > us giving up on having functional or integration tests from a project > because of the available implementations. It's reasons like this that > highlight Poppy being different from the rest of OpenStack. Would third

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

#x27;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 to support that would necessitate that. -- Ian Cordasco Glance Core Reviewer ___

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

y be wrong ;-) ) that in chapter 3 of the > "install guide: configuring > the network on target host", you propose the /etc/network/interfaces for both > controller > node (br-vxlan, br-storage: manual without IP) and compute node (br-vxlan, > br-storage:

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

e-create without passing it any image data. You should then be able to use location-add and I believe Glance will download the image itself in that case. Cheers, -- Ian Cordasco __ OpenStack Development Mailing List (not f

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

drivers) I think we have to also recognize a difference in the problem domains. Presently, I think we need a F/OSS CDN but it isn't going to happen until the infrastructure for a CDN is something any OpenStack consumer would want to

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" wrote: > > On 02/16/2016 11:48 AM, Ian Cordasco wrote: > > > > > > -Original Message- > > From: Matt Riedemann > > Reply: Matt Riedemann > > Date: February 16, 2016 at 09:30:49 > > To: O

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

k/specificity. I also think this clearly demonstrates why upper caps (although painful) are at least informational even when we have upper-constraints protecting the gates. -- Ian Cordasco __ OpenStack Development Ma

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 was updated in the > > 7230-7235 RFCs. (...) > > Where VCHAR is any visible US ASCII characte

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 that makes Nova fully >

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

On Fri, Feb 12, 2016 at 5:13 AM, Victor Stinner wrote: > Change 237027: For the encoding of HTTP headers, it looks like Swift doesn't > respect HTTP RFCs. The HTTP requires headers to be encoded to Latin1, but > Swift (server or client, sorry I don't know) encode headers to UTF-8. > Something shou

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

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 > > "stabilization cycles". We, as a community, are not using minor version > > numbers. During a stab

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

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 they'll rejoin us. I'd also be glad to welcome Kairat and Brian. (+2 to the entire email) -- Ian Cordasco __ 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] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

ld 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 to package and to be far more aware of each project's current development cycle. I'm not sure that's positive. -- Ian Cordasco __ 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] [API] [Glance] New v2 Image Import Specification Discussion

-Original Message- From: Ian Cordasco Reply: OpenStack Development Mailing List (not for usage questions) Date: January 8, 2016 at 11:16:35 To: OpenStack Development Mailing List (not for usage questions) Subject:  [openstack-dev] [API] [Glance] New v2 Image Import Specification

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

quota. This still doesn't discuss giving admin more visibility (in a direct upload case) about quota of uploaded but not yet processed data. That's an important question to have, but I don't have an easy answer for it though.

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

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. Thanks for babysitting those Matt!  -- Ian Cordasco __ OpenStac

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

match the actual > API. I agree. It's very easy for servers intending to mimic APIs and their behaviour to fall out of synchronization with the server they're attempting to mimic. -- Ian Cordasco __ OpenStac

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 like to include this property

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 - https://mail.python.org/pipermail/web-sig/2016-January/005357

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. >> So I was thinking altern

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 >>Catalog >> nam

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 Glance API and >will be ru

Re: [openstack-dev] [all][glance] Add Sabari Kumar Murugesan

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 >related to the design of t

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 specify a group for the >mapping

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 folks, > > >Thanks for the f

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 Recen

[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 tran

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 "Proposal" section o

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

mited activity in Kilo and absent in Liberty) Sad to see Zhi Yan Liu's activity drop off. > Please vote +1 or -1 and we will decide by Monday EOD PT. +1 -- Ian Cordasco __ OpenStack Development Mailing List (not fo

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 Mirantis, Inc. > >http://mi

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

On 8/25/15, 10:58, "Clay Gerrard" wrote: > > >On Tue, Aug 25, 2015 at 8:45 AM, Kevin L. Mitchell > 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 import *more* that one thing on a line (

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" 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 example config

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

On 8/7/15, 07:19, "Nicolas Trangez" 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 RING, >currently ou

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

On 8/5/15, 08:14, "McPeak, Travis" 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 developer/gate wa

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

On 8/4/15, 13:17, "Clark, Robert Graham" 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 is a very

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

On 8/3/15, 11:11, "Thierry Carrez" 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 increments .

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

On 7/31/15, 07:40, "Jesse Pretorius" 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 version be? Would the

[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 repo

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

On 7/29/15, 13:27, "William M Edmonds" wrote: > >> From: Doug Hellmann >> To: openstack-dev >> Date: 07/28/2015 07:59 PM >> Subject: Re: [openstack-dev] [glance] Removing python-swiftclient > >> from requirements.txt >> > > > >> I replied on both patches, but I'll repeat it here for a broade

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

On 7/27/15, 11:29, "Louis Taylor" 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 >> i

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

On 7/14/15, 10:41, "Monty Taylor" wrote: >On 07/14/2015 11:08 AM, Ian Cordasco wrote: >> >> >> On 7/13/15, 16:19, "Joshua Harlow" wrote: >> >>> Ian Cordasco wrote: >>>> >>>> On 7/13/15, 15:09, "Dave Walke

[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" wrote: >Excerpts from Ian Cordasco's message of 2015-07-24 08:58:06 -0700: >> >> On 7/23/15, 19:38, "michael mccune" 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,

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

On 7/23/15, 19:38, "michael mccune" 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 G

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

On 7/20/15, 05:16, "Jesse Pretorius" wrote: >On 17 July 2015 at 16:14, Kevin Carter 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 current install and use documentation[0], he i

[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 h

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

On 7/14/15, 13:47, "Monty Taylor" 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: > >http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8d

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

On 7/13/15, 16:19, "Joshua Harlow" wrote: >Ian Cordasco wrote: >> >> On 7/13/15, 15:09, "Dave Walker" wrote: >> >>> On 13 Jul 2015 8:52 pm, "Ian Cordasco" >>>wrote: >>>> On 7/13/15, 03:38, "Thierry Carrez&q

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

On 7/13/15, 15:09, "Dave Walker" wrote: > >On 13 Jul 2015 8:52 pm, "Ian Cordasco" wrote: >> On 7/13/15, 03:38, "Thierry Carrez" wrote: > >> >By "counter-productive", I meant: likely to generate more confusion >>than &g

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

On 7/13/15, 03:38, "Thierry Carrez" wrote: >Ian Cordasco wrote: >> On 7/10/15, 03:44, "Thierry Carrez" wrote: >>> Also you'll find that the various distros use different epoch values >>>for >>> the same software, because epo

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

On 7/3/15, 05:35, "Kuvaja, Erno" 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 to work a

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

On 7/9/15, 13:37, "Flavio Percoco" 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 production en

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

On 7/10/15, 03:44, "Thierry Carrez" 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 packaging via r

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

On 7/10/15, 18:34, "Monty Taylor" wrote: >On 07/10/2015 07:19 PM, Robert Collins wrote: >> On 10 July 2015 at 01:59, Morgan Fainberg >>wrote: >>> Or a database per python major version (or at least gracefully handle >>>the incompatibility). >> >> So that would partition the data, and the whole

Re: [openstack-dev] [glance] Progress of the Python 3 port

On 7/9/15, 06:25, "Victor Stinner" wrote: >Hi, > >gate-glance-python34 is now voting! > >Ian Cordasco and Erno Kuvaja approved my two last patches to port >glance_store to Python 3: thanks. "tox -e py34" now pass successfully, >cool! I proposed a &qu

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

On 7/9/15, 01:34, "Flavio Percoco" wrote: >On 08/07/15 22:52 +, Jeremy Stanley wrote: >>On 2015-07-09 10:37:17 +1200 (+1200), Robert Collins wrote: >>> So - I'm looking to: >>> >>> A) have a discussion and identify any issues with moving testr out of >>> the venvs. (Note: this doesn't mean

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

On 7/1/15, 09:13, "Jeremy Stanley" 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 achieve both

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

On 7/1/15, 09:03, "Mike Bayer" 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

of wheels (e.g., consistent 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 > wrote: > > > >On 6/29/15, 23:59, "Steven Dake (stdake)" wrote: > >>The Kolla community

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

aniel, I missed that. > >On Tue, Jun 30, 2015 at 8:28 PM, Ian Cordasco > wrote: > > > >On 6/29/15, 23:59, "Steven Dake (stdake)" wrote: > >>The Kolla community >>is pleased to announce the >> release of the >> Kolla Liberty 1 milestone. T

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

On 6/29/15, 23:59, "Steven Dake (stdake)" 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 >source-ba

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

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

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

On 6/19/15, 14:26, "Kevin L. Mitchell" 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 question, would us

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

Thanks everyone! On 6/19/15, 11:52, "Kevin Carter" wrote: >Please join me in welcoming Ian Cordasco to the `os-ansible-deployment` >core team! > >​​ >-- > >Kevin Carter > > > > > > > > >From:

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

On 6/18/15, 08:44, "Thomas Goirand" 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 Python

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

On 6/17/15, 13:53, "Jeremy Stanley" 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 favor of >any

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

On 6/15/15, 16:24, "Thomas Goirand" wrote: >On 06/15/2015 05:19 PM, Ian Cordasco wrote: >> On 6/15/15, 09:24, "Thomas Goirand" wrote: >> >>> On 06/08/2015 01:55 PM, Kuvaja, Erno wrote: >>>> One thing I like about plan D >>>>

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

On 6/15/15, 09:24, "Thomas Goirand" 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. I

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

On 6/12/15, 14:46, "KARR, DAVID" 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

ll be in ~/.pip/) - 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" wrote: >> -Original Message- >> From: Ian Cordasco [mailto:ian.corda...@rackspace.com] >>

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: Cheers, Ian On 6/12/15, 10:26, "KARR, DAVID" wrote: >As I apparently have to sudo this, it would likely be more effective, if >at all, to specify the proxy

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 /f6baf92/logs/devs

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

On 6/10/15, 09:12, "Thomas Goirand" 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 tried to

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

On 6/8/15, 12:17, "Finnigan, Jamie" wrote: >On 6/8/15, 8:26 AM, "Ian Cordasco" wrote: > >>Hey everyone, >> >>I drew up a blueprint >>(https://blueprints.launchpad.net/bandit/+spec/use-threading-when-running >>- >>c >>hecks)

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

how they work. Flake8 did have 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" wrote

[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 wil

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

On 6/7/15, 03:47, "Thomas Goirand" wrote: >On 05/29/2015 09:36 PM, Dave Walker wrote: >> Responses inline. >> >> On 29 May 2015 6:15 pm, "Haïkel" > > wrote: >>> >>> 2015-05-29 15:41 GMT+02:00 Thierry Carrez > >: >>> > Hi everyone,

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

On 6/7/15, 03:41, "Thomas Goirand" 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 SH

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

On 6/6/15, 02:03, "Alan Pevec" wrote: >2015-06-05 15:16 GMT+02:00 Jeremy Stanley : >> 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: >>> >>> "2015.1.0.post38" >> [...]

Re: [openstack-dev] [nova] [glance] How to deal with aborted image read?

On 6/5/15, 02:55, "Flavio Percoco" wrote: >On 04/06/15 11:46 -0600, Chris Friesen wrote: >>On 06/04/2015 03:01 AM, Flavio Percoco wrote: >>>On 03/06/15 16:46 -0600, Chris Friesen wrote: We recently ran into an issue where nova couldn't write an image file due to lack of space and so

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

On 6/2/15, 16:24, "Boris Pavlovic" 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 proje

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" 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, exception.for

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

On 6/1/15, 06:20, "Dimitri John Ledkov" wrote: >On 29 May 2015 at 14:41, Thierry Carrez 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 source of stable >> updates for all p

<    1   2   3   4   >