Jump to: navigation, search

Valence use cases

Please append your use case to this list if not already covered.

Also consider voting for use cases that particularly interest you to help prioritize the work.

  1. A cloud deployer would like to create nodes for compute, storage, networking from pooled resources.
  2. A cloud deployer conversant with deployment tool foo (fuel, ansible, kolla, tripleO, ...) would like to deploy a cloud from a shared resource pool.
  3. A cloud deployer needs to expand their cloud beyond the resources afforded by a single data center.
  4. A cloud deployer would like to compose the server by combining special or high performance IO devices like GPU's, NVMe drives, HDD on demand from the IO resource pool and release them when not required.
  5. A cloud operator to meet transient additional load seeks to temporarily grow their cloud.
  6. A cloud operator on noticing lower utilization seeks to power off some nodes and reduce operating costs.
  7. A cloud operator on noticing consistent lower utilization over a day or two who like to release nodes back to the datacenter, and reduce costs.
  8. A cloud operator would like to be "notified" of resource/composed node status changes (power-on/off, HW/SW errors)
  9. A cloud deployer (OpenStack, Kubernetes, Mesos, CIAO, ..) would like to use the richer telemetry and topology information provided by Rack Scale Design for better initial job placement and workload rebalance (as workloads come and go). (e.g., OpenStack Nova or Watcher using the information)
  10. A data center operator would like to lease out resources to one or more cloud providers.
  11. A data center operator would like to allocate quotas to users, to serve as a resource usage upper bound.