How long will the installation process take? HA/NON-HA/Standalone?
If you follow the documentation process from end-to-end by:
- Understanding the
- Understanding the High Availability Best Practices
- Preparing your infrastructure as listed in Phase 1: Prepare Infrastructure
- Configuring your network rules as listed in Phase 2: Configure Firewall Rules
- Ensuring that the validator check passes as listed in Phase 3: Run the Prerequisite Checker
- Performing the installation as listed in Phase 4: Install/Configure Components
- Configuring the CloudCenter platform as listed in Configure CloudCenter
...then, the following timing approximations apply to install VMs for Basic Deployments as identified in Virtual Appliance Overview:
- HA installation: Approximately 3 days
- Non-HA installation: Approximately 1 day
Which parameters are required, in the configuration wizard?
The required parameters differs based on the Component, the Role, and the Mode. The wizard for each component, identifies the required fields with an asterisk ( * ) as applicable.
Do I need to encrypt passwords?
No. CloudCenter encrypts passwords where required and you do not need to do anything additional to encrypt passwords.
How do I use my own image in the CloudCenter architecture?
See the following pages as applicable:
- Windows: Custom Windows Image (contact the the CloudCenter Support team to obtain instructions for the installer files.
- Linux: Custom Linux Image (a virtual appliance file is available for Linux images).
Do I need to install the Management Agent on each image?
Each VM that is managed by CloudCenter requires a Management Agent Bundle (agent) component to run on it. The CloudCenter platform installer files includes the management agent in each VM image. The CloudCenter platform detects that the agent is not installed and automatically pushes the agent to each VM as part of the deployment process.
How do I know if the CloudCenter platform installation is done?
This milestone differs for each component:
- CCM: Once you install the CCM, you should be able to access the CCM UI and Configure the Admin Account.
- CCO: Once you install the CCO component, you should be able to Register the CCO with the CCM.
- AMQP: Once you install the AMQP component for the first time, you may need to wait for a few minutes to ensure that all users are listed. You can verify that all users are listed by the
rabbitmqctl list_userscommand as listed in
What can I do if my PostgreSQL instance stops communicating with the CCM?
If you encounter this scenario when using the HA mode, follow these steps to correct this problem:
Start Postgres service.
Ensure that the .lock file is not present in the required directory.
Stop and start the cluster.
Check the status of the cluster to ensure that it running.
If you are still facing this issue, then restart the dbmaster and PGMasterVIP.
What can I do if my PostgreSQL cluster won't start after applying a RHEL 7 patch?
If you have patched both the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE servers on RHEL 7 and rebooted both the servers, you may encounter a situation when the cluster does not start even after rebooting both servers. This is because the cluster is not in sync and cannot be automatically started after the reboot.
See PostgreSQL Troubleshooting for additional context.
- No labels