[Openstack-operators] Ops@Barcelona - Updates

[Tom Fifield]

Hi all,

There have been some schedule updates for the Ops design summit sessions:

https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ops+Summit%3A 



New Sessions added:
* Ops Meetups Team
* Some working groups not previously listed
* Horizon: Operator and Plugin Author Feedback
* Neutron: End user and operator feedback
* Barbican: User and Operator Feedback Session

and some minor room and time changes too - please doublecheck your schedule!


** Call for Moderators **

We really need a moderator for:
>> * HAProy, MySQL, Rabbit Tuning

since it looks like it will be one of the most popular sessions, but we 
don't have a moderator yet.



These sessions will be canceled unless we can find a moderator:
>> * Fleet Management
>> * Swift
>> * Horizon
>> * Alt Deployment tech
>> * ControlPlane Design(multi region)


For those of you who want to know what it takes check out the 
Moderator's Guide: 
https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide & 
ask questions - we're here to help!




Regards,



Tom

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [openstack-dev] [mistral] Who's interested in attending PTG?

[Renat Akhmerov]

Thanks guys for letting us know.

Renat Akhmerov
@Nokia

> On 15 Oct 2016, at 07:35, Dmitri Zimine  wrote:
> 
> StackStorm is game for PGT: Winson will likely be there for Mistral F2F: from 
> what we see now it’s quite a few things where F2F get-together can help  & 
> accelerate. 
> 
> So if Renat you’re in, we have 3 companies.
> 
> 
> 
> Cheers, Dmitri.
> 
> 
> 
> 
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News

[Tom Fifield]

Hi Ops Meetups Team,

Woo! Less than a week to go to Barcelona. Let's have a quick meeting to  
finalise everything.



==Next Meeting==
So, the next meeting is at:

==> Tuesday, 18 of Oct at 1400 UTC[1] in #openstack-operators

[2] will be kept up to date with information about the meeting time and  
agenda



===Barcelona Meeting===
Our in-person meeting in Barcelona is on the schedule:

https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/17413/ops-ops-meetups-team

Tuesday, October 25, 5:55pm-6:35pm
AC Hotel - P3 - Montjuic



All welcome!






Regards,


Tom


[1]  
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Ops+Meetups+Team=20161018T22=241


[2] https://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack] [OpenStack] [Swift] How to create alias for a container?

[Kuo Hugo]

Btw, The Ask OpenStack would be another place for posting OPs questions.

https://ask.openstack.org/questions/

Regards // Hugo

2016-10-17 11:21 GMT+08:00 Kuo Hugo :

> Hi Alexandr,
>
> No, you can't. There's no certain implementation. The only option would be
> two-ways container-sync for ContainerA
>
> Regards // Hugo
>
> 2016-10-15 22:04 GMT+08:00 Alexandr Porunov :
>
>> Hello,
>>
>> Is it possible to create aliases for a container?
>> I have a container "ContainerA" I need to work with (put/remove/copy/get
>> objects) but using the name "ContainerB". Is it possible to create such
>> aliases? If yes then how?
>>
>> Sincerely,
>> Alexandr
>>
>> ___
>> Mailing list: http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>>
>>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [OpenStack] [Swift] How to create alias for a container?

[Kuo Hugo]

Hi Alexandr,

No, you can't. There's no certain implementation. The only option would be
two-ways container-sync for ContainerA

Regards // Hugo

2016-10-15 22:04 GMT+08:00 Alexandr Porunov :

> Hello,
>
> Is it possible to create aliases for a container?
> I have a container "ContainerA" I need to work with (put/remove/copy/get
> objects) but using the name "ContainerB". Is it possible to create such
> aliases? If yes then how?
>
> Sincerely,
> Alexandr
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [ironic][ironic-python-agent]code-review about thiscommit https://review.openstack.org/#/c/369245/

[吕冬兵]

Call them on irc would be better :)
 
 
-- Original --
From:  "zhou.ya";
Date:  Mon, Oct 17, 2016 11:09 AM
To:  "openstack-dev"; 

Subject:  [openstack-dev] [ironic][ironic-python-agent]code-review about 
thiscommit https://review.openstack.org/#/c/369245/

 
Hi ironic team： 
 
I send this email to ask something about 
https://review.openstack.org/#/c/369245/ . 
 
The jenkins has +1 for this commit.I hope you could spare some time to give me 
some advice of this commit. 
 
If it looks good to you，could you please do the workflow？ 
 
Thank you very much. 
 
Looking forward for your response. 
Regards 

zhouya__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [ironic][ironic-python-agent]code-review about this commit https://review.openstack.org/#/c/369245/

[zhou . ya]

Hi ironic team：

I send this email to ask something about 
https://review.openstack.org/#/c/369245/ .

The jenkins has +1 for this commit.I hope you could spare some time to 
give me some advice of this commit.

If it looks good to you，could you please do the workflow？

Thank you very much.

Looking forward for your response.
Regards
zhouya

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-announce] [new][mistral] mistral 3.0.2 release (newton)

[no-reply]

We are jubilant to announce the release of:

mistral 3.0.2: Mistral Project

This release is part of the newton stable release series.

Download the package from:

https://pypi.python.org/pypi/mistral

For more details, please see below.

Changes in mistral 3.0.0..3.0.2
---

6356bce Add a way to save action executions that run synchronously


Diffstat (except docs and test files)
-

mistral/api/controllers/v2/resources.py|  2 +-
mistral/engine/default_engine.py   | 44 --
4 files changed, 71 insertions(+), 15 deletions(-)




___
OpenStack-announce mailing list
OpenStack-announce@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce

[openstack-announce] [new][mistral] mistral-dashboard 3.0.2 release (newton)

[no-reply]

We are grateful to announce the release of:

mistral-dashboard 3.0.2: Mistral dashboard

This release is part of the newton stable release series.

Download the package from:

https://pypi.python.org/pypi/mistral-dashboard

For more details, please see below.

Changes in mistral-dashboard 3.0.0.0rc1..3.0.2
--

2c959e0 Update .gitreview for stable/newton


Diffstat (except docs and test files)
-

.gitreview | 1 +
1 file changed, 1 insertion(+)




___
OpenStack-announce mailing list
OpenStack-announce@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce

[openstack-dev] [new][keystone] keystoneauth1 2.4.2 release (mitaka)

[no-reply]

We are jubilant to announce the release of:

keystoneauth1 2.4.2: Authentication Library for OpenStack Identity

This release is part of the mitaka stable release series.

The source is available from:

http://git.openstack.org/cgit/openstack/keystoneauth

Download the package from:

https://pypi.python.org/pypi/keystoneauth1

Please report issues through launchpad:

http://bugs.launchpad.net/keystoneauth

For more details, please see below.

Changes in keystoneauth1 2.4.1..2.4.2
-

e8a06de be more explicit about connection errors
bf882dd Default serialize_with to json


Diffstat (except docs and test files)
-

keystoneauth1/fixture/keystoneauth_betamax.py |  2 +-
keystoneauth1/session.py  | 10 --
2 files changed, 9 insertions(+), 3 deletions(-)




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [osc] bug/design flaw: Clients not cached per region

[Adrian Turjak]

Hello OpenStack Dev,

I'm doing some work with custom plugins for openstackclient, and mostly
things are going well, but I've run into an annoying little bug/design
flaw around how per region clients are handled.

The openstackclient has a built in way for getting access to the various
openstack clients as such:
nova_client = self.app.client_manager.compute

The problem I'm running into is for some of our custom plugins we
require the commands to run in all regions. We do this by getting the
region list from keystone, and then doing the command in each region.

The expected workflow would be as such:

keystone = self.app.client_manager.identity
regions = [region.id for region in keystone.regions.list()]

for region in regions:
self.app.client_manager.region_name = region
nova_client = self.app.client_manager.compute
do_something(nova_client)


This will work for the first region, with the region_name value being
used to initialise the client the first time, but once a nova client is
created, that client is cached and isn't cached per region. When the
region_name is changed the client cache should be re-intialised or it
should cache per region per service rather than just per service.

Is there a way to explicitly reinitialise the client_manager?
'client_mananger.reinitialise()' or something as easy? Maybe even a
clear cache command?


Here is a very basic example command I've made to show exactly why this
doesn't work:
http://paste.openstack.org/show/585872/

If run in a deployment with more than one region, you will see that the
inbuilt client will list the same instances in all regions while the
explicitly created one will correctly list instances per region.


While explicitly initialising clients isn't exactly difficult, it is
something that would make more sense to simply work in the base
openstackclient code as multi-region commands can and will be useful for
a lot of people.

Not to mention adding multi-region support to some commands so you don't
have to change OS_REGION_NAME or your region in clouds.yaml could be
very useful. A command to list your instances across all regions could
be quite useful and easy to do.


Any thoughts? Suggestions?

Cheers,
Adrian Turjak


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] 答复: Re: 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

[dong . wenjuan]

Thanks a lot~





Julien Danjou  
2016-10-14 17:52

收件人
dong.wenj...@zte.com.cn
抄送
"OpenStack Development Mailing List \(not for usage questions\)" 

主题
Re: [openstack-dev] 答复: Re:  [vitrage][aodh] about aodh notifier to 
create a event alarm






On Fri, Oct 14 2016, dong.wenj...@zte.com.cn wrote:

> Is there any record about the discussion between Aodh and Vitrage?

The notes are in the Etherpad:

  https://etherpad.openstack.org/p/newton-telemetry-vitrage
 
-- 
Julien Danjou
/* Free Software hacker
   https://julien.danjou.info */
[附件 "signature.asc" 被 董文娟00101742/user/zte_ltd 删除]

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

[joehuang]

+1

Best Regards
Chaoyi Huang (joehuang)

From: Miguel Lavalle [mig...@mlavalle.com]
Sent: 15 October 2016 2:30
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Neutron] Neutron team social event in Barcelona

Dear Neutrinos,

I am organizing a social event for the team on Thursday 27th at 19:30. After 
doing some Google research, I am proposing Raco de la Vila, which is located in 
Poblenou: http://www.racodelavila.com/en/index.htm. The menu is here: 
http://www.racodelavila.com/en/carta-racodelavila.htm

It is easy to get there by subway from the Summit venue: 
https://goo.gl/maps/HjaTEcBbDUR2. I made a reservation for 25 people under 
'Neutron' or "Miguel Lavalle". Please confirm your attendance so we can get a 
final count.

Here's some reviews: 
https://www.tripadvisor.com/Restaurant_Review-g187497-d1682057-Reviews-Raco_De_La_Vila-Barcelona_Catalonia.html

Cheers

Miguel
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] CI blocker

[Emilien Macchi]

Hi,

Over the week-end a patch was merged in puppetlabs-ntp, that broke
deployments on Puppet3.
While TripleO is still running Puppet 3 - and will use Puppet 4 very
soon, we need to find a workaround until then.

The bug is reported here:
https://bugs.launchpad.net/tripleo/+bug/1633713

And we're trying to pin puppetlabs-ntp to a stable branch:
https://review.rdoproject.org/r/#/c/3345/

I hope we can fix this bug asap, as it blocks our CI jobs.
-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Infra] Third Party CI Question

[Doug Wiegley]

You can also selectively not use zuul. For those jobs pointed at other source 
control, use standard Jenkins triggers, and all the rest of the tooling remains 
the same (including jjb for those new triggers.)

Doug

> On Oct 16, 2016, at 9:09 AM, Monty Taylor  wrote:
> 
>> On 10/14/2016 01:50 PM, Pradeep Patra wrote:
>> Hi all,
>> 
>> I was referring the CI system in OpenStack [1]. I was reading this
>> approach and its pretty good. One limitation I could find is the CI
>> mechanism is tightly coupled with git/geritt.
>> 
>> [snippet from [1]]
>> Zuul  is a tool
>> that determines what jobs are run when. Zuul listens to the Gerrit event
>> stream, and first tries to match each event to one or more pipelines.
>> 
>> Is there a way to make Zuul listen to Code Collaborator or other Code
>> review tools events and the source control system is SVN not git?
> 
> Hi Pradeep!
> 
> Yes and no.
> 
> Zuul is _heavily_ based around git. We have made a conscious decision to
> have that not be extensible so that we can make the best use of git
> under the hood. It's central to the way zuul prepares speculative future
> states to present to the testing system.
> 
> On the other hand, zuul has a system of extensible Triggers and
> Reporters. Jobs can currently be triggered by both Gerrit and by
> cron-like timers. There is a set of patches proposed to add support for
> listening to github pull requests, although we're deferring landing them
> until we're a little further along with zuul v3. We have a desire for a
> "trigger from url" feature too - where zuul can watch for changes in a
> URL and trigger a job based on it.
> 
> So it should be totally possible to write a Trigger and Reporter module
> to interface with Code Collaborator. I do not believe having such
> modules natively understand SVN will be possible.
> 
> Monty
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

[Aihua Li]

I would like to join.  
 == Aihua Li == 

On Saturday, October 15, 2016 11:02 PM, Cathy Zhang 
 wrote:
 

 #yiv6312206573 #yiv6312206573 -- _filtered #yiv6312206573 
{font-family:SimSun;panose-1:2 1 6 0 3 1 1 1 1 1;} _filtered #yiv6312206573 
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv6312206573 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv6312206573 
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} _filtered #yiv6312206573 
{panose-1:2 1 6 0 3 1 1 1 1 1;}#yiv6312206573 #yiv6312206573 
p.yiv6312206573MsoNormal, #yiv6312206573 li.yiv6312206573MsoNormal, 
#yiv6312206573 div.yiv6312206573MsoNormal 
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv6312206573 a:link, 
#yiv6312206573 span.yiv6312206573MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv6312206573 a:visited, #yiv6312206573 
span.yiv6312206573MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv6312206573 
span.yiv6312206573EmailStyle17 {color:#1F497D;}#yiv6312206573 
.yiv6312206573MsoChpDefault {} _filtered #yiv6312206573 {margin:1.0in 1.0in 
1.0in 1.0in;}#yiv6312206573 div.yiv6312206573WordSection1 {}#yiv6312206573 +1   
 From: Miguel Lavalle [mailto:mig...@mlavalle.com]
Sent: Friday, October 14, 2016 11:31 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Neutron] Neutron team social event in Barcelona    
Dear Neutrinos, I am organizing a social event for the team on Thursday 27th at 
19:30. After doing some Google research, I am proposing Raco de la Vila, which 
is located in Poblenou:http://www.racodelavila.com/en/index.htm. The menu is 
here:http://www.racodelavila.com/en/carta-racodelavila.htm It is easy to get 
there by subway from the Summit venue:https://goo.gl/maps/HjaTEcBbDUR2. I made 
a reservation for 25 people under 'Neutron' or "Miguel Lavalle". Please confirm 
your attendance so we can get a final count. Here's some reviews: 
https://www.tripadvisor.com/Restaurant_Review-g187497-d1682057-Reviews-Raco_De_La_Vila-Barcelona_Catalonia.html
 
Cheers    Miguel 
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


   __
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-operators] [neutron] upgrade from liberty to mitaka

[Ihar Hrachyshka]

Richard Woo  wrote:


Ihar,

Thanks for your reply, seems like the fwaas is install when installed  
neutron server:


root@controller-01:~# dpkg -l | grep neutron
ii  neutron-common
2:8.2.0-0ubuntu1~cloud0   all  Neutron is a virtual  
network service for Openstack - common
ii  neutron-plugin-ml2
2:8.2.0-0ubuntu1~cloud0   all  Neutron is a virtual  
network service for Openstack - ML2 plugin
ii  neutron-server
2:8.2.0-0ubuntu1~cloud0   all  Neutron is a virtual  
network service for Openstack - server
ii  python-neutron
2:8.2.0-0ubuntu1~cloud0   all  Neutron is a virtual  
network service for Openstack - Python library
ii  python-neutron-fwaas  
1:7.1.1-0ubuntu1~cloud0   all  Firewall-as-a-Service  
driver for OpenStack Neutron
ii  python-neutron-lib
0.0.2-2~cloud0all  Neutron shared  
routines and utilities - Python 2.7
ii  python-neutronclient  
1:3.1.0-0ubuntu1~cloud0   all  client API library for  
Neutron

root@controller-01:~# apt-get remove python-neutron-fwaas
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer  
required:

  ipset libipset3 libmnl0 python-neutron python-neutron-lib python-openvswitch
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  neutron-common neutron-plugin-ml2 neutron-server python-neutron-fwaas
0 upgraded, 0 newly installed, 4 to remove and 30 not upgraded.
After this operation, 1,149 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
root@controller-01:~#


I know you solved your issue already, but I just want to comment on the  
packaging behaviour you see.


I don’t believe that your distribution set dependencies right: you should  
be able to install your system without fwaas code at all, it’s meant to be  
a plugin, not a dependency for neutron-server.


Now, it may be the case that due to defaults chosen by debian packages  
default configuration files for the neutron-server service do not work  
unless you also pull in neutron-fwaas. Maybe it’s something historical. But  
ideally, you should be able to run a bare neutron-server with just the code  
from openstack/neutron repo.


Ihar

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [Openstack-operators] [openstack-dev] [neutron] upgrade from liberty to mitaka

[Ihar Hrachyshka]

Richard Woo  wrote:


Ihar,

Thanks for your reply, seems like the fwaas is install when installed  
neutron server:


root@controller-01:~# dpkg -l | grep neutron
ii  neutron-common
2:8.2.0-0ubuntu1~cloud0   all  Neutron is a virtual  
network service for Openstack - common
ii  neutron-plugin-ml2
2:8.2.0-0ubuntu1~cloud0   all  Neutron is a virtual  
network service for Openstack - ML2 plugin
ii  neutron-server
2:8.2.0-0ubuntu1~cloud0   all  Neutron is a virtual  
network service for Openstack - server
ii  python-neutron
2:8.2.0-0ubuntu1~cloud0   all  Neutron is a virtual  
network service for Openstack - Python library
ii  python-neutron-fwaas  
1:7.1.1-0ubuntu1~cloud0   all  Firewall-as-a-Service  
driver for OpenStack Neutron
ii  python-neutron-lib
0.0.2-2~cloud0all  Neutron shared  
routines and utilities - Python 2.7
ii  python-neutronclient  
1:3.1.0-0ubuntu1~cloud0   all  client API library for  
Neutron

root@controller-01:~# apt-get remove python-neutron-fwaas
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer  
required:

  ipset libipset3 libmnl0 python-neutron python-neutron-lib python-openvswitch
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  neutron-common neutron-plugin-ml2 neutron-server python-neutron-fwaas
0 upgraded, 0 newly installed, 4 to remove and 30 not upgraded.
After this operation, 1,149 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
root@controller-01:~#


I know you solved your issue already, but I just want to comment on the  
packaging behaviour you see.


I don’t believe that your distribution set dependencies right: you should  
be able to install your system without fwaas code at all, it’s meant to be  
a plugin, not a dependency for neutron-server.


Now, it may be the case that due to defaults chosen by debian packages  
default configuration files for the neutron-server service do not work  
unless you also pull in neutron-fwaas. Maybe it’s something historical. But  
ideally, you should be able to run a bare neutron-server with just the code  
from openstack/neutron repo.


Ihar

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[openstack-dev] [oslo] Heartbeat timeout

[Ajay Kalambur (akalambu)]

Hi
In our setup we see the following message every second or 2
This cant be normal right?
This means 30 heartbeats were missed since interval is 2 seconds. So in 60 
seconds no heartbeat was sent. Is that how I interpret this message. I don’t 
see any Errors or Tracebacks related to oslo


2016-10-14 10:48:59.354 6 INFO oslo.messaging._drivers.impl_rabbit [-] A
recoverable connection/channel error occurred, trying to reconnect: Too
many heartbeats missed
2016-10-14 10:49:14.354 6 INFO oslo.messaging._drivers.impl_rabbit [-] A
recoverable connection/channel error occurred, trying to reconnect: Too
many heartbeats missed
2016-10-14 10:49:29.355 6 INFO oslo.messaging._drivers.impl_rabbit [-] A
recoverable connection/channel error occurred, trying to reconnect: Too
many heartbeats missed
2016-10-14 10:49:44.356 6 INFO oslo.messaging._drivers.impl_rabbit [-] A
recoverable connection/channel error occurred, trying to reconnect: Too
many heartbeats missed


Has anyone got a working cloud where they see these messages every so often
Typically when do you see these messages?



Ajay

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] upgrade from liberty to mitaka

[Richard Woo]

Ihar,

After looking at version of python-neutron-fwaas package, I found it is
still the old one. I upgraded this package to mitaka version, the problem
went away.

Thanks for your help.

Richard

On Sun, Oct 16, 2016 at 12:00 PM, Richard Woo 
wrote:

> Ihar,
>
> Thanks for your reply, seems like the fwaas is install when installed
> neutron server:
>
> root@controller-01:~# dpkg -l | grep neutron
> ii  neutron-common   2:8.2.0-0ubuntu1~cloud0
> all  Neutron is a virtual network service for Openstack - common
> ii  neutron-plugin-ml2   2:8.2.0-0ubuntu1~cloud0
> all  Neutron is a virtual network service for Openstack - ML2
> plugin
> ii  neutron-server   2:8.2.0-0ubuntu1~cloud0
> all  Neutron is a virtual network service for Openstack - server
> ii  python-neutron   2:8.2.0-0ubuntu1~cloud0
> all  Neutron is a virtual network service for Openstack -
> Python library
> ii  python-neutron-fwaas 1:7.1.1-0ubuntu1~cloud0
> all  Firewall-as-a-Service driver for OpenStack Neutron
> ii  python-neutron-lib   0.0.2-2~cloud0
>  all  Neutron shared routines and utilities - Python 2.7
> ii  python-neutronclient 1:3.1.0-0ubuntu1~cloud0
> all  client API library for Neutron
> root@controller-01:~# apt-get remove python-neutron-fwaas
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer
> required:
>   ipset libipset3 libmnl0 python-neutron python-neutron-lib
> python-openvswitch
> Use 'apt-get autoremove' to remove them.
> The following packages will be REMOVED:
>   neutron-common neutron-plugin-ml2 neutron-server python-neutron-fwaas
> 0 upgraded, 0 newly installed, 4 to remove and 30 not upgraded.
> After this operation, 1,149 kB disk space will be freed.
> Do you want to continue? [Y/n] n
> Abort.
> root@controller-01:~#
>
> I checked service_plugins value in 'neutron.conf', 'router' is enabled but
> not fwaas:
>
> # The core plugin Neutron will use (string value)
> core_plugin = ml2
>
> # The service plugins Neutron will use (list value)
> service_plugins = router
>
>
> Richard
>
>
> On Sun, Oct 16, 2016 at 3:36 AM, Ihar Hrachyshka 
> wrote:
>
>> Richard Woo  wrote:
>>
>> Hello, folks,
>>>
>>> I have a small cluster running openstack liberty, today I am starting to
>>> upgrading to Mitaka.
>>>
>>> I am having a problem to launch l3 agent on network node.
>>>
>>> I got the following error:
>>> Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward
>>> compatibility. SIGUSR1 will no longer be registered in a future release, so
>>> please use SIGUSR2 to generate reports.
>>> Option "verbose" from group "DEFAULT" is deprecated for removal.  Its
>>> value may be silently ignored in the future.
>>> 2016-10-15 22:13:20.800 24466 INFO neutron.common.config [-] Logging
>>> enabled!
>>> 2016-10-15 22:13:20.801 24466 INFO neutron.common.config [-]
>>> /usr/bin/neutron-l3-agent version 8.2.0
>>> 2016-10-15 22:13:20.801 24466 DEBUG neutron.common.config [-] command
>>> line: /usr/bin/neutron-l3-agent --config-file=/etc/neutron/neutron.conf
>>> --config-file=/etc/neutron/l3_agent.ini 
>>> --log-file=/var/log/neutron/l3-agent.log
>>> setup_logging /usr/lib/python2.7/dist-packag
>>> es/neutron/common/config.py:269
>>> 2016-10-15 22:13:20.923 24466 DEBUG oslo_messaging._drivers.amqpdriver
>>> [req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] CALL msg_id:
>>> 0b6eb35b95ec4edca605b2d3c6a76d37 exchange 'neutron' topic 'q-l3-plugin'
>>> _send /usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amq
>>> pdriver.py:454
>>> /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py:187:
>>> RuntimeWarning: You have iterated over the result of
>>> pkg_resources.parse_version. This is a legacy behavior which is
>>> inconsistent with the new version class introduced in setuptools 8.0. In
>>> most cases, conversion to a tuple is unnecessary. For comparison of
>>> versions, sort the Version instances directly. If you have another use case
>>> requiring the tuple, please file a bug with the setuptools project
>>> describing that need.
>>>   stacklevel=1,
>>> 2016-10-15 22:13:20.951 24466 DEBUG oslo_messaging._drivers.amqpdriver
>>> [-] received reply msg_id: 0b6eb35b95ec4edca605b2d3c6a76d37 __call__
>>> /usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amq
>>> pdriver.py:302
>>> 2016-10-15 22:13:20.953 24466 DEBUG neutron.callbacks.manager
>>> [req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] Subscribe:
>>>  router after_create
>>> subscribe /usr/lib/python2.7/dist-packages/neutron/callbacks/manager.p
>>> y:41
>>> 2016-10-15 22:13:20.954 24466 DEBUG neutron.callbacks.manager
>>> [req-8c392909-20ed-45f4-b997-9302008d0075 - - - 

Re: [Openstack-operators] [openstack-dev] [neutron] upgrade from liberty to mitaka

[Richard Woo]

Ihar,

After looking at version of python-neutron-fwaas package, I found it is
still the old one. I upgraded this package to mitaka version, the problem
went away.

Thanks for your help.

Richard

On Sun, Oct 16, 2016 at 12:00 PM, Richard Woo 
wrote:

> Ihar,
>
> Thanks for your reply, seems like the fwaas is install when installed
> neutron server:
>
> root@controller-01:~# dpkg -l | grep neutron
> ii  neutron-common   2:8.2.0-0ubuntu1~cloud0
> all  Neutron is a virtual network service for Openstack - common
> ii  neutron-plugin-ml2   2:8.2.0-0ubuntu1~cloud0
> all  Neutron is a virtual network service for Openstack - ML2
> plugin
> ii  neutron-server   2:8.2.0-0ubuntu1~cloud0
> all  Neutron is a virtual network service for Openstack - server
> ii  python-neutron   2:8.2.0-0ubuntu1~cloud0
> all  Neutron is a virtual network service for Openstack -
> Python library
> ii  python-neutron-fwaas 1:7.1.1-0ubuntu1~cloud0
> all  Firewall-as-a-Service driver for OpenStack Neutron
> ii  python-neutron-lib   0.0.2-2~cloud0
>  all  Neutron shared routines and utilities - Python 2.7
> ii  python-neutronclient 1:3.1.0-0ubuntu1~cloud0
> all  client API library for Neutron
> root@controller-01:~# apt-get remove python-neutron-fwaas
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer
> required:
>   ipset libipset3 libmnl0 python-neutron python-neutron-lib
> python-openvswitch
> Use 'apt-get autoremove' to remove them.
> The following packages will be REMOVED:
>   neutron-common neutron-plugin-ml2 neutron-server python-neutron-fwaas
> 0 upgraded, 0 newly installed, 4 to remove and 30 not upgraded.
> After this operation, 1,149 kB disk space will be freed.
> Do you want to continue? [Y/n] n
> Abort.
> root@controller-01:~#
>
> I checked service_plugins value in 'neutron.conf', 'router' is enabled but
> not fwaas:
>
> # The core plugin Neutron will use (string value)
> core_plugin = ml2
>
> # The service plugins Neutron will use (list value)
> service_plugins = router
>
>
> Richard
>
>
> On Sun, Oct 16, 2016 at 3:36 AM, Ihar Hrachyshka 
> wrote:
>
>> Richard Woo  wrote:
>>
>> Hello, folks,
>>>
>>> I have a small cluster running openstack liberty, today I am starting to
>>> upgrading to Mitaka.
>>>
>>> I am having a problem to launch l3 agent on network node.
>>>
>>> I got the following error:
>>> Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward
>>> compatibility. SIGUSR1 will no longer be registered in a future release, so
>>> please use SIGUSR2 to generate reports.
>>> Option "verbose" from group "DEFAULT" is deprecated for removal.  Its
>>> value may be silently ignored in the future.
>>> 2016-10-15 22:13:20.800 24466 INFO neutron.common.config [-] Logging
>>> enabled!
>>> 2016-10-15 22:13:20.801 24466 INFO neutron.common.config [-]
>>> /usr/bin/neutron-l3-agent version 8.2.0
>>> 2016-10-15 22:13:20.801 24466 DEBUG neutron.common.config [-] command
>>> line: /usr/bin/neutron-l3-agent --config-file=/etc/neutron/neutron.conf
>>> --config-file=/etc/neutron/l3_agent.ini 
>>> --log-file=/var/log/neutron/l3-agent.log
>>> setup_logging /usr/lib/python2.7/dist-packag
>>> es/neutron/common/config.py:269
>>> 2016-10-15 22:13:20.923 24466 DEBUG oslo_messaging._drivers.amqpdriver
>>> [req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] CALL msg_id:
>>> 0b6eb35b95ec4edca605b2d3c6a76d37 exchange 'neutron' topic 'q-l3-plugin'
>>> _send /usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amq
>>> pdriver.py:454
>>> /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py:187:
>>> RuntimeWarning: You have iterated over the result of
>>> pkg_resources.parse_version. This is a legacy behavior which is
>>> inconsistent with the new version class introduced in setuptools 8.0. In
>>> most cases, conversion to a tuple is unnecessary. For comparison of
>>> versions, sort the Version instances directly. If you have another use case
>>> requiring the tuple, please file a bug with the setuptools project
>>> describing that need.
>>>   stacklevel=1,
>>> 2016-10-15 22:13:20.951 24466 DEBUG oslo_messaging._drivers.amqpdriver
>>> [-] received reply msg_id: 0b6eb35b95ec4edca605b2d3c6a76d37 __call__
>>> /usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amq
>>> pdriver.py:302
>>> 2016-10-15 22:13:20.953 24466 DEBUG neutron.callbacks.manager
>>> [req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] Subscribe:
>>>  router after_create
>>> subscribe /usr/lib/python2.7/dist-packages/neutron/callbacks/manager.p
>>> y:41
>>> 2016-10-15 22:13:20.954 24466 DEBUG neutron.callbacks.manager
>>> [req-8c392909-20ed-45f4-b997-9302008d0075 - - - 

Re: [openstack-dev] [neutron] upgrade from liberty to mitaka

[Richard Woo]

Ihar,

Thanks for your reply, seems like the fwaas is install when installed
neutron server:

root@controller-01:~# dpkg -l | grep neutron
ii  neutron-common   2:8.2.0-0ubuntu1~cloud0
all  Neutron is a virtual network service for Openstack - common
ii  neutron-plugin-ml2   2:8.2.0-0ubuntu1~cloud0
all  Neutron is a virtual network service for Openstack - ML2
plugin
ii  neutron-server   2:8.2.0-0ubuntu1~cloud0
all  Neutron is a virtual network service for Openstack - server
ii  python-neutron   2:8.2.0-0ubuntu1~cloud0
all  Neutron is a virtual network service for Openstack -
Python library
ii  python-neutron-fwaas 1:7.1.1-0ubuntu1~cloud0
all  Firewall-as-a-Service driver for OpenStack Neutron
ii  python-neutron-lib   0.0.2-2~cloud0
   all  Neutron shared routines and utilities - Python 2.7
ii  python-neutronclient 1:3.1.0-0ubuntu1~cloud0
all  client API library for Neutron
root@controller-01:~# apt-get remove python-neutron-fwaas
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
  ipset libipset3 libmnl0 python-neutron python-neutron-lib
python-openvswitch
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  neutron-common neutron-plugin-ml2 neutron-server python-neutron-fwaas
0 upgraded, 0 newly installed, 4 to remove and 30 not upgraded.
After this operation, 1,149 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
root@controller-01:~#

I checked service_plugins value in 'neutron.conf', 'router' is enabled but
not fwaas:

# The core plugin Neutron will use (string value)
core_plugin = ml2

# The service plugins Neutron will use (list value)
service_plugins = router


Richard


On Sun, Oct 16, 2016 at 3:36 AM, Ihar Hrachyshka 
wrote:

> Richard Woo  wrote:
>
> Hello, folks,
>>
>> I have a small cluster running openstack liberty, today I am starting to
>> upgrading to Mitaka.
>>
>> I am having a problem to launch l3 agent on network node.
>>
>> I got the following error:
>> Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward
>> compatibility. SIGUSR1 will no longer be registered in a future release, so
>> please use SIGUSR2 to generate reports.
>> Option "verbose" from group "DEFAULT" is deprecated for removal.  Its
>> value may be silently ignored in the future.
>> 2016-10-15 22:13:20.800 24466 INFO neutron.common.config [-] Logging
>> enabled!
>> 2016-10-15 22:13:20.801 24466 INFO neutron.common.config [-]
>> /usr/bin/neutron-l3-agent version 8.2.0
>> 2016-10-15 22:13:20.801 24466 DEBUG neutron.common.config [-] command
>> line: /usr/bin/neutron-l3-agent --config-file=/etc/neutron/neutron.conf
>> --config-file=/etc/neutron/l3_agent.ini 
>> --log-file=/var/log/neutron/l3-agent.log
>> setup_logging /usr/lib/python2.7/dist-packages/neutron/common/config.py:
>> 269
>> 2016-10-15 22:13:20.923 24466 DEBUG oslo_messaging._drivers.amqpdriver
>> [req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] CALL msg_id:
>> 0b6eb35b95ec4edca605b2d3c6a76d37 exchange 'neutron' topic 'q-l3-plugin'
>> _send /usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/
>> amqpdriver.py:454
>> /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py:187:
>> RuntimeWarning: You have iterated over the result of
>> pkg_resources.parse_version. This is a legacy behavior which is
>> inconsistent with the new version class introduced in setuptools 8.0. In
>> most cases, conversion to a tuple is unnecessary. For comparison of
>> versions, sort the Version instances directly. If you have another use case
>> requiring the tuple, please file a bug with the setuptools project
>> describing that need.
>>   stacklevel=1,
>> 2016-10-15 22:13:20.951 24466 DEBUG oslo_messaging._drivers.amqpdriver
>> [-] received reply msg_id: 0b6eb35b95ec4edca605b2d3c6a76d37 __call__
>> /usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/
>> amqpdriver.py:302
>> 2016-10-15 22:13:20.953 24466 DEBUG neutron.callbacks.manager
>> [req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] Subscribe:
>>  router after_create
>> subscribe /usr/lib/python2.7/dist-packages/neutron/callbacks/manager.
>> py:41
>> 2016-10-15 22:13:20.954 24466 DEBUG neutron.callbacks.manager
>> [req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] Subscribe:
>>  router before_delete
>> subscribe /usr/lib/python2.7/dist-packages/neutron/callbacks/manager.
>> py:41
>> 2016-10-15 22:13:20.955 24466 DEBUG neutron_fwaas.services.firewal
>> l.agents.l3reference.firewall_l3_agent 
>> [req-8c392909-20ed-45f4-b997-9302008d0075
>> - - - - -] Initializing firewall agent __init__
>> /usr/lib/python2.7/dist-packages/neutron_fwaas/services/
>> 

Re: [openstack-dev] [Infra] Third Party CI Question

[Monty Taylor]

On 10/14/2016 01:50 PM, Pradeep Patra wrote:
> Hi all,
> 
> I was referring the CI system in OpenStack [1]. I was reading this
> approach and its pretty good. One limitation I could find is the CI
> mechanism is tightly coupled with git/geritt.
> 
> [snippet from [1]]
> Zuul  is a tool
> that determines what jobs are run when. Zuul listens to the Gerrit event
> stream, and first tries to match each event to one or more pipelines.
> 
> Is there a way to make Zuul listen to Code Collaborator or other Code
> review tools events and the source control system is SVN not git?

Hi Pradeep!

Yes and no.

Zuul is _heavily_ based around git. We have made a conscious decision to
have that not be extensible so that we can make the best use of git
under the hood. It's central to the way zuul prepares speculative future
states to present to the testing system.

On the other hand, zuul has a system of extensible Triggers and
Reporters. Jobs can currently be triggered by both Gerrit and by
cron-like timers. There is a set of patches proposed to add support for
listening to github pull requests, although we're deferring landing them
until we're a little further along with zuul v3. We have a desire for a
"trigger from url" feature too - where zuul can watch for changes in a
URL and trigger a job based on it.

So it should be totally possible to write a Trigger and Reporter module
to interface with Code Collaborator. I do not believe having such
modules natively understand SVN will be possible.

Monty

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova]Question about unit tests for shelve/unshleve

[Rikimaru Honjo]

Hi all,

I have a question about unit tests of nova.
(I found this question when I fixed a bug about shelve.[1])

"nova.tests.unit.compute.test_shelve.ShelveComputeAPITestCase" has
test cases for "nova.compute.api.API.shelve()/unshelve()".
But "nova.tests.unit.compute.test_compute_api._ComputeAPIUnitTestMixIn"
also has test cases for same methods.

Is their purpose duplicated?
And, can I organize them if their purpose is duplicated?

FYI, I think that we should consolidate them into
"nova.tests.unit.compute.test_compute_api._ComputeAPIUnitTestMixIn".
Because it is inherited to some test classes.


[1]: https://bugs.launchpad.net/nova/+bug/1588657

Best regards,
--
Rikimaru Honjo
E-mail:honjo.rikim...@po.ntts.co.jp


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [keystone][nova][neutron][all] Rolling upgrades: database triggers and oslo.versionedobjects

[Duncan Thomas]

On 14 October 2016 at 23:55, Jay Pipes  wrote:

> The primary thing that, to me at least, differentiates rolling upgrades of
> distributed software is that different nodes can contain multiple versions
> of the software and continue to communicate with other nodes in the system
> without issue.
>
> In the case of Glance, you cannot have different versions of the Glance
> service running simultaneously within an environment, because those Glance
> services each directly interface with the Glance database and therefore
> expect the Glance DB schema to look a particular way for a specific version
> of the Glance service software.
>

Cinder services can run N+-1 versions in a mixed manner, all talking to the
 same database, no conductor required.



-- 
Duncan Thomas
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] upgrade from liberty to mitaka

[Ihar Hrachyshka]

Richard Woo  wrote:


Hello, folks,

I have a small cluster running openstack liberty, today I am starting to  
upgrading to Mitaka.


I am having a problem to launch l3 agent on network node.

I got the following error:
Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward  
compatibility. SIGUSR1 will no longer be registered in a future release,  
so please use SIGUSR2 to generate reports.
Option "verbose" from group "DEFAULT" is deprecated for removal.  Its  
value may be silently ignored in the future.
2016-10-15 22:13:20.800 24466 INFO neutron.common.config [-] Logging  
enabled!
2016-10-15 22:13:20.801 24466 INFO neutron.common.config [-]  
/usr/bin/neutron-l3-agent version 8.2.0
2016-10-15 22:13:20.801 24466 DEBUG neutron.common.config [-] command  
line: /usr/bin/neutron-l3-agent --config-file=/etc/neutron/neutron.conf  
--config-file=/etc/neutron/l3_agent.ini  
--log-file=/var/log/neutron/l3-agent.log setup_logging  
/usr/lib/python2.7/dist-packages/neutron/common/config.py:269
2016-10-15 22:13:20.923 24466 DEBUG oslo_messaging._drivers.amqpdriver  
[req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] CALL msg_id:  
0b6eb35b95ec4edca605b2d3c6a76d37 exchange 'neutron' topic 'q-l3-plugin'  
_send  
/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:454
/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py:187:  
RuntimeWarning: You have iterated over the result of  
pkg_resources.parse_version. This is a legacy behavior which is  
inconsistent with the new version class introduced in setuptools 8.0. In  
most cases, conversion to a tuple is unnecessary. For comparison of  
versions, sort the Version instances directly. If you have another use  
case requiring the tuple, please file a bug with the setuptools project  
describing that need.

  stacklevel=1,
