-
Notifications
You must be signed in to change notification settings - Fork 92
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
Adding info about reinitializing the appliance #852
Conversation
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.
wait for anchal to review too
|
||
2. Delete the three Platform Services Controller configuration files from the appliance. | ||
|
||
<pre>rm /etc/vmware/psc/admiral/psc-config.properties`</pre> |
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.
Trailing ` character at the end on this line and the two below.
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.
Fixed
2. Stop the vSphere Integrated Containers Management Portal service. | ||
|
||
<pre>systemctl stop admiral.service</pre> | ||
2. List all of the containers that are running in the appliance. |
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.
List all of the containers that are running in the appliance.
-> List all of the containers in the appliance.
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.
Fixed
@@ -0,0 +1,16 @@ | |||
# Reinitialize the vSphere Integrated Containers Appliance | |||
|
|||
After you power on the vSphere Integrated Containers appliance for the first time, you are prompted to enter the vCenter Server credentials. This allows performs the OVA installer to perform two tasks to initialize the appliance: |
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.
... you are prompted to enter the vCenter Server credentials and PSC settings.
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.
Fixed
Adding @lgayatri - we should verify the steps documented in this PR for registering with a different PSC on your setup before merging this. |
Thanks @anchal-agrawal. A couple of questions about this info:
Thanks! |
@stuclem @anchal-agrawal . I reviewed the steps for https://github.com/stuclem/vic-product/blob/78713dd98a8246a8d950ee1fc619cc79427bea47/docs/user_doc/vic_vsphere_admin/register_different_psc.md. Guide looks great. Two comments:
By the way, I tested this workflow and it works perfectly. |
Ok @stuclem , please retain the port number as 9443. |
@anchal-agrawal these procedures relate exclusively to 1.2.1, correct? If so, I'll hold off merging this until we push the 1.2.1 update release. |
@stuclem This applies to 1.2.0 as well. However, the steps we have mentioned in Re: tagging - not sure how the tag could disappear unless the user removes it. If the tag is missing, the content trust feature would not work as expected. If tagging fails the first time the appliance is initialized via the Getting Started page, the user will see a red alert with the message |
|
||
The Getting Started Page includes a button labeled **Re-Initialize the vSphere Integrated Containers Appliance**. | ||
|
||
**CAUTION**: Clicking the reinitialize button when the appliance is functioning correctly can result in data loss. You must only reinitialize the appliance in the following circumstances: |
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 is not true - clicking the reinitialize button while the OVA is functioning does not break the OVA. However, during upgrade, it's important that the user not visit the Getting Started page and initialize from there or use the reinitialize button on that page. We mention this note on the OVA console screen and in the upgrade docs.
We should revert this note to its earlier form.
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.
Done in de44433
@@ -0,0 +1,30 @@ | |||
# Register the vSphere Integrated Containers Appliance with a Different Platform Services Controller |
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.
I suggest deferring this addition. As noted in a previous comment in this PR, these steps haven't been fully verified. @lgayatri saw an issue where this procedure worked fine and the OVA was working as expected, but the Admiral UI looked broken after ~15 hours. I haven't gotten a chance to look into that yet.
I think we should:
- remove this file and any references to it in this PR
- re-open Reregister with new PSC #610 since that issue is specifically for doc'ing the process to register with a different PSC
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.
Fixes #681
Fixes #763
@andrewtchin and @anchal-agrawal can you please review? Thanks!