Bug 1356565

Summary: Support admin CLI cmd to isolate projects
Product: OpenShift Container Platform Reporter: Jaspreet Kaur <jkaur>
Component: RFEAssignee: Ravi Sankar <rpenta>
Status: CLOSED ERRATA QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2.1CC: aos-bugs, jokerman, mmccomas, rpenta, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-27 09:40:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jaspreet Kaur 2016-07-14 11:45:40 UTC 
>3. What is the nature and description of the request?  
Well it's a good thing to be able to join pod/project network together but for some reasons like restructuration, changes, mistakes, ... we want to be able to unjoin two pod/project networks.
For example if we have project p1 and p2 linked we want to be possible to unlink these two projects.
      
>4. Why does the customer need this? (List the business requirements here)  
     - project restructurations 
     - project changes
     - project mistakes

>5. How would the customer like to achieve this? (List the functional requirements here)
- unjoin two projects with a command like: oadm pod-network unjoin p1 p2
Comment 2 Jaspreet Kaur 2016-07-14 11:49:37 UTC 
There is an existing trello card for this : 

https://trello.com/c/RrVYvOJj/30-3-support-admin-cli-cmd-to-isolate-projects-sdn-functionality
Comment 6 Ravi Sankar 2016-08-17 21:55:04 UTC 
Fixed in https://github.com/openshift/origin/pull/10365
Comment 9 errata-xmlrpc 2016-09-27 09:40:15 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1933