Re: [openstack-dev] [Nova] Gate broken

On Sat, Feb 8, 2014 at 3:29 PM, Gary Kotton wrote: > Hi, > Anyone aware of: > > It is caused the new boto 2.25 release. Joe Gordon filed a new bug on this[1], and I just submitted a patch [2] to fix. [1] https://bugs.launchpad.net/nova/+bug/1277790 [2] https://review.openstack.org/#/c/72066/ Th

[openstack-dev] [Nova] Gate broken

Hi, Anyone aware of: 2014-02-08 06:49:42.022 | ${PYTHON:-python} -m subunit.run discover -t ./ ./nova/tests --load-list /tmp/tmp.aaa9SCw11a/tmpuyhFPj 2014-02-08 06:49:42.022

Re: [openstack-dev] [savanna] project name collision - renaming required

There are already some names proposed in the etherpad, so, I'll setup a voting to choose top N options and discuss them detailed. The voting will be started after the next IRC team meeting next week, Feb 13. Thanks. P.S. Looking forward for new name proposals :) On Thu, Jan 30, 2014 at 10:39 AM

[openstack-dev] [savanna] team meeting minutes Feb 6

Thanks everyone who have joined Savanna meeting. Here are the logs from the meeting: Minutes: http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-06-18.09.html Log: http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-02-06-18.09.log.html -- Sincerely yours, Sergey

[openstack-dev] How to write a new neutron L2 plugin using ML2 framework?

Hi, All I want to write a new neutron L2 plugin using ML2 framework, I noticed openvswitch and linxubridge have been ported into ML2 framework, but it seems many code is removed compared to standalone L2 plugin, I guess some code has been written into a common library. Now I want to write a L2

[openstack-dev] [Glance] Why are location indices in Glance '1' (and not '0') based?

Hi all, In api.v2.images.ImagesController._get_locations_op_pos there is a comment that location indices start from one from the client's perspective and the code subtracts one from the incoming 'index position' parameter before proceeding with the subsequent operations. But I see that json-patch

Re: [openstack-dev] Cinder Stability Hack-a-thon

On Sat, Feb 1, 2014 at 3:06 AM, Mike Perez wrote: > Folks, > > I would love to get people together who are interested in Cinder stability > to really dedicate a few days. This is not for additional features, but > rather > finishing what we already have and really getting those in a good shape >

Re: [openstack-dev] [python-openstacksdk] Initial meeting scheduling

Grab that Thursday 2:00 Central while it's still available each week! gogogogo There's also 1:00 Central Mondays when each meeting room is open. Give a holla with a time you decide on and I'll update the ical. Anne On Fri, Feb 7, 2014 at 6:59 PM, Jesse Noller wrote: > > On Feb 7, 2014, at 5:5

Re: [openstack-dev] [All] Python 3.3 gates are failing

This issue is being tracked with the following bug: https://bugs.launchpad.net/openstack-ci/+bug/1277495 On Fri, Feb 7, 2014 at 4:09 AM, Sergey Lukjanov wrote: > The same with swiftclient, hacking, openstacksdk and others - > http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiJ2FzY2lpJyB

Re: [openstack-dev] pep8 barfs on long URL

On Fri, Feb 7, 2014 at 6:40 AM, Jay Pipes wrote: > On Fri, 2014-02-07 at 15:36 +0100, Julien Danjou wrote: >> On Fri, Feb 07 2014, Jay Pipes wrote: >> >> > On Fri, 2014-02-07 at 14:25 +, Matthew Booth wrote: >> >> I have a comment which references a long URL. The URL itself is longer >> >> tha

Re: [openstack-dev] [python-openstacksdk] Initial meeting scheduling

On Feb 7, 2014, at 5:57 PM, Doug Hellmann wrote: > > > > On Fri, Feb 7, 2014 at 6:15 PM, Jesse Noller > wrote: > Hi Everyone: > Circling back to the client tools / SDK discussion - we’ve gotten a > critical mass of people involved/interesting in the unified/common SDK back > end f

Re: [openstack-dev] [Horizon] RFC - Suggestion for switching from Less to Sass (Bootstrap 3 & Sass support)

Hi, +1 for switching sass. I believe this is a really nice idea. Sass is very similar to less (more powerful than less!), so I think switching is not a big deal. I just tried PyScss and django-pyscss. https://github.com/Kronuz/pyScss https://github.com/fusionbox/django-pyscss This is bootstrap.cs

Re: [openstack-dev] [heat] non-trivial example - IBM Connections

Hi Mike, Thank you for sharing this. It looks pretty impressive. Could you, please some details about DSL syntax, if it is possible? In our Murano project we are also solving the problem of Heat template generation. At his moment we are working on a new DSL for Murano to move from XMLs based DSL

Re: [openstack-dev] [python-openstacksdk] Initial meeting scheduling

On Fri, Feb 7, 2014 at 6:15 PM, Jesse Noller wrote: > Hi Everyone: > Circling back to the client tools / SDK discussion - we've gotten > a critical mass of people involved/interesting in the unified/common SDK > back end for application developers and other end-users. From the wiki page: >

Re: [openstack-dev] [Governance] Integrated projects and new requirements

On Feb 7, 2014, at 4:17 PM, Russell Bryant mailto:rbry...@redhat.com>> wrote: On 02/06/2014 08:47 AM, Thierry Carrez wrote: Dina Belova wrote: Perhaps we should start putting each project on the TC agenda for a review of its current standing. For any gaps, I think we should set a speci

[openstack-dev] [python-openstacksdk] Initial meeting scheduling

Hi Everyone: Circling back to the client tools / SDK discussion - we’ve gotten a critical mass of people involved/interesting in the unified/common SDK back end for application developers and other end-users. From the wiki page: "This is a proposed OpenStack project that is desig

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

On Feb 7, 2014, at 2:59 PM, Victor Stinner wrote: > I don't see why external libraries should be modified. Only the few libraries > sending HTTP queries and requests to the database should handle asyncio. > Dummy > example: the iso8601 module used to parse time doesn't need to be aware of >

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

Le vendredi 7 février 2014, 09:37:27 Vishvananda Ishaya a écrit : > To be clear, since many people weren’t around in ye olde days, nova started > using tornado. We exchanged tornado for twisted, and finally moved to > eventlet. People have suggested gevent and threads in the past, and now > asyncio

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

Le jeudi 6 février 2014, 22:32:26 Zane Bitter a écrit : > [BTW am I right in thinking that in trollius you _have_ to drive your > co-routines from a top-level Task? That's not the case in Heat (although > we do anyway), or IIUC in asyncio - I was expecting e.g. the exception > handling for Return t

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

Le mardi 4 février 2014, 12:53:24 Kevin Conway a écrit : > One of the great benefits of using a green thread abstraction, like > eventlet or gevent, is that it lets you write normal Python code and slap > your concurrency management over the top. It even lets us program in > familiar models by pret

[openstack-dev] [Ironic][Ceilometer]bp:send-data-to-ceilometer

>Haomeng wrote: >Ok, will implement the bp based on the first solution, thanks. I believe solution 2 is more flexible and it allows hardware to report additional sensors than solution 1. However, if there is a desire to define specific sensor categories as proposed by solution 1, then

[openstack-dev] [nova][ceilometer] Removing simple_tenant_usage and os-instance_usage_audit_log from V3 API

Hi All, I would like to propose removing the simple_tenant_usage and os-instance_usage_audit_log extensions from the nova V3 API (while keeping them in V2). Both of these are pre ceilometer extensions to generate rudimentary usage information, something that we should be using ceilometer for. For

Re: [openstack-dev] [Governance] Integrated projects and new requirements

On 02/06/2014 08:47 AM, Thierry Carrez wrote: > Dina Belova wrote: >> Perhaps we should start putting each project on the TC agenda for a >> review of its current standing. For any gaps, I think we should set a >> specific timeframe for when we expect these gaps to be filled. >> >> >>

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

On Feb 7, 2014, at 10:25 AM, Yuriy Taraday wrote: > Hello, Vish! > > I hope you can provide some historical data. > > On Fri, Feb 7, 2014 at 9:37 PM, Vishvananda Ishaya > wrote: > To be clear, since many people weren’t around in ye olde days, nova started > using tornado. We exchanged torna

Re: [openstack-dev] [Nova] Bug Triage Day Proposal - Friday 7th February

On Friday, February 07, 2014 1:15:11 PM, John Garbutt wrote: So untouched bugs: ~200 -> ~130 Awesome. Hope the US guys (and anyone else who is till working) have a good afternoon brining that down further. Anyways, I am going to have my dinner, because I like in the UK, and I have to play my

Re: [openstack-dev] [Governance] Integrated projects and new requirements

On 02/06/2014 09:14 AM, Sergey Lukjanov wrote: > Probably all PTLs could be asked to prepare initial report for > requirements like it was done last time for graduating projects. Yes, that sounds reasonable and would likely help the process along. -- Russell Bryant _

Re: [openstack-dev] several oslo library repositories have moved

+1 thanks guys! From: Doug Hellmann mailto:doug.hellm...@dreamhost.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Friday, February 7, 2014 at 1:02 PM To: OpenStack Development Mailing List mailto:openstack-dev@list

[openstack-dev] several oslo library repositories have moved

The Oslo program has adopted cliff, pycadf, stevedore, and taskflow, promoting them from stackforge, so we can establish symmetric gating with the rest of OpenStack. In order to do that, the git repositories were moved from "stackforge/*" to "openstack/*" (git:// git.openstack.org/stackforge/taskfl

Re: [openstack-dev] [keystone] Integrating with 3rd party DB

On Fri, Feb 7, 2014 at 3:29 AM, Jamie Lennox wrote: > > > - Original Message - > > From: "Noorul Islam K M" > > To: "Jamie Lennox" > > Cc: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > > Sent: Friday, 7 February, 2014 7:13:20 PM

Re: [openstack-dev] [nova][baremetal] Support multiple image write workers in nova bare-metal

On Fri, Feb 7, 2014 at 2:59 PM, Robert Collins wrote: > On 7 February 2014 23:02, Taurus Cheung wrote: >> Hi, >> >> >> >> I am working on deploying images to bare-metal machines using nova >> bare-metal. In existing implementation in nova-baremetal-deploy-helper.py, >> there's only 1 worker to wr

Re: [openstack-dev] [nova][baremetal] Delete disk image in nova after deploy image to bare-metal machine

On 7 February 2014 22:59, Taurus Cheung wrote: > Hi > > I am working on deploying images to bare-metal machines using nova > bare-metal. In current architecture, disk images are kept at > /var/lib/nova/instances after the image is written (by dd) to the hard disk > of bare-metal machines. But thes

Re: [openstack-dev] [nova][baremetal] Support configurable inject items in nova Bare-metal

On 7 February 2014 23:01, Taurus Cheung wrote: > Hi, > > > > I am working on deploying images to bare-metal machines using nova > bare-metal. In current design, some files like hostname, network config file > and meta.json are injected into the image before writing to bare-metal > machines. Can we

Re: [openstack-dev] [Tempest][Glance] Bogus Glance service and endpoint required for Tempest?

Actually another point which needs fixing is in test_utils, the scenario_images method should honour the glance_available configuration flag, it doesn't know. I'll submit a fix for that. andrea -Original Message- From: Frittoli, Andrea (Cloud Services) Sent: 07 February 2014 19:50 To: O

Re: [openstack-dev] [nova][baremetal] Support multiple image write workers in nova bare-metal

On 7 February 2014 23:02, Taurus Cheung wrote: > Hi, > > > > I am working on deploying images to bare-metal machines using nova > bare-metal. In existing implementation in nova-baremetal-deploy-helper.py, > there's only 1 worker to write image to bare-metal machines. If there is a > number of bare

Re: [openstack-dev] [Tempest][Glance] Bogus Glance service and endpoint required for Tempest?

Two days ago a patch I submitted introduced lazy load of glance httpin the api section... That already may help. I'm also working on a patch for lazy load of all clients in the manager classes, but that may take some more time before it's available Andrea Sent from my tiny device Jay

Re: [openstack-dev] [Nova][vmware] A new VMwareAPISession

Thanks! I've dropped a few comments around on reviews & the blueprints so people not watching the mailing list will see. On Feb 6, 2014 7:32 PM, "Davanum Srinivas" wrote: > Shawn, > > We are waiting on this infra review to pass - to create the > oslo.vmware git repo. > https://review.openstack.

Re: [openstack-dev] [Nova] Bug Triage Day Proposal - Friday 7th February

So untouched bugs: ~200 -> ~130 Awesome. Hope the US guys (and anyone else who is till working) have a good afternoon brining that down further. Anyways, I am going to have my dinner, because I like in the UK, and I have to play my Tuba this evening. johnthetubaguy On 7 February 2014 08:12, Joh

Re: [openstack-dev] [Tempest][Glance] Bogus Glance service and endpoint required for Tempest?

On Fri, 2014-02-07 at 12:01 -0700, Brian C Thornock wrote: > We are currently developing towards an OpenStack deployment of just > Keystone and Swift. Tempest would not run. We added a bogus Glance > entry to the service catalog with a corresponding bogus Glance > endpoint, and voila, Tempest ran a

[openstack-dev] [Tempest][Glance] Bogus Glance service and endpoint required for Tempest?

Hi Stackers- Is there a reason for the dependency in Tempest for a Glance service and endpoint? We are currently developing towards an OpenStack deployment of just Keystone and Swift. Tempest would not run. We added a bogus Glance entry to the service catalog with a corresponding bogus Glance end

Re: [openstack-dev] [nova][baremetal] Support configurable inject items in nova Bare-metal

On Fri, Feb 7, 2014 at 2:01 AM, Taurus Cheung wrote: > Hi, > > > > I am working on deploying images to bare-metal machines using nova > bare-metal. In current design, some files like hostname, network config > file and meta.json are injected into the image before writing to bare-metal > machines.

Re: [openstack-dev] [nova][baremetal] Partition layout of image used in nova bare-metal

On Fri, Feb 7, 2014 at 2:00 AM, Taurus Cheung wrote: > Hi, > > > > I am working on deploying images to bare-metal machines using nova > bare-metal. In current design, nova bare-metal would first write a > partition layout of root partition and swap partition, then write the image > to root partit

Re: [openstack-dev] [WSME] Can't install WSME 0.6 due to ipaddr library

According to https://groups.google.com/d/msg/ipaddr-py-dev/T8jV4csZUE4/cOjEdimzRD4J , 2.1.11 version just got uploaded to PyPI, so things should get back to normal. On Fri, Feb 7, 2014 at 9:36 PM, Yuriy Taraday wrote: > The simplest way to do so is to add caching to pip and put the file to > ap

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

Hello, Vish! I hope you can provide some historical data. On Fri, Feb 7, 2014 at 9:37 PM, Vishvananda Ishaya wrote: > > To be clear, since many people weren’t around in ye olde days, nova > started using tornado. We exchanged tornado for twisted, and finally moved > to eventlet. People have sugge

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

I want to address some of Chuck’s post, but I think we should come up with a list of requirements. Replies to Chuck inline, and then some requirements below: On Feb 7, 2014, at 8:38 AM, Chuck Thier wrote: > Concurrency is hard, let's blame the tools! > > Any lib that we use in python is going

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

On Feb 7, 2014, at 8:21 AM, Jesse Noller wrote: > > On Feb 7, 2014, at 1:51 AM, Chris Behrens wrote: > >> >> On Feb 6, 2014, at 11:07 PM, Joshua Harlow wrote: >> >>> +1 >>> >>> To give an example as to why eventlet implicit monkey patch the world isn't >>> especially great (although it's

Re: [openstack-dev] [WSME] Can't install WSME 0.6 due to ipaddr library

The simplest way to do so is to add caching to pip and put the file to appropriate place in the cache. You can add this to /root/.pip/pip.conf: [global] download_cache = /var/cache/pip And then put the file to /var/cache/pip/https%3A%2F%2Fgoogledrive.com%2Fhost%2F0Bwh63zyus-UlZ1dxQ08zczVRbXc%2Fip

Re: [openstack-dev] [nova][baremetal] Status of nova baremetal and ironic

Hi Taurus, You are correct Ironic is under rapid development right now, there are several patches in flight right now critical to Ironic. There have been successful tests using Ironic to boot both vm's and real hardware, but at this time I would say we are just about out of alpha and entering bata

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

On Feb 7, 2014, at 11:12 AM, Chris Behrens wrote: > > On Feb 7, 2014, at 8:21 AM, Jesse Noller wrote: > >> It seems that baking concurrency models into the individual clients / >> services adds some opinionated choices that may not scale, or fit the needs >> of a large-scale deployment. Thi

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

On Feb 7, 2014, at 8:21 AM, Jesse Noller wrote: > It seems that baking concurrency models into the individual clients / > services adds some opinionated choices that may not scale, or fit the needs > of a large-scale deployment. This is one of the things looking at the client > tools I’ve not

Re: [openstack-dev] [Neutron][QA] Making tests symmetric again

On Feb 7, 2014, at 10:16 AM, Matthew Treinish mailto:mtrein...@kortar.org>> wrote: So the flag to make tenant isolation was always a temporary thing just for neutron so we could work out stabilizing things. It's been on by default for all the other jobs for as long as I can remember. If you thi

[openstack-dev] oslo.config improvements

I've been working on the code that generates our configuration docs. A couple week ago, I rewrote most of it to address some major problems, most notably its inability to distinguish same-named options in different groups. I've tried to reuse bits from the oslo-incubator code to generate sample co

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

Concurrency is hard, let's blame the tools! Any lib that we use in python is going to have a set of trade-offs. Looking at a couple of the options on the table: 1. Threads: Great! code doesn't have to change too much, but now that code *will* be preempted at any time, so now we have to worry a

Re: [openstack-dev] [nova] Making periodic tasks config consistent.

I think I mangled my explanation a bit, sorry. I'm suggesting 2 things: 1 - make Nova's use of 0-length polling period consistent with the Oslo decorator. Nova-only. 2 - have Oslo's decorator use 0-length to mean "call regularly at the default period", rather than "call whenever any other t

Re: [openstack-dev] [WSME] Can't install WSME 0.6 due to ipaddr library

On Fri Feb 7 08:25:24 2014, Ilya Shakhat wrote: > Hi Doug, > > I'm trying to install WSME 0.6, but today it fails due to inability to > install ipaddr dependency. > > Pip output: > Downloading/unpacking ipaddr (from WSME) > You are installing a potentially insecure and unverifiable file. > Futu

Re: [openstack-dev] [WSME] Can't install WSME 0.6 due to ipaddr library

According to ipaddr's homepage: https://code.google.com/p/ipaddr-py/ , they've recently moved releases to Google Drive. And if you try to download them with your browser, you get: Sorry, you can't view or download this file at this time. > Too many users have viewed or downloaded this file recentl

Re: [openstack-dev] [Openstack-docs] Conventions on naming

On 02/06/2014 05:52 PM, Jonathan Bryce wrote: > > On Feb 6, 2014, at 2:56 AM, Andreas Jaeger wrote: >> >> Should other OpenStack projects adjust, e.g. Horizon shows >> "Orchestration". I guess this is fine - isn't it? > > Yes, Horizon’s usage is fine, and in my opinion preferred for clarity. W

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

On Feb 7, 2014, at 1:51 AM, Chris Behrens wrote: > > On Feb 6, 2014, at 11:07 PM, Joshua Harlow wrote: > >> +1 >> >> To give an example as to why eventlet implicit monkey patch the world isn't >> especially great (although it's what we are currently using throughout >> openstack). >> >> T

[openstack-dev] [Climate] Meeting minutes

Thanks everyone who took part in our weekly meeting :) Meeting minutes are: Minutes: http://eavesdrop.openstack.org/meetings/climate/2014/climate.2014-02-07-15.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/climate/2014/climate.2014-02-07-15.00.txt Log: http://eavesdrop.opensta

[openstack-dev] [qa] Adding support for a new plugin

Hi everybody, We have a new Neutron plugin being reviewed (approved for the Icehouse-3 milestone) and would like to add the corresponding file in devstack. Not being sure as to how to do this, I opened a blueprint ( https://blueprints.launchpad.net/devstack/+spec/ibm-sdnve-plugin-support ) and s

Re: [openstack-dev] [Neutron][QA] Making tests symmetric again

On Fri, Feb 07, 2014 at 03:58:28PM +0100, Salvatore Orlando wrote: > I just spoke with Eugene over IRC and the problem is that the test attempts > to connect to an instance over a private network, which cannot work in > isolated mode. > This patch will skip the load balancing scenario: > https://re

Re: [openstack-dev] [Neutron][QA] Making tests symmetric again

I just spoke with Eugene over IRC and the problem is that the test attempts to connect to an instance over a private network, which cannot work in isolated mode. This patch will skip the load balancing scenario: https://review.openstack.org/#/c/71898/ So thankfully, there is no new neutron issue.

Re: [openstack-dev] pep8 barfs on long URL

On Fri, Feb 07 2014, Jay Pipes wrote: > On Fri, 2014-02-07 at 14:25 +, Matthew Booth wrote: >> I have a comment which references a long URL. The URL itself is longer >> than 80 characters. Jenkins has flagged this as a pep8 failure, because >> the line is longer than 80 characters. >> >> This

Re: [openstack-dev] pep8 barfs on long URL

On Fri, 2014-02-07 at 15:36 +0100, Julien Danjou wrote: > On Fri, Feb 07 2014, Jay Pipes wrote: > > > On Fri, 2014-02-07 at 14:25 +, Matthew Booth wrote: > >> I have a comment which references a long URL. The URL itself is longer > >> than 80 characters. Jenkins has flagged this as a pep8 fail

Re: [openstack-dev] pep8 barfs on long URL

On Fri, 2014-02-07 at 14:25 +, Matthew Booth wrote: > I have a comment which references a long URL. The URL itself is longer > than 80 characters. Jenkins has flagged this as a pep8 failure, because > the line is longer than 80 characters. > > This is an instance where in the past I have alway

Re: [openstack-dev] pep8 barfs on long URL

On Fri, 2014-02-07 at 14:25 +, Matthew Booth wrote: > I have a comment which references a long URL. The URL itself is longer > than 80 characters. Jenkins has flagged this as a pep8 failure, because > the line is longer than 80 characters. > > This is an instance where in the past I have alway

[openstack-dev] pep8 barfs on long URL

I have a comment which references a long URL. The URL itself is longer than 80 characters. Jenkins has flagged this as a pep8 failure, because the line is longer than 80 characters. This is an instance where in the past I have always applied common sense to the line length limit. You either have a

[openstack-dev] [Neutron][QA] Making tests symmetric again

Hi, By merging patch https://review.openstack.org/#/c/53459/, full tenant isolation has been turned on for neutron API tests. We have executed a few experimental checks before merging and we found out that the isolated jobs were always passing. However, the gating jobs both in tempest and nova do

[openstack-dev] [WSME] Can't install WSME 0.6 due to ipaddr library

Hi Doug, I'm trying to install WSME 0.6, but today it fails due to inability to install ipaddr dependency. Pip output: Downloading/unpacking ipaddr (from WSME) You are installing a potentially insecure and unverifiable file. Future versions of pip will default to disallowing insecure files. H

Re: [openstack-dev] [All] Python 3.3 gates are failing

The same with swiftclient, hacking, openstacksdk and others - http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiJ2FzY2lpJyBjb2RlYyBjYW4ndCBkZWNvZGUgYnl0ZSAweGMzIGluIHBvc2l0aW9uIDkwNTU6IG9yZGluYWwgbm90IGluIHJhbmdlKDEyOClcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcG

[openstack-dev] [All] Python 3.3 gates are failing

Recently python3.3 jobs started failing. Noticed this in python-solumclient project but it looks like a common problem. python-solumclient http://logs.openstack.org/72/57172/2/check/gate-python-solumclient-python33/8da814d/console.html python-novaclient http://logs.openstack.org/46/71846/1/che

[openstack-dev] [nova][baremetal] Partition layout of image used in nova bare-metal

Hi, I am working on deploying images to bare-metal machines using nova bare-metal. In current design, nova bare-metal would first write a partition layout of root partition and swap partition, then write the image to root partition. It seems that the logic assumes there's no partition table ins

[openstack-dev] [nova][baremetal] Support multiple image write workers in nova bare-metal

Hi, I am working on deploying images to bare-metal machines using nova bare-metal. In existing implementation in nova-baremetal-deploy-helper.py, there's only 1 worker to write image to bare-metal machines. If there is a number of bare-metal instances to deploy, they need to queue up and wait t

[openstack-dev] [nova][baremetal] Support configurable inject items in nova Bare-metal

Hi, I am working on deploying images to bare-metal machines using nova bare-metal. In current design, some files like hostname, network config file and meta.json are injected into the image before writing to bare-metal machines. Can we control which items to be injected into the image? Regards

[openstack-dev] [nova][baremetal] Delete disk image in nova after deploy image to bare-metal machine

Hi I am working on deploying images to bare-metal machines using nova bare-metal. In current architecture, disk images are kept at /var/lib/nova/instances after the image is written (by dd) to the hard disk of bare-metal machines. But these disk images file are no longer needed. Does nova bare

[openstack-dev] [nova][baremetal] Status of nova baremetal and ironic

I am working on deploying images to bare-metal machines using nova bare-metal. So far working well. I know Ironic is under rapid development. Could I know the current status of Ironic and the suitable time to shift from nova baremetal to Ironic? Regards, Taurus _

Re: [openstack-dev] [keystone] Integrating with 3rd party DB

- Original Message - > From: "Noorul Islam K M" > To: "Jamie Lennox" > Cc: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Friday, 7 February, 2014 7:13:20 PM > Subject: Re: [openstack-dev] [keystone] Integrating with 3rd party DB > > Jamie Lennox writes: >

Re: [openstack-dev] [nova][glance] bp: glance-snapshot-tasks

Hi Josh, >> I think u are referring to the following: https://blueprints.launchpad.net/nova/+spec/glance-snapshot-tasks Yes, you're right. >> Can u describe the #2 part in more detail. Do some of the drivers already implement these new steps? I've mostly investigated snapshot method in libvirt

Re: [openstack-dev] [Neutron] [ML2] l2-pop bugs review

Thanks to you, Kyle. I proposed a backport [1] of the review 63913 you approved. [1] https://review.openstack.org/#/c/71821/ Édouard. On Thu, Feb 6, 2014 at 6:04 PM, Kyle Mestery wrote: > > On Feb 6, 2014, at 3:09 AM, Édouard Thuleau wrote: > > > Hi all, > > > > Just to point 2 reviews [1] &

Re: [openstack-dev] [keystone] Integrating with 3rd party DB

Jamie Lennox writes: > - Original Message - >> From: "Noorul Islam K M" >> To: "Dolph Mathews" >> Cc: "OpenStack Development Mailing List (not for usage questions)" >> >> Sent: Friday, 7 February, 2014 2:00:34 PM >> Subject: Re: [openstack-dev] [keystone] Integrating with 3rd party DB

Re: [openstack-dev] [Nova] Bug Triage Day Proposal - Friday 7th February

+1 - Original Message - From: "John Garbutt" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Friday, February 7, 2014 9:12:42 AM Subject: Re: [openstack-dev] [Nova] Bug Triage Day Proposal - Friday 7th February Just a quick reminder, its bug day! Lets

Re: [openstack-dev] [Neutron] ryu-ml2-driver

> hi, > > we (Ryu project) are currently working on a new version of > Ryu neutron plugin/agent. we have a blueprint for it > waiting for review/approval. can you please take a look? thanks. > https://blueprints.launchpad.net/neutron/+spec/ryu-ml2-driver we uploaded ready-to-review code to ger

Re: [openstack-dev] [keystone] Integrating with 3rd party DB

- Original Message - > From: "Noorul Islam K M" > To: "Dolph Mathews" > Cc: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Friday, 7 February, 2014 2:00:34 PM > Subject: Re: [openstack-dev] [keystone] Integrating with 3rd party DB > > Dolph Mathews writes:

Re: [openstack-dev] [Nova] Bug Triage Day Proposal - Friday 7th February

Just a quick reminder, its bug day! Lets collaborate in #openstack-nova We can track progress here: http://webnumbr.com/untouched-nova-bugs And later progress: http://status.openstack.org/bugday Get those bugs tagged: https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW Ta

Re: [openstack-dev] question of vcpu-memory-hotplug progress

> -Original Message- > From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] > Sent: Wednesday, January 29, 2014 3:02 PM > To: OpenStack Development Mailing List (not for usage questions) > Cc: Jinbo (Justin) > Subject: Re: [openstack-dev] question of vcpu-memory-hotplug progress > >> Sub