n revived. Doing a full sync.
https://github.com/openstack/neutron/blob/ea8cafdfc0789bd01cf6b26adc6e5b7ee6b141d6/neutron/agent/l3/agent.py#L697
https://github.com/openstack/neutron/blob/ea8cafdfc0789bd01cf6b26adc6e5b7ee6b141d6/neutron/agent/l3/agent.py#L679
--
Sean M. Collins
_
/master/lib/neutron-legacy#L767
[2]: https://review.openstack.org/269560
[3]: https://review.openstack.org/273228
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
On Wed, Jan 27, 2016 at 04:24:00PM EST, Assaf Muller wrote:
> On Wed, Jan 27, 2016 at 4:10 PM, Sean M. Collins <s...@coreitpro.com> wrote:
> > Hi,
> >
> > I started poking a bit at https://bugs.launchpad.net/devstack/+bug/1535661
> >
> > We have rad
in the past, and we are attempting to change Neutron, in
order for things to Just Work™
[1]: http://lists.openstack.org/pipermail/openstack-dev/2016-January/084241.html
--
Sean M. Collins
__
OpenStack Development Mailing List
case of DRY that needs to be done. We should just set
it once *somewhere* and then communicate it to related OpenStack
components.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: o
e sake of sanity.
--
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/ope
You need to set path_mtu. https://review.openstack.org/#/c/267604/ sets
it now and defaults to 1500 - then Neutron calculates the overhead for
your tunnel protocol down to the appropriate value
--
Sean M. Collins
Just an FYI for anyone taking the Neutron piece, please feel free to
attend the upgrades subteam - we have a meeting today.
https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam
--
Sean M. Collins
__
OpenStack
Opened a bug to track this
https://bugs.launchpad.net/neutron/+bug/1537734
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
(what is this, an MTU for ants?).
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/c
ome other
> means, like AMQP, then yes, it could be a reasonable approach.
This was my thought. It should be configured on the server and then
distributed to the agents that support the option over the message bus.
--
Sea
Linux Bridge was a separate plugin, before it became an ML2
mechanism driver.
So let's make LB more like the ML2 mechanism driver it's supposed to be.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
-to-1400-via-etcneutrondnsmasq-neutronconf-per-daniels/
http://blog.systemathic.ch/2015/03/05/openstack-mtu-pitfalls-with-tunnels/
https://twitter.com/search?q=openstack%20neutron%20MTU
--
Sean M. Collins
__
OpenStack Development
IRC I advocated that the QoS work
should have been a small, narrowly defined DevStack plugin. Instead, we
now find ourselves where the kitchen sink has been thrown into this
thing.
Can we please take this all out of Neutron and put all these different pieces
into their own separate DevStack plugi
ng this repo or something like this to pick up more
recent packaged versions of components like Open vSwitch?
[1]: https://launchpad.net/cloud-archive
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
On Thu, Jan 14, 2016 at 03:32:21PM CST, Ben Pfaff wrote:
> On Thu, Jan 14, 2016 at 09:30:03PM +0000, Sean M. Collins wrote:
> > On Thu, Jan 14, 2016 at 03:13:16PM CST, Clark Boylan wrote:
> > > Forgive my ignorance, but if we are gating on OVS 2.0 that is because it
> &
On Thu, Jan 14, 2016 at 03:45:39PM CST, Clark Boylan wrote:
> On Thu, Jan 14, 2016, at 01:32 PM, Ben Pfaff wrote:
> > On Thu, Jan 14, 2016 at 09:30:03PM +0000, Sean M. Collins wrote:
> > > On Thu, Jan 14, 2016 at 03:13:16PM CST, Clark Boylan wrote:
> > > > F
. I should make some more silly comments to bump my stats!
Time to break out that cron job that just writes 'o/' to a socket! ;)
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage question
hen running our
Neutron jobs is that yes, we get new features, but yes we also get
the newest bugs and the configuration matrix for Neutron now gets a new
dimension of 'packaged OVS versus git commit SHA'
--
Sean M. Collins
_
On Wed, Jan 13, 2016 at 04:47:19PM CST, Sean M. Collins wrote:
> I'd prefer to see small, very specific DevStack plugins that have narrow
> focus, and jobs that need them for specific things adding them to their
> local.conf settings explicitly via enable_repo lines.
Sorry, enable_plu
On Mon, Jan 11, 2016 at 12:57:05PM PST, Clark Boylan wrote:
> On Mon, Jan 11, 2016, at 12:35 PM, Sean M. Collins wrote:
> > Nice find. I actually pushed a patch recently that we should be
> > advertising the MTU by default. I think this really shows that it should
> >
Nice find. I actually pushed a patch recently that we should be advertising the
MTU by default. I think this really shows that it should be enabled by default.
https://review.openstack.org/263486l
--
Sent from my Android device with K-9 Mail. Please excuse my
get_tenant_id_for_create
>
> Just out of curiosity, is it not standard practice that a plugin
> shouldn't use a private method?
+1 - hopefully decomposed plugins will audit their code and look for
other calls to priva
the connection, 5
minutes later.
http://logs.openstack.org/35/187235/12/experimental/gate-grenade-dsvm-neutron-multinode/984e651/logs/grenade.sh.txt.gz#_2016-01-08_20_13_40_040
--
Sean M. Collins
__
OpenStack Development
0s.
[1]: http://tech.paulcz.net/2016/01/openstacks-and-ecosystems/
[2]: https://terraform.io/docs/providers/openstack/r/fw_firewall_v1.html
[3]:
http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/api
No FwaaS meeting this week. I will be on PTO the week after. I'm OK with
skipping that week too, and starting back up the first week of January
if there are no objections.
--
Sean M. Collins
__
OpenStack Development Mailing
Nova,
so let us know what we can do to help raise awareness on both sides.
https://wiki.openstack.org/wiki/CrossProjectLiaisons#Inter-project_Liaisons
--
Sean M. Collins
__
OpenStack Development Mailing Lis
s behind the API is where products and projects can
differentiate.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
t an API. Especially when api-site and
networking API doc needs improvement.
Specs are a good starting point, but my hope would be that perhaps we go
back through the specs and add a note at the top pointing to the
maintained API documentation - once the feature has lan
Thanks for the advance notice. Sounds good to me.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
ot
> > maintained and the implementation may differ in some ways. The devref should
> > be kept current with refactorings, etc. of the implementation.
>
> Henry, I was also impressed by how clearly you communicated this.
> This ought to be included somewhere prominently in our
>
for the Tokyo social).
[1]: http://lists.openstack.org/pipermail/openstack-dev/2015-July/068859.html
[2]: https://review.openstack.org/205674
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions
On Mon, Dec 07, 2015 at 10:26:53PM EST, Sean M. Collins wrote:
> FWaaS for example is v2.0/fw/
Sorry - typo
v2_0/fw/
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscr
listed under v2_0, and do not need
> any separate Parent ID.
Just because "most" are under /v2_0 doesn't mean new ones should.
FWaaS for example is v2.0/fw/
I think it's better to be more explicit.
--
Sean M. Collins
_
On Fri, Dec 04, 2015 at 01:15:07PM EST, Sean Dague wrote:
> Is *not* always due to a failure.
Yep - sorry. Friday typos :)
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscr
f running swift on wheezy is still
> a thing people care about.
They would also need to backport a more recent version of Open vSwitch.
https://bugs.launchpad.net/devstack/+bug/1520338
I think it might be time to cut support, the list of packages that need
to be backported is only going to grow
-
On Mon, Nov 30, 2015 at 07:00:07AM EST, Sean Dague wrote:
> On 11/25/2015 11:42 AM, Sean M. Collins wrote:
> > The first run for the multinode grenade job completed.
> >
> > http://logs.openstack.org/35/187235/11/experimental/gate-grenade-dsvm-neutron-multinode/011124b/log
On Thu, Dec 03, 2015 at 10:58:07AM EST, Ihar Hrachyshka wrote:
> The thing I would like us to see enhanced is making sure that tags set to
> bugs are actively tracked by corresponding teams.
Thanks - you just reminded me to tag two bugs that I had just touched.
:)
--
Sean M. C
at it didn't require being a core reviewer.
I pushed a patch to our policy docs to help clarify that
https://review.openstack.org/253164
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
the
relationship between neutron-specs, RFE bugs, and some features being
documented in devref. Especially when a review includes the actual code,
then a new RST file in devref - wasn't that what specs were for?
--
Sean M. Collins
Was perusing the documentation again this morning and there is another
thing I found - you can call join() with the aliased=True flag to get
similar results.
Check out the "Constructing Aliases Anonymously" section.
http://docs.sqlalchemy.org/en/latest/orm/query.html
--
Sean
on bugs where I think I can contribute productively.
So - I think it has been effective. It's made me pay attention to it. :)
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
router_intf_qry:
> router_id =router.router_id
>
That looks pretty close. My only suggestion would be to try and see if
you can just alias it once, instead of twice. Basically see if it is
possible to replace al
to use the aliased() function - since
there are some examples that are similar to what you are trying to do -
check out the "Joins to a Target with an ON Clause" section in the first
link.
http://docs.sqlalchemy.org/en/latest/orm/query.html#sqlalchemy.orm.aliased
--
Sean
I'd like that to
> be explicitly recorded somewhere, and volunteer to do that. Not sure
> yet whether that should be in the Neutron devref, or in the networking
> guide - opinions welcome!
The Networking guide is part of the solution, but we also
me issue as your failed run - we didn't even get to the
upgrade phase - we failed on the initial resource creation phase, since
my new/ directories were totally empty except for localrc.
--
Sean M. Collins
__
OpenSta
On Wed, Nov 25, 2015 at 12:53:56PM EST, Armando M. wrote:
> On 25 November 2015 at 09:49, Sean M. Collins <s...@coreitpro.com> wrote:
>
> > Yeah looks like I read it wrong - the failure occurred during the
> > initial resource creation phase, based on comparing the lo
Yeah looks like I read it wrong - the failure occurred during the
initial resource creation phase, based on comparing the logs that Artur
posted.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage
I'll have to run some rechecks - but perhaps the issue is stable/kilo
faceplanting on creating the initial resources (which is what, a 30%
success rate? 1 out of 3 runs?) - the only run where we got far enough
to upgrade we were actually successful?
--
Sean M. Collins
checks out stable/liberty - so that's probably a version
string generated from the tip of stable/liberty
> I am really confused, I should probably stop asking questions and do some
> homework :)
No please keep asking - I think we're all learning things here. I'm
certainly no expert.
--
Sea
We'll start again next week at the 18:30 UTC time
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
are we testing all this code we have for
the IPAM feature if you can't install it in DevStack?
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.opensta
Ignore me, I'm not able to read and comprehend today. Sorry.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
Attach to the screen session Devstack sets up, and verify that the Nova
compute service is running. It's running in the screen session named
n-api.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage
On Mon, Nov 16, 2015 at 12:47:13PM EST, Vasyl Saienko wrote:
> [0] https://github.com/jumpojoy/neutron
The way you created the repository in GitHub, it is impossible to diff
it against master to see what you did.
https://github.com/jumpojoy/neutron/compare
--
Sean M. Coll
Chatted with Sean D. on IRC, pushed up a patch
https://review.openstack.org/#/c/245862/
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
d then later start
introducing the actual method bodies in small pieces with good unit
tests for each one. Small pieces. Tiny steps.
My $0.02 USD
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage ques
Networking-sfc is still just a shell - there is no functional code.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
like iPXE would be a good
investment long term, just based on those three features.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
f working on the following on Monday:
1) capture that somewhere in the upgrade docs we're putting together in
neutron's devref
2) Adding the stanza to project-config to get grenade running for
Neutron
3) Take a look at the patches that Armando linked a couple emails back
in this thread.
--
Sean M
On Fri, Nov 13, 2015 at 01:53:49AM EST, Paul Carver wrote:
> On 11/3/2015 1:03 PM, Sean M. Collins wrote:
> >Anyway, the code is currently up on GitHub - I just threw it on there
> >because I wanted to scratch my hacking itch quickly.
> >
> >https://github.com
hat if we
start pulling things into Neutron we lose valuable insight from people
who know a lot about Grenade.
Not to mention, Sean and I have had conversations about trying to get
Neutron as the default for DevStack - we can't just take our ball and go
in our own corner.
--
Sean M
Monday sounds good to me. 1500 utc sounds good too.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
-upgrade tag
https://review.openstack.org/239778 - Introduce assert:supports-rolling-upgrade
tag
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
get started.
[1]:
http://specs.openstack.org/openstack/ironic-specs/specs/approved/ironic-ml2-integration.html#assignee-s
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-req
Take all the time you need, Neutron can wait, family is more important.
Take care.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
s own endpoint and repo, and have
stakeholders from other projects, not just networking-sfc. That will
take time and quite a bit of wrangling, so I'd like to defer that for a
bit and just work on all the services having the same data model, where
we can make changes quickly, since they are not visi
Learn from my mistake, check your calendar for the timezone if you've
created an event for the weekly meetings. Google makes it a hassle to
set things in UTC time, so I was caught by surprise by the FwaaS meeting
due to the DST change in the US of A.
--
Sean M. Collins
On Wed, Nov 04, 2015 at 07:25:24AM EST, Sean Dague wrote:
> On 11/02/2015 10:36 AM, Sean M. Collins wrote:
> > On Sun, Nov 01, 2015 at 10:12:10PM EST, Davanum Srinivas wrote:
> >> Sean,
> >>
> >> I typically switch off screen and am able to redirect logs
s it becomes super popular I think it's fine to just discuss on
#openstack-neutron.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?s
discussion.
--
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
/source/usage.rst
It's very basic, it was just me hacking away at a proof of concept to
demonstrate that what I was proposing was possible, that we didn't need
a single database table with 10+ columns.
--
Sean M. Collins
Cool. I plan on attending, now that I have a config for running DVR in my local
lab.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
I want screen to run, and not
log the output to files, since I have a tiny 16GB ssd card on these NUCs
and it fills it up if I leave it running for a week or so.
--
Sean M. Collins
__
OpenStack Development Mailing List (no
1]: https://etherpad.openstack.org/p/FWaaS_with_DVR
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstac
t
handle the issue of the log file growing in size.
I mean I guess the real answer is to configure logrotate. ugh.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On Mon, Nov 02, 2015 at 10:43:45AM EST, Davanum Srinivas wrote:
> Sean,
>
> ah. so the tip about LOGDIR to /dev/null may work for you
>
That's not going to work. LOGDIR is used in multiple mkdir calls.
--
Sea
Hi,
The docs right now are a little unclear about if it is possible to stop
logging the output of all the screen sessions to the local filesystem.
It has a tendency to fill up my filesystem on my little NUCs :(
--
Sean M. Collins
Due to the summit.
--
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
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
;
> I think Kilo did not have this problem.
>
Ok. I have assigned myself the bug. I will be sightseeing with my partner
Caroline in Tokyo next week before the summit, so it may take me a
little bit of time to get around to it, but I will try and follow up on
the bug after the summit.
-
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 easier :)
--
Sean M. C
I believe that pulling a localrc off a CI result is tribal knowledge. It can be
done, but most likely it's a trick that is only known by someone who has been
involved in OpenStack for a long time.
--
Sent from my Android device with K-9 Mail. Please excuse my
this
case, with any authority. I would imagine so - but you'd have better
luck on the ops list for specific controllers
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
ge is required.
> Good. I was afraid somebody would tell me there is no point in using OVS
> in a single-node setup. I will revisit this after settling the issues
> above.
Eventually I'll get around to writing a LinuxBridge guide. Maybe after
Tokyo.
Take a look at some of the patches
dedicated interface (so two total interfaces).
The Q_USE_PROVIDERNET_FOR_PUBLIC switch configures part of what is
required, but there may be other pieces if you only have one physical
interfaces.
--
Sean M. Collins
__
where they ran into the issue of network names and uniqueness.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
Please see my response here:
http://lists.openstack.org/pipermail/openstack-dev/2015-October/076251.html
In the future, do not create multiple threads since responses will get
lost
--
Sean M. Collins
__
OpenStack
ting for IPV6_ROUTER_GW_IP with
> something dug out of Neutron. That went wrong. It replaced my setting
> with fddf:2::2, but that address was already in use by something else.
OK - I'm not sure what your networking layout is like on your DevStack
node, and frankly I think we need to back u
8
If I understand your message correctly, I disagree that we should be
moving all the DevStack support for Neutron out of DevStack and making
it a plugin. All that does is move the mess from one corner of the room,
to another corner.
-
On Thu, Oct 01, 2015 at 11:05:29AM EDT, Kyle Mestery wrote:
> On Thu, Oct 1, 2015 at 9:57 AM, Sean M. Collins <s...@coreitpro.com> wrote:
>
> > On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote:
> > > - more changes with less infra tinkering! neutron dev
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 Development
view provide a better way to distribute
> and update this knowledge…
+1 - I've fallen out of love with Wikis for this exact reason.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
, as a L2
broadcast segment, implies that yes this should be possible.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubsc
You need to remove your Workflow-1.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org
Brent is our Neutron-Nova liaison - can someone from the SR-IOV team
please respond?
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
as a
replacement for Nova-Network in the future.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
a significant impact on our ability to recommend Neutron as a
replacement for Nova-Network in the future.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
vice work with IPv6 we'd be
supporting two implementations - the one we came up with and one for
supporting the way Amazon implemented it.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubsc
nStack branded APIs is a lost
opportunity to differentiate OpenStack from other projects, as well as
Amazon AWS.
Thanks for reading, and have a great holiday.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage q
101 - 200 of 294 matches
Mail list logo