2016-10-15 22:13:20.951 24466 DEBUG oslo_messaging._drivers.amqpdriver  
[-] received reply msg_id: 0b6eb35b95ec4edca605b2d3c6a76d37 __call__  
/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:302
2016-10-15 22:13:20.953 24466 DEBUG neutron.callbacks.manager  
[req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] Subscribe: after_router_added at 0x7fa2b1a82050> router after_create subscribe  
/usr/lib/python2.7/dist-packages/neutron/callbacks/manager.py:41
2016-10-15 22:13:20.954 24466 DEBUG neutron.callbacks.manager  
[req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] Subscribe: before_router_removed at 0x7fa2b1a86230> router before_delete subscribe  
/usr/lib/python2.7/dist-packages/neutron/callbacks/manager.py:41
2016-10-15 22:13:20.955 24466 DEBUG  
neutron_fwaas.services.firewall.agents.l3reference.firewall_l3_agent  
[req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] Initializing  
firewall agent __init__  
/usr/lib/python2.7/dist-packages/neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent.py:55
2016-10-15 22:13:20.956 24466 CRITICAL neutron  
[req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] AttributeError:  
'module' object has no attribute 'FIREWALL_PLUGIN'
2016-10-15 22:13:20.956 24466 ERROR neutron Traceback (most recent call  
last):
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/bin/neutron-l3-agent", line 10, in 

2016-10-15 22:13:20.956 24466 ERROR neutron sys.exit(main())
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/cmd/eventlet/agents/l3.py",  
line 17, in main

2016-10-15 22:13:20.956 24466 ERROR neutron l3_agent.main()
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/agent/l3_agent.py", line 57, in  
main

