search

ibm-cloud-architecture / terraform-icp-aws

This Terraform configurations uses the AWS provider to provision virtual machines on AWS to prepare VMs and deploy IBM Cloud Private on them. This Terraform template automates best practices learned from installing ICP on AWS at numerous client sites in production.
9 stars 30 forks source link

Tried to use the module for ICP Community Edition and got errors in ansible playbook. #5

Closed yudaykiran closed 6 years ago

yudaykiran commented 6 years ago

The ansible playbook exited with the following error:

TASK [check : Validating Hostname is resolvable] *******************************
[0;31mfatal: [10.10.10.30]: FAILED! => {"changed": false, "msg": "Please configure your hostname to resolve to an externally reachable IP"}[0m
[0;31mfatal: [10.10.10.223]: FAILED! => {"changed": false, "msg": "Please configure your hostname to resolve to an externally reachable IP"}[0m
[0;31mfatal: [10.10.11.155]: FAILED! => {"changed": false, "msg": "Please configure your hostname to resolve to an externally reachable IP"}[0m
[0;31mfatal: [10.10.12.252]: FAILED! => {"changed": false, "msg": "Please configure your hostname to resolve to an externally reachable IP"}[0m
[0;31mfatal: [10.10.10.185]: FAILED! => {"changed": false, "msg": "Please configure your hostname to resolve to an externally reachable IP"}[0m

I am new to IBM Cloud Private, just trying out any automated solution I could, to get it to deploy.

  1. Just wanted to know if this terraform module can be used for ICP CE as well?
  2. SSHed into the nodes created, but did not see the /etc/hosts updated with the hostnames of the master and worker nodes, is this an expected behaviour?
  3. Is there some step that I have missed and is not available in the ReadME?
osowski commented 6 years ago

This supports ICP CE installation as well. I've validated this against deploying ICP 3.1 Community Edition. You will need to ensure that master and proxy node counts are set to 1, va should be set to 0, and management can be optional at 0 or 1. If you set management to 0, you will want to increase the amount of resources allocated to your master node.

There is no need for the /etc/hosts file to be manually updated by our automation, as all the created instances are registered in Route53 and are directly addressable by name.

I will create a section in the main readme to document the Community Edition installation requirements.