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

Update modules - i1 using file input

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Done
    • Priority: (None)
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:

      Description

      The purpose of update modules are:

      • Grow the Mender community
        • I.e. they must be very easy to write
      • Cover more use cases by enabling custom application level updates
        • Example: overwrite file, install .deb, overwrite a partition
        • Non-example: Asymmetric rootfs updates

      Longer-term an update module can have multiple actions, such as install, restart and rollback, but we will start with just supporting install.

      In order to take a user-first approach, we will have these two reference update modules that we write before the implementation:

      • /bin/sh <DATA-IN-ARTIFACT>
        • Also covers “apt-get update abc”
      • dpkg -i <DATA-IN-ARTIFACT>

      A easy to use design will mean that these update modules will be very short (very little extra code needed to "integrate" them into the Mender update module framework).

      Iterations:

      • Write reference modules
      • Define new update type
        • Artifact spec & implementation
      • Save headers and payload locally
        • So update module can access them
      • Client support for running module’s install action

      Refereces

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support

                    Summary Panel