+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.
+1 for
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
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
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
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
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
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
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
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
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'd
+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
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
___
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
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
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
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
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
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
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 about
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]
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
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
22 matches
Mail list logo
