Re: [openstack-dev] [oslo][keystone] Move oslo.policy from oslo to keystone

On Thu, Dec 17 2015, Flavio Percoco wrote: > Just want to +1 all the above. > > It'd be great if we can finally hand the library over to the keystone > team, where I think it belongs. While I have nothing against moving oslo.policy to Keystone, I would like to emphasize that one of the upside

Re: [openstack-dev] [cinder] Custom fields for versioned objects

On 15/12, Ryan Rossiter wrote: > Thanks for the review Michal! As for the bp/bug report, there’s four options: > > 1. Tack the work on as part of bp cinder-objects > 2. Make a new blueprint (bp cinder—object-fields) I think #2 would be the best option, as this is not part of the effort to move

Re: [openstack-dev] [Performance][Holidays] IRC meeting schedule

Ok, so let's assume everyone is ok with the proposed schedule :) *Dear Performance Team folks, do not have more meetings this year and have the first meeting on Jan 12, 2016 .* Thanks everyone for short for our team,

[openstack-dev] [Fuel][UX] Throw KVM\QEMU and leave Libvirt on Wizard

Hi fuelers, We want to throw KVM/QEMU options from Wizard and instead of them leave only one: Libvirt [0]. Libvirt option enables QEMU by default and there are still be possibility to change it on KVM in settings. It looks more logically because both QEMU\KVM are options for libvirt which manage

Re: [openstack-dev] [kolla][nova] Orchiestrated upgrades in kolla

Thank you for clarification. -marek On 17.12.2015 18:02, Michał Jastrzębski wrote: Hey, Since our instances (and qemu) is in different container than nova services, there is no reason (specific to kolla) to meddle with them. Ofc it would be required if you'd like to upgrade qemu, but that's

Re: [openstack-dev] Announcing Gertty 1.3.0

On 12/17/2015 11:59 PM, James E. Blair wrote: > Announcing Gertty 1.3.0 > === > > Gertty is a console-based interface to the Gerrit Code Review system. > > Gertty is designed to support a workflow similar to reading network > news or mail. It syncs information from Gerrit to

Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

I think it might be a bit early to start a cross-project discussion on this. I'd suggest to first figure out what questions do we have, what would we like to get from nova. So I think it'd be more constructive if we first think on it within neutron team. I left some questions on the bug [1],

[openstack-dev] [neutron]how to import neutron module file for other official project ?

Hi All, how to import neutron module file for other official project ? Consider import neutron-lib to be use.. https://github.com/openstack/neutron-lib/blob/master/neutron_lib/exceptions.py What needs to be modify in official project to make it work? *Getting below error:* File

[openstack-dev] [fuel] Release schedule and branching strategy for Fuel 8.0/liberty and 9.0/mitaka

Team, With Fuel 8.0 Soft Code Freeze approaching, it's time to switch to the new branching strategy and implement the plan to align Fuel releases with OpenStack release cycles that we have discussed back in August [0]. [0]

Re: [openstack-dev] [gate] job failure rate at ~ 12% (check queue) <= issue?

Sean Dague wrote on 12/17/2015 04:48:17 PM: > From: Sean Dague > To: openstack-dev@lists.openstack.org > Date: 12/17/2015 04:48 PM > Subject: Re: [openstack-dev] [gate] job failure rate at ~ 12% (check > queue) <= issue? > > On 12/17/2015 05:52 AM, Markus

Re: [openstack-dev] [neutron][grenade] l3.filters fail to update at test server

Zong Kai YL Li wrote: >> Hi, all. >> I met a problem when I submitted a neutron l3 related patch, I updated >> l3.filters to add a rootwrap for command arp, but on test server, grenade >> seems doesn't update l3.filters, that cause gate-grenade-dsvm-neutron >> failed. >>

Re: [openstack-dev] [neutron]how to import neutron module file for other official project ?

P. Ramanjaneya Reddy wrote: Hi All, how to import neutron module file for other official project ? Consider import neutron-lib to be use.. https://github.com/openstack/neutron-lib/blob/master/neutron_lib/exceptions.py What needs to be modify in official project to

Re: [openstack-dev] Cleaning Up Deprecation Warnings in the Gate

On Thu, Dec 10, 2015 at 07:46:00PM -0500, Matthew Treinish wrote: > On Thu, Dec 10, 2015 at 03:03:01PM -0500, gord chung wrote: > > > > > > On 10/12/15 12:04 PM, Matthew Treinish wrote: > > >Using this query to see how many deprecation warning we emit on jobs > > >running on > > >master in the

Re: [openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

On Wed, Dec 09, 2015 at 01:42:13PM +0300, Sergey Kraynev wrote: >Hi Heaters, >On the last IRC meeting we had a question about Support Conditionals spec >[1]. >Previous attempt for this staff is here [2]. >The example of first POC in Heat can be reviewed here [3] >As I

[openstack-dev] [keystone] Addressing issue of keysone token expiry during long running operations

Jamie John Garbutt suggested I follow up this issue with you. I understand you may be leading the effort to address the issue of token expiry during a long running operation. Nova encounter this scenario during image snapshots and live migrations. Is there a keystone blueprint for this

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11 completed.

On 12/16/2015 11:40 PM, Zaro wrote: > We have identified this and will look into it soon. Thanks for > reporting the issue. > > On Wed, Dec 16, 2015 at 2:02 PM, Michał Dulko wrote: >> On 12/16/2015 10:22 PM, Zaro wrote: >>> Thanks to everyone for their patience while we

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11 completed.

On 12/16/2015 10:22 PM, Zaro wrote: On Tue, Dec 1, 2015 at 6:38 PM, Spencer Krum wrote: Hi All, The infra team will be taking gerrit offline for an upgrade on December 16th. We will start the operation at 17:00 UTC and will continue until about 21:00 UTC. This outage is

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

On 12/17/2015 04:45 PM, Ihar Hrachyshka wrote: Rossella Sblendido wrote: Hi Ihar, wow, good job!! Sorry for the very slow reply. I really like your proposal...some comments inline. On 12/03/2015 04:46 PM, Ihar Hrachyshka wrote: Hi, Small update on the RFE. It was

Re: [openstack-dev] [Fuel][Bareon] Fuel & Bareon integration (fuel modularisation)

+1 For Evgeniy, Also guys, as you know - fuel-agent now uses for a lot of different things : IBP\bootstrap\ironic\disk_managment at many other. I hope you are not going to remove all this functionality with re-factoring process. On Thu, Dec 17, 2015 at 4:53 PM, Evgeniy L

Re: [openstack-dev] [Fuel] Proposal to Delay Docker Removal From Fuel Master Node

Hi, having or not having docker on Fuel master affects mostly Fuel node deployment related scripts/manifests. If we need to fix a bug in Nailgun or OSTF - we can fix it in their codebase and it does not really matter whether we run Nailgin or OSTF inside docker or not. The same goes for all the

Re: [openstack-dev] [Fuel][UX] Throw KVM\QEMU and leave Libvirt on Wizard

Hi, looks good to me. Regards, Alex On Fri, Dec 18, 2015 at 10:17 AM, Andriy Popovych wrote: > Hi fuelers, > > We want to throw KVM/QEMU options from Wizard and instead of them leave > only one: Libvirt [0]. Libvirt option enables QEMU by default and there are > still

[openstack-dev] [neutron] 'NetworkNotFound' exception during listing ports

Hello, I have a problem - when I run tests in parallel then one/two can fail. As I see in logs one thread is deleting network while second thread is listing all ports. And second thread get result 'NetworkNotFound'. Part of neutron service logs is here - http://paste.openstack.org/show/482292/

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

On 12/17/2015 05:07 PM, Ihar Hrachyshka wrote: We may probably think of passing agent uuid into extensions to allow it to be used as a cookie for their flows, and make sure extensions are triggered before we reset obsolete flows in the agent. It may work. I would only want to see it as a

[openstack-dev] [nova] No team meeting for the next two weeks

Hi, Given so many folks are out, no Nova meeting for the next two weeks: https://wiki.openstack.org/wiki/Meetings/Nova Happy holidays, for those on holiday over the next few weeks! Thanks, johnthetubaguy PS I am mostly out for the next two weeks, taking time to recover from this year. Email

[openstack-dev] [murano][i18n] let's start translating murano

We’ve been receiving requests to get murano translated for some time and I’m happy to say that you can start doing that today. Murano is up on zanata [1]. So if you’re using murano and want to see it translated in your language and are willing to help that — please join the translation efforts.

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11 completed.

On 12/18/2015 06:48 AM, Dmitry Tantsur wrote: > On 12/16/2015 10:22 PM, Zaro wrote: >> On Tue, Dec 1, 2015 at 6:38 PM, Spencer Krum >> wrote: >>> Hi All, >>> >>> The infra team will be taking gerrit offline for an upgrade on December >>> 16th. We >>> will start the operation

Re: [openstack-dev] [Fuel] Proposal to Delay Docker Removal From Fuel Master Node

Hi all, I have one concern related to 8.0 bugfixing until GA. If we disable docker deployment in master, we will need to target docker-specific patches for 8.0 first to master and then backport to stable/8.0, which is still in line with our standard bugfixing strategy. It will mean we should

Re: [openstack-dev] [murano][i18n] let's start translating murano

On 12/18/2015 01:35 PM, Kirill Zaitsev wrote: We’ve been receiving requests to get murano translated for some time and I’m happy to say that you can start doing that today. Murano is up on zanata [1]. Note: It's up there and currently empty. It will get content *after* the next merge of any

Re: [openstack-dev] [Horizon] [Cinder] [Nova] [Neutron] Gathering quota usage data in Horizon

On 12/17/2015 2:40 PM, Ivan Kolodyazhny wrote: Hi Timur, Did you try this Cinder API [1]? Here [2] is cinderclient output. [1] https://github.com/openstack/python-cinderclient/blob/master/cinderclient/v2/quotas.py#L33 [2] http://paste.openstack.org/show/482225/ Regards, Ivan Kolodyazhny,

Re: [openstack-dev] [nova] proposed new compute review dashboard

Le 18/12/2015 15:20, Sean Dague a écrit : With Gerrit 2.11 upgrade in place, we get access to a few new query parameters. I've retooled the compute review dashboard in gerrit-dash-creator (https://github.com/openstack/gerrit-dash-creator) to take advantage of it. The url is -

[openstack-dev] [heat-translator] [tosca-parser] [heat] Heat-Translator 0.3.0 PyPI release

Hello Everyone, On behalf of the Heat-Translator team, I am pleased to announce the 0.3.0 PyPI release of heat-translator which can be downloaded from https://pypi.python.org/pypi/heat-translator This release includes following enhancements, Per project development plan, we will be having a

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

Hi, The idea behind configdb is that it is independent component that defines data flows between other components of the system. It has no knowledge about those components or specifics of their data. Data formats are defined by components themselves via schemas/templates and can be changed at any

[openstack-dev] [nova] proposed new compute review dashboard

With Gerrit 2.11 upgrade in place, we get access to a few new query parameters. I've retooled the compute review dashboard in gerrit-dash-creator (https://github.com/openstack/gerrit-dash-creator) to take advantage of it. The url is - https://goo.gl/1vTS0Z The contents are: [dashboard] title =

[openstack-dev] [glance][artifacts][app-catalog] Proposal to move artifacts meeting time

Hi folks, The current timeslot of our weekly IRC meeting for artifact subteam (14:00 UTC Mondays) seems a bit inconvenient: it's a bit early for people in the Pacific timezone. Since we want to maximise the presence of all the interested parties at our sync-ups, I'd propose to move our meeting to

Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

Hi, I'm also interested in live-migration in the context of two bugs in l2pop : https://bugs.launchpad.net/neutron/+bug/1483601 https://bugs.launchpad.net/neutron/+bug/1443421 Mathieu On Fri, Dec 18, 2015 at 11:16 AM, Oleg Bondarev wrote: > I think it might be a bit

Re: [openstack-dev] [murano][i18n] let's start translating murano

Thanks for noting that! I was probably a bit too excited for this =)  Anyway as of this moment murano project on zanata is populated with strings and is ready to be translated. =) --  Kirill Zaitsev Murano team Software Engineer Mirantis, Inc On 18 December 2015 at 16:16:17, Andreas Jaeger

Re: [openstack-dev] [keystone] Addressing issue of keysone token expiry during long running operations

Right now the solution is to increase the token expiration time in keystone config. I personally am working on a longer term solution but it is a ways out (regarding changing how services pass authorization around internally). Unfortunately the current architecture makes changing how token

[openstack-dev] [OpenStack-Infra] - Unable to save contact information in Gerrit

Receive a server error response when attempting to save Gerrit contact information on both the settings screen as well as when creating a new individual contributor agreement. Screenshot of error received: https://www.dropbox.com/s/0q7u0kku18132xg/Screenshot%202015-12-18%2010.32.09.png?dl=0

Re: [openstack-dev] [nova] proposed new compute review dashboard

On Fri, Dec 18, 2015 at 5:52 PM Matt Riedemann wrote: > This has come up before, but I think we should put something like this > in the nova IRC channel topic. Swift has something like this in their > IRC channel topic and it's very easy for someone new to the channel

Re: [openstack-dev] [nova][cinder] what are the key errors with volume detach

On 12/17/2015 9:24 AM, Matt Riedemann wrote: On 12/17/2015 8:51 AM, Andrea Rosa wrote: The communication with cinder is async, Nova doesn't wait or check if the detach on cinder side has been executed correctly. Yeah, I guess nova gets the 202 back:

Re: [openstack-dev] [nova] proposed new compute review dashboard

On 12/18/2015 8:20 AM, Sean Dague wrote: With Gerrit 2.11 upgrade in place, we get access to a few new query parameters. I've retooled the compute review dashboard in gerrit-dash-creator (https://github.com/openstack/gerrit-dash-creator) to take advantage of it. The url is -

Re: [openstack-dev] [neutron][stable] proactive backporting

Hi all, just wanted to note that the etherpad page [1] with backport candidates has a lot of work for those who have cycles for backporting relevant pieces to Liberty (and Kilo for High+ bugs), so please take some on your plate and propose backports, then clean up from the page. And please

Re: [openstack-dev] [gate] any project using olso.db test_migrations is currently blocked

On 12/16/2015 01:03 PM, Carl Baldwin wrote: On Wed, Dec 16, 2015 at 10:04 AM, Mike Bayer wrote: Instead of just breaking the world, and burning 10s to 100 engineer hours in redo tests and investigating and addressing the break after the fact. We shouldn't let this happen

Re: [openstack-dev] [Fuel][UX] Throw KVM\QEMU and leave Libvirt on Wizard

I think it may be confusing to a fair number of the users you are targeting. libvirt supports more then just qemu/kvm. xen, virtualbox, and others. saying libvirt makes people have to know that when you say libvirt you mean just the qemu/kvm that nova supports using the implementation detail of

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, completed.

On 12/17/2015 10:17 PM, Brian Haley wrote: On 2015-12-16 16:24, openstack-dev-requ...@lists.openstack.org wrote: Thanks to everyone for their patience while we upgraded to Gerrit 2.11. I'm happy to announce that we were able to successfully completed this task at around 21:00 UTC. You may

