Re: [openstack-dev] Team blogs

On 05/09/2016 05:45 PM, Robert Collins wrote: > IIRC mediawiki provides RSS of changes... maybe just using the wiki > more would be a good start, and have zero infra costs? We'd actually like to start using the wiki less, per the most recent summit. Also, the wiki currently has new accounts turned

Re: [openstack-dev] Making changes to gerrit's presentation

On 05/10/2016 06:32 AM, Chris Dent wrote: > On Tue, 10 May 2016, Sean Dague wrote: > >> Gerrit's is a GWT app, which means the entire thing is Java which >> compiles to HTML/JS, for anything deep, you have to dive down that >> rabbit hole. > > Thanks for the response, this is pretty much what I f

Re: [openstack-dev] [fuel] [QA] running Fuel tests using nodepool

On 05/10/2016 08:54 AM, Vladimir Eremin wrote: > Hi, > > I've investigated status of nodepool multi node testing and fuel-qa > approaches, and I wanna share my opinion on moving Fuel testing on > OpenStack and nodepool. Awesome! This is a great writeup - and hopefully will be useful as we validat

Re: [openstack-dev] Ansible inventory - Would you need another inventory system for your openstack cloud and how would you like it to be?

On 05/12/2016 12:25 PM, Sean M. Collins wrote: > Monty Taylor wrote: >> On 05/09/2016 09:27 AM, Jean-Philippe Evrard wrote: >>> Hello everyone, >>> >>> I am using ansible for some time now, and I think the current default >>> Ansible inventory sy

[openstack-dev] Naming Polls for N and O are open

Hey everybody! The naming polls for N and O have started. You should have received an email for each of them. They'll be open until the end of Dec 22 UTC. Once there are presumptive winners in each, please remember that we will then have the names vetted by the OpenStack Foundation's lawyers,

Re: [openstack-dev] [all] Proposal: copyright-holders file in each project, or copyright holding forced to the OpenStack Foundation

On 01/15/2016 10:28 AM, Daniel P. Berrange wrote: On Fri, Jan 15, 2016 at 12:53:49PM +, Chris Dent wrote: On Fri, 15 Jan 2016, Thomas Goirand wrote: Whatever we choose, I think we should ban having copyright holding text within our source code. While licensing is a good idea, as it is accu

Re: [openstack-dev] [all] Proposal: copyright-holders file in each project, or copyright holding forced to the OpenStack Foundation

On 01/15/2016 10:38 AM, Daniel P. Berrange wrote: On Fri, Jan 15, 2016 at 08:48:21PM +0800, Thomas Goirand wrote: This isn't the first time I'm calling for it. Let's hope this time, I'll be heard. Randomly, contributors put their company names into source code. When they do, then effectively, t

[openstack-dev] All hail Newton and Ocata

If you couldn't tell from the subject line, we've gotten clearance from our friends on the Foundation staff and their legal team to be able to announce the names of the N and O cycles. The N release will be called "Newton" Newton was the overall winner of the Condorcet poll. While you might be

[openstack-dev] Use of restricted and multiverse in the gate

Hey all, We're working on getting per-region APT mirrors stood up for the nodepool nodes to use in the gate. As part of working on this, it struck me that we currently have restricted and multiverse enabled in our sources.list file. I ran a quick test of removing both of them on a devstack-g

Re: [openstack-dev] [all] Proposal for having a service type registry and curated OpenStack REST API

On 02/07/2016 07:30 AM, Jay Pipes wrote: On 02/04/2016 06:38 AM, Sean Dague wrote: What options do we have? 2) Have a registry of "common" names. Upside, we can safely use common names everywhere and not fear collision down the road. Downside, yet another contention point. A registry would

Re: [openstack-dev] Use of restricted and multiverse in the gate

On 02/07/2016 12:56 PM, Jim Meyer wrote: On Feb 7, 2016, at 6:11 AM, Monty Taylor wrote: Hey all, We're working on getting per-region APT mirrors stood up for the nodepool nodes to use in the gate. As part of working on this, it struck me that we currently have restricted and multi

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/07/2016 02:07 PM, Jay Pipes wrote: Hello all, tl;dr = I have long thought that the OpenStack Summits have become too commercial and provide little value to the software engineers contributing to OpenStack. I propose the following: 1) Separate the design summits from the conferences

