[openstack-dev] [Neutron][Dragonflow] - Documentation

Hello All, We have recently uploaded a big amount of documents and diagrams to Dragonflow repository in order to expose what we are doing and make it as simple as we can for new contributors and users to start using Dragonflow. I have created a wiki page for Dragonflow [1]. Some recommended

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

On 2015-12-12 14:20:29 + (+), Yuriy Taraday wrote: > Tempest jobs in all our projects seem to become broken after tox 2.3.0 > release yesterday. It's a regression in tox itself: > https://bitbucket.org/hpk42/tox/issues/294 > > I suggest us to add tox to upper-constraints to avoid this

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

On 2015-12-12 16:51:09 + (+), Jeremy Stanley wrote: [...] > No, it won't, since upper-constraints is merely used to constrain > requirements lists. I take that back, the pip_install function in DevStack applies upper-constraints.txt on anything it installs, but regardless it's misleading

Re: [openstack-dev] Mesos Conductor usingcontainer-createoperations

Hi Hongbin, The proposal sounds reasonable: basically it provides an agnostic alternative to the single command line that a user can invoke with docker or kubectl. If the user needs more advanced support (environment variables, volumes, network, ...), we would defer to the COE support and

[openstack-dev] [all] tox 2.3.0 broke tempest jobs

Tempest jobs in all our projects seem to become broken after tox 2.3.0 release yesterday. It's a regression in tox itself: https://bitbucket.org/hpk42/tox/issues/294 I suggest us to add tox to upper-constraints to avoid this breakage for now and in the future: https://review.openstack.org/256947

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

Good initiative, will have to get infra folks and lifeless to chime in. For now we need devstack cores help with merging possibly https://review.openstack.org/#/c/256620/ -- dims > On Dec 12, 2015, at 4:20 PM, Yuriy Taraday wrote: > > Tempest jobs in all our projects

Re: [openstack-dev] [ansible] One or more undefined variables: 'dict object' has no attribute 'bridge'

Hi Mark, I haven't reviewed your configs yet but if "bridge" is a valid ansible inventory attribute , then this error is usually caused by trying to reference a host that ansible didn't check in on yet / gather facts on. At least this is what is has been in my brief experience. For example if I

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

Awesome thanks so much Jeremy for tracking this down. -- Dims On Sat, Dec 12, 2015 at 9:55 PM, Jeremy Stanley wrote: > On 2015-12-12 21:18:29 +0300 (+0300), Davanum Srinivas wrote: >> Here's a really recent failure : >>

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

Hi, Jeremy. On Sat, Dec 12, 2015 at 8:27 PM Jeremy Stanley wrote: > On 2015-12-12 16:51:09 + (+), Jeremy Stanley wrote: > [...] > > No, it won't, since upper-constraints is merely used to constrain > > requirements lists. > > I take that back, the pip_install function

[openstack-dev] [openstack][nova] Microversions support for extensions without Controller

Hi all, os-user-data extension implements server_create method to add user_data for server creation. No Controller is used for this, only "class UserData(extensions.V21APIExtensionBase)". I want to add server_update method allowing to update the user_data. Obviously I have to add it as a

[openstack-dev] [nova] Microversions support for extensions without Controller

Hi all, os-user-data extension implements server_create method to add user_data for server creation. No Controller is used for this, only "class UserData(extensions.V21APIExtensionBase)". I want to add server_update method allowing to update the user_data. Obviously I have to add it as a

Re: [openstack-dev] neutron metadata-agent HA

The neutron metadata agent is stateless. It takes requests from the metadata proxies running in the router namespaces and moves the requests on to the nova server. If you're using HA routers, start the neutron-metadata-agent on every machine the L3 agent runs, and just make sure that the

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

Jeremy, Here's a really recent failure : http://logs.openstack.org/30/256130/5/check/gate-tempest-dsvm-neutron-src-taskflow/5845dd4/logs/devstacklog.txt.gz tox still is 2.3.0 - http://logs.openstack.org/30/256130/5/check/gate-tempest-dsvm-neutron-src-taskflow/5845dd4/logs/pip-freeze.txt.gz

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

On Sat, Dec 12, 2015 at 10:27 PM Jeremy Stanley wrote: > On 2015-12-12 19:00:23 + (+), Yuriy Taraday wrote: > > I think it should be a good first step in right direction. For example, > > with today's issue it would break gate for tempest itself only since all > >

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

On 2015-12-12 21:18:29 +0300 (+0300), Davanum Srinivas wrote: > Here's a really recent failure : > http://logs.openstack.org/30/256130/5/check/gate-tempest-dsvm-neutron-src-taskflow/5845dd4/logs/devstacklog.txt.gz > tox still is 2.3.0 - >

Re: [openstack-dev] [all] tox 2.3.0 broke tempest jobs

On 2015-12-12 19:00:23 + (+), Yuriy Taraday wrote: > I think it should be a good first step in right direction. For example, > with today's issue it would break gate for tempest itself only since all > other jobs would have preinstalled tox reverted to one mentioned in > upper-constraints.

Re: [openstack-dev] Mesos Conductor usingcontainer-createoperations

On Dec 12, 2015, at 9:19 AM, Ton Ngo > wrote: Hi Hongbin, The proposal sounds reasonable: basically it provides an agnostic alternative to the single command line that a user can invoke with docker or kubectl. If the user needs more advanced support

Re: [openstack-dev] [Infra][nova][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

Hi, As Kai Qiang mentioned, magnum gate recently had a bunch of random failures, which occurred on creating a nova instance with 2G of RAM. According to the error message, it seems that the hypervisor tried to allocate memory to the nova instance but couldn’t find enough free memory in the