This is an old revision of the document!
OPNFV Brahmaputra User Guide:
Installation Guide
Post installation guide
User Guide:
Access the openstack dashboard:
open a browser http:<vip>/ for Intel pod5 http://10.4.1.21/ crendtials: admin/openstack Command line: source ./cloud/admin-openrc openstack role list openstack user list glance image-list nova list keystone tenanant-list OPNFV requirements: Troubleshooting: JOID is combination of MAAS and JUJU tools which do the OPNFV deployment on bare metal as well as on virtual machine. 1. MAAS deployment In case you are troubleshoot the deployment of 02-maasdeploy.sh then please look into logs during run time of any errors. Possible errors could be. a) Hardware does not support the virtualization. Please enable the virtualization in BIOS and rerun b) ERROR error: Failed to delete vol bootstrap.img error: cannot unlink file '/var/lib/libvirt/images/bootstrap.img': Success error: Failed to delete vol bootstrap.img error: cannot unlink file '/var/lib/libvirt/images/bootstrap.img': Success subprocess.CalledProcessError: Command 'virsh -c qemu:/system vol-delete –pool default
bootstrap.img' returned non-zero exit status 1
solution: There could be some corruption on the images at /var/lib/libvirt/images/ please remove all
image file from the directory /var/lib/libvirt/images/ and reboot the server then start
redeplopenstackoying 02-maasdeploy.sh
c) timeout issue.
Make sure you have good internet connection and your server is not behind proxy and try it again.
2. JUJU deployment
You may encounter issues in your lab environment. Below could be issues you may encounter
a) Right variable are not passed as part of deployment procedure.
./deploy.sh -o liberty -s odl -t ha -l intelpod5 -f none
b) if you have setup maas not with 02-maasdeply.sh then you could encounter hang on ./clean.sh
juju status command may hang because correct MAAS API keys are not listed in envrinments.yaml
or environments.yaml does not exist in current working directory.
Solution: Please make sure you have environments.yaml file under joid/ci directory and correct
MAAS API key has been listed.
c) deployment stuck at long time and timeout:
3. Openstack deployment
