08 September 2020

AuriStor offers clients for Debian and Ubuntu x86_64 architectures

Debian and Ubuntu client configuration

Along with our support for RPM-based Linux distributions, AuriStor supports platforms which use deb packages. 

Configuration is slightly more manual than the RPM repo situation, but is still pretty easy. You need to know what distribution you're running, which you can check with lsb_release -c. 

Here is an example for Ubuntu 18.04 (bionic) 

Setup

To do a client install, two files are required:

* /etc/apt/sources.list.d/auristor-client.list

This is a mostly normal Debian/Ubuntu repository specification. You can specify a specific version (for instance, v0.197) or go with the current recommended version ("recommended"). The file would thus contain a string like:

deb [arch=amd64] https://client-rpm-repo.auristor.com/filesystem/repo/v0.197/bionic/ bionic client

or

deb [arch=amd64] https://client-rpm-repo.auristor.com/filesystem/repo/recommended/bionic/ bionic client

* /etc/apt/trusted.gpg.d/AURISTOR-GPG-KEY-v1.gpg

This is a binary gpg key file for the Auristor client library.  If the armored version of the file is on hand, the requisite file can be generated with the command:

        gpg --dearmor AURISTOR-GPG-KEY-v1

Else you can

        apt-key add AURISTOR-GPG-KEY-v1

Installation

You're now ready to install!

    apt update

    apt install auristorfs-modules3-`uname -r`

    apt install auristorfs-client

At this point, your system has an installed client. The installed service is auristorfs-client, so you can use e.g.

    systemctl start auristorfs-client

and 

    systemctl status auristorfs-client

to check it; if you're happy, 

    systemctl enable auristorfs-client

and it will be started for subsequent boots.


1 comment:

  1. For all who has the same problem with the not working usually unattended-upgrades of the kernel-modules after a kernel-update, here is our little workaround:



    For everyone who has the same problem with the non-functioning
    unattended upgrades of the kernel modules, here is our little workaround:

    We configure a little ExecStartPre-Script which install the matching kernel-module for the running kernel before the auristor-client will be started

    cat /etc/systemd/system/auristorfs-client.service.d/yfs-kmod.conf

    [Service]
    ExecStartPre=/usr/local/sbin/update-yfs-kmod.sh
    ExecStartPre=/sbin/modprobe yfs

    and

    and


    cat /usr/local/sbin/update-yfs-kmod.sh
    #!/bin/bash


    dpkg -l | grep -q auristorfs-modules3-$(uname -r)

    if [[ $? -eq 0 ]]; then
    logger -t $(basename $0) "YFS module for $(uname -r) already installed, exiting."
    exit 0
    else
    logger -t $(basename $0) "YFS module not present for running kernel $(uname -r), installing."
    for attempt in $(seq 4); do
    host installserver.de > /dev/null && break;
    logger -t $(basename $0) "waiting for installserver.de name to be resolved"
    sleep 10;
    done
    DEBIAN_FRONTEND=noninteractive apt-get -q update
    DEBIAN_FRONTEND=noninteractive apt-get --yes -q install "auristorfs-modules3-$(uname -r)"
    logger -t $(basename $0) "Installation of auristorfs-modules3-$(uname -r) had exit code ${?}"
    exit 0
    fi


    Hope, it helps somebody

    cheers,
    martin

    ReplyDelete