Converge neutron agents onto Baremetal

The neutron connectivity agents will be deployed onto baremetal along
side the defined "network_hosts". This gives deployers the ability to
simplify deployments, keep a standard topology, and scale to meet the
demands of the environment.

This addresses several long standing operational issues where the
neutron_agent container would be restarted, due to config changes,
upgrades, etc. This can cause a prolonged network outages when L3
tenant networks are in service. Moving these services to baremetal
resolves the issue permanently by ensuring consistent hardware
configurations, mac addresses, and simplifying the network transport
as no vethpairs or macvlans are in service.

Change-Id: Id16b1bcd67bf075a8677206a205ece010e7b014c
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>

playbooks/inventory/env.d/neutron.yml

@@ -58,14 +58,17 @@ container_skel:
       - network_containers
     contains:
       - neutron_agent
+      - neutron_bgp_dragent
+      - neutron_dhcp_agent
+      - neutron_l3_agent
+      - neutron_lbaas_agent
+      - neutron_linuxbridge_agent
       - neutron_metadata_agent
       - neutron_metering_agent
-      - neutron_linuxbridge_agent
       - neutron_openvswitch_agent
-      - neutron_l3_agent
+      - neutron_sriov_nic_agent
-      - neutron_dhcp_agent
+    properties:
-      - neutron_lbaas_agent
+      is_metal: true
-      - neutron_bgp_dragent
   neutron_server_container:
     belongs_to:
       - network_containers

releasenotes/notes/neutron-agent-baremetal-c229e65c77e615fa.yaml

@@ -0,0 +1,16 @@
+---
+features:
+    - Neutron connectivity agents will now be deployed on baremetal within the
+      "network_hosts" defined within the ``openstack_user_config.yml``.
+
+upgrade:
+    - When upgrading there is nothing a deployer **must** immediately do to
+      run neutron agent services on hosts within the ``network_hosts`` group.
+      Simply executing the playbooks will deploy the neutron servers on the
+      baremetal machines and will leave all existing agents containers alone.
+    - It is recommended for deployers to clean up the **neutron_agents**
+      container(s) after an upgrade is complete and the cluster has been
+      verified as stable. This can be done by simply disabling the neutron
+      agents running in the **neutron_agent** container(s), re-balancing the
+      agent services targeting the new baremetal agents, deleting the
+      container(s), and finally removing the container(s) from inventory.