blob: a2e90dd60a22ed8235bc96687deaea340e9e3209 (
plain)
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
|
==================================================================================
APEX on AARCH64
==================================================================================
This document describes the changes needed to deploy OPNFV-APEX on aarch64
* General considerations
* Creating undercloud and overcloud images using DIB
* Creating Kolla containers
General considerations
--------------------------
OPNFV - APEX relies on artifacts created by the OOO project.
Those artifacts are:
1. Openstack packages, found in delorean_.
.. _delorean: http://www.python.org/
2. UC and OC images created by RDO and found in images_.
.. _images: https://images.rdoproject.org/master/rdo_trunk/current-tripleo-rdo-internal/
3. The containerized version of the openstack services found in docker.io_.
.. _docker.io: https://hub.docker.com/r/tripleomaster/
All the above artifacts are x86_64 only and as a result cannot be used by APEX on aarch64
As a result the user needs to create the Images locally before attempting to deploy.
The only supported scenario is 'os-nosdn-rocky-ha'.
Other than the aarch64 disk images and containers, there is no other special configuration
required for aarch64. The only requirement is for the nodes to be identified as aarch64 nodes
in the inventory files.
For example :
.. code-block:: yaml
node1:
mac_address: "68:05:CA:68:08:CA"
ipmi_ip: 10.10.10.10
ipmi_user: user
ipmi_pass: pass
pm_type: "pxe_ipmitool"
cpus: 1
memory: 128000
disk: 480
disk_device: sda
arch: "aarch64"
capabilities: "profile:control"
Creating undercloud and overcloud images using DIB
--------------------------------------------------
In order to create that image DIB_ must be used. DIB can either be built from source or use yum to be installed.
.. _DIB: https://github.com/openstack/diskimage-builder
It is important to use a fairly late version of DIB to support UEFI systems. The version currently on epel does NOT have support for UEFI. The version on delorean (15.01) works just fine. DIB uses a YAML file from the user which describes how the
image should look like. The original yaml from RDO is here_:
.. _here: https://github.com/openstack/tripleo-common/blob/master/image-yaml/overcloud-images.yaml
The equivelant yaml files for aarch64 are included in the apex repo in the "apex/contrib/aarch64" folder.
The UC and OC images are very similar in terms of packages. The major difference is the partition table in EFI so for the undercloud, that has to provided as an environmental variable.
.. code-block:: python
export DIB_BLOCK_DEVICE_CONFIG="
- local_loop:
name: image0
- partitioning:
base: image0
label: gpt
partitions:
- name: ESP
type: 'EF00'
size: 64MiB
mkfs:
type: vfat
mount:
mount_point: /boot/efi
fstab:
options: "defaults"
fsck-passno: 1
- name: root
type: '8300'
size: 50GiB
mkfs:
type: ext4
mount:
mount_point: /
fstab:
options: "defaults"
fsck-passno: 1
"
export DIB_YUM_REPO_CONF+="/etc/yum.repos.d/delorean-deps-rocky.repo /etc/yum.repos.d/delorean-rocky.repo /etc/yum.repos.d
/epel.repo "
openstack --debug overcloud image build --config-file undercloud_full.yaml --output-directory ./
The overcloud is built in a similar way.
.. code-block:: python
export DIB_YUM_REPO_CONF+="/etc/yum.repos.d/delorean-deps-rocky.repo /etc/yum.repos.d/delorean-rocky.repo /etc/yum.repos.d
/epel.repo "
openstack --debug overcloud image build --config-file overcloud_full_rootfs.yaml --output-directory ./
Apex container deployment
-------------------------
Similarly the containers provided by OOO are for x86 only. Containers for apex on aarch64 for the Rocky release can
be found in armbandapex_.
.. _armbandapex: https://registry.hub.docker.com/v2/repositories/armbandapex/
A user who wishes to rebuild the containers can easily do so by sing Kolla. An example kolla.conf and the command to build the containers is given bellow.
.. code-block:: python
[DEFAULT]
base=centos
type=binary
namespace="private docker.io repository"
tag=current-tripleo-rdo
rpm_setup_config=ceph.repo,epel.repo,delorean-deps.repo,delorean.repo
push=True
.. code-block:: python
openstack overcloud container image build --config-file /usr/share/tripleo-common/container-images/overcloud_containers.yaml
--kolla-config-file /etc/kolla/kolla-build.conf
|
