Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1362483 - To be able to disable the "auto unregister" of node [NEEDINFO]
Summary: To be able to disable the "auto unregister" of node
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.1.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: Derek Carr
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-02 10:52 UTC by Miheer Salunke
Modified: 2018-03-12 13:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-12 13:54:36 UTC
erich: needinfo? (misalunk)


Attachments (Terms of Use)

Description Miheer Salunke 2016-08-02 10:52:18 UTC
1. Proposed title of this feature request  
 
To be able to disable the "auto unregister" of node 


3. What is the nature and description of the request?  

For a cost reason a customer would like to shut down some openshift platform during the night and start up the morning.
We configured the aws provider in order to use EBS volume.
This issue is when we stop a node instance, it automatically disappear in openshift, and when it come back, it registered without labels


So, part of the cloud provider integration is that it removes nodes that are no longer present.
You would have to provide some type of orchestration with starting the node back up and re-labeling it.
Orchestration  would depend on what they currently use, how manual/automated they wanted the process, etc.
You could have a scheduled jenkins job that would shut down x% of nodes each night filtering based on the tags they provide
and a scheduled job in the morning that would bring up all of the stopped nodes in AWS and re-label them appropriately based on AWS tags on the hosts.
Re-running ansible again would re-label the hosts as well.

So, we should be able to find a way to automate the job, but do you know if something is planned in the next release to make the "remove" optional ?

We already tested the labeling by node with kubernetes and it is a good thing to automate this kind of situation.  But in our case we just want to use openshift like on baremetal server.
Our instances are just stopped (without ip or hostname changes), so we would like to simply start our servers without tricks to register the nodes each time.

We just want to enable the aws provider in order to use EBS volume, we don't want the  "auto unregister" feature.
Is it planned to be able to disable the "auto unregister" of node ?


It's not currently possible but it's an easy code change I think. It's in the Kube code so we'd need to discuss upstream. Probably adding a flag to enable or disable this would be the way to go. 




7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
No
    
10. List any affected packages or components.
Kube, openshift-ansible

Comment 5 Eric Rich 2018-03-12 13:54:36 UTC
This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.


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