Versions Compared

Old Version 1

changes.mady.by.user KevinPalis

Saved on

compared with

New Version Current

changes.mady.by.user KevinPalis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page Properties
Joshua Lamos-Sweeney (75%), Dominic Lapitan(50%), Angel Manica Raquel (25%), chris_vacalares (50%), Roy Petrie (25%)

Target release

20.0811

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

Status
colourPurple
titleIn Review

Developers

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 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
serverSystem JIRA
maximumIssues1000
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionmaximumIssues1000
jqlQueryproject = GE AND fixVersion = in (GE_20.8, GE_20.9, GE_20.7 10) order by key asc
serverId3ed8d091-172c-31ee-8b1a-f688a0e72656

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.

References