Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

This is still in progress


What we have to migrate?

  • Database:
    • eventlog
    • faultlog
    • historicalperformance (15m/24h)
    • inventory
    • maintenance
    • mediator-server
    • required-networkelement
  • MD-SAL:
    • mounted devices
  • Configuration Files:
    • apigateway


So in fact that we will have the feature data-provider in SDN-R this is the best point where to start the migration process. So for El Alto we have to provide an external solution, but all later versions will have this all integrated. Therefore we have to tag the backup data with a release information so that the data can be identified and a conversion can be done if needed. So this feature may also is used as backup and restore for the same version except that (up to now) it is not planned to have a restore script for El Alto.


Database data

We will use json format so the files will be *.json or compressed json as *.json.zip.


{
    "release":"el alto",
    "created":"2019-11-19T11:43:00.0Z",
    "components":{
        "<component-name>":[{data},...],
        "<component2-name>":[{data2},...],
        "<component3-name>":[{data3},...]
    }

}
  • No labels