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
n
EC2 and how to make the Metadata API service 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 Developm
Putting improvements in APIs that came from
somewhere else, instead of creating new OpenStack 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
It's not a case of cloud-init supporting IPv6 - The Amazon EC2 metadata API
defines transport level details about the API - and currently only defines a
well known IPv4 link local address to connect to. No well known link local IPv6
address has been defined.
I usually recommend config-drive for
6to4 is a whole different story. I'd prefer to avoid it unless there are
seriously compelling reasons to support it. I think dual stack is the
way to implement IPv6 support in Fuel.
--
Sean M. Collins
__
Open
mostly just be working on enabling IPv6 in all the components. Stretch
goal will be for Fuel to not require IPv4 at all so that in the future
we can deploy it in IPv6 only environments.
--
Sean M. Collins
__
OpenStack Development
Do you have a known good commit for the FwaaS repo? Or Neutron? Perhaps you can
run a git-bisect to find the commit that introduced. Labor intensive, but I did
a little digging in FwaaS and didn't see anything that was obvious.
--
Sent from my Android device with K-9 Mail. Please excuse my brevi
with isc-dhcpd. Which is no small task,
I can imagine.
The spec review has links to a post I made on the dnsmasq mailing list
to see if there is anyone there that can answer my question.
--
Sean M. Collins
__
OpenStack
Ah, I did not have enough coffee, my control node wasn't synced and
didn't pick up PHYSICAL_NETWORK - that'll do it. Now I look like a
moron.
Sorry for the panic I may have caused
--
Sean M. Collins
__
OpenSt
17202
--
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
the easy way to fix.
--
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
On August 22, 2015 11:58:03 AM EDT, Monty Taylor wrote:
>On 08/21/2015 03:33 PM, Jay Pipes wrote:
>> On 08/21/2015 02:34 PM, Sean M. Collins wrote:
>>> So - the tl;dr is that I don't think that we should accept inputs
>like
>>> the following:
>>>
>
for more information.
>>> import netaddr
>>> a = netaddr.IPNetwork("1", implicit_prefix=True)
>>> a
IPNetwork('1.0.0.0/8')
>>> a = netaddr.IPNetwork("1", implicit_prefix=False)
>>> a
IPNetwork('1.
0/y -> 192.168.0.0/16
x.x.x.0/y -> 192.168.0.0/24
--
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
On Thu, Aug 20, 2015 at 06:55:12AM EDT, hoan...@vn.fujitsu.com wrote:
> Hi Kye Mestery [PTL],
> CC: Sean M. Collins [FWaaS chair],
> CC: All,
>
> According to the last FWaaS IRC weekly meeting, the "Logging API for SG and
> FW rules" feature will be reviewed an
ystem.
We are testing dual stack
https://review.openstack.org/#/c/160856/
Have they found gaps in our coverage?
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: open
o say hello and bring up anything they've wanted to discuss.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
ike described in
[1], and then consume the SFC API in the backend.
At the very least, we're going to have lots to talk about in Tokyo :)
[1]:
http://specs.openstack.org/openstack/neutron-specs/specs/kilo/fwaas-router-inser
ck/neutron,access
--
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
Jenkins came back with a +1 about 20 minutes after your +1 - see if you
can +2 it now? Totally a guess.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
We're down to one last connected user in #openstack-fwaas - hold off on
reconnecting until further notice - we're close to getting OP so we can
register the channel.
--
Sean M. Collins
__
OpenStack Development Ma
re-think my -1, and we may need
to restore it.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.open
AC.
Ideally we'd alternate, with the odd week being the current time, and
the even week being the new APAC friendly time.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
On August 13, 2015 3:45:03 AM EDT, Robert Collins
wrote:
>tl;dr - developers running devstack probably want to be using
>USE_CONSTRAINTS=True, otherwise there may be a few rough hours today.
>[http://lists.openstack.org/pipermail/openstack-dev/2015-July/068569.html]
>
>
>Apparently some third par
I'm also working to register #openstack-fwaas with Freenode's ChanServ -
so if your IRC client is configured to automatically connect to it,
disable it for a day while we regain OP for the channel and register it.
--
Sean
) please review:
https://review.openstack.org/212595
https://review.openstack.org/212600
https://review.openstack.org/212606
https://review.openstack.org/212607
Thanks!
--
Sean M. Collins
__
OpenStack Development Mailing
[reformatted and infra tag added]
On Tue, Aug 11, 2015 at 07:32:34PM EDT, Salvatore Orlando wrote:
> On 12 August 2015 at 00:21, Sean M. Collins wrote:
>
> > Hello,
> >
> > Today has been an exciting day, to say the least. Earlier today I was
> > pinged on IRC ab
7;m not
sure if this will fix the problem - https://review.openstack.org/211677
- so I bumped it out of the merge queue when my anxiety reached maximum.
I'm just not confident enough about my knowledge of the FwaaS codebase
to really be making these kinds of changes.
Is there anyone that has a
free
for all that is the wiki
/rant
--
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
ap/commit/36a068cf3d3d6930ab9330efb099cd95a84ca785#diff-0445dd61b516b3357ecf54d6e4609e0fR76
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.
results soon.
https://review.openstack.org/#/c/208666/
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack
st my thoughts over a cup of coffee - someone shoot holes
in my thinking :)
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
On Mon, Jul 20, 2015 at 10:19:02AM EDT, Jim Rollenhagen wrote:
> On Mon, Jul 20, 2015 at 12:56:10PM +0000, Sean M. Collins wrote:
> > On Sun, Jul 19, 2015 at 02:26:32PM EDT, Jim Rollenhagen wrote:
> > > For a little background, this patch came from code that is running in
>
king-sfc and packet forwarding APIs, to see where we
have commonality. I think Cathy's initial e-mail may have ruffled
feathers - and I'd like to smooth them out again. I think the statement
"we only need one API" is far too premature.
Let's play nice with the oth
ged and maybe get
up into the 90% success rate I'll take off the WIP and solicit feedback
https://review.openstack.org/205674
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubs
mplify the API to remove these
multi-step, multi-api calls. Fixing it in the CLI only makes it easy for
those that are using that specific CLI, and leaves everyone else out in
the cold.
--
Sean M. Collins
__
OpenStack De
ained, compared to files in the code repo
(hopefully).
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
ource tree published - most likely to
docs.openstack.org/developer
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
/
At least there, changes can be reviewed by others - the problem with the
wiki is it can be changed without any review. At least with
neutron-specs it's versioned and there is discussion that is
captured and preserved.
I'm +1 on cleaning/deleting stuff from the wiki about the old SFC API
lan transparent API extension, or are you
using it currently?
http://specs.openstack.org/openstack/neutron-specs/specs/liberty/vlan-aware-vms.html
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage que
to take steps to improve it.
--
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/li
that you should go ahead and
unilaterally approve your own patch. That's not a way to build a
commmunity project.
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-d
ented on the review, but the provider network API extension
is admin only, most likely for the reasons that I think someone has
already mentioned, that it exposes details of the phyiscal network
layout that should not be exposed to tenants.
art creating RFE
bugs with the usecases and continue discussion there.
[1]: https://etherpad.openstack.org/p/LBaaS-FWaaS-VPNaaS_Summer_Midcycle_meetup
[2]: https://etherpad.openstack.org/p/fwaas_use_cases
[3]: https://etherpad.openstack.org/p/fwaas-api-evolut
an API that is
named the same as something in AWS - and it is meant for more complex
usecases.
http://lists.openstack.org/pipermail/openstack-dev/2015-June/068319.html
--
Sean M. Collins
__
OpenStack Development Mailing List (n
Let's keep it at >4 weeks without comment, and Jenkins failed - similar
to the script that Kyle Mestery uses for Neutron. In fact, we could
actually just use his script ;)
https://github.com/openstack/neutron/blob/master/tools/abandon_old_reviews.sh
--
Sean M.
.openstack.org/#/c/198833/
[2]: https://review.openstack.org/#/c/197162/
[3]: https://review.openstack.org/#/c/192906/
[4]: https://review.openstack.org/#/c/187235/
[5]: https://review.openstack.org/196986
[6]: https://review.openstack.org/#/c/138512/
[7]: https://review.openstack.org/#/c/19
t needs to
be done.
https://review.openstack.org/#/c/198906/
What is everyone's thoughts?
--
Sean M. Collins
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
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
___
; 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
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
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...
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
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
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 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
#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
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
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
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
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
__
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
>>
>>
>
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
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
| fc618c8151ad4c53b0fccbca89502b8e |
+---+--+
Basically, this boils down to the fact that with PHYSICAL_NETWORK,
DevStack populates the bridge_mappings file, while
PUBLIC_PHYSICAL_NETWORK d
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
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
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
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
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
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
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
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
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
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
/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
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
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
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
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
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
> 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
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
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
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
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
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
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/
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.
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
//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
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
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
Thanks Doug!
It is a big link but I'd rather see the full URL than trust opening a
URL shortener link. I've been rickrolled too many times to count. :)
--
Sean M. Collins
__
OpenStack Development Mailing Lis
ersion we were concerned about 12.04 LTS. I think we settled on
2.63 since that was what was available in the main release channel,
or possibly what was being shipped in the cloud-archive repos.
--
Sean M. Collins
___
OpenStack-dev mailing lis
I don't see a summit proposal for Neutron, on the
subject of IPv6. Are there plans to have one?
--
Sean M. Collins
pgpFNUoI1OtIP.pgp
Description: PGP signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.
imply specifying behavior that was originally undefined.
The motivation is to help Neutron work with IPv6 - which is a must-have
for Comcast.
--
Sean M. Collins
pgpQJV_mcuSwE.pgp
Description: PGP signature
___
OpenStack-dev mailing list
OpenStack-dev
ps to the qos_policies table), that stores
implementation specific behavior/configuration.
There is also a wiki page, that has some useful links:
https://wiki.openstack.org/wiki/Neutron/QoS
--
Sean M. Collins
pgpFaQTxkBTIG.pgp
Description: PGP signature
___
appreciate it.
I plan to study up on the ML2 plugin and add support for the QoS
extension, so we can transition away from the OVS plugin when it is
deprecated.
--
Sean M. Collins
pgpMxoF9m8RkP.pgp
Description: PGP signature
___
OpenStack-dev
empty migration_for_plugins
array,
which means that the migration script is never run, hence the tables are
never created.
The lbaas_add_status_des script, however, has migration_for_plugins
array set to "*" - meaning it is run for all plugins.
Does this sound correct to anyone else?
--
201 - 300 of 301 matches
Mail list logo
