-
Notifications
You must be signed in to change notification settings - Fork 13
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
removing initializer installation procedures per 2023-0914-770393. #608
base: master
Are you sure you want to change the base?
Conversation
docs/initializer_cli_reference.md
Outdated
@@ -5,7 +5,7 @@ sidebar_label: Initializer Command Line Reference | |||
|
|||
This is a reference document for the SSR Initializer command line interface. | |||
For a guide to basic usage, see the initialization section of the | |||
[Manual Installation Guide](intro_installation_installer.md#initialize-the-128t-node). | |||
[Router Interacrive Installation](intro_installation_bootable_media.mdx#initialize-the-ssr-node. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link will likely not work. I do not see a corresponding change that shows the heading change to match the new URI.
docs/initializer_cli_reference.md
Outdated
[Installation Guide](intro_installation_installer.md#initialize-the-128t-node). | ||
instructions for the Initializer can be found in the | ||
the initialization section of the | ||
[Router Interacrive Installation](intro_installation_bootable_media.mdx#initialize-the-ssr-node. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link will likely not work. I do not see a corresponding change that shows the heading change to match the new URI.
[Installation Guide](intro_installation_installer.md#install-using-128t-installer). | ||
Step-by-step instructions for the Installer can be found starting in the | ||
the initialization section of the | ||
[Router Interacrive Installation](intro_installation_bootable_media.mdx#initialize-the-ssr-node. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link will likely not work. I do not see a corresponding change that shows the heading change to match the new URI.
@@ -32,7 +32,7 @@ Click on the link of the public cloud provider where you want to perform the Ses | |||
|
|||
## Deploying the Primary Node Conductor – Node A | |||
|
|||
If the SSR software is not already installed on the Node A VM, launch the SSR installer using the command `install128t` and follow the [Installation Procedure](intro_installation_installer.md). After the installation is complete, the system will restart and the initializer will launch automatically. | |||
If the SSR software is not already installed on the Node A VM, launch the SSR installer using the command `install128t` and follow the installation procedure. After the installation is complete, the system will restart and the initializer will launch automatically. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should never be the case as you have created a guide for installing the conductor from an ISO, which forces stepping through the installation process of the SSR software.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ian-h-chamberlain is this guide still relevant with our packaged ISO install for the conductor?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From a docs perspective, it looks like he Cloud HA install doc needs to be completely revised. The process seems very outdated. I'll connect with Ian and the SE's to see who might have an updated procedure to follow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, frankly I'm not sure what the procedure looks like for installing in cloud environments, since they have always been a little bit different than our typical hardware deployment workflow. For non-cloud deployments I think the standard ISO workflow is still recommended best practice.
@@ -80,7 +80,7 @@ Node A is now ready to allow access to Node B in order to form the HA pair. The | |||
|
|||
## Deploying the Secondary Node Conductor – Node B | |||
|
|||
Log in to the Node B VM. If the SSR software is not already installed, launch the SSR installer using the command `install128t` and follow the [Installation Procedure](intro_installation_installer.md). After the installation is complete, the system will restart and the initializer will launch automatically. | |||
Log in to the Node B VM. If the SSR software is not already installed, launch the SSR installer using the command `install128t` and follow the installation procedure. After the installation is complete, the system will restart and the initializer will launch automatically. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should never be the case as you have created a guide for installing the conductor from an ISO, which forces stepping through the installation process of the SSR software.
No description provided.