On Fri, Oct 16, 2015 at 11:36:13AM EDT, Salvatore Orlando wrote:
> It might also make sense to ask contributors to resume the habit of tagging
> bugs with 'backport-potential' even if not in the RC period.
I like this idea because it'll make Ihar's job easi
My only concern is how tightly coupled the FwaaS code is with the L3 agent. We
have a bug already filed because the L3 agent inheriting the FwaaS code causes
circular dependencies, but it also be the reason why FwaaS co-gates with the
main Neutron repo.
Let's try and fix the tight coupling of t
| fc618c8151ad4c53b0fccbca89502b8e |
+---+--+
Basically, this boils down to the fact that with PHYSICAL_NETWORK,
DevStack populates the bridge_mappings file, while
PUBLIC_PHYSICAL_NETWORK d
ally become automated!
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailm
a WIP patch for
fuel-web. Please contact me if you want to help contribute to the work.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
GRE, and
>> nova-network are shown to the user.
>>
>> I am currently working on this blueprint and have a WIP patch for
>> fuel-web. Please contact me if you want to help contribute to the
>work.
>>
>> --
>> Sean M. Collins
>>
>>
>
the value for PHYSICAL_NETWORK and PUBLIC_PHYSICAL_NETWORK will be different?
Perhaps we can change the default value for PUBLIC_PHYSICAL_NETWORK from
"public" to just pulling in what PHYSICAL_NETWORK is set to, if it is
set?
--
Sean M. Collins
__
Can we update the vxlan bp to target it to 7.0? The series goal is still
set to 6.1.x
https://blueprints.launchpad.net/fuel/+spec/neutron-vxlan-support
Thanks
--
Sean M. Collins
__
OpenStack Development Mailing List (not
On June 2, 2015 2:57:29 PM EDT, Andrew Woodward wrote:
>Updated
>
>Sean, I see that there is no spec linked in gerrit or the BP do we have
>one?
>
>
>On Tue, Jun 2, 2015 at 11:07 AM Sean M. Collins
>wrote:
>
>> Can we update the vxlan bp to target it to 7.0? Th
ate is
down, which really messes things up when you try and add the FIXED_RANGE route.
I'm looking into that issue, perhaps it will shed light on yours as
well.
--
Sean M. Collins
__
OpenStack Development Mailing Lis
#x27;d actually prefer we not change PHYSICAL_NETWORK ->
PUBLIC_PHYSICAL_NETWORK since that may just confuse people more. What if
your machine is not on a public network? What if it's just an isolated
networking lab that you want your instances to just plug into? I think
the &quo
On Mon, Jun 08, 2015 at 01:38:28PM EDT, Jay Pipes wrote:
> On 06/08/2015 12:16 PM, Sean M. Collins wrote:
> >I'd expect the above, where we pull the setting from PHYSICAL_NETWORK.
> >Then perhaps in the lib/neutron-legacy define
> >
> >PHYSICAL_NETWORK={$PHYSICA
y-return ("http://docs.openstack.org/ext/";
--
vlantransparent.py:def get_namespace(cls):
vlantransparent.py-return
"http://docs.openstack.org/ext/vlantransparent/api/v1.0";
I believe that they
On Tue, Jun 09, 2015 at 05:21:18PM EDT, Kevin Benton wrote:
> I wasn't planning on wiping them out for now since I'm leveraging a lot of
> the extension loading that exists so someone can remove the namespaces if
> they want.
OK - I'll take it on if there's no ob
k Dr. Jens Rosenboom for the work that I borrowed
from him.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.ope
why
maintain two separate agent implementations when quite a bit of what
they do is functionally identical?
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...
g run.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
; us to have the discussion on the bug there too.
I didn't see one, so I filed one.
https://bugs.launchpad.net/neutron/+bug/1468803
Hopefully I did it right?
--
Sean M. Collins
__
OpenStack Development Mailing Li
s/networking/2015/networking.2015-06-22-21.00.html
[1]: https://en.wikipedia.org/wiki/Oracle_America,_Inc._v._Google,_Inc.
[2]:
https://aws.amazon.com/about-aws/whats-new/2011/05/24/elb-ipv6-zoneapex-securitygroups/
--
Sean M. Collins
___
I know historically there were postgres jobs that tested things, but I
think the community moved away from having postgres at the gate?
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions
on that will be used to flesh out a true vendor-neutral API
(as I understand Mike Perez's position, and agree with!).
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscri
point it does hijack the original
intent of the thread. Which is now happening.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.open
eally!
Yes, it's a lot of work, but without that, as I think others have
stated - where's the OpenStack part?
Like that Wendy's commercial from way back: "Where's the beef?"
--
Sean M. Collins
_
02-18T01:18:32
[4]:
http://logs.openstack.org/78/279378/9/experimental/gate-grenade-dsvm-neutron-multinode/40a5659/console.html#_2016-02-17_22_37_33_277
[5]: https://review.openstack.org/#/c/279721/
--
Sean M. Collins
__
OpenStack
Jay Pipes wrote:
> From our Mirantis team, I've asked Sergey Belous to handle any necessary
> changes to devstack and project-config (for a functional test gate check
> job).
I'll keep an eye out in my DevStack review queue for these patches and
will make sure to review them pr
reached out to during
these past months when I got stuck on this. Ihar, Matt K, Kevin B,
Armando - this is a huge win.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
- so the partial jobs are going to
reflect the reality on the ground better.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
Can you provide the output of
"ip route show"
Was this after a unstack.sh that failed?
It could be https://bugs.launchpad.net/devstack/+bug/1423020 popping up
again
--
Sean M. Collins
__
OpenStack Developme
dev eth0
> 172.18.20.0/24 dev eth0 proto kernel scope link src 172.18.20.23
> 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
Was this after you did an unstack? Or right after stack.sh fails?
--
Sean M. Collins
_
everything, and then filter using the guest - then fine. That's their
prerogative. All they've done is change where their security policies
are implemented. Instead of a REST API they want to do it directly on
their guest.
--
Sean M. Collins
erence between Nova-Net and Neutron, where security group names
are not unique in Neutron - hence the problem above.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
oting on a v4 network, which has NAT enabled.
Many public providers, the network you attach to is publicly routed, and
with the move to IPv6 - this will become more common. Remember, NAT is
not a security device.
--
Sean M. Collins
_
Clark Boylan wrote:
> On Wed, Mar 2, 2016, at 09:38 AM, Sean M. Collins wrote:
> > Kevin Benton wrote:
> > > * Neutron cannot be trusted to do what it says it's doing with the
> > > security
> > > groups API so users want to orchestrate firewalls directl
sridhar basam wrote:
> This doesn't sound like a neutron issue but an issue with how the
> conntrack module for GRE changed in the kernel in 3.18.
>
>
> http://comments.gmane.org/gmane.comp.security.firewalls.netfilter.general/47705
>
> Sri
Oooh! Wicked nice fin
t's put together a bug and tackle this in Newton?
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://list
I probably speak for all FwaaS cores when I say - "Welcome!"
Frankly I had just assumed he had core privileges for our repo anyway
via an inherited ACL.
--
Sean M. Collins
__
OpenStack Development Mailing Lis
ing complete or deep enough. That’s
> something we will look into improving at the start of the N cycle.
If I can make a suggestion, let's put it in the operations guide. I
think we can add a Neutron specific chapter - and I have a review up as
WIP to remind myself:
https://review.openstack
making it
voting and running on every patchset (sorry, not sorry).
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?sub
the old docbook
source - not the RST conversion.
I cheated a bit - I used Ihar's writeup in devref and directly
linked to it in the operations guide.
https://review.openstack.org/#/c/291784/
--
Sean M. Collins
__
O
OVS stuff that is currently in Neutron's DevStack plugin
moving over to this plugin.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...
breakage.
I have filed a bug with all the details of my findings, but I wanted to
bring it to the attention of a wider audience.
https://bugs.launchpad.net/python-novaclient/+bug/1561938
How do we proceed? Revert ae598280 ?
--
Sean M. Collins
intention is to replace the one file that uses Mako with Jinja2, to
keep things consistent.
Thoughts?
[1]: https://review.openstack.org/#/c/128259/
[2]:
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/db/migration/alembic_migrations/script.py.mako
--
Sean M. Collins
Sorry, I should have done a bit more grepping before I sent the e-mail,
since it appears that Mako is being used by alembic.
http://alembic.readthedocs.org/en/latest/tutorial.html
So, should we switch the radvd templating over to Mako instead?
--
Sean M. Collins
//github.com/sc68cal/chef-devstack/blob/master/recipes/default.rb#L50
[1]: http://docs.openstack.org/admin-guide-cloud/content/install_neutron-l3.html
[2]: https://review.openstack.org/#/c/153208/
--
Sean M. Collins
__
OpenStack
o create a CIDR of ::/64 to satisfy the
Neutron core API's requirement that a subnet MUST have a CIDR when creating,
but I think that in the case of prefix delegation we shouldn't expose this
sharp edge to the user by default.
Does this make se
a year
ago (
http://lists.openstack.org/pipermail/openstack-dev/2014-March/030581.html),
and I have some additional thoughts on how the REST API would behave,
but at this stage of the game I think the subnet allocation REST API is
a superior spec.
ilo/nfv-vlan-trunks.html#rest-api-impact
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/
eadline and was landed in Juno, so
for a time the attributes were hidden from users.
https://review.openstack.org/#/c/85869/
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: op
Hi,
My apologies for the short notice, but I will not be able to run the
IPv6 subteam meeting tomorrow. If one of the attendees who has items to
discuss would like to run the meeting in my absence, that would be
great!
--
Sean M. Collins
default, by using provider networks or flat networking.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsub
people want OVS get OVS and linuxbridge
people get linuxbridge and we can all live happily ever after. :)
[1]:
https://github.com/openstack-dev/devstack/blob/master/lib/neutron_plugins/ml2#L25
[2]:
https://github.com/openstack-dev/devstack/blob/master/lib/neutron_plugins/ml2#L21
be a
big part of my speaking session with Carl[3].
[1]:
http://specs.openstack.org/openstack/neutron-specs/specs/kilo/subnet-allocation.html
[2]: http://lists.openstack.org/pipermail/openstack-dev/2015-March/059329.html
[3]:
https://openstacksummitmay20
> Quick update about OVS vs LB:
> Sean M. Collins pushed up a patch that runs CI on Tempest with LB:
> https://review.openstack.org/#/c/168423/
>
> So far it's failing pretty badly.
I haven't had a chance to debug the failures - it is my hope that
perhaps there are ju
d to write a quick status update and publicly thank Dr.
Rosenboom. We are making excellent progress, and a majority of tests at the gate
are passing for Linuxbridge as the default in DevStack.
--
Sean M. Collins
__
OpenStack
I am on PTO - if someone else wishes to chair the weekly meeting please feel
free to do so.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.__
OpenStack Development Mailing List (not for usage questions
king at the innards of Nova-Network or
Neutron or looking to create a "production-like" DevStack
will be consulting documentation for configuration details.
--
Sean M. Collins
__
OpenStack Development
tyCodeSprint
I won't be able to attend in person, but I am interested in
participating. Will there be equipment available for remote attendees?
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage
efault, we should use the extra_dhcp_opts API extension
to set the IPXE tag.
http://specs.openstack.org/openstack/neutron-specs/specs/api/extra_dhcp_options__extra-dhcp-opt_.html
Thoughts?
--
Sean M. Collins
__
OpenStack D
/174693/
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
ed in also helping this effort, who could
do the reverse (Sit in on Neutron meetings, field Nova questions).
Thank you, and I look forward to working with everyone!
--
Sean M. Collins
__
OpenStack Development Mailing List (not
This is fantastic. Thank you so much for working on this Jens!
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subjec
The links for the developer documentation are currently broken.
https://software.mirantis.com/mirantis-openstack-fuel-plug-in-development/
Links to:
http://docs.mirantis.com/openstack/fuel/fuel-6.0/plugin-dev.html#developing-a-plug-in-for-fuel
Where can I find the documentation?
--
Sean M
a patch to the install guide fixing the convention, and
will go through and fix other instances.
[1]: https://www.brainyquote.com/quotes/quotes/r/ralphwaldo136909.html
--
Sean M. Collins
__
OpenStack Development Mailing Li
Oh, I should actually mention which way I think we should go with.
RegionOne should be the convention.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
RFACE
(depending on the mechanism driver) while also still using settings that
reflect our configuration at the gate.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
agenda of the main
meeting.
Unless there is any pressing business, I believe that we will not need a
recurring meeting, and tomorrow's meeting is cancelled.
As always, I am in #openstack-neutron and happy to help.
Thank you,
Sean
--
Sean M. Co
I think that Neutron exposes enough primitives through the API that
advanced services for handling your transition technique of choice could
be built.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage
x27;ve been listening to
my own advice and making the Ironic job explicitly set the OVS agent for
Neutron.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
on the wiki,
https://wiki.openstack.org/wiki/CrossProjectLiaisons#Inter-project_Liaisons
We still need a Nova liaison to sign up, to help me with the Nova/Neutron
cross project effort. If you are interested, please reply and replace
the "Volunteer Needed" sections in th
majority of an application's logic was
embedded in huge stored procedures and database triggers - so I'm a bit
biased.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubs
y I'm really hoping that with the new lib/neutron we can just
move away from this mess that we've got and start fresh.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
Also I was the one who approved the original patch, so the fault rests
on my shoulders. My apologies.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
For some reason I installed the newer version but still the version
string reports
Gertty version: 1.1.1.dev24
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
+1 on this plan too, if the +2's I've been slinging haven't made it
obvious :)
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
> OSIC cloud (that runs Neutron on IPv6) and that had an impact on the
> overall sluggishness of the gate [2]. Once all of the fixes are in, we
> should be back in business...until the next fire!
IPv6 only OpenStack installations sort of snuck u
ect suffers the same
organizational dysfunction as my previous jobs, but just overall they're
hard to debug and maintain and I don't like to use them.
/rant
--
Sean M. Collins
__
OpenStack Development Mailing List
08-30_18_56_58_838512
[4]:
http://logs.openstack.org/01/362901/1/check/gate-shade-dsvm-functional-neutron/9698d83/logs/devstacklog.txt.gz#_2016-08-30_18_46_38_671
--
Sean M. Collins
__
OpenStack Development Mailing List
Hey all,
Sorry for screwing up the gate - thankfully with the linuxbridge job
being in the check queue for DevStack we'll prevent me from making any
more oopsies.
--
Sean M. Collins
__
OpenStack Development Mailing
Thanks for all your hard work - I remember the Bad Old Days when there
was little to no documentation on anything in OpenStack. We are in a
much better place, thanks to your work.
--
Sean M. Collins
__
OpenStack
ng memory) in VBox so that I could re-run the upgrade
quickly. Worst case perhaps set up a 3rd party CI system that could use
that trick? Just throwing ideas out there.
Thoughts?
--
Sean M. Collins
__
OpenStack Development
o get that done (it's been an action item in our meetings for a few weeks,
> but hasn't landed just yet). If you have any questions or would like to get
> involved feel free to stop by and discuss in the #openstack-ansible channel
> on freenode.
>
Thanks
--
Sean M. Collins
I don't like how it's adding more conditionals and complexity to an
already fairly complex shell script. I've commented as such on the
review.
--
Sean M. Collins
__
OpenStack Development Mailing List
guration strategy before we start throwing things into
devstack-gate
My $0.02
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.o
es we added a "_upgrade" boolean var that is
> set when the upgrade job is run via tox - so feel free to take a look there.
Ah OK I see now.
I guess what I'm driving at, is how do we get automated coverage for the
full end-to-end upgrade, so that issues[1] that I uncovered during
le.
OK - is there any way that I can assist?
What about the challenges I discussed in my initial mail related to
long AIO build times etc..?
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage ques
ob/8740b6075b53e3c9bfda76d022fcc53904594e9c/devstack-vm-gate.sh#L121
[5]:
https://github.com/openstack-infra/devstack-gate/blob/8740b6075b53e3c9bfda76d022fcc53904594e9c/devstack-vm-gate.sh#L265
[6]: https://review.openstack.org/#/c/394895/
--
Sean M. Collins
_
can look
> into ways we can ensure this gets run, and what options we have.
Excellent. Thanks for all the info. I'm going to start poking around at
the gate-check-commit script and see if I can build up an AIO
te-openstack-ansible-openstack-ansible-upgrade-ubuntu-xenial-nv/ac09458/console.html#_2017-01-11_21_13_55_572404
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...
quot;""
We have a guide that sort of fits this usecase:
http://developer.openstack.org/firstapp-libcloud/
The networking section, can always use improvement:
http://developer.openstack.org/firstapp-libcloud/networking.html
--
Sean M. Collins
_
will work on
cleaning it up and fixing the errors (it might just need a recheck?)
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?
That is great news! Congrats!
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
Sean Dague wrote:
> I'll probably still default this to python3, it is the future direction
> we are headed.
Works for me :)
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
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
ab
Check out the networking guide.
http://docs.openstack.org/newton/networking-guide/
http://docs.openstack.org/newton/networking-guide/deploy-ovs.html
http://docs.openstack.org/newton/networking-guide/config-sriov.html
--
Sean M. Collins
_
such that we don't like these kind of patches, but I
couldn't find the mailing list thread where we last had this discussion.
https://review.openstack.org/#/c/343133/
Anyway, yeah this kind of thing is really annoying and burns a ton of
resources for no good reaso
3openstack-trove.2016-09-30.log.html#t2016-09-30T17:53:08
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http:/
so
far
[2]:
http://codesearch.openstack.org/?q=ml2_config.cfg.CONF.set_override&i=nope&files=&repos=
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsub
/neutron-multinode-jobs-newton
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
ds that we use for our testing infrastructure.
https://github.com/kubernetes/kubernetes/issues/12083
Obviously since k8s is written in Go, they can't really use Shade out of
the box - so this new project you are working on is *exactly* what the
doctor ordered.
--
s://git.openstack.org/openstack/neutron
OVS_BRANCH="v2.6.0"
I haven't tried it locally, but I think that's the idea.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage q
201 - 300 of 301 matches
Mail list logo
