Re: [openstack-dev] [barbican] python-barbicanclient-master.tar.gz outdated on tarballs.openstack.org

On Sat, 2015-08-29 at 19:05 +, Jeremy Stanley wrote: > On 2015-08-29 18:44:55 +0200 (+0200), Thomas Bechtold wrote: > > on http://tarballs.openstack.org/python-barbicanclient/ , master > > tarball is not the latest git version. Something seems to be > > broken. > > Any hints how to solve that?

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Hi Vivek I merged the repo into openstack-dashboard and restated the apache2, new panel did not show up. Any special things that should be done for getting it? Regards, Evg From: Jain, Vivek [mailto:vivekj...@ebay.com] Sent: Monday, August 03, 2015 6:09 PM To: OpenStack Development Mailing List

Re: [openstack-dev] [barbican] python-barbicanclient-master.tar.gz outdated on tarballs.openstack.org

On 2015-08-30 10:23:32 +0200 (+0200), Thomas Bechtold wrote: [...] > Maybe the tarball won't be regenerated if only a new git tag is pushed? > In that case the latest commit-id doesn't change but the content of the > tarball need to change (from 3.2.1.dev24 to 3.3.0). Correct, nobody has implement

Re: [openstack-dev] [neutron][L3][dvr][fwaas] FWaaS with DVR

On 08/28/2015 02:53 PM, Germy Lure wrote: Hi all, I have two points. a. For the problem in this thread, my suggestion is to introduce new concepts to replace the existing firewall and SG. Perhaps you have found the overlap between firewall and SG. It's trouble for user to select. So the new co

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Hi Evgeny, Did you add “loadbalancerv2" dir next to “loadbalancer” under openstack_dashboard/dashboards/project/ ? Thanks, Vivek From: Evgeny Fedoruk mailto:evge...@radware.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>>

Re: [openstack-dev] [Fuel] How much do we rely on dnsmasq?

6to4 is a whole different story. I'd prefer to avoid it unless there are seriously compelling reasons to support it. I think dual stack is the way to implement IPv6 support in Fuel. -- Sean M. Collins __ OpenStack Development

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Vivek, Is there a wiki or some document somewhere that explains how to get this running? Sorry if it's been posted somewhere else and I missed it. On Sun, 2015-08-30 at 18:36 +, Jain, Vivek wrote: > Hi Evgeny, > Did you add “loadbalancerv2" dir next to “loadbalancer” under > openstack_dashboa

Re: [openstack-dev] [heat] Deployment of Lock / Unlock Operation like MUTEX

On Sat, Aug 29, 2015 at 10:33 AM Shinobu Kinjo wrote: > Hello, > > Here is a situation which I faced, that can be reproduced. > > I did "heat resource-signal" multiple times simultaneously to scale > instance. > As a result 3 resources were made in the scaling group having max_size=2. > > "stack-

Re: [openstack-dev] [nova][manila] "latest" microversion considered dangerous

2015-08-29 2:07 GMT+08:00 Matt Riedemann : > > > On 8/28/2015 10:35 AM, Joe Gordon wrote: > >> >> On Aug 28, 2015 6:49 AM, "Sean Dague" > > wrote: >> > >> > On 08/28/2015 09:32 AM, Alex Meade wrote: >> > > I don't know if this is really a big problem. IMO, even with >> >

Re: [openstack-dev] [tricircle] multiple cascade services

Hi Joe, I think you misunderstood what Eran proposed. Eran proposed a "single service/multi-fake-node" scheme not only to enforce state-sync (as what ZK usually is used for), but also the execution *order* It means that even if we implement like what PoC did: multiple-services/one service per bo

[openstack-dev] [kosmos][designate][lbaas] Intial Kosmos source files for review in gerrit

Hi All I have checked in the initial source files to gerrit for review. https://review.openstack.org/#/c/218709/ Please take a look a look at it and provide feedback. Regards Kunal _

Re: [openstack-dev] [neutron][L3][dvr][fwaas] FWaaS

Hi Sean, Have you got the chance to test firewall locally? Any Clue on the issue i am facing? Thanks, bharath On Friday 28 August 2015 07:21 AM, Sean M. Collins wrote: Do you have a known good commit for the FwaaS repo? Or Neutron? Perhaps you can run a git-bisect to find the commit that i

[openstack-dev] [Neutron] Netaddr 0.7.16 and gate breakage

Hi, If you wonder why hell broke loose, [1] will have the answer to your questions. Armando [1] https://bugs.launchpad.net/neutron/+bug/1490380 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: ope

Re: [openstack-dev] [Neutron] Netaddr 0.7.16 and gate breakage

Looks like a legitimate bug in netaddr for mac address validation. The 'valid_mac' function gets setup twice at the top level. https://github.com/drkjam/netaddr/blob/b2b83f5d69f7b38f31330624ec9eb292b1cc880d/netaddr/__init__.py#L42-L46 On Sun, Aug 30, 2015 at 8:54 PM, Armando M. wrote: > Hi, > >

[openstack-dev] Capturing program architecture

Hi everyone! I'm trying to capture how each program is constructed for the purposes of writing a new set of OpenStack deep dive training material and wondering what is considered the best place to gi for this level of information? Such as breaking down neutron or nova... All programs really... Any

Re: [openstack-dev] [Neutron] Netaddr 0.7.16 and gate breakage

Yeah, The latest netaddr seems broken. The behavior is changed like * PREVIOUS: netaddr-0.7.15 >>> import netaddr >>> >>> mac = 'fa:16:3e:4e:a1:0a' >>> netaddr.valid_mac(mac) True >>> * LATEST: netaddr-0.7.16 >>> import netaddr >>> mac = 'fa:16:3e:4e:a1:0a' >>> netaddr.valid_mac(mac) False >>>

[openstack-dev] [nova-scheduler] Scheduler sub-group meeting - Agenda 8/31

Meeting on #openstack-meeting-alt at 1400 UTC (8:00AM MDT) 1) Liberty patches - https://etherpad.openstack.org/p/liberty-nova-priorities-tracking 2) Opens -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 ___

[openstack-dev] [Magnum] possible values for 'server_type', other tahn 'vm'

Hi Team, I have a doubt.What all values 'server type' used in below call can have? *get_template_definition(cls, server_type, os, coe*) Everywhere currently its value is 'vm' only. for example in classes representating template definitions: c *lass AtomicSwarmTemplateDefinition(BaseTemplateDef

Re: [openstack-dev] [neutron][sfc] Neutron stadium distribution and/or packaging

If your sub-project requires changes to the Neutron API or client, then those need to be made in the in the main neutron and client projects. monkey-patching or completely replacing components of the main neutron project is not the way to go. The purpose of big tent isn't to have a bunch of sub-pr

Re: [openstack-dev] [Heat] convergence rally test results (so far)

Hi Angus, Thanks for doing the tests with convergence. We are now assured that convergence has not impacted the performance in a negative way. Given that, in convergence, a stack provisioning process goes through a lot of RPC calls, it puts a lot of load on the message broker and the request loose

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Yes, I added it Sent from my iPhone > On Aug 31, 2015, at 01:19, Brandon Logan wrote: > > Vivek, > Is there a wiki or some document somewhere that explains how to get this > running? Sorry if it's been posted somewhere else and I missed it. > >> On Sun, 2015-08-30 at 18:36 +, Jain, Vivek

Re: [openstack-dev] [Neutron] Netaddr 0.7.16 and gate breakage

Even if this version is fixed for valid_mac, it appears the netaddr authors made the decision to make a backwards incompatible change WRT to the 'broadcast' attribute on IPNetwork objects that have CIDRs of /31 and /32. This means that all future versions of netaddr will be incompatible with the cu

Re: [openstack-dev] [Neutron] [DVR] easyOVS -- Smart tool to use/debug Neutron/DVR

Hi, It's Interesting! I have three points for you here. a.Support packet tracking which show the path of a packet traveled on the host, even on the source/destination host. b.Given a communication type and packet characteristic to find out the fault point. For example, if you want VM1 talk with VM

Re: [openstack-dev] [oslo] About "logging-flexibility"

Hi, Dims, and Oslo team members, > > > We can talk more about it on next > > > Monday's Oslo meeting. Please let us know and i'll add a topic > > > there if you can make it. I have uploaded a patch about logging-flexibility[1]. https://review.openstack.org/#/c/218139/ This is a single patch for