[openstack-dev] [Devstack][OVN] ovs modprobe bug

[Somanchi Trinath]

Hi -

When I try to install devstack+ovn, I get this error with OVS.

make[2]: Leaving directory `/usr/src/linux-headers-3.13.0-32-generic'
depmod `sed -n 's/#define UTS_RELEASE "\([^"]*\)"/\1/p' 
/lib/modules/3.13.0-32-generic/build/include/generated/utsrelease.h`
make[1]: Leaving directory `/opt/stack/ovs/datapath/linux'
modprobe: FATAL: Module openvswitch is in use.
Error on exit
World dumping... see /opt/stack/logs/worlddump-2015-12-16-131531.txt for details


Kindly help me resolve this issue.

Thanks in advance.

-
Trinath Somanchi

__
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][fwaas]some architectural advice on fwaas driver writing

[Somanchi Trinath]

Hi-

As I understand you are not sure on "How to locate the Hardware Appliance" 
which you have as your FW?

Am I right?  If so you can look into, 
https://github.com/jumpojoy/generic_switch kind of approach.

-
Trinath



From: Oguz Yarimtepe [mailto:oguzyarimt...@gmail.com]
Sent: Friday, November 20, 2015 5:52 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [neutron][fwaas]some architectural advice on fwaas 
driver writing

I created a sample driver by looking at vArmour driver that is at the Github 
FWaaS repo. I am planning to call the FW's REST API from the suitable functions.

The problem is, i am still not sure how to locate the hardware appliance. One 
of the FWaaS guy says that Service Chaining can help, any body has an idea or 
how to insert the fw to OpenStack?
On 11/02/2015 02:36 PM, Somanchi Trinath wrote:
Hi-

I'm confused. Do you really have an PoC implementation of what is to be 
achieved?

As I look into these type of Implementations, I would prefer to have proxy 
driver/plugin to get the configuration from Openstack to external 
controller/device and do the rest of the magic.

-
Trinath

__
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] Stepping Down from Neutron Core Responsibilities

[Somanchi Trinath]

Hi-

Congratulations for the support and excellent contributions.

-
Trinath

From: Edgar Magana [mailto:edgar.mag...@workday.com]
Sent: Thursday, November 05, 2015 5:58 AM
To: OpenStack Development Mailing List 
Subject: [openstack-dev] [neutron] Stepping Down from Neutron Core 
Responsibilities

Dear Colleagues,

I have been part of this community from the very beginning when in Santa Clara, 
CA back in 2011 a bunch of we crazy people decided to work on this networking 
project.
Neutron has become is a very unique piece of code and it requires an approval 
team that will always be on the top of everything, this is why I would like to 
communicate you that I decided to step down as Neutron Core.

These are not breaking news for many of you because I shared this thought 
during the summit in Tokyo and now it is a commitment. I want to let you know 
that I learnt a lot from you and I hope my comments and reviews never offended 
you.

I will be around of course. I will continue my work on code reviews and 
coordination on the Networking Guide.

Thank you all for your support and good feedback,

Edgar
__
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][fwaas]some architectural advice on fwaas driver writing

[Somanchi Trinath]

Hi –

Based on this “Assuming that, it will not be routing traffic, just filtering, 
and that we will be using virtual routers of Openstack”

As I understand from the email, you might be comfortable to configure the HW-FW 
using the ReST API. So you can write a proxy driver and connect the HW-FW in 
the setup (which you have tested to make it ready to use). The proxy driver 
written helps to Configure the HW-FW and the HW-FW filters the traffic.

Having said that, I assume that the HW-FW has some intelligence to process the 
requests from proxy driver and update the FW configuration.

*HW-FW – Hardware Firewall.

Hope this helps.

-
Trinath


From: Oğuz Yarımtepe [mailto:oguzyarimt...@gmail.com]
Sent: Monday, November 02, 2015 1:10 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: [openstack-dev] [neutron][fwaas]some architectural advice on fwaas 
driver writing

Hi,
After talking with FWaaS developers at the summit (German and Sridar), i 
decided to write here also, maybe someone has an idea. I am trying to integrate 
a hardware firewall to our Openstack environment. It is a custom hardware 
running BSD on it and has a REST API for configuring. I talked with Sridar, he 
gave me the brief understanding of how FWaaS driver is working.
Either i will be hacking the community driver and calling the REST API or 
writing the driver and calling the REST API there. The problem is, we couldn't 
figured it out how will the hardware firewall be working. Assuming that, it 
will not be routing traffic, just filtering, and that we will be using virtual 
routers of Openstack, do you have a reference architecture for such a case? It 
seems everyone has its own way of using firewall appliances in OpenStack. All i 
need is to create a firewall but instead of using Iptables, i want to use the 
hardware firewall and be able to define filtering rules.
FWaaS guys said that there will be API changes in the future so at Mitaka, it 
seems the way of FWaaS will be changing and there are some plans about merging 
FWaaS and security groups.
I am now using Kilo, the solution also will be working at Liberty also. Will be 
great if you give some guidance.
Regards.

--
Oğuz Yarımtepe
http://about.me/oguzy
__
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][fwaas]some architectural advice on fwaas driver writing

[Somanchi Trinath]

Hi-

I’m confused. Do you really have an PoC implementation of what is to be 
achieved?

As I look into these type of Implementations, I would prefer to have proxy 
driver/plugin to get the configuration from Openstack to external 
controller/device and do the rest of the magic.

-
Trinath

From: Oğuz Yarımtepe [mailto:oguzyarimt...@gmail.com]
Sent: Monday, November 02, 2015 4:36 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [neutron][fwaas]some architectural advice on fwaas 
driver writing

Hi,

On Mon, Nov 2, 2015 at 11:25 AM, Somanchi Trinath 
<trinath.soman...@freescale.com<mailto:trinath.soman...@freescale.com>> wrote:
Hi –

Based on this “Assuming that, it will not be routing traffic, just filtering, 
and that we will be using virtual routers of Openstack”

As I understand from the email, you might be comfortable to configure the HW-FW 
using the ReST API. So you can write a proxy driver and connect the HW-FW in 
the setup (which you have tested to make it ready to use). The proxy driver 
written helps to Configure the HW-FW and the HW-FW filters the traffic.

Having said that, I assume that the HW-FW has some intelligence to process the 
requests from proxy driver and update the FW configuration.


To be sure, calling the REST API at 
https://github.com/openstack/neutron-fwaas/blob/master/neutron_fwaas/services/firewall/drivers/linux/iptables_fwaas.py#L62
 for ex to create a firewall is what you are talking about. Instead of 
iptables, a new driver will be written to handle CRUD operations.
To distinguish the tenant networks, i will be using vlan or vxlan ids while 
entering firewall rules, i think.


*HW-FW – Hardware Firewall.

Hope this helps.

-
Trinath


Did I understand you right, about the proxy driver?

__
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] HenryG addition to the Neutron Drivers team

[Somanchi Trinath]

Congratulations HenryG !

From: Armando M. [mailto:arma...@gmail.com]
Sent: Wednesday, October 21, 2015 8:44 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

Hi folks,

Henry has been instrumental in many areas of the projects and his crazy working 
hours makes even Kevin and I bow in awe.

Jokes aside, I would like to announce HenryG as a new member of the Neutron 
Drivers team.

Having a propension to attendance, and desire to review of RFEs puts you on the 
right foot to join the group, whose members are rotated regularly so that 
everyone is given the opportunity to grow, and no-one burns out.

The team [1] meets regularly on Tuesdays [2], and anyone is welcome to attend.

Please, join me in welcome Henry to the team.

Cheers,
Armando

[1] 
http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#drivers-team
[2] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

__
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-docs][Neutron] Networking Guide - Call for contributors

[Somanchi Trinath]

Hi-

Count me too.

-
Trinath

From: Edgar Magana [mailto:edgar.mag...@workday.com]
Sent: Thursday, October 08, 2015 5:42 AM
To: OpenStack Development Mailing List (not for usage questions) 
; openstack-operat...@lists.openstack.org; 
openstack-d...@lists.openstack.org
Subject: [openstack-dev] [OpenStack-docs][Neutron] Networking Guide - Call for 
contributors

Hello,

I would like to invite everybody to become an active contributor for the 
OpenStack Networking Guide: http://docs.openstack.org/networking-guide/

During the Liberty cycle we made a lot of progress and we feel that the guide 
is ready to have even more contributions and formalize a bit more the team 
around it.
The first thing that I want to propose is to have a regular meeting over IRC to 
discuss the progress and to welcome new contributors. This is the same process 
that other guides like the operators one are following currently.

The networking guide is based on this ToC: 
https://wiki.openstack.org/wiki/NetworkingGuide/TOC
Contribution process is the same that the rest of the OpenStack docs under the 
openstack-manuals git repo: 
https://github.com/openstack/openstack-manuals/tree/master/doc/networking-guide/source

Please, response to this thread and let me know if you could allocate some time 
to help us to make this guide a rock star as the other ones. Based on the 
responses, I will propose a couple of times for the IRC meeting that could 
allocate to everybody if possible, this is why is very important to let me know 
your time zone.

I am really looking forward to increase the contributors in this guide.

Thanks in advance!

Edgar Magana
__
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] PTL Non-Candidacy

[Somanchi Trinath]

Kyle –

I see a Good and a Sad things here,

The Good one being, you lighted the path for new PTL to come up. The Sad thing 
is we are missing your leadership.
Hope you still lead the team in dotted line. ☺

-
Trinath

From: Irena Berezovsky [mailto:irenab@gmail.com]
Sent: Sunday, September 13, 2015 10:58 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [neutron] PTL Non-Candidacy

Kyle,
Thank you for the hard work you did making neuron project and neutron community 
 better!
You have been open and very supportive as a neutron community lead.
Hope you will stay involved.


On Fri, Sep 11, 2015 at 11:12 PM, Kyle Mestery 
> wrote:
I'm writing to let everyone know that I do not plan to run for Neutron PTL for 
a fourth cycle. Being a PTL is a rewarding but difficult job, as Morgan 
recently put it in his non-candidacy email [1]. But it goes further than that 
for me. As Flavio put it in his post about "Being a PTL" [2], it's a full time 
job. In the case of Neutron, it's more than a full time job, it's literally an 
always on job.

I've tried really hard over my three cycles as PTL to build a stronger web of 
trust so the project can grow, and I feel that's been accomplished. We have a 
strong bench of future PTLs and leaders ready to go, I'm excited to watch them 
lead and help them in anyway I can.
As was said by Zane in a recent email [3], while Heat may have pioneered the 
concept of rotating PTL duties with each cycle, I'd like to highly encourage 
Neutron and other projects to do the same. Having a deep bench of leaders 
supporting each other is important for the future of all projects.
See you all in Tokyo!
Kyle

[1] 
http://lists.openstack.org/pipermail/openstack-dev/2015-September/074157.html
[1] 
http://lists.openstack.org/pipermail/openstack-dev/2015-September/073986.html
[2] 
http://lists.openstack.org/pipermail/openstack-dev/2015-September/074242.html

__
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] Proposing Cedric Brandily to Neutron Core Reviewer Team

[Somanchi Trinath]

Congratulations Cedric. ☺

From: Miguel Lavalle [mailto:mig...@mlavalle.com]
Sent: Wednesday, July 22, 2015 10:32 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] Proposing Cedric Brandily to Neutron 
Core Reviewer Team

Congrats Cedric!

On Wed, Jul 22, 2015 at 10:37 AM, Carl Baldwin 
c...@ecbaldwin.netmailto:c...@ecbaldwin.net wrote:
It has been a week since this nomination.  I'm pleased to confirm
Cedric as a core reviewer for these areas of focus.  We look forward
to your continued contribution to the project!

Carl

On Wed, Jul 15, 2015 at 12:47 PM, Carl Baldwin 
c...@ecbaldwin.netmailto:c...@ecbaldwin.net wrote:
 As the Neutron L3 Lieutenant along with Kevin Benton for control
 plane, and Assaf Muller for testing, I would like to propose Cedric
 Brandily as a member of the Neutron core reviewer team under these
 areas of focus.

 Cedric has been a long time contributor to Neutron showing expertise
 particularly in these areas.  His knowledge and involvement will be
 very important to the project.  He is a trusted member of our
 community.  He has been reviewing consistently [1][2] and community
 feedback that I've received indicates that he is a solid reviewer.

 Existing Neutron core reviewers from these areas of focus, please vote
 +1/-1 for the addition of Cedric to the team.

 Thanks!
 Carl Baldwin

 [1] https://review.openstack.org/#/q/reviewer:zzelle%2540gmail.com,n,z
 [2] http://stackalytics.com/report/contribution/neutron-group/90

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://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] - Proposing Miguel Angel Ajo for the Control Plane core team

[Somanchi Trinath]

Congratulations Miguel :-)


-Original Message-
From: Miguel Angel Ajo [mailto:mangel...@redhat.com] 
Sent: Tuesday, July 14, 2015 7:45 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] - Proposing Miguel Angel Ajo for the 
Control Plane core team

Thanks Kevin and everybody for the positive feedback! :)

It's a pleasure to work with so many awesome people.

Best,
Miguel Ángel,



Kevin Benton wrote:
 It's been a week with no negative feedback. Welcome to the team Miguel!
 On Jul 7, 2015 5:22 AM, Ihar Hrachyshkaihrac...@redhat.com  wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Oh yes!

 It was a bit weird that Miguel, while owning a feature branch, did 
 not have a say in what is merged there. Now it should be more in line 
 with his actual position in the project.

 Good work, Miguel!

 On 07/06/2015 01:02 PM, Kevin Benton wrote:
 Hello!

 As the Lieutenant of the built-in control plane[1], I am proposing 
 to add Miguel Angel Ajo to the control plane core reviewer team.

 His review stats are inline with the other core reviewers[2], and 
 his work on improving the stability/performance of the agents over 
 the last year has been important in making the reference 
 implementation reliable.

 Existing cores, please vote +1/-1 for his addition to the team.

 Cheers!

 1.
 http://docs.openstack.org/developer/neutron/policies/core-reviewers.
 ht
 ml
 2. http://stackalytics.com/report/contribution/neutron/30
 http://stackalytics.com/report/contribution/neutron/60
 http://stackalytics.com/report/contribution/neutron/90
 -- Kevin Benton



 
 __
 
 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

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2

 iQEcBAEBCAAGBQJVm7WcAAoJEC5aWaUY1u57RUoH/jIimjwrLqzzq8u0Ix25YGrR
 CQVkLGbE7j+LtzvKOcFSORp/Y/gwsJ6KF3B7NBqfh1C0fHx/uMVp/tf7/NhuthE0
 7+gsMe3yn6oOraYCQHwEDHpxz6r+7dmMfhisknH5k7vsdnwNi5CrnXyr+knxrQ0L
 jjFvdi3F/+2ztV5LtPJLPoU72d81ATwEEFTH/9vUeFPlBu8okUuXRszPJCWR3MeL
 PrKeg5G6OH4b4GVC45Q7238rWB7uiwfFLILo9I8qwgJ/LZnKkK12bmk3tUgE3cqP
 BXxfuMKueJgOvRU0VPpWZwXicf2/pOmdUBv7uX+BeK9hPP5G9i8ITmFblB+doUk=
 =EuZs
 -END PGP SIGNATURE-

 _
 _ 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 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][stable] Kevin Benton added to neutron-stable-maint

[Somanchi Trinath]

Congrats Kevin! :) 

-Original Message-
From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] 
Sent: Tuesday, June 23, 2015 4:07 PM
To: openstack-dev
Subject: [openstack-dev] [neutron][stable] Kevin Benton added to 
neutron-stable-maint

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi all,

Just a heads-up that Kevin Benton is added to neutron-stable-maint team so now 
he has all the powers to +2/+A (and -2) backports.

Kevin is very active at voting for neutron backports (well, where is he NOT 
active?), so here you go.

Thanks
Ihar
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJViTblAAoJEC5aWaUY1u57lAIH/2lBqAQv5sL0avDmWYHljUXO
zolTmsaK8+qs9FXUlr+Ca3TU1KqOH5p27m49pkJS2n3Sy1ojL0TkzmQxA5sB0/Bg
ufVq2aMGzC1L0k9c8VbMiHpX6/CHOEnL/bpp4Gh6LRpovVOCGRXnlPabd+h0PPJm
krDhG428ZB6wMnd5S+ZuV77Mlr2Lrrv8o0mzd0joO1munJFepk7ar7BLwYV+QeZq
kpi8dInh7gODI3ciQ3OWuWZWk4Dsc0Dup2ARsdUlhDN0/Sfc/ElXKWmYIam+flCR
ToxtzQBrw2LT/mT/mOpT8bJRBbP8KGtcunXvDEeoGOxOTF1+2dpfMbHYlohlCX8=
=q6il
-END PGP SIGNATURE-

__
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] Proposing YAMAMOTO Takashi for the Control Plane core team

[Somanchi Trinath]

Congratulations! Yamamoto Takashi

From: Kevin Benton [mailto:blak...@gmail.com]
Sent: Friday, June 19, 2015 3:52 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] Proposing YAMAMOTO Takashi for the 
Control Plane core team

It has been a week and I haven't heard any negative feedback.
Welcome to the control plane core reviewer team YAMAMOTO Takashi!

On Mon, Jun 15, 2015 at 2:52 AM, Oleg Bondarev 
obonda...@mirantis.commailto:obonda...@mirantis.com wrote:
+1


On Mon, Jun 15, 2015 at 12:16 PM, Ihar Hrachyshka 
ihrac...@redhat.commailto:ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Not on the list either, but I want to +1 what Henry said. Yamamoto's
reviews expand to the whole code base and are pretty always *very* usefu
l.

On 06/12/2015 11:39 PM, Henry Gessau wrote:
 Although I am not on your list I would like to add my +1! Yamamoto
 shows great attention to detail in code reviews and frequently
 finds real issues that were not spotted by others.

 On Thu, Jun 11, 2015, Kevin Benton 
 blak...@gmail.commailto:blak...@gmail.com wrote:
 Hello all!

 As the Lieutenant of the built-in control plane[1], I would like
 YAMAMOTO Takashi to be a member of the control plane core
 reviewer team.

 He has been extensively reviewing the entire codebase[2] and his
 feedback on patches related to the reference implementation has
 been very useful. This includes everything ranging from the AMPQ
 API to OVS flows.

 Existing cores that have spent time working on the reference
 implementation (agents and AMQP code), please vote +1/-1 for his
 addition to the team. Aaron, Gary, Assaf, Maru, Kyle, Armando,
 Carl and Oleg; you have all been reviewing things in these areas
 recently so I would like to hear from you specifically.

 1.
 http://docs.openstack.org/developer/neutron/policies/core-reviewers.h
tml#core-review-hierarchy


2. http://stackalytics.com/report/contribution/neutron-group/90


 Cheers -- Kevin Benton


 __



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

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJVfpgHAAoJEC5aWaUY1u57z40IAL8HpGOEQY7aW1aa39C9ig3Y
bNLEabeQ0K5a4+5ynVLIm1sEl4s3GF2r0gCXak9FrkqjHx2r8VeyOx8TqrCj8gX3
+4aHI7n6rJoJtINuTd+bN7T65uaZE86erOcZN+yma5V69ObfIZhIfQKr3BMaBeZT
ah5hkUKl88ckLL5zqc0HnT4wcFH/3Ved2fuhP7hw/IEGMFsqTDS8QUTdXg7/OF5t
fLt0NluKoOuNMOk8dTqpqtQtiyS/E5TH+miVOzyrUeUmZOEayOO3O2b/9QRkX/hL
ijv1j+clT69fhoVAWSaeR7IsXSfqMuKK/hrVtjnyDpBH4KuZnl3QbRpKJ6Yi3bw=
=qnTt
-END PGP SIGNATURE-

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://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:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Kevin Benton
__
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] Proposing Assaf Muller for the Neutron Core Reviewer Team

[Somanchi Trinath]

Congratulations Assaf ☺



From: Jaume Devesa [mailto:devv...@gmail.com]
Sent: Thursday, June 04, 2015 9:25 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] Proposing Assaf Muller for the Neutron 
Core Reviewer Team

Congratulations Assaf!!

