Compass4nfv Frequently Asked Questions¶
1. What is Compass4nfv¶
Compass4nfv is an installer project based on open source project Compass, which provides automated deployment and management of OpenStack and other distributed systems. It can be considered as what the LiveCD to a single box for a pool of servers – bootstrapping the server pool.
see more information, please visit
2. What’s the additional setting in switch if use the default network configuration¶
Here is the Compass4nfv default network configration file: compass4nfv/deploy/conf/hardware_environment/huawei-pod1/network.yml OR compass4nfv_FAQ/deploy/conf/vm_environment/huawei-virtual1/network.yml
It uses a VLAN network for mgmt and storage networks that are share one NIC(eth1) as a default network configuration. So you need add an additional tagged VLAN (101) and VLAN (102) on eth1’s switch for access.
3. How to deal with installation failure caused by setting pxe and reset nodes failed¶
At first, please make sure that deployed nodes’ ipmi network can access from Jumphost and IPMI user/pass is correct.
Compass4nfv supports IPMI 1.0 or IPMI 2.0 to control your nodes, so you can set it according your IPMI version in dha.yml.
ipmiVer: '2.0'
4. How to deal with installation failure caused by “The Server quit without updating PID file”¶
If you see “The Server quit without updating PID file” in installation print log, it is caused by mgmt network can’t access from each deployed nodes, so you need to check your switch setting whether an additional tagged VLAN is added if uses default network configuration.
5. How to set OpenStack Dashboard login user and password¶
It uses admin as the default user for OpenStack Dashboard. The password can be achieved as below:
sudo docker cp compass-tasks:/opt/openrc ./
sudo cat openrc | grep OS_PASSWORD
6. How to visit OpenStack Dashboard¶
For vm deployment, because NAT bridge is used in virtual deployment, horizon can not be access directly in external IP address. you need to cofigure the related IPtables rule at first.
iptables -t nat -A PREROUTING -d $EX_IP -p tcp --dport $PORT -j DNAT --to 192.16.1.222:443
The $EX_IP here is the server’s ip address that can be access from external. You can use below command to query your external IP address.
external_nic=`ip route |grep '^default'|awk '{print $5F}'
ip addr show $external_nic
The $PORT here is the one of the port [1- 65535] that does’t be used in system.
After that, you can visit OpenStack Dashboard by URL: http://$EX_IP:$PORT
7. How to access controller nodes after deployment¶
You can login the controller nodes (host1-3) by default user/pass root/root via the install network IPs which are configured in “compass4nfv/deploy/conf/base.conf”, defined as below:
export MANAGEMENT_IP_START=${MANAGEMENT_IP_START:-'10.1.0.50'}
+-------------+
| |
+----------+ host1 |
| | |
| +-------------+
|
+---------+ | +-------------+
| | install | | |
| Compass +---------------+----------+ host2 |
| | network | | |
+---+VM+--+ | +-------------+
+--------------------+ |
| | | +-------------+
| Jumphost | | | |
| | +----------+ host3 |
+--------------------+ | |
+-------------+
8. Where is OpenStack RC file¶
The RC file named openrc is located in /root in utility container on each controller node as default. Please source it first if you want to use OpenStack CLI.
lxc-attach -n $(lxc-ls | grep utility)
source /root/openrc
9. How to recovery network connection after Jumphost reboot¶
source deploy/network.sh && save_network_info
10. How to use Kubernetes CLI¶
10.1. Login one of the controllers¶
There are 3 controllers referring to host1 to host3 with IPs from 10.1.0.50 to 10.1.0.52. The username of the nodes is root, and the password is root.
ssh root@10.1.0.50
10.3. Follow the k8s example to create a ngnix service¶
To create a nginx service, please read Ref[2] at the end of this page.
