Description

The Planner acts as the main manager for the V&V test requests. It is responsible for test plans management, sequencing, and triggering requests of the corresponding test requests. Although the Planner is responsible for coordinating overall test activity, execution of individual test plans is given over to the curator and executor components. An outline of the Planner architecture is shown in Architecture.

The Planner's responsibilities are as follows:

• Accept new package notifications.
• Find Test Descriptors (TDs) that match Network Service Descriptors (NSDs) received in new packages.
• Find NSDs that match TDs received in new packages.
• Generate a test plan for each (NSD,TD) pair.
• Send a test plan execution request to Curator.
• Accept test-plans status updates from Curator.
• Accept changes in the plans’ sorting.
• Accept ad hoc new test plans requests.
• Accept deletion of existing test plans.

The tests displayed in the portal are retrieved from the catalogue, and every execution (test instance) generates a test set composed of one or many Test Plans (test descriptor ID, service descriptor ID) pair depending on the involving tests/services/testing_tags defined in the catalogue. For every test plan the executor launches a set of probes storing the results in the test result repository.

By default V&V uses the V&V host itself to execute de testing probes and the Network Service under test is deployed in one of the Service Platforms randomly selected by the curator component. With Release 5.1 is possible:

• to execute the probes in other docker hosts than the V&V one. There is an optional paramenter in the testing request to inform the "testing host" to be used.
• to select the Service Platform where the network service will be instantiated. There is an optional paramenter in the testing request to include the platform to be used
• to associate an already associated service policy to the network service to be tested, using an optional parameter in the testing request.