On 4 June 2015 at 17:45, Paul Michali 
p...@michali.netmailto:p...@michali.net wrote:
+100 Great addition! Congratulations Assaf!

On Thu, Jun 4, 2015 at 11:41 AM Miguel Lavalle 
mig...@mlavalle.commailto:mig...@mlavalle.com wrote:
Congrats! Well deserved

On Thu, Jun 4, 2015 at 8:50 AM, Assaf Muller 
amul...@redhat.commailto:amul...@redhat.com wrote:
Thank you.

We have a lot of work ahead of us :)


- Original Message -
 It's a been a week since I proposed this, with no objections. Welcome to the
 Neutron core reviewer team as the new QA Lieutenant Assaf!

 On Tue, Jun 2, 2015 at 12:35 PM, Maru Newby  
 ma...@redhat.commailto:ma...@redhat.com  wrote:


 +1 from me, long overdue!


  On May 28, 2015, at 9:42 AM, Kyle Mestery  
  mest...@mestery.commailto:mest...@mestery.com  wrote:
 
  Folks, I'd like to propose Assaf Muller to be a member of the Neutron core
  reviewer team. Assaf has been a long time contributor in Neutron, and he's
  also recently become my testing Lieutenant. His influence and knowledge in
  testing will be critical to the team in Liberty and beyond. In addition to
  that, he's done some fabulous work for Neutron around L3 HA and DVR. Assaf
  has become a trusted member of our community. His review stats place him
  in the pack with the rest of the Neutron core reviewers.
 
  I'd also like to take this time to remind everyone that reviewing code is a
  responsibility, in Neutron the same as other projects. And core reviewers
  are especially beholden to this responsibility. I'd also like to point out
  that +1/-1 reviews are very useful, and I encourage everyone to continue
  reviewing code even if you are not a core reviewer.
 
  Existing Neutron cores, please vote +1/-1 for the addition of Assaf to the
  core reviewer team.
 
  Thanks!
  Kyle
 
  [1] http://stackalytics.com/report/contribution/neutron-group/180
  __
  OpenStack Development Mailing List (not for usage questions)
  Unsubscribe: 
  openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://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:unsubscribehttp://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:unsubscribehttp://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:unsubscribehttp://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:unsubscribehttp://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:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Jaume Devesa
Software Engineer at Midokura
__
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]: DVR Presentation slides from the Vancouver summit

[Somanchi Trinath]

Thanks for the share.. :)

From: Vasudevan, Swaminathan (PNB Roseville) 
[mailto:swaminathan.vasude...@hp.com]
Sent: Tuesday, May 26, 2015 11:20 PM
To: OpenStack Development Mailing List (openstack-dev@lists.openstack.org)
Subject: [openstack-dev] [Neutron]: DVR Presentation slides from the Vancouver 
summit

Hi Folks,
Unfortunately our presentation video is missing from the OpenStack Vancouver 
summit website.
But there was a lot more request for the slides that we presented in the summit.

Here is the link to the slides that we presented in the OpenStack Vancouver 
summit.
https://drive.google.com/file/d/0B4kh-7VVPWlPYXNaQWxXd1NDdm8/view?usp=sharing

Please let me know if you have any questions.

thanks

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


__
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] Stepping down from Neutron core team

[Somanchi Trinath]

My Score -1, Missing the comments.. ☹

From: Miguel Ángel Ajo [mailto:majop...@redhat.com]
Sent: Monday, May 25, 2015 2:57 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] Stepping down from Neutron core team

Ahh, I missed this email while I was in the summit.

Thank you for so many years of hard work Salvatore, as Edgar said, your 
“pedant” comments
made it better.  I will miss your sense of humor ;)

Best,
Miguel Ángel Ajo


On Thursday, 21 de May de 2015 at 21:04, Gary Kotton wrote:
-1

From: Carl Baldwin c...@ecbaldwin.netmailto:c...@ecbaldwin.net
Reply-To: OpenStack List 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Thursday, May 21, 2015 at 11:32 AM
To: OpenStack List 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron] Stepping down from Neutron core team


On May 21, 2015 9:06 AM, Kyle Mestery 
mest...@mestery.commailto:mest...@mestery.com wrote:

 On Thu, May 21, 2015 at 8:58 AM, Salvatore Orlando 
 sorla...@nicira.commailto:sorla...@nicira.com wrote:

 After putting the whole OpenStack networking contributors community through 
 almost 8 cycles of pedant comments and annoying what if questions, it is 
 probably time for me to relieve neutron contributors from this burden.

 It has been a pleasure for me serving the Neutron community (or Quantum as 
 it was called at the time), and now it feel right - and probably overdue - 
 to relinquish my position as a core team member in a spirit of rotation and 
 alternation between contributors.

 Note: Before you uncork your champagne bottles, please be aware that I will 
 stay in the Neutron community as a contributors and I might still end up 
 reviewing patches.

 Thanks for being so understanding with my pedant remarks,
 Salvatore


 If I could -1 this as a patch, I would.

 But seriously. Salvatore, thanks for all the years of work you've put into 
 Neutron. Please note that just because you've stepped down from the core 
 reviewer team doesn't mean we won't be relying on you to be a part of the 
 community.

 Thanks,
 Kyle

Kyle, I think you should -2 this one.  ;)  Maybe we should put the core team 
list in a repo just so you can.

All joking aside, @Salv, I have appreciated your feedback much more than you 
give yourself credit for, maybe more than I let on.  You don't need to be a 
core to give it, so keep it coming.

Carl
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto: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-dev] [Ceilometer] Adding Alarms gives error

[Somanchi Trinath-B39208]

Hi Julien-

With respect to ceilometers implementation and code base, I have a query about 
pecon framework

[*] Is Ceilometer completely integrated with pecon framework.
[*] As I see, Ceilometer implementation is different from Nova, Neutron type of 
implementations. Is this due the new WSGI framework?

Kindly, help me understand the same.

Thanking you.

--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048


-Original Message-
From: Julien Danjou [mailto:jul...@danjou.info] 
Sent: Thursday, September 19, 2013 6:31 PM
To: Somanchi Trinath-B39208
Cc: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Openstack-dev] [Ceilometer] Adding Alarms gives 
error

On Thu, Sep 19 2013, Somanchi Trinath-B39208 wrote:

 I get the following error when I create an alarm.

I think this is bug #1227264 that got fixed a few hours ago, you may want to 
update your copy of Ceilometer.

--
Julien Danjou
-- Free Software hacker - independent consultant
-- http://julien.danjou.info


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

[openstack-dev] [Openstack-dev] [Ceilometer] Adding Alarms gives error

[Somanchi Trinath-B39208]

Hi Stackers!

I was getting to understand ceilometer.

I get the following error when I create an alarm.

From the client I issue the command :

root@openstack:~# ceilometer alarm-create --name alm1 --description test 
--project-id 28296b3cb50f403c80e3c47a025398cc --user-id 
d7f7bb7a07504c29bd6cd2151fb7f2e3 --period 10 --state ok --meter-name m22 
--statistic min

From the Ceilometer API side, I get this error log,

2013-09-19 17:51:12.250 8385 ERROR wsme.api [-] Server-side error: coercing to 
Unicode: need string or buffer, Message found. Detail:
Traceback (most recent call last):

  File /usr/local/lib/python2.7/dist-packages/wsmeext/pecan.py, line 72, in 
callfunction
result = f(self, *args, **kwargs)

  File 
/usr/local/lib/python2.7/dist-packages/ceilometer/api/controllers/v2.py, line 
1144, in post
raise wsme.exc.ClientSideError(error)

  File /usr/local/lib/python2.7/dist-packages/wsme/exc.py, line 9, in __init__
super(ClientSideError, self).__init__(self.faultstring)

  File /usr/local/lib/python2.7/dist-packages/wsme/exc.py, line 18, in 
faultstring
return six.u(self.msg)

  File /usr/lib/python2.7/dist-packages/six.py, line 262, in u
return unicode(s, unicode_escape)

TypeError: coercing to Unicode: need string or buffer, Message found

Is there anything wrong with the input I'm sending to the API.

Kindly help me resolve this issue.

Thanking you..


--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048

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

Re: [openstack-dev] [Neutron] Configuration of Openflow controller reachability information in OVS from Openstack

