Ansible playbooks for a SAMBA domain controller with NethServer - Progetto Scuola, BgLUG.
Go to file
2015-10-31 01:15:32 +01:00
roles Fixing some minor issues on run.sh and lock-nethrelease. 2015-10-31 01:15:32 +01:00
utils
vagrant Updated vagrant provisioning for box 1.1.0. Little corrections to tasks for network configuration on setup playbook. 2015-09-06 14:51:36 +02:00
.gitignore Selecting only edubuntu desktop as DE. 2015-09-30 09:37:28 +02:00
ansible.cfg
domain.yml Modifica dominio locale per problemi con mdns. 2015-06-25 20:46:03 +02:00
hosts
init.yml
mirror.yml Consider default to have NFS mirror served. 2015-10-31 00:58:59 +01:00
README.md Other adjustments on the README page. Some clarifications, rephrased some passages. 2015-07-22 01:40:01 +02:00
run.sh Fixing some minor issues on run.sh and lock-nethrelease. 2015-10-31 01:15:32 +01:00
setup.yml Managed mirroring with NFS with additional mirror.yml file. 2015-10-31 00:55:10 +01:00
Vagrantfile Removed port forwarding from Vagrant. Host-only NIC has to be configured via provisioning, to cope with interface name change. 2015-09-06 20:35:27 +02:00

Ansible playbooks for a SAMBA domain controller with NethServer

Progetto Scuola BgLUG Logo BgLUG - Scenary 1

Starting from a NethServer configured machine (please check out the wiki for the installation process from CentOS and other requirements), these playbooks provision a SAMBA 3.0 domain controller which can be used with a network of Ubuntu clients.

Using the default settings, it will also provide an environment to boot from network, install and configure the clients, using a local copy of Ubuntu's repositories.

Quick start

You may use these playbooks as follows:

$ vim hosts
$ vim domain.yml
$ ansible-playbook init.yml --ask-pass -e "admin_sshkey=/path/to/id_rsa.pub"
$ ansible-playbook setup.yml 

Or, more simply:

$ bash run.sh

Use Vagrant for testing purposes

You may use the included Vagrantfile to do any tests before deploying the machine. vagrant and ansible must be installed on the host machine, then you may run the following commands:

$ cd /path/to/server-config
$ vagrant up

Update 14/06/2015: some basic configurations to the Vagrant box are now provisioned via Ansible, thus making it a dependency.

Update 25/06/2015: the Vagrant box now uses a host-only interface instead of a bridged one. If you built a Vagrant box before this date, please destroy it, recreate a new one and reprovision it with the provided playbooks.

To Do List

  • Implement backup
  • Detail physical installation procedure for the server machine within the Wiki.