To use the playbooks, several preconditions must be fulfilled. These preconditions are described in the Q&A section below. The preconditions are:
CentOS* 7.9.2009 must be installed on all the nodes (the controller and edge nodes) where the product is deployed. It is highly recommended to install the operating system using a minimal ISO image on nodes that will take part in deployment (obtained from inventory file). Also, do not make customizations after a fresh manual install because it might interfere with Ansible scripts and give unpredictable results during deployment.
Hosts for the Edge Controller (Kubernetes control plane) and Edge Nodes (Kubernetes nodes) must have proper and unique hostnames (i.e., not localhost). This hostname must be specified in /etc/hosts (refer to Setup static hostname).
The Network Edge deployment and cleanup is carried out via Ansible playbooks. The playbooks are run from the Ansible host. Before running the playbooks, an inventory file inventory.yml must be defined. The provided deployment helper scripts support deploying multiple clusters as defined in the Inventory file.
The following subsections describe the playbooks in more details.
For convenience, playbooks can be executed by running helper deployment scripts from the Ansible host. These scripts require that the Edge Controller and Edge Nodes be configured on different hosts (for deployment on a single node, refer to Single-node Network Edge cluster). This is done by configuring the Ansible playbook inventory, as described later in this document.
To get started with deploying an Smart Edge Open edge cluster using the Converged Edge Experience Kit:
Install pre-requisite tools for the the deployment script
$ sudo scripts/ansible-precheck.sh
Edit the inventory.yml file by providing information about the cluster nodes and the intended deployment flavor
NOTE: To deploy multiple clusters in one command run, append the same set of YAML specs separated by ---
Additional configurations should be applied to the default group_vars file: inventory/default/group_vars/all/10-default.yml. More details on the default values is explained in the Getting Started Guide.
Get the deployment started by executing the deploy script
$ python3 deploy.py
NOTE: This script parses the values provided in the inventory.yml file.
NOTE: If want to enforce deployment termination in case of any failure, use arguments -f or --any-errors-fatal, e.g.:
$ python3 deploy.py --any-errors-fatal
To cleanup an existing deployment, execute with -c or --clean, e.g:
$ python3 deploy.py --clean
NOTE: If it is intended to do the cleanup manually, i.e: one cluster at a time, update the inventory.yml with only the intended cluster configuration
For an initial installation, deploy.py with all/vars/limit: controller must be run before deploy.py with all/vars/limit: nodes. During the initial installation, the hosts may reboot. After reboot, the deployment script that was last run should be run again.
Network Edge playbooks
The network_edge.yml and network_edge_cleanup.yml files contain playbooks for Network Edge mode.
Playbooks can be customized by enabling and configuring features in the inventory/default/group_vars/all/10-open.yml file.
The cleanup procedure is used when a configuration error in the Edge Controller or Edge Nodes must be fixed. The script causes the appropriate installation to be reverted, so that the error can be fixed and deploy.py can be re-run. The cleanup procedure does not do a comprehensive cleanup (e.g., installation of DPDK or Golang will not be rolled back).
The cleanup procedure call a set of cleanup roles that revert the changes resulted from the cluster deployment. The changes are reverted by going step-by-step in the reverse order and undoing the steps.
For example, when installing Docker*, the RPM repository is added and Docker is installed. When cleaning up, Docker is uninstalled and the repository is removed.
To execute cleanup procedure
$ python3 deploy.py --clean
NOTE: There may be leftovers created by the installed software. For example, DPDK and Golang installations, found in /opt, are not rolled back.
Supported EPA features
Several enhanced platform capabilities and features are available in Smart Edge Open for Network Edge. For the full list of supported features, refer to Building Blocks / Enhanced Platform Awareness section. The documents referenced in this list provide a detailed description of the features, and step-by-step instructions for enabling them. Users should become familiar with available features before executing the deployment playbooks.
VM support for Network Edge
Support for VM deployment on Smart Edge Open for Network Edge is available and enabled by default. Certain configurations and prerequisites may need to be satisfied to use all VM capabilities. The user is advised to become familiar with the VM support documentation before executing the deployment playbooks. See smartedge-open-network-edge-vm-support for more information.
The default CNI for Smart Edge Open is calico. Non-default CNIs may be configured with Smart Edge Open by editing the file inventory/default/group_vars/all/10-open.yml.
To add a non-default CNI, the following edits must be carried out:
The CNI name is added to the kubernetes_cnis variable. The CNIs are applied in the order in which they appear in the file. By default, calico is defined. That is,
To add a CNI, such as SR-IOV, the kubernetes_cnis variable is edited as follows:
The Multus CNI is added by the Ansible playbook when two or more CNIs are defined in the kubernetes_cnis variable
The CNI’s networks (CIDR for pods, and other CIDRs used by the CNI) are added to the proxy_noproxy variable by Ansible playbooks.
Adding additional interfaces to pods
To add an additional interface from secondary CNIs, annotation is required.
Below is an example pod yaml file for a scenario with kube-ovn as a primary CNI along with calico and flannel as additional CNIs.
Multus* will create an interface named calico using the network attachment definition openness-calico and interface flannel using the network attachment definition openness-flannel.
NOTE: Additional annotations such as openness-calico@calico are required only if the CNI is secondary. If the CNI is primary, the interface will be added automatically by Multus*.
In addition to being a unique hostname within the cluster, the hostname must also follow Kubernetes naming conventions. For example, only lower-case alphanumeric characters “-“ or “.” start and end with an alphanumeric character. Refer to
K8s naming restrictions for additional details on these conventions.
Configuring the Inventory file
To execute playbooks, an inventory file inventory.yml must be defined in order to specify the target nodes on which the Smart Edge Open cluster(s) will be deployed.
The Smart Edge Open inventory contains three groups: all, controller_group, and edgenode_group.
all contains all the variable definitions relevant to the cluster:
cluster_name: defines the name of the Smart Edge Open edge cluster
flavor: the deployment flavor to be deployed to the Smart Edge Open edge cluster
single_node_deployment: when set to true, mandates a single-node cluster deployment
controller_group defines the node to be set up as the Smart Edge Open Edge Controller
NOTE: Because only one controller is supported, the controller_group can contain only one host.
edgenode_group defines the group of nodes that constitute the Smart Edge Open Edge Nodes.
NOTE: All nodes will be joined to the Smart Edge Open Edge Controller defined in controller_group.
In this example, a cluster named as 5g_near_edge is deployed using the pre-defined deployment flavor cera_5g_near_edge that is composed of one controller node ctrl.openness.org and 2 edge nodes: node01.openness.org and node02.openness.org.
Exchanging SSH keys between hosts
Exchanging SSH keys between hosts permits a password-less SSH connection from the host running Ansible to the hosts being set up.
In the first step, the host running Ansible (usually the Edge Controller host) must have a generated SSH key. The SSH key can be generated by executing ssh-keygen and obtaining the key from the output of the command.
The following is an example of a key generation, in which the key is placed in the default directory (/root/.ssh/id_rsa), and an empty passphrase is used.
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): <ENTER>
Enter passphrase (empty for no passphrase): <ENTER>
Enter same passphrase again: <ENTER>
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
The key's randomart image is:
| . . o=oB*|
| o . . ..o=.=|
| . oE. . ... |
| ooS. |
| ooo. . |
| . ...oo |
| . .*o+.. . |
| =O==.o.o |
In the second step, the generated key must be copied to every host from the inventory, including the host on which the key was generated, if it appears in the inventory (e.g., if the playbooks are executed from the Edge Controller host, the host must also have a copy of its key). It is done by running ssh-copy-id. For example:
# ssh-copy-id root@host
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host '<IP> (<IP>)' can't be established.
ECDSA key fingerprint is SHA256:c7EroVdl44CaLH/IOCBu0K0/MHl8ME5ROMV0AGzs8mY.
ECDSA key fingerprint is MD5:38:c8:03:d6:5a:8e:f7:7d:bd:37:a0:f1:08:15:28:bb.
Are you sure you want to continue connecting (yes/no)? yes
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
Number of key(s) added: 1
Now, try logging into the machine, with: "ssh 'root@host'"
and check to make sure that only the key(s) you wanted were added.
To make sure the key is copied successfully, try to SSH into the host: ssh 'root@host'. It should not ask for the password.
If a proxy is required to connect to the Internet, it is configured via the following steps:
Edit the proxy_ variables in the inventory/default/group_vars/all/10-open.yml file.
Set the proxy_enable variable in inventory/default/group_vars/all/10-open.yml file to true.
Append the network CIDR (e.g., 192.168.0.1/24) to the proxy_noproxy variable in inventory/default/group_vars/all/10-open.yml.
Sample configuration of inventory/default/group_vars/all/10-open.yml:
# Setup proxy on the machine - required if the Internet is accessible via proxyproxy_enable:true# Clear previous proxy settingsproxy_remove_old:true# Proxy URLs to be used for HTTP, HTTPS and FTPproxy_http:"http://proxy.example.org:3128"proxy_https:"http://proxy.example.org:3129"proxy_ftp:"http://proxy.example.org:3128"# Proxy to be used by YUM (/etc/yum.conf)proxy_yum:""# No proxy setting contains addresses and networks that should not be accessed using proxy (e.g., local network and Kubernetes CNI networks)proxy_noproxy:""
Sample definition of no_proxy environmental variable for Ansible host (to allow Ansible host to connect to other hosts):
There are no specific restrictions on the directory into which the Smart Edge Open directories are cloned. When Smart Edge Open is built, additional directories will be installed in /opt. It is recommended to clone the project into a directory such as /home.
NOTE: Only required when cloning private repositories. Not needed when using github.com/smart-edge-open repositories.
To clone private repositories, a GitHub token must be provided.