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>
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 a requrement from Daisy4NFV Jira: DAISY-53
Change-Id: I6e37c7d13f278b7712f14314080761fc108b0e4d
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
Zhijiang Hu