Bug 1462102

Summary: [RFE] Add support for --node-selector='zone in (zone1,zone2)' to oadm new-project
Product: OpenShift Container Platform Reporter: Brendan Mchugh <bmchugh>
Component: RFEAssignee: Paul Weil <pweil>
Status: CLOSED NOTABUG QA Contact: Xiaoli Tian <xtian>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: aos-bugs, bmchugh, dzhukous, jokerman, mbarrett, mmccomas, wmeng
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: 2018-02-12 13:06:06 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 Brendan Mchugh 2017-06-16 07:56:13 UTC
1. Proposed title of this feature request
Add support for --node-selector='zone in (zone1,zone2)' to oadm new-project

3. What is the nature and description of the request?  
We would like to be able to select nodes in the same form as in "oc get nodes -l 'zone in '(zone1, zone2)'"

For example with the following nodes:
# oc get nodes --show-labels 
NAME           STATUS                     AGE       LABELS
node200.lab   Ready,SchedulingDisabled   84d       beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=node200.lab,logging-infra-fluentd=false,zone=zone1
node201.lab   Ready                      84d       beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=node201.lab,logging-infra-fluentd=true,region=infra,zone=default
node202.lab   Ready                      84d       beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=node202.lab,logging-infra-fluentd=true,region=primary,zone=zone2


# oc get nodes -l 'zone in (zone1,zone2)'
NAME           STATUS                     AGE
node200.lab   Ready,SchedulingDisabled   84d
node202.lab   Ready                      84d

4. Why does the customer need this? (List the business requirements here)  
We are running our OpenShift nodes in multiple zones. We need to allow developers to run their pods in multiple zones, but not all zones.

5. How would the customer like to achieve this? (List the functional requirements here)  
Allow oadm new-project to accept the following type of argument:

oadm new-project --node-selector='zone in (zone1,zone2)'

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
BZ# URL
Trello URL

10. List any affected packages or components.
atomic-openshift

Comment 4 Brendan Mchugh 2018-03-19 11:59:40 UTC
Clearing needinfo - case was closed.