Page Properties | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Background
In preparation for the EBS V3 release, the GOBii-EBS team has finished working on refactoring code and creating the pipeline to build and deploy the new EBS-GOBii containers – 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 main goals is to have an initial build of the EBS-GOBii containers that can communicate with the Service Gateway and a comprehensive design of the templating system (and possibly a prototype of it).
Goals
For this sprint, the main focus is both the integration of the GOBii middleware with the Service Gateway and the complete design of the templating system for the automated loading workflow. By the end of this sprint, the following should be accomplished:
Service Gateway - GOBii Phase 1 integration
Josh in coordination with Ernesto’s team
Templating System Design
Josh in coordination with Star’s team
We will start with one file type (possibly DartTagIntertek KASP) for a prototype
System optimizations to be able to integrate GOBii with EBS
Majority Significant portion of this is done but there are some left for the that are of significant importance:
The middleware’s shift to using aspect objects instead of instruction files (Josh)
Removal of the middleware’s dependencies to the web node (Josh)
Configuration Tool - Add and remove crop
Angel in collaboration with Dominic
Swarm clusters in CBSU
These are critical servers for both development and testing
Carry over from last sprint and will likely be done early this sprint
JIRA
Fix VersionVersions: GE_20.808-20.11
Jira Legacy | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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.