Uploaded image for project: 'OpenShift Cloud'
  1. OpenShift Cloud
  2. OCPCLOUD-2707

[AWS] Investigate DeviceIndex support in MAPA/CAPA

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • 3
    • False
    • None
    • False
    • OCPSTRAT-683 - Migrate MAPI to Cluster API for AWS -Phase 1
    • CLOUD Sprint 260

      Background

      MAPA has support for users to configure the Network DeviceIndex.

      According to aws, the primary network interface must use the value 0.

      It appears that CAPA already forces this (it only supports creating one primary network interface) or assigns these values automatically if you are supplying your own network interfaces.

      Therefore, it is likely that we do not need to support this value (MAPA only supports a single network interface), but we must be certain.

      Steps

      • Test what happens if the DeviceIndex is a non-zero value in MAPA
      • If it works, we need to come up with a way to convince CAPA to support a custom device index
      • If it does not work, then in theory no customer could be using this, and dropping support should be fine. Document this in the conversion library.

      Stakeholders

      • Cluster Infra

      Definition of Done

      • We have made a decision about the device index field and how to handle it. Be that always erroring perpetually, or finding a way to get this support into CAPA.
      • Docs
      • <Add docs requirements for this card>
      • Testing
      • <Explain testing that will be added>

            rmanak@redhat.com Radek Manak
            joelspeed Joel Speed
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: