Versions Compared

Key

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

...

  • Seed code for placement decisions in OpenStack cloud and evaluate in an OpenStack testbed for this version. Later, extend to the other clouds including Azure and AWS.
  • Capacity & Capability checking for an OpenStack cloud: 1) Checking the number of zones of the target DC to solve the Anti-affinity rules, 2) Checking available capacity of each zone to solve Affinity rule, 3) Checking available host profiles of each zone to solve flavor matching (i.e., Host-Aggregates).
  • Placement decisions for Affinity and Anti-Affinity among zones of target DC. Optionally, decisions go into compute hosts (for private cloud case).
  • Defining Affinity and Anti-affinity rules in Policy (Stretch Goal). Until this is ready, evaluate with a manual/hard-coded policy.
  • Specifying Affinity and Anti-affinity rules in placement request (Stretch Goal). Until this is ready, evaluate with a manual/hard-coded specification.

Impacted Projects 

ProjectPTLJIRA Epic / User Story*Requirements
OOF
/HAS
  1. A repository to keep the ML/DL Model Management service
  2. A repository to keep the application image dispatcher service
OOMMike Elliott
  1. Helm Charts for PNDA based analytics framework packages
  2. Helm Charts for various analytics applications
  3. Helm Chart for Cloud infra Event/Alert/Alarm/Fault Normalization & Dispatching microservice
Sarat Puthenpura

OSDF: support new placement constraints.

HAS: 1) implement new placement constraints and interact with F-GPS, 2) deal with new placement result data returned from F-GPS.

Multi-VIM/Cloud
  1. Add new config-service plugin to work with Edge side Consul for configuration
Multi-VIM/CloudBin Yang

Cloud infra Event/Alert/Alarm/Fault Normalization & Dispatching microservice development

  • Integrate DMaaP (Kafka) client for communication to ONAP Central 
  • Receive Event/Alert/Alarm/Fault from infra analytics application
  • Normalize from cloud specific Event/Alert/Alarm/Fault format to cloud agnostic (ONAP internal) Event/Alert/Alarm/Fault format
  • Dispatch Event/Alert/Alarm/Fault to ONAP central using DMaaP (Kafka) client


    Collect Availability-Zone capacity data from Clouds.

    API to communicate with F-GPS for Availability-Zone capacity checking.

    Enable the placement decisions (Heat env in OpenStack case) to send them to Cloud orchestrator.

    A&AI

    API to communicate with F-GPS for sending Availability-Zone information of each Cloud Region.

    PolicyPamela Dragosh
    New type of homing/placement policy regarding Affinity, Anti-affinity, required resources is supported in the current interaction with OOF/OSDF.


    Testing

    Current Status