Re: [openstack-dev] [all] Proposal for having a service type registry and curated OpenStack REST API

On 02/08/2016 06:16 AM, Sean Dague wrote: On 02/07/2016 08:13 PM, Monty Taylor wrote: On 02/07/2016 07:30 AM, Jay Pipes wrote: On 02/04/2016 06:38 AM, Sean Dague wrote: What options do we have? 2) Have a registry of "common" names. Upside, we can safely use common names everywhe

Re: [openstack-dev] [Neutron] Being more aggressive with our defaults

On 02/08/2016 09:47 AM, Sean M. Collins wrote: Hi, With the path_mtu issue - our default was to set path_mtu to zero, and do no calculation against the physical segment MTU and the overhead for the tunneling protocol that was selected for a tenant network. Which means the network would break. I

Re: [openstack-dev] [all][infra] eventlet 0.18.1 not on PyPi anymore

On 02/09/2016 12:24 PM, McLellan, Steven wrote: From the list of versions that are there (https://pypi.python.org/simple/eventlet/), it appears that for a given major version only the most recent release is kept, so this will likely reoccur when/if 0.18.3 is released. Anybody know anybody in e

[openstack-dev] All hail the new per-region pypi, wheel and apt mirrors

Hey everybody, tl;dr - We have new AFS-based consistent per-region mirrors of PyPI and APT repos with additional wheel repos containing pre-built wheels for all the modules in global-requirements We've just rolled out a new change that you should mostly never notice - except that jobs should

[openstack-dev] OpenStack Meiji (明治) - Our next release name has been selected

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_4983776e190c8dbc As a follow on step, the OpenStack Foundation

Re: [openstack-dev] Build dependency loop: python-os-client-config and python-oslotest

On 07/07/2015 03:00 PM, Doug Hellmann wrote: > Excerpts from Steve Martinelli's message of 2015-07-07 14:51:33 -0400: >> >> Direct dependency for functional testing: >> https://github.com/openstack/oslotest/blob/6bd1f64542d5826cef288b43210650b50ba02ca3/oslotest/functional.py#L16 > > It looks like

Re: [openstack-dev] Build dependency loop: python-os-client-config and python-oslotest

On 07/07/2015 03:42 PM, Monty Taylor wrote: > On 07/07/2015 03:00 PM, Doug Hellmann wrote: >> Excerpts from Steve Martinelli's message of 2015-07-07 14:51:33 -0400: >>> >>> Direct dependency for functional testing: >>> h

Re: [openstack-dev] [openstack-community] OpenStack Meiji (明治) - Our next release name has been selected

ion 13. We already use semver. This is not a realistic solution to anything. > > Cheers > > Tristan > > > > > > *From:* Jaesuk Ahn [mailto:bluejay@gmail.com] > *Sent:* Wednesday, 8 July 2015 2:41 PM > *To:* OpenStack Development Mailing List; Openstack Us

[openstack-dev] Rescinding the M name decision

Hi everyone! In light of issues raised concerning the initially selected name for the M release (Meiji), that name will not be used. It turns out fully open community and fully inclusive collaboration is a hard thing to get right. On the one hand, we do not want to exclude anyone's input or contr

Re: [openstack-dev] [requirements] attention requirements-cores, please look out for constraints updates

On 07/08/2015 03:49 PM, Robert Collins wrote: > On 8 July 2015 at 21:01, Thierry Carrez wrote: >> Robert Collins wrote: >>> We've finally gotten all the kinks worked out and now >>> upper-constraints proposals should be coming in daily. >>> >>> *** These are timely and important: without them, no

[openstack-dev] [sdks] Nominating Ghe Rivero for os-client-config-core

Hey all! Ghe has been doing a great job both in writing patches and reviewing for os-client-config and I'd like to add him to the core team. He's got a good handle on what we're doing, and more importantly what we're not doing. Monty __

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

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 point of test > *repository* is that it builds a

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

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 Walker" wrote: >>> On 13 Jul 2015 8:52 pm, "Ian Cordasco" wrote: > On 7/13/15, 03:38, "Thierry Carrez" wrote: >> By "co

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

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_4983776e190c8dbc As you are all probably aware by now, as a fol

Re: [openstack-dev] OPENSTACK with CEPH storage backend cant down size an instance

On 07/24/2015 12:47 PM, Clint Byrum wrote: > Excerpts from James Galvin's message of 2015-07-24 09:08:36 -0700: >> Hi All >> >> I am having some trouble with down sizing an instance, >> >> I can resize the instance from say small flavour to medium flavour but when >> trying to resize the instance

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On 08/01/2015 03:40 AM, Mike Perez wrote: > On Fri, Jul 31, 2015 at 8:56 AM, Joshua Harlow wrote: >> ...random thought here, skip as needed... in all honesty orchestration >> solutions like mesos >> (http://mesos.apache.org/assets/img/documentation/architecture3.jpg), >> map-reduce solutions like

Re: [openstack-dev] [Neutron] netaddr and abbreviated CIDR format

On 08/21/2015 03:33 PM, Jay Pipes wrote: > On 08/21/2015 02:34 PM, Sean M. Collins wrote: >> So - the tl;dr is that I don't think that we should accept inputs like >> the following: >> >> x -> 192 >> x/y -> 10/8 >> x.x/y -> 192.168/16 >> x.x.x/y -> 192.168.0/24 >> >> which are equivalen

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

On 08/28/2015 07:36 AM, Lucas Alvares Gomes wrote: Hi, If you just want to shoot the breeze please respond here. If you have specific comments on the spec please response there. I have been thinking about doing it for Ironic as well so I'm looking for options. IMHO after using WSME I would t

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

On 08/28/2015 08:32 AM, Julien Danjou wrote: On Fri, Aug 28 2015, Chris Dent wrote: This morning I kicked off a quick spec for replacing WSME in Ceilometer with ... something: https://review.openstack.org/#/c/218155/ This is because not only is WSME not that great, it also results in con

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

On 08/28/2015 08:32 AM, Julien Danjou wrote: On Fri, Aug 28 2015, Chris Dent wrote: This morning I kicked off a quick spec for replacing WSME in Ceilometer with ... something: https://review.openstack.org/#/c/218155/ This is because not only is WSME not that great, it also results in con

[openstack-dev] This is what disabled-by-policy should look like to the user

mordred@camelot:~$ neutron net-create test-net-mt Policy doesn't allow create_network to be performed. Thank you neutron. Excellent job. Here's what that looks like at the REST layer: DEBUG: keystoneclient.session RESP: [403] date: Fri, 04 Sep 2015 13:55:47 GMT connection: close content-type:

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

On 09/04/2015 10:55 AM, Morgan Fainberg wrote: On Sep 4, 2015, at 07:04, Monty Taylor wrote: mordred@camelot:~$ neutron net-create test-net-mt Policy doesn't allow create_network to be performed. Thank you neutron. Excellent job. Here's what that looks like at the REST lay

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

On 09/04/2015 01:42 PM, John Griffith wrote: On Fri, Sep 4, 2015 at 11:35 AM, Mathieu Gagné wrote: On 2015-09-04 12:50 PM, Monty Taylor wrote: On 09/04/2015 10:55 AM, Morgan Fainberg wrote: Obviously the translation of errors would be more difficult if the enforcer is generating messages

Re: [openstack-dev] OpenStack support for Amazon Concepts - was Re: cloud-init IPv6 support

On 09/05/2015 06:19 PM, Sean M. Collins wrote: On Fri, Sep 04, 2015 at 04:20:23PM EDT, Kevin Benton wrote: Right, it depends on your perspective of who 'owns' the API. Is it cloud-init or EC2? At this point I would argue that cloud-init is in control because it would be a large undertaking to s

Re: [openstack-dev] [glance] proposed priorities for Mitaka

On 09/14/2015 02:41 PM, Flavio Percoco wrote: On 14/09/15 08:10 -0400, Doug Hellmann wrote: After having some conversations with folks at the Ops Midcycle a few weeks ago, and observing some of the more recent email threads related to glance, glance-store, the client, and the API, I spent last

Re: [openstack-dev] [glance] tasks (following "proposed priorities for Mitaka")

On 09/14/2015 04:58 PM, Brian Rosmaita wrote: Apologies for forking the thread, but there was way too much in Doug's email (and Flavio's response) and I only want to make a few points about tasks. Please read Doug's original email and Flavio's reply at some point, preferably before you read this

Re: [openstack-dev] [glance] proposed priorities for Mitaka

On 09/15/2015 02:06 AM, Clint Byrum wrote: Excerpts from Doug Hellmann's message of 2015-09-14 13:46:16 -0700: Excerpts from Clint Byrum's message of 2015-09-14 13:25:43 -0700: Excerpts from Doug Hellmann's message of 2015-09-14 12:51:24 -0700: Excerpts from Flavio Percoco's message of 2015-09

[openstack-dev] [glance] The current state of glance v2 in public clouds

Hi! In some of our other discussions, there have been musings such as "people want to..." or "people are concerned about..." Those are vague and unsubstantiated. Instead of "people" - I thought I'd enumerate actual data that I have personally empirically gathered. I currently have an account

[openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

Hey all! If any of you have ever gotten drunk with me, you'll know I hate floating IPs more than I hate being stabbed in the face with a very angry fish. However, that doesn't really matter. What should matter is "what is the most sane thing we can do for our users" As you might have seen

Re: [openstack-dev] [glance] proposed priorities for Mitaka

On 09/15/2015 03:13 PM, stuart.mcla...@hp.com wrote: After having some conversations with folks at the Ops Midcycle a few weeks ago, and observing some of the more recent email threads related to glance, glance-store, the client, and the API, I spent last week contacting a few of you individuall

Re: [openstack-dev] [glance] proposed priorities for Mitaka

On 09/15/2015 07:09 PM, stuart.mcla...@hp.com wrote: I've been looking into the existing task-based-upload that Doug mentions: can anyone clarify the following? On a default devstack install you can do this 'task' call: http://paste.openstack.org/show/462919 Yup. That's the one. as an alter

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On 09/15/2015 06:16 PM, Armando M. wrote: On 15 September 2015 at 08:27, Mike Spreitzer mailto:mspre...@us.ibm.com>> wrote: Monty Taylor mailto:mord...@inaugust.com>> wrote on 09/15/2015 11:04:07 AM: > a) an update to python-novaclient to allow a named netwo

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On 09/15/2015 06:30 PM, Armando M. wrote: On 15 September 2015 at 08:04, Monty Taylor mailto:mord...@inaugust.com>> wrote: Hey all! If any of you have ever gotten drunk with me, you'll know I hate floating IPs more than I hate being stabbed in the face with a very

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On 09/15/2015 08:28 PM, Matt Riedemann wrote: On 9/15/2015 10:27 AM, Mike Spreitzer wrote: Monty Taylor wrote on 09/15/2015 11:04:07 AM: > a) an update to python-novaclient to allow a named network to be passed > to satisfy the "you have more than one network" - the

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

