Overall Satisfaction with IBM Cloud Virtual Private Cloud (VPC)
IBM Cloud Virtual Private Cloud (VPC) is used as a development environment. We are working on learning IBM Cloud and IBM Cloud Pak for Automation. The environment is intended to be used for customer demos with our products.
- Creating Virtual Private Cloud and virtual server instances was quick and easy, saving us time.
- Documentation for setting up networking was easy to follow.
- IBM Cloud Command Line Interface allowed us to script repetitive tasks.
- The documentation and integration between OpenShift and IBMCloud was not clear. It took some time to figure out which interface to use to setup certain items.
- Better communication between departments could be improved. Had a billing question and had two departments saying it was the other team's issue. Took three days of back and forth to resolve.
- The documentation for loading containers into IBM Cloud OpenShift container registry was not clear. The correct commands were not documented.
- Future readiness--we have the ability to quickly respond and build custom demos for customers in a short timeframe.
- Savings on hardware--we have the ability to spin up large workloads to demonstrate to customers the performance of our tools and IBM Cloud.
- IBM Cloud Virtual Servers
- IBM Cloud Container Registry
- IBM Cloud Object Storage
- IBM Cloud Managed Knative
Being able to leverage the other IBM Cloud offerings with VPC allowed us flexibility in building a robust migration application. In addition it is enabling us more options for add-on solutions for IBM Cloud Pak for Automation.
IBM's documentation and support for IBM Cloud for IBM Cloud Pak for Automation was stronger than with Google Cloud.