2016-10-15 22:13:20.956 24466 ERROR neutron manager=manager)
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/service.py", line 331, in create
2016-10-15 22:13:20.956 24466 ERROR neutron  
periodic_fuzzy_delay=periodic_fuzzy_delay)
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/service.py", line 264, in  
__init__
2016-10-15 22:13:20.956 24466 ERROR neutron self.manager =  
manager_class(host=host, *args, **kwargs)
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 635,  
in __init__
2016-10-15 22:13:20.956 24466 ERROR neutron  
super(L3NATAgentWithStateReport, self).__init__(host=host, conf=conf)
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 243,  
in __init__
2016-10-15 22:13:20.956 24466 ERROR neutron super(L3NATAgent,  
self).__init__(conf=self.conf)
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent.py",  
line 77, in __init__
2016-10-15 22:13:20.956 24466 ERROR neutron self.fwplugin_rpc =  
FWaaSL3PluginApi(topics.FIREWALL_PLUGIN,

Re: [Openstack-operators] [openstack-dev] [neutron] upgrade from liberty to mitaka

[Ihar Hrachyshka]

Richard Woo  wrote:


Hello, folks,

I have a small cluster running openstack liberty, today I am starting to  
upgrading to Mitaka.


I am having a problem to launch l3 agent on network node.

I got the following error:
Guru mediation now registers SIGUSR1 and SIGUSR2 by default for backward  
compatibility. SIGUSR1 will no longer be registered in a future release,  
so please use SIGUSR2 to generate reports.
Option "verbose" from group "DEFAULT" is deprecated for removal.  Its  
value may be silently ignored in the future.
2016-10-15 22:13:20.800 24466 INFO neutron.common.config [-] Logging  
enabled!
2016-10-15 22:13:20.801 24466 INFO neutron.common.config [-]  
/usr/bin/neutron-l3-agent version 8.2.0
2016-10-15 22:13:20.801 24466 DEBUG neutron.common.config [-] command  
line: /usr/bin/neutron-l3-agent --config-file=/etc/neutron/neutron.conf  
--config-file=/etc/neutron/l3_agent.ini  
--log-file=/var/log/neutron/l3-agent.log setup_logging  
/usr/lib/python2.7/dist-packages/neutron/common/config.py:269
2016-10-15 22:13:20.923 24466 DEBUG oslo_messaging._drivers.amqpdriver  
[req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] CALL msg_id:  
0b6eb35b95ec4edca605b2d3c6a76d37 exchange 'neutron' topic 'q-l3-plugin'  
_send  
/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:454
/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py:187:  
RuntimeWarning: You have iterated over the result of  
pkg_resources.parse_version. This is a legacy behavior which is  
inconsistent with the new version class introduced in setuptools 8.0. In  
most cases, conversion to a tuple is unnecessary. For comparison of  
versions, sort the Version instances directly. If you have another use  
case requiring the tuple, please file a bug with the setuptools project  
describing that need.

  stacklevel=1,
2016-10-15 22:13:20.951 24466 DEBUG oslo_messaging._drivers.amqpdriver  
[-] received reply msg_id: 0b6eb35b95ec4edca605b2d3c6a76d37 __call__  
/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:302
2016-10-15 22:13:20.953 24466 DEBUG neutron.callbacks.manager  
[req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] Subscribe: after_router_added at 0x7fa2b1a82050> router after_create subscribe  
/usr/lib/python2.7/dist-packages/neutron/callbacks/manager.py:41
2016-10-15 22:13:20.954 24466 DEBUG neutron.callbacks.manager  
[req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] Subscribe: before_router_removed at 0x7fa2b1a86230> router before_delete subscribe  
/usr/lib/python2.7/dist-packages/neutron/callbacks/manager.py:41
2016-10-15 22:13:20.955 24466 DEBUG  
neutron_fwaas.services.firewall.agents.l3reference.firewall_l3_agent  
[req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] Initializing  
firewall agent __init__  
/usr/lib/python2.7/dist-packages/neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent.py:55
2016-10-15 22:13:20.956 24466 CRITICAL neutron  
[req-8c392909-20ed-45f4-b997-9302008d0075 - - - - -] AttributeError:  
'module' object has no attribute 'FIREWALL_PLUGIN'
2016-10-15 22:13:20.956 24466 ERROR neutron Traceback (most recent call  
last):
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/bin/neutron-l3-agent", line 10, in 

2016-10-15 22:13:20.956 24466 ERROR neutron sys.exit(main())
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/cmd/eventlet/agents/l3.py",  
line 17, in main

2016-10-15 22:13:20.956 24466 ERROR neutron l3_agent.main()
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/agent/l3_agent.py", line 57, in  
main

2016-10-15 22:13:20.956 24466 ERROR neutron manager=manager)
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/service.py", line 331, in create
2016-10-15 22:13:20.956 24466 ERROR neutron  
periodic_fuzzy_delay=periodic_fuzzy_delay)
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/service.py", line 264, in  
__init__
2016-10-15 22:13:20.956 24466 ERROR neutron self.manager =  
manager_class(host=host, *args, **kwargs)
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 635,  
in __init__
2016-10-15 22:13:20.956 24466 ERROR neutron  
super(L3NATAgentWithStateReport, self).__init__(host=host, conf=conf)
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 243,  
in __init__
2016-10-15 22:13:20.956 24466 ERROR neutron super(L3NATAgent,  
self).__init__(conf=self.conf)
2016-10-15 22:13:20.956 24466 ERROR neutron   File  
"/usr/lib/python2.7/dist-packages/neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent.py",  
line 77, in __init__
2016-10-15 22:13:20.956 24466 ERROR neutron self.fwplugin_rpc =  
FWaaSL3PluginApi(topics.FIREWALL_PLUGIN,

Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

[Cathy Zhang]

+1

From: Miguel Lavalle [mailto:mig...@mlavalle.com]
Sent: Friday, October 14, 2016 11:31 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Neutron] Neutron team social event in Barcelona

Dear Neutrinos,
I am organizing a social event for the team on Thursday 27th at 19:30. After 
doing some Google research, I am proposing Raco de la Vila, which is located in 
Poblenou: http://www.racodelavila.com/en/index.htm. The menu is here: 
http://www.racodelavila.com/en/carta-racodelavila.htm
It is easy to get there by subway from the Summit venue: 
https://goo.gl/maps/HjaTEcBbDUR2. I made a reservation for 25 people under 
'Neutron' or "Miguel Lavalle". Please confirm your attendance so we can get a 
final count.
Here's some reviews: 
https://www.tripadvisor.com/Restaurant_Review-g187497-d1682057-Reviews-Raco_De_La_Vila-Barcelona_Catalonia.html

Cheers

Miguel
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev