The Blueprint Validation User Interface (Bluval UI) provides a user-friendly way for displaying blueprints validation test results. Based on these results, the status of a blueprint can be determined (mature, incubation state, etc.).
It is a web application based on ONAP portal SDK, version 2.4.0 (Casablanca). It consists of the front-end and back-end parts. The front-end part is based on HTML, CSS, and AngularJS technologies. The back-end part is based on Spring MVC and Apache Tomcat technologies.
The Bluval UI can be reached in the following address:
The login page is displayed in Figure 1.
Figure 1. Bluval UI login page
The user must apply for an appropriate account creation. Details about the user account creation can be found in subsection 12.1.
When a user logs in, a redirection is performed towards the landing page displayed in Figure 2.
Figure 2. Bluval UI landing page
The general format of a Bluval UI page is the following:
The logout process is supported by clicking on the login id and then on log out button.
The “Validation results” menu is used for retrieving blueprint validation results from Nexus.
This menu is available for the following roles: admin, TSC member, Lab owner.
The “Validation Results” menu includes four sub-items, namely “Get most recent”, “Get by timestamp”, “Get last run” and “Get based on dates”.
This sub-item should be selected when the most recent validation results of a blueprint are needed. Currently, the last 100 results are retrieved and displayed. The corresponding page is depicted in Figure 2. It should be noted that this page is also used as the landing page of the Bluval UI.
A user should define the following data:
When the button ‘Get’ is clicked, the page shown in Figure 3 is illustrated.
Figure 3. Display of the Blueprint validation results
The user can use the following filters on the results, as is depicted in Figure 3:
Moreover, the following data is displayed for each result, as shown in Figure 3:
It should be noted that the user can be further informed about a result by clicking on the button available in the ‘result’ column. Then, the modal illustrated in Figure 4 will be displayed, based on which the user can select a specific test suite of a layer to be demonstrated.
Figure 4. Selection of test suites
Next, details based on these selections will be listed, as is illustrated in Figure 5. Some of these details are the following: test statistics, test execution log and sub-suite robot keywords. The user can hide or show details about the last two items by clicking on them.
Figure 5. General Info, Test statistics and Test execution log of a test suite
By scrolling down, the test cases section is shown. Here, details about the test cases of the test suite are depicted, as is illustrated in Figure 6.
Figure 6. Test cases of a test suite
By clicking on a specific test case, the user can be informed about the used robot keywords of this case.
This sub-item should be selected when only a result is needed whose timestamp is known. The corresponding page is depicted in Figure 7.
A user should define the following data:
When the button ‘Get’ is clicked, the same workflow should be used as with the one described in the subsection 3.1.
Figure 7. The page of “Get by timestamp” sub-item.
This sub-item should be selected when the last result associated with the combination of the following data is needed:
The corresponding page is shown in Figure 8.
When the button ‘Get’ is clicked, the same workflow should be used as with the one described in the subsection 3.1.
Figure 8. The page of “Get last run” sub-item.
This sub-item should be selected when the results associated with the combination of the following data is needed:
The corresponding page is shown in Figure 9.
When the button ‘Get’ is clicked, the same workflow should be used as with the one described in the subsection 3.1.
Figure 9. The page of “Get based on dates” sub-item.
TBD
TBD
The “Register data” menu is used for registering data within the context of the Bluval UI. It should be noted that this UI automatically registers data based on the results fetched from Nexus. This menu should be used as a complementary feature.
This menu is available for the following roles: admin, and TSC member.
The “Register data” menu includes five sub-items, namely “Lab”, “Blueprint”, “Layer”, “Timeslot” and “Blueprint Instance”.
Here, the labs and their silos can be registered, as shown in Figure 10.
Figure 10. The page of “Register Lab” sub-item
Only then can the Bluval UI retrieve results from Nexus associated with a lab.
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
The “Update password” menu is used for updating the password of a specific user.
This menu is available for the following roles: admin, TSC member and Lab owner.
Its page is shown in Figure 11.
Figure 11. The page of the “Update password” item.
The following data must be defined:
The following information is needed in order for a user account to be created:
An email should be sent to featureprojects@lists.akraino.org with the aforementioned information. If the corresponding user account is approved, a confirmation email will be sent back with the initial user password. When the user is logged in, this password should be changed using the ‘Update password’ menu tab (refer to subsection 11).
Currently, the following roles are supported by the Bluval UI: