Uploaded image for project: 'Mender'
  1. Mender
  2. MEN-1214

Installation wizard

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Rejected
    • Priority: Medium
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Epic Name:
      Installation wizard
    • Epic Total Estimate:
      10
    • DoD:
      show more show less

      Description

      The purpose of this Epic is to simplify getting started with Mender, especially for testing/demo purposes, but also to move toward unifying demo and production installations by making the demo environment more configurable and secure.

      It is based on the fairly standard approach of having an "install script" that will install and prepare Mender for your environment (Maciej Mrowiec already made a simple version of this in the past). E.g.

      ./mender-install
      Downlaoding Mender...
      Initial user email: ...
      Initial user password: ***
      Gateway address [docker.mender.io]:
      ...
      

      This script will be interactive and ask the user about relevant configuration options needed for the installation (e.g. hostname/IP addresses, virtual devices to start, etc.).

      Acceptance criteria

      • Dependencies are verified before starting and a notification about any missing dependencies or too old versions is displayed (most notably Docker Engine 1.11 and Docker Compose 1.6)
      • The installation is backed by git, like our Production installation
      • Initial user email and password is prompted and created
      • URL and port to backend gateway API and storage proxy can be set (default like today)
      • All keys are generated, based on input API and Storage Proxy CN (default like today, but keys are always generated)
      • It is noted where server.crt file is placed - (this is to be installed on Mender clients)
      • User is asked if he want to have virtual devices, and if so the relevant Artifacts are downloaded and modified (right URLs/keys), and the QEMU instance uses correct URLs and keys
      • User is asked if he wants BBB device, and if so the demo sdimg and Artifact is downloaded and modified
      • Designed in such a way that it can be used for production installs and upgrading the server in a future iteration

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                a10003 Eystein Maloy Stenberg
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support

                    Summary Panel