Skip to content

Commit ded7f6a

Browse files
SirSpideySirSpidey
authored
docs: update catalog diagram descriptions (#385)
Update the diagram descriptions that are displayed with the variation network diagram in the Cloud catalog. These descriptions are reduced. Details about the variation should be defined and maintained in the reference architecture.
1 parent 2170621 commit ded7f6a

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

‎ibm_catalog.json‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -170,11 +170,11 @@
170170
"diagrams": [
171171
{
172172
"diagram": {
173-
"caption": "Secure Landing Zone with VSIs",
173+
"caption": "VSI on VPC landing zone - QuickStart variation",
174174
"url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/main/reference-architectures/vsi-quickstart.drawio.svg",
175175
"type": "image/svg+xml"
176176
},
177-
"description": "The **QuickStart** flavor of Secure Landing Zone with VSIs requires at least 2 CPUs and 4 GB of memory.\n\nSecure Landing Zone with virtual server instances is implemented with virtual servers. It utilizes two separate Virtual Private Clouds (VPC), a Management VPC and a Workload VPC, to manage the environment and the deployed workload. Each VPC is a multi-zoned, multi-subnet implementation that keeps your workloads secure.\n\nVirtual Private Endpoints connect the VPCs to each other and to IBM Cloud services, including Key Protect, IAM, Container Registry, Object Storage, and any additional services. IBM Cloud services are configured for storage and key management.\n\nIBM Cloud Flow Logs for VPC enable the collection, storage, and presentation of information about the Internet Protocol (IP) traffic that is going to and from network interfaces within your VPC. In addition, Activity Tracker logs events from enabled services. IBM Cloud Flow Logs for VPC and Activity Tracker are included in this configuration. Additional security services can be added such as Hyper Connect Crypto Service."
177+
"description": "The QuickStart variation of the VSI on VPC landing zone deployable architecture creates a fully customizable Virtual Private Cloud (VPC) environment in a single region. The solution provides virtual servers in a secure VPC for your workloads. The QuickStart variation is designed to deploy quickly for demonstration and development."
178178
}
179179
]
180180
}
@@ -736,11 +736,11 @@
736736
"diagrams": [
737737
{
738738
"diagram": {
739-
"caption": "Secure Landing Zone with VSIs",
739+
"caption": "VSI on VPC landing zone - Standard variation",
740740
"url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/main/reference-architectures/vsi-vsi.drawio.svg",
741741
"type": "image/svg+xml"
742742
},
743-
"description": "Secure Landing Zone with virtual server instances is implemented with virtual servers running in a single, defined Virtual Private Cloud (VPC) which is used to manage the environment. The VPC is a multi-zoned, multi-subnet implementation that keeps your VPC secure and highly available. Virtual Private Endpoints connect the VPCs to each other and to IBM Cloud services, including Key Protect, IAM, Container Registry, Object Storage, and any additional services. IBM Cloud services are configured for storage and key management. \n\nIBM Cloud Flow Logs for VPC enable the collection, storage, and presentation of information about the Internet Protocol (IP) traffic that is going to and from network interfaces within your VPC. In addition, Activity Tracker logs events from enabled services. IBM Cloud Flow Logs for VPC and Activity Tracker are included in this configuration. Additional security services can be added such as Hyper Connect Crypto Service."
743+
"description": "The Standard variation of the VSI on VPC landing zone deployable architecture is based on the IBM Cloud for Financial Services reference architecture. The architecture creates a customizable and secure infrastructure, with virtual servers, to run your workloads with a Virtual Private Cloud (VPC) in multizone regions."
744744
}
745745
]
746746
}
@@ -1083,11 +1083,11 @@
10831083
"diagrams": [
10841084
{
10851085
"diagram": {
1086-
"caption": "Secure infrastructure on VPC for regulated industries",
1086+
"caption": "VPC landing zone - Standard variation",
10871087
"url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/main/reference-architectures/vpc.drawio.svg",
10881088
"type": "image/svg+xml"
10891089
},
1090-
"description": "Secure Landing Zone utilizes two separate Virtual Private Clouds (VPC), a Management VPC and a Workload VPC, to manage the environment and the deployed workload. Each VPC is a multi-zoned, multi-subnet implementation that keeps your workloads secure.\n\nVirtual Private Endpoints connect the VPCs to each other and to IBM Cloud services, including Key Protect, IAM, Container Registry, Object Storage, and any additional services. IBM Cloud services are configured for storage and key management.\n\nIBM Cloud Flow Logs for VPC enable the collection, storage, and presentation of information about the Internet Protocol (IP) traffic that is going to and from network interfaces within your VPC. In addition, Activity Tracker logs events from enabled services. IBM Cloud Flow Logs for VPC and Activity Tracker are included in this configuration. Additional security services can be added such as Hyper Connect Crypto Service."
1090+
"description": "The Standard variation of the VPC landing zone deployable architecture deploys a simple Virtual Private Cloud (VPC) infrastructure without any compute resources. You can use this architecture as a base on which to deploy compute resources. The Standard variation uses two Virtual Private Clouds (VPC) - a Management VPC and a Workload VPC - to manage the environment and the deployed workload. Each VPC is a multi-zoned, multi-subnet implementation that keeps your workloads secure. A transit gateway connects the VPCs to each other and Virtual Private Endpoints are used connect to IBM Cloud services."
10911091
}
10921092
]
10931093
}
@@ -1730,11 +1730,11 @@
17301730
"diagrams": [
17311731
{
17321732
"diagram": {
1733-
"caption": "OpenShift Container Platform on VPC for regulated industries",
1733+
"caption": "Red Hat OpenShift Container Platform on VPC landing zone - Standard variation",
17341734
"url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-landing-zone/main/reference-architectures/roks.drawio.svg",
17351735
"type": "image/svg+xml"
17361736
},
1737-
"description": "OpenShift Container Platform on VPC for regulated industries is implemented with a Red Hat Openshift cluster running in a single, defined Virtual Private Cloud (VPC) which is used to manage the environment. The VPC is a multi-zoned, multi-subnet implementation that keeps your VPC secure and highly available. Virtual Private Endpoints connect the VPCs to each other and to IBM Cloud services, including Key Protect, IAM, Container Registry, Object Storage, and any additional services. IBM Cloud services are configured for storage and key management. \n\nIBM Cloud Flow Logs for VPC enable the collection, storage, and presentation of information about the Internet Protocol (IP) traffic that is going to and from network interfaces within your VPC. In addition, Activity Tracker logs events from enabled services. IBM Cloud Flow Logs for VPC and Activity Tracker are included in this configuration. Additional security services can be added such as Hyper Connect Crypto Service."
1737+
"description": "The Standard variation of the Red Hat OpenShift Container Platform on VPC landing zone is based on the IBM Cloud for Financial Services reference architecture. The architecture creates secure and compliant Red Hat OpenShift Container Platform workload clusters on a Virtual Private Cloud (VPC) network."
17381738
}
17391739
]
17401740
}

0 commit comments

Comments
 (0)