Artemis Roadmap

HW requirements

Implementing support for the guest requests to have more detailed HW requirements. Current Artemis does support only one such requirement, architecture, nothing else. Our goal is to implement the specification outlined by TMT here and its future extensions, focusing first on the simpler constraints (memory size, CPU core count, disk size, etc.) and moving towards more complex later, as the specification grows to support storage or CPU topology, or particular NIC vendor.

See #115 for details.

Multi-cluster deployment

To provide a reliable source of guests, support for multi-cluster deployments is a must. The details and the level of how much data would be shared among the instances are still being discussed.

See #116 for details.

K8s/OpenShift compliant application

By using all standard and best practices recommended for K8s and OpenShift application development and deployment, Artemis will aim to provide compliant packaging for easy deployment and management of Artemis instances.

See #130 for details.

Extended metrics

To improve observability and monitoring, Artemis will offer even more metrics than now, especially metrics related to operations and its components like broker or cache.

See #127 for details.

Guest cache

Instead of releasing pool resources when the fully provisioned guest request is canceled, the request would be put into a cache. Future requests may be satisfied from the cache, to avoid the provisioning process or save time by using already configured guests.

See #118 for details.

Pre-provisioning

Build on top of the guest cache, pre-provisioning would speed up provisioning of the most wanted types of guests. The plan is to manage parts of the cache automatically, periodically refilling the cache(s) as needed to keep the predefined amount of available guests.

See #117 for details.