This is research blog where currently we are defining NuNet job orchestration semantics for the milestone Device Management Service Version 0.5.x – i.e DMS refactoring.
It consists of the following blogs, which are updated as needed:
- Ontology and nomenclature, which proposes the unified nomenclature and ontology of job orchestration to be used by NuNet in further development;
- Taxonomy of Job Scheduling, which takes a particularly useful meta-research on job scheduling and uses it as a basis for proposal for NuNet (as well as crystallizing the ontology and nomenclature);
- Scheduling and orchestration – builds on top of 1 to propose job orchestration semantics;
- Detailed Job Orchestration Sequences – builds of the 1,2 and 3 to provide detailed job orchestration semantics for further technical specification; Job Orchestration semantics is at the center of NuNet platform functinality;
- NuNet Framework Stakeholder Mapping, describing ontology of the whole framework, including external stakeholders, components, component classes, etc.
- Gossip, DHT and push/pull mechanisms – technical research for choosing technologies for routing messages in the network, for enabling job orcestration semantics;
- Kubernetes Integration Specs – design of Kubernetes interoperability layer to enable Kubernetes clusters to orchestrate pods on machines provisioned via NuNet;
The goal would be to collaborate on these specifications, which we can do by proposing merge requests to each post using the link provided below, linking to source files on Gitlab. After reaching initial agreement about platform design aspects, we proceed to define precise architecture and implementation issues via our specification/documentation process process.