openstack-ansible-os_neutron/tests/dragonflow_inventory
Jimmy McCrory c03c932c9b Use known group names
Avoid assuming that provider or deployment specific groups are defined
in inventory by making use of the group names defined in the
'neutron_services' var and checking group membership through a host's
group_names instead of Ansible's groups dictionary.

Change-Id: I66b7c639494d98fdb3baa52fe56c670e32dea3ce
2017-11-13 11:10:33 -08:00

83 lines
989 B
Plaintext

[all]
localhost
infra1
server1
server2
agents1
agents2
[physical_host]
localhost
[all_containers]
infra1
server1
server2
agents1
agents2
[rabbitmq_all]
infra1
[galera_all]
infra1
[memcached_all]
infra1
[etcd_all]
infra1
[etcd:children]
etcd_all
[service_all:children]
rabbitmq_all
galera_all
memcached_all
etcd_all
[keystone_all]
infra1
[neutron_server]
server1
server2
[dragonflow_pubsub_agent]
server1
server2
[dragonflow_controller_agent]
localhost
[dragonflow_l3_agent]
agents1
agents2
[neutron_agent]
[neutron_dhcp_agent]
[neutron_linuxbridge_agent]
[neutron_openvswitch_agent]
[neutron_metering_agent]
[neutron_l3_agent]
[neutron_lbaas_agent]
[neutron_metadata_agent]
[neutron_all:children]
neutron_agent
neutron_dhcp_agent
neutron_linuxbridge_agent
neutron_openvswitch_agent
neutron_metering_agent
neutron_l3_agent
neutron_lbaas_agent
neutron_metadata_agent
neutron_server
dragonflow_controller_agent
dragonflow_pubsub_agent
dragonflow_l3_agent
[utility_all]
infra1