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

Adding info about reinitializing the appliance #852

Merged
merged 8 commits into from
Sep 29, 2017

Conversation

stuclem
Copy link
Contributor

@stuclem stuclem commented Sep 21, 2017

Fixes #681

Fixes #763

@andrewtchin and @anchal-agrawal can you please review? Thanks!

Copy link
Contributor

@andrewtchin andrewtchin left a 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>
Copy link
Contributor

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.

Copy link
Contributor Author

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.
Copy link
Contributor

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.

Copy link
Contributor Author

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:
Copy link
Contributor

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

@anchal-agrawal
Copy link
Contributor

Adding @lgayatri - we should verify the steps documented in this PR for registering with a different PSC on your setup before merging this.

@stuclem
Copy link
Contributor Author

stuclem commented Sep 22, 2017

Thanks @anchal-agrawal. A couple of questions about this info:

  • Are these procedures only applicable to 1.2.1? If so, I will merge this just before I push the 1.2.1 update (I have other updates for 1.2.0 that I want to push today, before we release 1.2.1)
  • In the case of re-tagging the appliance, I just say that you might need to do it if someone accidentally deletes the tag.
    • Are there other cases in which the tag might disappear?
    • What exact errors do users see if the tag is missing?

Thanks!

@lgayatri
Copy link

@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:

  1. In Step 5, remove ` at the end of file name
  2. In Step 6, the URL would be https://vic_appliance_address:9443 instead of http://vic_appliance_address.

By the way, I tested this workflow and it works perfectly.

@stuclem
Copy link
Contributor Author

stuclem commented Sep 22, 2017

Thanks @lgayatri - I have removed the trailing ` from step 5 in 81dd1d0. For the address, http://vic_appliance_address redirects to https://vic_appliance_address:9443, so we opted to use the simpler address throughout the docs.

Glad to hear that the procedure works perfectly!

@lgayatri
Copy link

Ok @stuclem , please retain the port number as 9443.

@stuclem
Copy link
Contributor Author

stuclem commented Sep 25, 2017

@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.

@anchal-agrawal
Copy link
Contributor

anchal-agrawal commented Sep 25, 2017

@stuclem This applies to 1.2.0 as well. However, the steps we have mentioned in register_different_psc.md (originally doc'd in #681 (comment)) are not fully fleshed out and tested yet. Please hold off on merging that section.

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 Failed to locate VIC Appliance. Please check the vCenter Server provided and try again.


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:
Copy link
Contributor

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.

Copy link
Contributor Author

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
Copy link
Contributor

@anchal-agrawal anchal-agrawal Sep 27, 2017

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

Copy link
Contributor Author

@stuclem stuclem Sep 28, 2017

Choose a reason for hiding this comment

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

Removed in 6163c49 and fcb32b7. Reopened #644 to reinsert this text once the procedure is fixed and validated.

@stuclem stuclem merged commit 58f6e96 into vmware:master Sep 29, 2017
@stuclem stuclem deleted the initialize branch September 29, 2017 09:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants