Interactive configuration of mender client

Description

In MEN-2314 we create a .deb package to easily install Mender. This will also be the main path for onboarding new users, using application updates (MEN-2363), so it needs to be very streamlined and easy. To make this easier, we here introduce support for a "wizard" for the most important configuration for attended installations.

User value (why)

  • For new users to easily install Mender during onboarding

Size (SP)

  • 40

Acceptance criteria:

  • There is an interactive menu during attended installs of Mender client which asks for

    • server URL (https://hosted.mender.io is the default)

    • device type

    • whether to use demo or production settings (with one-line intro what this means: polling intervals & demo certificate)

  • If Hosted Mender is used, the user inputs his credentials and the TenantToken is obtained and stored in mender.conf automatically

  • Mender service is started after configuration is done

  • A short final message stating Mender has been started and will be available in server within a few minutes, with a link to the URL of the server's pending devices

  • Installation documentation updated (shortened)

Risk & mitigation

None

Market Goal

Improve time-to-value by lowering barriers to real application deployment during onboarding
100% Done
Loading...

Checklist

Activity

Show:

Lluis CamposNovember 21, 2019 at 3:14 PM

For future reference, this is the document that described the UX design: https://docs.google.com/document/d/1eIQx1azXSoNEkEgirou5w5aQ43qiGsnm0sJF3cc4xbs/edit#

eystein.maloy.stenbergSeptember 17, 2019 at 9:07 PM
Edited

now that current projects are wrapping up, it finally makes sense to take this in next sprint.

However, should we add an acceptance criteria & task about downstreaming this configuration tool to official Debian package as well, or should that be separate?

Michael ClellandApril 16, 2019 at 1:41 PM

Thanks , that makes sense!

Lluis CamposApril 16, 2019 at 1:00 PM

When installing the .deb package, I think we should assume it is installed in managed mode.

To allow setting it in standalone mode will require hackish logic in the package installation, I don't think it is a good idea. If any, we could print the commands that the user would need to switch to standalone mode.

Michael ClellandApril 16, 2019 at 12:42 PM

Should the install menu offer either managed or standalone mode? Or is it assumed that it is managed mode?

Fixed

Details

Assignee

Reporter

Epic Name

Goals

None

Priority

Backlog

yes

Zendesk Support

Checklist

Created January 9, 2019 at 9:34 AM
Updated June 25, 2024 at 12:02 PM
Resolved November 11, 2019 at 1:58 PM