Re: [openstack-dev] [OpenStack-Infra] Announcing Gertty 1.3.0

Michał Dulko writes: > As this was sent to openstack-dev list, I'll ask a Gertty usage question > here. Was anyone able to use Gertty successfully behind a proxy? My > environment doesn't allow any traffic outside the proxy and I haven't > noticed a config option to set

[openstack-dev] [Fuel] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective

2015-12-17 20:49:36ERR[566] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective, trace: ["/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/orchestrator.rb:196:in `validate_nodes_access'",

Re: [openstack-dev] [keystone] Addressing issue of keysone token expiry during long running operations

On Fri, Dec 18, 2015 at 11:13:37AM +, Paul Carlton wrote: > Jamie > > John Garbutt suggested I follow up this issue with you. I understand you > may be leading the > effort to address the issue of token expiry during a long running operation. > Nova > encounter this scenario during image

[openstack-dev] [doc] DocImpact vs. reno

Recently noticed that a new job ended up on all nova changes that was theoertically processing commit messages for DocImpact. It appears to be part of this spec - http://specs.openstack.org/openstack/docs-specs/specs/mitaka/review-docimpact.html First, a heads up would be good. Nova burns a lot

[openstack-dev] [midonet] NAT64 support

Hi Devs, MidoNet does not support IPv6 (in overlay or underlay). As a small and practical first step towards supporting IPv6, I'm proposing support for NAT64. The idea is that a Tenant can configure NAT64 for any Floating IPv4. The Operator should have control over the IPv6 prefix (well-known

Re: [openstack-dev] [Tacker] No IRC weekly meetings next two weeks

You're right. Spell checking did change your name to Spider. Good idea about the face to face. Bruce T From: Sridhar Ramaswamy > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [magnum]storage for docker-bootstrap

Wanghua, I see. The circular dependency you described does sound like a formidable challenge. Having multiple docker daemons violates the principle of least surprise. I worry that when it comes time to perform troubleshooting, an engineer would be surprised to find multiple dockers running at

Re: [openstack-dev] [Fuel] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective

Hey John, On Fri, Dec 18, 2015 at 11:15 AM, John Menke wrote: > > > > 2015-12-17 20:49:36ERR[566] Error running RPC method verify_networks: > Network verification not avaliable because nodes ["1"] not avaliable via > mcollective, trace: >

[openstack-dev] [glance] OVF/OVA introspection in Mitaka?

Greetings, This spec[0] was started back in Liberty and I'd like to hear from the folks involved in this work whether the intent of moving this forward is still active and the goals. This has been a long standing request and as it's being presented it seems to have no impact on the current API

Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

Hi Oleg/Sean M Collins/Carl_baldwin/Kevin Benton/GaryK, Here is my thought. I have updated the bug report with the details. But this is for your information. Oleg in my opinion, the right time to create the floatingip infrastructure would be before the vm actually migrates and is planning to

Re: [openstack-dev] [Neutron] [IPv6] [radvd] Advertise tenant prefixes from router to outside

Hi Carl, As far as I understand Address Scopes, end user’s algorithm will be next: 1. Administrator creates an address scope and associate an IPv6 subnet pool with it. 2. Administrator creates Public shared network’s subnet from this subnet pool. 3. Tenant user creates tenant network from this

Re: [openstack-dev] [Horizon] [Cinder] [Nova] [Neutron] Gathering quota usage data in Horizon

The point raised by Matt for Nova applies to Neutron as well. Neutron does not have strict deadlines for blueprint approval; however even if in theory it would still be possible to achieve this for Mitaka, it is rather unlikely since the number of blueprints already in the pipeline is way more

Re: [openstack-dev] [Horizon] [Cinder] [Nova] [Neutron] Gathering quota usage data in Horizon

Matt, actually Ivan (Ivan, thanks a lot!) showed me the exact cinderclient call that I needed. Now I know how to retrieve Cinder quota usage info per-tenant, seems that to retrieve the same info cloud-wide I should sum up all the available tenant usages. With Cinder quota usages being sorted

Re: [openstack-dev] [doc] DocImpact vs. reno

On 12/18/2015 01:34 PM, Andreas Jaeger wrote: > On 12/18/2015 07:03 PM, Sean Dague wrote: >> Recently noticed that a new job ended up on all nova changes that was >> theoertically processing commit messages for DocImpact. It appears to be >> part of this spec - >>

Re: [openstack-dev] [doc] DocImpact vs. reno

On Fri, Dec 18, 2015 at 12:03 PM, Sean Dague wrote: > Recently noticed that a new job ended up on all nova changes that was > theoertically processing commit messages for DocImpact. It appears to be > part of this spec - > >

Re: [openstack-dev] [Fuel] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective

Alex, Thanks for the reply. i was able to get around the issue. I rebooted all my instances and the mcollective error went away. mco ping from fuel now returns 11 time ... 12 time ... 13 time... master tim... Now it's complaining that it can't hit some repos from the compute node. I logged

Re: [openstack-dev] [stable] meeting time proposal

On 16/12/15 13:12 -0600, Matt Riedemann wrote: I'm not entirely sure what the geo distribution is for everyone that works on stable, but I know we have people in Europe and some people in Australia. So I was thinking alternating weekly meetings: Mondays at 2100 UTC This is quite late for

[openstack-dev] [nova] [all] Excessively high greenlet default + excessively low connection pool defaults leads to connection pool latency, timeout errors, idle database connections / workers

Hi all - Let me start out with the assumptions I'm going from for what I want to talk about. 1. I'm looking at Nova right now, but I think similar things are going on in other Openstack apps. 2. Settings that we see in nova.conf, including: #wsgi_default_pool_size = 1000 #max_pool_size =

Re: [openstack-dev] [doc] DocImpact vs. reno

On 12/18/2015 07:03 PM, Sean Dague wrote: Recently noticed that a new job ended up on all nova changes that was theoertically processing commit messages for DocImpact. It appears to be part of this spec - http://specs.openstack.org/openstack/docs-specs/specs/mitaka/review-docimpact.html Lana

Re: [openstack-dev] [Fuel] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective

On Fri, Dec 18, 2015 at 12:52 PM, John Menke wrote: > Alex, > > Thanks for the reply. i was able to get around the issue. I rebooted all > my instances and the mcollective error went away. > > Yes rebooting the node will restart mcollective and cause it to reconnect. So

Re: [openstack-dev] [doc] DocImpact vs. reno

On 12/18/2015 07:45 PM, Sean Dague wrote: On 12/18/2015 01:34 PM, Andreas Jaeger wrote: On 12/18/2015 07:03 PM, Sean Dague wrote: Recently noticed that a new job ended up on all nova changes that was theoertically processing commit messages for DocImpact. It appears to be part of this spec -

Re: [openstack-dev] [Fuel] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective

OK - turns out the compute node was not resolving names. I reset the name server on the vlan100 interface and it seems to get pas that now On Fri, Dec 18, 2015 at 4:53 PM, John Menke wrote: > Tailing the logs on the compute node -- seeing some failing requests to > repos-

[openstack-dev] [openstack-ansible]

when running openstack ansible quick start ( curl https://raw.githubusercontent.com/openstack/openstack-ansible/master/scripts/run-aio-build.sh | sudo bash ) it will halt with the following error. ++ ansible-galaxy install --role-file=ansible-role-requirements.yml --ignore-errors --force - the

Re: [openstack-dev] [Fuel] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective

This should be interface Vlan100 ip address 192.168.1.240 255.255.255.0 ip helper-address 192.168.1.1 no shutdown ! On Fri, Dec 18, 2015 at 3:17 PM, Alex Schultz wrote: > > > On Fri, Dec 18, 2015 at 12:52 PM, John Menke wrote: > >> Alex, >> >>

Re: [openstack-dev] [OpenStack-Infra] - Unable to save contact information in Gerrit

On 2015-12-18 15:33:17 + (+), Truman, Travis wrote: > Receive a server error response when attempting to save Gerrit > contact information on both the settings screen as well as when > creating a new individual contributor agreement. > > Screenshot of error received: >

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, completed.

On 2015-12-18 16:56:46 -0500 (-0500), Sean Dague wrote: [...] > Works fine. Is it firefox specific? Given that the behavior works in > Chromium I suspect not working is not a design point but a bug to be > reported. Must be. Installing another browser to test this was on my to do list, but I

Re: [openstack-dev] [Fuel] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective

Alex, Thanks again. They should have access, i can ping the remote gateway from the compute machine and i have my network setup as in this configuration: https://github.com/openstack/fuel-docs/blob/master/pages/planning-guide/0090-appendix/0095-neutron-switch-cisco-2960g.rst I am using 2960TT

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, completed.

On 12/17/2015 10:17 PM, Brian Haley wrote: > On 2015-12-16 16:24, openstack-dev-requ...@lists.openstack.org wrote: >> Thanks to everyone for their patience while we upgraded to Gerrit >> 2.11. I'm happy to announce that we were able to successfully >> completed this task at around 21:00 UTC. You

Re: [openstack-dev] [doc] DocImpact vs. reno

Le 18/12/2015 20:31, Andreas Jaeger a écrit : On 12/18/2015 07:45 PM, Sean Dague wrote: On 12/18/2015 01:34 PM, Andreas Jaeger wrote: On 12/18/2015 07:03 PM, Sean Dague wrote: Recently noticed that a new job ended up on all nova changes that was theoertically processing commit messages for

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, completed.

On 2015-12-18 12:12:26 -0500 (-0500), Jay Pipes wrote: > On 12/17/2015 10:17 PM, Brian Haley wrote: [...] > >Trying to copy text from a review no longer works easily. When I > >highlight text there's a little "bubble" pop-up of {press c to comment}, > >which seems to interfere with both my

Re: [openstack-dev] [Fuel] Error running RPC method verify_networks: Network verification not avaliable because nodes ["1"] not avaliable via mcollective

Tailing the logs on the compute node -- seeing some failing requests to repos- will sift through that and post more info. On Fri, Dec 18, 2015 at 4:00 PM, John Menke wrote: > This should be > > interface Vlan100 > ip address 192.168.1.240 255.255.255.0 > ip helper-address

[openstack-dev] OpenStack Developer Mailing List Digest December 12-18

Perma link: http://www.openstack.org/blog/2015/12/openstack-developer-mailing-list-digest-20151218/ Success Bot Says * jroll: Ironic is using the devstack plugin. * Tell us yours via IRC with a message “#success [insert success]”. * All: https://wiki.openstack.org/wiki/Successes

Re: [openstack-dev] [doc] DocImpact vs. reno

On 12/18/2015 02:31 PM, Andreas Jaeger wrote: > On 12/18/2015 07:45 PM, Sean Dague wrote: >> On 12/18/2015 01:34 PM, Andreas Jaeger wrote: >>> On 12/18/2015 07:03 PM, Sean Dague wrote: Recently noticed that a new job ended up on all nova changes that was theoertically processing commit

Re: [openstack-dev] [glance] OVF/OVA introspection in Mitaka?

Flavio, I uploaded a patch 15. Your comment about making import available to non-admin users and Mike Gerdt's comments with ova schema references Prompts the question how important is it to support upload of compressed ova. I am happy to jettison the compressed support for generally available.

Re: [openstack-dev] [neutron] 'NetworkNotFound' exception during listing ports

Ah, I believe what is happening is that the network is being deleted after the port has been retrieved from the database during the policy check. The policy check retrieves the port's network to be able to enforce the network_owner lookup: