20.6 GOBii-EBS PR
Target release | 20.06 |
---|---|
Phase | 1 |
Manpower Available | 2.25 |
Sprint Size | 4 weeks |
Component | GOBii Datawarehouse, GOBii Middleware, GOBii-EBS CI/CD pipeline |
Domain | GOBii-EBS Integration |
Document status | FINAL |
Developers | @KevinPalis @Joshua Lamos-Sweeney @Roy Petrie |
Product Owner | Ernesto Briones |
Requirements Analyst | @KevinPalis |
Service Owner | N/A |
QC Tester | N/A |
Functional Tester | N/A |
User Acceptance Tester | N/A |
Background
In preparation for the EBS V3 release, the GOBii-EBS team has started working on refactoring code, creating the pipeline to build new EBS-GOBii containers, and a test swarm cluster – all as preliminary work for the phase 1 of GOBii-EBS integration. Although the foundation has already been laid down through the 2019 EBS DevOps Hackathon, a lot of improvements have been identified and must be implemented. This product iteration’s goal is to have an initial build of the EBS-GOBii containers that satisfy parts of this architecture:
Goals
For this sprint, the main focus is both on the automated CD pipeline (infrastructure) and the initial integration of the GOBii middleware with the Service Gateway. By the end of this sprint, the following should be accomplished:
Test swarm cluster (4-node) and staging swarm cluster (11-node) on GOBii servers (CBSU)
Docker swarm support for deployment
EBS-GOBii Continuous Delivery pipeline
Testing the MonetDB-free system (making sure removing MonetDB didn’t break functionalities)
Initial integration with the Service Gateway (DigesterMediator JAR file linked and being used by WSO2 for some test digester calls)
Finish refactoring of the middleware (aspect files, Digesters)
Decoupling of Timescope with the web container - higher modularity and to allow for easier deployments. Middleware still has dependencies on the web container (web services).
Base database container upgraded to Postgres 12 - latest GDM is still on Postgres 9.5 which is nearing its end-of-life
JIRA
Fix Version: GE_20.6
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
---|---|
Assumptions
Mockups
What we're not Doing
Integration of database deployment processes to the DevOps pipeline.
Standardizing the continuous integration (CI) practices across EBS software development teams. Although this is something we would like to do in future sprints, for now the only requirement is software artifacts are to be released as Docker images.