1. Add unit test-cases
2. Integration testing with scheduler and other related modules
3. CI/CD and automation tests and Integration with Jenkins
4. Check for Functionality testing
5. Verify the Integration with the MultiCluster scheduler and K8s plugin

Internal Design details
Guidelines that need to kept in mind
Support for metrics that can be retrieved by Prometheus
Support for Jaeger distributed tracing by including opentracing libraries around HTTP calls.
Support for logging that is understood by fluentd
Mutual exclusion of database operations (keeping internal modules accessing database records simultaneously and also by replication entities of the scheduler micro-service).
Resilience - ensure that the information returned by controllers is not lost as the synchronization of resources to remote edge clouds can take hours or even days when the edge is not up and running and possibility of restart of scheduler micro service in the meantime.
Concurrency - Support multiple operations at a time and even synchronizing resources in various edge clouds in parallel.
Performance - Avoiding file system operations as much as possible.