bootstrapping

Bootstrapping

(At the moment this is a design document to show how we want to achieve our goal)

If you want to fork the elexis-admin project or just test a few changes, clone this repository, make your changes and when installing point to your new location
if a OC wants to change a few parts of this project, e.g. prefers to use MySQL instead of PostgreSQL then copy the OC folder to a private location. Convert it into a git archive, add your changes and make it accessible to your clients.
copy the Arztpraxis folder to a private location, fill in all the needed values and make it accessible as a git repository
Install the archivista VM and change the root password to something safe!
ssh root@archivista
Download the elexis-archivista-latest.deb from the repository subdirectory here
Download the elexis-archivista-latest.iso from the images subdirectory here
dpkg -i elexis-archivista-latest.deb # will create some configuration for virtual machine
- give the correct URL for the elexis-admin project
- give the correct URL for the OC config project (default to OC)
- give the correct URL for the concrete medical practice config project (defaults to Arztpraxis)
- give the correct URL for the OpenVPN configuration directory (if desired). This will allow you from the start to have a secure link to your server.
Use the web interface of archivista to start the desired machine(s)

Script gen_elexis_vm.sh generates unique MAC (starting with 00:60:13:87:52) for each VM. Idea: replace 87:52 with supplier/client-id to make it really unique)
Puppet will download the configuration, set its hostname depending on its MAC-address.
Optionally the first VM may install a (local) DNS-Cache-Server (dbndns or pdnsd?)
If not the OC must do this on the local DNS-Server(e.g. firewall)

Idea	Advantages	Disadvantages	Open points
Per client unique ISO	Can includes ssh/openvpn certificates	??	Script for certificates/iso-generation
gen_elexis_vm.sh asks for client config	Could download config, add keys, store locally	Backup?	script
Use Puppetmaster	defaults to polling every 30 minutes and updating automatically	I prefer to be at the client site to perform an update	Disable polling? Lockfile on server?

Decision: work with one incomplete solution. Decide once we have more than 5 clients. (ng: 11.06.2011)