P3

Scope & Goal - methodology explained

(2~8 pages are same, so skip to page 9)

26 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

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)
    • Demonstration on June or July: more to come
  • 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

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"

flows of P3

P3

current "Portals"

including OpenAPIs

current "Products"

current "Backends"

including Database

P3::API Gateway &
        Proxy
 

P3::Portal

P3::Database

P3::Docker on current OpenStack

bi-directional flow:
"Read" and "Write"

uni-directional flow:
"Read" only

bi-directional flow:
"Read" and "Write" in P3 platform only

P3::Authentication using OpenStack

why P3 doing like this?

P3

• for making AAA model
  • Authentication
  • Authorization
  • Accounting
• don't count on legacy system & don't affect any influences on legacy
  • "Read current, Write New One" 
• making Agile, Gradually Improving systems
• now, P3 are making
  • API frameworks 
  • Container Orchestration on current OpenStack
  • CI/CD pipeline 
  • Mock Up/PoC form for Portal 

Also we consider Top Down way

P3

UIs

Also we consider Top Down way

P3

Also we consider Top Down way

P3

Meeting Minute

P3