Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-3606

[R&D] Allow modifying ServiceNetworks post installation

    XMLWordPrintable

Details

    • Epic
    • Resolution: Unresolved
    • Major
    • None
    • None
    • CNO, SDN Core
    • Allow Expanding ServiceNetworks
    • False
    • False
    • To Do
    • OCPSTRAT-1242 - Allow modifying ServiceNetworks post installation
    • OCPSTRAT-1242Allow modifying ServiceNetworks post installation
    • 0
    • 0% 0%
    • Undefined
    • ---
    • 0
    • 0

    Description

      Goal: Allow the expansion of ServiceNetworks 

      Problem:
      In OpenShift 3.x, we had a procedure for expanding the ClusterCIDR of an existing cluster without disrupting running workloads. We have also seen a lot of customers requesting us to share process on modifying this post installation. Often they need to re-install. We don't have any tested methodologies on what it would take to modify ServiceNetwork CIDR with least cdisruption.

      As an outcome of R&D epic: 

      1. We need documentation on the process that customer should follow to
        1. Expand existing ServiceNetworks
        2. Modify ServiceNetworks. 

      Attachments

        Issue Links

          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SDN-1658 Allow Expanding ClusterNetworks

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users RFE-1315 Allow expanding ClusterNetworks and ServiceNetworks

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Accepted

          Activity

            People

              Unassigned Unassigned
              mcurry@redhat.com Marc Curry
              Votes:
              4 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated: