This session will include the following subject(s):
TripleO core network configuration:
Today we currently have a very simple set of bash scripts and elements to configure core networking connectivity (dhcp-all-interfaces, ensure-bridge, init-neutron-ovs, etc). We need need to extend our capabilities with things like support for bonding, better vlan support, static interfaces, provider networks. Basically anything we don't do in neutron directly.
This session is to discuss our approach to a more configurable core networking configuration in TripleO.
-High level config formats (JSON passed in via heat) -lower level tools which we need (possibly rewritting some of our shell scripts as python tools...) -look at tools which exist today and outline how we might adopt or learn from these within TripleO
(Session proposed by Dan Prince)
TripleO and Neutron:
Following the http://lists.openstack.org/pipermail/openstack-dev/2014-April/032018.html thread on the ML, we have a few Neutron related questions to discuss:
1. Do we need a separate Neutron node(s)? 2. How do we scale the Neutron node(s)? 3. How do we ensure HA of the Neutron node(s) (neutron-server, l2/dhcp/l3/metadata/lbaas/etc agents)?
Adding Marios' questions here:
4. Subnetting. Right now the undercloud uses a single subnet. Does it make sense to have multiple subnets here - one point I've heard is for segregation of your undercloud nodes (i.e.
