fiware ops demo meeting (health) (09 06-15)
TRANSCRIPT
FIWARE Ops: Health
Fernando LópezTelefónica [email protected], @flopezaguilar
Achieved in 4.3.2
• Subscription to each region in order to receive notification of status change
on that region.
• Possibility that any FIWARE Lab administrator can change the status of the
test by launching the tests again.
• Redesign the overview dashboard of the web application.
• Redesign the failure details page of the web application.
• Redesign the summarized page of the executed tests.
Achieved in 4.3.2
• Connection to the Orion in order to align with the Monitoring GE.
• Implementation of the Intermediate state in order to mark regions in yellow
only if the tests associated to the Object Storage do not pass.
• Update the public network interface of the different regions based on the
migration process.
• Implementation of the Basic Object Storage tests in order to cover this
functionality.
Achieved in 4.3.2
• Update the list of regions based in the new ones that was created in the
migration process.
• Improve the expected time to execute the tests from 5 hours to 30-40
minutes.
• Bug fixing- CIDR overlapping problems
- Clean up process associated to the network operations.
New FI-Health architecture
Test Engine
Identity Management
- KeyRock
Jenkins API
Email with status updated
New testexecution
Planed for 4.3.3
• Provide validation test for the metadata service.
• Delete the deprecated regions (such regions that was migrated to
Icehouse/Juno and do not use the previous version anymore).
• Align the web portal with the style guide of the rest of FIWARE portals.
• Check the existence of shared network on every region in order to manage
the new quotas assign in the new Terms&Conditions.
Planed for 4.3.3
• Store and recovery of the historical data associated to the previous tests
execution.
• Provide validation process for the blueprint operations.
• Provide validation to the upload and download of a object in the Object
Storage.
• Bugs fixing
– Skipped messages are not showed correctly.
– Problems layout when the log messages are printed.