Uploaded image for project: 'Policy Framework'
  1. Policy Framework
  2. POLICY-515

This epic covers the work to support Platform Maturity Requirements - Scalability Level 1

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Low Low
    • Beijing Release
    • None
    • None
    • None
    • R2 Beijing - Platform Maturity - Scalability Level 1
    • Done

      As an ONAP user, I want ONAP Policy to reach Scalability Level 1 so that ONAP Policy meets Platform Maturity Guidelines.

      Level 1 is defined as single site horizontal scaling.

      With the current software architecture, this may not be feasible at this time. The XACML PDP must be deployed in its own docker container. The Drools PDP would need to ensure it the policies loaded in each instance are not the same - thus the context would be very limited for this type of scale out. The connection between the Drools PDP and the PAP is inadequate at this time to meet this requirement. The Policy GUI and PAP would not be subject to scaling at this time.

       

      Proposed Solution:

      The initial solution in this user story is weakened:

      1. No scalability of design time components,
      2. horizontal escalability of runtime components

      pap, console, brmsgw, and mariadb component will work on single instance mode.

      pdp-x, and pdp-d can be horizontally escaled and work active/active.

      CONSOLE, PAP, MARIADB, and BRMSGW will only initially support single instance failure recovery and not horizontal escalability.    Under this simplifying assumption, the host names are fixed.

      PDP-X and PDP-Ds will be escaled through OOM mechanisms.

       

            jhh jhh
            pdragosh pdragosh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: