Re: [openstack-dev] [manila]: questions on update-access() changes

On June 18, 2016 1:47:10 AM Ben Swartzlander wrote: > Ramana, I think your questions got answered in a channel discussion last > week, but I just wanted to double check that you weren't still expecting > any answers here. If you were, please reply and we'll keep this

Re: [openstack-dev] [OpenStack-Infra] There is no Jenkins, only Zuul

On 06/20/2016 06:47 AM, Marek Zawadzki wrote: > Are 3d party CIs affected by this change and if yes how? > What's the recommendation for newly created 3rd party CIs - should they > use new zuul only or it's fine to use existing (and tested) jenkins+zuul > configuration? 3rd party should not be

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.06.21 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20160621T17 __ OpenStack

Re: [openstack-dev] [OpenStack-Infra] There is no Jenkins, only Zuul

Are 3d party CIs affected by this change and if yes how? What's the recommendation for newly created 3rd party CIs - should they use new zuul only or it's fine to use existing (and tested) jenkins+zuul configuration? Second question - if jobs are to be launched by zuul+ansible, how will the

Re: [openstack-dev] [all] Proposal: Architecture Working Group

I like the idea in principle, but am bullish on the implementation. For example: we have the API-WG which fulfills part of an Architectural mission, as well as the Cross-Project WG which fulfills a different part. Yet there's no incentive, carrot or stick, that drives adoption of the approved

Re: [openstack-dev] Recommended ways to find compute node's bandwidth (physical NIC)

Thanks Sudipto for pointing out the tool; another light weight tool I am thinking is 'ethtool', in order to collect basic NIC info, including "speed". Rao Adnan Khan AT Integrated Cloud (AIC) Development | SE Software Development & Engineering (SD) Emai: rk2...@att.com Cell phone: 972-342-5638

Re: [openstack-dev] Cinder multiple backends

In the mean time, the package list you have listed below is rather small. Easiest thing might be to just add them all to the docker/base/Dockerfile Thanks, Kevin From: Ryan Hallisey [rhall...@redhat.com] Sent: Monday, June 20, 2016 6:47 AM To: OpenStack

Re: [openstack-dev] [magnum] Need helps to implement the full baremetals support

Hi Yuanying, I tested your patch [2] with the image that Ton created [1] and it worked. For me devicemapper as docker-storage-driver didn't work but this is unrelated to this patch, I'll update devicemapper. I used overlay and it was ok. I'll sum up what I did here, for others to test. On a

[openstack-dev] [TripleO] Consolidating TripleO validations with Browbeat validations

Hello - It would seem there is a little bit of overlap with TripleO validations ( clapper validations ) and Browbeat *Checks*. I would like to see these two come together, and I wanted to get some feedback on this. For reference here are the Browbeat checks :

[openstack-dev] [tricircle]Pypi job works, and tagging leads to a package publish

Hello, team, After the pypi job configuration and help from the community, the first package of Tricircle is published automatically after tagging the version 2.0.1 in stable/mitaka branch. https://pypi.python.org/pypi/tricircle The package verified the release publish process, and

[openstack-dev] [tricircle]this weekly meeting

Hello, I am on the trip to attend the OPNFV Berlin summit, would like to know if someone can chair the weekly meeting of Tricircle. If no volunteer before Jun. 22, we may have to skip this weekly meeting. Best Regards Chaoyi Huang ( joehuang )

Re: [openstack-dev] Neutron trunk port - Kilo

> On 20 Jun 2016, at 18:23, KHAN, RAO ADNAN wrote: > > Hi, > > I couldn’t see neutron neutron trunk-create --.. (as suggested at > https://wiki.openstack.org/wiki/Neutron/TrunkPort#neutron_trunk) supported in > neutron agent 2.4. > > Can someone tell as to how to create

Re: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team

Sridhar, Thank you for nominating me as tacker core-reviewer. Tacker Core team, Thanks for appreciating my contributions in tacker and It's my pleasure to be part of the core-team. Regards Kanagaraj M On Mon, Jun 20, 2016 at 4:51 PM, Sridhar Ramaswamy wrote: > Thanks for

Re: [openstack-dev] [all] Proposal: Architecture Working Group

+1 , great idea. if we can add a mission/objective based on the nice definitions you added, will help a long way in cross-project architecture evolution. moreover, I'd like this to be a integration point for openstack projects (and not a silo) so that we can build the shared understanding we

[openstack-dev] [nova] libvirt driver: who should create the libvirt.xml file?

White working on the change series to implement the virtlogd feature I got feedback [1] to move code which creates parts of the libvirt.xml file from the "driver" module into the "guest" module. I'm a bit hesitant to do so as the responsibility of creating a valid libvirt.xml file is then spread

[openstack-dev] Neutron trunk port - Kilo

Hi, I couldn't see neutron neutron trunk-create --.. (as suggested at https://wiki.openstack.org/wiki/Neutron/TrunkPort#neutron_trunk) supported in neutron agent 2.4. Can someone tell as to how to create trunk port in Kilo? Thanks much! Rao Adnan Khan AT Integrated Cloud (AIC) Development |

Re: [openstack-dev] [magnum] Stable/liberty functional tests

On Tue, Jun 14, 2016 at 01:25:14PM +, Bunting, Niall wrote: > Hi, > > > There was work on a patch [1] to fix the liberty stable branch. However, we > are running into problems with the functional tests, because the functional > tests were set up differently in liberty eg. The current [2]

[openstack-dev] [nova] bugs team meeting of 2016-06-21 is cancelled

Due to a conflict with a company internal appointment I have to cancel tomorrows (2016-06-21) nova bugs team meeting. If you want to take over the bug skimming duty for this week, please add your name in the table at [1]. References: [1]

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Hi all! I really like the idea of the group, so count me in! Ghe Rivero Quoting Clint Byrum (2016-06-17 23:52:43) > ar·chi·tec·ture > ˈärkəˌtek(t)SHər/ > noun > noun: architecture > > 1. > > the art or practice of designing and constructing buildings. > > synonyms:building

[openstack-dev] [mistral] Team meeting reminder - 06/20/2016

Hi, This is a reminder that we’ll have a team meeting today at #openstack-meeting at 16.00 UTC. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Custom Actions API spec Volunteers to continue? Automated testing for OpenStack actions How can test

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On 06/14/2016 07:19 PM, Chris Hoge wrote: > >> On Jun 14, 2016, at 3:59 PM, Edward Leafe wrote: >> >> On Jun 14, 2016, at 5:50 PM, Matthew Treinish wrote: >> >>> But, if we add another possible state on the defcore side like conditional >>> pass, >>>

[openstack-dev] [smaug] Smaug Weekly IRC Meeting - Tuesday May 21st

Hello all, Our weekly IRC meeting will take place tomorrow (Tuesday, May 21st) at 09:00 UTC in #openstack-meeting Please review the proposed meeting agenda here: https://wiki.openstack.org/wiki/Meetings/smaug Feel free to add to the agenda any subject you would like to discuss. --Yuval

Re: [openstack-dev] [neutron][ovs] The way we deal with MTU

> On 15 Jun 2016, at 17:27, Ihar Hrachyshka wrote: > > First, some context: we talked it thru with Eugene on IRC, and Eugene > reported that he cannot reproduce the issue on his setup using Ubuntu > hypervisor with ovs 2.4: > >

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

> On Jun 20, 2016, at 8:46 AM, Doug Hellmann wrote: > > Excerpts from Mark Voelker's message of 2016-06-16 20:33:36 +: > >> On Tue, Jun 14, 2016 at 05:42:16PM -0400, Doug Hellmann wrote: >> >> >>> I don't think DefCore actually needs to change old versions of

[openstack-dev] [puppet] weekly meeting #86

Hi Puppeteers! We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting-4. Here's a first agenda: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160621 Feel free to add more topics, and any outstanding bug and patch. See you tomorrow! Thanks, -- Emilien

Re: [openstack-dev] [kolla] Cinder multiple backends

Right now you can install it by providing --include-header file during build. We are working on cleaner mechanism in Newton [1]. [1] https://review.openstack.org/#/q/topic:bp/third-party-plugin-support On 20 June 2016 at 08:29, Carlos Cesario wrote: > Hi folks, > > It

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

On 06/17/2016 12:14 PM, Chris Dent wrote: > On Fri, 17 Jun 2016, Sylvain Bauza wrote: > >> In the review, you explain why you don't trust Routes and I respect >> that. That said, are those issues logged as real problems for our API >> consumers, which are mostly client libraries that we own and

[openstack-dev] [neutron][calico] New networking-calico IRC meeting

Calling everyone interested in networking-calico ...! networking-calico has been around in the Neutron stadium for a while now, and it's way past time that we had a proper forum for discussing and evolving it - so I'm happy to be finally proposing a regular IRC meeting slot for it: [1]. A

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

On 06/17/2016 11:23 AM, Sylvain Bauza wrote: +1000 yes to that. Now the devil could be in the details, in particular how we implement the WSGI server, the corresponding WSGI app and the associated routing, and that's exactly the problem below. We shouldn't be implementing a WSGI server *at

[openstack-dev] [StoryBoard] [OpenStack-Infra] StoryBoard Bug Squash 22nd-23rd June

Hi everyone! For one week only*, the StoryBoard bug squash is coming to an OpenStack community near you! That's right; from 11:00 UTC 22nd June, to 11:00 UTC 23rd June THIS week, the StoryBoard team will be making a critically-acclaimed appearance in #openstack-sprint. We'll be setting time

[openstack-dev] [new][oslo] oslo.privsep 1.9.0 release (newton)

We are eager to announce the release of: oslo.privsep 1.9.0: OpenStack library for privilege separation This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.privsep With package available at:

Re: [openstack-dev] [kolla] Cinder multiple backends

Hey Carlos, The work to enable you to do this is in progress. Kolla needs to refactor the way the Dockerfiles are templated in order to create additional flexibility. You can follow the work here: https://blueprints.launchpad.net/kolla/+spec/third-party-plugin-support Thanks, Ryan -

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

Le 20/06/2016 16:04, Jay Pipes a écrit : On 06/17/2016 11:23 AM, Sylvain Bauza wrote: +1000 yes to that. Now the devil could be in the details, in particular how we implement the WSGI server, the corresponding WSGI app and the associated routing, and that's exactly the problem below. We

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

On 06/20/2016 10:21 AM, Sylvain Bauza wrote: Le 20/06/2016 16:04, Jay Pipes a écrit : On 06/17/2016 11:23 AM, Sylvain Bauza wrote: +1000 yes to that. Now the devil could be in the details, in particular how we implement the WSGI server, the corresponding WSGI app and the associated routing,

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

Excerpts from Mark Voelker's message of 2016-06-20 13:24:46 +: > > > On Jun 20, 2016, at 8:46 AM, Doug Hellmann wrote: > > > > Excerpts from Mark Voelker's message of 2016-06-16 20:33:36 +: > > > >> On Tue, Jun 14, 2016 at 05:42:16PM -0400, Doug Hellmann wrote: >

[openstack-dev] [neutron][upgrades] Bi-weekly upgrades work status. 6/20/2016

Hi all, (It’s not really bi-weekly since I missed it the previous week. This report is for the last 3 weeks. I will try to keep a more regular schedule for those updates in the future.) OK. What’s new in neutron upgrades since last update? 1. For the most part, the team works on migrating

Re: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team

Thanks for the responses, I'm closing the vote. Kanagaraj - welcome to the Tacker core team! On Sun, Jun 19, 2016 at 7:25 PM, bharath thiruveedula < bharath_...@hotmail.com> wrote: > +1 > -- > To: openstack-dev@lists.openstack.org > From: bob.haddle...@nokia.com >

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

Excerpts from Mark Voelker's message of 2016-06-16 20:33:36 +: > On Tue, Jun 14, 2016 at 05:42:16PM -0400, Doug Hellmann wrote: > > > > I don't think DefCore actually needs to change old versions of Tempest, > > but maybe Chris or Mark can verify that? > > So if I’m groking this correctly,

Re: [openstack-dev] [requirements][all] VOTE to expand the Requirements Team

Thanks for the VOTE everyone. Matthew, Dirk, Swapnil, Tony, Thomas, With this VOTE the training wheels come off :) Please be cautious with your new super powers! And thanks a Ton to Thierry as well. Thanks, Dims On Fri, Jun 17, 2016 at 3:59 PM, Robert Collins wrote:

Re: [openstack-dev] [nova] Question about redundant API samples tests for microversions

On 06/17/2016 04:16 PM, Matt Riedemann wrote: > I was reviewing this today: > > https://review.openstack.org/#/c/326940/ > > And I said to myself, 'self, do we really need to subclass the API > samples functional tests for this microversion given this change doesn't > modify the request/response

Re: [openstack-dev] Version header for OpenStack microversion support

On 06/18/2016 06:32 AM, Jamie Lennox wrote: > Quick question: why do we need the service type or name in there? You > really should know what API you're talking to already and it's just > something that makes it more difficult to handle all the different APIs > in a common way. It is also

Re: [openstack-dev] [OpenStack-Infra] There is no Jenkins, only Zuul

On Mon, Jun 20, 2016 at 01:47:24PM +0200, Marek Zawadzki wrote: > Are 3d party CIs affected by this change and if yes how? > What's the recommendation for newly created 3rd party CIs - should they use > new zuul only or it's fine to use existing (and tested) jenkins+zuul > configuration? > 3rd

Re: [openstack-dev] [nova] Question about redundant API samples tests for microversions

On 06/20/2016 08:24 AM, Sean Dague wrote: Honestly, I feel like subclassing tests is almost always an anti-pattern. It looks like you are saving code up front, but it massively couples things in ways that become super hard to deal with in the future. Test code doesn't need to be normalized to

Re: [openstack-dev] [requirements][all] VOTE to expand the Requirements Team

On 06/16/2016 10:44 AM, Davanum Srinivas wrote: > Folks, > > At Austin the Release Management team reached a consensus to spin off > with some new volunteers to take care of the requirements process and > repository [1]. The following folks showed up and worked with me on > getting familiar with

[openstack-dev] [neutron][taas] making a taas release for mitaka or not

hi, we tap-as-a-service project had a plan to make a release compatible with mitaka. however, - it's a bit late for mitaka already - the reference implementation needs to be adapted to l2 agent extension but no much progress yet so, a question is, if we still want to make a release for mitaka,

Re: [openstack-dev] [ironic] Proposing two new cores

Thanks everyone, I¹m super excited to continue my contribute to Ironic! Sam On 18/06/2016 16:25, "Jim Rollenhagen" wrote: >On Thu, Jun 16, 2016 at 11:12:31AM -0400, Jim Rollenhagen wrote: >> Hi all, >> >> I'd like to propose Jay Faulkner (JayF) and Sam Betts

[openstack-dev] [kolla] Cinder multiple backends

Hi folks, It seems that Kolla does nos provide option to enable multiple backends in Cinder config. Currently in my deploy/setup I needed enable the Storwize Cinder driver - http://docs.openstack.org/mitaka/config-reference/block-storage/drivers/ibm-storwize-svc-driver.html - and to this I

Re: [openstack-dev] [TripleO] Consolidating TripleO validations with Browbeat validations

> On 20 Jun 2016, at 18:37, Joe Talerico wrote: > > Hello - It would seem there is a little bit of overlap with TripleO > validations ( clapper validations ) and Browbeat *Checks*. I would > like to see these two come together, and I wanted to get some feedback > on this. >

Re: [openstack-dev] [nova] Initial oslo.privsep conversion?

17.06.2016 17:13, Matt Riedemann пишет: On 6/9/2016 6:51 PM, Tony Breeds wrote: On Fri, Jun 10, 2016 at 08:24:34AM +1000, Michael Still wrote: On Fri, Jun 10, 2016 at 7:18 AM, Tony Breeds wrote: On Wed, Jun 08, 2016 at 08:10:47PM -0500, Matt Riedemann wrote:

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

Excerpts from Jay Pipes's message of 2016-06-20 10:04:06 -0400: > On 06/17/2016 11:23 AM, Sylvain Bauza wrote: > > +1000 yes to that. Now the devil could be in the details, in particular > > how we implement the WSGI server, the corresponding WSGI app and the > > associated routing, and that's

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

On 2016-06-20 18:43:44 +0200 (+0200), Zane Bitter wrote: > The binaries are free-as-in-beer - IIUC you can't redistribute them. The > source code, of course, remains free-as-in-speech as it has always been. > (It's easy to forget the distinction when you work in Python all day and > there are no

[openstack-dev] [mistral] Team meeting minutes - 06/20/2016

Thanks for joining our meeting today! In case you didn’t attend here are the meeting minutes and log: http://eavesdrop.openstack.org/meetings/mistral/2016/mistral.2016-06-20-16.01.html

Re: [openstack-dev] [TripleO] Consolidating TripleO validations with Browbeat validations

On Mon, Jun 20, 2016 at 12:41 PM, Ihar Hrachyshka wrote: > >> On 20 Jun 2016, at 18:37, Joe Talerico wrote: >> >> Hello - It would seem there is a little bit of overlap with TripleO >> validations ( clapper validations ) and Browbeat *Checks*. I would >>

Re: [openstack-dev] [all] Proposal: Architecture Working Group

+1 The points about the PWG and TC are worth some consideration. >From my perspective, I think it would make sense for the PWG to define the expected behaviors of the system, which would be an input to the architecture group. The architecture group would define both prescriptive (where we'd like

Re: [openstack-dev] [nova] [api] [placement] strategy for placement api structure

On 06/20/2016 12:47 PM, Doug Hellmann wrote: Excerpts from Jay Pipes's message of 2016-06-20 10:04:06 -0400: On 06/17/2016 11:23 AM, Sylvain Bauza wrote: +1000 yes to that. Now the devil could be in the details, in particular how we implement the WSGI server, the corresponding WSGI app and the

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Jesse Cook's message of 2016-06-20 16:58:48 +: > +1 > > The points about the PWG and TC are worth some consideration. > > From my perspective, I think it would make sense for the PWG to define the > expected behaviors of the system, which would be an input to the > architecture

Re: [openstack-dev] [all] Proposal: Architecture Working Group

So, it sounds like you’ve just described the job of the TC. And they have so far refused to define OpenStack, leading to a series of derivative decisions that seem … inconsistent over time. How is this body going to be different? How will it have any teeth, and not just end up with the

[openstack-dev] [Neutron] IRC meeting for VLAN-aware VM's

At one point early during the Mitaka cycle we had a weekly IRC meeting on this topic going. I got side-tracked by other work at the time and I stopped attending, so my apologies if these are still happening. I'm wondering if it would be useful to get these going again if this is not currently

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Michael Krotscheck's message of 2016-06-20 15:26:20 +: > I like the idea in principle, but am bullish on the implementation. > As you should be, and we all must be. It's not going to happen if we just dream it. That's kind of the point. Let's write down a design _for the group

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Some other topics: * Rolling upgrades - For example, I haven't figured out a way to safely drain an rpc based service rather then just shooting it and hoping things go well... Is it safe? This safety code should be built into them all consistently. * How to get events to users in a usable

[openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Hi dib-gurus, I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX with a AMD A8-5557M APU with Ubuntu 16.04 installed and getting an odd error. Hoping someone has some ideas... The command I am running is: disk-image-create -o /tmp/ubuntu.qcow2 --image-size=10 ubuntu vm

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

On 16/06/16 23:04, Jeremy Stanley wrote: On 2016-06-16 16:04:28 -0400 (-0400), Steve Gordon wrote: [...] This is definitely a point worth clarifying in the general case, but tangentially for the specific case of the RHEL operating system please note that RHEL is available to developers for

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Doug Wiegley's message of 2016-06-20 10:40:56 -0600: > So, it sounds like you’ve just described the job of the TC. And they have so > far refused to define OpenStack, leading to a series of derivative decisions > that seem … inconsistent over time. > > How is this body going to be

[openstack-dev] [Magnum] Midcycle location and date

Hi all, This is a reminder that there are doodle pools for midcycle participants to select the location and time: Location: http://doodle.com/poll/2x9utspir7vk8ter Date: http://doodle.com/poll/5tbcyc37yb7ckiec If you are able to attend the midcycle, I encourage you to vote for your preferred

Re: [openstack-dev] [all] Proposal: Architecture Working Group

+1 From: Clint Byrum [cl...@fewbar.com] Sent: Monday, June 20, 2016 10:27 AM To: openstack-dev Subject: Re: [openstack-dev] [all] Proposal: Architecture Working Group Excerpts from Doug Wiegley's message of 2016-06-20 10:40:56 -0600: > So, it sounds like

Re: [openstack-dev] [Kuryr] jenkins failures "POST_FAILURE",

recheck fix my problem. You can try that. Thanks. On Tue, Jun 21, 2016 at 1:21 PM Andreas Jaeger wrote: > On 06/21/2016 06:35 AM, Vikas Choudhary wrote: > > Hi Team, > > > > Since yesterday, I am observing abnormal jenkins failures on some of > > patches while others are fine.

Re: [openstack-dev] [Kuryr] jenkins failures "POST_FAILURE",

yes, recheck fixed it this time. Thanks Vikas On Tue, Jun 21, 2016 at 11:13 AM, Will Zhou wrote: > recheck fix my problem. You can try that. Thanks. > > On Tue, Jun 21, 2016 at 1:21 PM Andreas Jaeger wrote: > >> On 06/21/2016 06:35 AM, Vikas Choudhary wrote:

[openstack-dev] [nova] Vendordata improvements

So, https://review.openstack.org/#/c/317739 is basically done I think. I'm after people's thoughts on: - I need to do some more things, as described in the commit message. Are we ok with them being in later patches to get reviews moving on this? - I'm unsure what level of tempest testing makes

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

Hi So following discussion on this, I have modified the spec to try and take account of the various concerns etc. See: https://review.openstack.org/#/c/318605/ For reference, here is an extract from this spec that summarizes the level of compatibility being proposed (A “3.6 client” refers to

Re: [openstack-dev] [Fuel] [Plugins] Netconfig tasks changes

Hi folks, it turned out that one change has to be made in your plugins though. If you're reusing 'netconfig' task for your custom roles, you need to remove 'configure_default_route' task from your roles (if you have it) and add 'hiera_default_route'. This is needed for proper default gateway

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Joshua Harlow's message of 2016-06-17 15:33:25 -0700: > Thanks for getting this started Clint, > > I'm happy and excited to be involved in helping try to guide the whole > ecosystem together (it's also why I like being in oslo) to a > architecture that is more cohesive (and is

Re: [openstack-dev] [TripleO] Consolidating TripleO validations with Browbeat validations

On Mon, Jun 20, 2016 at 12:43 PM, Joe Talerico wrote: > On Mon, Jun 20, 2016 at 12:41 PM, Ihar Hrachyshka wrote: >> >>> On 20 Jun 2016, at 18:37, Joe Talerico wrote: >>> >>> Hello - It would seem there is a little bit of overlap

Re: [openstack-dev] Version header for OpenStack microversion support

On Jun 18, 2016, at 9:03 AM, Clint Byrum wrote: > Whatever API version is used behind the compute API is none of the user's > business. Actually, yeah, it is. If I write an app or a tool that expects to send information in a certain format, and receive responses in a certain

Re: [openstack-dev] Version header for OpenStack microversion support

On 21 June 2016 at 11:41, Edward Leafe wrote: > On Jun 18, 2016, at 9:03 AM, Clint Byrum wrote: > > > Whatever API version is used behind the compute API is none of the user's > > business. > > Actually, yeah, it is. > > If I write an app or a tool that expects

[openstack-dev] [keystone] [stable/mitaka] Error: Discovering versions from the identity service failed when creating the password plugin....

Hi, I am getting below error while starting openstack devstack with stable/mitaka release. can someone look at this problem ? *Detail Error Logs:*2016-06-21 04:11:49.831 | ++^[[3242muserrc_early:source:11 ^[(B^[[m export OS_REGION_NAME=RegionOne 2016-06-21 04:11:49.857 |

Re: [openstack-dev] [Kuryr] jenkins failures "POST_FAILURE",

On 06/21/2016 06:35 AM, Vikas Choudhary wrote: > Hi Team, > > Since yesterday, I am observing abnormal jenkins failures on some of > patches while others are fine. Also not able to access logs for failures. > > https://review.openstack.org/#/c/326303/8 > Jenkins check Jun 20 12:32 PM >

Re: [openstack-dev] [Kuryr] jenkins failures "POST_FAILURE", logs not accessible

It seems to be working now after recheck. Ignore please for now. Regards Vikas On Tue, Jun 21, 2016 at 10:05 AM, Vikas Choudhary < choudharyvika...@gmail.com> wrote: > Hi Team, > > Since yesterday, I am observing abnormal jenkins failures on some of > patches while others are fine. Also not

[openstack-dev] [Kuryr] jenkins failures "POST_FAILURE", logs not accessible

Hi Team, Since yesterday, I am observing abnormal jenkins failures on some of patches while others are fine. Also not able to access logs for failures. https://review.openstack.org/#/c/326303/8 Jenkins check Jun 20 12:32 PM gate-kuryr-docs

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Hi! Before things getting said twice (looks that there is some public interest here ;-) ): Can you please rerun and skip the partition part of the loop device for fdisk -l? E.g. instead of /dev/loop0p1 just /dev/loop0? (This was my original intend but maybe not correctly described.) Also can

[openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Hi Chris, stackers, OK, so I've been a pretty vocal proponent of Chris' approach to the new placement REST API endpoint, which is to use no WSGI frameworks and instead just use the selector library (or Routes as a second choice) for defining the URI mappings. However, I had a chat with Doug

Re: [openstack-dev] [requirements][all] VOTE to expand the Requirements Team

Thank you all. On Mon, Jun 20, 2016 at 6:39 PM, Davanum Srinivas wrote: > Thanks for the VOTE everyone. > > Matthew, Dirk, Swapnil, Tony, Thomas, > With this VOTE the training wheels come off :) Please be cautious with > your new super powers! Dims, yes of course :) > > And

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for the fuel-web-core team

Well, the agreement is reached. I added Ilya to fuel-web-core group. Ilya, congratulations! Will be happy to see even more thorough reviews from you! Regards, Bulat Gaifullin Mirantis Inc. > On 08 Jun 2016, at 20:52, Bulat Gaifullin wrote: > > Hey Fuelers, > > I'd

Re: [openstack-dev] [nova] Do we need a config option for use_usb_tablet/pointer_model?

On Fri, Jun 17, 2016 at 03:36:53PM -0500, Matt Riedemann wrote: > I was reviewing the last change in this blueprint series today: > > https://review.openstack.org/#/c/174854/ > > And started to question why we even have a config option for this anymore. > The blueprint didn't have a spec but

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Hello Clint. I'd like to take part as well, so count me in. Kind regards, Denys Makogon 2016-06-20 10:23 GMT+03:00 Ghe Rivero : > Hi all! > I really like the idea of the group, so count me in! > > Ghe Rivero > > Quoting Clint Byrum (2016-06-17 23:52:43) > >

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

On Mon, Jun 20, 2016, at 03:52 PM, Jay Pipes wrote: > Hi dib-gurus, > > I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX > with a AMD A8-5557M APU with Ubuntu 16.04 installed and getting an odd > error. Hoping someone has some ideas... > > The command I am running is: > >

Re: [openstack-dev] Version header for OpenStack microversion support

FYI, Cinder implemented using the style recommended by the API-wg: https://review.openstack.org/#/c/224910 From: Sean Dague Sent: Monday, June 20, 2016 6:32:10 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Version header

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

Somehow, this thread hid from me for a couple of weeks. I just reviewed something relevant to this here [1]. It proposes adding tenant id to segment. But, it also enforces that tenant id is the same as that of the network owning the segment. So, I say why store it at all? I would argue that

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Excerpts from Jay Pipes's message of 2016-06-20 16:52:38 -0400: > Hi dib-gurus, > > I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX > with a AMD A8-5557M APU with Ubuntu 16.04 installed and getting an odd > error. Hoping someone has some ideas... > > The command I am

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

On 06/20/2016 06:12 PM, Clint Byrum wrote: Excerpts from Jay Pipes's message of 2016-06-20 16:52:38 -0400: Hi dib-gurus, I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX with a AMD A8-5557M APU with Ubuntu 16.04 installed and getting an odd error. Hoping someone has some

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

On 06/20/2016 06:24 PM, Gregory Haynes wrote: On Mon, Jun 20, 2016, at 03:52 PM, Jay Pipes wrote: Hi dib-gurus, I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX with a AMD A8-5557M APU with Ubuntu 16.04 installed and getting an odd error. Hoping someone has some ideas...

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Ahh derp, that's not an ARM CPU. I read "A8" and "APU" and my brain immediately lept to that. Ignore me. Excerpts from Clint Byrum's message of 2016-06-20 15:12:23 -0700: > Excerpts from Jay Pipes's message of 2016-06-20 16:52:38 -0400: > > Hi dib-gurus, > > > > I'm trying to build a simple

[openstack-dev] [Infra] Meeting Tuesday June 21st at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday June 21st, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agenda

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Excerpts from Gregory Haynes's message of 2016-06-20 17:24:28 -0500: > On Mon, Jun 20, 2016, at 03:52 PM, Jay Pipes wrote: > > Hi dib-gurus, > > > > I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX > > with a AMD A8-5557M APU with Ubuntu 16.04 installed and getting an odd >

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Hi all, During the discussion in this ML and team meetings, it seems most of us accepted the idea of supporting heterogeneous cluster. What we didn't agree well is how to implement it. To move it forward, I am going to summarize various implementation options so that we can debate each options

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

On 06/20/2016 06:41 PM, Paul Belanger wrote: On Mon, Jun 20, 2016 at 04:52:38PM -0400, Jay Pipes wrote: Hi dib-gurus, I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX with a AMD A8-5557M APU with Ubuntu 16.04 installed and getting an odd error. Hoping someone has some

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

On Mon, Jun 20, 2016, at 06:01 PM, Jay Pipes wrote: > On 06/20/2016 06:41 PM, Paul Belanger wrote: > > On Mon, Jun 20, 2016 at 04:52:38PM -0400, Jay Pipes wrote: > >> Hi dib-gurus, > >> > >> I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX with > >> a > >> AMD A8-5557M APU

Re: [openstack-dev] [kolla] Cinder multiple backends

Hi Michal and Ryan, Thank you so much by explanation. After instructions provide by Michal, I got built the container with additional packs. It folows the report: 1 - It was created a /etc/kolla/config/include_build/cinder-volume.include file with the content: {% if base_distro == 'ubuntu'