1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) Open Platform for NFV Project, Inc. and its contributors
**************************************
OPNFV Airship Installation Instruction
**************************************
Abstract
========
This document describes how to deploy NFVi with Airship Installer.
Version history
^^^^^^^^^^^^^^^
+--------------------+--------------------+--------------------+--------------------+
| **Date** | **Ver.** | **Author** | **Comment** |
| | | | |
+--------------------+--------------------+--------------------+--------------------+
| 2020-01-21 | 0.1.0 | James Gu | First draft based |
| | | | on Wiki content |
+--------------------+--------------------+--------------------+--------------------+
| 2020-09-29 | 0.2.0 | James Gu | Airship 1.8 update |
| | | | |
+--------------------+--------------------+--------------------+--------------------+
Introduction
============
This document provides concepts and procedures for deploying an NFVi with Airship Installer in a
hardware infrastructure.
This document includes the following content:
• Introduction to the upstream tool set used by the Airship Installer, for example, `Airship Project <https://www.airshipit.org>`_, `OpenStack Helm <https://wiki.openstack.org/wiki/Openstack-helm>`_, `Treasuremap <https://opendev.org/airship/treasuremap>`_, and so on.
• Instructions for preparing a site manifest in declarative YAML, including hardware profile and
software stack, according to the hardware infrastructure and software component model specified in
the NFVi reference model and reference architecture.
• Instructions for customizing the settings in the site manifest.
• Instructions for running the deployment script.
• Instructions for setting up a CI/CD pipeline for automating deployment and testing.
Intel Pod 17 is used to deploy reference NFVi. Therefore, the examples in this document are based on
the hardware profile of Intel Pod 17. Instructions are either referenced (to the upstream document) or
provided (in this document) so that the reader can modify the settings of the hardware profile and/or
software stack accordingly.
Airship
^^^^^^^
Airship is a collection of loosely coupled and interoperable open source tools that declaratively
automate cloud provisioning.
Airship is a robust delivery mechanism for organizations who want to embrace containers as the new
unit of infrastructure delivery at scale. Starting from raw bare metal infrastructure, Airship manages
the full lifecycle of data center infrastructure to deliver a production-grade Kubernetes cluster with
Helm deployed artifacts, including OpenStack-Helm. Airship allows operators to manage their
infrastructure deployments and lifecycle through the declarative YAML documents that describe an
Airship environment.
For more information, see https://www.airshipit.org.
OpenStack Helm
^^^^^^^^^^^^^^
OpenStack-Helm is a set of Helm charts that enable deployment, maintenance, and upgrading of loosely
coupled OpenStack services and their dependencies individually or as part of complex environments.
For more information, see https://wiki.openstack.org/wiki/Openstack-helm.
Treasuremap
^^^^^^^^^^^
Treasuremap is a deployment reference as well as CI/CD project for Airship.
Airship site deployments use the ``treasuremap`` repository as a ``global`` manifest set (YAML configuration
documents) that are then overridden with site-specific configuration details (networking, disk layout,
and so on).
For more information, see https://airship-treasuremap.readthedocs.io.
Manifests
=========
Airship is a declarative way of automating the deployment of a site. Therefore, all the deployment
details are defined in the manifests.
The manifests are divided into three layers: ``global``, ``type``, and ``site``. They are hierarchical and meant
as overrides from one layer to another. This means that `global` is baseline for all sites, `type` is a
subset of common overrides for a number of sites with common configuration patterns (such as similar
hardware, specific feature settings, and so on), and finally the `site` is the last layer of
site-specific overrides and configuration (such as specific IP addresses, hostnames, and so on). See
`Deckhand documentation <https://airship-deckhand.readthedocs.io/en/latest/overview.html#layering>`_ for more details on layering.
The `global` and `type` manifests can be used *as is* unless any major differences from a reference
deployment are required. In the latter case, this may introduce a new type, or even contributions to
the `global` manifests.
The site manifests are specific for each site and are required to be customized for each new
deployment. The specific documentation for customizing these documents is located here:
• Airship `Site Authoring and Deployment Guide <https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html>`_
• Code comments in the manifests themselves, for example `common-addresses.yaml <https://github.com/opnfv/airship/blob/master/site/intel-pod17/networks/common-addresses.yaml#L14>`_
• As well as each individual chart of components, for example, Deckhand chart `values.yaml <https://github.com/airshipit/deckhand/blob/master/charts/deckhand/values.yaml>`_
Global
^^^^^^
Global manifests, defined in Airship `Treasuremap <https://github.com/airshipit/treasuremap/tree/master/global>`_, contain base configurations common to all sites.
The versions of all Helm charts and Docker images, for example, are specified in `versions.yaml <https://github.com/airshipit/deckhand/blob/master/charts/deckhand/values.yaml>`_.
Type
^^^^
The type `cntt` will eventually support specifications published by the CNTT community. See `CNTT type <https://github.com/opnfv/airship/tree/master/type/cntt>`_.
Site
^^^^
The site documents reside under the `site` folder. While the folder already contains some sites, and
will contain more in the future, the `intel-pod17` site shall be considered the Airship OPNFV reference
site. See more at `POD17 manifests <https://github.com/opnfv/airship/tree/master/site/intel-pod17>`_.
The `site-definition.yaml <https://github.com/opnfv/airship/blob/master/site/intel-pod17/site-definition.yaml>`_ ties together site with the specific type and `global` manifests.
.. code-block:: yaml
data:
site_type: cntt
repositories:
global:
revision: v1.8
url: https://opendev.org/airship/treasuremap.git
Prerequisites
=============
Airship installation requires access to external repositories and the deployed services has two
virtual IPs that are defined in the site/intel-pod17/networks/common-addresses.yaml.
If an existing DNS service is to be used, add the Airship required DNS entries following
`Register DNS names <https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html#register-dns-names>`_.
In Intel POD 17, a CoreDNS service has been installed on the jump host using the following example
procedure:
.. code-block:: console
$ sudo -i
$ mkdir /root/coredns
$ cp {cloned_airship_repo_location}/site/intel-pod17/tools/files/Corefile-intel-pod17 /root/coredns
$ cp {cloned_airship_repo_location}/site/intel-pod17/tools/files/intel-pod17.db /root/coredns
$ docker run -d --name coredns --restart=always --volume=/root/coredns/:/root/coredns -p 53:53/udp coredns/coredns -conf /root/coredns/Corefile-intel-pod17
Update the external DNS server IP addresses and Airship MAAS and Ingress virtual IPS accordingly in
the `Corefile-intel-pod17` and `intel-pod17.db` files.
Set up and install the genesis node following `Genenis node <https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html#genesis-node>`_
section in Airship Site Authoring and Deployment Guide.
On the genesis node, ensure that Virtualization is enabled in BIOS, and PXE is set as first boot
device and the correct NIC is selected for PXE.
The last step is to configure the Hugepages settings for OVS-DPDK by adding the following line in
`/etc/default/grub` on the genesis node:
.. code-block:: console
GRUB_CMDLINE_LINUX="hugepagesz=1G hugepages=12 transparent_hugepage=never default_hugepagesz=1G dpdk-socket-mem=4096,4096 iommu=pt intel_iommu=on amd_iommu=on cgroup_disable=hugetlb console=ttyS1,115200n8"
Reboot the genesis node after GRUB setting change.
Note that the Hugepages configuration values should match the ones in
`treasuremap/type/cruiserlite/profiles/host/cp-intel-s2600wt.yaml`.
Deployment
==========
As Airship is tooling to declaratively automate site deployment, the automation from the installer
side is light. See `deploy.sh <https://github.com/opnfv/airship/blob/master/tools/deploy.sh>`_.
You will need to export environment variables that correspond to the new site (`keystone` URL, node
IPs, and so on). See the beginning of the deploy script for details on the required variables.
Once the prerequisites are met and the manifests are created, you are ready to execute deploy.sh
that supports Shipyard actions: `deploy_site` and `update_site`.
.. code-block:: console
$ tools/deploy.sh
Usage: deploy.sh <deploy_site|update_site>
CI/CD
=====
TODO: Describe pipelines and approach
https://build.opnfv.org/ci/view/airship/
OpenStack
=========
The `treasuremap` repository contains a wrapper script for running OpenStack clients tools/openstack.
The wrapper uses `heat` image that already has OpenStack client installed.
Clone latest ``treasuremap`` code
.. code-block:: console
$ git clone https://github.com/airshipit/treasuremap.git
Setup the needed environment variables, and execute the script as OpenStack CLI
.. code-block:: console
$ export OSH_KEYSTONE_URL='http://identity-nc.intel-pod17.opnfv.org/v3'
$ export OS_REGION_NAME=intel-pod17
$ treasuremap/tools/openstack image list
|
