Blazar

De TeriaHowto
Version datée du 24 janvier 2024 à 10:59 par Chris (discussion | contributions) (Page créée avec « Let's experiment [https://docs.openstack.org/blazar/latest/ Blazar], Openstack dedicated service for resource reservation. == Concept == Imagine this situation : you provides two services, one with high priority, the other one with low priority. During the week, each service runs VMs on multiple node with auto-scaling capability (i.e. another VMs are automatically provisionned if the workload increases). You know that during the week-end, your higher priority s... »)
(diff) ← Version précédente | Voir la version actuelle (diff) | Version suivante → (diff)
Sauter à la navigation Sauter à la recherche

Let's experiment Blazar, Openstack dedicated service for resource reservation.

Concept

Imagine this situation : you provides two services, one with high priority, the other one with low priority. During the week, each service runs VMs on multiple node with auto-scaling capability (i.e. another VMs are automatically provisionned if the workload increases). You know that during the week-end, your higher priority service will have more demand and you don't want your lower priority service starving it from resources.
Blazar brings the possibility to reserve dedicated compute nodes for your high prority service for a time period, say, the week-end.
Best of all, unreserved compute nodes managed by Blazar can run preemptible VMs, avoiding unused computing power.

Installation

Kolla-ansible is used to deploy our private cloud.

Enable Blazar in globals.yml

enable_blazar: "yes"
kolla_enable_tls_internal: "no"
kolla_enable_tls_backend: "no"

Note that TLS should be disabled (especially for internal traffic). This is a current limitation identified.

Actiave preemptible instances in nova-scheduler