ne is entitled to his/her opinion, but I don't honestly believe these are fair statements to make. The original statement by Monty Taylor is clear to me: I wish to boot an instance that is on a public network and reachable without madness. As of today, you can't unle

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On 09/17/2015 04:50 PM, Anita Kuno wrote: On 09/17/2015 08:22 AM, Matt Riedemann wrote: On 9/17/2015 8:25 AM, Tristan Cacqueray wrote: PTL Nomination is now over. The official candidate list is available on the wiki[0]. There are 5 projects without candidates, so according to this resolution

Re: [openstack-dev] [releases][requirements][keystone]something incompatible with our requirements

On 09/18/2015 03:32 PM, Robert Collins wrote: I know this is terrible timing with the release and all, but constraints updates are failing. This is the first evidence - and it doesn't look like a race to me: http://logs.openstack.org/57/221157/10/check/gate-tempest-dsvm-full/18eb440/logs/devstack

Re: [openstack-dev] [releases][requirements][keystone]something incompatible with our requirements

On 09/18/2015 04:29 PM, Robert Collins wrote: On 19 September 2015 at 08:03, Doug Hellmann wrote: Excerpts from Robert Collins's message of 2015-09-19 07:32:18 +1200: I know this is terrible timing with the release and all, but constraints updates are failing. This is the first evidence - and

Re: [openstack-dev] openstack-dahboard directory is not created

On 09/18/2015 02:03 PM, OpenStack Mailing List Archive wrote: Link: https://openstack.nimeyo.com/59453/?show=59453#q59453 From: vidya I am trying to create openstack -dashboard on my VM and /usr/share/openstack-dashboard in not create. Please help me what i am missing here. here is what i trie

[openstack-dev] Patches coming for .coveragerc

Hey all! Coverage released a 4.0 today (yay!) which changes how the config file is read. As a result, "ignore-errors" in the .coveragerc file needs to be ignore_errors. We're running a script right now to submit a change to every project with this change. The topic will be coverage-v4 Enjo

Re: [openstack-dev] [Heat] Assumptions regarding extensions to OpenStack api's

On 09/25/2015 02:32 PM, Pratik Mallya wrote: Hello Heat Team, I was wondering if OpenStack Heat assumes that the Nova extensions api would always exist in a cloud? My impression was that since these features are extensions, they may or may not be implemented by the cloud provider and hence Heat

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On 09/25/2015 06:37 PM, Chris Hoge wrote: On Sep 25, 2015, at 10:12 AM, Andrew Laski mailto:and...@lascii.com>> wrote: I understand that reasoning, but still am unsure on a few things. The direction seems to be moving towards having a requirement that the same functionality is offered in two

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

nt should land in the Nova codebase and couldn't be rather provided by the Heat API. Oh sure, it would perhaps require another endpoint behind the same service, but isn't that better than having another endpoint in Nova ? [1] https://github.com/openstack/governance/blob/master/reference/projec

[openstack-dev] [election][TC] TC Candidacy

Hi! I would like to continue serving on the TC, if you'll have me. Although past performance is no guarantee of future profits, I think it's worth noting that I've been doing this for a while now. I was on the precursor to the TC, the Project Policy Board. Over the time I've been the instigat

Re: [openstack-dev] [magnum]swarm + compose = k8s?

*waving hands wildly at details* ... I believe that the real win is if Magnum's control plan can integrate the network and storage fabrics that exist in an OpenStack with kube/mesos/swarm. Just deploying is VERY meh. I do not care - it's not interesting ... an ansible playbook can do that in 5

Re: [openstack-dev] [Fuel] py.test vs testrepository

On 10/06/2015 10:52 AM, Sebastian Kalinowski wrote: I've already wrote in the review that caused this thread that I do not want to blindly follow rules for using one or another. We should always consider technical requirements. And I do not see a reason to leave py.test (and nobody show me such r

Re: [openstack-dev] [Fuel] py.test vs testrepository

On 10/06/2015 06:01 PM, Thomas Goirand wrote: On 10/06/2015 01:14 PM, Yuriy Taraday wrote: On Mon, Oct 5, 2015 at 5:40 PM Roman Prykhodchenko mailto:m...@romcheg.me>> wrote: Atm I have the following pros. and cons. regarding testrepository: pros.: 1. It’s ”standard" in OpenStac

Re: [openstack-dev] [tc] naming N and O releases nowish

On 10/07/2015 09:24 AM, Sean Dague wrote: On 10/07/2015 08:57 AM, Thierry Carrez wrote: Sean Dague wrote: We're starting to make plans for the next cycle. Long term plans are getting made for details that would happen in one or two cycles. As we already have the locations for the N and O summi

Re: [openstack-dev] Scheduler proposal

On 10/08/2015 09:01 AM, Thierry Carrez wrote: Maish Saidel-Keesing wrote: Operational overhead has a cost - maintaining 3 different database tools, backing them up, providing HA, etc. has operational cost. This is not to say that this cannot be overseen, but it should be taken into consideratio

Re: [openstack-dev] [devstack] A few questions on configuring DevStack for Neutron

On 10/08/2015 07:13 PM, Christopher Aedo wrote: On Thu, Oct 8, 2015 at 9:38 AM, Sean M. Collins wrote: Please see my response here: http://lists.openstack.org/pipermail/openstack-dev/2015-October/076251.html In the future, do not create multiple threads since responses will get lost Yep, th

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

