Provide Sample Signed PNF Package for Integration Test

This can be used for integration test of Pre-Onboarding and Onboarding
of a PNF package.

Issue-ID: INT-949

Change-Id: I8f193dd6968f62d801530f99c5b130b0bdc57728
Signed-off-by: Szabolcs Hutvagner <szabolcs.hutvagner@ericsson.com>

1 files changed, 40 insertions, 0 deletions

diff --git a/test/mocks/pnf-onboarding/readme.md b/test/mocks/pnf-onboarding/readme.md
new file mode 100644
index 000000000..4ddf701b5
--- /dev/null
+++ b/test/mocks/pnf-onboarding/readme.md
@@ -0,0 +1,40 @@
+# PNF Package for Integration Test
+
+
+
+Builds 2 PNF packages based on the files in `/src/main/resources/csarContent/`
+
+
+
+1. unsigned package:
+
+	`sample-pnf-1.0.1-SNAPSHOT.csar`
+
+
+
+2. signed package:
+
+	`sample-signed-pnf-1.0.1-SNAPSHOT.zip`
+The signed package is based on ETSI SOL004 Security Option 2. It contains csar, cert and cms files.
+
+The packages are generated by running the following command in the same directory as this readme file i.e. pnf-onboarding directory:
+>	`mvn clean install`
+
+
+
+The packages will be stored in target folder under the pnf-onboarding directory.
+**NOTE: Currently this solution works for Linux OS only.**
+
+
+
+To be able to use the signed package in SDC the `src/main/resources/securityContent/root.cert` file has to be loaded into SDC onboarding backend container.
+
+
+
+If SDC is running in containers locally then the following commands could be used to copy the root.cert to the default location in SDC Onboarding Container. It is assumed that the commands are executed from inside pnf-onboarding directory.
+
+```
+	docker exec -it <sdc-onboard-backend-container-id> mkdir -p /var/lib/jetty/cert
+	docker cp src/main/resources/securityContent/root.cert <sdc-onboard-backend-container-id>:/var/lib/jetty
+```
+