Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

Liquid Host by Mind Map: Liquid Host
3.0 stars - 1 reviews range from 0 to 5

Liquid Host

Context/Assumptions/Goals

openSUSE 11.1

maintains compatibility with yast and standard admin tools

installs core stack directly

core stack can move independent of ditro release/politics

non-central and stable services may rely on distro, postfix, imap, ldap

Manages Key Services

Why Bother?

latest versions

had experience with really wanting features in latest Postgres and Apache, distro a semi-major version behind

multiple versions

it's not that hard

in fact, may be easier than not

we're not trying to reinvent the wheel

firmer foundation

distros do change layout

need to control integration between services

upgrade distro freely while maintaining stack version

this is the other side of the latest version; I've got stuff running Tomcat 4.x, want latest distro, but would be huge hassle to change tomcat versions

aesthetics

I like to put everything necessary for a project in the project, not scattered around the system

increases inter-distro portability

obviously Liquid Host itself only supports openSUSE (though no reason it should be limited to that), but the services themselves could be set up on any machine in the same way to get apps running on other distros, which is really the point. This stuff is, for me, all about making it easier to get stuff deployed

Design

bulk of scripts manage single service

service scripts in '.liquid-host'

master script for CL control deployed to users bin

individual scripts can be accessed by wrappers

service script interface

--query

--configure

--remove

--start

--restart

--stop

--update

--info

interface conventions

'fail' is the common failure indicator

try to make equivalent outcomes easily scannable, avoid scan interference

future: convention for output

future: liquid_host is itself a service

future: special scripts

list services

show common config

set common config

common config wizard

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

in other words, it's like a package manager, you may have 100 service scripts in your .liquid-host dir, but only 10 services installed; you always have all the scripts (for a given version)

kibbles vs. service configuration

kibbles variables in .liquid_host/etc

service configurations in natural place

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

build services with reasonable, but usable defaults

not all services build with reasonable defaults; they're often "too open"

Install

support new install

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

gathers hosts (domain == root host)

interface

xen

query

configure

host info

host deploy

host rename

host configure

host add volume

volume query

volume add

configure

mail

query

configure

domain add

domain remove

alias add

alias remove

apache web

query

configure

start

stop

domain add

domain remove

domain configure

domain query

tomcat web

query

configure

start stop

domains

list

add

remove

configure

db server

query

db add

db remove

db query

db configure

volume

query

add

remove

configure

backup

keys

query

add

remove

New node

liquid_host_install.sh