summaryrefslogtreecommitdiffstats
path: root/docs/usecases/pnf-simulator.rst
diff options
context:
space:
mode:
authorJakobKrieg <jakob.krieg@bcmsolutions.de>2020-10-19 14:17:30 +0200
committerJakobKrieg <jakob.krieg@bcmsolutions.de>2020-10-19 14:17:39 +0200
commit2798e38a91475a7853f5c66840bf312f82ee9525 (patch)
tree8f91323ea1017ee587e7acc556b6ea785d2e0dd6 /docs/usecases/pnf-simulator.rst
parent0db1e9030a0ffc7db566e74d23519079c17ace2e (diff)
PNF Simulator guide add unenriched CBA
Issue-ID: CCSDK-2848 Change-Id: I51c41a77f087609aed112fc562cd361188019873 Signed-off-by: JakobKrieg <jakob.krieg@bcmsolutions.de>
Diffstat (limited to 'docs/usecases/pnf-simulator.rst')
-rw-r--r--docs/usecases/pnf-simulator.rst18
1 files changed, 9 insertions, 9 deletions
diff --git a/docs/usecases/pnf-simulator.rst b/docs/usecases/pnf-simulator.rst
index 61aa138a3..5e44967c4 100644
--- a/docs/usecases/pnf-simulator.rst
+++ b/docs/usecases/pnf-simulator.rst
@@ -337,7 +337,7 @@ Config-assign and config-deploy in CDS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In the following steps the CBA is published in CDS, config-assignment is done and the config is deployed to to the
-Netconf server through CDS in the last step. We will use this CBA: :download:`zip <media/pnf-simulator-demo-cba.zip>`.
+Netconf server through CDS in the last step. We will use this CBA: :download:`zip <media/pnf-simulator-demo-cba-unenriched.zip>`.
If you want to use scripts instead of Postman the CBA also contains all necessary scripts.
.. tabs::
@@ -419,10 +419,10 @@ If you want to use scripts instead of Postman the CBA also contains all necessar
Move to the main folder of the CBA with ``cd ..`` and archive all folders with ``zip -r pnf-demo.zip *``.
.. warning::
- The provided CBA is already enriched, the following step anyhow will enrich the CBA again to show the full workflow.
- For Frankfurt release this causes an issue when the configuration is deployed later on. This happens because some parameters
- get deleted when enrichment is done a second time. Skip the next step until Deploy/Save Blueprint if you use
- Frankfurt release and use the CBA as it is. In future this step should be fixed and executed based on an unenriched CBA.
+ Sometimes there might be issues during enrichment (e.g. some parameters get deleted in the CBA)). If you face problems
+ during enrichment or deployment later on use the following CBA, which is already enriched:
+ :download:`zip <media/pnf-simulator-demo-cba-enriched.zip>`. If you use the enriched CBA, skip
+ this section until Deploy/Save Blueprint.
Enrich the blueprint through calling the following script. Take care to provide the zip file you downloader earlier.
@@ -716,10 +716,10 @@ If you want to use scripts instead of Postman the CBA also contains all necessar
**Enrichment:**
.. warning::
- The provided CBA is already enriched, the following steps anyhow will enrich the CBA again to show the full workflow.
- For Frankfurt release this causes an issue when the configuration is deployed later on. This happens because some parameters
- get deleted when enrichment is done a second time. Skip the next steps until Deploy/Save Blueprint if you use
- Frankfurt release and use the CBA as it is. In future this step should be fixed and executed based on an unenriched CBA.
+ Sometimes there might be issues during enrichment (e.g. some parameters get deleted in the CBA). If you face problems
+ during enrichment or deployment later on use the following CBA, which is already enriched:
+ :download:`zip <media/pnf-simulator-demo-cba-enriched.zip>`. If you use the enriched CBA, skip
+ this section until Deploy/Save Blueprint.
Enrich the blueprint through executing the `Enrich Blueprint` request. Take care to provide the CBA file which you
downloaded earlier in the request body. After the request got executed save the response body, this will be the