...
$ bash p12.sh <machine-name>
Copy initializations to Host Machine
AAF is setup so it can run
- On the O/S, using Java
- On Docker
- On K8
In each case, even for Docker/K8, we utilize the File O/S for host specific information. This is because
- Many things are Host Specific
- The Hostname required for TLS interactions
- Cassandra specific information (when external/clustered)
- Logging (if logging is done in container, it will be lost if container goes down)
To make things simpler, we are assuming that the file structure will be "/opt/app/osaaf". The code supports changing this, but documentation will wait until use cases arises for ONAP.
Steps:
1) Copy "osaaf.zip" to your Host Machine, where osaaf.zip is provided by AAF SME. // TODO POST SAMPLE HERE
2) Copy your "p12" file generated by your CA (see above), and place in your "certs" directory
3) SSH (or otherwise login) to your Docker/K8 Host Machine
4) setup your directories (you might need to be root, then adjust what you need for O/S File Permissions
$ mkdir /opt/app/osaaf
$ cd /opt/app/osaaf
$ mkdir cred logs
$ unzip ~/osaaf.zip
$ mv ~/<p12 file from CA above> cred
$
Unzip the "osaaf.zip" so it goes into the /opt/app/osaaf directory (should have "etc", "data", "public" and "certs" directories)
4) Modify "org.osaaf.props" to have
Load Data and/or Meta-Data into Cassandra
...