See everyone next year!
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Tue, Dec 16, 2014 at 05:12:31PM EST, Chris St. Pierre wrote:
> No, I'm looking to prevent images that are in use from being deleted. "In
> use" and "protected" are disjoint sets.
I have seen multiple cases of images (and snapshots) being deleted while
still in use in Nova, which leads to some v
Hi,
I've been bitten by a couple bugs lately on DevStack installs that have
been long lived. One is a built by Vagrant, and the other is bare metal
hardware.
https://bugs.launchpad.net/devstack/+bug/1395776
In this instance, a commit was made to rollback the introduction of
MariaDB in ubuntu, bu
Thanks Paul! Great pictures!
Sean M. Collins
From: Paul Michali (pcm) [p...@cisco.com]
Sent: Saturday, December 13, 2014 1:58 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [neutron] OT: Utah Mid-cycle sprint photos
I
Due to the mid-cycle, and other neutron meetings being cancelled, we will not
meet on the 9th
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
Based on today's meeting and previous discussions with Kyle, I've tried
to put down as much on paper about what I'd like to get done this
development cycle. I used some of the links that we swapped today in the
IRC meeting, but I know right now that I didn't get everything we talked
about.
Pl
Perhaps we should re-introduce the auto-expiration of patches, albeit on
a very leisurely timeframe. Before, it was like 1 week to expire a
patch, which was a bit aggressive. Perhaps we could auto-expire patches
that haven't been touched in 4 or 6 weeks, to expire patches that have
truly been aband
See everyone 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 Fri, Nov 07, 2014 at 02:16:52PM CET, Chris Dent wrote:
> What I hope to have at the end of this process is a nicely commented
> local.conf that I can post somewhere for people who want a similar
> thing.
Yes, and I hope my patchset will accomplish this, I just need to make
changes to it based o
We've been tagging things that are IPv6 related with "ipv6" - and we
monitor the following URL.
https://bugs.launchpad.net/neutron/+bugs?field.tag=ipv6
It has been very useful. Feel free to tag anything that looks IPv6
related as such and I'll triage.
--
Sean M. Collins
Looking forward to it, see you all then!
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I have reserved the 2:35 slot for Friday.
https://etherpad.openstack.org/p/neutron-kilo-meetup-slots
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
Like Atlanta, I will be at the summit. If there is interest, I can
schedule a time to talk about the QoS API extension.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/l
Hi,
I am currently working on my Neutron docs for DevStack[1], and realized
that there is some common pieces between provider networking API
extension and the l3 networking API extension.
In both cases, the administrator is directed to manually create a bridge
device and add the physical interfac
I look forward to seeing everyone in Paris!
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
With some xargs, sed, and pandoc - I now present to you the first
attempt at converting the DevStack docs to RST, and making the doc build
look similar to other projects.
https://review.openstack.org/130241
It is extremely rough, I basically ran everything through Pandoc and
cleaned up any errors
On Tue, Oct 21, 2014 at 11:59:12AM EDT, Monty Taylor wrote:
> On 10/21/2014 10:37 AM, Collins, Sean wrote:
> > I do see mentions of gh-pages in the build_docs.sh script - is
> > devstack.org redirect to GitHub?
> >
>
> Nope - it used to be. It's now buil
On Tue, Oct 21, 2014 at 11:33:44AM EDT, Dean Troyer wrote:
> On Tue, Oct 21, 2014 at 9:58 AM, Collins, Sean <
> sean_colli...@cable.comcast.com> wrote:
>
> > Looking at the current docs, they are all currently in raw HTML, and I
> > was hoping that it would be possib
I do see mentions of gh-pages in the build_docs.sh script - is
devstack.org redirect to GitHub?
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
I have a lot of documentation around DevStack and some configurations
that I run for a multi-node lab, that uses Neutron and IPv6. I would
love to contribute to them, but they are currently in Markdown format.
Looking at the current docs, they are all currently in raw HTML, and I
was hoping t
Hi,
I am seeing some patches in review that are adding skips to unit tests in the
Open Contrail plugin. If we can, please imitate the work that Kevin Benton did
in the One Convergence plugin and have your plugin skip tests that have "v6" in
the name, if your plugin does not support IPv6.
I hav
On Fri, Oct 03, 2014 at 02:58:36PM EDT, Henry Gessau wrote:
> There are some fixes for IPv6 bugs that unfortunately missed the RC1 cut.
> These bugs are quite important for IPv6 users and therefore I would like to
> lobby for getting them into a possible RC2 of Neutron Juno.
Henry and I spoke abou
Any objection? We need to move the time since the main meeting conflicts
with our current time slot.
Discussion from today's meeting:
http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-09-02-13.59.log.html
--
Sean M. Collins
_
Hi,
The amount of tests that we are having to add skips to for the One Convergence
plugin has grown quite a bit lately.
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/unit/oneconvergence/test_nvsd_plugin.py#n58
This is the only plugin that inherits from the NeutronDbPluginV2
Hi,
The QoS API extension has lived in Gerrit/been in review for about a
year. It's gone through revisions, summit design sessions, and for a
little while, a subteam.
I would like to request incubation in the upcoming incubator, so that
the code will have a more permanent "home" where we can coll
On Wed, Aug 13, 2014 at 03:28:34PM EDT, Kevin Benton wrote:
> Maybe the ipv6 subteam meeting could alternate as well...
OK, I can bring it up in the IRC meeting. I know our current time is
early for US PST and very late for Asia, so maybe we can find a time
that gives them a break :)
--
Sean M.
On Wed, Aug 13, 2014 at 10:05:26AM EDT, Kyle Mestery wrote:
> Tuesday 1400UTC
How do we want to handle the overlap with the IPv6 subteam meeting?
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack
On Tue, Aug 05, 2014 at 12:50:45PM EDT, Monty Taylor wrote:
> However, I think the cost to providing that path far outweighs
> the benefit in the face of other things on our plate.
Perhaps those large operators that are hoping for a
Nova-Network->Neutron zero-downtime live migration, could dedicat
On Wed, Jul 30, 2014 at 06:18:53PM EDT, Doug Wiegley wrote:
> Can we just have meeting-bot post the minutes, if we want a summary of
> each meeting? Or perhaps send that to a different DL, so it doesn¹t hit
> -dev?
>
> Doug
I agree, automation would be the best way. I did it for a while by hand
On Tue, Jul 29, 2014 at 04:40:33AM EDT, Nir Yechiel wrote:
> Now with the Juno efforts to provide IPv6 support and some features (provider
> networks SLAAC, RADVD) already merged, is there any plan/patch to revert this
> Icehouse change [1] and make the 'ra_mode' and 'ipv6_address_mode' consumabl
On Wed, Jul 23, 2014 at 12:06:06AM EDT, Xu Han Peng wrote:
> I would like to request one Juno Spec freeze exception for "Support Stateful
> and Stateless DHCPv6 by dnsmasq" BP.
>
> This BP is an important part if IPv6 support in Juno. Router advertisement
> support by RADVD has been merged and thi
On Wed, Jul 23, 2014 at 11:19:13AM EDT, Luke Gorrie wrote:
> Tail-f NCS: I want to keep this feature well maintained and compliant with
> all the rules. I am the person who wrote this driver originally, I have
> been the responsible person for 90% of its lifetime, I am the person who
> setup the cu
From: Luke Gorrie mailto:l...@snabb.co>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, July 21, 2014 3:22 PM
To: OpenStack Development Mailing List
mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-de
On Mon, Jul 07, 2014 at 03:29:31PM EDT, Scott Moser wrote:
> > I think it's also important to realize that the metadata service isn't
> > OpenStack invented, it's an AWS API. Which means I don't think we really
>
> Thats incorrect. The metadata service that lives at
> http://169.254.169.254/
>
On Tue, Jul 08, 2014 at 02:15:58AM EDT, Kevin Benton wrote:
> I think at this point the discussion is mostly contained in the review for
> the spec[1] so I don't see a particular need to continue the IRC meeting.
>
>
> 1. https://review.openstack.org/#/c/88599/
I agree, and I have removed the m
On Mon, Jul 07, 2014 at 11:01:52PM PDT, Kevin Benton wrote:
> I can lead it, but I'm not sure if there is anything new to discuss since
> the QoS spec is still under review.
> Did you have any specific agenda items that you wanted to cover?
Ah. The QoS IRC meeting will also need to be chaired in m
Hi,
I am currently at a book sprint and will probably not be able to run the
meeting, if someone could volunteer to chair the meeting and run it,
that would be great.
Any takers?
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.op
Hi,
Anthony Veiga and I are currently working on migrating a lab environment
from Neutron Havana w/ OVS plugin to Icehouse w/ ML2 plugin and ran into
a bug[0].
Now the patch that adds the ml2 migration[1] mentions that it was tested
without any data, and that it is waiting on grenade support for
You can use the provider networking API extension for Neutron, in order
to utilize non-openstack L3 hardware.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/opensta
Hi, I have posted a preliminary agenda for today. I will be unable to
attend the meeting, Kevin Benton will be chairing the meeting today.
Please do add items to the agenda that you wish to discuss!
https://wiki.openstack.org/wiki/Meetings/NeutronQoS
--
Sean M. Collins
_
On Tue, Jun 17, 2014 at 10:10:26AM EDT, Shixiong Shang wrote:
> Trying to join the weekly meeting, but my IRC client kept complaining…Is it
> just me?
If you have problems, you can always use the web client:
http://webchat.freenode.net/
--
Sean M. Collins
_
I think we need to pick either one or the other. We currently have two places
where debugging is documented, the OpenStack wiki and in the Neutron tree
http://git.openstack.org/cgit/openstack/neutron/tree/TESTING.rst#n143
Sean M. Collins
From: Gal Sagie [gsa...@v
On Wed, Jun 11, 2014 at 09:58:14AM EDT, Robert Li (baoli) wrote:
> Hi,
>
> With the right version of
> dnsmasq (I’m using 2.68) in use, it will be successfully launched and
> handing out both ipv6 and ipv4 addresses. An example of dnsmasq
> instance is shown as below:
We should consider bumping t
On Wed, Jun 11, 2014 at 09:07:59AM EDT, Robert Li (baoli) wrote:
> Hi,
>
> I was mistakenly reusing the Blueprint
> https://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-radvd-ra to draft
> up the ipv6 RA support in neutron. I apologize for any confusion that this
> may have caused. To co
Cool,
Thanks.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Tue, Jun 10, 2014 at 10:33:49AM EDT, Luke Gorrie wrote:
> Howdy!
>
> Here is a successful Sandbox test from right now:
> https://review.openstack.org/#/c/99061/. I don't immediately see how to
> list all historical sandbox tests. (The previous ones are from before the
> Summit anyway.)
One of
http://eavesdrop.openstack.org/meetings/neutron_qos/2014/neutron_qos.2014-05-27-18.01.html
See everyone next week!
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/op
http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-05-27-14.01.html
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I'm going to bump this thread based on some of the discussions we had
today during the IRC meeting.
I also added a comment to a review on the tempest side after our
discussion (I made some adjustments to my comment for context and
clarification)
https://review.openstack.org/#/c/93400/
>> The onl
On Thu, May 22, 2014 at 06:51:56PM EDT, Itsuro ODA wrote:
> BTW, where do you begin a discussion ? I thought you countinue
> work in Icehose. Or do you argue from the beginning of the API
> definition ?
My plan is to introduce the REST API and the work that has already been
done, and help bring
On Wed, May 21, 2014 at 04:47:48PM EDT, Kevin Benton wrote:
> +1
Looks like we have consensus - I'll conduct a meeting today (Tue May
27th 2014) at 1800 UTC.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lis
Here's the documentation on how to configure DevStack
http://devstack.org/configuration.html
From: Sachi Gupta mailto:sachi.gu...@tcs.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, May 26, 2014 3:37 AM
To
On Wed, May 21, 2014 at 10:47:16PM EDT, Mandeep Dhami wrote:
> The update from Sean seem to suggest to me that we needed blueprints only
> if the public API changes, and not for design changes that are internal to
> neutron.
There was no statement in my e-mail that made that
suggestion. My e-mail
(Edited the subject since a lot of people filter based on the subject
line)
I would also be interested in reserved IPs - since we do not deploy the
layer 3 agent and use the provider networking extension and a hardware
router.
On Wed, May 21, 2014 at 03:46:53PM EDT, Sławek Kapłoński wrote:
> Hell
Hi,
The session that we had on the Quality of Service API extension was well
attended - I would like to keep the momentum going by proposing a weekly
IRC meeting.
How does Tuesdays at 1800 UTC in #openstack-meeting-alt sound?
--
Sean M. Collins
___
Op
On Tue, May 20, 2014 at 05:18:57PM EDT, Mandeep Dhami wrote:
> Renewing the thread, is there a blueprint for this refactoring effort?
>
> In the email thread till now, we have just had an etherpad link. I would
> like to get more deeply involved in design/implementation and review of
> these chang
On Tue, May 20, 2014 at 06:19:44PM EDT, Paul Czarkowski wrote:
> Has anyone had any success with running devstack and neutron in a vagrant
> machine where the floating Ips are accessible from outside of the vagrant box
> ( I.e. From the host ).
>
> I’ve spent a few hours trying to get it working
http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-05-20-14.00.html
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi everyone,
I've been looking at two reviews that Ann Kamyshnikova has proposed
https://review.openstack.org/#/c/82073/
https://review.openstack.org/#/c/80518/
I think the changes are fundamentally a Good Thing™ - they appear to reduce
the differences between the database models and their co
On Mon, May 19, 2014 at 05:00:26PM EDT, Henrique Truta wrote:
> Controller localrc: http://paste.openstack.org/show/80953/
>
> Compute node localrc: http://paste.openstack.org/show/80955/
These look backwards. The first pastebin link has no enabled services,
while the pastebin you say is the comp
On Mon, May 19, 2014 at 04:44:05PM EDT, Henrique Truta wrote:
> Hello, everyone!
>
> I've been trying to install a multinode Devstack on CentOS. I ran stack.sh
> on both controller and compute node. The controller works fine, but the
> compute node is not working properly as a host. Looks like it'
https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_May_20th
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Etherpad link:
https://etherpad.openstack.org/p/qos-api-network-pod
From: , Sean Collins
mailto:sean_colli...@cable.comcast.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, May 14, 2014 12:01 PM
To: "OpenS
Be there or be square :)
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Thu, May 08, 2014 at 03:02:28PM EDT, Stephen Wong wrote:
> Hi Sean,
>
> Perfect (I assume it is local time, i.e. 2:30pm EDT).
>
> And I also assume this will be at the Neutron pod?
>
Correct on both counts. See everyone soon!
--
Sean M. Collins
_
On Tue, May 06, 2014 at 07:17:26PM EDT, Mohammad Banikazemi wrote:
>
> There are networking talks in the general session in the afternoon on
> Thursday including the talk on Network Policies from 1:30 to 2:10pm.
> Anything after that is ok with me.
How does 2:30PM on Thursday sound to everyone?
On Tue, May 06, 2014 at 03:04:09PM EDT, Mohammad Banikazemi wrote:
>
> +1.
>
> Please announce a date/time here so we can perhaps avoid any conflicts with
> others who plan to use the networking pod.
>
> Best,
Agreed. So - Thursday seems to be a pretty light in the afternoon -
there are only de
For those attending, to discuss the QoS API current status?
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
We will not be meeting tomorrow, May 6th 2014, since the summit
is 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 Wed, Apr 30, 2014 at 06:10:20PM EDT, Martinx - ジェームズ wrote:
> Since IPv6 is all public, don't you think that we (might) need a new
> blueprint for IPv6-Only, like just "dns-resolution"?
Yes - I think IPv6 only Neutron is at least one separate blueprint,
possibly more. Robert Li is currently wor
Count me in!
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Just a couple quick notes, since I've been pinged off-list. The summit
proposal for the QoS API was rejected due to time constraints, but I'm
hoping that we can still meet in Atlanta and discuss the next steps.
In the meantime, I have created a draft spec in neutron-specs, but it's
mostly just a c
From: Kyle Mestery mailto:mest...@noironetworks.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, April 28, 2014 3:08 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@li
Have you considered filing a blueprint for this? It'd be good to keep
this on the radar.
https://wiki.openstack.org/wiki/Blueprints#Neutron
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/
You know the drill - fill in anything you wish to discuss.
https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_April_21st
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.or
All,
We have a couple IPv6 design summit sessions that have been registered,
and at least one of them is in a pre-approved state:
http://summit.openstack.org/cfp/details/21
We'll have at least 40 minutes to discuss a roadmap for IPv6 in the
coming Juno cycle.
I have created an etherpad, and wou
Nice!! nwdiag would make things really easy.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Tue, Apr 15, 2014 at 04:30:53PM EDT, Joe Gordon wrote:
> One of my biggest issues with running devstack in vagrant is how slow
> it is
The vagrant_devstack project (github.com/bcwaldon/vagrant_devstack) has
some Chef recipes to cache pip and apt - so it's only the first run that
is slow, and re
I just want to quickly caution about having these meetings in person
since not everyone will be able to attend - the summits are probably
where we will have the most Neutron developers able to attend.
It's not that I oppose the idea - but there must be adequate facilities
for people to attend and
Meeting minutes:
http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-04-15-14.00.html
See you next week!
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mai
Feel free to update the agenda with items for discussion
https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_April_15th
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/c
Hi,
Sorry for the late response. Currently I am working on just getting
support for a single QoS policy on a network or port merged, before we
get into more complex operations.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.opens
On Fri, Apr 11, 2014 at 11:09:18PM EDT, Thomas Goirand wrote:
> On 04/11/2014 10:52 PM, Collins, Sean wrote:
> > Many of those patches are stale - please join us in the subteam IRC
> > meeting if you wish to coordinate development of IPv6 features, so that
> > we can focus
On Fri, Apr 11, 2014 at 02:24:10PM EDT, Sean Dague wrote:
> Honestly, multi provisioner support is something I think shouldn't be
> done.
Agreed - in addition let's keep this in perspective - we're just adding
a little bit of glue to prep the VM for the running of DevStack, which
does the heavy l
> Maybe it would be good to get an ad-hoc IRC meeting together to figure
> out what the must have features are that inspired everyone to write
> these. If we can come up with a way to overlap those all sanely, moving
> to stackforge and doing this via gerrit would be something I'd be into.
>
>
Many of those patches are stale - please join us in the subteam IRC
meeting if you wish to coordinate development of IPv6 features, so that
we can focus on updating them and getting them merged. At this point
simply applying them to the Icehouse tree is not enough.
--
Sean M. Collins
Hi,
I've noticed a proliferation of Vagrant projects that are popping up, is
there any interest from other authors in trying to consolidate?
https://github.com/bcwaldon/vagrant_devstack
https://github.com/sdague/devstack-vagrant
http://openstack.prov12n.com/how-to-make-a-lot-of-devstack-with-va
Hi,
I've added a section for tomorrow's agenda, please do add topics that
you'd like to discuss.
https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_April_8th
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.
Hi Martin,
I previously posted to the mailing list with some information about our
IPv6 lab environment and devstack setup.
http://lists.openstack.org/pipermail/openstack-dev/2014-February/026589.html
Keep in mind that code differs from what was eventually merged in
upstream, so I would ask for
I am currently working on a patch that allows upstream RAs and SLAAC
configuration. Currently testing it in devstack - it's based on chunks
of patchset 33 of this review that were skipped when Mark McClain
committed patchset 34.
https://review.openstack.org/#/c/56184/
Xu Han and Dazhao - do I hav
Sorry - not resolved: being tracked.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Thu, Apr 03, 2014 at 02:28:39AM EDT, Sebastian Herzberg wrote:
> Concerning dnsmasq: There is still no 2.66 version in the repos for Ubuntu
> 12.04. You always need to remove 2.59 and dpkg a newer version into it.
>
I think it was resolved with this bug:
https://bugs.launchpad.net/neutron/+b
On Wed, Apr 02, 2014 at 11:40:39AM EDT, Martinx - ジェームズ wrote:
> But, can this current "neutron-ipv6.patch" at least, be used to enable
> Neutron IPv6 with RA (--ipv6_ra_mode slaac --ipv6_address_mode slaac) ?
No, because even if you solved all the merge conflicts, the
tests were not passing in t
On Wed, Apr 02, 2014 at 11:13:32AM EDT, Martinx - ジェームズ wrote:
> Awesome guys! I'll do it!
OK - so keep an eye on:
https://review.openstack.org/#/c/70649/
Once it is rebased to solve the merge conflicts, and all the tests pass,
then perhaps we can look into any of this backporting or PPA busines
The patch that enables the new attribute support in dnsmasq still has a
lot of work that needs to be done. Once that patch is ready, I suppose we
can ask for it to be backported to Icehouse.
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-d
During the review[0] of the patch that only allows RAs from known
addresses, Robert Li brought up a bug in Neutron, where a
IPv6 Subnet could be created, with a link local address for the gateway,
that would fail to create the Neutron router because the IP address that
the router's port would be as
On Fri, Mar 21, 2014 at 08:35:05PM EDT, Rajdeep Dua wrote:
> Sean,
> If you can point me to the project file in github which needs to be modified
> , i will include these docs
>
> Thanks
> Rajdeep
I imagine inside the openstack-manuals git repo
https://github.com/openstack/openstack-manuals
Po
Hi,
Anthony Veiga and I did a small bit of whiteboarding this morning to
sketch out what a prefix delegation would look like in the Neutron API.
https://wiki.openstack.org/wiki/Neutron/IPv6/PrefixDelegation
--
Sean M. Collins
___
OpenStack-dev mailing
Hi,
I just read through some of the design docs that were linked to the DVR
blueprints - and realized we probably have a ton of Neutron developer
documentation and architecture stuff in Google docs.
Should we try and gather them all up and place links to them in
the Developer Documentation - or p
I put together another review that starts to document the HTTP API layer
and structure.
https://review.openstack.org/#/c/79675/
I think it's pretty dense - there's a ton of terminology and concepts
about WSGI and python that I sort of skim over - it's probably not
newbie friendly just yet - comme
1 - 100 of 187 matches
Mail list logo
