Changes since Amsterdam
- No scope changes for VF-C R2 Architecture
- Core components updates for supporting R2 Use Case
Scaling In/Out - Stretch goal
VF-C GVNFM demo
S3P Updates
Security
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-660 - Manageability-Logging
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-639 - Update log configuration for VF-C components according to Logging guideline
- Filebeat container packed with VF-C existing container for shipping logs to ONAP ELK logging stack.
- Resiliency and Scalability
- Depend on kubernetes to manage multiple instances of stateless VF-C components
- Usability
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-664 - Document APIs in Swagger and solve inconsistent problem between code and API
- Performance and stability
- VF-C team will work with Integration team to do performance testing
- VF-C team will work with Integration team to do performance testing
IM/DM Alignment
- VF-C team is participating the modeling discussion about Service/Resource IM/DM
- Stretch goal: Align with Service and Resource IM/DM proposed by the modelling subcommittee
API Updates
- Update APIs to align with ETSI SOL003 and SOL005.
- NSLCM northbound APIs V2
- NSLCM southbound APIs
Grant V2
package V2 - GVNFM northbound APIs V2
- Update APIs to align with ETSI SOL003 and SOL005.