Seperated storage nodes: ask IP to copy arakoon config file/etcd config

[kinvaris]

Currently, when trying to setup a HyperScale or GeoScale setup you have to execute these steps before trying the setup asd-manager setup:

#install the packages
openvstorage-sdb

#before starting the asd-manager setup
- copy /etc/init/sdm-etcd-config.conf to node
- adjust file for the already setup etcd cluster (see template)
- mkdir -p /opt/asd-manager/db/etcd/config/data
- chown alba:alba /opt/asd-manager/db/etcd/config/data -R
- start sdm-etcd-config
- asd-manager setup

#setup
asd-manager setup

Template:

description "Etcd (proxy) upstart for cluster config"

start on (local-filesystems and started networking)
stop on runlevel [016]

kill timeout 60
respawn
respawn limit 10 5
console log
setuid alba
setgid alba

env PYTHONPATH=/opt/asd-manager
chdir /opt/asd-manager

pre-start script
    if [ ! -d /opt/asd-manager/run ]
    then
        mkdir /opt/asd-manager/run
        chown alba:alba /opt/asd-manager/run
    fi
    echo `etcd --version | grep etcd | awk '{print $3}'` > /opt/asd-manager/run/etcd-config.version
end script

exec etcd -proxy on -data-dir /opt/asd-manager/db/etcd/config/data -listen-client-urls http://127.0.0.1:2379 -initial-cluster {% for etcd_proxy in etcd_cluster %}{{ etcd_proxy }}{% if not loop.last %},{% endif %}{% endfor %}

This should be implemented easier.

[khenderick]

Marked as feature as this semi-manual setup for non hyperconverged nodes was explicitly requested.

[wimpers]

@kinvaris please tackle in your ansible cookbook for now. Is this already added to the documentation?

[kinvaris]

@wimpers: this has already been tackled by the Ansible setup. Also I don't think this has already been added to the documentation.

[wimpers]

@kinvaris please add where you believe it should be added and create a PR.

[wimpers]

Since we moved to Arakoon as config mgmt, is the process still so cumbersome?

[khenderick]

Slightly less; in case of a hyperconverged setup, it will try to find and copy over the correct arakoon configuration file automatically. If not found, or a non-hyperconverged setup, the setup will ask for a file to copy.

[wimpers]

I'd like to keep this one open since the Arakoon as config mgmt has already solved the main issues (setting up the whole ETCD shebang).

Still copying over a file isn't really user friendly. Therefore an enhancement would be to ask for the IP of one of the master nodes and fetch the file from there. (Assuming the SSH keys have been generated in advance)