Troubleshooting cloud connections
To troubleshoot a cloud connection, make sure that the information for the cloud is correct and that the components of the blueprint design server can access the cloud.
- Check the logs
- The default location for the blueprint design server logs is /opt/ibm-ucd-patterns/logs. The default location for the engine logs is /var/log/heat/.
- Confirm software components
- Ensure that you have installed all the necessary components. Regardless of which type of cloud you are connecting to, the connection requires an OpenStack Keystone server, an engine, and a blueprint design server. See Connecting to clouds through the blueprint designer.
- Confirm connection information
- The connection information for the cloud must match the information on other systems. For example, the URL of the OpenStack identity service (Keystone) must be exactly the same (including any trailing slashes) in the authentication realm and on the allowed_auth_uris parameter of the engine configuration file.
- Provide proxy connection information
- If you provision to Amazon Web Services and use a proxy server, you must provide the proxy
server URL and port. Both the system that hosts the engine and the system that hosts the cloud
discovery service require this proxy.
- For a Linux™ operating system, create a file that is named .boto in the /home/user_name directory.
- For a Windows™ operating system, create a file that is
named boto.config in the
C:\Users\user_name directory. Then, set a user environment
variable that is named BOTO_CONFIG to the full path of the file,
C:\Users\user_name\boto.config.
See Boto Config.[Boto] proxy=proxy_host_name proxy_port=proxy_port_number
After you modify the boto.config file, you must restart the cloud discovery service. To restart the cloud discovery service, see Stopping the blueprint designer, cloud discovery service, and engine and Stopping the blueprint designer, cloud discovery service, and engine.
- Confirm the blueprint design server system time
- If you provision to Amazon Web Services and see a
Connection Failed
error in the blueprint designer, confirm that the system time of the blueprint design server is correct.
For more troubleshooting information, see the UrbanCode community on IBM® developerWorks®: https://developer.ibm.com/answers/?community=urbancode.