CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Install FAQs

How long will the installation process take? HA/NON-HA/Standalone?

If you follow the documentation process from end-to-end by:

  1. Understanding the Virtual Appliance Overview and selecting the required modes and roles for each component to be installed
  2. Understanding the High Availability Best Practices
  3. Preparing your infrastructure as listed in Phase 1: Prepare Infrastructure
  4. Configuring your network rules as listed in Phase 2: Configure Firewall Rules
  5. Ensuring that the validator check passes as listed in Phase 3: Run the Prerequisite Checker
  6. Performing the installation as listed in Phase 4: Install/Configure Components
  7. 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:

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:

Once you successfully model and deploy a New Application to a cloud of your choice, then the entire CloudCenter platform installation is considered a success!

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:

  1. Start Postgres service.

    systemctl start postgresql-9.5
  2. Ensure that the .lock file is not present in the required directory.

    cd /var/lib/pgsql/tmp/
    # IF the PGSQL.lock is present, remove it using command 
    rm -rf *.lock
  3. Stop and start the cluster.

    pcs cluster stop
    pcs cluster start
  4. Check the status of the cluster to ensure that it running. See PostgreSQL Troubleshooting for additional context.

    pcs status
  5. If you are still facing this issue, then restart the dbmaster and PGMasterVIP.

    pcs resource restart dbmaster
    pcs resource restart 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
Terms & Conditions Privacy Statement Cookies Trademarks