Re: [openstack-dev] [trove][stable] [Openstack-stable-maint] Stable check of openstack/trove failed

On Thu, Apr 07, 2016 at 12:24:07PM +, Amrith Kumar wrote: > The trove failure is [1], same as described in email yesterday[2]. > > We have a gracious volunteer who offered to help with stable management > changes, and I've emailed him a request to have this and some other changes > proposed

[openstack-dev] mitaka features

Hi all, The newest version called mitaka is released, what's the new features of this version. Or is there some documents to describe it? Thank you! Best regards! Kenny Ji__ OpenStack Development Mailing List (not for

Re: [openstack-dev] Mitaka packages for openSUSE and SLES available

Hi, Mitaka packages with the released versions for openSUSE and SLES are now available at: http://download.opensuse.org/repositories/Cloud:/OpenStack:/Mitaka/ We currently maintain + test the packages for SLE 12SP1 and openSUSE Leap 42.1. If you find issues, please do not hesitate to report

Re: [openstack-dev] [Neutron] Evolving the stadium concept

Thanks for resuming this up Armando! On Fri, Apr 8, 2016 at 8:45 AM, Armando M. wrote: > > > On 29 March 2016 at 20:43, Vikram Choudhary wrote: > >> Hi Armando, >> >> We want to add the support for a new ML2 driver. Can you please guide >> what is the step

Re: [openstack-dev] [jacket] Introduction to jacket, a new project

Kevin, Quick question. Does one OpenStack infrastructure have to be dedicated for one Jacket instance? Cheers, Shinobu On Thu, Mar 24, 2016 at 8:24 PM, Kevin.ZhangSen wrote: > Hi Ghanshyam, > > Thank you for your sugesstions, and I agree with your opinion that the >

[openstack-dev] [Neutron] Proposing Hirofumi Ichihara to Neutron Core Reviewer Team

Hi Neutrinos, As the API Lieutenant of Neutron team, I would like to propose Hirofumi Ichihara (irc: hichihara) as a member of Neutron core reviewer team mainly focuing on the API/DB area. Hirofumi has been contributing neutron actively in the recent two releases constantly. He was involved in

Re: [openstack-dev] [Congress] Issues with Tox testing

Hi Bryan, tox -epy27 doesn't run tempest tests , that is tests mentioned in https://github.com/openstack/congress/tree/stable/liberty/contrib/tempest , it runs only unit tests , tests present in

Re: [openstack-dev] [Congress] Issues with Tox testing

OK, somehow I did not pick up on that, or dropped it along the way of developing the script. Thanks for the clarification, also that Tempest is not required. I should have clarified that I'm using stable/liberty as the base. I will be moving to stable/mitaka soon, as part of the OPNFV Colorado

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

On 2016/04/08 12:10, Kevin Benton wrote: Try depending on I2a10a8f15cdd5a144b172ee44fc3efd9b95d5b7e I tried. Let's wait for the result. On Thu, Apr 7, 2016 at 8:02 PM, Hongbin Lu > wrote: > -Original Message- >

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 29 March 2016 at 20:43, Vikram Choudhary wrote: > Hi Armando, > > We want to add the support for a new ML2 driver. Can you please guide what > is the step moving forward? > > Thanks > Vikram > Vikram, Apologies for the late reply, the Mitaka release tasks took precedence

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

Try depending on I2a10a8f15cdd5a144b172ee44fc3efd9b95d5b7e On Thu, Apr 7, 2016 at 8:02 PM, Hongbin Lu wrote: > > > > -Original Message- > > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > > Sent: April-07-16 12:04 PM > > To: OpenStack Development Mailing List

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

> -Original Message- > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > Sent: April-07-16 12:04 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' > object has no attribute 'strftime' > >

Re: [openstack-dev] [Horizon][stable] proposing Rob Cresswell for Horizon stable core

definitely +1 On Fri, Apr 8, 2016 at 12:42 AM, Brad Pokorny wrote: > +1. I think Rob will provide good input for stable. > > Thanks, > Brad > > From: Timur Sufiev > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < >

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

hi hongbin & team. Thanks for all your supporting, Magnum core team and the community, I am very glad to have this opportunity to join this team. I will try my best to contribute Magnum team and OpenStack community. Thanks Eli. On 2016年04月08日 03:35, Hongbin Lu wrote: Hi all, Thanks for

Re: [openstack-dev] [all][elections] Results of the TC Election

On 04/07/2016 08:51 PM, Tony Breeds wrote: > On Fri, Apr 08, 2016 at 10:03:11AM +1000, Tony Breeds wrote: >> Please join me in congratulating the 7 newly elected members of the TC. >> >> << REMOVE UNEEDED > > > *sigh*, clearly this was a templating error and no reflection on the fine >

Re: [openstack-dev] [all][elections] Results of the TC Election

On Fri, Apr 08, 2016 at 10:03:11AM +1000, Tony Breeds wrote: > Please join me in congratulating the 7 newly elected members of the TC. > > << REMOVE UNEEDED > *sigh*, clearly this was a templating error and no reflection on the fine community members and friends that were *not* elected

[openstack-dev] [tricircle]dynamic pod binding discussion

Hello, team, As scheduled in the weekly meeting, we will have a meeting to discuss “dynamic pod binding” at #openstack-tricircle(http://webchat.freenode.net/?channels=openstack-tricircle) at UTC 1:00 (Beijing time 9:00am) Apr.8. The etherpad for discussion is:

Re: [openstack-dev] [Glance] Newton virtual pre-summit sync

On Apr 7, 2016 2:28 PM, "Nikhil Komawar" wrote: > > Hi Flavio, > > Thank you for responding. > > Will it be still possible to do this sync on your bridge? I agree, it > worked pretty well the last time and would save us time on setting up > something new too. Hey, Yes,

Re: [openstack-dev] [all][elections] Results of the TC Election

Congrats everyone! -Rob On 8 April 2016 at 12:03, Tony Breeds wrote: > Please join me in congratulating the 7 newly elected members of the TC. > > << REMOVE UNEEDED > > * Davanum Srinivas (dims) > * Flavio Percoco (flaper87) > * John Garbutt (johnthetubaguy) > *

Re: [openstack-dev] [Congress] Issues with Tox testing

Thanks for the feedback, Bryan. Glad you got things working! 1. The instructions asking to install those packages are missing from kilo (we¹ll fix that), but they have been there since liberty. Was it perhaps unclear because the line is too long? * Additionally: * $ sudo apt-get install git gcc

[openstack-dev] [all][elections] Results of the TC Election

Please join me in congratulating the 7 newly elected members of the TC. << REMOVE UNEEDED > * Davanum Srinivas (dims) * Flavio Percoco (flaper87) * John Garbutt (johnthetubaguy) * Matthew Treinish (mtreinish) * Mike Perez (thingee) * Morgan Fainberg (morgan)/(notmorgan) * Thierry Carrez

Re: [openstack-dev] [Neutron] Newton blueprints call for action

Folks, thanks to everyone who has replied to the the thread. Much appreciated it. I'll reach out individually to figure out next steps and come back here to provide a status update. Cheers, Armando On 6 April 2016 at 07:17, Brent Eagles wrote: > -BEGIN PGP SIGNED

Re: [openstack-dev] [Congress] Issues with Tox testing

Thanks Clark, I found the same thing upon searching the issue, and replied to my post with the set of things I had to do to get this working. Thanks, Bryan Sullivan > From: cboy...@sapwetik.org > To: openstack-dev@lists.openstack.org > Date: Thu, 7 Apr 2016 12:19:56 -0700 > Subject: Re:

Re: [openstack-dev] [Congress] Issues with Tox testing

An update: I found that there were two dependencies needed that were not clear in the guide at https://github.com/openstack/congress. I also installed Tempest which was not referenced before. If these additions are correct (they worked for me), they should be added to

[openstack-dev] [release][stable][telemetry] ceilometer-powervm 2.0.0 release (mitaka)

We are excited to announce the release of: ceilometer-powervm 2.0.0: PowerVM Ceilometer Inspector for OpenStack Ceilometer. This release is part of the mitaka stable release series. For more details, please see below. Changes in ceilometer-powervm 1.0.0rc1..2.0.0

[openstack-dev] [release][stable] nova_powervm 2.0.0 release (mitaka)

We are thrilled to announce the release of: nova_powervm 2.0.0: PowerVM driver for OpenStack Nova. This release is part of the mitaka stable release series. For more details, please see below. Changes in nova_powervm 2.0.0.0rc1..2.0.0 - cde3fee

Re: [openstack-dev] [oslo] oslo.context and name fields

Sean, I've taken your WIP https://review.openstack.org/#/c/302744/ a step forward and its in review now. I'd value Jamie's input on your proposed from_environ signature change to see if that does meet his indented goal. Regards Ronald Ronald Bradford Web Site: http://ronaldbradford.com

[openstack-dev] [release][keystone] keystoneauth1 2.5.0 release (newton)

We are psyched to announce the release of: keystoneauth1 2.5.0: Authentication Library for OpenStack Identity This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/keystoneauth With package available at:

[openstack-dev] [TripleO][CI] Ability to reproduce failures

Hi, I'm trying to find an entry point to join the effort in TripleO CI. I studied the infrastructure and the scripts, but there's still something I'm missing. The last step of studying the complex landscape of TripleO CI and the first to start contributing is being able to reproduce failures in

Re: [openstack-dev] [neutron][vpnaas] VPNaaS tox api failure

Thanks Paul for info. Yes i had run the tests locally under VPN-repo. My analysis: * VPN test cases were using the neutron client for VPN services (which no longer supported by neutron). Thats why its throwing "tempest.lib.exceptions.NotFound: Object not found"

[openstack-dev] [Neutron] Drivers team cancelled

Hi Neutrinos, Too many firefights this week and I personally didn't have much time to spend on reviewing RFEs etc. If you guys want to have it, please go ahead but I won't be able to join. Cheers, Armando __ OpenStack

[openstack-dev] Drivers team cancelled

Hi Neutrinos, Too many firefights this week and I personally didn't have much time to spend on reviewing RFEs etc. If you guys want to have it, please go ahead but I won't be able to join. Cheers, Armando __ OpenStack

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

Hi all, Thanks for your feedback. The vote is unanimous. Eli Qiao has been added to the core team [1]. [1] https://review.openstack.org/#/admin/groups/473,members Best regards, Hongbin From: Vilobh Meshram [mailto:vilobhmeshram.openst...@gmail.com] Sent: April-04-16 10:31 PM To: OpenStack

Re: [openstack-dev] [neutron][vpnaas] VPNaaS tox api failure

Are you running the test locally? IIRC, the tempest based API tests for VPN have been (are being) moved to the VPN repo, but I don't know if a job was ever created for this so that the tests actually run. You may want to check with the author who moved the tests (madhusudan-kandadai) under commit

Re: [openstack-dev] [Horizon][Keystone]Re: Keystone 'adminURL' option to fallback to 'internalURL' within Horizon api/keystone.py?

Hi, I think Brad's spot on. See inline, but short version - the special case is only required if the KS catalog returns v2.0 endpoints. On 4/7/16, 1:39 PM, "Brad Pokorny" wrote: >Hi Brian, > >Copying to the general list, as this is something I've wondered about, and

Re: [openstack-dev] [Congress] Issues with Tox testing

On Thu, Apr 7, 2016, at 11:16 AM, Bryan Sullivan wrote: > Hi Congress team, > > A question for tox testing expert on the Congress team. I'm trying to run > the tox tests as described at https://github.com/openstack/congress, > specifically the two commands: > > $ sudo pip install 'tox<1.7' > >

[openstack-dev] [Horizon][app-catalog] Discussions in Austin

Greetings Horizon team! We'd like to find time at the design summit to cover a few of the things that impact both Horizon and the Community App Catalog. I think many of these topics will be of interest to other teams working on plugins using angular as well. If you've already got these on your

Re: [openstack-dev] [Glance] Newton virtual pre-summit sync

Hi Flavio, Thank you for responding. Will it be still possible to do this sync on your bridge? I agree, it worked pretty well the last time and would save us time on setting up something new too. On 4/1/16 8:56 AM, Flavio Percoco wrote: > On 31/03/16 17:34 -0400, Nikhil Komawar wrote: > >> Hi

Re: [openstack-dev] [Glance] Newton virtual pre-summit sync

Hi all, Thank you to those who have responded. As there were no objections, we will go with the proposed plan: We will have virtual sync related to Glance summit topics on, Tuesday April 12th from 1400 to ~1800 UTC. You can ask for the access to the conferencing tool on IRC (#openstack-glance)

[openstack-dev] [Horizon][Keystone]Re: Keystone 'adminURL' option to fallback to 'internalURL' within Horizon api/keystone.py?

Hi Brian, Copying to the general list, as this is something I've wondered about, and others probably are as well. Please see below. I'm not an expert on this topic, but I've looked at it a little bit. On 4/7/16, 11:02 AM, "Tully, Brian" wrote: >Hi there - > >I'm reaching

[openstack-dev] [neutron][vpnaas] VPNaaS tox api failure

Hi, While running "tox -e api" i hitting " tempest.lib.NotFound" Error. Is it a known issue ? failures expected? https://review.openstack.org/#/c/291949/1 ==> In this commit messages it says it kindof expected failure. Can someone provide some clarification on this Thanks, bharath

[openstack-dev] [Congress] Issues with Tox testing

Hi Congress team, A question for tox testing expert on the Congress team. I'm trying to run the tox tests as described at https://github.com/openstack/congress, specifically the two commands: $ sudo pip install 'tox<1.7' $ tox -epy27 Due to conflicts with the OS-owned python config, I

[openstack-dev] [release] Mitaka stable packaged for RDO

Hi, the RDO community has packages available for Mitaka Stable in its testing repositories. Official RDO release will be announced after we validate this release with our CI. Regards, H. __ OpenStack Development Mailing

[openstack-dev] [all][api] Recently accepted API-WG guidelines

hello all, this is a friendly update about guidelines that the API working group has recently accepted: 1. version discover guideline for API microversions https://review.openstack.org/243429 2. client interaction guideline for API microversions https://review.openstack.org/243414 3.

Re: [openstack-dev] [trove][stable] [Openstack-stable-maint] Stable check of openstack/trove failed

On 07/04/16 12:24 +, Amrith Kumar wrote: The trove failure is [1], same as described in email yesterday[2]. We have a gracious volunteer who offered to help with stable management changes, and I've emailed him a request to have this and some other changes proposed into other stable

Re: [openstack-dev] [Horizon][stable] proposing Rob Cresswell for Horizon stable core

+1. I think Rob will provide good input for stable. Thanks, Brad From: Timur Sufiev > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date:

Re: [openstack-dev] [TripleO] FreeIPA integration

Yeah, the console can be used as a building block to solve it. I'm just saying we should formalize the plumbing enough that it can be relied upon by everyone, instead of asking everyone to reinvent the wheel. Thats partially what the spec's about. Thanks, Kevin

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

Hongbin Lu wrote: Hi all, Magnum gate recently broke with error: “AttributeError: 'str' object has no attribute 'strftime'” (here is a full log [1]). I would like to confirm if there is a recent commit in Neutron that causes the breakage. If yes, a quick fix is

[openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

Hi all, Magnum gate recently broke with error: "AttributeError: 'str' object has no attribute 'strftime'" (here is a full log [1]). I would like to confirm if there is a recent commit in Neutron that causes the breakage. If yes, a quick fix is greatly appreciated. [1]

Re: [openstack-dev] [Fuel][library] Update of astute.yaml fixtures and noop tests

Alex, we can do this (and I hope we'll do) after we fix https://bugs.launchpad.net/fuel/+bug/1567367 Regards, Alex On Thu, Apr 7, 2016 at 5:04 PM, Alex Schultz wrote: > > On Thu, Apr 7, 2016 at 7:41 AM, Aleksandr Didenko > wrote: > >> Hi, >> >>

Re: [openstack-dev] [Fuel][library] Update of astute.yaml fixtures and noop tests

On Thu, Apr 7, 2016 at 7:41 AM, Aleksandr Didenko wrote: > Hi, > > thanks to Dima, we now have ROLE annotations in noop tests [0]. I've > updated all the noop rspec tests that we currently have and added > appropriate role annotation [1]. So after this patch is merged, we

[openstack-dev] [TripleO] [CI] Tempest configuration in Tripleo CI jobs

Hi, all I'd like to discuss the topic about how do we configure tempest in CI jobs for TripleO. I have currently two patches: support for tempest: https://review.openstack.org/#/c/295844/ actually run of tests: https://review.openstack.org/#/c/297038/ Right now there is no upstream tool to

[openstack-dev] [nova] Instance Snapshot Capability Extended

Hi All, I have proposed a blueprint (https://blueprints.launchpad.net/nova/+spec/instance-memory-snapshot) and nova spec (https://review.openstack.org/#/c/295415/) to improve the current snapshot capability. In the past this topic has been introduced and several times it has been left behind.

[openstack-dev] [release] Mitaka packaged on Gentoo.

While we have had 2016.1. packages (ebuilds that track the stable/mitaka branches) and it has already seen deployment I'm now happy to announce that now that the tarballs are up we also have ebuilds based on the tags/tarballs. -- Matthew Thode (prometheanfire) signature.asc Description:

Re: [openstack-dev] [Nova] RFC Host Maintenance

The only gap based on my limited understanding is that nova is not emitting events compute host state changes. This knowledge is still kept inside nova as some service states. If that info is posted to oslo messaging, a lot of usage scenarios can be enabled and we can avoid too much churns to nova

Re: [openstack-dev] [Fuel][library] Update of astute.yaml fixtures and noop tests

Hi, thanks to Dima, we now have ROLE annotations in noop tests [0]. I've updated all the noop rspec tests that we currently have and added appropriate role annotation [1]. So after this patch is merged, we no longer need to put any new fixtures into dozens of rspec files in order to enable it.

Re: [openstack-dev] [TripleO] FreeIPA integration

Excerpts from Adam Young's message of 2016-04-05 19:02:58 -0700: > On 04/05/2016 11:42 AM, Fox, Kevin M wrote: > > Yeah, and they just deprecated vendor data plugins too, which > > eliminates my other workaround. :/ > > > > We need to really discuss this problem at the summit and get a viable >

Re: [openstack-dev] [tc][ptl][keystone] Proposal to split authentication part out of Keystone to separated project

In response to point 2.2, the progress with Fernet in the last year has exposed performance pain points in keystone. Finding sensible solutions for those issues is crucial in order for people to adopt Fernet. In Mitaka we had a lot of discussion that resulted in landing several performance related

Re: [openstack-dev] [trove][stable] [Openstack-stable-maint] Stable check of openstack/trove failed

The trove failure is [1], same as described in email yesterday[2]. We have a gracious volunteer who offered to help with stable management changes, and I've emailed him a request to have this and some other changes proposed into other stable branches. That request is below: > You had offered

Re: [openstack-dev] Launch of an instance from a bootable volume fails on Xen env

Hi, did you file a bug for Horizon about this? I did file a bug for nova about this, but I wasn't sure where to put it. Zitat von Matthias Runge : On 24/03/16 12:03, Eugen Block wrote: Hi, Has this been resolved? Is anyone working on this issue? I had traced down

Re: [openstack-dev] [Horizon][stable] proposing Rob Cresswell for Horizon stable core

+1 Чт, 7 апр. 2016 г. в 14:04, Itxaka Serrano Garcia : > Im still not sure if non-cores (i.e. peasants like me) can vote but I > will do it anyway :D > > A big +1 from me. > > Itxaka > > On 04/07/2016 12:01 PM, Matthias Runge wrote: > > Hello, > > > > I'm proposing Rob

Re: [openstack-dev] [Nova] RFC Host Maintenance

Thanks Sean, I totally understand your comment and this logic might really be somewhere else, not to overload Nova with all kind of things and the level of exposing you suggested might then be enough. Anyhow I am also asking more user or operator perspectives to get more use cases. Surely if

Re: [openstack-dev] [Horizon][stable] proposing Rob Cresswell for Horizon stable core

Im still not sure if non-cores (i.e. peasants like me) can vote but I will do it anyway :D A big +1 from me. Itxaka On 04/07/2016 12:01 PM, Matthias Runge wrote: Hello, I'm proposing Rob Cresswell to become stable core for Horizon. I thought, in the past all PTL were in stable team, but

Re: [openstack-dev] [Nova] RFC Host Maintenance

On 04/07/2016 03:26 AM, Juvonen, Tomi (Nokia - FI/Espoo) wrote: > Hi Nova, Ops, stackers, > > I am trying to figure out different use cases and requirements there > would be for host maintenance and would like to get feedback and > transfer all this to spec and discussion what could and should

[openstack-dev] [Horizon][stable] proposing Rob Cresswell for Horizon stable core

Hello, I'm proposing Rob Cresswell to become stable core for Horizon. I thought, in the past all PTL were in stable team, but this doesn't seem to be true any more. Please chime in with +1/-1 -- Matthias Runge Red Hat GmbH, http://www.de.redhat.com/, Registered seat:

Re: [openstack-dev] [fuel] Component Leads Elections

Dear colleagues, Looks like we have consensus (lazy, but still consensus) on this topic: we don't need this role CL exposed to Fuel project. I have prepared a change [1] for our team structure policy. My suggestion is to make Fuel is an aggregator of independent components. Component teams could

[openstack-dev] [Cinder] About snapshot Rollback?

Dear Cruz: Thanks for you kind support, I will review the previous spec according to the following links. May be more user scenario we should considered,such as backup,create volume from snapshot,consistency group and etc,we will spend some time to gather the user's scenarios and

Re: [openstack-dev] [rally]rally-mysql-py27-unit FAILURE

Hi, don't panic=) Looks like it is not you fault. I'm watching out for your patch. Best regards, Roman Vasilets. On Thu, Apr 7, 2016 at 10:51 AM, Wu, Liming wrote: > Hi > > I have push a simple patch to rally, but " Mirantis Rally CI check" was > not passed. > "

Re: [openstack-dev] [kloudbuster] authorization failed problem

Thanks Yichen and Alec. Yichen, It was what I was looking for. I started with Rally , but faced problem with defining the number of router per tenant and traffic generation. Then, I found that there is a new project Kloudbuster. I faced some issues , but with your help , I succeeded in running it.

[openstack-dev] [release][release] reno 1.6.2 release

We are pleased to announce the release of: reno 1.6.2: RElease NOtes manager With source available at: http://git.openstack.org/cgit/openstack/reno Please report issues through launchpad: http://bugs.launchpad.net/reno For more details, please see below. Changes in reno 1.6.1..1.6.2

[openstack-dev] [release] Sorry for the recent flurry of announce emails

Hi! We are sorry for the recent flurry of announce emails. We are preparing for the final Mitaka release and an error in the build script led to prematurely sending erroneous release announcements. While the version numbers are correct, those announcements contain only partial release notes

Re: [openstack-dev] [Tricircle] Original Blueprint

All clear. Cheers, Shinobu On Thu, Apr 7, 2016 at 5:21 PM, joehuang wrote: > Yes, of course. > > And in Newton release, we want to use BP + spec for review and approve for > new features, just like https://review.openstack.org/#/c/282180/. > > Best Regards > Chaoyi Huang (

Re: [openstack-dev] [Tricircle] Original Blueprint

Yes, of course. And in Newton release, we want to use BP + spec for review and approve for new features, just like https://review.openstack.org/#/c/282180/. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Shinobu Kinjo [mailto:shinobu...@gmail.com] Sent: Thursday,

Re: [openstack-dev] [Tricircle] Original Blueprint

Hi Chaoyi, Just to clarify more. On Thu, Apr 7, 2016 at 5:02 PM, joehuang wrote: > Hi, Shinobu, > > Thanks for your review. Just replied in the google doc, that the table is the > latest design, not old one, and some fields need to be implemented in new > patches. I'm

Re: [openstack-dev] [Tricircle] UUID Mapping

Hi Chaoyi, Thank you for your reply. All clear. Cheers, Shinobu On Thu, Apr 7, 2016 at 5:00 PM, joehuang wrote: > Hi, Shinobu, > > This part has been deleted just few minutes ago. No UUID mapping in stateless > design, but a resource routing table is used there, but read

Re: [openstack-dev] [Tricircle] UUID Mapping

Hi, Shinobu, This part has been deleted just few minutes ago. No UUID mapping in stateless design, but a resource routing table is used there, but read the "7.2 Resource Routing Table". Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Shinobu Kinjo

Re: [openstack-dev] [Tricircle] Original Blueprint

Hi, Shinobu, Thanks for your review. Just replied in the google doc, that the table is the latest design, not old one, and some fields need to be implemented in new patches. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Shinobu Kinjo [mailto:shinobu...@gmail.com]

Re: [openstack-dev] [Neutron] OVS flow modification performance

At Thu, 07 Apr 2016 16:33:02 +0900, IWAMOTO Toshihiro wrote: > > At Mon, 18 Jan 2016 12:12:28 +0900, > IWAMOTO Toshihiro wrote: > > > > I'm sending out this mail to share the finding and discuss how to > > improve with those interested in neutron ovs performance. > > > > TL;DR: The native

[openstack-dev] [rally]rally-mysql-py27-unit FAILURE

Hi I have push a simple patch to rally, but " Mirantis Rally CI check" was not passed. " rally-mysql-py27-unit FAILURE" was occurred. I don't know why. Who I Help me. Thx. https://review.openstack.org/#/c/302097/ Best regards wuliming

Re: [openstack-dev] Launch of an instance from a bootable volume fails on Xen env

On 24/03/16 12:03, Eugen Block wrote: > Hi, > >> Has this been resolved? Is anyone working on this issue? > > I had traced down the effect and found a possible solution, see > https://bugs.launchpad.net/nova/+bug/1560965 > > If you're just trying to start via Horizon, changing >

Re: [openstack-dev] [Neutron] OVS flow modification performance

At Mon, 18 Jan 2016 12:12:28 +0900, IWAMOTO Toshihiro wrote: > > I'm sending out this mail to share the finding and discuss how to > improve with those interested in neutron ovs performance. > > TL;DR: The native of_interface code, which has been merged recently > and isn't default, seems to

[openstack-dev] [Nova] RFC Host Maintenance

Hi Nova, Ops, stackers, I am trying to figure out different use cases and requirements there would be for host maintenance and would like to get feedback and transfer all this to spec and discussion what could and should land for Nova or other places. As working in OPNFV Doctor project that

Re: [openstack-dev] [osc] Meeting time preferences for OSC team

Dear All, Thanks for sharing preffered time. Common votes seems for below time options E.4 - Thursday at 1600 UTC in #openstack-meeting (IRC webclient) O.3 - Thursday at 1900 UTC in #openstack-meeting (IRC webclient) Lets discuss and finalize this time in today's meeting at 1900 UTC in

[openstack-dev] [Tricircle] UUID Mapping

Hi Team, Can we elaborate on uuid mapping more? As described in blueprint, it's expected to be a solution for one of challenges. > The object UUID in the top layer is different from the UUIDs in the bottom > layers. There should theoretical logic, mechanism. But I've not been able to find any