Hi
I want to open this topic, to ask for opinions about the best way to
create bridges for our infra-cloud.
- What do we have now? We have glean configuring successfully the
network, properly creating a tagged vlan for it, configuring routable
ip, etc...
- What do we miss? In order for networking to work in OpenStack
deployment, we need to create a bridge, associating that to our tagged
vlan. Something like:
https://review.openstack.org/#/c/231757/31/files/elements/infra-cloud-networking/static/etc/network/interfaces.d/br-vlan25.cfg
(different settings for east)
I want to know what are people thoughts, about the best way to do it. We
can have several options:
1. Teach glean how to create bridges
2. Be able to pass some chunk of text to glean, that will configure the
interface with all the fragments we need, instead of composing it using
the glean parameters. Our final needs are something like:
auto eth0.1598
iface eth0.1598 inet manual
vlan-raw-device eth0
auto br-vlan1598
iface br-vlan1598 inet static
bridge_ports eth0.1598
bridge_hello 2
bridge_maxage 12
bridge_stp off
address 15.126.48.53
netmask 255.255.255.0
gateway 15.126.48.2
post-up ip route add default via 15.126.48.1 dev br-vlan1598
3. Teach glean how to call scripts after some event happens. For
example, we may want to run an script, after the network in glean has
been configured, that takes the interface generated by glean, and
updates the config to include the bridge
4. Do it on ansible or on puppet
5. Any other ideas?
Best
--
Yolanda Robla Mota
Cloud Automation and Distribution Engineer
+34 605641639
yolanda.robla-m...@hpe.com
_______________________________________________
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
