diff --git a/book/docs/environment/install-cam.md b/book/docs/environment/install-cam.md index 73410d6..4b0cb33 100644 --- a/book/docs/environment/install-cam.md +++ b/book/docs/environment/install-cam.md @@ -4,7 +4,7 @@ IBM Cloud Automation Manager (CAM) is a cloud management solution in IBM Cloud P Cloud Automation Manager uses open source Terraform to manage and deliver cloud infrastructure as code. Cloud infrastructure that is delivered as code is reusable, is able to be placed under version control, can be shared across distributed teams, and can be used to easily replicate environments. -In relation to ICP4A, CAM is used to deploy IBM Business Automation Workflow (BAW) to traditional WebSphere nodes. +In relation to the Cloud Pak, CAM is used to deploy IBM Business Automation Workflow (BAW) to traditional WebSphere nodes. Eventually, IBM BAW will be deployed as containers which will mean that CAM would not be used in this case. diff --git a/book/docs/environment/install-icp.md b/book/docs/environment/install-icp.md index 6f96d7e..68cc893 100644 --- a/book/docs/environment/install-icp.md +++ b/book/docs/environment/install-icp.md @@ -6,9 +6,9 @@ The components involved in building the Denim Compute environment for [IBM Cloud One of the goal of Denim Compute is to create a highly available environment to run solutions with the IBM Cloud Pak for Automation. This section reviews a set of documents that provide configuration and sizing recommendations towards that goal. -### ICP4A sizing +### Cloud Pak sizing -- [This report](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/hardwareReqsForProduct?deliverableId=77D6C42017D411E9AEAFE0FEBCE2D22F&osPlatforms=Linux&duComponentIds=D002%7CD001%7CS005%7CS008%7CS003%7CS006%7CS004%7CS007) provides hardware requirements (CPU, RAM, disk) for the different ICP4A components, but it is difficult to derive an aggregated requirement for a cluster that will support multiple capabilities. +- [This report](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/hardwareReqsForProduct?deliverableId=77D6C42017D411E9AEAFE0FEBCE2D22F&osPlatforms=Linux&duComponentIds=D002%7CD001%7CS005%7CS008%7CS003%7CS006%7CS004%7CS007) provides hardware requirements (CPU, RAM, disk) for the different Cloud Pak components, but it is difficult to derive an aggregated requirement for a cluster that will support multiple capabilities. ### ICP sizing diff --git a/book/docs/environment/intro.md b/book/docs/environment/intro.md index fe2684b..c62fc94 100644 --- a/book/docs/environment/intro.md +++ b/book/docs/environment/intro.md @@ -10,5 +10,5 @@ In the next sections, we detail how to: - Install the individual DBA components (BAW, ODM, BAI, ...). ## Scripted install and deployment -A collection of Ansible scripts to configure and install platforms, and deploy the ICP4A components are available in the `ibm-cloud-architecture/icp4a-deployment` GitHub repository. +A collection of Ansible scripts to configure and install platforms, and deploy the Cloud Pak components are available in the `ibm-cloud-architecture/icp4a-deployment` GitHub repository. diff --git a/book/docs/environment/sundries.md b/book/docs/environment/sundries.md index 4bdb2e1..4118c88 100644 --- a/book/docs/environment/sundries.md +++ b/book/docs/environment/sundries.md @@ -39,13 +39,13 @@ Even after Workflow containers are available, customers will still want to or ne ## About BAW -### Installing through CAM (ICP4A 19.0.1 and before) +### Installing through CAM (Cloud Pak 19.0.1 and before) The install of BAW involves the use of the IBM Cloud Automation Manager (CAM). While BAW can be installed on manually provisioned VMs, the use of CAM brings the following benefits: - It facilitates the replication of the install process to multiple environments (e.g. DEV, TEST, PROD, etc.) -- It allows to have the same metering in ICP that the Docker containers use and go to the same dashboard. This means that VPC usage can be tracked for all Docker and non-Docker based offerings within ICP4A. +- It allows to have the same metering in ICP that the Docker containers use and go to the same dashboard. This means that VPC usage can be tracked for all Docker and non-Docker based offerings within the Cloud Pak. ### BAW/CPE compatibility (BAW 19.0.02 and before)