Skip to content

Commit

Permalink
README.adoc: Add a standalone setup part
Browse files Browse the repository at this point in the history 
Signed-off-by: Erwann Roussy <[email protected]>
  • Loading branch information
@eroussy
eroussy committed Mar 21, 2024
1 parent 5dbf040 commit 53e4548
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions README.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -264,6 +264,18 @@ The --skip-tags "package-install" is there for ceph-ansible no to try to install

The --limit cluster_machines is there not to take into account the guests or standalone machines in the inventory.

=== Setting up a standalone machine

To set up a standalone machine, you can also use the playbook _cluster_setup_debian.yaml_ which regroups the other playbooks.

$ ansible-playbook -i inventories/standalone_inventory.yaml --limit standalone_machine playbooks/cluster_setup_debian.yaml

Or if you use `cqfd`:

$ cqfd run ansible-playbook -i inventories/standalone_inventory.yaml --limit standalone_machine playbooks/cluster_setup_debian.yaml

The --limit standalone_machine is there not to take into account the guests or cluster machines in the inventory.

=== Hardening ===

SEAPATH cluster security can be improved by running the Hardening playbook
Expand Down

2 comments on commit 53e4548

@dknueppe
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To avoid confusion in the naming scheme, would it not make sense if the setup playbook would be called something like system_setup_debian.yml instead of cluster_setup_debian.yml to reflect that it handles both cases - standalone and cluster? Same for other cluster* files. Also, what happens if you omit the --limit flag? Is that anything valid or will it constantly result in errors from playing the playbooks?

@eroussy
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regarding the naming, yes you are right, we should change that. There are other playbooks to rename like the CI playbooks
It is part of the Ansible refactoring (see #441 ). It will be done there.

Regarding the --limit flag, you don't need it here, in the inventory you provided because you only describe one standalone machine.
But it is useful when you have for example VMs or cluster machines all described in the same inventory.
It is just to avoid confusion.

Please sign in to comment.