Project	PTL	Requirements
OOF	Sarat Puthenpura	OSDF: support new homing/placement constraints (Affinity, Anti-affinity, and resources per workload (e.g., VM) of VNF) as policies and/or VNFD model. HAS: 1) implement new placement constraints and interact with F-GPS, 2) deal with new placement decisions returned from F-GPS.
Multi-VIM/Cloud	Bin Yang	Collect Availability-Zone capacity data from Clouds. Open new API to communicate with F-GPS for per Availability-Zone capacity checking. Enable the placement decisions (e.g., update Heat env in OpenStack case) to send them to Cloud orchestrator (e.g., OpenStack) via plugins.
A&AI	Jimmy Forsyth	Open (new) API for F-GPS to obtain Availability-Zone information of each Cloud Region. Distributed cloud modelling immediately relevant to F-GPS - a single cloud control plane to be able manage several distributed DC locations/zones.

Architecture committee suggestions

On Dec. 4, 2018

Need end-to-end workflows: The overall flow is ready (below), and detailed will be ready soon.
Modeling Affinity/Anti-affinity: Investigated ETSI NFV-IFA and turns out that it includes Affinity/Anti-affinity specification per DC (NFVI-PoP), Zone (Availability-zone), and compute server (NFVI-node).
Modeling Distributed cloud: Each Cloud Region has multiple Availability-zones (DCs)
Capacity check: Fine grained, per Availability-zone (or DC).

Testing

View file

name	ONAP-Valet_edge_usecase.pptx
height	250