Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-1434

[RFE] NMState to revert configuration on the nodes when NNSP is removed

XMLWordPrintable

    • nmstate-2.2.18-1.el9
    • Minor
    • 1
    • sst_network_management
    • ssg_networking
    • 22
    • 5
    • False
    • Hide

      None

      Show
      None
    • Yes
    • NMT - RHEL 8.10/9.4 DTM 08
    • Hide

      User story

      As an OCP administrator, I want the node network configuration to revert to its original state when a NodeNetworkConfigurationPolicy (NNSP) is removed, so that I can ensure consistent networking environments and avoid creating separate NNSPs for reverting changes

      Acceptance criteria

      Given an OCP administrator applying an NNSP to a node with a basic network configuration, 

      When the NNSP has been applied successfully and the OCP administrator removes it

      Then nmstate should automatically generate a reverse network state YAML file to capture the original state of the node.

      Definition of Done

      • The implementation meets the acceptance criteria
      • Unit tests and integration tests if applicable (decided during refinement) are written and passed
      • DocText/DocType is set.
      • The code is part of a downstream build attached to an errata
      Show
      User story As an OCP administrator, I want the node network configuration to revert to its original state when a NodeNetworkConfigurationPolicy (NNSP) is removed, so that I can ensure consistent networking environments and avoid creating separate NNSPs for reverting changes Acceptance criteria Given an OCP administrator applying an NNSP to a node with a basic network configuration,  When the NNSP has been applied successfully and the OCP administrator removes it Then nmstate should automatically generate a reverse network state YAML file to capture the original state of the node. Definition of Done The implementation meets the acceptance criteria Unit tests and integration tests if applicable (decided during refinement) are written and passed DocText/DocType is set. The code is part of a downstream build attached to an errata
    • Pass
    • Enhancement
    • Hide
      .Nmstate can now create a YAML file to revert settings

      With this enhancement, Nmstate can create a "revert configuration file" that contains the differences between the current network settings and a YAML file with the new configuration that you want to apply. If the settings do not work as expected after you applied the YAML file, you can use the revert configuration file to restore the previous settings:

      . Create a YAML file, for example, `new.yml` with the configuration that you want to apply.

      . Create a revert configuration file that contains the differences between intended settings in `new.yml` and the current state:
      +
      ----
      # nmstatectl gr new.yml > revert.yml
      ----

      . Apply the configuration from `new.yml`.

      . If you want now to switch back to the previous state, apply `revert.yml`.

      Alternatively, you can use the `NetworkState::generate_revert(current)` call if you use the Nmstate API to create a revert configuration.
      Show
      .Nmstate can now create a YAML file to revert settings With this enhancement, Nmstate can create a "revert configuration file" that contains the differences between the current network settings and a YAML file with the new configuration that you want to apply. If the settings do not work as expected after you applied the YAML file, you can use the revert configuration file to restore the previous settings: . Create a YAML file, for example, `new.yml` with the configuration that you want to apply. . Create a revert configuration file that contains the differences between intended settings in `new.yml` and the current state: + ---- # nmstatectl gr new.yml > revert.yml ---- . Apply the configuration from `new.yml`. . If you want now to switch back to the previous state, apply `revert.yml`. Alternatively, you can use the `NetworkState::generate_revert(current)` call if you use the Nmstate API to create a revert configuration.
    • Done
    • None

      Description of problem:

      Clone of https://issues.redhat.com/browse/RFE-4210

      New OCP node is installed with basic network configuration (network interface has an IP assigned for installation purposes)
      NodeNetworkConfigurationPolicy (NNSP) is applied to configure netwok on the node.
      NNSP is removed by the administrator.
      Request:

      The configuration of the node should be reverted to the state before NNSP has been applied when an NNSP is removed.

      Without preparing for the situation and having an NNSP with the original state it is currently impossible to revert to the original state.
      According to the customer this is not 'Kubernetes like' behavior.

      Version-Release number of selected component (if applicable):

      How reproducible: Always

      Steps to Reproduce:
      1.
      2.
      3.

      Actual results:

      Expected results:

      Additional info:

      Acceptance Criteria:
      User story

      As an OCP administrator, I want the node network configuration to revert to its original state when a NodeNetworkConfigurationPolicy (NNSP) is removed, so that I can ensure consistent networking environments and avoid creating separate NNSPs for reverting changes

      Acceptance criteria

      Given an OCP administrator applying an NNSP to a node with a basic network configuration, 

      When the NNSP has been applied successfully and the OCP administrator removes it

      Then nmstate should automatically generate a reverse network state YAML file to capture the original state of the node.

      Definition of Done

      • The implementation meets the acceptance criteria
      • Unit tests and integration tests if applicable (decided during refinement) are written and passed
      • Release Note text is set.
      • The code is part of a downstream build attached to an errata

            fge@redhat.com Gris Ge
            ellorent Felix Enrique Llorente Pastora
            Network Management Team Network Management Team
            Mingyu Shi Mingyu Shi
            Marc Muehlfeld Marc Muehlfeld
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: