Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-1643

MicroShift should work on a host without NIC

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • openshift-4.15
    • None
    • None
    • MicroShift should work on a host without NIC
    • Proactive Architecture
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-839MicroShift technical enhancements V4.15
    • 0% To Do, 0% In Progress, 100% Done

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • We need to have configuration instructions for basic MicroShift functionality to work on a host that has no IP, route, or network access.
      • We need an automated test to verify that basic MicroShift functionality works on a host that has no IP, route, or network access.
      • We need public documentation for users to follow on RPM and ostree systems

      Why is this important?

      • MicroShift use-cases include occasionally disconnected environments (i.e. drones)

      Scenarios

      1. Start without network connection, plug a "network cable", verify all works
      2. Start with network connection, unplug a "network cable", verify all works

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • Public documentation written

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. https://docs.google.com/document/d/1Jxst5rq02J3DZAaytm31UTV7v-6xjWNqp-xsMTQAprI/edit

      Open questions::

      1. ...

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              jcope@redhat.com Jon Cope
              ggiguash@redhat.com Gregory Giguashvili
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: