s.
I didn't emerge from the void, fully formed, as a Neutron developer. I
was part of a team that had pain points in Neutron that we needed to
alleviate, so we jumped into the Neutron community, participated in
the weekly IRC meetings, filed bugs, started contributing patches,
etc...
So w
a full disk.
--
Sean M. Collins
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
e manual configuration?
--
Sean M. Collins
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
re is a lot that I
> think the group can help out with to make sure we capture what we get via
> etherpads and turn them into "Blueprints", "Bugs", etc so we can help
> follow-up with projects and track them for the entire Operators group.
I think this is a great idea.
because
obviously they are. But an RFE bug and coming to the midcycle is part of
Neutron's development process. Not a working group.
--
Sean M. Collins
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://list
volved with in the Mitaka cycle, when
it comes to Neutron and upgrades (https://review.openstack.org/304181)
--
Sean M. Collins
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Kilo is in the security supported stage of the lifecycle.
http://releases.openstack.org/
So, unless it is a security bug, I do not believe that this will be
able to be backported.
--
Sean M. Collins
___
OpenStack-operators mailing list
OpenStack
.
Please take a look, and if you have thoughts you'd like to share, post
them on openstack-dev
http://lists.openstack.org/pipermail/openstack-dev/2016-March/087982.html
--
Sean M. Collins
___
OpenStack-operators mailing list
OpenStack-oper
ll
supported releases in upstream, and for anyone they're selling LTS-like
support, fixing it in their distro release.
--
Sean M. Collins
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
-operators/2015-August/007976.html
[6]: http://eavesdrop.openstack.org/#Firewall_as_a_Service_(FWaaS)_Team_Meeting
--
Sean M. Collins
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailma
To help kick off this topic, the Neutron team has been tracking some
performance profiling in this etherpad.
https://etherpad.openstack.org/p/router-scheduling-performance
--
Sean M. Collins
___
OpenStack-operators mailing list
OpenStack-operators
On Wed, Aug 05, 2015 at 03:26:24AM EDT, Mike Spreitzer wrote:
> "Sean M. Collins" wrote on 08/04/2015 10:38:26 PM:
>
> > We have adapted the contents of that wiki page into the networking
> > guide, however I have not seen any work in the Juno release
[Resending this since I didn't CC the list the first time]
We have adapted the contents of that wiki page into the networking guide,
however I have not seen any work in the Juno release for IPv6 only networking.
Brian Haley and I had a talk submission for Tokyo about work that has been done
du
Most likely by querying the Nova or Neutron mysql/pgsql database
directly.
--
Sean M. Collins
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
is the 3rd item on our priority list.
https://etherpad.openstack.org/p/YVR-nova-network
If anyone else wishes to volunteer, now is the time.
Thanks
--
Sean M. Collins
___
OpenStack-operators mailing list
OpenStack-operators@lists.ope
ion, I'll be sure
to add a section on dual stacking.
https://review.openstack.org/#/c/181049/
It will eventually appear on http://docs.openstack.org/networking-guide/
if all goes to plan
--
Sean M. Collins
___
OpenStack-operators mailing
16 matches
Mail list logo
