summaryrefslogtreecommitdiff
path: root/clusters/openstack-cluster.morph
Commit message (Collapse)AuthorAgeFilesLines
* CLUSTER: fix swift storage device to sdbRichard Ipsum2015-03-091-1/+1
|
* CLUSTER: fix sdb fstab lineRichard Ipsum2015-03-091-1/+1
|
* CLUSTER: attach sdb1 to swiftstackRichard Ipsum2015-03-061-0/+2
|
* CLUSTER: deploy to shiny new thingRichard Ipsum2015-03-051-1/+1
|
* Add SWIFT_HASH_PATH vars to cluster morphRichard Ipsum2015-03-041-0/+2
| | | | | | | | | The deployer just needs to make these random unique values*, they must keep them secret and not lose them. So the cluster morph musn't be pushed to some public repo. * e.g. by running $ openssl rand -hex 10
* CLUSTER: SWIFT_STORAGE_DEVICES is a listRichard Ipsum2015-03-041-1/+1
| | | | | | TODO: please please add validation for this, user is guaranteed to typo or make syntax err which will not cause a problem till first boot of the node
* CLUSTER: install unitsRichard Ipsum2015-03-041-2/+2
|
* CLUSTER: deploy to homeRichard Ipsum2015-03-041-2/+2
|
* debugRichard Ipsum2015-03-041-2/+2
|
* modify cluster to suitRichard Ipsum2015-03-041-7/+5
|
* Make a unit for each type of nodeRichard Ipsum2015-03-041-0/+2
| | | | | | | | | swift-controller and swift-storage these units are enabled my specifying a flag in the cluster morph, SWIFT_CONTROLLER and SWIFT_STORAGE
* Add swift vars needed for ring creationRichard Ipsum2015-03-041-0/+4
|
* Add SWIFT_*_URL vars to clusterRichard Ipsum2015-03-041-0/+3
|
* Add MANAGEMENT_INTERFACE_IP_ADDRESS variableRichard Ipsum2015-03-041-0/+1
| | | | | | | | | Ideally this would be inferred from the network information provided in the cluster, but at the moment the means to do that aren't available so we're forced to have the deployer provide this address. Note that this address is the ip for *this* node (the node we are deploying) that sits on the management network.
* Add ip map stuff to cluster morphRichard Ipsum2015-03-041-0/+5
|
* SPLITME: Add all OpenstackFrancisco Redondo Marchena2015-03-041-0/+66