pp-10 secured platform deployement, provide --security option

[KaioKei]

Pull Request

Issue

• 10 Deployment and validation support a secured Punchplatform configuration

Testing

1. Compile a v6.0.x Punchplatform
2. In this Punchbox project, merge the branch 6-0-10-secured-deployment inside 6.0
3. Use the punchbox security feature:

cd $PUNCHBOX_DIR
# generate configuration model and vagrant file
make clean
make install
bin/punchbox --config configurations/complete_punch_32G.json \
    --punch-conf /home/user/punchplatform-standalone-6.0.1-SNAPSHOT-linux/conf/ \
    --deployer $PP_PUNCH_DIR/pp-packaging/punchplatform-deployer/target/punchplatform-deployer-6.0.1-SNAPSHOT.zip \
    --security \
    --generate-vagrantfile
# mount VMs
cd vagrant
vagrant up
# generate configuration
cd ..
punchplatform-deployer.sh -gc --templates-dir punch/platform_template/ --model punch/build/model.json
# check configuration and deploy
punchplatform-deployer.sh -gi
punchplatform-deployer.sh deploy -kK

4. Test ES security with curl :

curl -v GET https://server2:9200/_cat/indices -k -u admin:admin

5. In a browser, onnect to kibana with address https://server1:5601 and login with admin:admin

Author's checklist (You)

Before submitting merge request:

• [x] Merge locally
• [x] Compile the same version of a Punchplatform
• [x] Check that the documentation explains the changes
• [x] Explain how to test new features

Reviewer's checklist (Reviewer)

• [ ] Technical review
• [ ] Check that the documentation explains these changes
• [ ] Review is done and tests passed.
• [ ] Notice the autor of finished review. The autor must be the one to press merge.