https://github.com/ai4os/ai4-ansible
Ansible roles to deploy the federated nomad cluster
Science Score: 26.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (8.2%) to scientific vocabulary
Repository
Ansible roles to deploy the federated nomad cluster
Basic Info
Statistics
- Stars: 0
- Watchers: 5
- Forks: 1
- Open Issues: 8
- Releases: 1
Metadata Files
README.md
Ansible roles for Consul, Nomad and Traefik automated deployment
These are the Ansible roles to manage the federated Nomad cluster in the AI4OS project. The Ansible roles are valid to manage both iMagine and AI4EOSC sites.
Ansible configuration
The machine running Ansible commands will be referred subsequently as Ansible master.
The ssh public key (id_rsa.pub) of the Ansible master must be added to every node
it manages (Ansible slave), inside .ssh/authorized_keys.
Ansible hosts file
The default location for this file is /etc/ansible/hosts.
The file can also be specified at the command line using the -i hosts option when
executing.
console
ansible-playbook -i hosts <playbook>
SSH config file
This file configures a bastion node with a public IP which will be used as a proxy to provide SSH access to the rest of the nodes in that subnet.
The bastion node will be the server node of the new site, which will be used to connect to the client nodes of the new site (which do not have public IP).
Copy config_template into a config file with name
config. The location for this file must be the SSH folder (.ssh/config).Modify the config file to match the cluster configuration. An example can be found on config_example.
The following parameters must be set:
- bastion-name is the name of the server node.
- bastion-public-ip is the public IP associated to the server node.
- ssh-username is the username of the server node's machine.
If it was created with an Ubuntu flavour
(see Create nodes - step 3),
this username will be ubuntu.
- private-ips-on-bastion-subnet are the set of private IPs of the client nodes.
It can be configured as <subnet>.*, as in the example below.
Template:
```
Host
Host
Example: ``` Host node-ifca-0 User ubuntu Hostname 193.146.75.205
Host 172.16.44.* ProxyJump node-ifca-0 ```
Usage
IFCA admin
This use cases are aimed at IFCA admins.
Create federated cluster
To create a new federated cluster from scratch, the IFCA admin must complete the following step:
Add a new site to the federated cluster
To include a new site to the federated cluster, the IFCA admin must complete the following steps:
- Run Ansible to create the required certificates for the new site
- Configure your Openstack to integrate the new site
Site admin
To join the federated cluster with a new site, the new site admin must complete the following steps:
Version update
To update Consul or Nomad versions on any nodes, the following step must be completed:
Owner
- Name: AI4OS
- Login: ai4os
- Kind: organization
- Email: ai4eosc-po@listas.csic.es
- Website: http://ai4eosc.eu
- Twitter: AI4EOSC
- Repositories: 1
- Profile: https://github.com/ai4os
AI4OS is the software powering the AI4EOSC platform
GitHub Events
Total
- Issues event: 6
- Delete event: 2
- Member event: 1
- Issue comment event: 27
- Push event: 28
- Pull request review event: 8
- Pull request event: 19
- Fork event: 1
- Create event: 9
Last Year
- Issues event: 6
- Delete event: 2
- Member event: 1
- Issue comment event: 27
- Push event: 28
- Pull request review event: 8
- Pull request event: 19
- Fork event: 1
- Create event: 9
Issues and Pull Requests
Last synced: 10 months ago
All Time
- Total issues: 5
- Total pull requests: 3
- Average time to close issues: 11 days
- Average time to close pull requests: about 1 month
- Total issue authors: 2
- Total pull request authors: 2
- Average comments per issue: 0.4
- Average comments per pull request: 0.33
- Merged pull requests: 1
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 5
- Pull requests: 3
- Average time to close issues: 11 days
- Average time to close pull requests: about 1 month
- Issue authors: 2
- Pull request authors: 2
- Average comments per issue: 0.4
- Average comments per pull request: 0.33
- Merged pull requests: 1
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- IgnacioHeredia (4)
- micafer (2)
- Sftobias (2)
Pull Request Authors
- micafer (29)
- Sftobias (19)
- IgnacioHeredia (1)
- Stifo (1)