Skip to content

Commit 3b1d503

Browse files
committed
Add amp prefix to follow the same pattern as in the other blueprints
Signed-off-by: Arrobo, Gabriel <[email protected]>
1 parent 6c058a8 commit 3b1d503

4 files changed

Lines changed: 18 additions & 18 deletions

File tree

onramp/blueprints.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ The Multi-UPF blueprint includes the following:
7575

7676
* New make targets, ``5gc-upf-install`` and ``5gc-upf-uninstall``, to
7777
be executed after the standard SD-Core installation. The blueprint
78-
also reuses the ``roc-load`` target to activate new slices in ROC.
78+
also reuses the ``amp-roc-load`` target to activate new slices in ROC.
7979

8080
* New Ansible role (``upf``) added to ``deps/5gc``, including a new
8181
UPF-specific template (``upf-5g-values.yaml``).
@@ -103,8 +103,8 @@ You can also optionally install the monitoring subsystem.
103103
.. code-block::
104104
105105
$ make k8s-install
106-
$ make roc-install
107-
$ make roc-load
106+
$ make amp-roc-install
107+
$ make amp-roc-load
108108
$ make 5gc-install
109109
$ make gnbsim-install
110110
@@ -171,7 +171,7 @@ Then run the following to load the patch:
171171

172172
.. code-block::
173173
174-
$ make roc-load
174+
$ make amp-roc-load
175175
176176
At this point you can bring up the Aether GUI and see that a second
177177
slice and a second device group have been mapped onto the second UPF.

onramp/inspect.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -104,19 +104,19 @@ ROC:
104104

105105
.. code-block::
106106
107-
$ make roc-install
108-
$ make roc-load
107+
$ make amp-roc-install
108+
$ make amp-roc-load
109109
$ ...
110-
$ make roc-uninstall
110+
$ make amp-roc-uninstall
111111
112112
and for Monitoring:
113113

114114
.. code-block::
115115
116-
$ make monitor-install
117-
$ make monitor-load
116+
$ make amp-monitor-install
117+
$ make amp-monitor-load
118118
$ ...
119-
$ make monitor-uninstall
119+
$ make amp-monitor-uninstall
120120
121121
In both cases, installing the component is a two-step process: first
122122
the microservices that implement the component are instantiated on

onramp/ref.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -262,17 +262,17 @@ other blueprints.)
262262
.. list-table::
263263
:widths: 25 50
264264

265-
* - `roc-install`
265+
* - `amp-roc-install`
266266
- Install ROC workload.
267-
* - `roc-load`
267+
* - `amp-roc-load`
268268
- Load model values into ROC; assumes ROC already deployed.
269-
* - `roc-uninstall`
269+
* - `amp-roc-uninstall`
270270
- Uninstall ROC workload.
271-
* - `monitor-install`
271+
* - `amp-monitor-install`
272272
- Install Monitor workload.
273-
* - `monitor-load`
273+
* - `amp-monitor-load`
274274
- Load dashboard panels into Monitor; assumes Monitor already deployed.
275-
* - `monitor-uninstall`
275+
* - `amp-monitor-uninstall`
276276
- Uninstall Monitor workload.
277277

278278
**SD-RAN Blueprint**

onramp/roc.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,8 +93,8 @@ define the Models into that service.
9393

9494
.. code-block::
9595
96-
$ make roc-install
97-
$ make roc-load
96+
$ make amp-roc-install
97+
$ make amp-roc-load
9898
9999
To see these initial configuration values using the GUI, open the
100100
dashboard available at ``http://<server-ip>:31194``. If you select

0 commit comments

Comments
 (0)