Re: [openstack-dev] [neutron] Design Summit Session etherpad
Its UTC, check with your local time. From: Vikram Choudhary [mailto:vikram.choudh...@huawei.com] Sent: Wednesday, April 01, 2015 10:42 AM To: mest...@mestery.com Cc: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [neutron] Design Summit Session etherpad Hi Kyle, The link [2] https://etherpad.openstack.org/p/liberty-neutron-summit-topics shows the next meeting is scheduled on (4/7/2015) but it’s Tuesday not Monday. Date on Monday is (4/6/2015) so I got confused:☹ Agenda for Next Neutron Team Meeting Monday (4/7/2015) at 1400 UTC on #openstack-meeting Thanks Vikram From: Kyle Mestery [mailto:mest...@mestery.com] Sent: 01 April 2015 01:02 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] Design Summit Session etherpad Hi folks! Now that we're deep into the feature freeze and the Liberty specs repository is open [1], I wanted to let everyone know I've created an etherpad to track Design Summit Sessions. If you'd like to propose something, please have a look at the etherpad. We'll discuss these next week in the Neutron meeting [3], so please join and come with your ideas! Thanks, Kyle [1] http://lists.openstack.org/pipermail/openstack-dev/2015-March/060183.html [2] https://etherpad.openstack.org/p/liberty-neutron-summit-topics [3] https://wiki.openstack.org/wiki/Network/Meetings __ 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] Gerrit downtime on 2015-03-21
Hi- The Issue is resolved. Its an update to the NEW IP address of Gerrit. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: trinath.soman...@freescale.com [mailto:trinath.soman...@freescale.com] Sent: Monday, March 23, 2015 11:57 AM To: OpenStack Development Mailing List (not for usage questions) Cc: openstack-in...@lists.openstack.org Subject: Re: [OpenStack-Infra] [openstack-dev] Gerrit downtime on 2015-03-21 Hi- I get this error from my CI Zuul debug Log. 2015-03-23 12:16:45,618 ERROR gerrit.GerritWatcher: Exception on ssh event stream: Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/zuul/lib/gerrit.py, line 64, in _run key_filename=self.keyfile) File /usr/local/lib/python2.7/dist-packages/paramiko/client.py, line 236, in connect retry_on_signal(lambda: sock.connect(addr)) File /usr/local/lib/python2.7/dist-packages/paramiko/util.py, line 278, in retry_on_signal return function() File /usr/local/lib/python2.7/dist-packages/paramiko/client.py, line 236, in lambda retry_on_signal(lambda: sock.connect(addr)) File /usr/lib/python2.7/socket.py, line 224, in meth return getattr(self._sock,name)(*args) error: [Errno 111] Connection refused Kindly help me resolve the issue. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: James E. Blair [mailto:cor...@inaugust.com] Sent: Saturday, March 21, 2015 9:46 PM To: OpenStack Development Mailing List (not for usage questions) Cc: openstack-in...@lists.openstack.org Subject: Re: [openstack-dev] Gerrit downtime on 2015-03-21 cor...@inaugust.com (James E. Blair) writes: Hi, Gerrit will be unavailable for a few hours starting at 1500 UTC on Saturday, March 21. Gerrit is up and running on the new server. Actual downtime was about 1 hour from 1500 to 1600. Please let us know either here or on Freenode in #openstack-infra if you notice any problems. -Jim __ 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-Infra mailing list openstack-in...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra __ 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] Gerrit downtime on 2015-03-21
Hi- I get this error from my CI Zuul debug Log. 2015-03-23 12:16:45,618 ERROR gerrit.GerritWatcher: Exception on ssh event stream: Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/zuul/lib/gerrit.py, line 64, in _run key_filename=self.keyfile) File /usr/local/lib/python2.7/dist-packages/paramiko/client.py, line 236, in connect retry_on_signal(lambda: sock.connect(addr)) File /usr/local/lib/python2.7/dist-packages/paramiko/util.py, line 278, in retry_on_signal return function() File /usr/local/lib/python2.7/dist-packages/paramiko/client.py, line 236, in lambda retry_on_signal(lambda: sock.connect(addr)) File /usr/lib/python2.7/socket.py, line 224, in meth return getattr(self._sock,name)(*args) error: [Errno 111] Connection refused Kindly help me resolve the issue. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: James E. Blair [mailto:cor...@inaugust.com] Sent: Saturday, March 21, 2015 9:46 PM To: OpenStack Development Mailing List (not for usage questions) Cc: openstack-in...@lists.openstack.org Subject: Re: [openstack-dev] Gerrit downtime on 2015-03-21 cor...@inaugust.com (James E. Blair) writes: Hi, Gerrit will be unavailable for a few hours starting at 1500 UTC on Saturday, March 21. Gerrit is up and running on the new server. Actual downtime was about 1 hour from 1500 to 1600. Please let us know either here or on Freenode in #openstack-infra if you notice any problems. -Jim __ 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] Ryu/ofagent CI outage
Hi-
Regarding the CI offline mails, I previously received an email from Anita.
Please find the summary below.
Please set your account listing to down on this page:
https://wiki.openstack.org/wiki/ThirdPartySystems
Following these instructions: If your system is going down or having problems,
change the entry to {{ThirdPartySystemTableEntryDown|your
ci system name}} which are found on the
https://wiki.openstack.org/wiki/ThirdPartySystems page.
Leave the details of your system status on this page:
https://wiki.openstack.org/wiki/ThirdPartySystems/Ryu_CI
This is the expected workflow of offline systems communication.
Posting to this mailing list is not part of the communication.
Hope this helps when you further communicate the CI status.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
-Original Message-
From: YAMAMOTO Takashi [mailto:yamam...@valinux.co.jp]
Sent: Wednesday, March 11, 2015 12:33 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Neutron] Ryu/ofagent CI outage
hi,
Ryu/ofagent CI will be offline during the next weekend for a scheduled
maintenance. sorry for inconvenience.
YAMAMOTO Takashi
__
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] PLUMgrid CI maintenance
Hi- This is the not the ML for these notifications. Use 3rd Party announce ML for the same. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Fawad Khaliq [mailto:fa...@plumgrid.com] Sent: Sunday, February 15, 2015 12:07 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Neutron] PLUMgrid CI maintenance Folks, PLUMgrid CI is down because of unforeseen hardware breakdown issues. We are working on getting it sorted out asap. I will respond to this thread when it's back up. Thanks, Fawad Khaliq __ 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] Minimal ML2 mechanism driver after Neutron decomposition change
But then, is this decomposition is for the ML2 MDs or for all vendor specific
plugins/drivers in all the sub divisions around neutron?
Any comments on the same.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
-Original Message-
From: Irena Berezovsky [mailto:ire...@mellanox.com]
Sent: Tuesday, December 16, 2014 12:00 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: henry4...@gmail.com
Subject: Re: [openstack-dev] Minimal ML2 mechanism driver after Neutron
decomposition change
-Original Message-
From: henry hly [mailto:]
Sent: Tuesday, December 16, 2014 3:12 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Minimal ML2 mechanism driver after Neutron
decomposition change
On Tue, Dec 16, 2014 at 1:53 AM, Neil Jerram neil.jer...@metaswitch.com wrote:
Hi all,
Following the approval for Neutron vendor code decomposition
(https://review.openstack.org/#/c/134680/), I just wanted to comment
that it appears to work fine to have an ML2 mechanism driver
_entirely_ out of tree, so long as the vendor repository that provides
the ML2 mechanism driver does something like this to register their
driver as a neutron.ml2.mechanism_drivers entry point:
setuptools.setup(
...,
entry_points = {
...,
'neutron.ml2.mechanism_drivers': [
'calico = xyz.openstack.mech_xyz:XyzMechanismDriver',
],
},
)
(Please see
https://github.com/Metaswitch/calico/commit/488dcd8a51d7c6a1a2f0378900
1c2139b16de85c for the complete change and detail, for the example
that works for me.)
Then Neutron and the vendor package can be separately installed, and
the vendor's driver name configured in ml2_conf.ini, and everything works.
Given that, I wonder:
- is that what the architects of the decomposition are expecting?
- other than for the reference OVS driver, are there any reasons in
principle for keeping _any_ ML2 mechanism driver code in tree?
Good questions. I'm also looking for the linux bridge MD, SRIOV MD...
Who will be responsible for these drivers?
Excellent question. In my opinion, 'technology' specific but not vendor
specific MD (like SRIOV) should not be maintained by specific vendor. It should
be accessible for all interested parties for contribution.
The OVS driver is maintained by Neutron community, vendor specific hardware
driver by vendor, SDN controllers driver by their own community or vendor. But
there are also other drivers like SRIOV, which are general for a lot of vendor
agonitsc backends, and can't be maintained by a certain vendor/community.
So, it would be better to keep some general backend MD in tree besides SRIOV.
There are also vif-type-tap, vif-type-vhostuser,
hierarchy-binding-external-VTEP ... We can implement a very thin in-tree base
MD that only handle vif bind which is backend agonitsc, then backend provider
is free to implement their own service logic, either by an backend agent, or by
a driver derived from the base MD for agentless scenery.
Keeping general backend MDs in tree sounds reasonable.
Regards
Many thanks,
Neil
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for Additional Meeting for third-party
With Kurt Taylor. +1 Very nice idea to start with. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Kurt Taylor [mailto:kurt.r.tay...@gmail.com] Sent: Friday, December 05, 2014 8:39 PM To: OpenStack Development Mailing List (not for usage questions); openstack-in...@lists.openstack.org Subject: Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for Additional Meeting for third-party In my opinion, further discussion is needed. The proposal on the table is to have 2 weekly meetings, one at the existing time of 1800UTC on Monday and, also in the same week, to have another meeting at 0800 UTC on Tuesday. Here are some of the problems that I see with this approach: 1. Meeting content: Having 2 meetings per week is more than is needed at this stage of the working group. There just isn't enough meeting content to justify having two meetings every week. 2. Decisions: Any decision made at one meeting will potentially be undone at the next, or at least not fully explained. It will be difficult to keep consistent direction with the overall work group. 3. Meeting chair(s): Currently we do not have a commitment for a long-term chair of this new second weekly meeting. I will not be able to attend this new meeting at the proposed time. 4. Current meeting time: I am not aware of anyone that likes the current time of 1800 UTC on Monday. The current time is the main reason it is hard for EU and APAC CI Operators to attend. My proposal was to have only 1 meeting per week at alternating times, just as other work groups have done to solve this problem. (See examples at: https://wiki.openstack.org/wiki/Meetings) I volunteered to chair, then ask other CI Operators to chair as the meetings evolved. The meeting times could be any between 1300-0300 UTC. That way, one week we are good for US and Europe, the next week for APAC. Kurt Taylor (krtaylor) On Wed, Dec 3, 2014 at 11:10 PM, trinath.soman...@freescale.commailto:trinath.soman...@freescale.com trinath.soman...@freescale.commailto:trinath.soman...@freescale.com wrote: +1. -- Trinath Somanchi - B39208 trinath.soman...@freescale.commailto:trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Anita Kuno [mailto:ante...@anteaya.infomailto:ante...@anteaya.info] Sent: Thursday, December 04, 2014 3:55 AM To: openstack-in...@lists.openstack.orgmailto:openstack-in...@lists.openstack.org Subject: Re: [OpenStack-Infra] [openstack-dev] [third-party]Time for Additional Meeting for third-party On 12/03/2014 03:15 AM, Omri Marcovitch wrote: Hello Anteaya, A meeting between 8:00 - 16:00 UTC time will be great (Israel). Thanks Omri -Original Message- From: Joshua Hesketh [mailto:joshua.hesk...@rackspace.commailto:joshua.hesk...@rackspace.com] Sent: Wednesday, December 03, 2014 9:04 AM To: He, Yongli; OpenStack Development Mailing List (not for usage questions); openstack-in...@lists.openstack.orgmailto:openstack-in...@lists.openstack.org Subject: Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for Additional Meeting for third-party Hey, 0700 - 1000 UTC would work for me most weeks fwiw. Cheers, Josh Rackspace Australia On 12/3/14 11:17 AM, He, Yongli wrote: anteaya, UTC 7:00 AM to UTC9:00, or UTC11:30 to UTC13:00 is ideal time for china. if there is no time slot there, just pick up any time between UTC 7:00 AM to UCT 13:00. ( UTC9:00 to UTC 11:30 is on road to home and dinner.) Yongi He -Original Message- From: Anita Kuno [mailto:ante...@anteaya.infomailto:ante...@anteaya.info] Sent: Tuesday, December 02, 2014 4:07 AM To: openstack Development Mailing List; openstack-in...@lists.openstack.orgmailto:openstack-in...@lists.openstack.org Subject: [openstack-dev] [third-party]Time for Additional Meeting for third-party One of the actions from the Kilo Third-Party CI summit session was to start up an additional meeting for CI operators to participate from non-North American time zones. Please reply to this email with times/days that would work for you. The current third party meeting is on Mondays at 1800 utc which works well since Infra meetings are on Tuesdays. If we could find a time that works for Europe and APAC that is also on Monday that would be ideal. Josh Hesketh has said he will try to be available for these meetings, he is in Australia. Let's get a sense of what days and timeframes work for those interested and then we can narrow it down and pick a channel. Thanks everyone, Anita. Okay first of all thanks to everyone who replied. Again, to clarify, the purpose of this thread has been to find a suitable additional third-party meeting time geared towards folks in EU and APAC. We live on a sphere, there is no time that will suit everyone. It looks like we are converging on 0800 UTC as a time and I am going to suggest Tuesdays. We have very little competition for space at that date + time
Re: [openstack-dev] [neutron] Changes to the core team
Congratulation Kevin and Henry ☺ -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Kyle Mestery [mailto:mest...@mestery.com] Sent: Monday, December 08, 2014 11:32 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] Changes to the core team On Tue, Dec 2, 2014 at 9:59 AM, Kyle Mestery mest...@mestery.commailto:mest...@mestery.com wrote: Now that we're in the thick of working hard on Kilo deliverables, I'd like to make some changes to the neutron core team. Reviews are the most important part of being a core reviewer, so we need to ensure cores are doing reviews. The stats for the 180 day period [1] indicate some changes are needed for cores who are no longer reviewing. First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from neutron-core. Bob and Nachi have been core members for a while now. They have contributed to Neutron over the years in reviews, code and leading sub-teams. I'd like to thank them for all that they have done over the years. I'd also like to propose that should they start reviewing more going forward the core team looks to fast track them back into neutron-core. But for now, their review stats place them below the rest of the team for 180 days. As part of the changes, I'd also like to propose two new members to neutron-core: Henry Gessau and Kevin Benton. Both Henry and Kevin have been very active in reviews, meetings, and code for a while now. Henry lead the DB team which fixed Neutron DB migrations during Juno. Kevin has been actively working across all of Neutron, he's done some great work on security fixes and stability fixes in particular. Their comments in reviews are insightful and they have helped to onboard new reviewers and taken the time to work with people on their patches. Existing neutron cores, please vote +1/-1 for the addition of Henry and Kevin to the core team. Enough time has passed now, and Kevin and Henry have received enough +1 votes. So I'd like to welcome them to the core team! Thanks, Kyle Thanks! Kyle [1] http://stackalytics.com/report/contribution/neutron-group/180 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for Additional Meeting for third-party
Hi- Its nice to have CI operators meetings. I'm from India, Its okay for me for 05:00AM UTC on Tuesdays. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent: Tuesday, December 02, 2014 1:37 AM To: openstack Development Mailing List; openstack-in...@lists.openstack.org Subject: [OpenStack-Infra] [third-party]Time for Additional Meeting for third-party One of the actions from the Kilo Third-Party CI summit session was to start up an additional meeting for CI operators to participate from non-North American time zones. Please reply to this email with times/days that would work for you. The current third party meeting is on Mondays at 1800 utc which works well since Infra meetings are on Tuesdays. If we could find a time that works for Europe and APAC that is also on Monday that would be ideal. Josh Hesketh has said he will try to be available for these meetings, he is in Australia. Let's get a sense of what days and timeframes work for those interested and then we can narrow it down and pick a channel. Thanks everyone, Anita. ___ OpenStack-Infra mailing list openstack-in...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] Can Neutron VPNaaS work with strongswan? (Openswan removed from Debian)
Hi- Yes, VPNaaS works with Strong Swan too. I have tried and was successful. Take the cherry-pick of 67 patchset from https://review.openstack.org/#/c/33148 Work on the conflicts and run neutron. It works perfect. Hope this helps. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Thomas Goirand [mailto:z...@debian.org] Sent: Sunday, October 12, 2014 9:54 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] Can Neutron VPNaaS work with strongswan? (Openswan removed from Debian) Hi, As you may know, OpenSwan has been largely unmaintained in Debian, and then was removed from Testing, and then Sid last summer. OpenSwan had some unaddressed security issues, and removing it from Debian was IMO the correct thing to do. Ubuntu followed, and Utopic doesn't have OpenSwan anymore either. Though there's StrongSwan, which is apparently an alternative. But can Neutron work with it? If not, how much work would it be to make Neutron use StrongSwan instead of OpenSwan, and could the maintainers of the VPNaaS people do this be worked on for Kilo? BTW, why not using something as popular as OpenVPN, which has more chances to be well maintained? Cheers, Thomas Goirand (zigo) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][Architecture]Suggestions for the third vendors' plugin and driver
Though Code reviews for vendor code takes more time, I feel it must go through Core reviews. Since, Vendors might submit the code that is working fine within their third party CI environment but the Code review make it more efficient with respect to the coding standards followed in the community. Also, for all the vendor plugins/drivers the code reviews (+1s and +2s) give a feedback on the quality they must be in to be with Neutron. But one suggestion I want to put forward, when an -1 or -2 is given to the code, Reviewers might give a brief comment on why this was given, what might be preferred solution and Is there any reference implementation that can be considered for the code in review to move away from these errors. This can help the developers. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Amit Das [mailto:amit@cloudbyte.com] Sent: Thursday, September 18, 2014 11:01 AM To: OpenStack Development Mailing List (not for usage questions) Cc: tanny...@huawei.com Subject: Re: [openstack-dev] [Neutron][Architecture]Suggestions for the third vendors' plugin and driver +1 I don't think it will be seen as punitive. Vendors can write their plugins or drivers when a deal occurs and they do not need to submit code to community and wait for approving. Being a third party vendor, i do not think this is punitive. OpenStack has already established through processes like cert tests via tempest, external CI, etc. However, waiting for months for reviews and some more days for next round of reviews is really disturbing. Vendor plugins can always always provide repository links, cert tests, external CI logs, pep8 logs, flake8 logs, code coverage stats etc. to confirm if they are abiding by the OpenStack processes. Regards, Amit CloudByte Inc.http://www.cloudbyte.com/ On Thu, Sep 18, 2014 at 9:56 AM, Germy Lure germy.l...@gmail.commailto:germy.l...@gmail.com wrote: Hi Salvatore, Thanks for your hyperlink. It's really a monster thread that contains everyone's opinion. But it's useful to me. So, Before we focus on the Neutron core itself, we should firstly release a suite standardized APIs and a framework for vendors' codes. About this job, I think most of it is already OK. We have 20+ monolithic plugins following NB API and plugin framework. We need publish an API doc for internal interface(I prefer to call it SB API, stand on the Neutron core's point to consider, vendors' codes do not belong to core.) and other things unsuitable now. In my opinion, the Neutron core's main responsibility is data model and DB, schedule and dispatch, API and validation, framework and workflow. Some more comments inline. This is a very important discussion - very closely related to the one going on in this other thread http://lists.openstack.org/pipermail/openstack-dev/2014-September/045768.html. Unfortunately it is also a discussion that tends to easily fragment and move in a thousand different directions. A few months ago I was too of the opinion that vendor plugins and drivers were the main reason of unnecessary load for the core team. I still think that they're an unnecessary heavy load, but I reckon the problem does not really lies with open source versus vendor code. It lies in matching people's competencies with subsystems and proper interface across them - as already pointed out in this thread. Yes, it's really important. I have some more comments inline, but unless growing another monster thread I'd rather start a different, cross-project discussion (which will hopefully not become just a cross-project monster thread!) Salvatore On 15 September 2014 08:29, Germy Lure germy.l...@gmail.commailto:germy.l...@gmail.com wrote: Obviously, to a vendor's plugin/driver, the most important thing is API.Yes? NB API for a monolithic plugin or a service plugin and SB API for a service driver or agent, even MD. That's the basic. Now we have released a set of NB APIs with relative stability. The SB APIs' standardization are needed. The internal interface between the API and the plugins is standardized at the moment through use of classes like [1]. A similar interface exists for ML2 drivers [2]. To the monolithic plugins, [1] is useful. Vendors can implement those APIs and keep their codes locally. At the moment the dispatch of an API call to the plugin or from a plugin to a ML2 driver is purely a local call so these interfaces are working fairly well at the moment. I don't know yet however whether they will be sufficient in case plugins are split into different repos. ML2 Driver maintainers have however been warned in the past that the driver interface is to be considered internal and can be changed at any time. This does not apply to the plugin interface which has been conceived in this way to facilitate the development of out of tree plugins. Indeed, it's difficult to split MDs from ML2 plugin framework. I think it need some adaption
Re: [openstack-dev] [neutron] [third-party] collecting recheck command to re-trigger third party CI
This is a Good option to go with. To trigger a specific CI, CI can have their own string or in a community specified format. Like retrigger-freescale .. Also, in the ML or in IRC rooms, I have seen many people asking on how to recheck with an X CI. And many people are not aware of what string to use to trigger a recheck for certain CI. As we have now a separate page for each CI, it would be good to have Trigger String too in those pages. +1 to Akihiro Motoki for this email. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Akihiro Motoki [mailto:amot...@gmail.com] Sent: Wednesday, September 03, 2014 11:34 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [neutron] [third-party] collecting recheck command to re-trigger third party CI Hi Neutron team, There are many third party CI in Neutron and we sometimes/usually want to retrigger third party CI to confirm results. A comment syntax varies across third party CI, so I think it is useful to gather recheck command in one place. I struggled to know how to rerun a specific CI. I added to recheck command column in the list of Neutron plugins and drivers [1]. Could you add recheck command of your CI in the table? If it is not available, please add N/A. Note that supporting recheck is one of the requirements of third party testing. [2] I understand not all CIs support it due to various reasons, but collecting it is useful for developers and reviewers. A syntax of recheck command is under discussion in infra review [3]. I believe the column of recheck command is still useful even after the official syntax is defined because it is not an easy thing to know each CI system name. [1] https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugin_and_Drivers [2] http://ci.openstack.org/third_party.html#requirements [3] https://review.openstack.org/#/c/118623/ Thanks, Akihiro ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party] What tests are required to be run
Hi Edgar, Freescale CI is reporting the results for ML2 Mechanism driver (J-1) and FWaaS Plugin (to be approved for J-3). I'm the owner for this CI. The Wiki page for this CI is https://wiki.openstack.org/wiki/ThirdPartySystems/Freescale_CI. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Edgar Magana [mailto:edgar.mag...@workday.com] Sent: Saturday, August 16, 2014 4:06 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] [third-party] What tests are required to be run Importance: High Team, I did a quick audit on the Neutron CI. Very sad results. Only few plugins and drivers are running properly and testing all Neutron commits. I created a report here: https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugin _and_Drivers We will discuss the actions to take on the next Neutron IRC meeting. So please, reach me out to clarify what is the status of your CI. I had two commits to quickly verify the CI reliability: https://review.openstack.org/#/c/114393/ https://review.openstack.org/#/c/40296/ I would expect all plugins and drivers passing on the first one and failing for the second but I got so many surprises. Neutron code quality and reliability is a top priority, if you ignore this report that plugin/driver will be candidate to be remove from Neutron tree. Cheers, Edgar P.s. I hate to be the inquisitor hereŠ but someone has to do the dirty job! On 8/14/14, 8:30 AM, Kyle Mestery mest...@mestery.com wrote: Folks, I'm not sure if all CI accounts are running sufficient tests. Per the requirements wiki page here [1], everyone needs to be running more than just Tempest API tests, which I still see most neutron third-party CI setups doing. I'd like to ask everyone who operates a third-party CI account for Neutron to please look at the link below and make sure you are running appropriate tests. If you have questions, the weekly third-party meeting [2] is a great place to ask questions. Thanks, Kyle [1] https://wiki.openstack.org/wiki/NeutronThirdPartyTesting [2] https://wiki.openstack.org/wiki/Meetings/ThirdParty ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra] [infra] Third Party CI naming and contact (action required)
Hi Franck - Thanks for the update. I too have that re-order in mind. :) Here after CI owners may add their CI names in appropriate alphabetical order. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Franck Yelles [mailto:franck...@gmail.com] Sent: Thursday, August 14, 2014 3:33 PM To: James E. Blair Cc: OpenStack Development Mailing List (not for usage questions); openstack-in...@lists.openstack.org Subject: Re: [OpenStack-Infra] [infra] Third Party CI naming and contact (action required) Hi James, I have added the Nuage CI system to the list; I also took the liberty to reorder alphabetically the list Franck Franck On Wed, Aug 13, 2014 at 11:23 AM, James E. Blair cor...@inaugust.com wrote: Hi, We've updated the registration requirements for third-party CI systems here: http://ci.openstack.org/third_party.html We now have 86 third-party CI systems registered and have undertaken an effort to make things more user-friendly for the developers who interact with them. There are two important changes to be aware of: 1) We now generally name third-party systems in a descriptive manner including the company and product they are testing. We have renamed currently-operating CI systems to match these standards to the best of our abilities. Some of them ended up with particularly bad names (like Unknown Function...). If your system is one of these, please join us in #openstack-infra on Freenode to establish a more descriptive name. 2) We have established a standard wiki page template to supply a description of the system, what is tested, and contact information for each system. See https://wiki.openstack.org/wiki/ThirdPartySystems for an index of such pages and instructions for creating them. Each third-party CI system will have its own page in the wiki and it must include a link to that page in every comment that it leaves in Gerrit. If you operate a third-party CI system, please ensure that you register a wiki page and update your system to link to it in every new Gerrit comment by the end of August. Beginning in September, we will disable systems that have not been updated. Thanks, Jim ___ OpenStack-Infra mailing list openstack-in...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list openstack-in...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party] What tests are required to be run
Hi- I'm hitting bugs for (basic/advanced)_server_ops testing. https://bugs.launchpad.net/nova/+bug/1232303 Kindly help me with a fix to this. Thanking you. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Kyle Mestery [mailto:mest...@mestery.com] Sent: Thursday, August 14, 2014 9:00 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] [third-party] What tests are required to be run Folks, I'm not sure if all CI accounts are running sufficient tests. Per the requirements wiki page here [1], everyone needs to be running more than just Tempest API tests, which I still see most neutron third-party CI setups doing. I'd like to ask everyone who operates a third-party CI account for Neutron to please look at the link below and make sure you are running appropriate tests. If you have questions, the weekly third-party meeting [2] is a great place to ask questions. Thanks, Kyle [1] https://wiki.openstack.org/wiki/NeutronThirdPartyTesting [2] https://wiki.openstack.org/wiki/Meetings/ThirdParty ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] Rotating the weekly Neutron meeting
+1 and Like -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Gary Kotton [mailto:gkot...@vmware.com] Sent: Wednesday, August 13, 2014 8:07 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] Rotating the weekly Neutron meeting Huge +1 On 8/13/14, 5:19 PM, Paul Michali (pcm) p...@cisco.com wrote: +1 PCM (Paul Michali) MAIL Š..Š. p...@cisco.com IRC ŠŠ..Š pcm_ (irc.freenode.com) TW ŠŠŠ... @pmichali GPG Key Š 4525ECC253E31A83 Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83 On Aug 13, 2014, at 10:05 AM, Kyle Mestery mest...@mestery.com wrote: Per this week's Neutron meeting [1], it was decided that offering a rotating meeting slot for the weekly Neutron meeting would be a good thing. This will allow for a much easier time for people in Asia/Pacific timezones, as well as for people in Europe. So, I'd like to propose we rotate the weekly as follows: Monday 2100UTC Tuesday 1400UTC If people are ok with these time slots, I'll set this up and we'll likely start with this new schedule in September, after the FPF. Thanks! Kyle [1] http://eavesdrop.openstack.org/meetings/networking/2014/networking.201 4-0 8-11-21.00.html ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra] [infra] Third Party CI naming and contact (action required)
Hi- I have updated the page for 'Freescale CI'. Need a change in the CI display name, Can you change 'Freescale CI' to 'Freescale Neutron CI'. Here is the page I added, https://wiki.openstack.org/wiki/ThirdPartySystems/Freescale_CI and the Index page https://wiki.openstack.org/wiki/ThirdPartySystems -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: James E. Blair [mailto:cor...@inaugust.com] Sent: Wednesday, August 13, 2014 11:54 PM To: openstack-in...@lists.openstack.org Cc: openstack-dev@lists.openstack.org Subject: [OpenStack-Infra] [infra] Third Party CI naming and contact (action required) Hi, We've updated the registration requirements for third-party CI systems here: http://ci.openstack.org/third_party.html We now have 86 third-party CI systems registered and have undertaken an effort to make things more user-friendly for the developers who interact with them. There are two important changes to be aware of: 1) We now generally name third-party systems in a descriptive manner including the company and product they are testing. We have renamed currently-operating CI systems to match these standards to the best of our abilities. Some of them ended up with particularly bad names (like Unknown Function...). If your system is one of these, please join us in #openstack-infra on Freenode to establish a more descriptive name. 2) We have established a standard wiki page template to supply a description of the system, what is tested, and contact information for each system. See https://wiki.openstack.org/wiki/ThirdPartySystems for an index of such pages and instructions for creating them. Each third-party CI system will have its own page in the wiki and it must include a link to that page in every comment that it leaves in Gerrit. If you operate a third-party CI system, please ensure that you register a wiki page and update your system to link to it in every new Gerrit comment by the end of August. Beginning in September, we will disable systems that have not been updated. Thanks, Jim ___ OpenStack-Infra mailing list openstack-in...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party] Freescale CI log site is being blocked
Hi-
Today I contacted the service provider regarding the malware in the website.
Got a response that website is truly functional and malware free.
I too have verified all the directories, subdirectories and log files manually
for any malware injected into the website. I have detected none.
There is no anonymous login enabled for FTP or cPanel login to the server. The
FTP is protected with Strong Passcode.
This is an update from my end.
Like all other CI's now normal browsing of logs is available for view.
The CI is made down to take the above explained changes to take place. Now the
CI is active running the jobs.
All the old logs are present as in place.
You may browse the old logs using the url
For ML2 Mechanism driver :
http://fslopenstackci.com/{change_number}/{change_patchset}/Freescale-ML2-Mechanism-Driver
For FWaaS Plugin :
http://fslopenstackci.com/{change_number}/{change_patchset}/Freescale-FWaaS-Plugin
Now I have updated the CI to create a BUILD directory as well to showcase logs
for rechecks.
With this new change the log URL will be
For ML2 Mechanism driver :
http://fslopenstackci.com/{build_number}/{change_number}/{change_patchset}/Freescale-ML2-Mechanism-Driver
For FWaaS Plugin :
http://fslopenstackci.com/{build_number}/{change_number}/{change_patchset}/Freescale-FWaaS-Plugin
Hi Mestery-
Kindly please verify the access to the site.
Also, if it's still in blocking mode, kindly mail me the logs with Cisco WSA to
verify the reason behind this blocking.
Kindly help me with your review on my code at
https://review.openstack.org/#/c/109659/
Thanking you all.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | Mob: +91 9866 235 130
-Original Message-
From: Anita Kuno [mailto:ante...@anteaya.info]
Sent: Saturday, August 09, 2014 11:09 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [neutron] [third-party] Freescale CI log site is
being blocked
On 08/08/2014 11:27 PM, trinath.soman...@freescale.com wrote:
Thanks anita for the reply.
Previously the existing server is accessible by kyle. But now its not being
accessible.
For the paid hosting I have its administered by godaddy
If you are paying godaddy to administer the server, have you asked them why one
of your users has acknowledged your site is blacklisted by Cisco WSA appliances?
If you are paying them to administer your server, answering your question falls
within their job.
You need to find out the reason behind Cisco security blocking, that is what I
am asking you to do. It if fine if you don't know, but it is your
responsibility to find out.
Thanks Trinath,
Anita.
and the FTP is only accessed by Jenkins.
I can try relocating FTP web based file browser script and provide a normal
view of files.
Don't know the reason behind Cisco Security blocking the access where it has
given access to view the website before.
Thanks a lot again for the brief email.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
-Original Message-
From: Anita Kuno [mailto:ante...@anteaya.info]
Sent: Saturday, August 09, 2014 10:21 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [neutron] [third-party] Freescale CI log
site is being blocked
On 08/08/2014 10:06 PM, trinath.soman...@freescale.com wrote:
Hi Sumit-
When I try to paste a large log text into paste.openstack, It is giving me
image verification and says its spam.
Let's not confuse paste.openstack.org's spam blocker from spam blockers on
servers. They are two separate functionalities and the conversation does not
move forward if we try to pretend they are the same thing or even remotely
related, which they are not.
If you recall, Trinath, the first server you had got hacked since you had not
hardened it appropriately. Having hosting via go daddy or any other paid
hosting service does not absolve you of the responsibility of having a well
maintained server. If you need help maintaining your server, I suggest you
contract a server administrator to advise you or do the work. We have to
assume a certain level of competence here, due to the responsibility involved
I don't think you are going to get many responses to questions if you don't
know how to maintain your server.
This isn't really the the place to ask. Running your third party ci system
and copying the logs, sure this is the place, basic server maintenance is
your responsibility.
If you recall, a basic evaluation of your server logs told you you had been
hacked the last time. This might be a place to start now.
In any case, please maintain your server and please address Kyle's concerns.
Thank you Trianth,
Anita.
I don't know why its taken as spam/malware. It's a paid hosting I had from
GODADDY.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
-Original Message-
From: Sumit Naiksatam
Re: [openstack-dev] [neutron] [third-party] Freescale CI log site is being blocked
Hi Kyle- I’m using a paid hosting from GODADDY. The website is http://fslopenstackci.com. I registered this domain too. This time it’s not a free hosting that I used long back. I’m posting to this domain from past 3 months. Does anyone have the same issue with my logs website? -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Kevin Benton [mailto:blak...@gmail.com] Sent: Friday, August 08, 2014 11:29 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Somanchi Trinath-B39208 Subject: Re: [openstack-dev] [neutron] [third-party] Freescale CI log site is being blocked Does your log server allow anonymous uploads that caused it to host malware or something that led to it being blocked? On Fri, Aug 8, 2014 at 7:12 AM, Kyle Mestery mest...@mestery.commailto:mest...@mestery.com wrote: Trinath: In looking at your FWaaS review [1], I noticed the site you are using for log storage is being blacklisted again, at least by Cisco WSA appliances. Thus, I cannot see the logs for it. Did you change the location of your log storage again? Is anyone else seeing this issue? Thanks, Kyle [1] https://review.openstack.org/#/c/109659/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party] Freescale CI log site is being blocked
Hi Sumit- When I try to paste a large log text into paste.openstack, It is giving me image verification and says its spam. I don't know why its taken as spam/malware. It's a paid hosting I had from GODADDY. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Sumit Naiksatam [mailto:sumitnaiksa...@gmail.com] Sent: Saturday, August 09, 2014 1:12 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] [third-party] Freescale CI log site is being blocked Actually I am able to access the logs in this CI over the internet and through my service provider. I have copy-pasted the log from the latest freescale run here (to validate if this is indeed the latest run): http://paste.openstack.org/show/92229/ But good point Kevin, when I was trying to post this on paste, it did complain about the log text appearing like spam. On Fri, Aug 8, 2014 at 10:58 AM, Kevin Benton blak...@gmail.com wrote: Does your log server allow anonymous uploads that caused it to host malware or something that led to it being blocked? On Fri, Aug 8, 2014 at 7:12 AM, Kyle Mestery mest...@mestery.com wrote: Trinath: In looking at your FWaaS review [1], I noticed the site you are using for log storage is being blacklisted again, at least by Cisco WSA appliances. Thus, I cannot see the logs for it. Did you change the location of your log storage again? Is anyone else seeing this issue? Thanks, Kyle [1] https://review.openstack.org/#/c/109659/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [third-party] Freescale CI log site is being blocked
Thanks anita for the reply. Previously the existing server is accessible by kyle. But now its not being accessible. For the paid hosting I have its administered by godaddy and the FTP is only accessed by Jenkins. I can try relocating FTP web based file browser script and provide a normal view of files. Don't know the reason behind Cisco Security blocking the access where it has given access to view the website before. Thanks a lot again for the brief email. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent: Saturday, August 09, 2014 10:21 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [neutron] [third-party] Freescale CI log site is being blocked On 08/08/2014 10:06 PM, trinath.soman...@freescale.com wrote: Hi Sumit- When I try to paste a large log text into paste.openstack, It is giving me image verification and says its spam. Let's not confuse paste.openstack.org's spam blocker from spam blockers on servers. They are two separate functionalities and the conversation does not move forward if we try to pretend they are the same thing or even remotely related, which they are not. If you recall, Trinath, the first server you had got hacked since you had not hardened it appropriately. Having hosting via go daddy or any other paid hosting service does not absolve you of the responsibility of having a well maintained server. If you need help maintaining your server, I suggest you contract a server administrator to advise you or do the work. We have to assume a certain level of competence here, due to the responsibility involved I don't think you are going to get many responses to questions if you don't know how to maintain your server. This isn't really the the place to ask. Running your third party ci system and copying the logs, sure this is the place, basic server maintenance is your responsibility. If you recall, a basic evaluation of your server logs told you you had been hacked the last time. This might be a place to start now. In any case, please maintain your server and please address Kyle's concerns. Thank you Trianth, Anita. I don't know why its taken as spam/malware. It's a paid hosting I had from GODADDY. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Sumit Naiksatam [mailto:sumitnaiksa...@gmail.com] Sent: Saturday, August 09, 2014 1:12 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] [third-party] Freescale CI log site is being blocked Actually I am able to access the logs in this CI over the internet and through my service provider. I have copy-pasted the log from the latest freescale run here (to validate if this is indeed the latest run): http://paste.openstack.org/show/92229/ But good point Kevin, when I was trying to post this on paste, it did complain about the log text appearing like spam. On Fri, Aug 8, 2014 at 10:58 AM, Kevin Benton blak...@gmail.com wrote: Does your log server allow anonymous uploads that caused it to host malware or something that led to it being blocked? On Fri, Aug 8, 2014 at 7:12 AM, Kyle Mestery mest...@mestery.com wrote: Trinath: In looking at your FWaaS review [1], I noticed the site you are using for log storage is being blacklisted again, at least by Cisco WSA appliances. Thus, I cannot see the logs for it. Did you change the location of your log storage again? Is anyone else seeing this issue? Thanks, Kyle [1] https://review.openstack.org/#/c/109659/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron][third-party] A question about building third-party CI?
Hi- In your CI, before running devstack, configure neutron code base with your code (yet to be approved) and run stack.sh. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Yangxurong [mailto:yangxur...@huawei.com] Sent: Tuesday, August 05, 2014 4:06 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [neutron][third-party] A question about building third-party CI? Hi folks, Recently I am working on building CI for our ml2 driver. Since our code has not been merged, when running the devstack-vm-gate script, the code in neutron project will be updated so our code is missing. Without the code, devstack will fail since it is configured to use our own ml2 driver. Any suggestions to solve this problem? Thanks, XuRong Yang ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron][third-party] Protocol for bringing up CI for a new driver?
Hope this links helps you http://www.joinfu.com/2014/01/understanding-the-openstack-ci-system/ http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/ http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/ -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Luke Gorrie [mailto:l...@tail-f.com] Sent: Tuesday, August 05, 2014 5:02 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][third-party] Protocol for bringing up CI for a new driver? Hi Salvatore, On 5 August 2014 10:34, Salvatore Orlando sorla...@nicira.commailto:sorla...@nicira.com wrote: Once in place, the CI system should be able to pick up the patches from the new plugin or driver on gerrit. In my opinion, successful CI runs against those patches should constitute a sufficient proof of the validity of the CI system. That sounds good to me. Is there already an easy way to pick up the patches with devstack? (would one create a local repo, do some git-fu to merge the driver, then point devstack's NEUTRON_REPO there?) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron] tox -e pep8 fails at requirements.txt
Hi -
When I run tox to check pep8 on the newly cloned neutron from openstack git , I
get the following error.
pep8 create: /root/fw_code_base/neutron_01082014/.tox/pep8
pep8 installdeps: -r/root/fw_code_base/neutron_01082014/requirements.txt,
-r/root/fw_code_base/neutron_01082014/test-requirements.txt
ERROR: invocation failed, logfile:
/root/fw_code_base/neutron_01082014/.tox/pep8/log/pep8-1.log
ERROR: actionid=pep8
msg=getenv
cmdargs=[local('/root/fw_code_base/neutron_01082014/.tox/pep8/bin/pip'),
'install', '-U', '-r/root/fw_code_base/neutron_01082014/requirements.txt',
'-r/root/fw_code_base/neutron_01082014/test-requirements.txt']
env={'PYTHONIOENCODING': 'utf_8', 'XDG_RUNTIME_DIR': '/run/user/0',
'VIRTUAL_ENV': '/root/fw_code_base/neutron_01082014/.tox/pep8', 'LESSOPEN': '|
/usr/bin/lesspipe %s', 'SSH_CLIENT': '10.232.84.77 61736 22', 'LOGNAME':
'root', 'USER': 'root', 'HOME':
'/root/fw_code_base/neutron_01082014/.tox/pep8/tmp/pseudo-home', 'PATH':
'/root/fw_code_base/neutron_01082014/.tox/pep8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games',
'XDG_SESSION_ID': '19', '_': '/usr/bin/tox', 'SSH_CONNECTION': '10.232.84.77
61736 10.232.90.26 22', 'LANG': 'en_IN', 'TERM': 'xterm', 'SHELL': '/bin/bash',
'LESSCLOSE': '/usr/bin/lesspipe %s %s', 'LANGUAGE': 'en_IN:en', 'SHLVL': '1',
'SSH_TTY': '/dev/pts/0', 'OLDPWD': '/root/fw_code_base', 'PWD':
'/root/fw_code_base/neutron_01082014', 'PYTHONHASHSEED': '0', 'MAIL':
'/var/mail/root', 'LS_COLORS':
'rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:'}
Downloading/unpacking pbr=0.6,!=0.7,1.0 (from -r
/root/fw_code_base/neutron_01082014/requirements.txt (line 1))
Cannot fetch index base URL https://pypi.python.org/simple/
Could not find any downloads that satisfy the requirement pbr=0.6,!=0.7,1.0
(from -r /root/fw_code_base/neutron_01082014/requirements.txt (line 1))
Cleaning up...
No distributions at all found for pbr=0.6,!=0.7,1.0 (from -r
/root/fw_code_base/neutron_01082014/requirements.txt (line 1))
Storing debug log for failure in
/root/fw_code_base/neutron_01082014/.tox/pep8/tmp/pseudo-home/.pip/pip.log
ERROR: could not install deps
[-r/root/fw_code_base/neutron_01082014/requirements.txt,
-r/root/fw_code_base/neutron_01082014/test-requirements.txt]
__ summary
__
ERROR: pep8: could not install deps
[-r/root/fw_code_base/neutron_01082014/requirements.txt,
-r/root/fw_code_base/neutron_01082014/test-requirements.txt]
Can anyone help me on resolving this issue.
Kindly please help me in this regard.
Thanks in advance.
--
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][CI] DB migration error
Hi Kevin- The fix given in the bug report is not working for my CI. I think I need to wait for the real fix in the main stream. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Kevin Benton [mailto:blak...@gmail.com] Sent: Wednesday, July 16, 2014 10:01 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][CI] DB migration error This bug is also affecting Ryu and the Big Switch CI. There is a patch to bump the version requirement for alembic linked in the bug report that should fix it. It we can't get that merged we may have to revert the healing patch. https://bugs.launchpad.net/bugs/1342507 On Jul 16, 2014 9:27 AM, trinath.soman...@freescale.commailto:trinath.soman...@freescale.com trinath.soman...@freescale.commailto:trinath.soman...@freescale.com wrote: Hi- With the neutron Update to my CI, I get the following error while configuring Neutron in devstack. 2014-07-16 16:12:06.349 | INFO [alembic.autogenerate.compare] Detected server default on column 'poolmonitorassociations.status' 2014-07-16 16:12:06.411 | INFO [neutron.db.migration.alembic_migrations.heal_script] Detected added foreign key for column 'id' on table u'ml2_brocadeports' 2014-07-16 16:12:14.853 | Traceback (most recent call last): 2014-07-16 16:12:14.853 | File /usr/local/bin/neutron-db-manage, line 10, in module 2014-07-16 16:12:14.853 | sys.exit(main()) 2014-07-16 16:12:14.854 | File /opt/stack/new/neutron/neutron/db/migration/cli.py, line 171, in main 2014-07-16 16:12:14.854 | CONF.command.func(config, CONF.command.namehttp://CONF.command.name) 2014-07-16 16:12:14.854 | File /opt/stack/new/neutron/neutron/db/migration/cli.py, line 85, in do_upgrade_downgrade 2014-07-16 16:12:14.854 | do_alembic_command(config, cmd, revision, sql=CONF.command.sql) 2014-07-16 16:12:14.854 | File /opt/stack/new/neutron/neutron/db/migration/cli.py, line 63, in do_alembic_command 2014-07-16 16:12:14.854 | getattr(alembic_command, cmd)(config, *args, **kwargs) 2014-07-16 16:12:14.854 | File /usr/local/lib/python2.7/dist-packages/alembic/command.py, line 124, in upgrade 2014-07-16 16:12:14.854 | script.run_env() 2014-07-16 16:12:14.854 | File /usr/local/lib/python2.7/dist-packages/alembic/script.py, line 199, in run_env 2014-07-16 16:12:14.854 | util.load_python_file(self.dir, 'env.py') 2014-07-16 16:12:14.854 | File /usr/local/lib/python2.7/dist-packages/alembic/util.py, line 205, in load_python_file 2014-07-16 16:12:14.854 | module = load_module_py(module_id, path) 2014-07-16 16:12:14.854 | File /usr/local/lib/python2.7/dist-packages/alembic/compat.py, line 58, in load_module_py 2014-07-16 16:12:14.854 | mod = imp.load_source(module_id, path, fp) 2014-07-16 16:12:14.854 | File /opt/stack/new/neutron/neutron/db/migration/alembic_migrations/env.py, line 106, in module 2014-07-16 16:12:14.854 | run_migrations_online() 2014-07-16 16:12:14.855 | File /opt/stack/new/neutron/neutron/db/migration/alembic_migrations/env.py, line 90, in run_migrations_online 2014-07-16 16:12:14.855 | options=build_options()) 2014-07-16 16:12:14.855 | File string, line 7, in run_migrations 2014-07-16 16:12:14.855 | File /usr/local/lib/python2.7/dist-packages/alembic/environment.py, line 681, in run_migrations 2014-07-16 16:12:14.855 | self.get_context().run_migrations(**kw) 2014-07-16 16:12:14.855 | File /usr/local/lib/python2.7/dist-packages/alembic/migration.py, line 225, in run_migrations 2014-07-16 16:12:14.855 | change(**kw) 2014-07-16 16:12:14.856 | File /opt/stack/new/neutron/neutron/db/migration/alembic_migrations/versions/1d6ee1ae5da5_db_healing.py, line 32, in upgrade 2014-07-16 16:12:14.856 | heal_script.heal() 2014-07-16 16:12:14.856 | File /opt/stack/new/neutron/neutron/db/migration/alembic_migrations/heal_script.py, line 78, in heal 2014-07-16 16:12:14.856 | execute_alembic_command(el) 2014-07-16 16:12:14.856 | File /opt/stack/new/neutron/neutron/db/migration/alembic_migrations/heal_script.py, line 93, in execute_alembic_command 2014-07-16 16:12:14.856 | parse_modify_command(command) 2014-07-16 16:12:14.856 | File /opt/stack/new/neutron/neutron/db/migration/alembic_migrations/heal_script.py, line 126, in parse_modify_command 2014-07-16 16:12:14.856 | op.alter_column(table, column, **kwargs) 2014-07-16 16:12:14.856 | File string, line 7, in alter_column 2014-07-16 16:12:14.856 | File string, line 1, in lambda 2014-07-16 16:12:14.856 | File /usr/local/lib/python2.7/dist-packages/alembic/util.py, line 322, in go 2014-07-16 16:12:14.857 | return fn(*arg, **kw) 2014-07-16 16:12:14.857 | File /usr/local/lib/python2.7/dist-packages/alembic/operations.py, line 300, in alter_column 2014-07-16 16:12:14.857 | existing_autoincrement=existing_autoincrement 2014-07-16 16:12:14.857 | File /usr/local/lib/python2.7/dist-packages/alembic
[openstack-dev] [Neutron][CI] DB migration error
=dialect) 2014-07-16 16:12:14.858 | File string, line 1, in lambda 2014-07-16 16:12:14.858 | File /usr/local/lib/python2.7/dist-packages/sqlalchemy/sql/elements.py, line 493, in compile 2014-07-16 16:12:14.859 | return self._compiler(dialect, bind=bind, **kw) 2014-07-16 16:12:14.859 | File /usr/local/lib/python2.7/dist-packages/sqlalchemy/sql/ddl.py, line 25, in _compiler 2014-07-16 16:12:14.859 | return dialect.ddl_compiler(dialect, self, **kw) 2014-07-16 16:12:14.859 | File /usr/local/lib/python2.7/dist-packages/sqlalchemy/sql/compiler.py, line 196, in __init__ 2014-07-16 16:12:14.859 | self.string = self.process(self.statement, **compile_kwargs) 2014-07-16 16:12:14.859 | File /usr/local/lib/python2.7/dist-packages/sqlalchemy/sql/compiler.py, line 219, in process 2014-07-16 16:12:14.859 | return obj._compiler_dispatch(self, **kwargs) 2014-07-16 16:12:14.859 | File /usr/local/lib/python2.7/dist-packages/sqlalchemy/ext/compiler.py, line 410, in lambda 2014-07-16 16:12:14.859 | lambda *arg, **kw: existing(*arg, **kw)) 2014-07-16 16:12:14.859 | File /usr/local/lib/python2.7/dist-packages/sqlalchemy/ext/compiler.py, line 448, in __call__ 2014-07-16 16:12:14.859 | return fn(element, compiler, **kw) 2014-07-16 16:12:14.859 | File /usr/local/lib/python2.7/dist-packages/alembic/ddl/mysql.py, line 98, in _mysql_alter_column 2014-07-16 16:12:14.860 | autoincrement=element.autoincrement 2014-07-16 16:12:14.860 | File /usr/local/lib/python2.7/dist-packages/alembic/ddl/mysql.py, line 118, in _mysql_colspec 2014-07-16 16:12:14.860 | spec += DEFAULT %s % _render_value(compiler, server_default) 2014-07-16 16:12:14.860 | File /usr/local/lib/python2.7/dist-packages/alembic/ddl/mysql.py, line 106, in _render_value 2014-07-16 16:12:14.860 | return compiler.sql_compiler.process(expr) 2014-07-16 16:12:14.860 | File /usr/local/lib/python2.7/dist-packages/sqlalchemy/sql/compiler.py, line 219, in process 2014-07-16 16:12:14.860 | return obj._compiler_dispatch(self, **kwargs) 2014-07-16 16:12:14.860 | AttributeError: 'DefaultClause' object has no attribute '_compiler_dispatch' Kindly help how to resolve this issue. Thanks in advance. -- 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
[openstack-dev] [3rd Party] Log retention with 3rd party testing
Hi Stackers- I have a doubt on what is the timeline for log retention. From the discussion (irc), I learnt that time for log retention is ONE month. I have two scenarios to deal with. [1] A change takes two months or more to get merged into the master branch. Here, if CI's, delete the logs of the last month, the owner/reviewer may not be able to check the old logs. [2] A change is good and merged into the master branch. Here, if in future this change creates a BUG, a research on the CI logs might be a helpful to resolve this. To retain all the logs forever will be an storage issue. Kindly help me with you suggestions to resolve this. Thanks in advance. -- 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
[openstack-dev] [3rd Party] Log retention with 3rd party testing
Hi Stackers- I have a doubt on what is the timeline for log retention. From the discussion (irc), I learnt that time for log retention is ONE month. I have two scenarios to deal with. [1] A change takes two months or more to get merged into the master branch. Here, if CI's, delete the logs of the last month, the owner/reviewer may not be able to check the old logs. [2] A change is good and merged into the master branch. Here, if in future this change creates a BUG, a research on the CI logs might be a helpful to resolve this. To retain all the logs forever will be an storage issue. Kindly help me with you suggestions to resolve this. Thanks in advance. -- 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] Booting a Vm Failed VirtualMachineInterfaceFailed
Hi- Can you check whether all the neutron agents are running. Use this command $ neutron agent-list Check for all :) -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Sachi Gupta [mailto:sachi.gu...@tcs.com] Sent: Thursday, June 05, 2014 9:41 AM To: openstack-dev@lists.openstack.org Cc: Ankit21 A Subject: [openstack-dev] Booting a Vm Failed VirtualMachineInterfaceFailed Hi, 1. 1. While booting a virtual machine from Openstack dashboard, the call comes to Openstack compute where it is showing vif_binding details as vif_type = ovs 2. Please suggest on how to change the vif_type to vrouter Thanks Regards Sachi Gupta =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][Advanced Services] Requesting reviewers
+1 Summit. This really helps a lot for code and spec reviews. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Sumit Naiksatam [mailto:sumitnaiksa...@gmail.com] Sent: Saturday, May 31, 2014 5:31 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][Advanced Services] Requesting reviewers Hi Ivar, This is not just aimed at Neutron core reviewers. We are trying to get a set of reviewers who will commit to doing the reviews on a weekly basis. In fact, we would like to have a large number of non-core reviewers be a part of this review team. Patches which are filtered through this team can then bubble up to the cores, such that the cores can perform more focussed reviews (on these vetted patches). Of course, nothing stopping the cores from getting to the reviews sooner if they wish to. I have accordingly split the reviewers into two lists. Thanks, ~Sumit. On Fri, May 30, 2014 at 11:50 PM, Ivar Lazzaro ivarlazz...@gmail.com wrote: Hi Sumit, Review commitment sound like a good idea. Is this aiming core reviewers only? What number of cores / non cores are you ideally trying to reach? Thanks, Ivar. On Fri, May 30, 2014 at 7:21 PM, Sumit Naiksatam sumitnaiksa...@gmail.com wrote: During the Neutron Advanced Services' meeting this week [1], we discussed a plan to make the review process more predictable and accountable (as an experiment within this sub-team). We are soliciting reviewers who will commit to reviewing at least the prioritized blueprints [2] on a weekly basis and help make progress. If you feel comfortable making this commitment, please add your name to the top of this wiki page [2]. This will help the task owners to reach out to you and reconcile issues faster. It will also aid the core reviewers in making a judgement based on the feedback from of this reviewer team. Thanks, ~Sumit. [1] http://eavesdrop.openstack.org/meetings/networking_advanced_services/ 2014/networking_advanced_services.2014-05-28-17.31.log.html [2] https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Ivar. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] BPs for Juno-1
Hi-
Our CI FTP server is active now.
You may check the same at http://115.249.211.42/
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
-Original Message-
From: trinath.soman...@freescale.com [mailto:trinath.soman...@freescale.com]
Sent: Wednesday, May 28, 2014 12:28 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] BPs for Juno-1
Hi Kyle-
I'm working the issues with our FTP server which is hosting the CI testing logs.
Will update the status of the Server in this Email chain.
-
Trinath
From: Kyle Mestery mest...@noironetworks.com
Sent: Wednesday, May 28, 2014 12:24 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] BPs for Juno-1
I've marked it as Juno-1 for now, but as Salvatore indicated, there are some
issues with third party testing which need to be addressed before this can be
merged. It would be a good idea to attend the IRC meeting Anita pointed out as
well.
Thanks,
Kyle
On Tue, May 27, 2014 at 1:45 PM, trinath.soman...@freescale.com
trinath.soman...@freescale.com wrote:
Hi Kyle-
The BP Spec approved.
https://review.openstack.org/#/c/88190/
Kindly consider my BP spec for Juno-1.
Thanking all the code reviewers for their time to review my ML2 MD Spec and
making me to improve the spec.
-
Trinaths
From: Kyle Mestery mest...@noironetworks.com
Sent: Tuesday, May 27, 2014 10:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] BPs for Juno-1
On Tue, May 27, 2014 at 12:12 PM, Vinay Yadhav vinayyad...@gmail.com wrote:
Hi,
I have been working on the port mirroring blueprint and i was asked
to submit a neutron spec related to this I have drafter the spec and
ready to commit it to the
'git://git.openstack.org/openstack/neutron-specs' repository for
review. Since the blueprint for this was old i was asked to submit
the spec for review. should i also bring the old blueprint to life by
linking it the spec that i will commit.
You can file a BP in launchpad. We're using those to track progress
against milestones for release management reasons. Please see the
instructions here [1]. Once the BP is filed in neutron-specs, reviewed
and approved, we can track it to milestones. But at this point, this
won't make it to Juno-1, given that's 2 weeks away.
Thanks,
Kyle
[1] https://wiki.openstack.org/wiki/Blueprints#Neutron
We are calling the new spec Tap-as-a-Service
Cheers,
main(i){putchar((5852758((i-1)/2)*8)-!(1i)*'\r')^89main(++i);}
On Tue, May 27, 2014 at 4:14 PM, Kyle Mestery
mest...@noironetworks.com
wrote:
Hi Neutron developers:
I've spent some time cleaning up the BPs for Juno-1, and they are
documented at the link below [1]. There are a large number of BPs
currently under review right now in neutron-specs. If we land some
of those specs this week, it's possible some of these could make it
into Juno-1, pending review cycles and such. But I just wanted to
highlight that I removed a large number of BPs from targeting Juno-1
now which did not have specifications linked to them nor
specifications which were actively under review in neutron-specs.
Also, a gentle reminder that the process for submitting
specifications to Neutron is documented here [2].
Thanks, and please reach out to me if you have any questions!
Kyle
[1] https://launchpad.net/neutron/+milestone/juno-1
[2] https://wiki.openstack.org/wiki/Blueprints#Neutron
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] BPs for Juno-1
Hi Kyle Kindly consider my BP spec (https://review.openstack.org/#/c/88190/) too for Juno1. I have been mailing the reviewer to kindly make some to to review the BP spec. I have code too in place for review along with working CI. The Code for review : https://review.openstack.org/#/c/78092/ Kindly please do the needful. -- Trinath Somanchi. From: Kyle Mestery mest...@noironetworks.com Sent: Tuesday, May 27, 2014 7:44 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] BPs for Juno-1 Hi Neutron developers: I've spent some time cleaning up the BPs for Juno-1, and they are documented at the link below [1]. There are a large number of BPs currently under review right now in neutron-specs. If we land some of those specs this week, it's possible some of these could make it into Juno-1, pending review cycles and such. But I just wanted to highlight that I removed a large number of BPs from targeting Juno-1 now which did not have specifications linked to them nor specifications which were actively under review in neutron-specs. Also, a gentle reminder that the process for submitting specifications to Neutron is documented here [2]. Thanks, and please reach out to me if you have any questions! Kyle [1] https://launchpad.net/neutron/+milestone/juno-1 [2] https://wiki.openstack.org/wiki/Blueprints#Neutron ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] BPs for Juno-1
Hi- Sure!. Will change the topic and update you. Thanks a lot for the reply and review. Your review helps me a lot to proceed further with code. Thanking you .. - Trinath Somanchi From: Edgar Magana Perdomo (eperdomo) eperd...@cisco.com Sent: Tuesday, May 27, 2014 10:18 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] BPs for Juno-1 My only comment is that the name of the topic should be: bp/fsl-sdn-os-mech-driver Instead of: bp/https I guss we can pass this.. Edgar On 5/27/14, 9:23 AM, trinath.soman...@freescale.com trinath.soman...@freescale.com wrote: Hi Kyle Kindly consider my BP spec (https://review.openstack.org/#/c/88190/) too for Juno1. I have been mailing the reviewer to kindly make some to to review the BP spec. I have code too in place for review along with working CI. The Code for review : https://review.openstack.org/#/c/78092/ Kindly please do the needful. -- Trinath Somanchi. From: Kyle Mestery mest...@noironetworks.com Sent: Tuesday, May 27, 2014 7:44 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] BPs for Juno-1 Hi Neutron developers: I've spent some time cleaning up the BPs for Juno-1, and they are documented at the link below [1]. There are a large number of BPs currently under review right now in neutron-specs. If we land some of those specs this week, it's possible some of these could make it into Juno-1, pending review cycles and such. But I just wanted to highlight that I removed a large number of BPs from targeting Juno-1 now which did not have specifications linked to them nor specifications which were actively under review in neutron-specs. Also, a gentle reminder that the process for submitting specifications to Neutron is documented here [2]. Thanks, and please reach out to me if you have any questions! Kyle [1] https://launchpad.net/neutron/+milestone/juno-1 [2] https://wiki.openstack.org/wiki/Blueprints#Neutron ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] BPs for Juno-1
Hi- Thanks a lot Salvatore. I'm looking into that issue. I'm troubleshooting the same. Will update this mail chain when its accessible for review. Thanks a lot for the review Salvatore. -- Trinath From: Salvatore Orlando sorla...@nicira.com Sent: Tuesday, May 27, 2014 10:29 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] BPs for Juno-1 Too late. I just approved the specification. I don't think there is any need for reverting the blueprint and just updating the topic in the patch. Please have a look at Freescale CI - logs are not accessible at the moment. Salvatore On 27 May 2014 18:51, trinath.soman...@freescale.commailto:trinath.soman...@freescale.com trinath.soman...@freescale.commailto:trinath.soman...@freescale.com wrote: Hi- Sure!. Will change the topic and update you. Thanks a lot for the reply and review. Your review helps me a lot to proceed further with code. Thanking you .. - Trinath Somanchi From: Edgar Magana Perdomo (eperdomo) eperd...@cisco.commailto:eperd...@cisco.com Sent: Tuesday, May 27, 2014 10:18 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] BPs for Juno-1 My only comment is that the name of the topic should be: bp/fsl-sdn-os-mech-driver Instead of: bp/https I guss we can pass this.. Edgar On 5/27/14, 9:23 AM, trinath.soman...@freescale.commailto:trinath.soman...@freescale.com trinath.soman...@freescale.commailto:trinath.soman...@freescale.com wrote: Hi Kyle Kindly consider my BP spec (https://review.openstack.org/#/c/88190/) too for Juno1. I have been mailing the reviewer to kindly make some to to review the BP spec. I have code too in place for review along with working CI. The Code for review : https://review.openstack.org/#/c/78092/ Kindly please do the needful. -- Trinath Somanchi. From: Kyle Mestery mest...@noironetworks.commailto:mest...@noironetworks.com Sent: Tuesday, May 27, 2014 7:44 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] BPs for Juno-1 Hi Neutron developers: I've spent some time cleaning up the BPs for Juno-1, and they are documented at the link below [1]. There are a large number of BPs currently under review right now in neutron-specs. If we land some of those specs this week, it's possible some of these could make it into Juno-1, pending review cycles and such. But I just wanted to highlight that I removed a large number of BPs from targeting Juno-1 now which did not have specifications linked to them nor specifications which were actively under review in neutron-specs. Also, a gentle reminder that the process for submitting specifications to Neutron is documented here [2]. Thanks, and please reach out to me if you have any questions! Kyle [1] https://launchpad.net/neutron/+milestone/juno-1 [2] https://wiki.openstack.org/wiki/Blueprints#Neutron ___ 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 ___ 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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] BPs for Juno-1
Hi Kyle-
The BP Spec approved.
https://review.openstack.org/#/c/88190/
Kindly consider my BP spec for Juno-1.
Thanking all the code reviewers for their time to review my ML2 MD Spec and
making me to improve the spec.
-
Trinaths
From: Kyle Mestery mest...@noironetworks.com
Sent: Tuesday, May 27, 2014 10:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] BPs for Juno-1
On Tue, May 27, 2014 at 12:12 PM, Vinay Yadhav vinayyad...@gmail.com wrote:
Hi,
I have been working on the port mirroring blueprint and i was asked to
submit a neutron spec related to this
I have drafter the spec and ready to commit it to the
'git://git.openstack.org/openstack/neutron-specs' repository for
review. Since the blueprint for this was old i was asked to submit the spec
for review. should i also bring the old blueprint to life
by linking it the spec that i will commit.
You can file a BP in launchpad. We're using those to track progress
against milestones for release management reasons. Please see the
instructions here [1]. Once the BP is filed in neutron-specs, reviewed
and approved, we can track it to milestones. But at this point, this
won't make it to Juno-1, given that's 2 weeks away.
Thanks,
Kyle
[1] https://wiki.openstack.org/wiki/Blueprints#Neutron
We are calling the new spec Tap-as-a-Service
Cheers,
main(i){putchar((5852758((i-1)/2)*8)-!(1i)*'\r')^89main(++i);}
On Tue, May 27, 2014 at 4:14 PM, Kyle Mestery mest...@noironetworks.com
wrote:
Hi Neutron developers:
I've spent some time cleaning up the BPs for Juno-1, and they are
documented at the link below [1]. There are a large number of BPs
currently under review right now in neutron-specs. If we land some of
those specs this week, it's possible some of these could make it into
Juno-1, pending review cycles and such. But I just wanted to highlight
that I removed a large number of BPs from targeting Juno-1 now which
did not have specifications linked to them nor specifications which
were actively under review in neutron-specs.
Also, a gentle reminder that the process for submitting specifications
to Neutron is documented here [2].
Thanks, and please reach out to me if you have any questions!
Kyle
[1] https://launchpad.net/neutron/+milestone/juno-1
[2] https://wiki.openstack.org/wiki/Blueprints#Neutron
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] BPs for Juno-1
Hi- Sure Anita. I have been attending meeting for ML2 at #openstack-meeting-alt. Will also, attend the below mentioned meetings .. Thanking you. - Trinaths From: Anita Kuno ante...@anteaya.info Sent: Tuesday, May 27, 2014 10:45 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [neutron] BPs for Juno-1 On 05/27/2014 01:03 PM, trinath.soman...@freescale.com wrote: Hi- Thanks a lot Salvatore. I'm looking into that issue. I'm troubleshooting the same. Will update this mail chain when its accessible for review. Thanks a lot for the review Salvatore. -- Trinath Have you considered starting an irc client, navigating to freenode and joining the #openstack-dev and #openstack-neutron channels? It would increase the rate at which you learn how to amend your code to get it merged. It also would help as you troubleshoot your CI system. Give it some thought, Anita. From: Salvatore Orlando sorla...@nicira.com Sent: Tuesday, May 27, 2014 10:29 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] BPs for Juno-1 Too late. I just approved the specification. I don't think there is any need for reverting the blueprint and just updating the topic in the patch. Please have a look at Freescale CI - logs are not accessible at the moment. Salvatore On 27 May 2014 18:51, trinath.soman...@freescale.commailto:trinath.soman...@freescale.com trinath.soman...@freescale.commailto:trinath.soman...@freescale.com wrote: Hi- Sure!. Will change the topic and update you. Thanks a lot for the reply and review. Your review helps me a lot to proceed further with code. Thanking you .. - Trinath Somanchi From: Edgar Magana Perdomo (eperdomo) eperd...@cisco.commailto:eperd...@cisco.com Sent: Tuesday, May 27, 2014 10:18 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] BPs for Juno-1 My only comment is that the name of the topic should be: bp/fsl-sdn-os-mech-driver Instead of: bp/https I guss we can pass this.. Edgar On 5/27/14, 9:23 AM, trinath.soman...@freescale.commailto:trinath.soman...@freescale.com trinath.soman...@freescale.commailto:trinath.soman...@freescale.com wrote: Hi Kyle Kindly consider my BP spec (https://review.openstack.org/#/c/88190/) too for Juno1. I have been mailing the reviewer to kindly make some to to review the BP spec. I have code too in place for review along with working CI. The Code for review : https://review.openstack.org/#/c/78092/ Kindly please do the needful. -- Trinath Somanchi. From: Kyle Mestery mest...@noironetworks.commailto:mest...@noironetworks.com Sent: Tuesday, May 27, 2014 7:44 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] BPs for Juno-1 Hi Neutron developers: I've spent some time cleaning up the BPs for Juno-1, and they are documented at the link below [1]. There are a large number of BPs currently under review right now in neutron-specs. If we land some of those specs this week, it's possible some of these could make it into Juno-1, pending review cycles and such. But I just wanted to highlight that I removed a large number of BPs from targeting Juno-1 now which did not have specifications linked to them nor specifications which were actively under review in neutron-specs. Also, a gentle reminder that the process for submitting specifications to Neutron is documented here [2]. Thanks, and please reach out to me if you have any questions! Kyle [1] https://launchpad.net/neutron/+milestone/juno-1 [2] https://wiki.openstack.org/wiki/Blueprints#Neutron ___ 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 ___ 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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] BPs for Juno-1
Hi Kyle-
I'm working the issues with our FTP server which is hosting the CI testing logs.
Will update the status of the Server in this Email chain.
-
Trinath
From: Kyle Mestery mest...@noironetworks.com
Sent: Wednesday, May 28, 2014 12:24 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] BPs for Juno-1
I've marked it as Juno-1 for now, but as Salvatore indicated, there
are some issues with third party testing which need to be addressed
before this can be merged. It would be a good idea to attend the IRC
meeting Anita pointed out as well.
Thanks,
Kyle
On Tue, May 27, 2014 at 1:45 PM, trinath.soman...@freescale.com
trinath.soman...@freescale.com wrote:
Hi Kyle-
The BP Spec approved.
https://review.openstack.org/#/c/88190/
Kindly consider my BP spec for Juno-1.
Thanking all the code reviewers for their time to review my ML2 MD Spec and
making me to improve the spec.
-
Trinaths
From: Kyle Mestery mest...@noironetworks.com
Sent: Tuesday, May 27, 2014 10:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] BPs for Juno-1
On Tue, May 27, 2014 at 12:12 PM, Vinay Yadhav vinayyad...@gmail.com wrote:
Hi,
I have been working on the port mirroring blueprint and i was asked to
submit a neutron spec related to this
I have drafter the spec and ready to commit it to the
'git://git.openstack.org/openstack/neutron-specs' repository for
review. Since the blueprint for this was old i was asked to submit the spec
for review. should i also bring the old blueprint to life
by linking it the spec that i will commit.
You can file a BP in launchpad. We're using those to track progress
against milestones for release management reasons. Please see the
instructions here [1]. Once the BP is filed in neutron-specs, reviewed
and approved, we can track it to milestones. But at this point, this
won't make it to Juno-1, given that's 2 weeks away.
Thanks,
Kyle
[1] https://wiki.openstack.org/wiki/Blueprints#Neutron
We are calling the new spec Tap-as-a-Service
Cheers,
main(i){putchar((5852758((i-1)/2)*8)-!(1i)*'\r')^89main(++i);}
On Tue, May 27, 2014 at 4:14 PM, Kyle Mestery mest...@noironetworks.com
wrote:
Hi Neutron developers:
I've spent some time cleaning up the BPs for Juno-1, and they are
documented at the link below [1]. There are a large number of BPs
currently under review right now in neutron-specs. If we land some of
those specs this week, it's possible some of these could make it into
Juno-1, pending review cycles and such. But I just wanted to highlight
that I removed a large number of BPs from targeting Juno-1 now which
did not have specifications linked to them nor specifications which
were actively under review in neutron-specs.
Also, a gentle reminder that the process for submitting specifications
to Neutron is documented here [2].
Thanks, and please reach out to me if you have any questions!
Kyle
[1] https://launchpad.net/neutron/+milestone/juno-1
[2] https://wiki.openstack.org/wiki/Blueprints#Neutron
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Jenkins CI job Error
-20_11_16_12_368 15678 TRACE oslo.messaging.notify.dispatcher File /opt/stack/new/ceilometer/ceilometer/plugin.py, line 125, in to_samples_and_publish 2014-05-20 11:16:12.368http://logs.openstack.org/92/78092/10/check/check-tempest-dsvm-neutron-pg-2/850d041/logs/screen-ceilometer-anotification.txt.gz?level=TRACE#_2014-05-20_11_16_12_368 15678 TRACE oslo.messaging.notify.dispatcher p(list(self.process_notification(notification))) 2014-05-20 11:16:12.368http://logs.openstack.org/92/78092/10/check/check-tempest-dsvm-neutron-pg-2/850d041/logs/screen-ceilometer-anotification.txt.gz?level=TRACE#_2014-05-20_11_16_12_368 15678 TRACE oslo.messaging.notify.dispatcher File /opt/stack/new/ceilometer/ceilometer/network/notifications.py, line 88, in process_notification 2014-05-20 11:16:12.368http://logs.openstack.org/92/78092/10/check/check-tempest-dsvm-neutron-pg-2/850d041/logs/screen-ceilometer-anotification.txt.gz?level=TRACE#_2014-05-20_11_16_12_368 15678 TRACE oslo.messaging.notify.dispatcher resource_id=message['payload']['id'], 2014-05-20 11:16:12.368http://logs.openstack.org/92/78092/10/check/check-tempest-dsvm-neutron-pg-2/850d041/logs/screen-ceilometer-anotification.txt.gz?level=TRACE#_2014-05-20_11_16_12_368 15678 TRACE oslo.messaging.notify.dispatcher KeyError: 'id' 2014-05-20 11:16:12.368http://logs.openstack.org/92/78092/10/check/check-tempest-dsvm-neutron-pg-2/850d041/logs/screen-ceilometer-anotification.txt.gz?level=TRACE#_2014-05-20_11_16_12_368 15678 TRACE oslo.messaging.notify.dispatcher In the Console logs, it posted the error as 2014-05-20 11:06:12.493 | ... this takes 5 - 8 minutes (logs in logs/devstacklog.txt.gz) 2014-05-20 11:13:50.065 | ERROR: the main setup script run by this job failed - exit code: 1 2014-05-20 11:13:50.066 | please look at the relevant log files to determine the root cause With these errors, it posted a '-1' for code review. Kindly help me to resolve this issue -- 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
[openstack-dev] JUNO BP review and Approvals
Hi Stackers- Since, the Juno summit is completed, when can we have the JUNO Blueprints reviews and approvals getting started. Kindly help me the J-1 deadlines for Blueprint approval and Code merge. Thanks in advance -- 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] Voting for the TC Election is now open
Hi Anita- I did not receive any mail for vote. Is there any process to do from my end to vote. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent: Friday, April 18, 2014 8:53 PM To: OpenStack Development Mailing List Subject: [openstack-dev] Voting for the TC Election is now open Voting for the TC Election is now open and will remain open until after 1300 utc April 24 2014. We are electing 7 positions from a pool of 17 candidates[0]. Follow the instructions that are available when you vote. If you are confused and need more instruction, close the webpage without submitting your vote and then email myself and Tristan[1]. Your ballot will still be enabled to vote until the election is closed, as long as you don't submit your ballot before your close your webpage. You are eligible to vote if are a Foundation individual member[2] that also has committed to one of the official programs projects[3] over the Havana-Icehouse timeframe (April 4, 2013 06:00 UTC to April 4, 2014 05:59 UTC) Or if you are one of the extra-atcs.[4] What to do if you don't see the email and have a commit in at least one of the official programs projects[3]: * check the trash of your gerrit Preferred Email address[5], in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from the program project repos[3] and email me and Tristan[1]. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Our democratic process is important to the health of OpenStack, please exercise your right to vote. Candidate statements/platforms can be found linked to Candidate names on this page: https://wiki.openstack.org/wiki/TC_Elections_April_2014#Candidates Happy voting, Anita. (anteaya) [0] https://wiki.openstack.org/wiki/TC_Elections_April_2014#Candidates [1] Anita: anteaya at anteaya dot info Tristan: tristan dot cacqueray at enovance dot com [2] http://www.openstack.org/community/members/ [3] http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml?id=april-2014-elections [4] http://git.openstack.org/cgit/openstack/governance/tree/reference/extra-atcs [5] Sign into review.openstack.org: Go to Settings Contact Information. Look at the email listed as your Preferred Email. That is where the ballot has been sent. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Voting for the TC Election is now open
Hi Anita- I have check the spam and junk emails .. None have the ballot email. Here are the gerrit details Usernametrinaths Full Name Trinath Somanchi Email Address trinath.soman...@freescale.com Registered Sep 2, 2013 12:35 PM Account ID 8645 Can you kindly please check at your end. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent: Saturday, April 19, 2014 7:26 PM To: Somanchi Trinath-B39208; OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] Voting for the TC Election is now open On 04/19/2014 05:42 AM, trinath.soman...@freescale.com wrote: Hi Anita- I did not receive any mail for vote. Is there any process to do from my end to vote. Yes. Please read this section of my original email. What to do if you don't see the email and have a commit in at least one of the official programs projects[3]: * check the trash of your gerrit Preferred Email address[5], in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from the program project repos[3] and email me and Tristan[1]. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Thank you, Anita. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent: Friday, April 18, 2014 8:53 PM To: OpenStack Development Mailing List Subject: [openstack-dev] Voting for the TC Election is now open Voting for the TC Election is now open and will remain open until after 1300 utc April 24 2014. We are electing 7 positions from a pool of 17 candidates[0]. Follow the instructions that are available when you vote. If you are confused and need more instruction, close the webpage without submitting your vote and then email myself and Tristan[1]. Your ballot will still be enabled to vote until the election is closed, as long as you don't submit your ballot before your close your webpage. You are eligible to vote if are a Foundation individual member[2] that also has committed to one of the official programs projects[3] over the Havana-Icehouse timeframe (April 4, 2013 06:00 UTC to April 4, 2014 05:59 UTC) Or if you are one of the extra-atcs.[4] What to do if you don't see the email and have a commit in at least one of the official programs projects[3]: * check the trash of your gerrit Preferred Email address[5], in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from the program project repos[3] and email me and Tristan[1]. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Our democratic process is important to the health of OpenStack, please exercise your right to vote. Candidate statements/platforms can be found linked to Candidate names on this page: https://wiki.openstack.org/wiki/TC_Elections_April_2014#Candidates Happy voting, Anita. (anteaya) [0] https://wiki.openstack.org/wiki/TC_Elections_April_2014#Candidates [1] Anita: anteaya at anteaya dot info Tristan: tristan dot cacqueray at enovance dot com [2] http://www.openstack.org/community/members/ [3] http://git.openstack.org/cgit/openstack/governance/tree/reference/prog rams.yaml?id=april-2014-elections [4] http://git.openstack.org/cgit/openstack/governance/tree/reference/extr a-atcs [5] Sign into review.openstack.org: Go to Settings Contact Information. Look at the email listed as your Preferred Email. That is where the ballot has been sent. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] Neutron BP review process for Juno
Hi Mestery With respect to the new BP review process, can we start submitting the BPs in the review system and in the launchpad. Since, BP is a thought process of the developer either for core dev or for vendor specific dev, can you give some light on how the review process of the BP can be ? asciiflow.com is a best tool for showing the pictorial representation of the BP work. Thank you for the link.. Were there any variations in general code review processes. - Trinath From: Kyle Mestery mest...@noironetworks.com Sent: Wednesday, April 16, 2014 7:22 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] Neutron BP review process for Juno Actually, +1 to that Salvatore! I've found asciiflow.com to be superb for these types of things. On Wed, Apr 16, 2014 at 8:39 AM, Salvatore Orlando sorla...@nicira.com wrote: if the image you're adding is a diagram, I would think about asciiflow.com first! On 16 April 2014 15:09, Kyle Mestery mest...@noironetworks.com wrote: I think the problem is that your spec should be at the toplevel of the juno directory, and that's why the UT is failing. Can you move your spec up a level, including the image? You can create a spec images directory to put them in there and reference it in the spec as well if you want. On Tue, Apr 15, 2014 at 11:48 PM, Sumit Naiksatam sumitnaiksa...@gmail.com wrote: What's the convention for adding images to the patch? The following directory structure seemed logical to me (but the current UT will not allow it): specs/juno/bp-name/bp-name.rst specs/juno/bp-name/images/image1.png Thanks, ~Sumit. On Tue, Apr 15, 2014 at 3:35 PM, Carl Baldwin c...@ecbaldwin.net wrote: +1. I think we'll like this process better. I hope to have some of the first blueprints to propose to the new repository very soon. On Tue, Apr 15, 2014 at 4:07 PM, Kyle Mestery mest...@noironetworks.com wrote: Given the success the Nova team has had in handling reviews using their new nova-specs gerrit repository, I think it makes a lot of sense for Neutron to do the same. With this in mind, I've added instructions to the BP wiki [1] for how to do. Going forward in Juno, this is how Neutron BPs will be handled by the Neutron core team. If you are currently working on a BP or code for Juno which is attached to a BP, please file the BP using the process here [1]. Given this is our first attempt at using this for reviews, I anticipate there may be a few hiccups along the way. Please reply on this thread or reach out in #openstack-neutron and we'll sort through whatever issues we find. Thanks! Kyle [1] https://wiki.openstack.org/wiki/Blueprints#Neutron ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra] [3rd party testing] QA meeting today at 14:00 EST / 18:00 UTC
+1 Attending -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Monday, March 10, 2014 9:30 PM To: OpenStack Development Mailing List; openstack-infra Subject: [OpenStack-Infra] [3rd party testing] QA meeting today at 14:00 EST / 18:00 UTC Hi Stackers, We'll be having our second weekly QA/workshop session around third party testing today at 14:00 EST / 18:00 UTC in #openstack-meeting on Freenode IRC. See you all there. Best, -jay ___ OpenStack-Infra mailing list openstack-in...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] FFE Request: Freescale SDN ML2 Mechanism Driver
Hi Mark,? We have the codebase and the 3rd Party CI setup in place for review. Freescale CI is currently in non-voting status. Kindly please consider the Blueprint and the codebase for FFE (icehouse release). Blueprint: https://blueprints.launchpad.net/neutron/+spec/fsl-sdn-os-mech-driver and Code base: https://review.openstack.org/#/c/78092/ ? Kindly please do the needful. Thanking you - Trinath Somanchi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra] [Third Party CI] Reminder: Workshop/QA meeting on #openstack-meeting today at 13:00EST/18:00 UTC
Hi Jay- Thank you for the reminder. Waiting to meet you at the IRC webchat. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Monday, March 03, 2014 9:47 PM To: OpenStack Development Mailing List; openstack-infra Subject: [OpenStack-Infra] [Third Party CI] Reminder: Workshop/QA meeting on #openstack-meeting today at 13:00EST/18:00 UTC Hi all, Just a friendly reminder we will have a workshop and QA meeting on Freeonde #openstack-meeting channel today at 18:00 UTC (13:00 EST) for folks interested in setting up or debugging third party CI platforms. See you there! Best, -jay ___ OpenStack-Infra mailing list openstack-in...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Devstack Error
Hi Ben- Can you give a guess of the problem. I feel that there might be some error with devstack-gate which brings down the things from git and configure it in the system. The first error started at “openstack role add: error: argument –user: expected one argument” Do I need to check or verify any other configuration for this issue. Kindly help me resolve the same. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Ben Nemec [mailto:openst...@nemebean.com] Sent: Tuesday, February 25, 2014 9:23 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Devstack Error On 2014-02-25 08:19, trinath.soman...@freescale.commailto:trinath.soman...@freescale.com wrote: Hi Stackers- When I configured Jenkins to run the Sandbox tempest testing, While devstack is running, I have seen error “ERROR: Invalid Openstack Nova credentials” and another error “ERROR: HTTPConnection Pool(host=’127.0.0.1’, port=8774): Max retries exceeded wuth url: /v2/91dd….(caused by class ‘socket.error’: [Errno 111] Connection refused) I feel devstack automates the openstack environment. Kindly guide me resolve the issue. Thanks in advance. -- Trinath Somanchi - B39208 trinath.soman...@freescale.commailto:trinath.soman...@freescale.com | extn: 4048 Those are both symptoms of an underlying problem. It sounds like a service didn't start or wasn't configured correctly, but it's impossible to say for sure what went wrong based on this information. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra] [third-party-ci] Proposing a regular workshop/meeting to help folks set up CI environments
Hi Jay- Rather than March 3rd Can you kindly make it on Feb 28th if possible. I'm interested in attending the meeting. I have doubts to get clarified regarding setp, configuration and CI system. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Wednesday, February 26, 2014 4:38 AM To: Arx Cruz Cc: OpenStack Development Mailing List; openstack-infra; John Griffith Subject: Re: [OpenStack-Infra] [third-party-ci] Proposing a regular workshop/meeting to help folks set up CI environments On Tue, 2014-02-25 at 20:02 -0300, Arx Cruz wrote: Hello, Great Idea, I'm very interested! I wasn't able to see the Google Hangout Event, is the url correct? Hi Arx! We changed from Google Hangout to using IRC. See here for more info: http://lists.openstack.org/pipermail/openstack-dev/2014-February/028124.html Best, -jay ___ OpenStack-Infra mailing list openstack-in...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra] [Neutron][third-party-testing] Third Party Test setup and details
Hi Sukhdev- Really a good document to go with. In the ‘System flow’ section of the document, where do this testRunner script come from ?? And the below actions are specified to be run with the testRunner script. Can you elaborate that part. Also, I’m looking into the document in a way to setup a CI. Will this help me in this regard. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Sukhdev Kapur [mailto:sukhdevka...@gmail.com] Sent: Wednesday, February 26, 2014 3:39 AM To: openstack-in...@lists.openstack.org; OpenStack Development Mailing List (not for usage questions) Subject: [OpenStack-Infra] [Neutron][third-party-testing] Third Party Test setup and details Fellow developers, I just put together a wiki describing the Arista Third Party Setup. In the attached document we provide a link to the modified Gerrit Plugin to handle the regex matching for the Comment Added event so that recheck/reverify no bug/ can be handled. https://wiki.openstack.org/wiki/Arista-third-party-testing Have a look. Your feedback/comments will be appreciated. regards.. -Sukhdev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Devstack Error
Hi Stackers- When I configured Jenkins to run the Sandbox tempest testing, While devstack is running, I have seen error ERROR: Invalid Openstack Nova credentials and another error ERROR: HTTPConnection Pool(host='127.0.0.1', port=8774): Max retries exceeded wuth url: /v2/91dd(caused by class 'socket.error': [Errno 111] Connection refused) I feel devstack automates the openstack environment. Kindly guide me resolve the issue. Thanks in advance. -- 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 ML2 and openvswitch agent
Hi Hope this helps http://fr.slideshare.net/mestery/modular-layer-2-in-openstack-neutron ___ Trinath Somanchi _ From: Sławek Kapłoński [sla...@kaplonski.pl] Sent: Tuesday, February 25, 2014 9:24 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] Neutron ML2 and openvswitch agent Hello, I have question to You guys. Can someone explain me (or send to link with such explanation) how exactly ML2 plugin which is working on neutron server is communicating with compute hosts with openvswitch agents? I suppose that this is working with rabbitmq queues but I need to add own function which will be called in this agent and I don't know how to do that. It would be perfect if such think will be possible with writing for example new mechanical driver in ML2 plugin (but how?). Thanks in advance for any help from You :) -- Best regards Slawek Kaplonski sla...@kaplonski.pl ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Infra] [Neutron][third-party-testing] Third Party Test setup and details
Excellent! Will check this From: Sukhdev Kapur [sukhdevka...@gmail.com] Sent: Wednesday, February 26, 2014 3:38 AM To: openstack-in...@lists.openstack.org; OpenStack Development Mailing List (not for usage questions) Subject: [OpenStack-Infra] [Neutron][third-party-testing] Third Party Test setup and details Fellow developers, I just put together a wiki describing the Arista Third Party Setup. In the attached document we provide a link to the modified Gerrit Plugin to handle the regex matching for the Comment Added event so that recheck/reverify no bug/ can be handled. https://wiki.openstack.org/wiki/Arista-third-party-testing Have a look. Your feedback/comments will be appreciated. regards.. -Sukhdev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core
+1 -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 -Original Message- From: Akihiro Motoki [mailto:mot...@da.jp.nec.com] Sent: Wednesday, February 12, 2014 1:45 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core +1 (2014/02/11 8:28), Mark McClain wrote: All- I'd like to nominate Oleg Bondarev to become a Neutron core reviewer. Oleg has been valuable contributor to Neutron by actively reviewing, working on bugs, and contributing code. Neutron cores please reply back with +1/0/-1 votes. mark ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Neutron py27 test 'FAIL: process-returncode'
Hi Gary- Look into the logs with a search towards your written code keywords.. There might be some issues related to PEP8 or invalid import paths. Hope this helps. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Gary Duan [mailto:garyd...@gmail.com] Sent: Wednesday, February 12, 2014 9:20 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Neutron py27 test 'FAIL: process-returncode' Clark, You are right. The test must have been bailed out. The question is what I should look for. Even a successful case has a lot of Traceback, ERROR log in subunit_log.txt. Thanks, Gary On Tue, Feb 11, 2014 at 7:19 PM, Clark Boylan clark.boy...@gmail.commailto:clark.boy...@gmail.com wrote: On Tue, Feb 11, 2014 at 7:05 PM, Gary Duan garyd...@gmail.commailto:garyd...@gmail.com wrote: Hi, Clark, Thanks for your reply. I thought the same thing at first, but the page by default only shows the failed cases. The other 1284 cases were OK. Gary On Tue, Feb 11, 2014 at 6:07 PM, Clark Boylan clark.boy...@gmail.commailto:clark.boy...@gmail.com wrote: On Tue, Feb 11, 2014 at 5:52 PM, Gary Duan garyd...@gmail.commailto:garyd...@gmail.com wrote: Hi, The patch I submitted for L3 service framework integration fails on jenkins test, py26 and py27. The console only gives following error message, 2014-02-12 00:45:01.710 | FAIL: process-returncode 2014-02-12 00:45:01.711 | tags: worker-1 and at the end, 2014-02-12 00:45:01.916 | ERROR: InvocationError: '/home/jenkins/workspace/gate-neutron-python27/.tox/py27/bin/python -m neutron.openstack.common.lockutils python setup.py testr --slowest --testr-args=' 2014-02-12 00:45:01.917 | ___ summary 2014-02-12 00:45:01.918 | ERROR: py27: commands failed I wonder what might be the reason for the failure and how to debug this problem? The patch is at, https://review.openstack.org/#/c/59242/ The console output is, http://logs.openstack.org/42/59242/7/check/gate-neutron-python27/e395b06/console.html Thanks, Gary ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev I haven't dug into this too far but http://logs.openstack.org/42/59242/7/check/gate-neutron-python27/e395b06/testr_results.html.gz seems to offer some clues. Not sure why the console output doesn't show the additional non exit code errors (possibly a nonstandard formatter? or a bug?). Also, cases like this tend to be the test framework completely dying due to a sys.exit somewhere or similar. This kills the tests and runs only a small subset of them which seems to be the case here. Clark ___ 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 I picked a different neutron master change and it ran 10k py27 unittests. Pretty sure the test framework is bailing out early here. Clark ___ 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.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Agenda for todays ML2 Weekly meeting
Hi- Kindly share me the agenda for today weekly meeting on Neutron/ML2. Best Regards, -- 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] [QA][Neutron][3rd Party Testing] Methodology for 3rd party
Hi - I'm a new bee here.. Can anyone guide me on setting up a new 3rd party Testing account. How it is useful ? What the machine requirements? How testing is automated ? How to post back +/- 1 to Jenkins ? What packages are to be installed ? Kindly help me understand them. Thanks in advance -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Miguel Angel [mailto:miguelan...@ajo.es] Sent: Wednesday, February 05, 2014 11:59 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [QA][Neutron][3rd Party Testing] Methodology for 3rd party Interesting points here, I agree with Akihiro, some components leave services, and left over settings over the system even when shut down (I know of neutron net namespaces, .. etc..). +1 to Akihiro proposals for a fresh-vm. --- irc: ajo / mangelajo Miguel Angel Ajo Pelayo +34 636 52 25 69 skype: ajoajoajo 2014-02-05 Akihiro Motoki mot...@da.jp.nec.commailto:mot...@da.jp.nec.com: Hi, I think it is better to use a fresh VM to run tests. When running tempest scenario tests, there is a case where some resources can not be cleanup properly. It happens when some test fails of course. I think 10 minutes is not too long. It requires more than 30 minutes until gate jobs on openstack-ci report test results. 10 minutes is fast enough compared to this time. Other ways to speed up the testing are: - to instsall dependecy packages in advance - to create PyPI mirror - to clone required git repos in advance and just sync when testing From my experience the first one will contribute most to save time. Thanks, Akihiro (2014/02/05 10:24), Franck Yelles wrote: Hello, I was wondering how everyone was doing 3rd party testing at the moment when it comes to the process. It takes me around 10 minutes for me to do a +1 or -1. my flow is the following: (I only use Jenkins for listening to the feed) 1) a job is triggered from Jenkins. 2) a VM is booted 3) the devstack repo is clone 4) the patch is applied 5) stack.sh is run (longest time is here) 6) the test are run 7) the result is posted 8) the VM is destroyed I am looking for ways to speed up the process. I was thinking of keeping the stack.sh up; and follow this 1) Shutdown the affected component (neutron, etc..) 2) apply the patch 3) restart the component 4) run the test 5) post the result 6) shutdown the affected component 7) remove the patch 8) restart the component What are you thoughts ? Ideally I would like to achieve a sub 3 minutes. Thanks, Franck ___ 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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron]Contributing code to Neutron (ML2)
Hi Akihiro-
What kind of third party testing is required?
I have written the driver, unit test case and checked the driver with tempest
testing.
Do I need to check with any other third party testing?
Kindly help me in this regard.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
-Original Message-
From: Akihiro Motoki [mailto:mot...@da.jp.nec.com]
Sent: Friday, January 24, 2014 6:41 PM
To: openstack-dev@lists.openstack.org
Cc: kmest...@cisco.com
Subject: Re: [openstack-dev] [Neutron]Contributing code to Neutron (ML2)
Hi Trinath,
Jenkins is not directly related to proposing a new code.
The process to contribute the code is described in the links Andreas pointed.
There is no difference even if you are writing a new ML2 mech driver.
In addition to the above, Neutron now requires a third party testing for all
new/existing plugins and drivers [1].
Are you talking about third party testing for your ML2 mechanism driver when
you say Jenkins?
Both two things can be done in parallel, but you need to make your third party
testing ready before merging your code into the master repository.
[1] http://lists.openstack.org/pipermail/openstack-dev/2013-November/019219.html
Thanks,
Akihiro
(2014/01/24 21:42), trinath.soman...@freescale.com wrote:
Hi Andreas -
Thanks you for the reply.. It helped me understand the ground work
required.
But then, I'm writing a new Mechanism driver (FSL SDN Mechanism
driver) for ML2.
For submitting new file sets, can I go with GIT or require Jenkins for
the adding the new code for review.
Kindly help me in this regard.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
-Original Message-
From: Andreas Jaeger [mailto:a...@suse.com]
Sent: Friday, January 24, 2014 4:54 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Kyle Mestery (kmestery)
Subject: Re: [openstack-dev] [Neutron]Contributing code to Neutron
(ML2)
On 01/24/2014 12:10 PM, trinath.soman...@freescale.com wrote:
Hi-
Need support for ways to contribute code to Neutron regarding the ML2
Mechanism drivers.
I have installed Jenkins and created account in github and launchpad.
Kindly guide me on
[1] How to configure Jenkins to submit the code for review?
[2] What is the process involved in pushing the code base to the main
stream for icehouse release?
Kindly please help me understand the same..
Please read this wiki page completely, it explains the workflow we use.
https://wiki.openstack.org/wiki/GerritWorkflow
Please also read the general intro at
https://wiki.openstack.org/wiki/HowToContribute
Btw. for submitting patches, you do not need a local Jenkins running,
Welcome to OpenStack, Kyle!
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272
A126
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron-ML2] Unit testing ML2 Mechanism driver
Hi-
While running unit test case for test the ML2 mechanism driver, I have got
this error.
Command: tox -epy27 --
neutron.tests.unit.ml2.drivers.test_fslsdn_mech.TestFslSdnMechanismDriver.test_create_network_postcommit
Error output:
...
...
byte-compiling
/root/neutron_icehouse/neutron-2014.1.b1/.tox/py27/lib/python2.7/site-packages/neutron/context.py
to context.pyc
running install_data
error: can't copy 'etc/neutron/plugins/metaplugin/metaplugin.ini': doesn't
exist or not a regular file
Cleaning up...
Command /root/neutron_icehouse/neutron-2014.1.b1/.tox/py27/bin/python2.7 -c
import
setuptools;__file__='/tmp/pip-qoHPZO-build/setup.py';exec(compile(open(__file__).read().replace('\r\n',
'\n'), __file__, 'exec')) install --record
/tmp/pip-9CF9eS-record/install-record.txt --single-version-externally-managed
--install-headers
/root/neutron_icehouse/neutron-2014.1.b1/.tox/py27/include/site/python2.7
failed with error code 1 in /tmp/pip-qoHPZO-build
Storing complete log in /root/.pip/pip.log
__
summary
__
ERROR: py27: InvocationError:
/root/neutron_icehouse/neutron-2014.1.b1/.tox/py27/bin/pip install --pre
/root/neutron_icehouse/neutron-2014.1.b1/.tox/dist/neutron-2014.1.b1.zip -U
--no-deps (see
/root/neutron_icehouse/neutron-2014.1.b1/.tox/py27/log/py27-7.log)
From the above error, metaplugin.ini do exists and is readable. But here its
taken as doesn't exists.
Kindly help me troubleshoot the issue.
--
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]Contributing code to Neutron (ML2)
Hi Andreas -
Thanks you for the reply.. It helped me understand the ground work required.
But then, I'm writing a new Mechanism driver (FSL SDN Mechanism driver) for ML2.
For submitting new file sets, can I go with GIT or require Jenkins for the
adding the new code for review.
Kindly help me in this regard.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
-Original Message-
From: Andreas Jaeger [mailto:a...@suse.com]
Sent: Friday, January 24, 2014 4:54 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Kyle Mestery (kmestery)
Subject: Re: [openstack-dev] [Neutron]Contributing code to Neutron (ML2)
On 01/24/2014 12:10 PM, trinath.soman...@freescale.com wrote:
Hi-
Need support for ways to contribute code to Neutron regarding the ML2
Mechanism drivers.
I have installed Jenkins and created account in github and launchpad.
Kindly guide me on
[1] How to configure Jenkins to submit the code for review?
[2] What is the process involved in pushing the code base to the main
stream for icehouse release?
Kindly please help me understand the same..
Please read this wiki page completely, it explains the workflow we use.
https://wiki.openstack.org/wiki/GerritWorkflow
Please also read the general intro at
https://wiki.openstack.org/wiki/HowToContribute
Btw. for submitting patches, you do not need a local Jenkins running,
Welcome to OpenStack, Kyle!
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Tempest Testcases for ML2 Mechanism drivers - Help
Hi - With respect to writing test cases with Tempest for Neutron, I have a Freescale Mechanism Driver which support a Cloud Resource Discovery (CRD) Service . The complete data flow is show below. [cid:image001.png@01CF0BA3.7DB6CAE0] The FSL Mechanism driver partly depends on ML2 Plug-in (_pre_commint and _post_commit definitions) and Partly depends on CRD Service (with CRD client calls in _post_commit definitions). I want to write Tempest test cases for the FSL Mechanism driver. Kindly please help me on how to write the Tempest test cases for these kind of mechanism drivers. Also, help me on how to submit the BP document, Code base and Test cases for review. Thanking you for the help. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 inline: image001.png___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] {opestack][Neutron - FWaaS] CLI Firewall-Policy-Update Bug
Hi -
I found this issue with FWaaS CLI commands.
When I issue the command,
$ neutron firewall-policy-update dd2c7d33-2c36-4200-b1f8-daaa1ab202d5
--firewall-rules rule1
404-{u'NeutronError': {u'message': u'Firewall Rule r could not be found.',
u'type': u'FirewallRuleNotFound', u'detail': u''}}
With respect to the code, I see that the split is not happening based on the
white space character rather, the string is being split or parsed.
Is there a bug assigned to this and is that resolved ?
Kindly help me in this regard.
--
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] {opestack][Neutron - FWaaS] CLI Firewall-Policy-Update Bug
Hi-
Thanks a lot for the reply.
Can you kindly also add the help guideline in the FWaaS Documentation too..
This might be helpful.
Thanking you.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
From: Yongsheng Gong [mailto:gong...@unitedstack.com]
Sent: Wednesday, December 11, 2013 11:48 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] {opestack][Neutron - FWaaS] CLI
Firewall-Policy-Update Bug
try to use:
neutron firewall-policy-update dd2c7d33-2c36-4200-b1f8-daaa1ab202d5
--firewall-rules list=true rule1
On Wed, Dec 11, 2013 at 1:37 PM,
trinath.soman...@freescale.commailto:trinath.soman...@freescale.com
trinath.soman...@freescale.commailto:trinath.soman...@freescale.com wrote:
Hi -
I found this issue with FWaaS CLI commands.
When I issue the command,
$ neutron firewall-policy-update dd2c7d33-2c36-4200-b1f8-daaa1ab202d5
--firewall-rules rule1
404-{u'NeutronError': {u'message': u'Firewall Rule r could not be found.',
u'type': u'FirewallRuleNotFound', u'detail': u''}}
With respect to the code, I see that the split is not happening based on the
white space character rather, the string is being split or parsed.
Is there a bug assigned to this and is that resolved ?
Kindly help me in this regard.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.commailto:trinath.soman...@freescale.com | extn:
4048
___
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.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
