This PS does:
1) Build and run Daisycloud-core in queens env
2) Upgrade image verison to Queens
3) Remove UI out from daisycloud-core
Change-Id: Iecdce8bf73001a7930c2f90cb814e4bfcbaae7c4
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
This PS also update required image to a image which
includes gnocchi.
Change-Id: I5b6343d6e8b4cd170e6616521040330b3283b434
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
1. kill ODL leader IP since we are now deploying ODL cluster.
2. Inventory file update bugfix
3. Fix ansible version to 2.4.0
Change-Id: I06aa442dd935ef1ea2225d06c89bf07351744793
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
1. Solve Docker service not start after restart.
2. Solve a variable not exist error in upgrade thread code.
3. Consider update global.yml before calling kolla-ansible
upgrade to aware of changing of multicast switch in daisy.conf.
Change-Id: I9cddb4614264689d5fe1858249875f950c41a699
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
dockerproject.org is slow sometimes lose connection in China.
Change-Id: I73cc6cc36dd6ec674b29b704a6db6d79cf76f981
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
yum.dockerproject.org is slow in China, Daisy should be
more sensitive to errors occured when using that URL.
Change-Id: I4484a1090f0ad9a88b8c9a5bb948a32d9d0e0101
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
when use daisy.conf to deploy the pxe server:
get "instal_func.sh: line 39: bc: command not found" error
the env is lack of bc package
Change-Id: I8d23f7755cde86fee39b6717f13dc1146303bfc8
Historically, Daisy's discoverd is a fork from ironic-discoverd
without changing package name. This has problems:
1) When user want to install daisy but there is already a
ironic-discoverd which from OpenStack, then daisy's discoverd
will not be installed due to already existed.
2) When user already installed Daisy's discoverd and later do
yum update, then daisy's discoverd will be replaced by
ironic-discoverd which from OpenStack.
Both scenarios above will results in Daisy does not work. So
This PS changes ironic-discoverd to daisy-discoverd.
Change-Id: Ic505feb12271dd87e5781da28f79ca604d49374e
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
1.fix bug of get config from conf file is a str
2.modify daisy default backend as kolla
3.modify daisy max os install num to 20
Change-Id: I9ebb0e9ec4ff100ec723544d10a15aebe78585f2
clustershell is provided by epel-release, so we need to install
epel-release before installing clustershell.
Change-Id: Ide471d6b3501ea39d561f599c5a87ac487c41392
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
1. When install daisy, save registry-serve.tar into
/var/lib/daisy/tools just like jasmine.rpm
2. During preparation stage, scp registry-serve.tar and jasmine.rpm
to all targets, and install them on the target hosts.
3. Add version_load_mcast() to use jasmines/jasminec to multicast
kolla image, and build registry server on each target hosts.
4. (TODO)
If version_load_mcast() failed (may due to mcast not allowed by
config or mcast failed on server or any client), config kolla to let
it to fallback to use remote docker image registry. If
version_load_mcast() successful, then config kolla to use
127.0.0.1 as docker registyr server IP.
Change-Id: I69cda8c0c259c356459770f4cb2b6f46da868893
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
Current directory is $sourcedir/kolla.
So the absolute path should be used.
Change-Id: I77aa46d9085ebaf9573cdd8bd71f848f70c3d4e3
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
Zhijiang Hu