Workflow
This section describes the workflows of the four main operations of the Planner.
The Planner can generate a test based on the packages already uploaded to the V&V catalogue. In this case, the Planner is notified that a package was uploaded to the V&V. Planner will check its associated testing_tags and will generate test plans as pairs of network services and tests descriptors that matches uploaded package's testing_tags.
The Planner can generate a test based on the testing tags of the package that contains a specific service descriptor. Planner is requested about a test execution by service. Planner checks the testing_tags in the package that contains the service uuid, retrieve the testing_tags related tests and generated the pairs of the given network service and the matched tests.
Planner can generate as well a test based on the testing tags of the package that contains a specific test descriptor. Planner is requested about a test execution by test. Planner checks the testing_tags in the package that contains the test uuid, retrieve the testing_tags related services and generate (NSD,TD) pairs of the given test and the matched services.
In addition to the test generation, Planner is also responsible for test status management. The Planner is notified by Curator about the new status of a test plan. With this information, the Planner updates the test plan and test set status and checks if a new test is ready for execution.
Optionally, in each of the test-plan-controller operations are the fields "executionHost", "spName" and "policyId".
- ExecutionHost: probes (containers) from a test can be deployed in another machine than the V&V's
- spName: SP where the service to be tested should be instantiated
- policyId: be able to test Policies using the V&V