P3
Scope & Goal - with Status
13 Apr
P3 Unit Leader
Haeseung Lee
"piece of cake"?
P3

Fully develped system will be here
Short-term goal will be here:
- new user inteface portal with some products/services
- mini set for whole system
+ "Cake Base"
Scope of P3?
- scope consideration
- Initiative: legacy portals into 'One Portal'
- there are many portals such as OUI, Prism, Aurora, OCSP for each regions, COP, IHMS: NO retirement or migration or integrated.
- also there are many sub system such as SMS, Metric, SAA portal, Cloud Security Portals, etc.: Monitoring and related KPI-metric not matched.
- and, there are reseller portals for Dora, Megafon, IndoSat, and new-comers: identity, accounting & UI issues always.
- consideration for architecture also needed: OpenStack, Docker, Micro Service Architecture(MSA), monolithic, DDD, etc.: who charges full architecture & topologies?
- Perspective of Stockholders are different: which will be good lead to new portal? for Ops? for Dev? for customer? or for what?
P3
Goals of P3 - 1st Guess
- Phasic Approach(not confirmed yet)
-
Stage Zero
- Analysis - Eat your own dog food
- Requirements gathering from scratch
-
short-term Goals
- strong API
- new customer-faced portal on top of new API
-
Mid-term Goals
- Rewrite all key components of system
- Retire old system
- Bring new practices and rules to the all company units
-
Stage Zero
P3
Goals of P3 - Go for it?
- Phasic Approach
-
Stage Zero
- Analysis - Eat your own dog food
- Requirements gathering from scratch
-
short-term Goals(~Dec 2017)
- 'One Portal and portal management for products" as AAA model
- setup Wizard, Look&Feel/Menu configuration changed by log in
- manageable & internal/external customer facing / "White Labeling" support for sales
- Identity & Authentication --> core components
- Analysis & Stats --> Chart & Report(components enhancement)
- Docker(container) with CI/CD --> CM enhancement
- API-centric platform(MSA) with featured API Framework
- Retirement or Migration from OCSP to new Portal(more analysis needed)
- setup Wizard, Look&Feel/Menu configuration changed by log in
- Demonstration on June or July: more to come
- 'One Portal and portal management for products" as AAA model
-
Mid-term Goals to Long-term Goals
- Rewrite all key components of system
- Retire old system
- Bring new practices and rules to the all company units
-
Stage Zero
P3
Epic / Backlog - User Stories
P3


Current Status
P3

Backend & API progress(iterative)
- Python v3.3-3.7
-
Front-end(or FE)
- Good REST support - React/Redux
- WebSockets
- SSE(Server Sent Events)
- HTTP long pooling
- SwaggerFile support
- AAA
- Services API Frameworks
- Python local Package Manager
- Python Testing/integration Automation Framework
- Python Linting
- API Gateway with Swagger (image)
- Open API(Cache Edge, Config, Purge, Flush, HermesSync Purge, Stat) Analyzing for integrating
- Analyzing "Migration Blocker"
- Considering "Stats & Report" enhancing
"piece of cake"?
P3

API Framework & Environment
- Dev & Test Environment for FE & BE based on proper API framework
- Docker Swarm for easy deployment & orchestration
currently making "Cake Base"

Text
P3
P3

Meeting Minute
P3
Portal 3.0 - scope & goal
By Lee, Haeseung
Portal 3.0 - scope & goal
- 55