[openstack-dev] [Neutron][IPv6] No weekly meeting until Jan 6th 2015
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
Re: [openstack-dev] [glance] Option to skip deleting images in use?
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 very, shall we say, interesting bugs and support problems. I do think that we should try and determine a way forward on this, they are indeed disjoint sets. Setting an image as protected is a proactive measure, we should try and figure out a way to keep tenants from shooting themselves in the foot if possible. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [DevStack] A grenade for DevStack?
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, but it does not appear that there was anything done to revert the change in existing deployments, so I had to go and fix by hand on the bare metal lab because I didn't want to waste a lot of time rebuilding the whole lab from scratch just to fix. I also got bit by this on my Vagrant node, but I nuked and paved to fix. https://bugs.launchpad.net/devstack/+bug/1402762 It'd be great to somehow make a long lived dsvm node and job where DevStack is continually deployed to it and restacked, to check for these kinds of errors? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] OT: Utah Mid-cycle sprint photos
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 put a link in the Etherpad, to some photos I took from the mid-cycle sprint in Utah. Here’s the direct link… http://media.michali.net/21/198/ That gallery doesn’t correctly scale portrait oriented photos initially, but you can select a size and it’ll resize it. I’ve got to get to that some day. PCM (Paul Michali) MAIL …..…. p...@cisco.commailto:p...@cisco.com IRC ……..… pc_m (irc.freenode.comhttp://irc.freenode.com) TW ………... @pmichali GPG Key … 4525ECC253E31A83 Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] No IPv6 meeting next week - Dec. 9th 2014
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
[openstack-dev] [Neutron][IPv6] Priorities for Kilo?
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. Please review, and give me links to bugs in launchpad and specs in Gerrit. I am trying to avoid linking directly to patches that fix bugs or implement a spec, to keep things simple. https://review.openstack.org/137169 Finally, please let me know if you agree with what I've marked highest priority. The tl;dr is that we need to fix gaps in Neutron Routers and DVR support since everyone is going to want tenant networks with IPv6 functionality and also DVR support. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Stale patches
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 abandoned by authors? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] No meeting this week
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
Re: [openstack-dev] [Neutron] Let's fix all neutron bugs! (NOT)
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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [qa] [neutron] local.conf for devstack using neutron on home network
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 on both your feedback on the review, as well as in-person discussions with Dean Troyer. It is currently adapted from notes for my multi-node lab that contains dual interfaces and provider networking. I am working to address your comments about using a single interface, although some additions may need to be done to DevStack to add the public interface to the bridge and re-assign the IP address, similar to what Nova-Network does. https://review.openstack.org/#/c/131201/ -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] IPv6 team summit meetup
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
Re: [openstack-dev] [Neutron][QoS] Pod time at Paris Summit
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
[openstack-dev] [Neutron][QoS] Pod time at Paris Summit
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/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] No meeting tomorrow
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
[openstack-dev] [DevStack][Neutron] Creating bridges automatically?
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 interface to it[2]. I have a patch into DevStack that does this in the provider networking case[3] - and a Vagrant setup I use for the l3 networking extension has a puppet recipie that automatically adds the public interface to the bridge after DevStack runs[4]. Should we have DevStack go ahead and wire up the bridge and interface when using the L3 agent? [1]: https://review.openstack.org/#/c/131201/ [2]: http://docs.openstack.org/admin-guide-cloud/content/install_neutron-l3.html [3]: http://git.openstack.org/cgit/openstack-dev/devstack/tree/lib/neutron#n654 [4]: https://github.com/sc68cal/chef-devstack/blob/master/recipes/default.rb#L55 -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] Proposal - add support for Markdown for docs
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 that Sphinx spat out. I'm sure there is a lot of work that needs to be done to format it to be more readable - but I'm pretty pleased with the result. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [DevStack] Proposal - add support for Markdown for docs
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 that it would be possible to add Pelican[1], which would make it easier to contribute documentation since we wouldn't have to write raw HTML. This may help make contributing docs more seamless. What does everyone think? [1]: http://blog.getpelican.com/ -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] Proposal - add support for Markdown for docs
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
Re: [openstack-dev] [DevStack] Proposal - add support for Markdown for docs
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 possible to add Pelican[1], which would make it easier to contribute documentation since we wouldn't have to write raw HTML. This may help make contributing docs more seamless. Sean, I assume you realize that by standing up and saying this you become the first volunteer to do the work, right? ;) Yep - I already have a branch that adds it as a dependency, and I'm starting to hack on it right now, I just figured I'd check on the ML and see core reviewer blessings :) -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [DevStack] Proposal - add support for Markdown for docs
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 built and published like the rest of openstack docs. Now - I don't want to get in the way of the work you're wanting to contribute, because I'm pretty sure that's awesome ... but all of the rest of the OpenStack docs are in RST and not MD, so it seems strange to do new work in a different format. Actually after I sent the e-mail I checked, and Pelican supports multiple formats, including RST. Changing from Markdown to RST isn't too onerous - I'd rather go from Markdown - RST than Markdown - HTML. Thinking a little more, it may be worth cribbing the code from other projects, like how the *-specs repos are generating docs from RST files rather than importing Pelican? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] Skipping IPv6 unit tests in proprietary plugins
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 have added similar logic to the OpenContrail plugin's tests. https://review.openstack.org/#/c/126407/1 -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] IPv6 bug fixes that would be nice to have in Juno
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 about these bugs, and I agree with his assessment. +1! -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] Moving meeting time to 1500 UTC on Tuesdays on #openstack-meeting-alt?
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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] Allowing Plugins in tree that explicitly do not support IPv6
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 class and has completely disabled creating Subnets that have an ip_version of 6. http://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/oneconvergence/plugin.py#n228 I hate to single out this plugin. Before this development cycle, open source plugins would allow the creation of Subnets with ip_version set to 6, and then have lots of bugs which would prevent any instances from actually obtaining IPv6 addresses and routing. But we didn't have to explicitly skip tests every time someone wanted to fix bugs - like the following patch. https://review.openstack.org/#/c/116317/ Also, I want to highlight some meeting minutes, where it was discussed that in the K release, all plugins will be required to support IPv6. I hope we can discuss this, build consensus, and ensure that the K release requirement is reasonable. http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-07-14-21.02.html Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][QoS] Request to be considered for neutron-incubator
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 collaborate and improve. -- Sean M. Collins ___ 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
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.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] Rotating the weekly Neutron meeting
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. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova][Neutron][Technical Committee] nova-network - Neutron. Throwing a wrench in the Neutron gap analysis
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 dedicate resources to this requirement? It is my direct experience that features that are important to a large organization will require resources from that very organization to be completed. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] [IPv6] Hide ipv6 subnet API attributes
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' consumable? There are currently no plans, since all of the changes that implement IPv6 functionality have been landing in Juno. I suggest upgrading to Juno when it is released. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Infra][Neutron] Request voting for Tail-f CI account
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 current CI, and I am the one responsible for smooth operation of that CI. I am reviewing its results with my morning coffee and have been doing so for the past 6 weeks. I would like to have it start voting and I believe that it and I are ready for that. I am responsive to email, I am usually on IRC (lukego), and in case of emergency you can SMS/call my mobile on +41 79 244 32 17. So... Let's be friends again? (and do ever cooler stuff in Kilo?) Luke was kind enough to reach out to me, and we had a discussion in order to bury the hatchet. Posting his contact details and being available to discuss things has put my mind at ease, I am ready to move forward. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] [Spec freeze exception] Support Stateful and Stateless DHCPv6 by dnsmasq
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 this BP is planned for configure OpenStack dnsmasq to co-work with router advertisement from either external router or OpenStack managed RADVD to get IPv6 network fully functional. This BP also supports dnsmasq to work independently for DHCPv6 subnet. Without this BP, only SLAAC mode is enabled without any stateful/stateless DHCPv6 support. The spec is under review: https://review.openstack.org/#/c/102411/ Code change for this BP is submitted as well for a while: https://review.openstack.org/#/c/106299/ Thanks, Xu Han I'd like to +1 this request, if this work landed in Juno, this would mean Neutron would have 100% support for all IPv6 subnet attribute settings, since slaac support landed in J-2. I know that we're competing for bandwidth and asking for special consideration, but I feel it's my role to advocate for the devs on the subteam. Thank you for the consideration! -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Infra][Neutron] Request voting for Tail-f CI account
From: Luke Gorrie l...@snabb.comailto:l...@snabb.co Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Monday, July 21, 2014 3:22 PM To: OpenStack Development Mailing List openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] [Infra][Neutron] Request voting for Tail-f CI account The account has a rich history :-). Initially we brought it online back around Nov 2013 early in the Icehouse cycle. That didn't work out so well: we had a bunch of operational issues and as OpenStack newbies we were oblivious to the impact they had on other people's workflows -- we were mortified to learn that we had created a disruption. Since then we have been more conservative which is why the account was mostly idle until June. The fact that I tried to reach out to the person who was listed as the contact back in November to try and resolve the –1 that this CI system gave, and never received a response until the public mailing list thread about revoking voting rights for Tail-F, makes me believe that the Tail-F CI system is still not ready to have that kind of privilege. Especially if the account was idle from around February, until June – that is a huge gap, if I understand correctly? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] cloud-init IPv6 support
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/ and http://169.254.169.254/ec2 is a mostly-aws-compatible metadata service. The metadata service that lives at http://169.254.169.254/openstack is 100% Openstack Invented. The URL structure and schema of data within may be 100% openstack invented, but the idea of having a link local address that takes HTTP requests and returns metadata was (to my knowledge) an Amazon EC2 idea from the beginning. There have been some good arguments and workarounds for the fact that Amazon EC2 is not dual-stacked. My concern is that when Amazon finally brings IPv6 to EC2, if we are trying to anticipate what they are going to do on items like the metadata API, and we guess wrong, we're going to have to make breaking changes. For now, I think we should document that only config drive for metadata works in an IPv6 environment, and wait for Amazon to make changes to their metadata API to enable IPv6 support, for those who wish for AWS compatibility. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][IPv6] Volunteer to run tomorrow's IRC meeting?
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 my absence, although lately there has not been a lot of participation. This is partly my fault since I didn't start the meeting on time last week, but I wonder if we should continue the IRC meeting? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] Volunteer to run tomorrow's IRC meeting?
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.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][ML2] Migration bug - Bug #1332564
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 neutron to be merged. Firstly, who has strong mysql-fu to pair up and track down why the foreign key statement is failing in 1332564, and secondly what can I do to help add grenade support for the OVS/LB - ML2 migration? This is a critical bug and I can probably devote a great deal of my time to fixing this. [0]: https://bugs.launchpad.net/neutron/+bug/1332564 [1]: https://review.openstack.org/#/c/76533/10 -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] High bandwidth routers
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/openstack-dev
Re: [openstack-dev] [neutron][ipv6] Do you have problem accessing IRC
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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][QoS] Meeting agenda for Today's meeting
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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Debugging Devstack Neutron with Pycharm
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...@vmware.com] Sent: Wednesday, June 11, 2014 8:36 AM To: ges...@cisco.com Cc: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Debugging Devstack Neutron with Pycharm Thanks a lot, this works, i will update the wiki. Gal. From: Henry Gessau ges...@cisco.com To: openstack-dev@lists.openstack.org Sent: Wednesday, June 11, 2014 2:41:47 PM Subject: Re: [openstack-dev] [Neutron] Debugging Devstack Neutron with Pycharm Gal Sagie wrote: I am trying to debug devstack Neutron with Pycharm, i have found here (https://wiki.openstack.org/wiki/NeutronDevelopment#How_to_debug_Neutron_.28and_other_OpenStack_projects_probably_.29) That i need to change the neutron server code to this=eventlet.monkey_patch() To: eventlet.monkey_patch(os=False, thread=False) I don't need to do this. But I do need to go into the PyCharm settings under Python Debugger and enable Gevent compatible debugging. I have done so, debug seems to run, but when i am trying to initiate commands from the CLI i get this: gal@ubuntu:~/devstack$ neutron net-list Connection to neutron failed: Maximum attempts reached Are you sure you have sourced openrc correctly for the credentials? (the server seems to run ok...) Any help is appreciated as i am trying to learn and understand main flows by debugging the code locally. First I start devstack in offline mode. OFFLINE=True ./stack.sh Once it is running I go to the neutron window in screen. There I stop neutron-server with ctrl-C, and press up-arrow to view the start command. To run neutron-server in the PyCharm debugger edit the Run/Debug configuration with the following settings: Script: /usr/local/bin/neutron-server Script params: --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini # I got this from the screen window where I stopped neutron Working directory: /opt/stack/neutron Now restart neutron from PyCharm instead of screen. ___ 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][ipv6] Support ipv6 RA in neutron
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 correct it, I created a new blueprint https://blueprints.launchpad.net/neutron/+spec/neutron-ipv6-ra and linked it to a neutron spec https://review.openstack.org/92164. The basic idea behind this blueprint is that neutron dhcp service as it is can hand out IPv6 addresses either in IPv6 only data network or in a dual stack data network. But the RA service including SLAAC support is missing in neutron. This service is important. Without RA, VMs won’t be able to automatically install default routes. Without SLAAC, a deployment that prefers SLAAC won’t be able to do it with neutron. The BP takes a straightforward approach to achieve that without requiring significant change to the existing dhcp service. Any feedback is appreciated. To be clear, you are still proposing that we remove the IPv6 subnet attributes that have been merged, and replaced with a single attribute, yes? Would you be willing to set aside the single attribute API proposal, and instead work on fixing dnsmasq and adding support for rtadvd, and supporting the two attribute blueprint that the community developed and merged? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron][ipv6] ipv6 dual stack
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 the minimum dnsmasq version that we support. Older versions will crash when adding a second tag to the command line arguments for launching dnsmasq. I run Ubuntu 12.04 in my lab, with devstack, and the version of dnsmasq that gets installed exhibits this behavior. https://bugs.launchpad.net/neutron/+bug/129 -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [driverlog] Tail-f CI and it's lack of running and it's DriverLog status
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 the links that is posted in that review comment for the Tail-f NCS Jenkins timed out for me. http://egg.snabb.co:8080/job/jenkins-ncs/19/ I notice that there is another link included in that review that does work and has the logs: http://88.198.8.227:81/html/ci-logs/2014-06-10_15-52-09 Can you comment on what the egg.snabb.co URL is for? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] [driverlog] Tail-f CI and it's lack of running and it's DriverLog status
Cool, Thanks. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][QoS] Weekly IRC Meeting?
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://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][QoS] Weekly IRC Meeting?
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 everyone up to date. I am working on a blueprint in neutron-specs and documenting the work that has been completed. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][IPv6] Neutron Routers and LLAs
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 only time that the gateway will be specified in advance for a V6 subnet is if you are using an external device or something not orchestrated by OpenStack. We discussed this today, in the meeting, at 14:24:09 http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-05-27-14.01.log.html Basically, if you are going to create a router in Neutron for a v6 subnet, we plan on having the router attachment step populate the gateway attribute of the subnet, since we will be wiring it up and will have a LLA for the router. For now, we are not addressing the problem of multiple routers attached to different subnets - since we need to do some research on that. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] Minutes from May 27 2014
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
[openstack-dev] [Neutron][QoS] First meeting minutes
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/openstack-dev
Re: [openstack-dev] Configuration Changes Ignored in devstack
Here's the documentation on how to configure DevStack http://devstack.org/configuration.html From: Sachi Gupta sachi.gu...@tcs.commailto:sachi.gu...@tcs.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Monday, May 26, 2014 3:37 AM To: openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] Configuration Changes Ignored in devstack Installed Openstack-dev for deploying OpenStack cloud, and made changes to the configuration files (such as - /etc/nova/nova.conf etc) and have ran stack.sh script. Running stack.sh script overrides the configuration file changes. To make the changes persistent, have added Reclone=no and Offline=true in localrc file, but still facing the same issue. Please suggest how to make changes persistent in configuration files. 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 -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Core API refactoring
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 was only an attempt to try and help provide context for what was discussed at the summit. I dislike having people put words in my mouth, and you also seem to continue to insinuate that things are not done in the open, with everyone having a chance to participate. I believe this is a serious charge, and I do not appreciate being publicly accused of this. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] devstack w/ neutron in vagrant - floating IPs
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 without any real success. I have had this issue as well, when developing vagrant_devstack (https://github.com/bcwaldon/vagrant_devstack) - but I haven't had the capacity to track down the cause. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Core API refactoring
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 changes and I get a feeling that not being able to attend the Atlanta summit is going to be a significant barrier to participation in this critical effort. It is possible there is a misconception here: refactoring the API core does not mean changing the APIs that are presented to the user. We are in the process of replacing a homegrown WSGI with Pecan to make the WSGI layer of Neutron cleaner and easier to create API extensions. http://pecan.readthedocs.org/en/latest/index.html -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][QoS] Weekly IRC Meeting?
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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] reservation of fixed ip
(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: Hello, Ok, I found that now there is probably no such feature to reserve fixed ip for tenant. So I was thinking about add such feature to neutron. I mean that it should have new table with reserved ips in neutron database and neutron will check this table every time when new port will be created (or updated) and IP should be associated with this port. If user has got reserved IP it should be then used for new port, if IP is reserver by other tenant - it shouldn't be used. What You are thinking about such possibility? Is it possible to add it in some future release of neutron? -- Best regards Sławek Kapłoński sla...@kaplonski.pl Dnia Mon, 19 May 2014 20:07:43 +0200 Sławek Kapłoński sla...@kaplonski.pl napisał: Hello, I'm using openstack with neutron and ML2 plugin. Is there any way to reserve fixed IP from shared external network for one tenant? I know that there is possibility to create port with IP and later connect VM to this port. This solution is almost ok for me but problem is when user delete this instance - then port is also deleted and it is not reserved still for the same user and tenant. So maybe there is any solution to reserve it permanent? I know also about floating IPs but I don't use L3 agents so this is probably not for me :) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] Meeting minutes for 5/20/2014
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
[openstack-dev] [Neutron][IPv6] Agenda for tomorrow's meeting - please add items
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
Re: [openstack-dev] [devstack] Devstack Multinode on CentOS
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's just pointing to the controller, once I run nova host-list and I only get the the controller host. Are you setting SERVICE_HOST, MYSQL_HOST, RABBIT_HOST correctly? Are you able to post your configs for compute and control nodes? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [devstack] Devstack Multinode on CentOS
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 compute node appears to have API services running in the enabled_services list. So - here's an example from my lab: Controller localrc: # Nova disable_service n-net enable_service n-cpu # Neutron ENABLED_SERVICES+=,neutron,q-svc,q-dhcp,q-meta,q-agt Compute localrc: ENABLED_SERVICES=n-cpu,rabbit,neutron,q-agt -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron] Consistency between models and migrations
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 corresponding migrations – as well as fixing differences in the generated DDL between Postgres and MySQL. The only thing I'm concerned about, is how to prevent these inconsistencies from sneaking into the codebase in the future. The one review that fixes ForeignKey constraints that are missing a name argument which ends up failing to create indexes in Postgres – I can see myself repeating that mistake, it's very subtle. Should we have some sort of HACKING for database models and migrations? Are these problems subtle enough that they warrant changes to SQLAlchemy/Alembic? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][QoS] Reminder - 2:30 PM tomorrow at the Networking pod
Etherpad link: https://etherpad.openstack.org/p/qos-api-network-pod From: Collins, Sean Collins sean_colli...@cable.comcast.commailto:sean_colli...@cable.comcast.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Wednesday, May 14, 2014 12:01 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] [Neutron][QoS] Reminder - 2:30 PM tomorrow at the Networking pod Be there or be square :) -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][QoS] Reminder - 2:30 PM tomorrow at the Networking pod
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
Re: [openstack-dev] [Neutron][QoS] Interest in a meeting at the Networking pod at the design summit?
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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][QoS] Interest in a meeting at the Networking pod at the design summit?
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? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][QoS] Interest in a meeting at the Networking pod at the design summit?
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
Re: [openstack-dev] [Neutron][QoS] Interest in a meeting at the Networking pod at the design summit?
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 design summit sessions in the morning, perhaps that would be the best time? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] No IRC meeting
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
Re: [openstack-dev] [Neutron][Nova][Designate][L3][IPv6] Discussion about Cross-Project Integration of DNS at Summit
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 working on a DevStack patch that moves the management network API endpoints to be dual stack or ipv6 only. BTW, maybe this dns-resolution for IPv6-Only networks (if desired) might also handle the IPv4 Floating IPs (in a NAT46 fashion)... I believe that is out of scope and is large enough to warrant separate blueprints. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][QoS] Quick update
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 copy paste of a Google doc, I will be updating it and submitting it for review. I've restored some of the patches for the QoS API, but they need to be rebased and updated. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] Design Summit Sessions
From: Kyle Mestery mest...@noironetworks.commailto:mest...@noironetworks.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Monday, April 28, 2014 3:08 PM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [neutron] Design Summit Sessions I think the idea in general was to make it more open and possibly to use it for continuing discussions which overflowed their time. What do others think? Perfect! Love the idea – I know at Hong Kong I had a couple times where we moved it into the lounge to continue discussions -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] Agenda for tomorrow's meeting
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.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [NEUTRON] [IPv6] [VPNaaS] - IPSec by default on each Tenant router, the beginning of the Opportunistic Encryption era (rfc4322 ?)...
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/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] Neutron Mid-Cycle Meeting
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 participate remotely - and that they are not considered an afterthought. -- Sean M. Collins ___ 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
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
[openstack-dev] [Neutron][IPv6] Meeting Minutes
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/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][QoS] API Design Document v2
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.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] Agenda for April 15th
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/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it
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 updating them and getting them merged. At this point simply applying them to the Icehouse tree is not enough. When and where is the next meeting? https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam 1400 UTC on Tuesdays 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
[openstack-dev] Vagrant Devstack projects - time to consolidate?
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-vagrant/ https://github.com/jogo/DevstackUp https://github.com/search?q=vagrant+devstackref=cmdform -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it
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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
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. -Sean +1 to this idea. I found vagrant_devstack a while ago and started using it and then started documenting it for our development team at Comcast, it has been very helpful for getting new developers started. Having something in Stackforge would be great, so that we can consolidate all our knowledge and energy. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?
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 lifting. Being opinionated is good when it comes to providing tools to make things easy to onboard people. The provisioner in infra is puppet. Learning puppet lets you contribute to the rest of the openstack infra, and I expect to consume some piece of that in this process. +1000 on this - if there's already a provisioner that is used for infra, let's re-use some of that knowledge and expertise. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron] [IPv6] Supporting upstream RAs
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 have your permission to post a rebased version of this patch into Gerrit - I have set myself as the author and added you both as Co-Authors. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] [IPv6] Supporting upstream RAs
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 your patience while I rebase some patches and submit them for review, to work with the two new IPv6 attributes. Please join us on the IRC channel tomorrow, if you are available. 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/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] Agenda for tomorrow - please add topics
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.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it
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/+bug/129 -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it
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
Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it
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 business. So keep your powder dry ;) -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Using Python-Neutronclient from Python - docstrings needed?
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 Possibly inside the doc/user-guide tree. Although others may have better suggestions. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] Neutron Routers and LLAs
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 assigned, was a link local
address that was not on the subnet.
This may or may have been run before force_gateway_on_subnet flag was
introduced. Robert - if you can give us what version of Neutron you were
running that would be helpful.
Here's the full text of what Robert posted in the review, which shows
the bug, which was later filed[1].
This is what I've tried, creating a subnet with a LLA gateway address:
neutron subnet-create --ip-version 6 --name myipv6sub --gateway fe80::2001:1
mynet :::/64
Created a new subnet:
+--++
| Field | Value |
+--++
| allocation_pools | {start: :::1, end:
::::::fffe} | | cidr | :::/64 | |
dns_nameservers | | | enable_dhcp | True | | gateway_ip | fe80::2001:1 | |
host_routes | | | id | a1513aa7-fb19-4b87-9ce6-25fd238ce2fb | | ip_version |
6 | | name | myipv6sub | | network_id | 9c25c905-da45-4f97-b394-7299ec586cff
| | tenant_id | fa96d90f267b4a93a5198c46fc13abd9 |
+--++
openstack@devstack-16:~/devstack$ neutron router-list
+--+-+-+
| id | name | external_gateway_info
|
+--+-+-+
| 7cf084b4-fafd-4da2-9b15-0d25a3e27e67 | router1 | {network_id:
02673c3c-35c3-40a9-a5c2-9e5c093aca48, enable_snat: true}
|
+--+-+-+
openstack@devstack-16:~/devstack$ neutron router-interface-add
7cf084b4-fafd-4da2-9b15-0d25a3e27e67 myipv6sub
400-{u'NeutronError': {u'message': u'Invalid input for operation: IP address
fe80::2001:1 is not a valid IP for the defined subnet.', u'type':
u'InvalidInput', u'detail': u''}}
During last week's meeting, we had a bit of confusion near the end of the
meeting[2] about the following bug, and the fix[3].
If I am not mistaken - the fix is so that when you create a v6 Subnet
with a link local address, then create a Neutron router to serve as the
gateway for that subnet - the operation will successfully complete and a
router will be created.
We may need to take a look at the code that create a router - to ensure
that only one gateway port is created, and that the link local address
from the subnet's 'gateway' attribute is used as the address.
This is at least my understanding of the problem as it stands today -
and that this bug and fix does not involve any external gateways or
physical devices that Neutron does not control - this is exclusively
about Neutron routers.
[0]: https://review.openstack.org/#/c/72252/
[1]: https://bugs.launchpad.net/neutron/+bug/1284518
[2]:
http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-03-18-14.02.log.html
[3]: https://review.openstack.org/#/c/76125/
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron][IPv6] Prefix delegation - API Attributes
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 list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron] Developer Documentation - Architecture design docs in Google docs
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 perhaps even bring them into the developer documentation tree (if they are not currently undergoing discussion and development)? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron][IPv6] IRC meeting today?
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: [openstack-dev] [Neutron][IPv6] IRC meeting today? Do we have IRC meeting today? Didn’t see anybody in the chat room…..:( Shixiong Shixiong Shang !--- Stay Hungry, Stay Foolish ---! ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron][QOS]How is the BP about ml-qos going?
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, so I continued to do improvements and bug fixes and push them to the Comcast GitHub repo for Neutron, to support our deployment, but I did not update the reviews in Gerrit. I recently revived the reviews - and have pushed some updates. I hope to get this merged for the J release, and have scheduled a summit session for Atlanta to discuss. Anyone who knows the history can help me or give me a hint how to find the discuss mail? Search for posts tagged [QoS] - that should get most of them. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Developer documentation
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 - comments and suggestions welcome - especially on how to introduce WSGI and everything else without making someone's head explode. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Neutron and IPv6 for IceHouse?
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 sending ICMPv6 RA packets. We are working on a series of patches that will make Neutron create IPv6 subnets, and launch dnsmasq with the correct configuration. Please join us on IRC, and post/read threads with the subject line of [Neutron][IPv6]. https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam Sean M. Collins From: Martinx - ジェームズ [thiagocmarti...@gmail.com] Sent: Saturday, March 08, 2014 3:11 PM To: OpenStack Development Mailing List Subject: [openstack-dev] Neutron and IPv6 for IceHouse? Hello Stackers! Please, forgive me to ask this here but, I'm about to lose my budget to deploy OpenStack in my ISP, because it does not support IPv6. There is no more IPv4 around here and I can not grow without IPv6. Please, I'm begging for you guys, pleeease, release IceHouse with IPv6! Otherwise, I'll lose the opportunity and there will be no more OpenStack around here... The company is about to give it up and look for another solution... I'll lost more than a year of development and a lot of time and money... I know that none of you are responsible for this, of course, this is my own problem but, I'm just trying to show for you guys, that IPv6 is a requirement, OpenStack can not live without it any longer (I believe)... Wait six more months is just out of the table (for me and for my company)... I am not a coder but, I have a huge lab and I'm good in testing and debugging softwares, please, let me know if there is anything that I can do, to make this [Neutron with IPv6] a reality. Is it working with Devstack?! Thanks! Thiago ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Neutron and IPv6 for IceHouse?
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/openstack-dev/2014-February/026589.html Sean M. Collins From: Martinx - ジェームズ [thiagocmarti...@gmail.com] Sent: Saturday, March 08, 2014 3:11 PM To: OpenStack Development Mailing List Subject: [openstack-dev] Neutron and IPv6 for IceHouse? Hello Stackers! Please, forgive me to ask this here but, I'm about to lose my budget to deploy OpenStack in my ISP, because it does not support IPv6. There is no more IPv4 around here and I can not grow without IPv6. Please, I'm begging for you guys, pleeease, release IceHouse with IPv6! Otherwise, I'll lose the opportunity and there will be no more OpenStack around here... The company is about to give it up and look for another solution... I'll lost more than a year of development and a lot of time and money... I know that none of you are responsible for this, of course, this is my own problem but, I'm just trying to show for you guys, that IPv6 is a requirement, OpenStack can not live without it any longer (I believe)... Wait six more months is just out of the table (for me and for my company)... I am not a coder but, I have a huge lab and I'm good in testing and debugging softwares, please, let me know if there is anything that I can do, to make this [Neutron with IPv6] a reality. Is it working with Devstack?! Thanks! Thiago ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Neutron and IPv6 for IceHouse?
Yes, you can test these patches that are under review, but be prepared to do some debugging/hacking. They were not merged for I-3 since there is still work being done on them. There is also some patches that are under review to start bringing up Neutron routers and do RAs, but it is still under 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: [openstack-dev] Neutron and IPv6 for IceHouse? Mmm... But can I test those patches that are still under review, with Devstack? I meant, I would like to start testing a IPv6 provided by Neutron + RA, not by external provider. Tks! Thiago On 8 March 2014 21:58, Collins, Sean sean_colli...@cable.comcast.commailto:sean_colli...@cable.comcast.com wrote: 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/openstack-dev/2014-February/026589.html Sean M. Collins From: Martinx - ジェームズ [thiagocmarti...@gmail.commailto:thiagocmarti...@gmail.com] Sent: Saturday, March 08, 2014 3:11 PM To: OpenStack Development Mailing List Subject: [openstack-dev] Neutron and IPv6 for IceHouse? Hello Stackers! Please, forgive me to ask this here but, I'm about to lose my budget to deploy OpenStack in my ISP, because it does not support IPv6. There is no more IPv4 around here and I can not grow without IPv6. Please, I'm begging for you guys, pleeease, release IceHouse with IPv6! Otherwise, I'll lose the opportunity and there will be no more OpenStack around here... The company is about to give it up and look for another solution... I'll lost more than a year of development and a lot of time and money... I know that none of you are responsible for this, of course, this is my own problem but, I'm just trying to show for you guys, that IPv6 is a requirement, OpenStack can not live without it any longer (I believe)... Wait six more months is just out of the table (for me and for my company)... I am not a coder but, I have a huge lab and I'm good in testing and debugging softwares, please, let me know if there is anything that I can do, to make this [Neutron with IPv6] a reality. Is it working with Devstack?! Thanks! Thiago ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Developer documentation
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 TESTING file, but I felt that they can be addressed in other patchsets - since I don't feel confident in making the changes that they suggested, and some of the comments refer to issues that exist in the In addition, we're almost to the goal line - I'd rather get some docs merged and update in another patchset, rather than update this review with another patchset, that clears out all the +2's and +1's and then wait for everyone to circle back and re-approve. I understand this is a unusual request and I am asking for special treatment, but Neutron is severely lacking in documentation for new developers and I think this patch moves us closer to fixing it. Thoughts? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Developer documentation
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, Akihiro Motoki and others highlighted. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
