Uploaded image for project: 'Hybrid Cloud Infrastructure Documentation'
  1. Hybrid Cloud Infrastructure Documentation
  2. HCIDOCS-100

Document Changes to ConfigMap Value Retrieval

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Duplicate
    • Icon: Normal Normal
    • OSC 1.7.0
    • None
    • Sandboxed Containers
    • None
    • 5

      Link to recording: https://drive.google.com/open?id=12YZWFm2XcZXcxaOyCa3TDxPqBFIqadIq

      Background info

      Epic Goal
      The user no longer needs to manually retrieve config values when creating a ConfigMap for Azure and AWS.

      Why?
      Currently the user needs to run a lot of extra commands to retrieve values in order to create the ConfigMap that communicates between Azure/AWS and the OSC operator. We want to simplify this process.

      In addition to removing the steps for retrieving each of these values, they will also be removed for the ConfigMap yaml manifests the user needs to create. These config values will be automatically populated behind the scenes.

      AWS
      Remove AMI ID retrieval.

      New YAML:
      apiVersion: v1
      kind: ConfigMap
      metadata:
      name: peer-pods-cm
      namespace: openshift-sandboxed-containers-operator
      data:
      CLOUD_PROVIDER: "aws"
      VXLAN_PORT: "9000"
      PODVM_INSTANCE_TYPE: "t3.small"
      PROXY_TIMEOUT: "5m"

      Azure
      Remove image ID, VNET name, subnet ID, NSG ID.

      New YAML:
      apiVersion: v1
      kind: ConfigMap
      metadata:
      name: peer-pods-cm
      namespace: openshift-sandboxed-containers-operator
      data:
      CLOUD_PROVIDER: "azure"
      VXLAN_PORT: "9000"
      AZURE_INSTANCE_SIZE: "Standard_D8as_v5"
      PROXY_TIMEOUT: "5m"
      DISABLECVM: "true"

      IMPORTANT
      The YAML files listed here do not include the new field added for Instance size/type connected to TELCODOCS-1419. Make sure when working on this to take that into account so we don't end up with conflicts.

      Additional info
      Emanuele is currently working on this. He believes it will be done in time for 1.5. He's working on the Azure side, but says once that's done, it's a simple thing to apply it to AWS as well. Make sure to follow up in the future to verify.

      (Day 1) Install, Configure, Acceptance Test (procedures)

      Creating a peer-pod ConfigMap for AWS using the web console
      Creating a peer-pod ConfigMap for AWS using the CLI

      • Edit info at beginning of section to reflect changes.
      • Remove steps for manual retrieval of parameters.
      • Update new YAML file.

      Creating a peer-pod ConfigMap for Azure using the web console
      Creating a peer-pod ConfigMap for Azure using the CLI

      • Edit info at beginning of section to reflect changes.
      • Remove steps for manual retrieval of parameters.
      • Update new YAML file.

      QE: Need to check. Not sure.

              Unassigned Unassigned
              rhn-support-miweiss Miriam Weiss
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: