sonata-nfv / son-security-pilot Goto Github PK

• Create the Docker container running this application
• Create a VM running the Docker

Create a documentation on the GitHub repo on where to put the code and how to use the project/milestones tool.

• Add the HTTP-proxy (Squid) to the NSD.
• Test the data-path connectivity to other VNFs.

$ ansible-playbook son-cmud.yml -e "ops=create plat=snort pop=alabs proj=demo distro=xenial|Core" -v

The user-facing GUI allows users to view the available VNFs, see the VNF status (active or inactive), start VNFs (add them to the running service) and stop VNFs (remove them from the running service).

The command {{ lookup('env','PWD') }} used in all playbooks to obtain the current directory is not working.

@arocha7 do you also have problems with this or is just me?

An alternative approach is to use the built-in ansible var {{ playbook_dir }}

We temporarily changed the CP in VNFD of the VPN to have type="managed" as input. This needs to be changed to external once supported by the IA!

The real management CP needs also to be changed.

See: #45

$ ansible-playbook son-cmud.yml -e "ops=create plat=docker-vpsa pop=alabs proj=demo distro=xenial|Core" -v

NOTE: "pfSense" not included; an alternative must be pursued

• Setup another integration meeting.
• Contact George/Felipe/Stavros.

$ ansible-playbook son-cmud.yml -e "ops=create plat=haproxy pop=alabs proj=demo distro=xenial|Core" -v

Test the self-service portal manually. Maybe with the help of Alberto

• Create a basic Network Service Descriptor comprising VPN and TOR.
• Test the network between these two VNFs.

Please help to plan the next PSA integration meeting. That is, list the tasks (maybe linked to GitHub issues) below:

• Test the SNORT VM manually #23

• Create the Docker container running this application
• Create a VM running the Docker

$ ansible-playbook son-cmud.yml -e "ops=create plat=squid pop=alabs proj=demo distro=xenial|Core" -v

• Add the self-service portal VNF to the NSD
• Check that the VNF is managed automatically by the Service Platform.

Ask Manuel, Hadi, and Wouter in particular how to develop and test FSMs and SSMs without a Service Platform in place. Maybe by using the SONATA emulator.

The self-service portal backend server offers a REST API to allow user to list, add, and remove applications (VNFs) within the PSA service.

• Create the Docker container running this application
• Create a VM running the Docker

$ ansible-playbook son-cmud.yml -e "ops=create plat=nginx pop=alabs proj=demo distro=xenial|Core" -v

• Create an FSM docker that configures the self-service backend server.
• Check that the FSM receives messages from the self-service backend.
• Check that the FSM sends messages to the SSM.

• Create the Docker container running this application
• Create a VM running the Docker

Well - we know this is not possible for pfSense. But What about IPCop and FireIP? Can we test this?