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>
Also remove ansible/python2-docker installation from prepare.sh as it is useless
for target node.
Change-Id: I90ae9a34f6319bb418aeabdc70405e14b48ed893
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
/dev/hugepages is already mounted automatically by OS, we can not
use it
Change-Id: Iadff675cc26e844fcc6f4889038344c54fb8b7eb
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
In Python3, assertRegexpMatches & assertNotRegexpMatches
are deprecated in favor of assertRegex and assertNotRegex
Change-Id: I85c539cef94ca4bfbf76229aadb8bf05eee4eaee
This PS modify ks file to support auto mount hugetlbfs during
OS startup if hugepage is enabled by Daisy.
This PS also add transparent_hugepages=never alonge with
hugepagesz, hugepages kernel parameters, according to [1].
[1] https://docs.openstack.org/nova/pike/admin/huge-pages.html
Change-Id: Ic236ac785a16544c62c27ad59fb68c08371f7627
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
keystoneclient classes has been long deprecated in favor of keystoneauth.
This change replaces both session and auth from keystoneclient to keystoneauth.
Change-Id: I9b22e4351cef24360889eabf9d35c8758465dfce
1. If one or more NIC is assigned to be DPDK NIC,
allocate_cpus_for_dpdk() will calculate CPU Ids to be used by
DPDK pmd threads when user calling get_host(s) API. Currently, one
CPU per each NUMA region is allocated. For example:
NUMA layout:
{'numa_node0': [0,1,2,3,4,5,6,7, 16,17,18,19,20,21,22,23],
'numa_node1': [8,9,10,11,12,13,14,15, 24,25,26,27,28,29,30,31]}
CPU choosed(no matter which NUMA region the NICs are located):
[1,9]
Note: On systems with HyperThreading enabled, it is recommended to
also allocate the HT sibling core. But currently, this is not
supported.
Note: We currently restrict that all NICs which are assigned to be
DPDK NIC must be located in one NUMA region(In future, this limitation
should be removed, keep it for now for simplicity and compatibility
with DVS).
2. Next step is to impl. assigning NIC as a DPDK nic. Otherwise,
allocate_cpus_for_dpdk() returns nothing.
3. In future, user can get cores allocated to dpdk from host_meta info,
then fills them in isolcpus field in host_meta info to let Daisy to build the
final isolcpus kernel parameters for each compute node.
Note: Cores allocated to dpdk should be removed from the nova vcpu_pin_set
but currently we do not support setting the nova vcpu_pin_set.
Note: It is not recommended to isolate cores in the nova vcpu_pin_set
unless the host will be dedicated for vms that request cpu pinning.
So for the common usecase, isolcpus = Cores allocated to dpdk.
Change-Id: I58cd6d361d3d194cd35377b1c1bcef113f8036b0
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
This is just a cleanup, should be no function change.
This can be seen as a re-factory before we go further with
redesign of update_host API.
Change-Id: I59e048ca5ad19325722ae4b7c49903297a466130
Zhijiang Hu