Re: [openstack-dev] [Fuel] CLI api for working with granular deployment model

On Fri, Feb 6, 2015 at 11:16 PM, Mike Scherbakov wrote: > Dmitry, > thanks for sharing CLI options. I'd like to clarify a few things. > > > Also very important to understand that if task is mapped to role > controller, but node where you want to apply that task doesn't have this > role - it wont

Re: [openstack-dev] BUG in OpenVSwitch Version ovs-vswitchd (Open vSwitch) 1.4.6

On Sat, Feb 7, 2015 at 5:09 AM, masoom alam wrote: > raise DistributionNotFound(req)\npkg_resources.DistributionNotFound: > alembic<0.6.4,>=0.4.1\n' > It looks like your system is failing to find a version of alembic that satisfies those requirements. In your last post on this issue you said yo

Re: [openstack-dev] [Fuel] CLI api for working with granular deployment model

Dmitry, thanks for sharing CLI options. I'd like to clarify a few things. > Also very important to understand that if task is mapped to role controller, but node where you want to apply that task doesn't have this role - it wont be executed. Is there a particular reason why we want to restrict a u

[openstack-dev] BUG in OpenVSwitch Version ovs-vswitchd (Open vSwitch) 1.4.6

Hi every one, Can any one spot why the following bug will appear in Openstack leaving all services of Neutron to unusable state? To give you an idea that I was trying: "I tried to configure 173.39.237.0 ip to a VM, with the CIDR 173.39.236.0/23, however the OVS gave error and now all the neu

Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody should know about Galera

Thanks for the additional details Peter. This confirms the parts I'd deduced from the docs I could find, and is useful knowledge. On Sat Feb 07 2015 at 2:24:23 AM Peter Boros wrote: > > - Like many others said it before me, consistent reads can be achieved > with wsrep_causal_reads set on in the

Re: [openstack-dev] [Magnum] Scheduling for Magnum

On Sat, 2015-02-07 at 00:44 +, Adrian Otto wrote: > Magnum Team, > > In our initial spec, we addressed the subject of resource scheduling. Our > plan was to begin with a naive scheduler that places resources on a specified > Node and can sequentially fill Nodes if one is not specified. > >

[openstack-dev] [Magnum] Scheduling for Magnum

Magnum Team, In our initial spec, we addressed the subject of resource scheduling. Our plan was to begin with a naive scheduler that places resources on a specified Node and can sequentially fill Nodes if one is not specified. Magnum supports multiple conductor backends[1], one of which is our

Re: [openstack-dev] Need nova-specs core reviews for Scheduler spec

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/06/2015 12:15 PM, Nikola Đipanov wrote: > I've left a comment on the spec - basically I don't think this is an > approach we should take. Understood. There have been so many back-and-forth changes, with each making the solution more and more co

[openstack-dev] [cinder] Volume Replication and Migration bug triage ...

All, In discussion with Mike Perez earlier this week the following bugs were highlighted in Volume Migration and Volume Replication. IBM is focusing on investigating and resolving these bugs. I will be putting out updates as we progress towards resolution of these issues. Replication: /h

Re: [openstack-dev] [oslo] oslo.versionedobjects repository is ready for pre-import review

Overall looks good to me and the unit tests are passing locally. I'm wondering about some of the stuff that was left commented out without a FIXME and left a couple of comments about them, but I'm mostly assuming they were just things commented for testing that weren't removed later. -Ben On 02/

Re: [openstack-dev] [Magnum] Mid-Cycle Meetup Planning

Team, Our dates have been set as 2015-03-02 and 2015-03-03. Wiki (With location, map, calendar links, agenda planning link, and links to tickets): https://wiki.openstack.org/wiki/Magnum/Midcycle RSVP Tickets: https://www.eventbrite.com/e/magnum-midcycle-meetup-tickets-15673361446 Please be sur

[openstack-dev] [nova] Feature Freeze Exception Request (Use libvirt storage pools)

Hi, I would like to request a non-priority feature freeze exception for the "Use libvirt storage pools" blueprint [1]. The blueprint introduces a new image backed type that uses libvirt storage pools, and is designed to supercede several of the existing image backends for Nova. Using libvirt st

[openstack-dev] [nova] Feature Freeze Exception Request for Quiesce boot from volume instances

Hello, I'd like to request a feature freeze exception for the change https://review.openstack.org/#/c/138795/ . This patch makes live volume-boot instance snapshots consistent by quiescing instances before snapshotting. Quiescing for image-boot instances are already merged in the libvirt driver

[openstack-dev] [nova] will the real v2.1/v3 API status please stand up?

I'm not going to hide it, I don't know what's going on with the v2.1 API status, i.e. what is the criteria to that thing dropping it's 'experimental' label? I wasn't at the mid-cycle meetup for Kilo but even for Juno I'll admit I was a bit lost. It's not my fault, I'm more good looks than brai

[openstack-dev] [nova] Feature Freeze Exception Request

Hi all, I’d like to ask a FFE for the Hyper-V Rescue feature Patch: https://review.openstack.org/#/c/127159/ Blueprint: https://blueprints.launchpad.net/nova/+spec/hyper-v-rescue It’s a feature parity blueprint with no impact outside of the Hyper-V driver. It already received a +2 (curre

Re: [openstack-dev] [devstack] how to use a devstack external plugin in gate testing

On Fri, Feb 6, 2015 at 1:36 PM, Sean Dague wrote: > For those that didn't notice, on the Devstack team we've started to push > back on new in-tree support for all the features. That's intentional. > We've got an external plugin interface now - > > http://docs.openstack.org/developer/devstack/plug

Re: [openstack-dev] [Murano][Heat][Mistral] Use and adoption of YAQL

Stan, Alex, Renat: Should we migrate to YAQL 1.0 now? and stop using the initial one? What’s the delta? Still short on the docs :) but I understand they’re coming up. https://github.com/stackforge/yaql/tree/master/doc/source Cheers, Dmitri. On Jan 16, 2015, at 6:46 AM, Stan Lagun wrote:

Re: [openstack-dev] [nova] release request for python-novaclient

Before releasing a new python-novaclient we should make sure novaclient is capped on stable branches so we don't break the world yet again. On Fri, Feb 6, 2015 at 8:17 AM, Matt Riedemann wrote: > We haven't done a release of python-novaclient in awhile (2.20.0 was > released on 2014-9-20 before

Re: [openstack-dev] [python-cinderclient] Return request ID to caller

On Thu, Feb 5, 2015 at 11:24 PM, Kekane, Abhishek < abhishek.kek...@nttdata.com> wrote: > Hi Devs, > > > > This change is not backward compatible and to do not break OpenStack > services which are using cinder-client, > > we need to first make provision in these consumer services to handle > cind

Re: [openstack-dev] [Fuel] CLI api for working with granular deployment model

> Thank you for the excellent run-down of the CLI commands. I assume this > will make its way into the developer documentation? I would like to know if > you could point me to more information about the inner workings of granular > deployment. Currently it's challenging to debug issues related to g

Re: [openstack-dev] [cinder] Why not allow deleting volume from a CG ?

As Mike said, allowing deletion of a single volume from a CG is error prone. User could be deleting a single volume without knowing that it is part of a CG. The new Modify CG feature for Kilo allows you to remove a volume from CG and you can delete it as a separate operation. When user remove

Re: [openstack-dev] [Fuel] CLI api for working with granular deployment model

Dmitriy, Thank you for the excellent run-down of the CLI commands. I assume this will make its way into the developer documentation? I would like to know if you could point me to more information about the inner workings of granular deployment. Currently it's challenging to debug issues related to

[openstack-dev] [devstack] how to use a devstack external plugin in gate testing

For those that didn't notice, on the Devstack team we've started to push back on new in-tree support for all the features. That's intentional. We've got an external plugin interface now - http://docs.openstack.org/developer/devstack/plugins.html#externally-hosted-plugins, and have a few projects li

[openstack-dev] [nova] FFE request for passing capabilities in the flavor to ironic

Hi, I would like to ask for a feature freeze exception for passing capabilities in the flavor to Ironic: https://blueprints.launchpad.net/nova/+spec/pass-flavor-capabilities-to-ironic-virt-driver Addressed by: https://review.openstack.org/136104 Pass on the capabilities in

Re: [openstack-dev] [horizon][keystone] SSO

>From the sound of things, we're not actually talking about SSO. If so, we >would not be talking about the design of a login screen. An SSO application such as Horizon would not have a login page. If the user was logged in already through corporate/organisation SSO page, nothing would appear b

Re: [openstack-dev] [horizon][keystone]

On 02/05/2015 04:20 AM, Anton Zemlyanov wrote: Hi, I guess "Credentials" is login and password. I have no idea what is "Default Protocol" or "Discovery Service". The proposed UI is rather embarrassing. No it is not. It is a rapid prototyping technique to get things to fail fast, and to get f

Re: [openstack-dev] [horizon][keystone]

On 02/04/2015 03:54 PM, Thai Q Tran wrote: Hi all, I have been helping with the websso effort and wanted to get some feedback. Basically, users are presented with a login screen where they can select: credentials, default protocol, or discovery service. If user selects credentials, it works e

Re: [openstack-dev] [cinder] Why not allow deleting volume from a CG ?

On 15:51 Fri 06 Feb , Nilesh P Bhosale wrote: > I understand this is as per design, but curious to understand logic behind > this. > Why not allow deletion of volumes form the CG? at least when there are no > dependent snapshots. >From the review [1], this is because allowing a volume that

Re: [openstack-dev] [infra][project-config][oslo.messaging] Pre-driver requirements split-up initiative

On 02/06/2015 10:12 AM, Doug Hellmann wrote: > > > On Fri, Feb 6, 2015, at 07:37 AM, Denis Makogon wrote: >> Hello to All. >> >> >> As part of oslo.messaging initiative to split up requirements into >> certain >> list of per messaging driver dependencies >>

Re: [openstack-dev] Need nova-specs core reviews for Scheduler spec

On 02/06/2015 02:15 PM, Ed Leafe wrote: > At the mid-cycle we discussed the last spec for the scheduler cleanup: > Isolate Scheduler DB for Instances > > https://review.openstack.org/#/c/138444/ > > There was a lot of great feedback from those discussions, and that has been > incorporated into

Re: [openstack-dev] [Murano] SQLite support - drop or not?

Drop. It is wasting cycles, and not something we should use in production. Migrations specific to SQLPlus are the most time consuming work-arounds we have. SQLPlus does not suit our development approach. On 02/03/2015 01:32 PM, Georgy Okrokvertskhov wrote: I think we should switch to clean

[openstack-dev] [neutron][nova] GRE Performance Problem, Multi-queue and Bridge MTUs

Hello, I was having serious network issues using GRE and I have been tracking it for a few weeks. Finally, I solved the issue but it needs a proper fix. To summarize, I need a way to set MTU settings of br-int and br-tun interfaces, enable MQ support in libvirt, and run "ethtool -L eth0 combined N

[openstack-dev] [cinder] Why not allow deleting volume from a CG ?

Hi All, I see the following error, while deleting a volume from a consistency group: $ [admin]cinder delete vol1 Delete for volume vol1 failed: Bad Request (HTTP 400) (Request-ID: req-7c958443-edb2-434f-82a2-4254ab357e99) ERROR: Unable to delete any of specified volumes. And when I tried to deb

Re: [openstack-dev] [heat] operators vs users for choosing convergence engine

Excerpts from Zane Bitter's message of 2015-02-06 06:25:57 -0800: > On 03/02/15 14:12, Clint Byrum wrote: > > The visible change in making things parallel was minimal. In talking > > about convergence, it's become clear that users can and should expect > > something radically different when they is

[openstack-dev] [all][oslo.db] Repeatable Read considered harmful

I was surprised recently to discover that MySQL uses repeatable read for transactions by default. Postgres uses read committed by default, and SQLite uses serializable. We don't set the isolation level explicitly anywhere, so our applications are running under different isolation levels depending o

Re: [openstack-dev] Status of NovaOrchestration

On 2/6/2015 10:44 AM, Cameron Seader wrote: Nevermind answered in IRC On 02/06/2015 09:33 AM, Cameron Seader wrote: Is this something that was implemented? If so which version of OpenStack? https://wiki.openstack.org/wiki/NovaOrchestration#Long_Running_Transactions_in_Nova Thanks, Maybe

Re: [openstack-dev] [infra][project-config][oslo.messaging] Pre-driver requirements split-up initiative

Sounds good to me Doug. +1 for a spec since this will affect every project. -- dims On Fri, Feb 6, 2015 at 11:12 AM, Doug Hellmann wrote: > > > On Fri, Feb 6, 2015, at 07:37 AM, Denis Makogon wrote: >> Hello to All. >> >> >> As part of oslo.messaging initiative to split up requirements into >> c

Re: [openstack-dev] Status of NovaOrchestration

Nevermind answered in IRC On 02/06/2015 09:33 AM, Cameron Seader wrote: > Is this something that was implemented? If so which version of OpenStack? > https://wiki.openstack.org/wiki/NovaOrchestration#Long_Running_Transactions_in_Nova > > Thanks, > -- Cameron Seader Sr. Systems Engineer SUSE c.

Re: [openstack-dev] [horizon][keystone]

But selecting from a list is harder then from a grid. A grid would give you ample room for icons, which also make finding what your looking for easier. Having a bit more space makes selecting the thing you want with a mouse(or finger on a tablet) easier. To make it not visually overloaded, you

[openstack-dev] Status of NovaOrchestration

Is this something that was implemented? If so which version of OpenStack? https://wiki.openstack.org/wiki/NovaOrchestration#Long_Running_Transactions_in_Nova Thanks, -- Cameron Seader Sr. Systems Engineer SUSE c...@suse.com (W)208-577-6857 (M)208-420-2167 Register for SUSECon 2015 www.susecon.c

[openstack-dev] [nova] release request for python-novaclient

We haven't done a release of python-novaclient in awhile (2.20.0 was released on 2014-9-20 before the Juno release). It looks like there are some important feature adds and bug fixes on master so we should do a release, specifically to pick up the change for keystone v3 support [1]. So can t

Re: [openstack-dev] [infra][project-config][oslo.messaging] Pre-driver requirements split-up initiative

On Fri, Feb 6, 2015, at 07:37 AM, Denis Makogon wrote: > Hello to All. > > > As part of oslo.messaging initiative to split up requirements into > certain > list of per messaging driver dependencies > > > it was figured that we need to find a way to use

Re: [openstack-dev] [infra][project-config][oslo.messaging] Pre-driver requirements split-up initiative

On Fri, Feb 6, 2015 at 5:54 PM, Doug Hellmann wrote: > > > On Fri, Feb 6, 2015, at 09:56 AM, Denis Makogon wrote: > > On Fri, Feb 6, 2015 at 4:16 PM, Donald Stufft wrote: > > > > > > > > > On Feb 6, 2015, at 9:00 AM, Jeremy Stanley > wrote: > > > > > > > > On 2015-02-06 14:37:08 +0200 (+0200),

Re: [openstack-dev] [nova] Feature Freeze Exception Request

Of course i asked Daniel directly prior to publicly declaring him a sponsor!!! :-) 2015-02-06 16:55 GMT+01:00 Matt Riedemann : > > > On 2/6/2015 7:28 AM, Silvan Kaiser wrote: > >> Hello! >> >> I am requesting a feature freeze exception for Kilo-2 milestone >> regarding https://review.openstack.or

Re: [openstack-dev] [nova] Feature Freeze Exception Request

On Fri, Feb 06, 2015 at 09:55:42AM -0600, Matt Riedemann wrote: > > > On 2/6/2015 7:28 AM, Silvan Kaiser wrote: > >Hello! > > > >I am requesting a feature freeze exception for Kilo-2 milestone > >regarding https://review.openstack.org/#/c/110722/ . > > > >This change adds support for using the Qu

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On 02/06/2015 07:49 AM, Sean Dague wrote: On 02/06/2015 07:39 AM, Alexandre Levine wrote: Rushi, We're adding new tempest tests into our stackforge-api/ec2-api. The review will appear in a couple of days. These tests will be good for running against both nova/ec2-api and stackforge/ec2-api. As

Re: [openstack-dev] [nova] Feature Freeze Exception Request

On 2/6/2015 7:28 AM, Silvan Kaiser wrote: Hello! I am requesting a feature freeze exception for Kilo-2 milestone regarding https://review.openstack.org/#/c/110722/ . This change adds support for using the Quobyte Storage system for provisioning images in Nova. It works in conjunction with the

Re: [openstack-dev] [infra][project-config][oslo.messaging] Pre-driver requirements split-up initiative

On Fri, Feb 6, 2015, at 09:56 AM, Denis Makogon wrote: > On Fri, Feb 6, 2015 at 4:16 PM, Donald Stufft wrote: > > > > > > On Feb 6, 2015, at 9:00 AM, Jeremy Stanley wrote: > > > > > > On 2015-02-06 14:37:08 +0200 (+0200), Denis Makogon wrote: > > >> As part of oslo.messaging initiative to spli

Re: [openstack-dev] [nova] stuck patches at the nova IRC meeting

On 2/6/2015 7:20 AM, Sean Dague wrote: Ok, my bad. When I proposed this part of the Nova meeting I was also thinking about "lost" patches where a couple of weeks had gone by without any negative feedback and the patch author got a chance to advocate for it. That's how we used it in Tempest meet

Re: [openstack-dev] [Trove] Core reviewer update

Thanks all for the show of support! Victoria, Peter, and Edmond -- welcome to core. Thanks Michael, and Tim for all the hard work on Trove. Cheers, Nikhil On Thu, Feb 5, 2015 at 2:38 PM, McReynolds, Auston wrote: > +1 > > welcome aboard peter + victoria + edmond! > > From: Nikhil Manchanda

[openstack-dev] [nova] Feature Freeze Exception Request

Hi, I would like to request a feature freeze exception for the "Websockify security proxy framework" blueprint [1]. The blueprint introduces a framework for defining "security drivers" for the connections between the websocket proxy and the hypervisor, and provides a TLS driver for VNC connection

Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody should know about Galera

Hi Angus and everyone, I would like to reply for a couple of things: - The behavior of overlapping transactions is dependent on the transaction isolation level, even in the case of the single server, for any database. This was pointed out by others earlier as well. - The deadlock error from Galer

Re: [openstack-dev] Which repo should the API WG use?

Top posting to wrap this up. During the last API WG meeting [1] we discussed this topic. Of the 8 people who voted, it was unanimous and we agreed [2] to use the api-wg repo to write our guidelines. This email thread wasn’t conclusive on the subject so we’ll be moving forward with the result o

Re: [openstack-dev] [infra][project-config][oslo.messaging] Pre-driver requirements split-up initiative

On Fri, Feb 6, 2015 at 4:16 PM, Donald Stufft wrote: > > > On Feb 6, 2015, at 9:00 AM, Jeremy Stanley wrote: > > > > On 2015-02-06 14:37:08 +0200 (+0200), Denis Makogon wrote: > >> As part of oslo.messaging initiative to split up requirements into > >> certain list of per messaging driver depend

Re: [openstack-dev] [infra][project-config][oslo.messaging] Pre-driver requirements split-up initiative

On Fri, Feb 6, 2015 at 4:00 PM, Jeremy Stanley wrote: > On 2015-02-06 14:37:08 +0200 (+0200), Denis Makogon wrote: > > As part of oslo.messaging initiative to split up requirements into > > certain list of per messaging driver dependencies > [...] > > I'm curious what the end goal is here... when

[openstack-dev] What's Up Doc? Feb 6 2014

News from docland, here we go. Take a minute to click over to http://docs.openstack.org to see the new landing page! Refresh to see even more characters added to the docs. :) The openstackdocstheme, a Sphinx theme that replicates the www.openstack.org header for docs content pages in RST, is rele

[openstack-dev] [Fuel] CLI api for working with granular deployment model

Hello folks, Not long ago we added necessary commands in fuel client to work with granular deployment configuration and API. So, you may know that configuration is stored in fuel-library, and uploaded into database during bootstrap of fuel master. If you want to change/add some tasks right on mas

Re: [openstack-dev] [heat] operators vs users for choosing convergence engine

On 03/02/15 14:12, Clint Byrum wrote: The visible change in making things parallel was minimal. In talking about convergence, it's become clear that users can and should expect something radically different when they issue stack updates. I'd love to say that it can be done to just bind convergenc

Re: [openstack-dev] [Openstack-operators] [Telco][NFV][infra] Review process of TelcoWG use cases

- Original Message - > From: "Anthony Veiga" > To: "OpenStack Development Mailing List (not for usage questions)" > > > > On Feb 6, 2015, at 8:17 , Jeremy Stanley wrote: > > > > On 2015-02-06 12:11:40 +0100 (+0100), Marc Koderer wrote: > > [...] > >> Therefore I uploaded one of them (

Re: [openstack-dev] [infra][project-config][oslo.messaging] Pre-driver requirements split-up initiative

> On Feb 6, 2015, at 9:00 AM, Jeremy Stanley wrote: > > On 2015-02-06 14:37:08 +0200 (+0200), Denis Makogon wrote: >> As part of oslo.messaging initiative to split up requirements into >> certain list of per messaging driver dependencies > [...] > > I'm curious what the end goal is here... when

Re: [openstack-dev] [infra][project-config][oslo.messaging] Pre-driver requirements split-up initiative

On 2015-02-06 14:37:08 +0200 (+0200), Denis Makogon wrote: > As part of oslo.messaging initiative to split up requirements into > certain list of per messaging driver dependencies [...] I'm curious what the end goal is here... when someone does `pip install oslo.messaging` what do you/they expect

Re: [openstack-dev] [neutron] looking for status of an old wiki page work item

Yes, that looks much more detailed, thank you! Ryan (having finished a minor wiki page edit) Salvatore Orlando wrote on 02/05/2015 06:40:44 PM: > From: Salvatore Orlando > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 02/05/2015 06:42 PM > Subject: Re: [opensta

Re: [openstack-dev] [Openstack-operators] [Telco][NFV][infra] Review process of TelcoWG use cases

> On Feb 6, 2015, at 8:17 , Jeremy Stanley wrote: > > On 2015-02-06 12:11:40 +0100 (+0100), Marc Koderer wrote: > [...] >> Therefore I uploaded one of them (Session Border Controller) to >> the Gerrit system into the sandbox repo: >> >>https://review.openstack.org/#/c/152940/1 > [...] > >

Re: [openstack-dev] [nova] FFE request for instance tagging

On 02/06/2015 08:30 AM, Sergey Nikitin wrote: Hello. I'd like to ask for a feature freeze exception for the instance tags API extension: https://review.openstack.org/#/c/128940/ spec https://review.openstack.org/#/c/127281/ blueprint was approved, but its status was changed to "Pending Approv

Re: [openstack-dev] [nova] Feature Freeze Exception Request

On 02/06/2015 08:28 AM, Silvan Kaiser wrote: Hello! I am requesting a feature freeze exception for Kilo-2 milestone regarding https://review.openstack.org/#/c/110722/ . This change adds support for using the Quobyte Storage system for provisioning images in Nova. It works in conjunction with th

[openstack-dev] [nova] FFE request for instance tagging

Hello. I'd like to ask for a feature freeze exception for the instance tags API extension: https://review.openstack.org/#/c/128940/ spec https://review.openstack.org/#/c/127281/ blueprint was approved, but its status was changed to "Pending Approval" because of FF. https://blueprints.launchpad.

[openstack-dev] [nova] Feature Freeze Exception Request

Hello! I am requesting a feature freeze exception for Kilo-2 milestone regarding https://review.openstack.org/#/c/110722/ . This change adds support for using the Quobyte Storage system for provisioning images in Nova. It works in conjunction with the Quobyte driver in Cinder (which was merged at

Re: [openstack-dev] [nova] stuck patches at the nova IRC meeting

Ok, my bad. When I proposed this part of the Nova meeting I was also thinking about "lost" patches where a couple of weeks had gone by without any negative feedback and the patch author got a chance to advocate for it. That's how we used it in Tempest meetings. The theory being that engaging in mo

Re: [openstack-dev] [Openstack-operators] [Telco][NFV][infra] Review process of TelcoWG use cases

On 2015-02-06 12:11:40 +0100 (+0100), Marc Koderer wrote: [...] > Therefore I uploaded one of them (Session Border Controller) to > the Gerrit system into the sandbox repo: > > https://review.openstack.org/#/c/152940/1 [...] This looks a lot like the beginnings of a specification which has im

[openstack-dev] Need nova-specs core reviews for Scheduler spec

At the mid-cycle we discussed the last spec for the scheduler cleanup: Isolate Scheduler DB for Instances https://review.openstack.org/#/c/138444/ There was a lot of great feedback from those discussions, and that has been incorporated into the spec. It has been re-reviewed by most of the sched

Re: [openstack-dev] [OpenStack-Infra] Devstack error when running g-reg: 401 Unauthorized

This is likely https://launchpad.net/bugs/1415795 which is fixed by https://review.openstack.org/#/c/151506/ Make sure you have the above change in your devstack and it should work again. Bob From: liuxinguo [mailto:liuxin...@huawei.com] Sent: 06 February 2015 03:08 To: OpenStack Development Ma

[openstack-dev] [nova] kilo progress and feature freeze process

Hi, So we have now released kilo-2 and past the non-priority Feature Freeze for kilo. Please note 5th March is the General FeatureProposalFreeze: https://wiki.openstack.org/wiki/Kilo_Release_Schedule For kilo we agreed to focus on bug fixes, and the other agreed priority 'slots'. The plan is we

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

On 02/06/2015 07:39 AM, Alexandre Levine wrote: > Rushi, > > We're adding new tempest tests into our stackforge-api/ec2-api. The > review will appear in a couple of days. These tests will be good for > running against both nova/ec2-api and stackforge/ec2-api. As soon as > they are there, you'll be

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

Rushi, We're adding new tempest tests into our stackforge-api/ec2-api. The review will appear in a couple of days. These tests will be good for running against both nova/ec2-api and stackforge/ec2-api. As soon as they are there, you'll be more than welcome to add even more. Best regards, A

[openstack-dev] [infra][project-config][oslo.messaging] Pre-driver requirements split-up initiative

Hello to All. As part of oslo.messaging initiative to split up requirements into certain list of per messaging driver dependencies it was figured that we need to find a way to use pip inner dependencies and we were able to do that, short info our solutio

Re: [openstack-dev] [OpenStack Foundation] Finding people to work on the EC2 API in Nova

There seems to be an agreement that people are fine if we improve the in-tree Nova EC2 API more robust by adding proper Tempest tests to it, regardless of the way forward (in-Nova-tree vs out-of-tree repo). But there are also concerns that Tempest is not the right place for these EC2 API tests. Wh

[openstack-dev] [MagnetoDB] Kilo-2 development milestone available

Hello everyone, MagnetoDB Kilo-2 development milestone has been released https://launchpad.net/magnetodb/kilo/kilo-2 Have a nice day, Ilya Sviridov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Telco][NFV][infra] Review process of TelcoWG use cases

Hello everyone, we are currently facing the issue that we don’t know how to proceed with our telco WG use cases. There are many of them already defined but the reviews via Etherpad doesn’t seem to work. I suggest to do a review on them with the usual OpenStack tooling. Therefore I uploaded one of

Re: [openstack-dev] [openstack][nova] Question on rollback live migration at the destination

Robert, Your concern seems to be correct. The bug has already been reported: https://bugs.launchpad.net/nova/+bug/1284719. # Oops, 1 year old bug... Regards, Makkie On 2015/01/27 3:58, Robert Li (baoli) wrote: Hi, I’m looking at rollback_live_migration_at_destination() in compute/manager.py.