[Somanchi Trinath-B39208]

Hi Ravi-

We want achieve the same from Quantum Client through Quantum OVS Agent.

Is there any such implementation available for the same with openstack.

I think, the below manual mentions the manual configuration using ovs cli.



Thanking you.

--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048

From: Ravi Chunduru [mailto:ravi...@gmail.com]
Sent: Wednesday, August 07, 2013 8:04 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Neutron] Configuration of Openflow controller 
reachability information in OVS from Openstack

Hi Trinath,

I could get this information from Grizzly installation guide 
https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/Nicira_SingleNode/OpenStack_Grizzly_Install_Guide.rst


· Register this Hypervisor Transport Node (Open vSwitch) with Nicira 
NVP:

·

·

· # Set the open vswitch manager address

· ovs-vsctl set-manager ssl:IP Address of one of your Nicira NVP 
controllers

·

· # Get the client pki cert

· cat /etc/openvswitch/ovsclient-cert.pem

·

· # Copy the contents of the output including the BEGIN and END 
CERTIFICATE lines and be prepared to paste this into NVP manager

· # In NVP Manager add a new Hypervisor, follow the prompts and paste 
the client certificate when prompted

# Please review the NVP User Guide for details on adding Hypervisor transport 
nodes to NVP for more information on this step

Thanks,
-Ravi.

On Wed, Aug 7, 2013 at 2:58 AM, Somanchi Trinath-B39208 
b39...@freescale.commailto:b39...@freescale.com wrote:
Hi Ravi-

With respect to NICIRA NVP Plugin in Quantum, All the processing is done with 
respect to Nicira NVP.

Also, the Controller cluster arguments are provided from ini file.

Can you point me to where the OVS certificates are handled in Nicira code base 
for quantum.


--
Trinath Somanchi - B39208
trinath.soman...@freescale.commailto:trinath.soman...@freescale.com | extn: 
4048

From: Ravi Chunduru [mailto:ravi...@gmail.commailto:ravi...@gmail.com]
Sent: Wednesday, August 07, 2013 11:32 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Neutron] Configuration of Openflow controller 
reachability information in OVS from Openstack


look into nicira neutrón plugin.
I like the idea of ovs controller config driven through neutrón api. Nicira 
approach today  is to add ovs certificates onto ovs controller manually.

On Aug 6, 2013 9:09 PM, Addepalli Srini-B22160 
b22...@freescale.commailto:b22...@freescale.com wrote:

 Hi,

 Using OVS Quantum Plugin and agent,  it is possible to configure OVS with

 Openflow logical switches.
 Tables
 Ports to the logical switches (VLAN, VXLAN, GRE etc..)

 OVS Agent in each compute node uses local ovs-vsctl command to configure 
 above.

 But, there is no simple way for Openstack quantum to configure OVS in compute 
 nodes with  OF controller IP address,  TCP Port,  SSL Certificates etc..
 Also, there is no mechanism today to get hold of DPID of the OVS logical 
 switches by Openstack controller.

 Do  you think that it is good to enhance  Openstack OVS Quantum Plugin and 
 agent to pass above information?

 At very high level, we are thinking to introduce following:


 Configuration of OF Controller reachability information
 Quantum extension API though  which is used to set following:
 Set of Openflow controllers  - For each OF controller
 IP address,   Port
 SSL  Enabled Yes/No.
 If SSL enabled
 CA certificate chain to validate OF controller identification by the OVS.
 Zone/Cell for which this OF controller is applicable for.
 Changes to QuantumClient to configure above.
 OVS Quantum Plugin to store above information in the database.
 OVS Quantum Agent to Plugin communication to get hold of OF controller 
 information.
 OVS Quantum Agent to add the information in OVS using ovs-vsctl.
 Generation of logical switch certificates
   OVS Quantum agent requests the plugin to generate local certificate and 
 private key for each one of the logical switches
 Agent to send DPID
 Plugin to generate certificate  private key pair and sending them as 
 response.
 Plugin configuration file to have CA certificate to use to sign the logical 
 switch certificates.


 Does that make sense?  Is this work going on somewhere else?

 Thanks
 Srini




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


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



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