You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
This page is used to collect VF-C requirements for Beijing Release. Welcome feedback.
Functionality Requirement
Functionality Requirement | Requirement Description |
|---|
| NS/VNF auto scaling(in/out) | NS/VNF auto scaling out/in based on policies |
| NS/VNF manual scaling(in/out) | NS/VNF manual scaling |
| VNF scale to | - On the S-VNFM interface the LCN should support scale to operation type
- On the S-VNFM interface the scale to operation should be available
|
| Indirect Mode | support Indirect mode related to VNF-related Resource Management |
| VNF Image Management | - support VNF Image storage and distribute to VIM
- the image to be used for one particular VNFC should be passed on S-VNFM interface during grant response
|
| VNC Flavour Management | - the flavour to be used for one particular VNFC should be passed on S-VNFM interface during grant response
|
| VNF availability zone management | - the availability zone to be used for one particular VNFC should be passed on S-VNFM interface during grant response
|
| Multiple instantiation level support | - it should be possible to define multiple instantiation levels in VNFD (without using vendor specific extensions)
- the instantiation level to be used should be passed on S-VNFM interface during instantiation
|
| Externally supplied addresses | - it should be possible to pass external IP addresses, subnet ids ... for each external connection points
|
| Affinity support | - it should be possible to define affinity policies in the VNFD
- VF-C should send the availability zones to be used in accordance to the VNF affinity requirements in VNFD
- VF-C should take the affinity requirements (host and zone) when answering grant on S-VNFM interface
|
| VNF attribute support | - it should be possible to define VNF specific attributes in VNFD (without using vendor specific extensions)
- the VNF attributes should be sent from VF-C S-VNFM during instantiation
|
| Security issues | - both KeyStone authentication domains should be visible on S-VNFM VIM query API
- it should be possible to define multiple endpoints for a single ESR (S-VNFM)
- S-VNFM should authenticate itself to VF-C (LCN & granting)
- VF-C should authenticate itself to S-VNFM
- SSL should be supported on VF-C APIs (LCM, catalog)
- SSL should be supported on S-VNFM API
- the VNFM query should provide the trusted CA certificates for VF-C interfaces
|
| Workflow function improvement | support workflow loading distributed by SDC |
| R2 Model alignment | R2 Information Model and Data Model alignment |
| GVNFM usecase Test | Find GVNFM usecase and test |
| Interface align with ETSI SOL003 | Existing interface aligns with ETSI SOL003 - support VNF modify interface
|
|
|
Integration with other projects(VF-C will consume the interfaces these projects provided ):
Functionality Requirement | Requirement Description |
|---|
| OOM Integration | Integration with OOM to deploy VF-C |
| A&AI Integration | Improve integration with A&AI(Virtual resource created by VF-C save to A&AI ) |
| OF Integration | Plan to integration with OF when do resource granting |
|
|
Non-functional Requirement
Reference ONAP R2 proposals for Non-functional requirements
Non-functional Requirement | Requirement Description |
|---|
| Community S3P requirements | Requirements abou S3P |
|
|
|
|
