Portal:Cloud VPS/Admin/Neutron Notes
This page is a dumping ground for links and documentation in the process of moving Labs to using Neutron.
** Currently unused
** Future neutron network controller host
** Compute node
** Runs nova-compute
** Has space for 4 or 5 smallish VMs
** Current network host and api server
** Runs nova-api
** Runs nova-network
** Currently unused
** Potential experimental host for openstack 'ironic'
** Openstack controller node
** Runs keystone API and all keystone services
** Runs nova scheduler
** Runs nova conductor
** Hosts all OpenStack databases for labtest
** Hosts puppetmaster for all labtest VMs
** Ldap/DNS server
** Runs pdns
** Runs all designate services
** Web UI frontend for labtest
** Runs Horizon test instance
** Runs Wikitech test instance
- /etc/nova/nova-compute.conf is managed but unused?
- Can the migration be performed online? (as in data plane)
- Should we use linux bridging or OpenVSwitch?
- Linux bridging is simpler conceptually and component wise but not as featurefull.
- What Neutron plugin should we use?
- What type and mechanism should we use?
- Does L2 Population work as expected?
The shared switch is a Boolean value that, when set to true, allows a network to be utilized among all tenants. This attribute is available only for networks created by administrators and is not available for networks created by users.
Denton, James (2015-11-27). Learning OpenStack Networking (Neutron) - Second Edition (p. 129). Packt Publishing. Kindle Edition.
Neutron l2/l3 agents https://www.youtube.com/watch?v=uNAkDfkTGBw
- General overview of transition mechanics with no real technical insight
- assumes things exist and are working such as 'Run a DB dump/restore tool that creates Networking data structures representing current legacy networking config.'
- TODO - fill in the migration process script here -^^
- very limited test case only using devstack
- https://review.openstack.org/#/c/100265/ (depends on and abandoned)
- depends on https://review.openstack.org/#/c/100265/7/nova/api/openstack/compute/contrib/admin_actions.py and associated completely
- custom behavior from patch example (unproven and unloved): nova migration-to-neutron <vm-id> <neutron-net-id>
Spec for Neutron Migration feature (permanent -2?)
- This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.
http://lists.openstack.org/pipermail/openstack/2017-March/018903.html (andrew asking for migration stories)
https://www.youtube.com/watch?v=54wp1yzC-d8 (cern migration story)
- 2.1+ described as best and ubuntu seems to be on 2.0 (flow-eviction-thresholds) via apt-cache
- 2.3 is OVS LTS
ML2 Linux Bridging
https://wiki.openstack.org/wiki/Neutron-Linux-Bridge-Plugin (older docs seems redirected from old monolithic plugin)
OpenVSwitch vs Linux Bridging
Migrating Production Workloads from OVS to Linux Bridge w/ ML2 (RS internal cloud)
ML2: The Plugin Of Plugins
- Virtual networks can be composed of multiple segments of the same or different types.
- EXCEPT: The database schema and driver APIs support multi-segment networks, but the client API for multi-segment networks is not yet implemented.
https://wiki.openstack.org/wiki/Neutron/ModularL2Agent (original spec)