dms package implementation

Structure

├── domain-management-system
│   ├── dms
│   │   ├── resource
│   │   ├── onboarding

Key Points

1. dms package responsible for starting the whole application while being dependent on other packages for most functionality
2. resource - package responsible for querying machine resource amount, calculating amount of free and used resources etc...
3. onboarding - package responsible for everything related to onboarding

Work Package Deliverables

No	Deliverable	Proof
1	Structure re-factored as determined by DMS architecture design	as agreed and defined in proposed package specification
2	Implements job orchestration semantics	as defined in research blog and specified accordingly
3	Implements all other functionalities and connects all packages together	As determined by the package design
4	Flexible and pluggable initialization of other packages in a way that allows swapping functionality whenever required.

Timeline

Substantial, as determined by WP tech dependencies

Additional notes and context

1. related bacalhau packages to look into for inspiration and integration: pkg/compute, pkg/config, pkg/requester;
2. current onboarding will move into dms; already moved
3. The general functionality will not change;
4. Do dependency injection (this package will be used by all other packages); e.g. we need to check if docker api exists or not before creating docker workers;
5. Dms package will take care that all objects that are needed for any package; dms package will be responsible for instantiating objects and provide references to other packages; packages will not be able to instantiate objects; These objects will have to comply with api/interfaces/data structures implemented in models package;