On Mon, Mar 10, 2014 at 11:13:47PM EDT, Yuzhou (C) wrote:
> Hi stackers,
>
> The progress of the bp about ml2-qos is code review for long time.
> Why didn't the implementation of qos commit the neutron master ?
For a while, I did not believe that this API extension would ever
get merged, s
It starts at 10AM EST, due to daylight savings. See you in a couple minutes
Sean M. Collins
From: Shixiong Shang [sparkofwisdom.cl...@gmail.com]
Sent: Tuesday, March 11, 2014 9:15 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [opensta
development. See
the IPv6 section of the wiki for a full list.
Sean M. Collins
From: Martinx - ジェームズ [thiagocmarti...@gmail.com]
Sent: Saturday, March 08, 2014 8:01 PM
To: Collins, Sean
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re
Also, I posted an e-mail to the mailing list that discusses a branch of Neutron
and Nova, that can be used with DevStack, which contains patches for using IPv6
with non-openstack gateways and routers - it contains patches that we have
currently under review.
http://lists.openstack.org/pipermail
Hi,
We have a number of patches that are in in review for IPv6 support in Neutron.
https://wiki.openstack.org/wiki/Neutron/IPv6
Currently, we have two patches that have landed in Neutron and Nova that allows
IPv6 to function correctly, when you have an external gateway/router set up and
sendin
On Fri, Mar 07, 2014 at 02:20:24PM EST, Miguel Angel Ajo wrote:
>
> Good work on the documentation, it's something that will really help
> new neutron developers.
>
Thank you everyone! I am very happy!
I'll start cranking out some patchsets to address some of the comments
that Henry Gessau, Aki
Hi,
I know everyone is very busy working on the I-3 release, but I wanted
solicit feedback on my developer documentation review.
https://review.openstack.org/#/c/72428/
Currently, we have a couple +1's and a +2 from Nachi - Akihirio Motoki
and Henry Gessau brought up valid points about the TESTI
Hi Robert,
I'm reaching out to you off-list for this:
On Wed, Mar 05, 2014 at 09:48:46AM EST, Robert Li (baoli) wrote:
> As a result of this change, it will end up having two LLA addresses in the
> router's qr interface. It would have made more sense if the LLA will be
> replacing the qr interfac
On Mon, Jan 13, 2014 at 05:16:16PM EST, Mark McClain wrote:
> I’d rather us explicitly skip the tests if the module is not available.
>
> mark
Just wanted to close the loop on this - thanks to Darragh O'Reilly,
who submitted https://review.openstack.org/#/c/66609/, which removes
the Pyudev depend
On Tue, Mar 04, 2014 at 02:08:03PM EST, Robert Li (baoli) wrote:
> Hi Xu Han & Sean,
>
> Is this code going to be committed as it is? Based on this morning's
> discussion, I thought that the IP address used to install the RA rule
> comes from the qr-xxx interface's LLA address. I think that I'm co
On Tue, Mar 04, 2014 at 12:01:00PM -0500, Brian Haley wrote:
> On 03/03/2014 11:18 AM, Collins, Sean wrote:
> > On Mon, Mar 03, 2014 at 09:39:42PM +0800, Xuhan Peng wrote:
> >> Currently, only security group rule direction, protocol, ethertype and port
> >> range are su
On Tue, Mar 04, 2014 at 04:06:02PM +, Robert Li (baoli) wrote:
> Hi Sean,
>
> I just added the ipv6-prefix-delegation BP that can be found using the
> search link on the ipv6 wiki. More details about it will be added once I
> find time.
Perfect - we'll probably want to do a session at the sum
Hi All,
We've got a lot of work in progress, so if you
have a blueprint or bug that you are working on (or know about),
let's make sure that we keep track of them. Ideally, for bugs, add the
"ipv6" tag
https://bugs.launchpad.net/neutron/+bugs?field.tag=ipv6
For blueprints and code reviews, pleas
On Mon, Mar 03, 2014 at 10:51:59AM +0800, Xuhan Peng wrote:
> Abishek,
>
> The two attributes are editable if you look at Sean's patch
> https://review.openstack.org/#/c/52983/27/neutron/api/v2/attributes.py. The
> "allow_put" is set to be "True" for these two attributes.
>
> Xuhan
+1 - the attr
On Mon, Mar 03, 2014 at 09:39:42PM +0800, Xuhan Peng wrote:
> Currently, only security group rule direction, protocol, ethertype and port
> range are supported by neutron security group rule data structure. To allow
If I am not mistaken, I believe that when you use the ICMP protocol
type, you can
Shixiong Shang and I ran into this problem with Tox today while we were
pair programming, and I've also seen similar barfs on my DevStack lab
boxes - it's quite a mess. Frankly I've moved to using nosetests as a
workaround, and have added it to the developer docs.
We really do need to figure out
Make sure that you also log in, or have your username and password handy before
you redeem it.
If you click a link to send a password reset, you'll lose your session, and the
invite code is a one-time use – I had to dig through my history to get the URL
back, since the back button did not work
Sorry - fired off this e-mail without looking too closely at your log
output - I just saw the escape characters and the long lines from tox
and it reminded me of the last discussion we had about it. It's
probably not the same error as I was describing.
That's the tough thing that I strongly dislik
Yes - it's a problem with non-Linux platforms not being able to install
pyudev, which is a requirement for the linuxbridge plugin, which makes
testr barf when it hits an ImportError.
http://lists.openstack.org/pipermail/openstack-dev/2014-January/023268.html
In the past, I've run tox -e py26 as a
On Thu, Feb 20, 2014 at 12:53:51AM +, Vilobh Meshram wrote:
> Hello OpenStack Dev,
>
> We wanted to have your input on how different companies/organizations, using
> Openstack, are monitoring IP availability as this can be useful to track the
> used IP’s and total number of IP’s.
A while ag
No surprise, the code is quite stale, so bear with me while I debug the
failures.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
I'd like to apologize for the long delays in updating the QoS API
patch sets - I am working on cleaning them up so that they are ready for
review.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.open
On Sun, Feb 09, 2014 at 09:24:48PM -0800, Rajdeep Dua wrote:
> Yes, We would be interested in doing that.
> Please let me know which is the right group/ team for this?
I believe you would add your examples somewhere in netconn-api
git://git.openstack.org/openstack/netconn-api
Then you would add
-guide.cfapps.io/content/neutron.html
You can find get the source here https://github.com/rajdeepd/openstack-samples
Thanks
Rajdeep
On Sunday, February 9, 2014 12:57 AM, "Collins, Sean"
wrote:
Hi,
I was writing a small script yesterday to parse a list of IP blocks and
create security groups
Ah, so they fixed the issue the blog post by AppNeta[0] brought up. Very
Cool!
http://www.appneta.com/blog/s3-list-get-bucket-default/
https://github.com/boto/boto/issues/2078
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.opens
Hi,
I was writing a small script yesterday to parse a list of IP blocks and
create security groups and rules, by using python-neutronclient.
To be honest, it was very difficult - even though I have actually
written extensions to Python-Neutronclient for the QoS API.
For those that are trying to
Hi,
During our last meeting, there was an action item to share the Devstack
configuration that we have in the lab. Anthony Veiga, Paul Richie,
and other members of the infrastructure team did the majority of
the work involved in setting up the lab, while I was given the easier
task of just modifyi
On Tue, Feb 04, 2014 at 07:52:22AM -0600, Anne Gentle wrote:
> Currently the docs contributor sign the same CLA as code contributors. I'd
> encourage you to use the docs to really explain not just link to slide
> decks. There's a better chance of maintenance over time.
Agreed - I plan on writing u
Hi,
I've posted a preliminary agenda for the upcoming IPv6 meeting. See everyone
soon!
https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_Feb_4th
---
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.or
Hi,
Some Neutron developers have some really great slides from some of the summits,
and I'd like to link them in the documentation I am building as part of a
developer doc blueprint,
with proper attribution.
https://blueprints.launchpad.net/neutron/+spec/developer-documentation
I'm hoping to ad
On Sat, Feb 01, 2014 at 01:18:09AM -0500, Shixiong Shang wrote:
> In other words, I can retrieve the values by:
>
> subnet.ipv6_ra_mode
> subnet.ipv6_address_mode
>
> Is that correct? Would you please confirm?
Yes - that is the intent.
I just have to fix an issue with the DB column definitions,
I just pushed a new patch that adds the two new attributes to Subnets.
https://review.openstack.org/#/c/52983/
It's a very rough draft - but I wanted to get it out the door so people
had sufficient time to take a look, so we can discuss at the next IRC
meeting.
--
Sean M. Collins
__
OK - any suggestions for the names of API attributes?
The PDF[0] shared does not specify the names of the attributes, so I had
two ideas for the names of the two new attributes being added to the
Subnet resource:
Either prefix them with "ipv6"
* ipv6_ra_mode
* ipv6_address_mode
Or don't prefix
I don't know if it's reasonable to expect a deployment of OpenStack that
has an *external* DHCP server. It's certainly hard to imagine how you'd
get the Neutron API and an external DHCP server to agree on an IP
assignment, since OpenStack expects to be the source of truth.
--
Sean M. Collins
I don't see a second new attribute being proposed - I only see one new
one and the existing enable_dhcp attribute. Can we get a writeup of what
is being proposed?
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http:/
On Mon, Jan 13, 2014 at 07:32:29PM +0100, Ian Wells wrote:
> To fill others in, we've had discussions on the rest of the patch and
> Shixiong is working on it now, the current plan is:
>
> New subnet attribute ipv6_address_auto_config (not catchy, but because of
Hi, will this patch replace https:
16:04, Collins, Sean wrote:
> Can we get the -1 from Tail-F cleared from this review?
>
> https://review.openstack.org/#/c/56184/17
>
I've been trying to do this but it fails.
Possibly because it is 'Abandoned' ?
See below:
$ ssh -p 29418 ncsopenstack gerrit review
Can we get the -1 from Tail-F cleared from this review?
https://review.openstack.org/#/c/56184/17
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Wed, Jan 01, 2014 at 07:56:22PM -0800, Clark Boylan wrote:
> It looks like the problem is that there is a dependency on pyudev
> which only works properly on Linux. The neutron setup_hook does
> properly install pyudev on Linux (explains why the tests run in the
> gate), but would not work prope
Hi,
I posted a message to the mailing list[1] when I first began work on the
subnet mode keyword, asking if anyone had a suggestion about if it
should be an API extension or can be a change to the core API.
> I don't know if adding the "dhcp_mode" attribute to Subnets should be
> considered an AP
In #openstack-meeting
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
The 1500 UTC time conflicts with Marconi, although the time was not
listed on the Meetings wikipage.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I will make sure to add these items to the agenda.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
How should we handle existing -1's that have been posted?
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I think we've got consensus. See everyone tomorrow at 1500 UTC in
#openstack-meeting-alt
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/2014 08:36 PM, Collins, Sean wrote:
> +1 to this, there are IPv6 patches that have been -1'd by this system that I
> believe prevents them
> from being reviewed, since most people skip over changes that have a -1 from
> Jenkins jobs.
>
> I also attempted to Reach out mid D
3 at 12:24 PM, Joe Gordon
mailto:joe.gord...@gmail.com>> wrote:
On Mon, Dec 23, 2013 at 11:13 AM, Sean Dague
mailto:s...@dague.net>> wrote:
On 12/23/2013 12:10 PM, Collins, Sean wrote:
> On Sun, Dec 22, 2013 at 12:30:50PM +0100, Salvatore Orlando wrote:
>> I would suggest tha
Happy New Year!
Since we're still hashing out the logistics of changing our meeting
time, we'll meet at 2100 UTC - and hopefully transition to a new meeting
day and time by next week.
I have created a section in the wiki for today's agenda:
https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-
Looking at the calendar, our options for 1500 UTC require us to change
the day that we meet. The following days are available:
* Tuesdays
* Fridays
Thoughts?
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://li
> It looks like the problem is that there is a dependency on pyudev
> which only works properly on Linux. The neutron setup_hook does
> properly install pyudev on Linux (explains why the tests run in the
> gate), but would not work properly on windows or OS X. I assume folks
> are trying to run the
On Mon, Dec 23, 2013 at 02:13:59PM -0500, Sean Dague wrote:
> On 12/23/2013 12:10 PM, Collins, Sean wrote:
> I also think we need to have these systems prove themselves on
> reliability before they post votes back. A mis configured CI system can
> easily -1 the entire patch stream, an
Spoke too soon – I think 1500 UTC on Thursdays is already taken, we'd have to
change days.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
OK - if nobody has any objections, we'll start the new meetings up at
1500 UTC - that appears to be the time that everyone is OK with?
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
+1 for this - I've been seeing this error as well, when running
tox -e py27 from fresh clones - I've been using tox -e py26
as a workaround.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/c
See you all next week!
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Sun, Dec 22, 2013 at 12:30:50PM +0100, Salvatore Orlando wrote:
> I would suggest that external jobs should not vote until logs are publicly
> accessible, otherwise contributors would have no reason to understand where
> the negative vote came from.
+1
I've had Tail-F NCS Jenkins -1 some thing
Thoughts? I know we have people who are not able to attend at our
current time.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Minutes from the meeting:
http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-12-19-21.00.html
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listin
Perfect! Will you be at the IRC meeting to discuss these? I've added
them to the agenda in the hopes that we can discuss
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listi
On Wed, Dec 18, 2013 at 10:29:35PM -0500, Shixiong Shang wrote:
> It is up to Sean to make the call, but I would love to see IBM team in the
> meeting.
Agreed - If we can find a time that works for USA, Europe and
China that would be great.
How good/bad is 1500 UTC? I don't trust my math :)
Hi,
Agenda for today's meeting is pretty light - if you have something you'd
like to discuss please add it to the wiki page
https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_Dec_19_2013
I would also ask that when we conduct the meeting - we stick to the
agenda that has bee
On Tue, Dec 17, 2013 at 07:39:14PM +0100, Ian Wells wrote:
> 1. The patch ties Neutron's parameters specifically to dnsmasq. It would
> be, I think, impossible to reimplement this for isc-dhcpd, for instance.
While I agree in theory with this point - there are currently no
active blueprints to ad
Hi,
I have registered two blueprints, one in Nova and one in Neutron to make
it a VIF attribute that the libvirt driver in Nova will honor.
https://blueprints.launchpad.net/neutron/+spec/vif-attribute-for-hairpinning
https://blueprints.launchpad.net/nova/+spec/nova-hairpin-vif-attribute
--
Sea
The agenda for today is pretty light - if there is anything that people
would like to discuss, please feel free to add.
https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_Dec_12._2013
--
Sean M. Collins
___
OpenStack-dev mailing l
Hi,
We currently have a bug for IPv6 work, which is to disable hairpinning
on the bridge that Nova creates. By default, it is always turned on,
which prevents instances from configuring IPv6 SLAAC addresses
https://launchpad.net/bugs/1251235
https://review.openstack.org/#/c/56381/
Daniel Berran
> >
> > +1 for the meeting time. Any particular reason for voice over IRC?
> >
> We kind of decided that doing this over voice initially would be expedient,
> but I am fine with moving to IRC. If I don't hear objections, lets assume we
> will meet at 1700UTC Thursday on #openstack-meeting-alt.
Transcript:
http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-12-05-21.03.html
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-d
Agenda has been posted - look forward to speaking to you all soon.
https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mail
Thank you - that'll work great for the short term until Nachi's patch
lands.
We still need a +2 from another Nova dev for a patch that disables
hairpinning when Neutron is being used [1].
The patch to allow ICMPv6 into instances for SLAAC
just landed today[2]. So we're making progress.
[1] https
On Wed, Nov 27, 2013 at 09:29:16PM +0200, George Shuklin wrote:
> Why iptables, not internal openvswitch flow rules? Those rules allows to
> filter packets on L2-L4 headers and operates very fast. Is some
> iptables-only features used in ovs-agent?
I've seen a couple references floating around abo
Moving this from the Gerrit review about change #58186 [1], to the
mailing list for discussion.
Let's start making some blueprints under the ipv6-feature-parity
blueprint[2]. I've already registered a blueprint for the work
that I've been doing, to get provider networking with V6 running,
which li
On Tue, Nov 26, 2013 at 06:07:07PM +0800, Da Zhao Y Yu wrote:
> Sean, what about your progress? I saw your code change jekins still in
> failed status.
Hi,
I've been busy tracking down the IPv6 issue in our lab environment -
we were using the Hybrid OVS driver in our Nova.conf and that was
break
Great! Let's try and schedule a time for an IRC meeting that works for
everyone so we can discuss the patch. I'm happy to do the meeting on an
Asia friendly time, since it's hard to do the scheduled time at
2100UTC, and we'll just post the logs.
--
Sean M. Collins
Meeting minutes and the logs for the Neutron IPv6 meeting has been
posted.
We will not meet next week, due to the Thanksgiving holiday in the US.
Our next meeting will be Thursday Dec 5th - 2100 UTC, where we will
review the goals from this week's meeting and look to create actionable
items for I
I've put up a preliminary agenda for tomorrow's meeting. Please feel
free to add anything that comes to mind.
https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_Nov._21_2013
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenSta
Ah. Here's why.
diff --git a/neutron/tests/unit/openvswitch/test_ovs_qos.py
b/neutron/tests/unit/openvswitch/test_ovs_qos.py
index 3450b2c..8feaef4 100644
--- a/neutron/tests/unit/openvswitch/test_ovs_qos.py
+++ b/neutron/tests/unit/openvswitch/test_ovs_qos.py
@@ -32,6 +32,7 @@ class OpenvswitchQ
I fired up the tests in a virtual machine, and when you run the full
tox - it'll error out like Jenkins does, but when you run
just the one module of tests by itself, it passes.
http://paste.openstack.org/show/53159/
--
Sean M. Collins
___
OpenStack-de
+1 for more IPv6 functionality testing - we're tracking down some
problems with IPv6 security group rules not properly evaluating and
ending up hitting DROP statements, instead of letting the traffic into
the instance.
My goal is to start contributing IPv6 tempest tests to replicate what
we're se
On Wed, Nov 13, 2013 at 10:20:55AM -0500, Shixiong Shang wrote:
> Thanks a bunch for finalizing the time! Sorry for my ignorance….how do we
> usually run the meeting? On Webex or IRC channel?
IRC.
I'm not opposed to Webex (other teams have used it before) - but it
would involve more set-up. We'
I haven't heard any negative response to the proposed time,
so I'd like to put a stake in the ground and utilize that time slot.
We will have our first meeting on Nov 21st.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack
On Mon, Nov 11, 2013 at 01:16:43PM -0500, Shixiong Shang wrote:
> +1.
>
> We have great interest to run OpenStack over IPv6 and would love to be a
> part of the discussion.
Excellent - please see the thread I've made in OpenStack-Dev - we're
tossing out times for the IRC meeting, that works for e
As long as the -1's include a correction that can be copied
and pasted, I think they're OK.
I know I would be grateful if someone were to
proofread my work, if I had to document in a second-language.
--
Sean M. Collins
___
OpenStack-dev mailing list
Op
OK - how about Thursdays, 21:00 UTC?
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
I'm experiencing an issue where I run the unit tests on my local
machine and the unit tests pass, while on the Jenkins system they
fail with a very strange error.
2013-11-11 13:16:04.132 |
2013-11-11 13:16:04.132 | Traceback (most recent call last):
2013-11-11 13:16:04.132 | File
"/home/
How about scheduling an IRC meeting in close proximity to the other
Neutron meetings on Mondays?
* 20:00 to 21:00 UTC, before the Neutron meeting
OR
* 23:00 UTC - after the distributed virtual router meeting?
--
Sean M. Collins
___
OpenStack-dev mail
Cool!
I've put a placeholder on the meetings wiki page, until we can find a
time that works for everyone.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-
Hi,
Is there any interest in organizing a IPv6 sub-team, similar to how
there are sub-teams for FwaaS, VPNaas, ML2, etc?
--
Sean M. Collins
AIM: seanwdp
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
101 - 187 of 187 matches
Mail list logo
