You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"description": "The Power Virtual Server with VPC landing zone as variation 'Create a new architecture' deploys VPC services and a Power Virtual Server workspace and interconnects them.\n\nRequired and optional management components are configured."
@@ -792,6 +801,10 @@
792
801
"key": "enable_monitoring",
793
802
"required": true
794
803
},
804
+
{
805
+
"key": "enable_scc_wp",
806
+
"required": true
807
+
},
795
808
{
796
809
"key": "vpc_intel_images",
797
810
"hidden": true
@@ -884,6 +897,11 @@
884
897
"type": "json_editor"
885
898
}
886
899
},
900
+
{
901
+
"key": "ansible_vault_password",
902
+
"type": "multiline_secure_value",
903
+
"display_name": "Multiline secure value"
904
+
},
887
905
{
888
906
"key": "configure_dns_forwarder"
889
907
},
@@ -1174,7 +1192,7 @@
1174
1192
{
1175
1193
"diagram": {
1176
1194
"caption": "Power Virtual Server with VPC landing zone 'Quickstart' variation",
"description": "The Power Virtual Server with VPC landing zone as 'Quickstart' variation of 'Create a new architecture' option deploys VPC services and a Power Virtual Server workspace and interconnects them. It also creates one Power virtual server instance of chosen t-shirt size or custom configuration.\n\nRequired and optional management components are configured."
@@ -1500,7 +1518,7 @@
1500
1518
{
1501
1519
"diagram": {
1502
1520
"caption": "Power Virtual Server with VPC landing zone 'Import' variation",
"description": "This solution helps to install the deployable architecture 'Power Virtual Server for SAP HANA' on top of a pre-existing Power Virtual Server(PowerVS) landscape. 'Power Virtual Server for SAP HANA' automation requires a schematics workspace id for installation. The 'Import' solution creates a schematics workspace by taking pre-existing VPC and PowerVS infrastructure resource details as inputs. The ID of this schematics workspace will be the pre-requisite workspace id required by 'Power Virtual Server for SAP HANA' to create and configure the PowerVS instances for SAP on top of the existing infrastructure.\n\nRequired and optional management components are configured."
@@ -1818,7 +1836,7 @@
1818
1836
{
1819
1837
"diagram": {
1820
1838
"caption": "Power Virtual Server with VPC landing zone 'Standard Extend' variation",
"description": "The Power Virtual Server with VPC landing zone as variation 'Extend Power Virtual Server with VPC landing zone' creates an additional Power Virtual Server workspace and connects it with already created Power Virtual Server with VPC landing zone. It builds on existing Power Virtual Server with VPC landing zone deployed as a variation 'Create a new architecture'."
| <aname="input_ansible_vault_password"></a> [ansible\_vault\_password](#input\_ansible\_vault\_password)| Vault password to encrypt ansible playbooks that contain sensitive information. Required when SCC workload Protection is enabled. Password requirements: 15-100 characters and at least one uppercase letter, one lowercase letter, one number, and one special character. Allowed characters: A-Z, a-z, 0-9, !#$%&()*+-.:;<=>?@[]\_{\|}~. |`string`|`null`| no |
132
135
| <aname="input_certificate_template_name"></a> [certificate\_template\_name](#input\_certificate\_template\_name)| The name of the Certificate Template to create for a private\_cert secret engine. When `var.existing_sm_instance_guid` is not null, then it has to be the existing template name that exists in the private cert engine. |`string`|`"my-template"`| no |
133
136
| <aname="input_client_to_site_vpn"></a> [client\_to\_site\_vpn](#input\_client\_to\_site\_vpn)| VPN configuration - the client ip pool and list of users email ids to access the environment. If enabled, then a Secret Manager instance is also provisioned with certificates generated. See optional parameters to reuse existing certificate from secrets manager instance. | <pre>object({<br/> enable = bool<br/> client_ip_pool = string<br/> vpn_client_access_group_users = list(string)<br/> })</pre> | <pre>{<br/> "client_ip_pool": "192.168.0.0/16",<br/> "enable": true,<br/> "vpn_client_access_group_users": []<br/>}</pre> | no |
134
137
| <aname="input_configure_dns_forwarder"></a> [configure\_dns\_forwarder](#input\_configure\_dns\_forwarder)| Specify if DNS forwarder will be configured. This will allow you to use central DNS servers (e.g. IBM Cloud DNS servers) sitting outside of the created IBM PowerVS infrastructure. If yes, ensure 'dns\_forwarder\_config' optional variable is set properly. DNS forwarder will be installed on the network-services vsi. |`bool`|`false`| no |
135
138
| <aname="input_configure_nfs_server"></a> [configure\_nfs\_server](#input\_configure\_nfs\_server)| Specify if NFS server will be configured. This will allow you easily to share files between PowerVS instances (e.g., SAP installation files). [File storage share and mount target](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create&interface=ui) in VPC will be created.. If yes, ensure 'nfs\_server\_config' optional variable is set properly below. Default value is '200GB' which will be mounted on specified directory in network-service vsi. |`bool`|`false`| no |
136
139
| <aname="input_configure_ntp_forwarder"></a> [configure\_ntp\_forwarder](#input\_configure\_ntp\_forwarder)| Specify if NTP forwarder will be configured. This will allow you to synchronize time between IBM PowerVS instances. NTP forwarder will be installed on the network-services vsi. |`bool`|`false`| no |
137
140
| <aname="input_dns_forwarder_config"></a> [dns\_forwarder\_config](#input\_dns\_forwarder\_config)| Configuration for the DNS forwarder to a DNS service that is not reachable directly from PowerVS. | <pre>object({<br/> dns_servers = string<br/> })</pre> | <pre>{<br/> "dns_servers": "161.26.0.7; 161.26.0.8; 9.9.9.9;"<br/>}</pre> | no |
138
141
| <aname="input_enable_monitoring"></a> [enable\_monitoring](#input\_enable\_monitoring)| Specify whether Monitoring will be enabled. This includes the creation of an IBM Cloud Monitoring Instance and an Intel Monitoring Instance to host the services. If you already have an existing monitoring instance then specify in optional parameter 'existing\_monitoring\_instance\_crn'. |`bool`|`true`| no |
142
+
| <aname="input_enable_scc_wp"></a> [enable\_scc\_wp](#input\_enable\_scc\_wp)| Set to true to enable SCC Workload Protection and install and configure the Sysdig agent on all VSIs and PowerVS instances in this deployment. |`bool`|`false`| no |
139
143
| <aname="input_existing_monitoring_instance_crn"></a> [existing\_monitoring\_instance\_crn](#input\_existing\_monitoring\_instance\_crn)| Existing CRN of IBM Cloud Monitoring Instance. If value is null, then an IBM Cloud Monitoring Instance will not be created but an intel VSI instance will be created if 'enable\_monitoring' is true. |`string`|`null`| no |
140
144
| <aname="input_existing_sm_instance_guid"></a> [existing\_sm\_instance\_guid](#input\_existing\_sm\_instance\_guid)| An existing Secrets Manager GUID. The existing Secret Manager instance must have private certificate engine configured. If not provided an new instance will be provisioned. |`string`|`null`| no |
141
145
| <aname="input_existing_sm_instance_region"></a> [existing\_sm\_instance\_region](#input\_existing\_sm\_instance\_region)| Required if value is passed into `var.existing_sm_instance_guid`. |`string`|`null`| no |
@@ -150,7 +154,7 @@ Creates VPC Landing Zone | Performs VPC VSI OS Config | Creates PowerVS Infrastr
150
154
| <aname="input_powervs_management_network"></a> [powervs\_management\_network](#input\_powervs\_management\_network)| Name of the IBM Cloud PowerVS management subnet and CIDR to create. | <pre>object({<br/> name = string<br/> cidr = string<br/> })</pre> | <pre>{<br/> "cidr": "10.51.0.0/24",<br/> "name": "mgmt_net"<br/>}</pre> | no |
151
155
| <aname="input_powervs_resource_group_name"></a> [powervs\_resource\_group\_name](#input\_powervs\_resource\_group\_name)| Existing IBM Cloud resource group name. |`string`| n/a | yes |
152
156
| <aname="input_powervs_zone"></a> [powervs\_zone](#input\_powervs\_zone)| IBM Cloud data center location where IBM PowerVS infrastructure will be created. |`string`| n/a | yes |
153
-
| <aname="input_prefix"></a> [prefix](#input\_prefix)| A unique identifier for resources. Must begin with a lowercase letter and end with a lowercase letter or number. This prefix will be prepended to any resources provisioned by this template. Prefixes must be 16 or fewer characters. |`string`| n/a | yes |
157
+
| <aname="input_prefix"></a> [prefix](#input\_prefix)| A unique identifier for resources. Must begin with a lowercase letter and end with a lowercase letter or number. This prefix will be prepended to any resources provisioned by this template. Prefixes must be 10 or fewer characters. |`string`| n/a | yes |
154
158
| <aname="input_sm_service_plan"></a> [sm\_service\_plan](#input\_sm\_service\_plan)| The service/pricing plan to use when provisioning a new Secrets Manager instance. Allowed values: `standard` and `trial`. Only used if `existing_sm_instance_guid` is set to null. |`string`|`"standard"`| no |
155
159
| <aname="input_ssh_private_key"></a> [ssh\_private\_key](#input\_ssh\_private\_key)| Private SSH key (RSA format) to login to Intel VSIs to configure network management services (SQUID, NTP, DNS and ansible). Should match to public SSH key referenced by 'ssh\_public\_key'. The key is not uploaded or stored. For more information about SSH keys, see [SSH keys](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys). |`string`| n/a | yes |
156
160
| <aname="input_ssh_public_key"></a> [ssh\_public\_key](#input\_ssh\_public\_key)| Public SSH Key for VSI creation. Must be an RSA key with a key size of either 2048 bits or 4096 bits (recommended). Must be a valid SSH key that does not already exist in the deployment region. |`string`| n/a | yes |
@@ -165,7 +169,7 @@ Creates VPC Landing Zone | Performs VPC VSI OS Config | Creates PowerVS Infrastr
165
169
| <aname="output_access_host_or_ip"></a> [access\_host\_or\_ip](#output\_access\_host\_or\_ip)| Access host(jump/bastion) for created PowerVS infrastructure. |
166
170
| <aname="output_ansible_host_or_ip"></a> [ansible\_host\_or\_ip](#output\_ansible\_host\_or\_ip)| Central Ansible node private IP address. |
167
171
| <aname="output_dns_host_or_ip"></a> [dns\_host\_or\_ip](#output\_dns\_host\_or\_ip)| DNS forwarder host for created PowerVS infrastructure. |
168
-
| <aname="output_monitoring_instance"></a> [monitoring\_instance](#output\_monitoring\_instance)| Details of the IBM Cloud Monitoring Instance: CRN, location, guid |
172
+
| <aname="output_monitoring_instance"></a> [monitoring\_instance](#output\_monitoring\_instance)| Details of the IBM Cloud Monitoring Instance: CRN, location, guid, monitoring\_host\_ip.|
169
173
| <aname="output_network_services_config"></a> [network\_services\_config](#output\_network\_services\_config)| Complete configuration of network management services. |
170
174
| <aname="output_nfs_host_or_ip_path"></a> [nfs\_host\_or\_ip\_path](#output\_nfs\_host\_or\_ip\_path)| NFS host for created PowerVS infrastructure. |
171
175
| <aname="output_ntp_host_or_ip"></a> [ntp\_host\_or\_ip](#output\_ntp\_host\_or\_ip)| NTP host for created PowerVS infrastructure. |
@@ -178,10 +182,11 @@ Creates VPC Landing Zone | Performs VPC VSI OS Config | Creates PowerVS Infrastr
178
182
| <aname="output_powervs_workspace_id"></a> [powervs\_workspace\_id](#output\_powervs\_workspace\_id)| PowerVS infrastructure workspace id. The unique identifier of the new resource instance. |
| <aname="output_powervs_zone"></a> [powervs\_zone](#output\_powervs\_zone)| Zone where PowerVS infrastructure is created. |
181
-
| <aname="output_prefix"></a> [prefix](#output\_prefix)| The prefix that is associated with all resources |
185
+
| <aname="output_prefix"></a> [prefix](#output\_prefix)| The prefix that is associated with all resources.|
182
186
| <aname="output_proxy_host_or_ip_port"></a> [proxy\_host\_or\_ip\_port](#output\_proxy\_host\_or\_ip\_port)| Proxy host:port for created PowerVS infrastructure. |
183
187
| <aname="output_resource_group_data"></a> [resource\_group\_data](#output\_resource\_group\_data)| List of resource groups data used within landing zone. |
184
-
| <aname="output_ssh_public_key"></a> [ssh\_public\_key](#output\_ssh\_public\_key)| The string value of the ssh public key used when deploying VPC |
188
+
| <aname="output_scc_wp_instance"></a> [scc\_wp\_instance](#output\_scc\_wp\_instance)| Details of the Security and Compliance Center Workload Protection Instance: guid, access key, api\_endpoint, ingestion\_endpoint. |
189
+
| <aname="output_ssh_public_key"></a> [ssh\_public\_key](#output\_ssh\_public\_key)| The string value of the ssh public key used when deploying VPC. |
185
190
| <aname="output_transit_gateway_global"></a> [transit\_gateway\_global](#output\_transit\_gateway\_global)| Connect to the networks outside the associated region. |
186
191
| <aname="output_transit_gateway_id"></a> [transit\_gateway\_id](#output\_transit\_gateway\_id)| The ID of transit gateway. |
187
192
| <aname="output_transit_gateway_name"></a> [transit\_gateway\_name](#output\_transit\_gateway\_name)| The name of the transit gateway. |
0 commit comments