diff options
Diffstat (limited to 'sanitycheck/pnfsimulator-secured/certservice/README.md')
| -rw-r--r-- | sanitycheck/pnfsimulator-secured/certservice/README.md | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/sanitycheck/pnfsimulator-secured/certservice/README.md b/sanitycheck/pnfsimulator-secured/certservice/README.md index 16a4793..2708041 100644 --- a/sanitycheck/pnfsimulator-secured/certservice/README.md +++ b/sanitycheck/pnfsimulator-secured/certservice/README.md @@ -6,22 +6,23 @@ This readme describes how to run PNF Simulator with certificates fetched using O Using Makefile in this directory following can be achieved: * Setup environment for PNF Simulator, i.e.: - * Create certificates that will be used for internal communication between CertService and CertService Clients. - Generated internal certificates should be present in `resources/certs` directory. + * Create certificates that will be used for internal communication between CertService and CertService Clients. + Generated internal certificates should be present in `resources/certs` directory. * Start and configure EJBCA * Start and configure AAF Cert Service. - * Run Cert Service Clients to fetch certificates for VES and PNF Simulator. Certificates will be stored for the components -in `resources/certservice-client/client-volume-for-ves` and `resources/certservice-client/client-volume-for-pnfsim` accordingly. - * Start VES and DMaaP Simulator. Fetched certificates will be mounted to VES. + * Run Cert Service Clients to fetch certificates for VES and PNF Simulator. Certificates will be stored for the + components in `resources/certservice-client/client-volume-for-ves` + and `resources/certservice-client/client-volume-for-pnfsim` accordingly. + * Start VES and DMaaP Simulator. Fetched certificates will be mounted to VES. * Start PNF Simulator. Fetched certificates will be mounted to PNF Simulator. * Clean up. - + ### Prerequisites ##### VES collector local deployment prerequisites -By default, the image of VES from Nexus supports only HTTP communication. A local image with enabled HTTPS must be -build to use local VES as PNF simulator destination. +By default, the image of VES from Nexus supports only HTTP communication. A local image with enabled HTTPS must be build +to use local VES as PNF simulator destination. 1. Pull VES repository 2. In `<VES_PROJECT_ROOT>/etc/collector.properties` file set field `auth.method=certBasicAuth` @@ -31,8 +32,6 @@ Local VES deployment uses also DMaaP simulator. Its image should be built locall 1. Go to `sanitycheck/dmaap-simulator` directory 2. Run: `make build` - - ### Setup environment To set up whole environment for PNF Simulator, i.e.: - deploy and configure EJBCA @@ -52,7 +51,9 @@ To run PNF Simulator execute: ```` make start-pnfsim ```` -This command starts PNF Simulator with certificates fetched using CertService (certificates are fetched in the previous step) +PNF Simulator starts together with the http server. +This command starts PNF Simulator with certificates fetched using CertService (certificates are fetched in the previous +step) ### Send event @@ -61,7 +62,6 @@ Configure PNF simulator to use proper VES URL by executing this command from ``p make reconfigure-ves-url ``` - Send an event from PNF simulator to VES by executing this command from ``pnf-simulator/sanitycheck`` directory: ``` make generate-event |