Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-2086

System Identification for LPAR / KVM / zVM / zCX in on IBM Z and LinuxONE

XMLWordPrintable

    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None
    • None

      Feature Overview (aka. Goal Summary)  

      • We would like to work on BareMetal support for confidential containers. For that we would like to differentiate between OCP BareMetal node and VM.

 We would like to know the type of compute node(differentiate between OCP BareMetal node and VM).

  Currently, /etc/sysinfo provide this information. Could you please provide a way to differentiate between BareMetal node and VM by adding “LABEL”(something like Label or some other way) on worker node, so that we can choose the compute node to deploy Confidential container workload based on this label.

      Goals (aka. expected user outcomes)

      • Be able to differentiate between a bare metal node and a VM

      Requirements (aka. Acceptance Criteria):

      • Be able to differentiate between a bare metal node and a VM

       

      Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

      Deployment considerations List applicable specific needs (N/A = not applicable)
      Self-managed, managed, or both Both
      Classic (standalone cluster) Yes
      Hosted control planes Yes
      Multi node, Compact (three node), or Single node (SNO), or all All
      Connected / Restricted Network Both
      Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) IBM Z
      Operator compatibility n/a
      Backport needed (list applicable versions) no
      UI need (e.g. OpenShift Console, dynamic plugin, OCM) no
      Other (please specify) n/a

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

      <your text here>

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

      <your text here>

      Out of Scope

      High-level list of items that are out of scope.  Initial completion during Refinement status.

      <your text here>

      Background

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

      <your text here>

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

      <your text here>

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

      <your text here>

      Interoperability Considerations

      Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

      <your text here>

              rhn-support-dhardie Duncan Hardie
              rhn-support-dhardie Duncan Hardie
              None
              Dominik Werle, Florian Leber, Holger Wolf
              Prashanth Sundararaman Prashanth Sundararaman
              Dominik Werle Dominik Werle
              Florian Leber Florian Leber
              Silke Niemann Silke Niemann
              Kyle Walker Kyle Walker
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: