@@ -24,12 +24,12 @@ generate the ``kolla-build.conf`` file using the following steps.
24
24
25
25
If you don't, you can also run ``kolla-build `` without a
26
26
``kolla-build.conf `` or with the file you find in the ``etc_examples ``
27
- folder of the Kolla pip package. But you should only do that for
27
+ folder of the Kolla Python package. But you should only do that for
28
28
testing purposes, if at all.
29
29
30
30
.. code-block :: console
31
31
32
- pip install tox
32
+ python3 -m pip install tox
33
33
cd kolla/
34
34
tox -e genconfig
35
35
@@ -51,7 +51,7 @@ In general, images are built like this:
51
51
52
52
.. code-block :: console
53
53
54
- python tools/build.py
54
+ python3 tools/build.py
55
55
56
56
By default, the above command would build all images based on CentOS image.
57
57
@@ -65,7 +65,7 @@ The operator can change the base distro with the ``-b`` option:
65
65
66
66
.. code-block :: console
67
67
68
- python tools/build.py -b ubuntu
68
+ python3 tools/build.py -b ubuntu
69
69
70
70
There are following distros available for building images:
71
71
@@ -94,7 +94,7 @@ command line:
94
94
95
95
.. code-block :: console
96
96
97
- python tools/build.py keystone
97
+ python3 tools/build.py keystone
98
98
99
99
In this case, the build script builds all images whose name contains the
100
100
``keystone `` string along with their dependencies.
@@ -109,7 +109,7 @@ Multiple names may be specified on the command line:
109
109
110
110
.. code-block :: console
111
111
112
- python tools/build.py keystone nova
112
+ python3 tools/build.py keystone nova
113
113
114
114
The set of images built can be defined as a profile in the ``profiles `` section
115
115
of ``kolla-build.conf ``. Later, profile can be specified by ``--profile `` CLI
@@ -176,7 +176,7 @@ installed from source code. The default method of the OpenStack install is
176
176
177
177
.. code-block :: console
178
178
179
- python tools/build.py -t source
179
+ python3 tools/build.py -t source
180
180
181
181
The locations of OpenStack source code are written in
182
182
``etc/kolla/kolla-build.conf ``.
@@ -268,7 +268,7 @@ Then rebuild the horizon image, passing the ``--template-override`` argument:
268
268
269
269
.. code-block :: console
270
270
271
- python tools/build.py --template-override template-overrides.j2 horizon
271
+ python3 tools/build.py --template-override template-overrides.j2 horizon
272
272
273
273
.. note ::
274
274
@@ -312,7 +312,7 @@ Then rebuild the horizon image, passing the ``--template-override`` argument:
312
312
313
313
.. code-block :: console
314
314
315
- python tools/build.py --template-override template-overrides.j2 horizon
315
+ python3 tools/build.py --template-override template-overrides.j2 horizon
316
316
317
317
Alternatively ``template_override `` can be set in ``kolla-build.conf ``.
318
318
@@ -359,7 +359,7 @@ image, one may want to add the following to the ``template-override`` file:
359
359
360
360
{% block neutron_server_footer %}
361
361
RUN git clone https://opendev.org/x/networking-cisco \
362
- && pip --no-cache-dir install networking-cisco
362
+ && pip3 --no-cache-dir install networking-cisco
363
363
{% endblock %}
364
364
365
365
Astute readers may notice there is one problem with this however. Assuming
@@ -411,7 +411,7 @@ The template now becomes:
411
411
412
412
{% block neutron_server_footer %}
413
413
ADD plugins-archive /
414
- pip --no-cache-dir install /plugins/*
414
+ pip3 --no-cache-dir install /plugins/*
415
415
{% endblock %}
416
416
417
417
Many of the Dockerfiles already copy the ``plugins-archive `` to the image and
0 commit comments