US Description –As an SDN-C user Iwant the SDN-C component to take periodic configuration backup’s on all VNF’s under its control so that all the different configurations pushed to the VNF’s are stored for later reference.
Scope - this user story provides the functionality to take configuration backups of the VNF’s automatically at configured regular intervals and maintain configured no of backups in inventory with recorded date, time, VNF and other details required.
Backend Impact –
1. The configuration backups have to be stored in the internal SDN-C DB.
2. The backup process is either triggered by external API call at any time or by internal timer as per the configured backup interval. Default value could be 1 per day i.e 24 hours.
3. The no of backup’s to maintain is configurable and if no value is set then a max value if no of backups should be defined. Default value could be 10.
4. The service will highlight the current version of configuration that the device is running with.
Acceptance Criteria –As an SDN-C user, I need the SDN-C to backup all device configurations automatically as per scheduled time interval and maintaining the configured no of backups.
Design Detail -
1. The config mgmt. component interfaces with SDN-C, APP-C, SO, AAI and Policy to be able to determine the config back up time periods and rules for VNF’s, request Config snap shot from APP-C, request config update on SDN-C, and request operational policies for VNF for config restoration from POLICY.
2. The configMgmt component will use the SDN-C internal SQL DB to store the configs retrieved from the devices. Alternatively A&AI can be used for this.
3. All config back up rules will be available in POLICY for each VNF type and Service type. The ConfigMgmt component will be updated with any changes on these policies after updation from SDC catalog.