Hi Dan, et al,
Thanks for all your warmhearted help.
I followed Dan's suggestions as well as others' and tried
again, I see an explicit error in the overcloud: "Connection
aborted.', error(113, 'No route to host')".
(Below are the error messages and information)
I think it could because of lacking of sufficient network
configuration.
Looks the proof-of-concept use case doesn't work for me as I
changed something, such as the undercloud.conf (eg., all the IPs,
etc).
So next, I would try to do the network isolation. Is there a
simple/concise example of the network configuration (
network-environment.yaml). I know
that
there is a guide for this but I've lost myself in the ocean of the
information. It would be the best to start from a basic
configuration, if you could help.
Thanks,
Erming
$openstack overcloud deploy --timeout 90
--ntp-server time1.srv.ualberta.ca -e
/home/stack/storage-environment.yaml
--neutron-public-interface enp1s0f1 --templates
Oct 27 16:16:58 overcloud-controller-0
os-collect-config[12030]: 2015-10-27 16:16:58.626 12030
WARNING os-collect-config [-] Source [ec2] Unavailable.
Oct 27 16:16:58 overcloud-controller-0
os-collect-config[12030]: 2015-10-27 16:16:58.626 12030
WARNING os_collect_config.ec2 [-] ('Connection aborted.',
error(113, 'No route to host'))
Oct 27 16:16:25 overcloud-controller-0
os-collect-config[12030]: 2015-10-27 16:16:25.586 12030
WARNING os_collect_config.local [-] No local metadata found
(['/var/lib/os-collect-config/local-data'])
Oct 27 16:16:25 overcloud-controller-0
os-collect-config[12030]: 2015-10-27 16:16:25.586 12030
WARNING os_collect_config.local [-]
/var/lib/os-collect-config/local-data not found. Skipping
Oct 27 16:16:25 overcloud-controller-0
os-collect-config[12030]: 2015-10-27 16:16:25.586 12030
WARNING os-collect-config [-] Source [request] Unavailable.
Oct 27 16:16:25 overcloud-controller-0
os-collect-config[12030]: 2015-10-27 16:16:25.586 12030
WARNING os_collect_config.request [-] No metadata_url
configured.
Oct 27 16:16:25 overcloud-controller-0
os-collect-config[12030]: 2015-10-27 16:16:25.585 12030
WARNING os_collect_config.heat [-] No auth_url configured.
[heat-admin@overcloud-controller-0 ~]$ ifconfig
br-ex: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu
1500
inet6 fe80::225:90ff:fe33:a63f prefixlen 64
scopeid 0x20<link>
ether 00:25:90:33:a6:3f txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 75 bytes 23562 (23.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0
collisions 0
enp1s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>
mtu 1500
inet 10.0.6.77 netmask 255.255.0.0 broadcast
10.0.255.255
inet6 fe80::225:90ff:fe33:a63e prefixlen 64
scopeid 0x20<link>
ether 00:25:90:33:a6:3e txqueuelen 1000 (Ethernet)
RX packets 44760 bytes 16134789 (15.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 30109 bytes 3840484 (3.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0
collisions 0
device memory 0xfade0000-fadfffff
enp1s0f1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:25:90:33:a6:3f txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0
collisions 0
device memory 0xfad20000-fad3ffff
ib0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu
2044
inet6 fe80::202:c902:24:4045 prefixlen 64 scopeid
0x20<link>
Infiniband hardware address can be incorrect! Please read
BUGS section in ifconfig(8).
infiniband
80:00:04:04:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
txqueuelen 256 (InfiniBand)
RX packets 161572 bytes 9048032 (8.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 17 bytes 5380 (5.2 KiB)
TX errors 0 dropped 7 overruns 0 carrier 0
collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 134 bytes 11552 (11.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 134 bytes 11552 (11.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0
collisions 0
[heat-admin@overcloud-controller-0 ~]$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric
Ref Use Iface
0.0.0.0 10.0.6.40 0.0.0.0 UG 0
0 0 enp1s0f0
10.0.0.0 0.0.0.0 255.255.0.0 U 0
0 0 enp1s0f0
169.254.169.254 10.0.6.40 255.255.255.255 UGH 0
0 0 enp1s0f0
[heat-admin@overcloud-controller-0 ~]$ sudo ovs-vsctl show
1cf8f4ac-fd60-43a3-84cd-6259387e44c9
Bridge br-ex
Port "enp1s0f1"
Interface "enp1s0f1"
Port br-ex
Interface br-ex
type: internal
ovs_version: "2.3.1"
[heat-admin@overcloud-controller-0 ~]$ systemctl -l
...
ceph.service
loaded active exited LSB: Start Ceph distributed file system
daemons at boot time
chronyd.service
loaded active running NTP client/server
cloud-config.service
loaded active exited Apply the settings specified in
cloud-config
cloud-final.service
loaded failed failed Execute cloud user/final scripts
cloud-init-local.service
loaded active exited Initial cloud-init job (pre-networking)
cloud-init.service
loaded active exited Initial cloud-init job (metadata service
crawler)
crond.service
loaded active running Command Scheduler
dbus.service
loaded active running D-Bus System Message Bus
dhcp-interface@br-ex.service
loaded failed failed DHCP interface br/ex
dhcp-interface@enp1s0f0.service
loaded active exited DHCP interface enp1s0f0
dhcp-interface@enp1s0f1.service
loaded failed failed DHCP interface enp1s0f1
dhcp-interface@ib0.service
loaded failed failed DHCP interface ib0
dhcp-interface@ovs-system.service
loaded failed failed DHCP interface ovs/system
getty@tty1.service
loaded active running Getty on tty1
ipmievd.service
loaded active running Ipmievd Daemon
irqbalance.service
loaded active running irqbalance daemon
iscsi-shutdown.service
loaded active exited Logout off all iSCSI sessions on
shutdown
kdump.service
loaded active exited Crash recovery kernel arming
kmod-static-nodes.service
loaded active exited Create list of required static device
nodes for the current kerne
ksm.service
loaded active exited Kernel Samepage Merging
ksmtuned.service
loaded active running Kernel Samepage Merging (KSM) Tuning
Daemon
libvirtd.service
loaded active running Virtualization daemon
lvm2-lvmetad.service
loaded active running LVM2 metadata daemon
lvm2-monitor.service
loaded active exited Monitoring of LVM2 mirrors, snapshots
etc. using dmeventd or prog
netcf-transaction.service
loaded active exited Rollback uncommitted netcf network
config change transactions
network.service
loaded active exited LSB: Bring up/down networking
openvswitch-nonetwork.service
loaded active exited Open vSwitch Internal Unit
openvswitch.service
loaded active exited Open vSwitch
os-collect-config.service
loaded active running Collect metadata and run hook commands.
On 10/15/15, 5:00 PM, Dan Sneddon wrote:
If you are doing the most basic deployment (no network isolation) on
bare metal, you will want to specify which interface is your external
network interface. This will be the interface that gets attached to
br-ex (this defaults to your first interface, which may not be correct
in your case). In the basic deployment, this network will require a
DHCP server to give the controller an address, and if you want to use
floating IPs you will need a range of IPs that are free (won't be
assigned to other hosts by DHCP server).
So, if your external interface is 'enp11s0f0' (just guessing, since
that one actually has a DHCP address), then your command-line will be
at least:
openstack overcloud deploy --templates \
--neutron-public-interface enp11s0f0
But you should probably include a reference to an NTP server:
openstack overcloud deploy --templates \
--neutron-public-interface enp11s0f0 \
--ntp-server pool.ntp.org
Some other options to consider:
--timeout <mins>
--debug
Selecting tunnel type:
--neutron-network-type <vxlan|gre>
--neutron-tunnel-types <vxlan,gre>