From 238b0853711b91422eff5b97397b549a66370f72 Mon Sep 17 00:00:00 2001 From: elijah Date: Wed, 14 Sep 2016 15:31:42 -0700 Subject: refresh /docs/ --- docs/en/upgrading/upgrade-0-8.html | 3 + docs/en/upgrading/upgrade-0-9.html | 149 +++++++++++++++++++++++++++++++++++++ 2 files changed, 152 insertions(+) create mode 100644 docs/en/upgrading/upgrade-0-9.html (limited to 'docs/en/upgrading') diff --git a/docs/en/upgrading/upgrade-0-8.html b/docs/en/upgrading/upgrade-0-8.html index bb0d4974..275abd11 100644 --- a/docs/en/upgrading/upgrade-0-8.html +++ b/docs/en/upgrading/upgrade-0-8.html @@ -77,6 +77,9 @@ Upgrade to 0.8 - LEAP Platform Documentation
  • Upgrading
    • +
  • +Upgrade to 0.9 +
  • Upgrade to 0.8
    • diff --git a/docs/en/upgrading/upgrade-0-9.html b/docs/en/upgrading/upgrade-0-9.html new file mode 100644 index 00000000..cb78569d --- /dev/null +++ b/docs/en/upgrading/upgrade-0-9.html @@ -0,0 +1,149 @@ + + + + +Upgrade to 0.9 - LEAP Platform Documentation + + + + + + + + +
    +
    +

    Upgrade to 0.9

    + +
    +
    +
    +

    Upgrading to Platform 0.9

    + +

    You will need the new version of leap_cli:

    + +
    workstation$ sudo gem install leap_cli --version=1.9
+
    + +

    If you don’t want to install using ‘sudo’:

    + +
    workstation$ gem install --user-install leap_cli --version=1.9
+workstation$ PATH="$PATH:$(ruby -e 'puts Gem.user_dir')/bin"
+
    + +

    Because 0.9 does not use submodules anymore, you must remove them before pulling +the latest leap_platform from git:

    + +
    workstation$ cd leap_platform
+workstation$ for dir in $(git submodule | awk '{print $2}'); do
+workstation$   git submodule deinit $dir
+workstation$ done
+workstation$ git pull
+workstation$ git checkout 0.9.0
+
    + +

    Alternately, just clone a fresh leap_platform:

    + +
    workstation$ git clone https://leap.se/git/leap_platform
+workstation$ cd leap_platform
+workstation$ git checkout 0.9.0
+
    + +

    Then, just deploy

    + +
    workstation$ cd PROVIDER_DIR
+workstation$ leap deploy
+
    + +

    Known issues

    + +

    When upgrading, sometimes systemd does not report the correct state of a daemon. +The daemon will be not running, but systemd thinks it is. The symptom of this is +that a deploy will succeed but leap test will fail. To fix, you can run +systemctl stop DAEMON and then systemctl start DAEMON on the affected host +(systemctl restart seems to work less reliably).

    + +
    +
    + + -- cgit v1.2.3