Release notes for Daisy4nfv¶
1. Abstract¶
This document compiles the release notes for the E 1.0 release of OPNFV when using Daisy as a deployment tool.
1.1. Configuration Guide¶
Before installing Daisy4NFV on jump server,you have to configure the daisy.conf file.Then put the right configured daisy.conf file in the /home/daisy_install/ dir.
- you have to supplement the “daisy_management_ip” field with the ip of management ip of your Daisy server vm.
- Now the backend field “default_backend_types” just support the “kolla”.
- “os_install_type” field just support “pxe” for now.
- Daisy now use pxe server to install the os, the “build_pxe” item must set to “no”.
- “eth_name” field is the pxe server interface, and this field is required when the “build_pxe” field set to “yes”.This should be set to the interface (in Daisy Server VM) which will be used for communicating with other target nodes on management/PXE net plane. Default is ens3.
- “ip_address” field is the ip address of pxe server interface.
- “net_mask” field is the netmask of pxe server,which is required when the “build_pxe” is set to “yes”
- “client_ip_begin” and “client_ip_end” field are the dhcp range of the pxe server.
- If you want to use the multicast type to deliver the kolla image to target node, set the “daisy_conf_mcast_enabled” field to “True”
2. OpenStack Configuration Guide¶
2.1. Before The First Deployment¶
When executing deploy.sh, before doing real deployment, Daisy utilizes Kolla’s service configuration functionality [1] to specify the following changes to the default OpenStack configuration which comes from Kolla as default.
a) If is it is a VM deployment, set virt_type=qemu amd cpu_mode=none for nova-compute.conf.
b) In nova-api.conf set default_floating_pool to the name of the external network which will be created by Daisy after deployment for nova-api.conf.
c) In heat-api.conf and heat-engine.conf, set deferred_auth_method to trusts and unset trusts_delegated_roles.
Those above changes are requirements of OPNFV or environment’s constraints. So it is not recommended to change them. But if the user wants to add more specific configurations to OpenStack services before doing real deployment, we suggest to do it in the same way as deploy.sh do. Currently, this means hacking into deploy/prepare.sh or deploy/prepare/execute.py then add config file as described in [1].
Notes: Suggest to pass the first deployment first, then reconfigure and deploy again.
2.2. After The First Deployment¶
After the first time of deployment of OpenStack, its configurations can also be changed and applied by using Kolla’s service configuration functionality [1]. But user has to issue Kolla’s command to do it in this release:
