This is an old revision of the document!
This is a basic verification scenario. It will eventually include three methods for verification:
In some cases a combination of these is necessary as noted below.
Reference Links:
1) On your test driver node browse to, and verify that these services are active:
2) On controller, setup CLI environment for access to OpenStack APIs
[root@oscontroller1 ~]# vi admin-openrc.sh # (paste admin-openrc.sh contents downloaded) [root@oscontroller1 ~]# source admin-openrc.sh
2) Create image cirros-0.3.3-x86_64
3) Verify that an external network and subnet exists (subnet "192.168.1.0/24", no DHCP) in Project / Network / Networks. For base-metal single-NIC non-HA install, you may need to create the external network via the CLI, if not already created as in Bare-metal Multi-node single-NIC install using Foreman.
[root@oscontroller1 ~]# neutron net-create external1 -- --router:external=true --provider:network_type=flat --provider:physical_network=physnet1 Created a new network: +---------------------------+--------------------------------------+ | Field | Value | +---------------------------+--------------------------------------+ | admin_state_up | True | | id | d7868a94-47ec-4ec7-93cc-645d3bc45898 | | name | external1 | | provider:network_type | flat | | provider:physical_network | physnet1 | | provider:segmentation_id | | | router:external | True | | shared | False | | status | ACTIVE | | subnets | | | tenant_id | c3b15e900f0f4c7ab01576bb28d34f10 | +---------------------------+--------------------------------------+ [root@oscontroller1 ~]# neutron subnet-create --disable-dhcp external1 192.168.1.0/24 Created a new subnet: +-------------------+--------------------------------------------------+ | Field | Value | +-------------------+--------------------------------------------------+ | allocation_pools | {"start": "192.168.1.2", "end": "192.168.1.254"} | | cidr | 192.168.1.0/24 | | dns_nameservers | | | enable_dhcp | False | | gateway_ip | 192.168.1.1 | | host_routes | | | id | 2a6a6be2-2ea2-4a38-84cd-3a2e9e3197e8 | | ip_version | 4 | | ipv6_address_mode | | | ipv6_ra_mode | | | name | | | network_id | d7868a94-47ec-4ec7-93cc-645d3bc45898 | | tenant_id | c3b15e900f0f4c7ab01576bb28d34f10 | +-------------------+--------------------------------------------------+
4) Create internal network.
5) Create router
6) Add internal network interface to the router.
7) Launch images
8) Verify connectivity from VMs.