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

Good work~ 2015-12-13 15:38 GMT+08:00 Gal Sagie : > 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

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

On 12/12/15, 10:44 PM, "Assaf Muller" wrote: >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

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

On Sun, Dec 13, 2015 at 12:14 PM Shinobu Kinjo wrote: > What is the current status of this failure? > > > 2015-12-13 08:55:04.863 | ValueError: need more than 1 value to unpack > It shouldn't reappear in gate because CI images have been reverted to tox 2.2.1. It can be

[openstack-dev] [astara][requirements] astara-appliance has requirements not in global-requirements

Astara team, The requirements proposal job complains about astara-appliance with: 'gunicorn' is not in global-requirements.txt Please get this requirement into global-requirements or remove it. Details: https://jenkins.openstack.org/job/propose-requirements-updates/602/consoleFull

[openstack-dev] [Neutron][Dragonflow] - IRC Meeting tomorrow (12/14) - 0900 UTC

Hello All, We will have an IRC meeting tomorrow (Monday, 12/14) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last meeting action items and logs here:

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

What is the current status of this failure? > 2015-12-13 08:55:04.863 | ValueError: need more than 1 value to unpack Thank you Shinobu On Sun, Dec 13, 2015 at 4:48 AM, Yuriy Taraday wrote: > On Sat, Dec 12, 2015 at 10:27 PM Jeremy Stanley wrote: > >>

[openstack-dev] [Neutron] HELP CONFIRM OR DISCUSS: How to add extension common attributes into db table 'standardattributes'

Hi guys, Could you give some good ideas about add neutron common attributes into db table 'standardattributes'? Like timestamp, it must be a common one should be added. The table 'standardattributes' is imported from [1]. It must be neutron common attrs should be added into this table in the

[openstack-dev] [all] broken gitreviews after stackforge rename

A lot of projects still have broken .gitreview files after the stackforge rename two months ago ;(. This will make contribution by new users difficult - and break all our automation jobs. Please check https://review.openstack.org/#/q/status:open++topic:stackforge-retirement,n,z and approve

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

Thank you for your confirmation. Something installed tox onto my CentOS7, 3.10.0-229.el7.x86_64 because of dependency. I need to elaborate more. Shinobu On Sun, Dec 13, 2015 at 6:47 PM, Yuriy Taraday wrote: > On Sun, Dec 13, 2015 at 12:14 PM Shinobu Kinjo

[openstack-dev] [Kuryr] IRC Meeting - Tuesday 0300 UTC (12/15)

Hello All, I have updated the agenda for the upcoming Kuryr IRC meeting [1] Please review and add any additional topics you might want to cover. Also please go over last meeting action items [2] , there are still patches (IPAM) that are looking for review love :) Since this is the week we do

Re: [openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines

On Thu, Dec 10, 2015 at 06:20:44PM +, Flavio Percoco wrote: > Greetings, > > I'd like to explore the possibility of having .ics generated - pretty > much the same way we generate it for irc-meetings - for the OpenStack > release schedule and project's deadlines. I believe just 1 calendar >

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

It is as 'single' as active L3 router that is handling traffic at current point of time. On Sun, Dec 13, 2015 at 11:13 AM, Gary Kotton wrote: > > > > > > On 12/12/15, 10:44 PM, "Assaf Muller" wrote: > > >The neutron metadata agent is stateless. It takes

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

Hi Mark, What Wade said is spot on, there's a missing entry in your inventory. From looking at your configuration it seems you need to add this stanza [0], or something like it, in to your `openstack_user_config.yml` file under the "provider_networks" section. This will add the required

Re: [openstack-dev] [Keystone][Tempest] OS-INHERIT APIs were skipped by Jenkins because "os_inherit" in keystone.conf was disable.

Hi Henry, When adding this extension on https://review.openstack.org/#/c/35986/ , the extension is disabled as the default setting. Now can we enable this os_inherit extension on Keystone side like keystone/common/config.py 'os_inherit': [ - cfg.BoolOpt('enabled', default=False, +

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

Hi, I think for this kind of change you should register a Blueprint and submit a spec for discussion. Sounds like it will be a bit change. BR On Sun, Dec 13, 2015 at 2:18 AM, Alexandre Levine wrote: > Hi all, > > os-user-data extension implements server_create

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

Sorry, s/bit/big On Mon, Dec 14, 2015 at 10:46 AM, Zhenyu Zheng wrote: > Hi, I think for this kind of change you should register a Blueprint and > submit a spec for discussion. Sounds like it will be a bit change. > > BR > > On Sun, Dec 13, 2015 at 2:18 AM, Alexandre

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

Hi Kevin, On 2015/12/14 11:10, Kevin Benton wrote: Hi all, The availability zone code added a new field to the network API that shows the availability zones of a network. This caused a pretty big performance impact to get_networks calls because it resulted in a database lookup for every

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

Hi, Can we just add "availability_zones" as one Column in Network? And update it when "NetworkDhcpAgentBinding" updates. The code will be a bit more complex, but it can save the time when retrieving Network resource. From: Hirofumi Ichihara To:

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

Thanks cloudnull, This solved the installation issue. I commented out all non-flat related networks before, to investigate my main problem, which is > PortBindingFailed: Binding failed for port > fe67a2d5-6d6a-4440-80d0-acbe2ff5c27f, please check neutron logs for more > information. I still

Re: [openstack-dev] [trove] Upcoming specs and blueprints for Trove/Mitaka

On 10/12/15 20:05 +, Amrith Kumar wrote: Flavio, The issue we had in the last cycle was that a lot of specs and code arrived for review late in the process and this posed a challenge. The intent this time around was to ensure that there wasn't such a back-end loaded process and that

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

The L3 agent monitors the metadata proxies it spawns and restarts them automatically. You should be using an external tool to restart the metadata *agent* in case that crashes. On Sun, Dec 13, 2015 at 7:49 AM, Gary Kotton wrote: > > > From: Eugene Nikanorov

[openstack-dev] [Group Based Policy] [Policy] [GBP]

Hello, how can i write an application with gbp using the libcloud? Thanks in advance. Best regards, ernesto __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

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

From: Eugene Nikanorov > Reply-To: OpenStack List > Date: Sunday, December 13, 2015 at 12:09 PM To: OpenStack List

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

On Sat, Dec 12, 2015, at 02:16 PM, Hongbin Lu wrote: > 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

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

Hi, OVH is a new cloud provider for openstack-infra nodes: http://www.openstack.org/blog/2015/12/announcing-a-new-cloud-provider-for-openstacks-ci-system-ovh/ It appears that selection of nodes on any cloud provider is a matter of luck: "When a developer uploads a proposed change to an

Re: [openstack-dev] [nova][serial-console-proxy]

On Fri, Dec 11, 2015 at 11:07:02AM +0530, Prathyusha Guduri wrote: > Hi All, > > I have set up open stack on an Arm64 machine and all the open stack related > services are running fine. Also am able to launch an instance successfully. > Now that I need to get a console for my instance. The noVNC

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

On 13 December 2015 at 03:20, 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

Re: [openstack-dev] [oslo] stable/liberty branch needed for oslo-incubator

On 12/11/2015 10:24 PM, Davanum Srinivas wrote: Matt, Do you have an example? This was a deliberate decision to leave it out. -- Dims On Sat, Dec 12, 2015 at 4:35 AM, Matt Riedemann wrote: oslo-incubator is EOL now but it's missing a stable/liberty branch, and

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

I see, so regular users are supposed to use this information as well. But how are they supposed to use it? For example, if they see that their network has availability zones 1 and 4, but their instance is hosted in zone 3, what are they supposed to do? On Sun, Dec 13, 2015 at 8:57 PM, Hirofumi

Re: [openstack-dev] [Keystone][Tempest] OS-INHERIT APIs were skipped by Jenkins because "os_inherit" in keystone.conf was disable.

A devstack patch is https://review.openstack.org/#/c/257085/ for enabling os_inherit extension. 2015-12-14 10:43 GMT+09:00 Ken'ichi Ohmichi : > Hi Henry, > > When adding this extension on https://review.openstack.org/#/c/35986/ > , the extension is disabled as the default

[openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

Hi all, The availability zone code added a new field to the network API that shows the availability zones of a network. This caused a pretty big performance impact to get_networks calls because it resulted in a database lookup for every network.[1] I already put a patch up to join the

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

Adrian, Its a real shame Atomic can't execute its mission - serve as a container operating system. If you need some guidance on image building find experienced developers on #kolla – we have extensive experience in producing containers for various runtime environments focused around

Re: [openstack-dev] [oslo] stable/liberty branch needed for oslo-incubator

On 14 December 2015 at 15:28, Matt Riedemann wrote: > > > I don't have a pressing need to backport something right now, but as long as > there was code in oslo-incubator that *could* be synced to other projects > which wasn't in libraries, then that code could have

Re: [openstack-dev] [Neutron] HELP CONFIRM OR DISCUSS: How to add extension common attributes into db table 'standardattributes'

I would avoid trying to make special functions that are meant for everyone to use to interact with the standard attribute table. There are a wide variety of use cases (1:1 relationships, 1:M relationships, stuff visible in the API, stuff internal to Neutron, etc) and trying to guess how they will

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

Yes, as I'm starting to understand the use case, I think it would actually make more sense to add an AZ-network mapping table. Then whatever implementation can populate them based on the criteria it is using (reference would just do it on agent updates). On Sun, Dec 13, 2015 at 9:53 PM, Hong Hui

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

On 2015/12/14 15:58, Kevin Benton wrote: What decision would lead the user to request AZ1 and AZ2 in the first place? Especially since when it fails to get AZ2, they just request again with AZ1 and AZ3 instead. I expected that user gets AZ1 and AZ2 (and AZ3) via GET Availability zones API

Re: [openstack-dev] [Fuel] Separate master node provisioning and deployment

Oleg, Thanks a lot for your opinion. Here are some more thoughts on this topic. 1) For a package it is absolutely normal to throw a user dialog. But probably there is kind of standard for the dialog that does not allow to use fuelmenu. AFAIK, for DEB packages it is debconf and there is a

[openstack-dev] [nova-scheduler] Scheduler sub-group meeting - Agenda 12/14

Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT) 1) Spec & BPs - https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking 2) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler 3) Opens -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph:

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

On 2015/12/14 14:52, Kevin Benton wrote: I see, so regular users are supposed to use this information as well. But how are they supposed to use it? For example, if they see that their network has availability zones 1 and 4, but their instance is hosted in zone 3, what are they supposed to

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

What decision would lead the user to request AZ1 and AZ2 in the first place? Especially since when it fails to get AZ2, they just request again with AZ1 and AZ3 instead. On Sun, Dec 13, 2015 at 10:31 PM, Hirofumi Ichihara < ichihara.hirof...@lab.ntt.co.jp> wrote: > > > On 2015/12/14 14:52, Kevin

Re: [openstack-dev] [nova][serial-console-proxy]

Hi Tony, Thanks a lot for your response. I actually did a rejoin-stack.sh which will also restart n-api and all other services. But still the same issue. Anyway now that I've to run all over again, will change my local.conf according to the guide and run stack. Will keep you updated. Thanks,