[openstack-dev] TC candidacy

OpenStack Members, I would like to announce my candidacy to serve for first time on the Technical Committee. Objective: I want to be part of the Technical Committee (TC) because I have all the passion in the world for OpenStack and I want to keep dedicating my energy and love to the most revo

[openstack-dev] ERROR: openstackclient.shell Exception raised: python-keystoneclient 1.4.0

HI All: Recently, our local machine often happened "Failed to launch devstack". Does anyone happen below issue in the Opnestack third-part CI devstack machine? Any workaround or solution to fixed it. 2015-04-24 06:00:18.352 | ERROR: openstackclient.shell Exception raised: (python

Re: [openstack-dev] [magnum] New fedora 21 Atomic images available for testing

Hi Steve, Thank you for working on this. It will be really good for us to remove dependency on external projects. Regards, Madhuri On Fri, Apr 24, 2015 at 8:27 AM, Steven Dake (stdake) wrote: > Hi folks, > > I have spent the last couple of days trying to bring some sanity to the > image bui

Re: [openstack-dev] [all] Question for the TC candidates

On 24 April 2015 at 04:14, Chris Dent wrote: > > This might be a bit presumptuous, but why not give it a try... Nothing presumptuous about it at all :) > There are many different ways to define "quality". For the sake of > this question feel free to use whatever definition you like but take > it

Re: [openstack-dev] [Manila] Two nominations for Manila Core Reviewer Team

+1 to both. - Original Message - From: "Ben Swartzlander" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Wednesday, April 22, 2015 11:53:15 PM Subject: [openstack-dev] [Manila] Two nominations for Manila Core Reviewer Team I would like to nominate Thomas

[openstack-dev] [Fuel][Plugins] Fuel Plugin Guide is replaced with the wiki page

Hi to everyone, Please, be informed that Fuel Plugin Guide has been removed and split into more specific sections at the wiki page [1]. The Plugins wiki page covers the following issues: - basic development issues (Fuel Plugin Builder, package types) - detailed plugin files description - repo cre

Re: [openstack-dev] [all] Question for the TC candidates

On Fri, Apr 24, 2015 at 2:14 AM, Chris Dent wrote: > > This might be a bit presumptuous, but why not give it a try... > > This cycle's TC elections didn't come with a set of prepackaged > questions and though the self-nomination messages have included some > very interesting stuff I think it woul

Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side

Thanks Andrey for hard work on the microverison client support. Wrote down some my thought: I also agreed we will have only one endpoint 'compute'. Hope we can switch v2.1 export as '/v2' in the api-paste.conf as default very soon~ let's say what expected after we only have v2.1 in the world fir

[openstack-dev] [nova] Need more suggestion about nova-scheduler patch/147048

Hi all: I'm working on the patch https://review.openstack.org/#/c/147048/ for bug/1408859 Description of Bug: When the nova-scheduler can't select enough hosts for multiple creating instance, a NoValidHost exception was raised, but the part of hosts had been consumed from instance in

[openstack-dev] use OSTF to test Openstack Deployment

Hi, I want to know how can one use OSTF to test his Openstack Deployment. I searched for it but everywhere i found that it is integrated with fuel, can i have some CLI that can be used to test Openstack Deployment. I searched a lot but cannot found a good article that describes its usage, with

Re: [openstack-dev] [TripleO] splitting out image building from devtest_overcloud.sh

On Thu, 2015-04-16 at 02:59 +, Gregory Haynes wrote: > Excerpts from Gregory Haynes's message of 2015-04-16 02:50:17 +: > > Excerpts from Dan Prince's message of 2015-04-15 02:14:12 +: > > > I've been trying to cleanly model some Ceph and HA configurations in > > > tripleo-ci that use P

Re: [openstack-dev] [puppet] CI status & proposal for puppet-syntax-future jobs

On Thu, 2015-04-23 at 18:56 -0400, Emilien Macchi wrote: > Hi, > > I dressed a spreadsheet with the current status of our CI [1]. > You can see that we need to work on Puppet 4.0 [2] and beaker [3]. Would it be reasonable to add a column representing the TripleO tests as well. Currently we only h

[openstack-dev] [puppet] Openstack Cluster Management

Apache Ambari(https://ambari.apache.org/) is to manage Hadoop cluster. Is it possible to port ambari framework to manage Openstack cluster. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack

Re: [openstack-dev] [all] Question for the TC candidates

On 23/04/15 12:14, Chris Dent wrote: This might be a bit presumptuous, but why not give it a try... Not at all, we should *strongly* encourage people to ask questions of the candidates. In fact, I think we should encourage everyone to contribute to the discussion, not just the candidates.

[openstack-dev] [magnum] New fedora 21 Atomic images available for testing

Hi folks, I have spent the last couple of days trying to bring some sanity to the image building process for Magnum. I have found a tool which the Atomic upstream produces which allows a simple repeatable building process for Fedora Atomic images using any upstream repos of our choosing. I pu

Re: [openstack-dev] [puppet] CI status & proposal for puppet-syntax-future jobs

Emilien Macchi wrote: I dressed a spreadsheet with the current status of our CI [1]. You can see that we need to work on Puppet4.0 [2] and beaker [3]. Otherwise, gate-puppet-*-puppet-syntax-future is green everywhere and I don't see any reason why they should not vote in our CI process. Also,

Re: [openstack-dev] [tripleo] Adventures in QuintupleO

On 23/04/15 23:25, James Slagle wrote: On Tue, Apr 21, 2015 at 5:23 PM, Ben Nemec wrote: On 04/20/2015 04:39 PM, Steve Baker wrote: I've been spending some time getting quintupleo working on top of a Juno RDO OpenStack. I'm at a point now where I think it is worth putting effort into making it

[openstack-dev] [puppet] CI status & proposal for puppet-syntax-future jobs

Hi, I dressed a spreadsheet with the current status of our CI [1]. You can see that we need to work on Puppet 4.0 [2] and beaker [3]. Otherwise, gate-puppet-*-puppet-syntax-future is green everywhere and I don't see any reason why they should not vote in our CI process. Also, once we have Puppet

Re: [openstack-dev] Barbican : Dependency of pyenv configuration in Barbican.sh script

Thanks a lot Douglas for your response. Explanation is great ! I appreciate for your time and efforts. But Accept header is not required for posting the secret but is required while geting the secret as per [1] Accept header was mentioned while retrieving the secret . The same curl command works

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

On Thu, Apr 23, 2015 at 4:41 AM, Thomas Goirand wrote: > > > On 04/10/2015 09:41 AM, Thierry Carrez wrote: > >> Victor Stinner wrote: >> >>> I fixed 4 issues with monkey-patching in Python 3 (importlib, os.open(), >>> threading.RLock, threading.Thread). Good news: the just released eventlet >>> 0

[openstack-dev] [Nova]Devstack live migration.

I am trying to execute a live migration of a VM from node-1 to node-2. As i drill thro' the code it ends up calling function "migrate_server" of nova/nova/conductor/rpcapi.py This migrate_server ends up calling cctxt.call(context, 'migrate_server', **kw) I am trying to understand, what this call

Re: [openstack-dev] Barbican : Dependency of pyenv configuration in Barbican.sh script

Hi Asha, I hope I can clear up some of your confusion about the Barbican server. Barbican is a standard WSGI application. [1] The WSGI application object is created by the create_main_app function in barbican.api.app [2]. WSGI should not be confused with uWSGI [3], which is a web server that

Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)

On 24/04/15 06:02, Richard Raseley wrote: > Flavio Percoco wrote: >>> I think getting operators to adopt it is key to getting other openstack >>> projects to also adopt it. There is something of a chicken and the egg >>> problem >>> with the integration. Some of the projects you will want to inte

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

On 04/23/2015 04:24 PM, Victor Stinner wrote: Also, on the Python 3 topic, there's still a big issue with memcached (aka: python-memcache). Oh, thanks Thomas for the reminder. I just sent a pull request to port python-memcached to Python 3: https://github.com/linsomniac/python-memcached

[openstack-dev] [oslo] summit session scheduling

We need to start figuring out the schedule for summit sessions. Dims has taken a look through the proposed topics and made some recommendations, and I have expanded on that with a proposed breakdown of sessions by room type (fishbowl and working). All of the results are at the bottom of https://et

Re: [openstack-dev] [ec2-api] EC2-API release 0.1.0 available

Excellent, and well done! I think it would be a good idea to send this announcement to the openstack-operators list as well, as some ops people might not notice it here. Cheers, Michael On Thu, Apr 23, 2015 at 10:33 PM, Alexandre Levine wrote: > Hello everyone, > > We've decided to cut our firs

Re: [openstack-dev] Barbican : Dependency of pyenv configuration in Barbican.sh script

Hi All , Would need help! I tried executing the script present in the link https://github.com/openstack/barbican/blob/master/bin/barbican-api to start the barbican instance but the use cases of barbican are failing. Please find the details of the investigations : Usecase for posting and retrie

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 2015-04-23 12:45:14 -0700 (-0700), Joshua Harlow wrote: > Maybe about time we make something like: > > http://projects.apache.org/indexes/category.html > > And link names to repos there...? http://governance.openstack.org/reference/projects/ is sort of our analogue there, I think. It's not ex

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

Doug, HMS Octavia was a British mine sweeper that served during WW2 figthing German warships and u-boats somewhere in the sea. I therefore believe if you have anything against this name you are secretly a nazi. Does that work for the Godwin's law call? Salvatore On 23 April 2015 at 22:09, Doug W

[openstack-dev] [Ironic] Kilo RC2 available

Hello everyone, Due to release-critical issues spotted in Ironic during RC1 testing, a new release candidate was created for Kilo. The list of RC2 fixes, as well as the RC2 tarball are available at: https://launchpad.net/ironic/kilo/kilo-rc2 Unless new release-critical issues are found that warr

Re: [openstack-dev] [Fuel] Plugin development docs - currently 404

Thanks for the correct link, Chris! Indeed we are aware of this problem, here's the bug where it is tracked: https://bugs.launchpad.net/fuel/+bug/1447025 On Thu, Apr 23, 2015 at 1:11 PM, Christopher Aedo wrote: > On Thu, Apr 23, 2015 at 12:33 PM, Sean M. Collins wrote: >> The links for the deve

Re: [openstack-dev] [Fuel] Plugin development docs - currently 404

On Thu, Apr 23, 2015 at 12:33 PM, Sean M. Collins wrote: > The links for the developer documentation are currently broken. I would bet the docs team is sorting out the broken link as I type this, thanks for pointing it out! In the mean time it looks like the docs on the wiki are up to date (or a

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> On Apr 23, 2015, at 1:42 PM, Russell Bryant wrote: > > On 04/23/2015 03:23 PM, Kyle Mestery wrote: >> On Thu, Apr 23, 2015 at 2:18 PM, Doug Wiegley >> mailto:doug...@parksidesoftware.com>> wrote: >> >> >>> On Apr 23, 2015, at 11:57 AM, Russell Bryant >> wrote:

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

Russell Bryant wrote: On 04/23/2015 03:23 PM, Kyle Mestery wrote: On Thu, Apr 23, 2015 at 2:18 PM, Doug Wiegley mailto:doug...@parksidesoftware.com>> wrote: > On Apr 23, 2015, at 11:57 AM, Russell Bryantmailto:rbry...@redhat.com>> wrote: > > On 04/23/2015 01:19 PM, Armando M

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/23/2015 03:23 PM, Kyle Mestery wrote: > On Thu, Apr 23, 2015 at 2:18 PM, Doug Wiegley > mailto:doug...@parksidesoftware.com>> wrote: > > > > On Apr 23, 2015, at 11:57 AM, Russell Bryant > wrote: > > > > On 04/23/2015 01:19 PM, Armando M. wrote: >

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

Victor Stinner wrote: Also, on the Python 3 topic, there's still a big issue with memcached (aka: python-memcache). Oh, thanks Thomas for the reminder. I just sent a pull request to port python-memcached to Python 3: https://github.com/linsomniac/python-memcached/pull/67 I don't understa

[openstack-dev] [Fuel] Plugin development docs - currently 404

The links for the developer documentation are currently broken. https://software.mirantis.com/mirantis-openstack-fuel-plug-in-development/ Links to: http://docs.mirantis.com/openstack/fuel/fuel-6.0/plugin-dev.html#developing-a-plug-in-for-fuel Where can I find the documentation? -- Sean M. Co

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Thu, Apr 23, 2015 at 2:18 PM, Doug Wiegley wrote: > > > On Apr 23, 2015, at 11:57 AM, Russell Bryant wrote: > > > > On 04/23/2015 01:19 PM, Armando M. wrote: > >> > >> > >> On 23 April 2015 at 09:58, Russell Bryant >> > wrote: > >> > >>On 04/23/2015 12:14 PM, A

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> On Apr 23, 2015, at 11:57 AM, Russell Bryant wrote: > > On 04/23/2015 01:19 PM, Armando M. wrote: >> >> >> On 23 April 2015 at 09:58, Russell Bryant > > wrote: >> >>On 04/23/2015 12:14 PM, Armando M. wrote: >>> >>> >>> On 23 April 2015 at 07:32, Russell Brya

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

On Thu, Apr 23, 2015 at 12:10 AM, Victor Stinner wrote: > Hi, > > > How invasive would the port to python3 be? > > I squashed all my commits into a single commit of my draft port and I > pushed it at: > > https://github.com/haypo/nova/commit/bad54bc2b278c7c7cb7fa6cc73d03c70138bd89d I like how t

[openstack-dev] [Neutron][Keystone] Kilo RC2 available

Hello everyone, Due to release-critical issues spotted in Neutron and Keystone during RC1 testing, new release candidates were created for Kilo. The list of RC2 fixes, as well as RC2 tarballs are available at: https://launchpad.net/neutron/kilo/kilo-rc2 https://launchpad.net/keystone/sahara/kilo-

Re: [openstack-dev] cirros 0.3.4~pre1 available

On Thu, Apr 23, 2015 at 09:24:20AM EDT, Scott Moser wrote: > The changes since 0.3.3 are: > - Improve tooling for IPv6 and network debugging >adding ping6, traceroute6 and arp. > > Thanks to Jens Rosenboom for pushing on getting some ipv6 things going and > fixing nc -ll. This is fantastic.

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Thu, Apr 23, 2015 at 1:31 PM, Fox, Kevin M wrote: > Yeah. In the end, its what git repo the source for a given rpm you > install comes from. Ops will not care that neutron-openvswitch-agent comes > from repo foo.git instead of bar.git. > > That's really the tl;dr of the proposed split. Than

Re: [openstack-dev] [Horizon] Outreachy call for mentor

Hi Thai, Will do, thanks a lot to you too! 2015-04-22 22:21 GMT-03:00 Thai Q Tran : > Hi Victoria, > > Count me in also. I'll go ahead and subscribe myself to the mailing list > as well. > > [image: Inactive hide details for Victoria Martínez de la Cruz > ---04/22/2015 06:10:13 PM---Hi David, Th

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

Yeah. In the end, its what git repo the source for a given rpm you install comes from. Ops will not care that neutron-openvswitch-agent comes from repo foo.git instead of bar.git. Thanks, Kevin From: Armando M. [arma...@gmail.com] Sent: Thursday, April 23, 2015 9

Re: [openstack-dev] [api] API WG Meeting Time

On 04/23/2015 01:12 PM, michael mccune wrote: > On 03/31/2015 10:13 PM, Everett Toews wrote: >> Ever since daylight savings time it has been increasing difficult for >> many API WG members to make it to the Thursday 00:00 UTC meeting time. >> >> Do we change it so there’s only the Thursday 16:00 UT

[openstack-dev] [magnum] Re: [atomic-devel] Adding kubernetes 0.15 to Fedora 21 Atomic

On 4/17/15, 10:25 AM, "Matthew Miller" wrote: >On Fri, Apr 17, 2015 at 04:29:36PM +, Steven Dake (stdake) wrote: >> Fedora 21 only has kubernetes 0.13 although I see in koji k8s 0.15 >> has been built for f23. Is there any possibility of getting >> kubernetes 0.15 in fedora atomic 21 by May

Re: [openstack-dev] [all] Question for the TC candidates

Hey there Chris! On Thu, Apr 23, 2015 at 9:17 AM Chris Dent wrote: > What can and should the TC at large, and you specifically, do to > ensure quality improves for the developers, end-users and operators > of OpenStack as a full system, both as a project being developed and > a product being use

Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)

Flavio Percoco wrote: I think getting operators to adopt it is key to getting other openstack projects to also adopt it. There is something of a chicken and the egg problem with the integration. Some of the projects you will want to integrate the most with are already considered pretty stable and

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/23/2015 01:19 PM, Armando M. wrote: > > > On 23 April 2015 at 09:58, Russell Bryant > wrote: > > On 04/23/2015 12:14 PM, Armando M. wrote: > > > > > > On 23 April 2015 at 07:32, Russell Bryant > >

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

Excerpts from Victor Stinner's message of 2015-04-23 07:24:06 -0700: > > Also, on the Python 3 topic, there's still a big issue with memcached > > (aka: python-memcache). > > Oh, thanks Thomas for the reminder. I just sent a pull request to port > python-memcached to Python 3: > >https://gi

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 23 April 2015 at 09:58, Russell Bryant wrote: > On 04/23/2015 12:14 PM, Armando M. wrote: > > > > > > On 23 April 2015 at 07:32, Russell Bryant > > wrote: > > > > On 04/22/2015 10:33 PM, Armando M. wrote: > > > > > > Would it make sense to captur

Re: [openstack-dev] [api] API WG Meeting Time

On 03/31/2015 10:13 PM, Everett Toews wrote: Ever since daylight savings time it has been increasing difficult for many API WG members to make it to the Thursday 00:00 UTC meeting time. Do we change it so there’s only the Thursday 16:00 UTC meeting time? this topic was brought up again at tod

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/23/2015 12:14 PM, Armando M. wrote: > > > On 23 April 2015 at 07:32, Russell Bryant > wrote: > > On 04/22/2015 10:33 PM, Armando M. wrote: > > > > Would it make sense to capture these projects as simply > > 'affiliated', ie. with

Re: [openstack-dev] [all] Question for the TC candidates

On 04/23/2015 12:14 PM, Chris Dent wrote: > > This might be a bit presumptuous, but why not give it a try... Thank you for asking the question, Chris, my response is below. Anita. > > This cycle's TC elections didn't come with a set of prepackaged > questions and though the self-nomination messa

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

+1 From: Armando M. [arma...@gmail.com] Sent: Wednesday, April 22, 2015 7:44 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code Could you please also pay some attentio

Re: [openstack-dev] Barbican : Dependency of pyenv configuration in Barbican.sh script

Hi All, Thanks Adam for your response. I am able to run the barbican-api script without SQLLite installation .I guess SQLLite comes configured with barbican installation .Please correct me if I am wrong. [root@barbican-keystone2 barbican]# bin/barbican-api 2015-04-23 11:12:31.571 8265 INFO barbic

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 23 April 2015 at 07:32, Russell Bryant wrote: > On 04/22/2015 10:33 PM, Armando M. wrote: > > > > Would it make sense to capture these projects as simply > > 'affiliated', ie. with a loose relationship to Neutron, because > > they use/integrate with Neutron in some form

[openstack-dev] [all] Question for the TC candidates

This might be a bit presumptuous, but why not give it a try... This cycle's TC elections didn't come with a set of prepackaged questions and though the self-nomination messages have included some very interesting stuff I think it would be useful to get answers from the candidates on at least one

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

> > >> I agree with henry here. > Armando, If we use your analogy with nova that doesn't build and deliver > KVM, we can say that Neutron doesn't build or deliver OVS. It builds a > driver and an agent which manage OVS, just like nova which provides a > driver to manage libvirt/KVM. > Moreover, ext

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 23 April 2015 at 01:49, Thierry Carrez wrote: > Armando M. wrote: > > Is it sensible to assume that Stackforge is going away entirely at some > > point in the future, and we'll have a single namespace - OpenStack? > > The key difference between Stackforge and OpenStack is governance. Any > pro

[openstack-dev] [Trove] Kilo RC2 available

Hello everyone, Due to release-critical issues spotted in Trove during RC1 testing, a new release candidate was created for Kilo. The list of RC2 fixes, as well as the RC2 tarball are available at: https://launchpad.net/trove/kilo/kilo-rc2 Unless new release-critical issues are found that warran

Re: [openstack-dev] Barbican : Dependency of pyenv configuration in Barbican.sh script

Do you have sqlite installed on your system, and do you have config.py in the root of your barbican directory? The database is configured there (assuming it hasn’t changed since I last ran Barbican locally), and mine looks like this: config = { 'sqlalchemy': { 'url': 'sqlite:tmp/

Re: [openstack-dev] Barbican : Dependency of pyenv configuration in Barbican.sh script

Sorry I forgot to introduce myself. My name is Neetu Jain and I will be working on Barbican/HSM at softlayer/IBM. Asha and I are in the same team. On Thu, Apr 23, 2015 at 10:07 AM, neetu jain wrote: > Thanks John for you answer. > I tried running the script bin/barbican-api and ran into this

Re: [openstack-dev] Barbican : Dependency of pyenv configuration in Barbican.sh script

Thanks John for you answer. I tried running the script bin/barbican-api and ran into this issue (pasted at the end) . Seems like the script does not take care of the database side. 1) do we need to do something else to setup database? or its being worked on ? 2) Can we help in the process of remo

Re: [openstack-dev] [glance] Why no DB index on sort parameters

Messing with indices is not a good idea to do iteratively. Indexing large data sets is a really expensive operation and should be done carefully and consistently. Changing around indices is only going to make things unstable. Thanks, -Nikhil From: Flavi

Re: [openstack-dev] Fedora 21 Kubernetes 0.15.0 Image Status

Madhuri, Copying openstack-dev mailing list – hope you don’t mind. Folks, we are talking about the images here: https://fedorapeople.org/groups/magnum/ Specifically the images with “15” in the filename. Feel free to test these images as your leisure. From: Madhuri Rai mailto:madhuri.ra...@gma

Re: [openstack-dev] [release] release critical oslo.messaging changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The review on master branches are ready: oslo.messaging with heartbeat off: https://review.openstack.org/#/c/174929/ requirement changes: https://review.openstack.org/#/c/174930/ Once they are merged, I will backport them to stable/kilo and sy

Re: [openstack-dev] [Nova][Sahara][Heat] Kilo RC2 available

> Hello everyone, > > Due to release-critical issues spotted in Nova, Sahara and Heat during > RC1 testing, new release candidates were created for Kilo. The list of > RC2 fixes, as well as RC2 tarballs are available at: > > https://launchpad.net/nova/kilo/kilo-rc2 > https://launchpad.net/nova/sa

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/22/2015 10:33 PM, Armando M. wrote: > > Would it make sense to capture these projects as simply > 'affiliated', ie. with a loose relationship to Neutron, because > they use/integrate with Neutron in some form or another (e.g. > having 3rd-party, extending-api,

Re: [openstack-dev] TC Non-Candidacy

On 04/23/2015 08:33 AM, Ed Leafe wrote: > On Apr 22, 2015, at 9:31 PM, Devananda van der Veen > wrote: > >> Being a member of the technical committee is not merely a >> commitment of a few hours a week; it is not just a forum for >> resolving differences between two or three projects; and it's >>

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/22/2015 09:55 PM, Anita Kuno wrote: > On 04/22/2015 09:46 PM, Kyle Mestery wrote: >> On Wed, Apr 22, 2015 at 7:44 PM, Armando M. wrote: >> >>> >>> >>> On 22 April 2015 at 11:19, Russell Bryant wrote: >>> Hello! A couple of things I've been working on lately are project govern

Re: [openstack-dev] TC non-candidacy

Confirmed. :P On 04/23/2015 02:05 AM, Michael Still wrote: Hi, I've served on the TC for a while now and enjoyed it. However, I feel I've reached a point where I need to step back and take a break. I will therefore not be running this time around. I'm sure I'll return just as soon as my righteo

Re: [openstack-dev] TC non-candidacy

On 04/23/2015 02:05 AM, Michael Still wrote: > Hi, > > I've served on the TC for a while now and enjoyed it. However, I feel > I've reached a point where I need to step back and take a break. I > will therefore not be running this time around. I'm sure I'll return > just as soon as my righteous an

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

> Also, on the Python 3 topic, there's still a big issue with memcached > (aka: python-memcache). Oh, thanks Thomas for the reminder. I just sent a pull request to port python-memcached to Python 3: https://github.com/linsomniac/python-memcached/pull/67 I don't understand. I saw a lot of "P

Re: [openstack-dev] [Nova][Neutron] Cross-project coordination

Good luck Sean!! Hopefully you can sort out the DNS and the Qoutas. Thanks again ! On Wed, Apr 22, 2015 at 11:41 PM, Jay Pipes wrote: > On 04/22/2015 04:33 PM, Kyle Mestery wrote: > >> On Wed, Apr 22, 2015 at 3:28 PM, Sean M. Collins > > wrote: >> >> Hi, >> >>

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On Thu, Apr 23, 2015 at 10:28 AM, henry hly wrote: > On Thu, Apr 23, 2015 at 10:44 AM, Armando M. wrote: > >> > >> Could you please also pay some attention on Cons of this ultimate > >> splitting Kyle? I'm afraid it would hurt the user experiences. > >> > >> On the position of Dev, A naked Neutr

Re: [openstack-dev] OpenStack-dev Digest, Vol 36, Issue 67

> > > >> I recommend to use mysqlclient instead of MySQL-python even on > >> Python 2. > >> > >> https://pypi.python.org/pypi/mysqlclient > >> https://github.com/PyMySQL/mysqlclient-python > > > Is it packaged in popular distributions? RHEL? Fedora? SuSe? Ubuntu? > > Debian? Gentoo? > > If this lib

Re: [openstack-dev] [tempest][nova] TestVolumeBootPattern fail with libvirt-xen, how to fix it?

On 16 April 2015 at 18:11, Anthony PERARD wrote: > Hi all, > > With libvirt_type=xen, the tempest test > tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern > fail. > > This is because it setup a volume with 'vda' as device_name and nova (well > libvirt) fail t

Re: [openstack-dev] [nova] Required data migrations in Kilo, need Turbo Hipster tests updated

> That change works on the dataset. However I was referring to the > db/object api (which I have no real knowledge of) that it should be able > to get_by_uuid unmigrated instances and in my case I got the traceback > given in that paste. It's possible I'm just using the API incorrectly. You should

Re: [openstack-dev] [Nova][Neutron] Cross-project coordination

On 22 April 2015 at 23:41, Jay Pipes wrote: > On 04/22/2015 04:33 PM, Kyle Mestery wrote: >> >> On Wed, Apr 22, 2015 at 3:28 PM, Sean M. Collins > > wrote: >> >> Hi, >> >> Kyle Mestery has asked me to serve as a cross-project liaison between >> Neutron and No

[openstack-dev] cirros 0.3.4~pre1 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello all, I've made a build of cirros versioned '0.3.4~pre1' available on http://download.cirros-cloud.net/0.3.4~pre1/ Hello all, cirros 0.3.3 has been released. It is available for download at http://download.cirros-cloud.net/0.3.4~pre1 . The

Re: [openstack-dev] [packaging][neutron] --config-dir vs. --config-file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I just realized that while RDO now has a way to configure each service separately with user defined configuration file, there is still one limitation - a replacement for neutron.conf that contains lots of options that are common to all services. I th

Re: [openstack-dev] [oslo][policy][neutron] oslo.policy API is not powerful enough to switch Neutron to it

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've sent a patch that makes And, Or, Not, and Rule checks public. As for RoleCheck, we don't need it anymore since we're going to kill the code that relied on it. The patch is: https://review.openstack.org/#/c/176683/ Note that we will need a new

Re: [openstack-dev] TC Non-Candidacy

On Apr 22, 2015, at 9:31 PM, Devananda van der Veen wrote: > Being a member of the technical committee is not merely a commitment of a few > hours a week; it is not just a forum for resolving differences between two or > three projects; and it's definitely not a social club or popularity conte

[openstack-dev] [ec2-api] EC2-API release 0.1.0 available

Hello everyone, We've decided to cut our first release of the standalone EC2-API project. All of the known to us major problems are solved - NovaDB direct access is cut off, performance is checked and improved, all of the necessary functional, unit and Rally tests are in place. One known cavea

[openstack-dev] [Nova][Sahara][Heat] Kilo RC2 available

Hello everyone, Due to release-critical issues spotted in Nova, Sahara and Heat during RC1 testing, new release candidates were created for Kilo. The list of RC2 fixes, as well as RC2 tarballs are available at: https://launchpad.net/nova/kilo/kilo-rc2 https://launchpad.net/nova/sahara/kilo-rc2 ht

Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)

On 21/04/15 14:08 +, Fox, Kevin M wrote: I think getting operators to adopt it is key to getting other openstack projects to also adopt it. There is something of a chicken and the egg problem with the integration. Some of the projects you will want to integrate the most with are already consi

Re: [openstack-dev] TC Candidacy

confirmed On 04/23/2015 12:56 AM, Maish Saidel-Keesing wrote: > I would like to announce my candidacy for the OpenStack Technical Committee > > Many of you many not know me, because I am not a very active contributor. > > First a bit about myself. I am a Platform Architect working for Cisco in >

Re: [openstack-dev] TC Candidacy

confirmed On 04/23/2015 12:26 AM, David Medberry wrote: > Announcing my candidacy for the TC. > > I would bring an operator's perspective (ie, operator, user, super-user and > dev) to the Technical Committee. > > I've been involved in OpenStack for four years. I gave talks at San Diego, > Atlant

Re: [openstack-dev] TC candidacy

confirmed On 04/22/2015 09:52 PM, Mark McClain wrote: > All- > > I'd like to announce my candidacy to continue serving on the Technical > Committee. > > > Platform > — > OpenStack is a growing community comprised of many parts and we we must view > ourselves as one unit. As a TC member, I

Re: [openstack-dev] TC Candidacy

confirmed On 04/22/2015 09:32 PM, Michael Krotscheck wrote: > Hi everyone! > > I'd like to announce my own candidacy for the OpenStack Technical > Committee. My TL/DR platform is: "Represent Front-End Engineering". It's > what I do, it's what I love, it's what I've been doing for the last 15 > ye

Re: [openstack-dev] [glance] Why no DB index on sort parameters

On 21/04/15 14:55 +, Nikhil Komawar wrote: Rally is great overall however, we need good EXPLAIN examples on real world data. Smaller deployments might benefit from a simple sample performance analysis however, larger data sets can have impacts on areas that you never expect. A spec means

Re: [openstack-dev] [tripleo] Adventures in QuintupleO

On Tue, Apr 21, 2015 at 5:23 PM, Ben Nemec wrote: > On 04/20/2015 04:39 PM, Steve Baker wrote: >> I've been spending some time getting quintupleo working on top of a Juno >> RDO OpenStack. I'm at a point now where I think it is worth putting >> effort into making it easy for anyone to try this. >

Re: [openstack-dev] [Glance] Open glance-drivers to all glance-cores

On 22/04/15 05:57 +, Nikhil Komawar wrote: Hello all, With all due respect to all the Glance core-reviewers (who are doing an excellent job, by the way), please NO. First reaction that came to my mind after reading the title: What might be the thinking behind this, what is the direction t

Re: [openstack-dev] [neutron-lbaas] [third-party] trying to set up 3rd party CI, neutron-lbaas tox fails to import some neutron

Thanks guys that was it! Did a git pull on the egg that tox cloned and it works now. Pretty strange that it clones an out of date neutron though. This was all a fresh environment. Cheers Shane McGough Junior Software Developer KEMP Technologies National Technology Park, Limerick, Ireland.

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

On 04/10/2015 09:41 AM, Thierry Carrez wrote: Victor Stinner wrote: I fixed 4 issues with monkey-patching in Python 3 (importlib, os.open(), threading.RLock, threading.Thread). Good news: the just released eventlet 0.17.3 includes these fixes and it is now fully compatible with Python 3! For

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

Victor Stinner writes: >> Is there already a static analysis tool that helps find these things? (Would >> a >> pylint check for the above be useful? Some of them would be hard to find >> reliably, but a bunch of the above would be trivial) > > I read that hacking has some checks. It's quite easy

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

Armando M. wrote: > Is it sensible to assume that Stackforge is going away entirely at some > point in the future, and we'll have a single namespace - OpenStack? The key difference between Stackforge and OpenStack is governance. Any project can be in Stackforge. Projects that are considered "OpenS

Re: [openstack-dev] Sahara HA discussion

Hi Lu I'm going to start working on HA support for Sahara for HDP and CDH plugins. Now I didn't create specs or blueprints about HA. Also I don't have code for HA support. When are you going to start implement HA for CDH? Thanks Sergey 2015-04-20 4:06 GMT+03:00 Lu, Huichun : > Hi Sergey > > L

  1   2   >