On 10/08/2015 08:39 PM, Robert Collins wrote: This is a bugbear that keeps cropping up and biting us. I'm hoping we can figure out a permanent fix. The problem that occurs is the result of a few interacting things: - requests has very very specific versions of urllib3 it works with. So specifi

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 11:07 AM, David Lyle wrote: I'm in too. Yes please. On Fri, Oct 9, 2015 at 8:51 AM, Dean Troyer wrote: On Fri, Oct 9, 2015 at 9:39 AM, Sean Dague wrote: Lastly, I think it's pretty clear we probably need a dedicated workgroup meeting to keep this ball rolling, come to a rea

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 10:39 AM, Sean Dague wrote: It looks like some great conversation got going on the service catalog standardization spec / discussion at the last cross project meeting. Sorry I wasn't there to participate. Just so folks know, the collection of existing service catalogs has been up

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 11:21 AM, Shamail wrote: On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: It looks like some great conversation got going on the service catalog standardization spec / discussion at the last cross project meeting. Sorry I wasn't there to participate. Apologize if this is a ques

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 01:39 PM, David Stanek wrote: On Fri, Oct 9, 2015 at 1:28 PM, Jonathan D. Proulx mailto:j...@csail.mit.edu>> wrote: On Fri, Oct 09, 2015 at 01:01:20PM -0400, Shamail wrote: :> On Oct 9, 2015, at 12:28 PM, Monty Taylor mailto:mord...@inaugust.com>> wrote:

Re: [openstack-dev] Scheduler proposal

On 10/12/2015 12:43 PM, Clint Byrum wrote: Excerpts from Thomas Goirand's message of 2015-10-12 05:57:26 -0700: On 10/11/2015 02:53 AM, Davanum Srinivas wrote: Thomas, i am curious as well. AFAIK, cassandra works well with OpenJDK. Can you please elaborate what you concerns are for #1? Thanks

Re: [openstack-dev] Scheduler proposal

On 10/12/2015 02:45 PM, Joshua Harlow wrote: Alec Hothan (ahothan) wrote: On 10/10/15, 11:35 PM, "Clint Byrum" wrote: Excerpts from Alec Hothan (ahothan)'s message of 2015-10-09 21:19:14 -0700: On 10/9/15, 6:29 PM, "Clint Byrum" wrote: Excerpts from Chris Friesen's message of 2015-10-

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

On 10/13/2015 05:15 PM, Dean Troyer wrote: On Tue, Oct 13, 2015 at 3:58 PM, Shifali Agrawal mailto:shaifali.agrawa...@gmail.com>> wrote: All above make sense, just one thing, how about using word "zaqar" instead of messaging? That is what all other projects are doing, for example:

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 descriptions format.

Re: [openstack-dev] [Murano] py26 support in python-muranoclient

On 10/18/2015 04:52 PM, Robert Collins wrote: On 11 October 2015 at 01:17, Jeremy Stanley wrote: On 2015-10-09 18:51:51 + (+), Tim Bell wrote: There is a need to distinguish between server side py26 support which is generally under the control of the service provider and py26 support o

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

On 10/19/2015 01:46 AM, Wan-yen Hsu wrote: I fully agreed with Ramesh. There is a need for driver owners to be able to quickly update their driver’s document. Particularly, vendor's drivers have strong dependencies on their platform’s firmware. For instance, a new release of firmware may hav

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On 10/20/2015 06:43 AM, Andreas Jaeger wrote: On 2015-10-20 12:17, Qiming Teng wrote: Hi, Just encountered this again in code review [1]. The question is about the repository to point to when documenting things up. Between the following links, which one should we use? - https://git.openstack.o

Re: [openstack-dev] [new][app-catalog] App Catalog next steps

On 05/27/2015 06:35 PM, Keith Bray wrote: > Joe, regarding apps-catalog for any app deployable on OpenStack > (regardless of deployment technology), my two cents is that is a good > idea. I also believe, however, that the app-catalog needs to evolve > first with features that make it super simple

Re: [openstack-dev] [Ironic] [TC] Discussion: changing Ironic's release model

On 05/28/2015 12:41 PM, Devananda van der Veen wrote: > Hi all, > > tl;dr; > > At the summit, the Ironic team discussed the challenges we've had with > the current release model and came up with some ideas to address them. > I had a brief follow-up conversation with Doug and Thierry, but I'd > li

Re: [openstack-dev] [nova] usefulness of device parameter at volumeAttachment

