When Model Sync is completed:

1. Create Anchor with SchemaSet in new datastore NCMP-CmHandle-Operational-Data
   see (almost identical to): org.onap.cps.ncmp.api.impl.NetworkCmProxyDataServiceImpl#syncModulesAndCreateAnchor
2. Update SyncSate (and timestamp) (for operational datastore) depending on (new undocumented) config param
   1. UNSYNCHRONIZED   or
   2. NONE_REQUESTED  
   3. config parameter defined in src/main/resources/application.yml. e.g.
      ncmp:
          data-sync:
               upon-registration: false

See also https://wiki.onap.org/display/DW/CPS-799+Spike%3A+Define+states+and+state+handling+for+CM+handle

A/C

1. Can demo that anchor in new datastore is created
2. Can demo sync-state wil set correctly according to yaml parameter
3. State setting to "READY" should be the very last action for the model-sync watchdog
   (demo-able through logging or maybe just code review, possible use groovy test to verify order too)

Out-of-scope

• No CSIT test required
• Data-Sync itself is in separate user story