Juniper Openstack

Comment 3 for bug 1599583

Revision history for this message

amudhar (amudha) wrote on 2016-07-06: Re: Vcenter: Fresh install dpkg not creating "contrail_packages" build #2739

From 3.1, with the use of contrail-installer-packages, the below seems to be the provisioning flow:
-> on one of the target nodes, to setup fabric and python:
    -> dpkg –i contrail-installer-packages.deb
    -> cd /opt/contrail/contrail-installer-packages; .setup.sh
-> fab install_contrail:<list of contrail tgz/path to contrail tgz) - this puts the contrail packages on all
     the nodes, and sets up the install repo
-> fab setup_all

In case of vcenter-only and vcenter-as-compute modes, we run prov_esxi and setup_vcenter even
before install_contrail. With the above set of sequence changes, we do not have contrail-vmware-utils
available in the controller node (as the contrail-installer-packages does not have it bundled) and so
prov_esxi fails.

The contrail-vmware-utils package today contains only python-pyvmomi, so I am going ahead and
adding the python-pyvmomi deb into the contrail-installer-packages and we should be able to
do vcenter provisioning with the contrail-installer-packages after this fix.

-Amudha