Other adjustments on the README page. Some clarifications, rephrased some passages.

This commit is contained in:
Emiliano Vavassori 2015-07-22 01:40:01 +02:00
parent 18f5368b49
commit 93d95f5abd
1 changed files with 16 additions and 15 deletions

View File

@ -1,10 +1,11 @@
# Ansible configuration playbooks for SMB domain controller with NethServer #
# Ansible playbooks for a SAMBA domain controller with NethServer #
## Progetto Scuola [<img src="https://avatars1.githubusercontent.com/u/12886037?v=3&s=200" width="25" height="25" alt="BgLUG Logo" /> BgLUG][bglug] - Scenary 1 ##
Starting from a [NethServer][] configured machine (please check out the
[wiki][]), these playbooks provision a SMB domain controller which can be
used with a network of Ubuntu clients.
[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
@ -12,25 +13,22 @@ repositories.
### Quick start ###
You may use this repo proceeding as follows:
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 init.yml --ask-pass -e "admin_sshkey=/path/to/id_rsa.pub"
$ ansible-playbook setup.yml
Or, more simply:
$ bash run.sh
### Use [`vagrant`][vagrant] for testing purposes ###
### Use [Vagrant][] for testing purposes ###
You may use the included `Vagrantfile` to do any tests before deploying the
machine.
You just need `vagrant` and `ansible` installed on the host machine, then you
may run the following commands:
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
@ -39,7 +37,8 @@ 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.
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 ###
@ -48,7 +47,9 @@ a *bridged* one.
Wiki.
[bglug]: http://bglug.it/ "BgLUG Homepage"
[ansible]: http://www.ansible.com "Ansible Homepage"
[nethserver]: http://www.nethserver.org "NethServer Homepage"
[vagrant]: http://www.vagrantup.com "Vagrant Homepage"
[wiki]: https://github.com/bglug-it/server-config/wiki "server-config wiki"
[ansible]: http://www.ansible.com
[nethserver]: http://www.nethserver.org
[vagrant]: http://www.vagrantup.com
[samba]: https://www.samba.org
[centos]: https://www.centos.org