Vincent Van der Kussen
59749462c0
required varaibles / remove append group / blocks in shell
2018-08-26 15:10:15 +02:00
Vincent Van der Kussen
c53f502220
make distinction between bash and csh shell config
2018-08-18 14:07:19 +02:00
Serge van Ginderachter
95e4ee8c06
Import project for #9
...
add users, groups, authorized_keys, and dot files
2018-08-18 10:49:16 +02:00
Vincent V.d Kussen
caa1e1fa65
testing with FreeBSD on ec2
2018-08-18 10:13:25 +02:00
Vincent V.d Kussen
c1ab857680
add docs
2018-08-17 20:37:45 +02:00
Vincent V.d Kussen
935d660a1d
markdown column
2018-08-15 20:37:02 +02:00
Vincent V.d Kussen
a96d82d5ed
ssh-config role / docs / updated user config
2018-08-15 20:35:23 +02:00
Bryan Black
0fced972da
Thanks @vincentvdk
2018-08-13 10:50:40 -07:00
Vincent V.d Kussen
f12466dead
config users shell/ssh
2018-08-13 16:02:31 +02:00
Vincent V.d Kussen
47ef7a7045
initial work users role
2018-08-07 21:23:08 +02:00
Vincent V.d Kussen
7f67fa4c60
initial commit
2018-08-07 20:22:55 +02:00
Bryan Black
f5451349ac
add permalinks
2018-07-08 02:21:23 -07:00
Bryan Black
549549df8f
up the version
2018-07-07 15:47:38 -07:00
Bryan Black
c77eb0c4d3
fix name of repo and up the version number
...
github user tersmitten moved the ownership of their apt repo to the Oefenweb github org.
https://github.com/tersmitten/apt
https://github.com/Oefenweb/ansible-apt
2018-07-07 15:47:29 -07:00
Bryan Black
927566e306
fix typo
2018-06-12 10:37:46 -07:00
Bryan Black
22812d7f6f
fix typo
2018-06-11 15:30:02 -07:00
Bryan Black
41e07611ee
Fix typos
2018-06-11 12:43:57 -07:00
Bryan Black
c110c5316a
Merge pull request #8 from ginsys/feature-clean-up-ami-snapshots-#2
...
Clean up AMI and related snapshots
2018-06-11 10:38:33 -07:00
Serge van Ginderachter
3fa8629123
Clean up AMI and related snapshots
...
Playbook that removes old AMI's and the related snapshots
that were created using the ec2_ami module with machines
tagged MakeImage=true
2018-06-09 16:01:40 +02:00
Bryan Black
38b5df4372
add contributors and support button
2018-05-18 12:00:52 -07:00
Bryan Black
e4bbf8ca3d
add contributors and Support buttons
2018-05-18 11:57:55 -07:00
Bryan Black
b2906ebb14
all the things
2018-05-17 09:21:11 -07:00
Bryan Black
2ac163b811
add link to update playbook
2018-05-17 09:16:53 -07:00
Bryan Black
046bd4e92f
gif placement up
2018-05-16 16:27:11 -07:00
Bryan Black
5b8f113747
add wide gif
2018-05-16 16:26:29 -07:00
Bryan Black
179eb1bfca
add gif
2018-05-16 16:09:46 -07:00
Bryan Black
afabde03ce
add gif
2018-05-16 16:09:00 -07:00
Bryan Black
c0074cc5dc
add rtfm
2018-05-16 15:52:09 -07:00
Bryan Black
671dcb0648
add instructions, emojis, and 2nd H1
2018-05-16 15:46:02 -07:00
Bryan Black
d56582ab15
Clarity
2018-05-16 15:36:16 -07:00
Bryan Black
4f0fc41adb
Add instructions
2018-05-16 15:31:17 -07:00
Bryan Black
e062b9ca9a
Update package_updates README
2018-05-16 14:40:45 -07:00
Bryan Black
6159e49e04
add my shitty instructions
2018-05-15 19:22:13 -07:00
Bryan Black
3707750246
fix for #7
...
Fix for https://github.com/stationgroup/ansible-experiments/issues/7
I think `freebsd-update` return failed even when _"No updates needed"_ or _"No update are available"_. https://github.com/freebsd/pkg/issues/1470
```
failed_when: False # --dry-run always returns failure
# https://github.com/freebsd/pkg/issues/1470
```
2018-05-15 10:20:13 -07:00
Bryan Black
7c04dfed2b
/bin/sh compatibility
2018-05-14 21:47:18 -07:00
Bryan Black
58ce5f14f2
fix for 'No updates are available to install' error
...
resolves common problem of false `No updates are available to install` errors after updating FreeBSD base OS files.
```yml
TASK [freebsd-update : Install FreeBSD updates] ****************************************************
fatal: [freebsd6]: FAILED! => {"changed": true, "cmd": ["freebsd-update", "install", "--not-running-from-cron"], "delta": "0:00:00.274477", "end": "2018-05-14 18:13:56.977638", "msg": "non-zero return code", "rc": 1, "start": "2018-05-14 18:13:56.703161", "stderr": "rm: filelist: No such file or directory", "stderr_lines": ["rm: filelist: No such file or directory"], "stdout": "src component not installed, skipped\nInstalling updates...", "stdout_lines": ["src component not installed, skipped", "Installing updates..."]}
changed: [freebsd5]
TASK [freebsd-update : debug] **********************************************************************
```
2018-05-14 11:29:22 -07:00
Bryan Black
3981829d0a
Merge pull request #5 from ginsys/feature-package-updates-#4
...
Feature package updates #4
2018-05-12 15:04:48 -07:00
Serge van Ginderachter
4a06112096
install correct dependency version
2018-05-12 14:34:13 +02:00
Serge van Ginderachter
aa4cd65e69
setup script does all from vagrant up to check upgrade'
2018-05-12 14:33:13 +02:00
Serge van Ginderachter
d54b537240
Fix typo - Ubuntu dynamic group name
2018-05-12 13:12:08 +02:00
Serge van Ginderachter
21943464f5
fix: let ansible install handle dependencies
...
and add proper task names
2018-05-12 13:11:30 +02:00
Serge van Ginderachter
1671c7b1e2
fix: pkg upgrade --dry-run always returns an error
...
It is considered as the same flow as the user refusing to perform the actual
upgrade See https://github.com/freebsd/pkg/issues/1470
2018-05-12 12:50:57 +02:00
Serge van Ginderachter
b1a9d16f50
avoid provisioning timeout for freebsd
2018-05-12 12:50:57 +02:00
Bryan Black
23ee2bf873
uncomment work around
...
01baf3d0ec
2018-05-11 19:35:38 -07:00
Bryan Black
9c9ed4950d
increase key length
2018-05-11 17:38:54 -07:00
Bryan Black
15245a47a9
fix for #4 by apt update
...
Fixe for https://github.com/stationgroup/ansible-experiments/issues/4 by running `apt update` before installing `python`.
2018-05-11 17:38:30 -07:00
Bryan Black
5963e5d413
Merge pull request #3 from ginsys/feature-package-updates-#1
...
Update packages on ubuntu and freebsd
### Merging to make testing easier
So I don't have to keep going to the ginsys repo.
2018-05-11 14:51:14 -07:00
Bryan Black
e6cd6bc239
fix typo ubuntu
2018-05-11 14:14:38 -07:00
Serge van Ginderachter
dac2298622
Update packages on ubuntu and freebsd
...
Fixes #1
The Vagrant file being used is a copy from
`https://github.com/stationgroup/vagrant-labs/tree/master/imperialspeculate `.
Two roles are being used: debian-upgrade (an upstream Galaxy role) and
freebsd-upgrade (a small role based on what was proposed in the comments of #1
and extended with proper support for check mode.)
The upgrade process is contained in the playbook os_upgrade.yml, which will
automatically create proper groups for Ubuntu and FreeBSD hosts. If unneeded,
this first play can be left out, and the target hosts: in the second play can be
replaced by the relevant groups you have in the inventory (e.g. ec2 tags.)
A local ansible.cfg is defined, and needed for these scripts to run out of the
box. This implies that all ansible commands must be run from the
`ansible-experiments/package_updates` folder.
A small script `setup-requirements` is provided, that initializes everything,
to be executed after the vagrant boxes came online. It will generate an
ssh-config for said vagrant boxes, download roles from galaxy, and make a
base-install for the hosts (installing python dependencies, ansible itself
on ubuntu1, a deploying an ssh key to all nodes to be used from the vagrant box
`ubuntu1`, as ansible controller machine.)
When deploying and setting up from the machine where vagrant runs, you need to
add some extra arguments:
`--ssh-extra-args "-F ./vagrant-ssh-config" --inventory hosts-vagrant`
to ansible execution. These are not necessary once running ansible from
`ubuntu1`.
The vagrant setup seems to have a provisioning bug, that kicks in with the
latest 18.04 Ubuntu. The FreeBSD boxes also experience a provisioning problem,
with the same result: the second, private network interface does not get
configured. As these interfaces are used to run ansible from `ubuntu1`, I could
not fully test the scripts from there.
2018-05-11 16:37:03 +02:00
Bryan Black
31e3a0352a
Create LICENSE
2018-03-28 17:38:34 -07:00