Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOC-307] [2024.1] Replace/decommision a node #22207

Open
wants to merge 12 commits into
base: master
Choose a base branch
from

Conversation

aishwarya24
Copy link
Collaborator

@aishwarya24 aishwarya24 commented Apr 30, 2024

@aishwarya24 aishwarya24 added the area/documentation Documentation needed label Apr 30, 2024
@aishwarya24 aishwarya24 self-assigned this Apr 30, 2024
@aishwarya24 aishwarya24 added this to In progress in Documentation via automation Apr 30, 2024
@aishwarya24 aishwarya24 changed the title [DOC-307] Replace/decommision a node [DOC-307] [2024.1]Replace/decommision a node Apr 30, 2024
Copy link

netlify bot commented Apr 30, 2024

Deploy Preview for infallible-bardeen-164bc9 ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 833ab10
🔍 Latest deploy log https://app.netlify.com/sites/infallible-bardeen-164bc9/deploys/664cb54ee5027500085bccda
😎 Deploy Preview https://deploy-preview-22207--infallible-bardeen-164bc9.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@aishwarya24 aishwarya24 changed the title [DOC-307] [2024.1]Replace/decommision a node [DOC-307] [2024.1] Replace/decommision a node May 1, 2024
The on-premises node instances have three states: In use, Free, and Decommissioned and the following illustration describes the workflow of the states.

![Decommissioned node workflow](/images/ee/decommissioned-node.png)
To check the state of an on-premises node, navigate to **Configs > On-Premises Datacenters**, then click its associated on-premises configuration, and click **Instances**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be good to have a picture for this

cc @rajmaddy89

![Recommission Node](/images/ee/recommission-node.png)

Clicking the **Recommission Node** button opens a popup window to confirm the recommission of this node. Confirming the task redirects to the task page and will take a few minutes to complete.

## Eliminate an unresponsive node
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should say now that replace is the recommended flow for elinating an unreachable node.

And that now remove, release, delete, add are not recommended and are put in the advanced actions

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will need pics for this

cc @rajmaddy89

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this case, we can put the start/stop node above remove, release, add, delete, as it will be used more often

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@charleswang234 - If its not recommended, then should those sequence of steps just be removed? For what situations would a user actually choose it ?

At the moment ill comment it out and recommend using replace.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently we have remove, release, delete, add for old users, as they are used to that workflow. Other than that, it should not be used.

Copy link
Contributor

@charleswang234 charleswang234 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add some comments, thanks, think we will also need to make some changes regarding the manual cleanup of a node, which I will take a look at later

aishwarya24 and others added 2 commits May 15, 2024 19:50
Copy link
Contributor

@iSignal iSignal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incorporating feedback from @charleswang234

aishwarya24 and others added 2 commits May 21, 2024 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Documentation needed
Projects
Documentation
In progress
Development

Successfully merging this pull request may close these issues.

None yet

4 participants