<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/16/2014 05:41 AM, NOTSU Arata
wrote:<br>
</div>
<blockquote cite="mid:52D79B50.9060801@virtualtech.jp" type="cite">
<pre wrap="">Hello,
I'm trying to add a new configuration option for Neutron OVS agent. Although I've submitted a patch and it is being reviewed [1], I'm posting to this mailing list seeking opinion from a wider range.
At present, when you deploy an environment using Neutron + OVS + GRE/VXLAN, you have to set local_ip for tunnelling in neutron agent config (typically ovs_neutron_plugin.ini). As each host has different local_ip, preparing and maintaining the config files is a cumbersome work.
So, I would like to introduce automatic configuration of local_ip in Neutron. Although such a management should be done by some management system, Neutron having this feature cloud be also helpful to the deployment system. It would reduce the need for the systems to implement such a feature on their own.
Anyway, with this feature, instead of setting an actual IP address to local_ip, you set some options (criteria) for choosing an IP address suitable for local_ip among IP addresses assigned to the host. At runtime, OVS agent will choose an IP address according to the criteria. You will get the same effect as you set local_ip=<the IP address> by hand.
The question is, what criteria is appropriate for the purpose. The criteria being mentioned so far in the review are:
1. assigned to the interface attached to default gateway
2. being in the specified network (CIDR)
3. assigned to the specified interface
(1 can be considered a special case of 3)</pre>
</blockquote>
3 option is the only that have sense to me, most of our deploys have
the many subnets with the same CIDR, also when we use tunneling it
don't run over the default gateway but over a network dedicated for
tunneling<br>
<br>
i would appreciate more if i can include other config file, local to
each node, where i could put local_ip and other settings (maybe
that's already possible. i haven't tested it) <br>
something like
/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini.local being
parsed by /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini<br>
<br>
thanks<br>
<blockquote cite="mid:52D79B50.9060801@virtualtech.jp" type="cite">
<pre wrap="">
Any comment would be appreciated.
Thanks,
Arata
[1] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/64253/">https://review.openstack.org/#/c/64253/</a>
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Mailing list: <a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a>
Post to : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a>
Unsubscribe : <a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333</pre>
</body>
</html>