Re: [openstack-dev] [astara] Retirement of astara repos?

018-02-23 14:34, Andreas Jaeger wrote: >>> On 2018-01-11 22:55, Mark McClain wrote: >>> Sean, Andreas- >>> >>> Sorry I missed Andres’ message earlier in December about retiring astara. >>> Everyone is correct that development stopped a good while

Re: [openstack-dev] Retirement of astara repos?

Sean, Andreas- Sorry I missed Andres’ message earlier in December about retiring astara. Everyone is correct that development stopped a good while ago. We attempted in Barcelona to find others in the community to take over the day-to-day management of the project. Unfortunately, nothing

Re: [openstack-dev] [neutron][astara-neutron]

Development of the project has been quiet for some time as the developers have moved onto to other work. The main project repo is astara [1] and which had a few commits last fall. At summit in Barcelona, we solicited for those interested in continuing Astara. For those interested in

[openstack-dev] [election][tc] Not Running for Re-Election

All- I wanted to drop a note to let everyone know that I will not seek re-election to the TC for this cycle. I’ve really enjoyed working with everyone in our community through the TC the past three years. I’m super excited by the candidates who are running where they’ll lead our community.

Re: [openstack-dev] [all] Austin Design Summit track layout

> On Mar 28, 2016, at 6:28 AM, Thierry Carrez wrote: > > Hi everyone, > > Please find attached in PDF the proposed layout for the various tracks at the > Design Summit in Austin. I tried to take into account all the talk conflicts > and the constraints that you

Re: [openstack-dev] [stable] meeting time proposal

> On Dec 16, 2015, at 2:12 PM, Matt Riedemann > wrote: > > I'm not entirely sure what the geo distribution is for everyone that works on > stable, but I know we have people in Europe and some people in Australia. So > I was thinking alternating weekly meetings: >

Re: [openstack-dev] [Neutron] virtual machine can not get DHCP lease due packet has no checksum

On Jun 1, 2015, at 7:26 PM, Tidwell, Ryan ryan.tidw...@hp.com wrote: I see a fix for https://bugs.launchpad.net/neutron/+bug/1244589 merged during Kilo. I'm wondering if we think we have identified a root cause and have merged an appropriate long-term fix, or if

[openstack-dev] TC candidacy

All- I'd like to announce my candidacy to continue serving on the Technical Committee. Platform — OpenStack is a growing community comprised of many parts and we we must view ourselves as one unit. As a TC member, I will continue to place the interests of the larger community over those

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

On Mar 24, 2015, at 9:30 AM, John Griffith john.griffi...@gmail.com wrote: On Tue, Mar 24, 2015 at 4:52 AM, Thierry Carrez thie...@openstack.org mailto:thie...@openstack.org wrote: Walter A. Boring IV wrote: Thanks Mike for all of your efforts on this, +1 I think Mike checked

Re: [openstack-dev] [Neutron] Multiple template libraries being used in tree

You’re right that the Mako dependency is really a side effect from Alembic. We used jinja for tempting radvd because it is used by the projects within the OpenStack ecosystem and also used in VPNaaS. mark On Feb 2, 2015, at 3:13 PM, Sean M. Collins s...@coreitpro.com wrote: Sorry, I

Re: [openstack-dev] [neutron] Changes to the core team

On Jan 22, 2015, at 12:21 PM, Kyle Mestery mest...@mestery.com wrote: On Thu, Jan 15, 2015 at 4:31 PM, Kyle Mestery mest...@mestery.com mailto:mest...@mestery.com wrote: The last time we looked at core reviewer stats was in December [1]. In looking at the current stats, I'm going to

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

On Dec 11, 2014, at 8:43 AM, Jay Pipes jaypi...@gmail.com wrote: I'm generally in favor of making name attributes opaque, utf-8 strings that are entirely user-defined and have no constraints on them. I consider the name to be just a tag that the user places on some resource. It is the

Re: [openstack-dev] [neutron] mid-cycle update

On Dec 11, 2014, at 10:29 AM, Kyle Mestery mest...@mestery.com wrote: On Wed, Dec 10, 2014 at 5:41 PM, Michael Still mi...@stillhq.com mailto:mi...@stillhq.com wrote: This all sounds like good work. Did you manage to progress the nova-network to neutron migration tasks as well? I

Re: [openstack-dev] [neutron] Changes to the core team

On Dec 2, 2014, at 10:59 AM, Kyle Mestery mest...@mestery.com wrote: First of all, I'm proposing we remove Bob Kukura and Nachi Ueno from neutron-core. Bob and Nachi have been core members for a while now. They have contributed to Neutron over the years in reviews, code and leading

[openstack-dev] [tc][neutron] Proposal to split Neutron into separate repositories

All- Over the last several months, the members of the Networking Program have been discussing ways to improve the management of our program. When the Quantum project was initially launched, we envisioned a combined service that included all things network related. This vision served us well

Re: [openstack-dev] [tc][neutron] Proposal to split Neutron into separate repositories

On Nov 18, 2014, at 5:45 PM, Doug Hellmann d...@doughellmann.com wrote: There would not be a service or REST API associated with the Advanced Services code base? Would the REST API to talk to those services be part of the Neutron repository? Doug We had considered having a standalone

Re: [openstack-dev] [neutron][advanced services] Weekly IRC meeting day/time change

On Nov 9, 2014, at 11:14 PM, Sumit Naiksatam sumitnaiksa...@gmail.com wrote: Hi All, Following up from the discussions during the Kilo Summit, we will be resuming the Advanced Services' meetings [1]. The new day/time will be Tuesday 17.00 UTC on #openstack-meeting-4 to follow the LBaaS

Re: [openstack-dev] [Neutron][Spec freeze exception] Rootwrap daemon ode support

On Nov 7, 2014, at 5:52 AM, Miguel Ángel Ajo majop...@redhat.com wrote: Ohh, sad to hear that Yuriy, you were doing an awesome work. I will take some time to re-review the final state of the code and specs, and move it forward. Thank you very much for your contribution. -- Miguel

Re: [openstack-dev] [neutron] Limitation of permissions on modification some resources

On Sep 29, 2014, at 7:09 AM, Andrey Epifanov aepifa...@mirantis.com wrote: Hi All, I started working on the the https://bugs.launchpad.net/neutron/+bug/1339028 and realized that we have the same issue with other connected resources in Neutron. The is a bug in how we’re implementing the

Re: [openstack-dev] [neutron] [IPv6] New API format for extra_dhcp_opts

On Sep 26, 2014, at 2:39 AM, Xu Han Peng pengxu...@gmail.com wrote: Currently the extra_dhcp_opts has the following API interface on a port: { port: { extra_dhcp_opts: [ {opt_value: testfile.1,opt_name: bootfile-name}, {opt_value: 123.123.123.123,

Re: [openstack-dev] [nova] 2 weeks in the bug tracker

On Sep 19, 2014, at 9:13 AM, Sean Dague s...@dague.net wrote: Cross interaction with Neutron and Cinder remains racey. We are pretty optimistic on when resources will be available. Even the event interface with Neutron hasn't fully addressed this. I think a really great Design Summit session

Re: [openstack-dev] [Neutron][db] End of meetings for neutron-db

On Sep 22, 2014, at 9:26 AM, Henry Gessau ges...@cisco.com wrote: https://wiki.openstack.org/wiki/Meetings/NeutronDB The work on healing and reorganizing Neutron DB migrations is complete, and so we will no longer hold meetings. Great work by all who worked on this. mark

Re: [openstack-dev] [Neutron] - what integration with Keystone is allowed?

On Sep 22, 2014, at 1:20 PM, Monty Taylor mord...@inaugust.com wrote: On 09/21/2014 10:57 PM, Nader Lahouti wrote: Thanks Kevin for bring it up in the ML, I was looking for a guideline or any document to clarify issues on this subject. I was told, even using keystone API in neutron is not

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

On Sep 3, 2014, at 11:04 AM, Brian Haley brian.ha...@hp.com wrote: On 09/03/2014 08:17 AM, Kyle Mestery wrote: Given how deep the merge queue is (146 currently), we've effectively reached feature freeze in Neutron now (likely other projects as well). So this morning I'm going to go through

Re: [openstack-dev] [infra] [neutron] [tc] Neutron Incubator workflow

On Aug 28, 2014, at 10:45 AM, Jay Pipes jaypi...@gmail.com wrote: On 08/27/2014 04:28 PM, Kevin Benton wrote: What are you talking about? The only reply was from me clarifying that one of the purposes of the incubator was for components of neutron that are experimental but are intended to be

Re: [openstack-dev] [Neutron] Author tags

On Aug 27, 2014, at 2:27 PM, Mandeep Dhami dh...@noironetworks.commailto:dh...@noironetworks.com wrote: T hese should all be comment changes, so there should be no impact. While I agree that it is late for J3, IMO this is the type of change (minor/comment only) that should be OK J4 rather

Re: [openstack-dev] [Neutron][QA] Enabling full neutron Job

On Aug 15, 2014, at 6:20 PM, Salvatore Orlando sorla...@nicira.commailto:sorla...@nicira.com wrote: The neutron full job is finally voting, and the first patch [1] has already passed it in gate checks! I've collected a few data points before it was switched to voting, and we should probably

[openstack-dev] [Neutron] Group Based Policy and the way forward

All- tl;dr * Group Based Policy API is the kind of experimentation we be should attempting. * Experiments should be able to fail fast. * The master branch does not fail fast. * StackForge is the proper home to conduct this experiment. Why this email? --- Our community has been

Re: [openstack-dev] [Neutron][policy] Long standing -2 on Group-based policy patch

On Aug 4, 2014, at 1:16 PM, Sumit Naiksatam sumitnaiksa...@gmail.com wrote: The first patch[1] of this high priority approved blueprint[2][3] targeted for Juno-3 has been blocked by a core reviewer’s (Mark McClain) -2 since July 2nd. This patch was at patch-set 13 then, and has been

Re: [openstack-dev] [Neutron] Not support dnsmasq 2.63?

The hard limit should be 2.63 since that is supported in all of the modern long term releases from the distros. I’d prefer we not exit processes because we’ve been removing active checks on process starts. mark On Jul 29, 2014, at 9:51 PM, Xuhan Peng

Re: [openstack-dev] [Neutron][LBaaS] topics for Thurday's Weekly LBaaS meeting's agenda

On Jul 8, 2014, at 9:57 AM, Susanne Balle sleipnir...@gmail.com wrote: Hi I would like to discuss what talks we plan to do at the Paris' summit and who will be submitting what? The deadline for submitting talks is July 28 so it is approaching. Also how many working sessions do we

Re: [openstack-dev] [Neutron][LBaaS] Status of entities that do not exist in a driver backend

On Jul 4, 2014, at 5:27 PM, Brandon Logan brandon.lo...@rackspace.com wrote: Hi German, That actually brings up another thing that needs to be done. There is no DELETED state. When an entity is deleted, it is deleted from the database. I'd prefer a DELETED state so that should be

Re: [openstack-dev] [neutron] Flavor framework: Conclusion

On Jul 4, 2014, at 1:09 AM, Eugene Nikanorov enikano...@mirantis.commailto:enikano...@mirantis.com wrote: German, First of all extension list looks lbaas-centric right now. Actually far from it. SSL VPN should be service extension. Secondly, TLS and L7 are such APIs which objects should

Re: [openstack-dev] [Neutron] validation of input against column-size specified in schema

On Jun 25, 2014, at 12:26 AM, Manish Godara mani...@yahoo-inc.com wrote: Hi, Is there any way in current neutron codebase that can be used to validate the length of a string attribute against the max column size specified in the schema for that attribute. E.g. , in models_v2.py class

Re: [openstack-dev] [Neutron] High bandwidth routers

On Jun 23, 2014, at 9:21 AM, CARVER, PAUL pc2...@att.commailto:pc2...@att.com wrote: Is anyone using Neutron for high bandwidth workloads? (for sake of discussion let’s “high” = “50Gbps or greater”) With routers being implemented as network namespaces within x86 servers it seems like Neutron

Re: [openstack-dev] [Neutron] Core API refactoring

On May 21, 2014, at 10:23 AM, Mandeep Dhami dh...@noironetworks.commailto:dh...@noironetworks.com wrote: Hi Sean: While the APIs might not be changing*, I suspect that there are significant design decisions being made**. These changes are probably more significant than any new feature being

Re: [openstack-dev] [neutron] Proposed changes to core team

On May 21, 2014, at 4:59 PM, Kyle Mestery mest...@noironetworks.com wrote: Neutron cores, please vote +1/-1 for the proposed addition of Carl Baldwin to Neutron core. Carl has been a great contributor. +1 to adding to core team mark ___

Re: [openstack-dev] [Neutron][LBaaS][FWaaS][VPNaaS] Advanced Services (particularly LBaaS) and Neutron

On May 7, 2014, at 7:45 AM, Susanne Balle sleipnir...@gmail.commailto:sleipnir...@gmail.com wrote: Based on discussions with Rackspace, Mirantis, and others it is clear that the advanced services (i.e. LBaaS) in Neutron are not getting the attention and the support to move forward and create

Re: [openstack-dev] [neutron] explanations on the current state of config file handling

On May 4, 2014, at 8:08, Sean Dague s...@dague.net wrote: Question (because I honestly don't know), when would you want more than 1 l3 agent running on the same box? For the legacy case where there are multiple external networks connected to a node on different bridges.

Re: [openstack-dev] [neutron] explanations on the current state of config file handling

On May 2, 2014, at 7:39 AM, Sean Dague s...@dague.net wrote: Some non insignificant number of devstack changes related to neutron seem to be neutron plugins having to do all kinds of manipulation of extra config files. The grenade upgrade issue in neutron was because of some placement change

Re: [openstack-dev] [neutron] status of VPNaaS and FWaaS APIs in Icehouse

On Apr 23, 2014, at 6:20 PM, McCann, Jack jack.mcc...@hp.com wrote: Are VPNaaS and FWaaS APIs still considered experimental in Icehouse? For VPNaaS, [1] says This extension is experimental for the Havana release. For FWaaS, [2] says The Firewall-as-a-Service (FWaaS) API is an experimental

Re: [openstack-dev] [neutron] Service VMs

On Apr 21, 2014, at 3:07 PM, Kyle Mestery mest...@noironetworks.com wrote: For the upcoming Summit there are 3 sessions filed around Service VMs in Neutron. After discussing this with a few different people, I'd like to propose the idea that the Service VM work be moved out of Neutron and

Re: [openstack-dev] [Neutron] Trying to make sense of allow_overlapping_ips in neutron

On Apr 18, 2014, at 17:03, Ryan Moats rmo...@us.ibm.commailto:rmo...@us.ibm.com wrote: Apologies if this is posted to the wrong place, but after talking with Kyle Mestery (mest...@cisco.commailto:mest...@cisco.com), he suggested that I bring my question here... I'm trying to make sense of

Re: [openstack-dev] [Neutron] Migrations, service plugins and Grenade jobs

On Apr 14, 2014, at 11:54 AM, Salvatore Orlando sorla...@nicira.commailto:sorla...@nicira.com wrote: 1) Specify that all migrations must run for every plugin (*) unless they are really introducing schemas which are specific to a particular technology (such as uuid mappings between neutron

[openstack-dev] TC Candidacy

All- I'd like to announce my candidacy to continue serving on the Technical Committee. Platform --- OpenStack is one community comprised of many parts and we must view ourselves as one unit. As a TC member, I will continue to place the interests of the larger community over those of

Re: [openstack-dev] [Neutron] DHCP address being SNAT by L3 agent

On Apr 8, 2014, at 3:58 AM, Xuhan Peng pengxu...@gmail.com wrote: Hi Neutron stackers, I have a question about how to fix the problem of DHCP port address being SNAT by L3 agent. I have my neutron DHCP agent and L3 agent running on the same network node, and I disabled namespace

Re: [openstack-dev] [Neutron] Release Notes for Icehouse

On Apr 4, 2014, at 11:03 AM, Yaguang Tang yaguang.t...@canonical.commailto:yaguang.t...@canonical.com wrote: I think it's important for our developers to publish an official Release Note as other core openstack projects does at the end of Icehouse development cycle, it contains the new

[openstack-dev] [Neutron] PTL Candidacy

All- I writing to announce my candidacy for the OpenStack Networking (Neutron) PTL. I am the current Neutron PTL and would like to continue leading our team during the Juno cycle. As PTL, I have worked to promote a vibrant open ecosystem of deployers, integrators and vendors within Neutron.

Re: [openstack-dev] Spec repos for blueprint development and review

On Mar 24, 2014, at 2:23 PM, Sean Dague s...@dague.netmailto:s...@dague.net wrote: On 03/24/2014 02:05 PM, James E. Blair wrote: Russell Bryant rbry...@redhat.commailto:rbry...@redhat.com writes: On 03/24/2014 12:34 PM, James E. Blair wrote: Hi, So recently we started this experiment with the

Re: [openstack-dev] [neutron] Globally-unique VM MAC address to do vendor-backed DHCP

On Mar 18, 2014, at 7:40 AM, Roman Verchikov rverchi...@mirantis.commailto:rverchi...@mirantis.com wrote: Hi stakers, We’re trying to replace dnsmasq-supplied DHCP for tenant VMs with a vendor’s baremetal DHCP server. In order to pass DHCP request to a vendor’s server and send DHCP response

Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?

On Mar 13, 2014, at 4:22 PM, Jay Pipes jaypi...@gmail.com wrote: I personally would not be able to attend a mini-summit days before the regular summit. I would, however, support a mini-summit about a month after the regular summit, where the focus would be on implementing the designs

Re: [openstack-dev] [neutron][rootwrap] Performance considerations, sudo?

On Mar 6, 2014, at 3:31 AM, Miguel Angel Ajo majop...@redhat.com wrote: Yes, one option could be to coalesce all calls that go into a namespace into a shell script and run this in the ootwrap ip netns exec But we might find a mechanism to determine if some of the steps failed, and

Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?

On Mar 6, 2014, at 4:31 PM, Jay Pipes jaypi...@gmail.com wrote: On Thu, 2014-03-06 at 21:14 +, Youcef Laribi wrote: +1 I think if we can have it before the Juno summit, we can take concrete, well thought-out proposals to the community at the summit. Unless something has changed

Re: [openstack-dev] [neutron] Significance of subnet_id for LBaaS Pool

On Feb 25, 2014, at 1:06 AM, Rabi Mishra ramis...@redhat.com wrote: Hi All, 'subnet_id' attribute of LBaaS Pool resource has been documented as The network that pool members belong to However, with 'HAProxy' driver, it allows to add members belonging to different subnets/networks to a

Re: [openstack-dev] [Neutron][LBaaS] Object Model discussion

On Feb 21, 2014, at 1:29 PM, Jay Pipes jaypi...@gmail.commailto:jaypi...@gmail.com wrote: I disagree on this point. I believe that the more implementation details bleed into the API, the harder the API is to evolve and improve, and the less flexible the API becomes. I'd personally love to see

Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core

I’d like to welcome Oleg as member of the core Neutron team as he has received more than enough +1s and no negative votes from the other cores. mark On Feb 10, 2014, at 6:28 PM, Mark McClain mmccl...@yahoo-inc.com wrote: All- I’d like to nominate Oleg Bondarev to become a Neutron core

[openstack-dev] [Neutron] Nominate Oleg Bondarev for Core

All- I’d like to nominate Oleg Bondarev to become a Neutron core reviewer. Oleg has been valuable contributor to Neutron by actively reviewing, working on bugs, and contributing code. Neutron cores please reply back with +1/0/-1 votes. mark ___

Re: [openstack-dev] [Neutron][QA] Making tests symmetric again

On Feb 7, 2014, at 10:16 AM, Matthew Treinish mtrein...@kortar.orgmailto:mtrein...@kortar.org wrote: So the flag to make tenant isolation was always a temporary thing just for neutron so we could work out stabilizing things. It's been on by default for all the other jobs for as long as I can

Re: [openstack-dev] [Governance] Integrated projects and new requirements

On Feb 7, 2014, at 4:17 PM, Russell Bryant rbry...@redhat.commailto:rbry...@redhat.com wrote: On 02/06/2014 08:47 AM, Thierry Carrez wrote: Dina Belova wrote: Perhaps we should start putting each project on the TC agenda for a review of its current standing. For any gaps, I think we

Re: [openstack-dev] [Neutron] Adding package to requirements.txt

I’m interested to know why you are using urllib3 directly. Have you considered using the requests module? requests is built upon urllib3 and already a dependency of Neutron. mark On Feb 3, 2014, at 6:45 PM, Hemanth Ravi hemanthrav...@gmail.com wrote: Hi, We are in the process of

Re: [openstack-dev] [Neutron][Testr] Brand new checkout of Neutron... getting insane unit test run results

I’d rather us explicitly skip the tests if the module is not available. mark On Jan 13, 2014, at 3:39 PM, Collins, Sean sean_colli...@cable.comcast.com wrote: On Wed, Jan 01, 2014 at 07:56:22PM -0800, Clark Boylan wrote: It looks like the problem is that there is a dependency on pyudev

Re: [openstack-dev] [Neutron][IPv6] Subnet mode - API extension or change to core API?

On Jan 13, 2014, at 12:24 PM, Collins, Sean sean_colli...@cable.comcast.com wrote: Hi, I posted a message to the mailing list[1] when I first began work on the subnet mode keyword, asking if anyone had a suggestion about if it should be an API extension or can be a change to the core API.

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day

On Jan 9, 2014, at 7:46 AM, Sean Dague s...@dague.net wrote: I think we are all agreed that the current state of Gate Resets isn't good. Unfortunately some basic functionality is really not working reliably, like being able to boot a guest to a point where you can ssh into it. These are

Re: [openstack-dev] [Neutron] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

about to sign the contract for Salle du Parc at 3625 Parc avenue, a room in a residence of McGill University. Time: 9am - 5am I am expecting to see the following people in Montreal in January: Mark McClain Salvatore Orlando Sean Dague Matt Trenish Jay Pipes Sukhdev Kapur Miguel Lavelle

Re: [openstack-dev] [Neutron] Find the compute host on which a VM runs

Stefan- Your workflow is very similar to many other plugins. You’ll want to look at implementing the port binding extension in your plugin. The port binding extension allows Nova to inform Neutron of the host where the VM is running. mark On Nov 15, 2013, at 9:55 AM, Stefan Apostoaie

Re: [openstack-dev] [Neutron] New plug-ins requirements

On Nov 14, 2013, at 2:02 AM, Edgar Magana emag...@plumgrid.com wrote: I do agree with you. When I said in my first email little bit of guidance I mean the policy for Icehouse and moving forward. I do not want to make our PTL angry :-) I wouldn’t worry about making me angry. I officiated

Re: [openstack-dev] [neutron] [ipv6] IPv6 meeting - Thursdays 21:00UTC - #openstack-meeting-alt

On Nov 13, 2013, at 12:46 PM, Collins, Sean (Contractor) sean_colli...@cable.comcast.com wrote: On Wed, Nov 13, 2013 at 10:20:55AM -0500, Shixiong Shang wrote: Thanks a bunch for finalizing the time! Sorry for my ignorance….how do we usually run the meeting? On Webex or IRC channel?

[openstack-dev] [Neutron] Plugin and Driver Inclusion Requirements

tl;dr - The Neutron team has experienced tremendous growth in vendor plugins and drivers over the last few cycles. As a result of the growth, the Neutron team is implementing new requirements for plugin and driver code for Icehouse cycle to ensure continued code quality and stability. -

Re: [openstack-dev] [Neutron] IPv6 sub-team?

I definitely think this should be a standing Neutron sub team. mark On Nov 6, 2013, at 7:50 AM, Collins, Sean (Contractor) sean_colli...@cable.comcast.com wrote: Hi, Is there any interest in organizing a IPv6 sub-team, similar to how there are sub-teams for FwaaS, VPNaas, ML2, etc?

Re: [openstack-dev] Need suggestions and pointers to start contributing for development :

On Oct 11, 2013, at 9:14 AM, Dolph Mathews dolph.math...@gmail.com wrote: On Friday, October 11, 2013, Mayank Mittal wrote: Hi Teams, Please suggest and guide for starting to contribute in development. About me - I have been working on L2/L3 protocol, SNMP, NMS development and ready to

[openstack-dev] [Neutron] PTL Candidacy

Hi- I writing to announce my candidacy for the OpenStack Networking (Neutron) PTL. I am the current Neutron PTL. Our team continued to grow during the Havana cycle and both existing and new contributors worked to deliver double the number of blueprints than the previous release. Our vibrant

Re: [openstack-dev] [Neutron] Need some clarity on security group protocol numbers vs names

Names are not necessarily portable across implementations and this would be a major change to make this late in the cycle. At this point in the cycle, we need to focus on ensuring fixes minimize disruption. mark On Sep 11, 2013, at 6:03 PM, Arvind Somya (asomya) aso...@cisco.com wrote: Ok,

Re: [openstack-dev] [Neutron] Need some clarity on security group protocol numbers vs names

On Sep 11, 2013, at 1:46 PM, Akihiro Motoki amot...@gmail.com wrote: On Thu, Sep 12, 2013 at 12:46 AM, Justin Hammond justin.hamm...@rackspace.com wrote: As it seems the review is no longer the place for this discussion, I will copy/paste my inline comments here: I dislike the idea of

Re: [openstack-dev] [Neutron] New Plug-in development for Neutron

I think Gary and Kyle have answered this very well; however I do have a few things to add. It is definitely too late for Havana, so Icehouse is next available release for new plugins. I can work with you offline to find you a core sponsor. mark On Sep 10, 2013, at 9:37 AM, Kyle Mestery

Re: [openstack-dev] [Neutron] Bug #1209011

Carl- Thanks for pointing this out. I've fixed the bug status. mark On Sep 9, 2013, at 6:33 PM, Baldwin, Carl (HPCS Neutron) carl.bald...@hp.com wrote: Hi all, This bug was marked as fix released for H-3. However, the fix that was merged was reverted due to gate breakage. The patch

Re: [openstack-dev] [Neutron] Resource URL support for more than two levels

Stay tuned. There are folks working on a proposed set of API framework changes. This will be something that we'll discuss as part of deciding the features in the Icehouse release. mark On Aug 29, 2013, at 10:08 AM, Justin Hammond justin.hamm...@rackspace.com wrote: I find that kind of

Re: [openstack-dev] [Neutron][Climate] bp:configurable-ip-allocation

Nokolay- Expect to updated code posted soon for Havana. mark On Aug 22, 2013, at 12:47 AM, Nikolay Starodubtsev nstarodubt...@mirantis.com wrote: Hi, everyone! We are working on Climate, and we are interested in https://blueprints.launchpad.net/neutron/+spec/configurable-ip-allocation I

Re: [openstack-dev] proposing Alex Gaynor for core on openstack/requirements

+1 mark On Aug 16, 2013, at 11:04 AM, Doug Hellmann doug.hellm...@dreamhost.com wrote: I'd like to propose Alex Gaynor for core status on the requirements project. Alex is a core Python and PyPy developer, has strong ties throughout the wider Python community, and has been watching and

Re: [openstack-dev] Usage of mox through out the Openstack project.

On Jul 25, 2013, at 4:01 AM, Julien Danjou jul...@danjou.info wrote: On Wed, Jul 24 2013, Russell Bryant wrote: A practical approach would probably be: 1) Prefer mock for new tests. 2) Use suggestion #2 above to mitigate the Python 3 concern. 3) Convert tests to mock over time,

[openstack-dev] [Neutron] Proposal to add new neutron-core members

All- I'd like to propose that Kyle Mestery and Armando Migliaccio be added to the Neutron core team. Both have been very active with valuable reviews and contributions to the Neutron community. Neutron core team members please respond with +1/0/-1. mark

Re: [openstack-dev] [Neutron] Service Type Framework implementation

On Jul 9, 2013, at 5:37 PM, Nachi Ueno na...@ntti3.com wrote: We have two suboption for db api based solution Option4. REST API + DB with Preload with Conf https://docs.google.com/presentation/d/1v0nLTEsFOwWeYpYjpw4qe3QHB5lLZEE_b0TmmR5b7ic/edit#slide=id.gf14b7b30_00 so IMO, we can drop

Re: [openstack-dev] [Networking] Allocation of IPs

Here's the blueprint… https://blueprints.launchpad.net/quantum/+spec/configurable-ip-allocation On Jun 21, 2013, at 5:34 PM, Edgar Magana emag...@plumgrid.com wrote: Mark, Can you point me to the BP for this feature? I want to keep an eye on it. Thanks, Edgar From: Mark McClain

Re: [openstack-dev] [Networking] Allocation of IPs

the allocation for the IP? If the no allocation flag is enabled, all ports will have an empty value for IPs. It will increase the config parameters in quantum, should we try it? Edgar From: Mark McClain mark.mccl...@dreamhost.com Reply-To: OpenStack List openstack-dev@lists.openstack.org Date

Re: [openstack-dev] [Networking] Allocation of IPs

There's work under way to make IP allocation pluggable. One of the options will include not having an allocator for a subnet. mark On Jun 20, 2013, at 2:36 PM, Edgar Magana emag...@plumgrid.com wrote: Developers, So far in Networking (formerly Quantum) IPs are pre-allocated when a new port