On 05/28/2015 11:25 PM, Jay Pipes wrote: > On 05/26/2015 03:13 AM, Daniel P. Berrange wrote: >> On Sat, May 23, 2015 at 11:00:32AM +0200, Géza Gémes wrote: >>> Hi, >>> >>> When someone calls nova volume-attach or the block-device-mapping >>> parameter >>> at boot, it is possible to specify a device

[openstack-dev] Release naming for M open for nominations

Hey everyone! It's time to pick a name for the M release. If you have a name you'd like us to vote on, please add it here: https://wiki.openstack.org/wiki/Release_Naming/M_Proposals The nominations will be open until 2015-06-07 23:59:59 UTC. If you don't remember the rules, they're here: http

Re: [openstack-dev] [Ironic] When to bump the microversion?

On 06/04/2015 11:27 AM, Dmitry Tantsur wrote: > On 06/04/2015 05:03 PM, Sean Dague wrote: >> On 06/04/2015 10:50 AM, Dmitry Tantsur wrote: >>> On 06/04/2015 04:40 PM, Ruby Loo wrote: Hi, In Kilo, we introduced microversions but it seems to be a work-in-progress. There is an effo

[openstack-dev] Please Merge patches titled "Merge Tag ..."

Hi! When we cut a release, we do so on a branch. This means that the tag for the release is not in the master branch of the repo, which means git can produce unexpected output in some cases. To solve this, we have the proposal bot propose a null-merge of the tag back in to master. The patch in qu

[openstack-dev] Starting the M Release Name Poll

Hey everybody! I've started the poll for the M release. By now, you should have gotten an email with a link to the vote. If you did not and think that you should have, please let me know (directly, not to the mailing list please) and I can re-send and/or fix as necessary. Please remember that the

Re: [openstack-dev] [puppet][murano] Developing puppet module for Murano

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/17/2015 08:53 AM, Emilien Macchi wrote: > Hi Serg, > > On 06/17/2015 05:35 AM, Serg Melikyan wrote: >> Hi Emilien, >> >> I would like to answer your question regarding >> stackforge/puppet-murano repository asked in different thread: >> >>>

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

On 06/17/2015 03:24 PM, Ian Cordasco wrote: > > > 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 sc

Re: [openstack-dev] [Stackalytics] Complementary projects

On 06/19/2015 11:40 AM, Jay Pipes wrote: > On 06/19/2015 10:31 AM, Joe Gordon wrote: >> On Jun 19, 2015 3:56 PM, "Jay Pipes" > > wrote: >> > >> > On 06/19/2015 09:19 AM, Ilya Shakhat wrote: >> >> >> >> Some reasons of having complementary projects in Stackalytics: >>

Re: [openstack-dev] [Neutron][DevStack] Standing on the shoulders of giants - Linux Bridge testing at the gate

On 06/19/2015 03:20 AM, Sean M. Collins wrote: > Hi, > > I wanted to give a quick update on the new experimental job for testing > the Linux Bridge mechanism driver for Neutron. > > I believe that there is only one patch that needs to be merged, in order to > get the job to a point where we could

[openstack-dev] M Naming Poll ended - results still need to clear legal

Hey all! The M naming poll has concluded. I'd say "and the winner is ..." except we still need to get the winning choice(s) vetted for legal entanglements. Feel free to go and look at the results, they are publicly available - but please DON'T start making t-shirts or having parties (ok, have as

Re: [openstack-dev] [all][requirements] requirements reviews falling behind

On 06/22/2015 02:49 PM, Doug Hellmann wrote: > We have quite a long list of patches to the openstack/requirements > repository, many of which are straightforward changes to increase the > minimums for libraries we develop within the community (meaning we are > holding up projects from using new

Re: [openstack-dev] [Fuel][Fuel-library] Using librarian-puppet to manage upstream fuel-library modules

On 06/23/2015 01:51 PM, Alex Schultz wrote: > Hello everyone, > > I took some time this morning to write out a document[0] that outlines > one possible ways for us to manage our upstream modules in a more > consistent fashion. I know we've had a few emails bouncing around > lately around this topi

Re: [openstack-dev] [cinder][stable] Cinder client broken in Juno

On 06/23/2015 11:49 AM, Mike Perez wrote: > There was a bug raised [1] from some large deployments that the Cinder > client 1.2.0 and beyond is not working because of version discovery. > Unfortunately it's not taking into account of deployments that have a > proxy. > > Cinder client asks Keystone

Re: [openstack-dev] [devstack] apache wsgi application support

On 06/24/2015 02:05 PM, Sean Dague wrote: > On 06/24/2015 01:51 PM, Brant Knudson wrote: >> >> >> On Wed, Jun 24, 2015 at 7:27 AM, Chris Dent > > wrote: >> >> On Wed, 24 Jun 2015, Sean Dague wrote: >> >> On 06/24/2015 07:57 AM, Chris Dent wrote: >> >>

Re: [openstack-dev] Scheduler hints, API and Objects

On 06/25/2015 10:22 AM, Andrew Laski wrote: > I have been growing concerned recently with some attempts to formalize > scheduler hints, both with API validation and Nova objects defining > them, and want to air those concerns and see if others agree or can help > me see why I shouldn't worry. > >

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

On 06/25/2015 01:35 PM, Devananda van der Veen wrote: > Sean's point and Dmitri's are similar. > > There are APIs for projects which do not have official team or "program" > names. And some teams may produce more than one forward-facing service. > Naming the API based in the team name doesn't make

Re: [openstack-dev] [cinder][glance][nova] Python 3 coming!

On 06/26/2015 04:26 AM, Victor Stinner wrote: > Hi, > > The Python 3.4 gate (py34) of cinder, glance and nova just became > voting. You now have to write Python code compatible with Python 2.7 and > 3.4. WOOHOO! Well done! > If the py34 check job fails on your patch, you may try to rebase it to

Re: [openstack-dev] [all] Any other downstream developers having problems with pbr?

On 06/26/2015 07:24 AM, Clark Boylan wrote: > On Fri, Jun 26, 2015, at 04:01 AM, Matthew Booth wrote: >> I wrote this: >> >> https://review.openstack.org/#/c/195983/1/tools/de-pbr.py,cm >> >> Ideally we'd fix PBR, but this seems to be expected behaviour. Thoughts? >> > Use the PBR_VERSION env var [

Re: [openstack-dev] [TripleO] diskimage-builder 1.0.0

On 06/29/2015 08:44 AM, Gregory Haynes wrote: > Hello all, > > DIB has come a long way and we seem to have a fairly stable interface > for the elements and the image creation scripts. As such, I think it's > about time we commit to a major version release. Hopefully this can give > our users the (

Re: [openstack-dev] [all] tenant vs. project

On 02/12/2016 07:36 AM, Jay Pipes wrote: On 02/12/2016 07:01 AM, Sean Dague wrote: Ok... this is going to be one of those threads, but I wanted to try to get resolution here. OpenStack is wildly inconsistent in it's use of tenant vs. project. As someone that wasn't here at the beginning, I'm no

Re: [openstack-dev] [neutron] Postgres support in (fwaas) tests

On 02/12/2016 11:03 AM, Sean M. Collins wrote: I know historically there were postgres jobs that tested things, but I think the community moved away from having postgres at the gate? Historically postgres jobs have been started by someone who is interested, then that person disappears and nob

Re: [openstack-dev] [docs] [api] Why WADL when you can Swagger

On 02/12/2016 03:45 PM, Anne Gentle wrote: Hi all, I wanted to give an update on the efforts to provide improved application developer information on developer.openstack.org . Wrangling this much valuable information and gathering it in a way that helps people is n

Re: [openstack-dev] [all] tenant vs. project

On 02/12/2016 06:40 PM, John Griffith wrote: On Fri, Feb 12, 2016 at 5:01 AM, Sean Dague mailto:s...@dague.net>> wrote: Ok... this is going to be one of those threads, but I wanted to try to get resolution here. OpenStack is wildly inconsistent in it's use of tenant vs. project. A

Re: [openstack-dev] [nova] python-novaclient region setting

On 02/21/2016 11:40 PM, Andrey Kurilin wrote: Hi! `novaclient.client.Client` entry-point supports almost the same arguments as `novaclient.v2.client.Client`. The difference is only in api_version, so you can set up region via `novaclient.client.Client` in the same way as `novaclient.v2.client.Cli

<    1   2   3   4   5   6   7   8   9   >