a1602f7e5e
1. What is the problem? In production clouds, each availability zone (AZ) is built by modularized OpenStack instances. Each OpenStack instance acts as a pod. One AZ consists of multiple pods. Among the pods within an AZ, they are classified into different categories for different proposes, for instance, general propose, CAD modeling and so on. Each tenant is bound to one pod, where it creates various types of resources. However such a binding relationship should be dynamic instead of static. For instance when some resources in the pod are exhausted, tenant needs to be bound to a new pod in same AZ. 2. What is the solution to the problem? To deal with the above problem, the Tricircle dynamically bind tenants to pod which has available resources. We call this feature dynamic pod binding 3. What the features need to be implemented to the Tricircle to realize the solution? To realize dynamic pod binding, the following features need to be implemented in the Tricircle. 1) To collect the usage in pod daily to evaluate whether the threshold is reached or not. 2) To filter and weigh all the available pods for cloud tenants to bind a tenant to a proper pod. 3) To manage and maintain all the active and historical binding relationship. This spec explains how Tricircle binds pods to tenants dynamically in detail. Blueprint: https://blueprints.launchpad.net/tricircle/+spec/dynamic-pod-binding Change-Id: Ib429a59d3d216e578f9c451d84c1fe9a333cf050 |
||
---|---|---|
.. | ||
dynamic-pod-binding.rst |