Using Ansible to Manage install and update Apple OSX DHCP clients
-
@IRJ Each command individually?
-
@DustinB3403 said in Using Ansible to Manage install and update Apple OSX DHCP clients:
@IRJ Each command individually?
yes reinstall the role this way
-
@IRJ So wouldn't I have to delete the role first?
-
Also this fails.
sudo ansible-galaxy install -p roles -r /etc/ansible/requirements.yml [WARNING]: - /etc/ansible/apple.yml was NOT installed successfully: the file downloaded was not a tar.gz ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list. -
@DustinB3403 said in Using Ansible to Manage install and update Apple OSX DHCP clients:
@IRJ So wouldn't I have to delete the role first?
Just try running it first. If you delete the role, then the reference to source file will break.
-
@DustinB3403 said in Using Ansible to Manage install and update Apple OSX DHCP clients:
Also this fails.
sudo ansible-galaxy install -p roles -r /etc/ansible/requirements.yml
[WARNING]: - /etc/ansible/apple.yml was NOT installed successfully: the file downloaded was not a tar.gzERROR! - you can use --ignore-errors to skip failed roles and finish processing the list.
let me see your
/etc/ansible/requirements.yml -
cat /etc/ansible/requirements.yml - src: /etc/ansible/apple.yml - src: /etc/ansible/apple.yml - src: /etc/ansible/roles/geerlineguy -
@DustinB3403 said in Using Ansible to Manage install and update Apple OSX DHCP clients:
cat /etc/ansible/requirements.yml - src: /etc/ansible/apple.yml - src: /etc/ansible/apple.yml - src: /etc/ansible/roles/geerlineguyget rid of the first two entries
-
@IRJ just did, not sure why they're in there as I haven't touched this file.
-
@DustinB3403 said in Using Ansible to Manage install and update Apple OSX DHCP clients:
@IRJ just did, not sure why they're in there as I haven't touched this file.
They are there because we did echo command in script to add them.
-
sudo ansible-galaxy install -p roles -r /etc/ansible/requirements.yml - downloading role '/etc/ansible/roles/geerlineguy', owned by [WARNING]: - /etc/ansible/roles/geerlineguy was NOT installed successfully: Content has no field named 'owner' ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list. -
@DustinB3403 said in Using Ansible to Manage install and update Apple OSX DHCP clients:
sudo ansible-galaxy install -p roles -r /etc/ansible/requirements.yml
- downloading role '/etc/ansible/roles/geerlineguy', owned by
[WARNING]: - /etc/ansible/roles/geerlineguy was NOT installed successfully: Content has no field named 'owner'
ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list.
We need the master @stacksofplates
- downloading role '/etc/ansible/roles/geerlineguy', owned by
-
Running
ansible-playbook -i hosts apple.ymlansible-playbook -i hosts apple.yml PLAY [apple_workstations] ******************************************************************************************************************************************************************************************************************* TASK [Gathering Facts] ********************************************************************************************************************************************************************************************************************** ok: [x.x.x.143] PLAY RECAP ********************************************************************************************************************************************************************************************************************************** x.x.x.143 : ok=1 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0So I think the playbook and role are installed correctly.
-
@DustinB3403 said in Using Ansible to Manage install and update Apple OSX DHCP clients:
Running
ansible-playbook -i hosts apple.ymlansible-playbook -i hosts apple.yml
PLAY [apple_workstations] *******************************************************************************************************************************************************************************************************************
TASK [Gathering Facts] **********************************************************************************************************************************************************************************************************************
ok: [x.x.x.143]PLAY RECAP **********************************************************************************************************************************************************************************************************************************
x.x.x.143 : ok=1 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0So I think the playbook and role are installed correctly.
what changed?
-
@IRJ I used the test.yml file from within the geerlingguy tests folder.
I stated this up above.
What doesn't appear to work is anything actually being installed. . .
-
Ok I'm eating dinner and I'll make a post afterwards.
-
Ok. I made a skeleton repo for you here. This is how I set up all of my playbooks. I use a single repo for most of my playbooks and then the roles have their own repositories (because they're called in with Galaxy). I never use the
/etc/ansibledirectory because of permissions issues and it's not portable. You can take this one step further and use a virtualenv but that's for later after you get this working.It will be easiest if you fork this and have your own. Clone your copy locally and then put your playbook(s) in the top level folder of the repository. In the inventory directory, add a file called
macsor whatever your group is called, but still add the group name in the file like you would normally. It's just a nice way to be able to separate things out logically so you can see them easier. Also add any group_vars if you have them.Add your role to the
roles/requirements.ymlfile. Once you've added all of your files to your repo, commit your changes. Then runmake roles. It will remove any roles you've installed, and then reinstall them. Now you should be ready to run the playbook.You can also run
make cleanand it will reset your repository to the latest commit. So if you want to keep the work make sure to commit. -
Okay so this is my existing tree.
/etc/ansible/ ├── ansible.cfg ├── apple.yml ├── clients ├── default.config.yml ├── hosts ├── main.yml ├── playbook-skeleton │ ├── ansible.cfg │ ├── group_vars │ │ └── README │ ├── inventory │ │ ├── apple_workstations │ │ └── dev │ ├── library │ │ └── README │ ├── Makefile │ └── roles │ └── requirements.yml ├── requirements.yml ├── roles │ ├── ansible-role-homebrew │ │ ├── defaults │ │ │ └── main.yml │ │ ├── handlers │ │ │ └── main.yml │ │ ├── LICENSE │ │ ├── meta │ │ │ └── main.yml │ │ ├── README.md │ │ ├── requirements.yml │ │ ├── tasks │ │ │ ├── main.yml │ │ │ └── playbook.yml │ │ └── tests │ │ ├── local-testing │ │ │ ├── playbook.yml │ │ │ └── README.md │ │ └── test.yml │ ├── elliotweiser.osx-command-line-tools │ │ ├── ansible.cfg │ │ ├── CONTRIBUTING.md │ │ ├── defaults │ │ │ └── main.yml │ │ ├── handlers │ │ │ └── main.yml │ │ ├── LICENSE │ │ ├── meta │ │ │ └── main.yml │ │ ├── molecule │ │ │ ├── default │ │ │ │ ├── create.yml │ │ │ │ ├── destroy.yml │ │ │ │ ├── molecule.yml │ │ │ │ └── prepare.yml │ │ │ ├── elcapitan.sh │ │ │ ├── highsierra.sh │ │ │ ├── mojave.sh │ │ │ ├── sierra.sh │ │ │ ├── unset.sh │ │ │ └── yosemite.sh │ │ ├── README.md │ │ ├── tasks │ │ │ └── main.yml │ │ ├── tests │ │ │ ├── inventory │ │ │ ├── playbook.yml │ │ │ ├── test_default.py │ │ │ ├── test-requirements.txt │ │ │ └── version_check.py │ │ └── vars │ │ └── main.yml │ └── geerlingguy.homebrew │ ├── defaults │ │ └── main.yml │ ├── handlers │ │ └── main.yml │ ├── LICENSE │ ├── meta │ │ └── main.yml │ ├── README.md │ ├── requirements.yml │ ├── tasks │ │ ├── main.yml │ │ └── playbook.yml │ └── tests │ ├── local-testing │ │ ├── playbook.yml │ │ └── README.md │ └── test.yml └── ssh.sh 29 directories, 61 filesThe
makecommand wasn't found so I installedmake. Runningmake rolesfrom within the/etc/ansible/playbook-skeletonI gotmake roles git clean -fdx roles ansible-galaxy install -r roles/requirements.yml - extracting ansible-role-homebrew to /etc/ansible/playbook-skeleton/roles/ansible-role-homebrew - ansible-role-homebrew was installed successfully - adding dependency: elliotweiser.osx-command-line-tools - downloading role 'osx-command-line-tools', owned by elliotweiser - downloading role from https://github.com/elliotweiser/ansible-osx-command-line-tools/archive/2.2.1.tar.gz - extracting elliotweiser.osx-command-line-tools to /etc/ansible/playbook-skeleton/roles/elliotweiser.osx-command-line-tools - elliotweiser.osx-command-line-tools (2.2.1) was installed successfully -
@DustinB3403 said in Using Ansible to Manage install and update Apple OSX DHCP clients:
Okay so this is my existing tree.
The
makecommand wasn't found so I installedmake. Runningmake rolesfrom within the/etc/ansible/playbook-skeletonI gotmake roles
git clean -fdx roles
ansible-galaxy install -r roles/requirements.yml- extracting ansible-role-homebrew to /etc/ansible/playbook-skeleton/roles/ansible-role-homebrew
- ansible-role-homebrew was installed successfully
- adding dependency: elliotweiser.osx-command-line-tools
- downloading role 'osx-command-line-tools', owned by elliotweiser
- downloading role from https://github.com/elliotweiser/ansible-osx-command-line-tools/archive/2.2.1.tar.gz
- extracting elliotweiser.osx-command-line-tools to /etc/ansible/playbook-skeleton/roles/elliotweiser.osx-command-line-tools
- elliotweiser.osx-command-line-tools (2.2.1) was installed successfully
I think your missing my point. Don't use /etc/ansible.
Clone the repo somewhere in your home directory that you store your projects and run everything from there.
-
@stacksofplates eh. . .
Can I just use mv at this point?
