20.7 GOBii-EBS PR
- KevinPalis
Target release | 20.07 |
|---|---|
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 @Dominic Lapitan |
Product Owner | Ernesto Briones |
Requirements Analyst | @KevinPalis |
Service Owner | N/A |
QC Tester | N/A |
Functional Tester | N/A |
User Acceptance Tester | N/A |
FINAL
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 can communicate with the Service Gateway.
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:
Service Gateway - GOBii Phase 1 integration
Templating System for input files for Phase 1 [Design]
On-demand processor node
System optimizations to be able to integrate GOBii with EBS
Configuration Tool (Design phase)
JIRA
Fix Version: GE_20.7
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.