https://github.com/redhat-cop/babylon_agnostics
Ansible role for interacting with the scheduler (https://github.com/redhat-gpe/AgnosticS ) from anarchy babylon governor
https://github.com/redhat-cop/babylon_agnostics
babylon gpte
Last synced: 12 days ago
JSON representation
Ansible role for interacting with the scheduler (https://github.com/redhat-gpe/AgnosticS ) from anarchy babylon governor
- Host: GitHub
- URL: https://github.com/redhat-cop/babylon_agnostics
- Owner: redhat-cop
- License: mit
- Created: 2020-10-09T15:31:30.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2023-08-21T03:56:26.000Z (almost 3 years ago)
- Last Synced: 2026-04-21T09:53:10.798Z (about 2 months ago)
- Topics: babylon, gpte
- Language: Python
- Homepage:
- Size: 18.6 KB
- Stars: 0
- Watchers: 12
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: readme.adoc
- License: LICENSE
Awesome Lists containing this project
README
= babylon_agnostics
This roles allows you to communicate with the link:https://github.com/redhat-gpe/agnostics[AgnosticS scheduler].
It is to be used in link:https://github.com/redhat-cop/babylon[Babylon] link:https://github.com/redhat-cop/anarchy[Anarchy].
This role does the following:
. call the scheduler
. Look for a corresponding secret in the provided namespace (default is `gpte`)
. load that secret
. inject it back into `dynamic_job_vars`
== Input ==
For *input* variables, please refer to link:defaults/main.yaml[].
The credentials to access the API can be loaded via an OpenShift secret in your OCP Babylon cluster and the special var `agnostics_mgr_access`. For example, if you created a secret `agnostics-api-mgr-access` in the `agnostics` namespace, you can inject it into the `agnostics_mgr_access` this way:
.using agnosticv-operator:
[source,yaml]
----
__meta__:
secrets:
- name: agnostics-api-mgr-access
namespace: agnostics
var: agnostics_mgr_access
----
.using Anarchy Governor directly:
[source,yaml]
----
spec:
varSecrets:
- name: agnostics-api-mgr-access
namespace: agnostics
var: agnostics_mgr_access
----
The following **output** variables will be set using `set_fact` module.
|=============================================
| Variable name | example | Purpose
| `agnostics_placement_cloud`
| openstack-orange
| The name of the cloud
|=============================================