Bug 1462102 - [RFE] Add support for --node-selector='zone in (zone1,zone2)' to oadm new-project
[RFE] Add support for --node-selector='zone in (zone1,zone2)' to oadm new-pro...
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE (Show other bugs)
3.4.0
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Paul Weil
Xiaoli Tian
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-16 03:56 EDT by Brendan Mchugh
Modified: 2017-06-17 23:04 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brendan Mchugh 2017-06-16 03:56:13 EDT
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

Note You need to log in before you can comment on or make changes to this bug.