Liquid Host

Get Started. It's Free
or sign up with your email address
Rocket clouds
Liquid Host by Mind Map: Liquid Host

1. Context/Assumptions/Goals

1.1. openSUSE 11.1

1.2. maintains compatibility with yast and standard admin tools

1.3. installs core stack directly

1.3.1. core stack can move independent of ditro release/politics

1.3.2. non-central and stable services may rely on distro

1.3.2.1. postfix

1.3.2.2. imap

1.3.2.3. ldap

2. Manages Key Services

3. Why Bother?

3.1. latest versions

3.2. multiple versions

3.3. it's not that hard

3.3.1. in fact, may be easier than not

3.3.2. we're not trying to reinvent the wheel

3.4. firmer foundation

3.4.1. distros do change layout

3.4.2. need to control integration between services

3.5. upgrade distro freely while maintaining stack version

3.6. aesthetics

3.7. increases inter-distro portability

4. Design

4.1. bulk of scripts manage single service

4.1.1. service scripts in '.liquid-host'

4.1.2. master script for CL control deployed to users bin

4.1.3. individual scripts can be accessed by wrappers

4.2. service script interface

4.2.1. --query

4.2.2. --configure

4.2.3. --remove

4.2.4. --start

4.2.5. --restart

4.2.6. --stop

4.2.7. --update

4.2.8. --info

4.3. interface conventions

4.3.1. 'fail' is the common failure indicator

4.3.2. try to make equivalent outcomes easily scannable

4.3.2.1. avoid scan interference

4.4. future: convention for output

4.5. future: liquid_host is itself a service

4.6. future: special scripts

4.6.1. list services

4.6.2. show common config

4.6.3. set common config

4.6.4. common config wizard

4.7. complete set of scripts in liquid host, does not imply services installed locally

4.8. kibbles vs. service configuration

4.8.1. kibbles variables in .liquid_host/etc

4.8.2. service configurations in natural place

5. It's about reliably deploying a specific configuration with basic start/stop controls, NOT general administation

5.1. build services with reasonable, but usable defaults

6. Install

6.1. support new install

6.2. manually adapt web.liquid-labs.com host to conform to expectations

6.3. gathers hosts (domain == root host)

7. interface

7.1. xen

7.1.1. query

7.1.2. configure

7.1.3. host info

7.1.4. host deploy

7.1.5. host rename

7.1.6. host configure

7.1.7. host add volume

7.1.8. volume query

7.1.9. volume add

7.2. configure

7.3. mail

7.3.1. query

7.3.2. configure

7.3.3. domain add

7.3.4. domain remove

7.3.5. alias add

7.3.6. alias remove

7.4. apache web

7.4.1. query

7.4.2. configure

7.4.3. start

7.4.4. stop

7.4.5. domain add

7.4.6. domain remove

7.4.7. domain configure

7.4.8. domain query

7.5. tomcat web

7.5.1. query

7.5.2. configure

7.5.3. start stop

7.6. domains

7.6.1. list

7.6.2. add

7.6.3. remove

7.6.4. configure

7.7. db server

7.7.1. query

7.7.2. db add

7.7.3. db remove

7.7.4. db query

7.7.5. db configure

7.8. volume

7.8.1. query

7.8.2. add

7.8.3. remove

7.8.4. configure

7.8.5. backup

7.9. keys

7.9.1. query

7.9.2. add

7.9.3. remove

7.10. New node

7.11. liquid_host_install.sh