Re: [openstack-dev] KILO: neutron port-update --allowed-address-pairs action=clear throws an exception

2015-09-27 Thread shihanzhang
I don't see any exception using bellow command root@szxbz:/opt/stack/neutron# neutron port-update 3748649e-243d-4408-a5f1-8122f1fbf501 --allowed-address-pairs action=clear Allowed address pairs must be a list. At 2015-09-28 14:36:44, "masoom alam" wrote: stable KILO shall I checkout the

Re: [openstack-dev] KILO: neutron port-update --allowed-address-pairs action=clear throws an exception

2015-09-27 Thread masoom alam
stable KILO shall I checkout the latest code are you saying this...Also can you please confirm if you have tested this thing at your endand there was no problem... Thanks On Sun, Sep 27, 2015 at 11:29 PM, shihanzhang wrote: > which branch do you use? there is not this problem in master b

Re: [openstack-dev] KILO: neutron port-update --allowed-address-pairs action=clear throws an exception

2015-09-27 Thread shihanzhang
which branch do you use? there is not this problem in master branch. At 2015-09-28 13:43:05, "masoom alam" wrote: Can anybody highlight why the following command is throwing an exception: Command# neutron port-update db3113df-14a3-4d6d-a3c5-d0517a134fc3 --allowed-address-pairs action=cle

[openstack-dev] KILO: neutron port-update --allowed-address-pairs action=clear throws an exception

2015-09-27 Thread masoom alam
Can anybody highlight why the following command is throwing an exception: *Command#* neutron port-update db3113df-14a3-4d6d-a3c5-d0517a134fc3 --allowed-address-pairs action=clear *Error: * 2015-09-27 21:44:32.144 ERROR neutron.api.v2.resource [req-b1cbe1f2-ba21-4337-a714-f337c54ee9fc admin None]

Re: [openstack-dev] [lbaas] [octavia] Proposing new meeting time Wednesday 16:00 UTC

2015-09-27 Thread Brandon Logan
Is there a lot of people requesting this meeting change? Thanks, Brandon On Fri, 2015-09-25 at 23:58 +, Eichberger, German wrote: > All, > > In our last meeting [1] we discussed moving the meeting earlier to > accommodate participants from the EMEA region. I am therefore proposing to > move

[openstack-dev] [nova-scheduler] Scheduler sub-group meeting - Agenda 9/21

2015-09-27 Thread Dugger, Donald D
Meeting on #openstack-meeting-alt at 1400 UTC (8:00AM MDT) 1) Mitaka planning 2) Opens -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [cinder] should we use fsync when writing iscsi config file?

2015-09-27 Thread Chris Friesen
On 09/26/2015 02:48 AM, Julien Danjou wrote: On Tue, Sep 22 2015, Chris Friesen wrote: On 09/22/2015 05:48 PM, Joshua Harlow wrote: A present: >>> import contextlib >>> import os >>> >>> @contextlib.contextmanager ... def synced_file(path, mode='wb'): ... with open(path, mode) as fh

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

2015-09-27 Thread WANG, Ming Hao (Tony T)
Russell and Kevin, Thanks for your detail information! I got it. Thanks again, Tony -Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: Monday, September 28, 2015 4:18 AM To: Kevin Benton; OpenStack Development Mailing List (not for usage questions) Cc: WANG, Ming

[openstack-dev] [oslo][doc] Oslo Doc Sprint final Tally (was Re: [oslo][doc] Oslo doc sprint 9/24-9/25)

2015-09-27 Thread Davanum Srinivas
Hello, We had a very good Doc Sprint. Thanks everyone who contributed. Finally tally: Merged 88 commits across 20+ repos and gained one core commiter! :) Huge welcome to Brant Knudson. The full list of reviews are at the bottom of the etherpad [1] Thanks, Dims [1] https://etherpad.openstack.or

Re: [openstack-dev] [puppet] Fwd: Action required: stackforge/puppet-openstack project move

2015-09-27 Thread Jeremy Stanley
On 2015-09-27 18:37:59 -0600 (-0600), Matt Fischer wrote: > On Sep 27, 2015 6:09 PM, "Emilien Macchi" wrote: > > > > should we delete it? > > I'm not sure what value it has anymore but why not just readonly? We aren't deleting any repos, just making them read-only and committing a change to rep

Re: [openstack-dev] [puppet] Fwd: Action required: stackforge/puppet-openstack project move

2015-09-27 Thread Matt Fischer
I'm not sure what value it has anymore but why not just readonly? On Sep 27, 2015 6:09 PM, "Emilien Macchi" wrote: > should we delete it? > > FYI: the module is deprecated in Juno release. > > I vote for yes. > > > Forwarded Message > Subject: Action required: stackforge/puppet-

[openstack-dev] [puppet] Fwd: Action required: stackforge/puppet-openstack project move

2015-09-27 Thread Emilien Macchi
should we delete it? FYI: the module is deprecated in Juno release. I vote for yes. Forwarded Message Subject: Action required: stackforge/puppet-openstack project move Date: Fri, 25 Sep 2015 21:57:10 + From: OpenStack Infrastructure Team To: clayton.one...@twcable.com, c

Re: [openstack-dev] [Openstack-operators] [puppet] feedback request about puppet-keystone

2015-09-27 Thread Matt Fischer
On Fri, Sep 25, 2015 at 11:01 AM, Emilien Macchi wrote: > > > So after 5 days, here is a bit of feedback (13 people did the poll [1]): > > 1/ Providers > Except for 1, most of people are managing a few number of Keystone > users/tenants. > I would like to know if it's because the current implement

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

2015-09-27 Thread Russell Bryant
On 09/27/2015 06:50 AM, Kevin Benton wrote: > Assuming it implements the normal provider networks API, you just > specify the segmentation_id when you create the network. > > neutron net-create NET_NAME --provider:network_type vlan > --provider:physical_network physnet1 --provider:segmentation_id

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

2015-09-27 Thread Russell Bryant
On 09/27/2015 02:26 AM, WANG, Ming Hao (Tony T) wrote: > Russell, > > Thanks for your valuable information. > I understood Geneve is some kind of tunnel format for network virtualization > encapsulation, just like VxLAN. > But I'm still confused by the connection between Geneve and VTEP. > I supp

Re: [openstack-dev] [lbaas] [octavia] Proposing new meeting time Wednesday 16:00 UTC

2015-09-27 Thread Bertrand LALLAU
Hi all, Living in France I prefer the previous meeting time (20:00 UTC) regards, On Sat, Sep 26, 2015 at 3:30 AM, Doug Wiegley wrote: > Works for me. > > Doug > > > > On Sep 25, 2015, at 5:58 PM, Eichberger, German < > german.eichber...@hpe.com> wrote: > > > > All, > > > > In our last meeting [1

Re: [openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

2015-09-27 Thread Armando M.
On 25 September 2015 at 15:40, Chris Hoge wrote: > In November, the OpenStack Foundation will start requiring vendors > requesting > new "OpenStack Compatible" storage driver licenses to start passing the > Cinder > third-party integration tests. The new program was approved by the Board at > th

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

2015-09-27 Thread Doug Hellmann
Excerpts from Mark Voelker's message of 2015-09-25 20:43:23 +: > On Sep 25, 2015, at 1:56 PM, Doug Hellmann wrote: > > > > Excerpts from Mark Voelker's message of 2015-09-25 17:42:24 +: > >> On Sep 25, 2015, at 1:24 PM, Brian Rosmaita > >> wrote: > >>> > >>> I'd like to clarify somethi

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

2015-09-27 Thread Kevin Benton
Assuming it implements the normal provider networks API, you just specify the segmentation_id when you create the network. neutron net-create NET_NAME --provider:network_type vlan --provider:physical_network physnet1 --provider:segmentation_id VLAN_TAG On Sun, Sep 27, 2015 at 9:50 AM, WANG, Ming

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

2015-09-27 Thread WANG, Ming Hao (Tony T)
Russell, Another question is about "localnet". It is a very useful feature. :-) Is it possible to assign which VLAN tag will be used for a specific provider network? In your example in https://github.com/openvswitch/ovs/commit/c02819293d52f7ea7b714242d871b2b01f57f905 : "physnet1" is used as ph