• Optimized AIX OS initialization

• Added prefix to Trusted Profile Names for SCC WP.
• Updated AIX OS initialization to use curl version - 7.53.

• Upgraded IBM terraform provider version to 1.79.2 which fixes resource group, trusted profile and resource key creation in parallel.

• Upgraded IBM terraform provider version to 1.79.0
• Enabled OS initialization and configured SCC Workload Protection for AIX and Linux systems as part of the Quickstart Variant deployment

• Upgraded IBM terraform provider version to 1.78.3
• Enabled Cloud Security Posture Management (CSPM) for SCC workload Protection

• Optimized monitoring host configuration.

• Automatically generate new certificates for Client to site VPN if reusing Secrets manager instance.

• Upgrade IBM TF provider version to 1.78.2 to enable retry support for PowerVS network create and delete operations.

• All Terraform module variations now output KMS keys and VSI SSH key details, enhancing transparency and simplifying integration with dependent resources.

• Standard Variation has been renamed to Standard Landscape and Standard Extend variation has been renamed to Extend Standard Landscape.
• Import varaition has been removed.
• Quickstart now deploys Client-to-site VPN, SCC-WP by default. These can be disabled by adjusting the optional parameter settings.
• Stock catalog image import into the PowerVS workspace is no longer needed. PowerVS instances can now be created from catalog images without previously importing the images.
• Fixed Quickstart deployments for SAP profile t-shirt:
  • In P10 datacenters, the sh2-4x256 profile is used.
  • In non-P10 datacenters, the ush1-4x256 profile is used.

• Upgrade IBM terraform provider version to 1.78.0 which fixes provider trying to recreate the atracker target set to COS and updating the atracker route.

• Quickstart now deploys an instance on Power 10 (s1022) in the following regions: dal10, dal12, dal14, eu-de-1, eu-de-2, mad02, mad04, osa21, sao01, sao04, tok04, wdc06, wdc07
• In the following regions, s922 is used: che01, lon04, lon06, mon01, syd04, syd05, tor01, us-east, us-south

• Included outputs for VPC and Application Load Balancer
• Upgrade IBM terraform provider to 1.77.0
• Upgrade landing-zone module to 7.4.4
• Upgrade client-to-site-vpn module to 2.2.5

• Modified the creation of the Secrets Manager instance to support both public and private endpoints, instead of private-only.

• Increase the maximum length of prefix that's used for the resources deployed by this architecture from 10 to 16
• Upgrade client-to-site-vpn module to 2.1.6
• Upgrade landing-zone module to 7.3.2
• Upgrade scc-workload-protection module to 1.5.3
• Upgrade IBM terraform provider to 1.76.2
• Upgrade powers-instance module to 2.5.2

• The Standard and Quickstart Variation now supports optional deployment of IBM Cloud® Security and Compliance Center Workload Protection instance and SCC Workload Protection agent installation and configuration on all intel VSIs. IBM Cloud® Security and Compliance Center Workload Protection helps to find and prioritize software vulnerabilities, detect and respond to threats, and manage configurations, permissions, and compliance from source to run.

• The PowerVS instance created through the Quickstart variation now includes a prefix in its instance name.
• Upgrade IBM TF provider to 1.76.1

• Ensured the use of a strong Ansible Vault password with 15-100 characters, including at least one uppercase letter, one lowercase letter, one number, and one special character from the allowed set: !#$%&()*+-.:;<=>?@[]_{|}~.
• Upgrade IBM TF provider to 1.75.2
• Upgrade VSI intel image

• Users can now specify their desired boot image for VPC's Intel Virtual Server Instances
• Updated the default AiX image for product variation standard-plus-vsi
• Upgraded IBM provider version to 1.74.0

Version 8.1.1 of the Power Virtual Server with VPC landing zone deployable architecture is available in the IBM Cloud catalog

Features:

• Upgraded version of powervs-workspace module to 2.4.0
  • Support tags for networks and images
  • Upgrade minimum IBM provider version to >=1.71.0
• Upgraded version of powervs-instance module to 2.3.0
  • Support tags for instance and storage
• Upgraded Default IBMi and RHEL images for Quickstart

Version 8.1.0 of the Power Virtual Server with VPC landing zone deployable architecture is available in the IBM Cloud catalog

• Breaking Change:
  • New landing zone version 6.4.0 creates VSis using VNIs and legacy interfaces are not used any more.
  • Landing zone preset reworked to create security groups separately and then assign to VSIs. This will recreate the VSIs.

Features:

• Provision Monitoring Instance and an intel VSI to host and process monitoring metrics for SAP
• Upgrade Rhel images running on Intel VSI (jump box and network services vsi to RHEL 9.4)
• Upgraded minimum IBM power linux sap ansible role version to v3.0.0
• Upgraded IBM TF version to 1.71.3
• Remove ansible collection version dependencies from scripts instead install collection dependencies from ansible galaxy requirements.yml
• Support DAL14 and LON04 DC
• Support Mad04 DC for Quickstart. Deployments in MAD04 requires value in custom profile to be set as this DC supports P10 only.

Version 7.1.0 of the Power Virtual Server with VPC landing zone deployable architecture is available in the IBM Cloud catalog

• Upgraded minimum required terraform version to >=1.9.0
• Upgraded IBM terraform provider version to v1.71.1
• Upgraded Default IBMi and AIX images for Quickstart
• Upgraded version of powervs-workspace module to 2.2.0
• support custom image import from Cloud Object Storage to Power Virtual Server workspace for up to three images in the Standard and standard extension variations

Version 7.0.0 of the Power Virtual Server with VPC landing zone deployable architecture is available in the IBM Cloud catalog

• BREAKING CHANGE:
  • Version 7.0.0 includes backward-incompatible changes.
  • When you upgrade to version 7.0.0, you might see some of your infrastructure marked for deletion and re-creation. Fully supported migration steps will be available shortly to prevent this from occurring, so if re-creating infrastructure is going to impact day-to-day operations, don't update to this version until there is a fully supported migration path.
• VPC landing zone deployable architecture is not affected.
• Allows user to specify the compute profile (cores and memory) for network services Intel VSI
• The IBM Terraform provider version is now locked to 1.69.2.
• The landing-zone-vsi submodule is updated from 3.3.0 to 4.2.0. In this version, the naming convention for Virtual Server Instances has changed to be prefix- + the last 4 digits of the subnet ID + a sequential number for each subnet. For example, prefix-3ad7-001.

Version 6.0.0 of the Power Virtual Server with VPC landing zone deployable architecture is available in the IBM Cloud catalog

• BREAKING CHANGE:
  • Version 6.0.0 includes backward-incompatible changes.
  • create ibm_is_share in correct resource group and update ansible role version
  • Backup your data. All data on the NFS share will be lost.
  • If you upgrade from an older version, this will destroy and recreate the NFS share in correct resource group. It is important to backup your data. You can copy the the data to COS or copy it locally using commands. The automation does not help in doing this. Once it is recreated and mounted, you can copy the files to the NFS mount.

• Enable support for global transit gateway in optional parameters for standard variation.

• Renamed Power Virtual Server Workspace Variation to Standard.
• Renamed Import Power Virtual Server Workspace to Import.

• Take a look at may26 release notes( version 5.1.2).
• Support Linux images in custom images for Quickstart variation.
• Upgrade IBMi images in tshirt sizes.

• Completely New architecture. Does not support the upgrade process from previous version 4.x.x to 5.x.x
• Use this version for new deployments only.
• Option to create new secrets manager instance or reuse existing one.
• Optional Client to site VPN deployment.
• Switched from Block storage NFS volumes to File storage shares. Uses Application Load Balancer to mount the File Storage shares on Power Virtual Server instances.
• Removed Cloud connection support.
• Private SSH keys need not be entered in here doc string format. Can be passed in directly.
• Improved documentation.
• Network-services vsi is now the central ansible execution node.
• Both intel VSIs run on RHEL 8.8 OS.

• Do not upgrade if you already have an existing deployment.
• Make a new deployment and then restore your OS data that use data migration techniques.

• Upgrade Toronto 01 tor01 DC to PER. New deployments in theToronto 01 region makes use of PER.
• Upgrade US-south us-south DC to PER. New deployments in theUs-south region makes use of PER.
• Quickstart now supports SLES SAP DEV t-shirt size.

• Do not upgrade to this version if previous deployments were made in tor01 and us-south Power Virtual Server zone as doing so corrupts the landscape due to the switch from Cloud Connections to PER.
• Use this version for New deployments in thetor01 and us-south Power Virtual Server zone.
• Deployments that are done in other Power Virtual Server zone can be upgraded with any issue.

• Upgrade Sydney 04 syd04 DC to PER. New deployments in theSydney 04 region makes use of PER.

• Do not upgrade to this version if previous deployments were made in Sydney 04 syd04 Power Virtual Server zone as doing so corrupts the landscape due to the switch from Cloud Connections to PER.
• Use this version for New deployments in theSydney 04 syd04 Power Virtual Server zone.
• Deployments that are done in other Power Virtual Server zone can be upgraded with any issue.

• Upgrade DAs to version 1.64.1 terraform IBM provider version
• Upgrade Quickstart Solution to utilize the latest AIX and IBMi images.

• Upgrade London 06 lon06 DC to PER. New deployments in theLondon 06 region makes use of PER.

• Do not upgrade to this version if previous deployments were made in London 06 lon06 Power Virtual Server zone as doing so corrupts the landscape due to the switch from Cloud Connections to PER.
• Use this version for New deployments in theLondon 06 lon06 Power Virtual Server zone.
• Deployments that are done in other Power Virtual Server zone can be upgraded with any issue.

• Upgrade Sydney 05 syd05 DC to PER. New deployments in theSydney 05 region makes use of PER.

• Do not upgrade to this version if previous deployments were made in Sydney 05 syd05 Power Virtual Server zone as doing so corrupts the landscape due to the switch from Cloud Connections to PER.
• Use this version for New deployments in theSydney 05 syd05 Power Virtual Server zone.
• Deployments that are done in other Power Virtual Server zone can be upgraded with any issue.

• Upgrade Osaka 21 osa21 DC to PER. New deployments in theOsaka region makes use of PER.

• Do not upgrade to this version if previous deployments were made in Osaka 21 osa21 Power Virtual Server zone as doing so corrupts the landscape due to the switch from Cloud Connections to PER.
• Use this version for New deployments in theOsaka 21 osa21 Power Virtual Server zone.
• Deployments that are done in other Power Virtual Server zone can be upgraded with any issue.

• Upgrade Tokyo 04 tok04 DC to PER. New deployments in theTokyo region makes use of PER.

• Do not upgrade to this version if previous deployments were made in Tokyo 04 tok04 Power Virtual Server zone as doing so corrupts the landscape due to the switch from Cloud Connections to PER.
• Use this version for New deployments in theTokyo 04 tok04 Power Virtual Server zone.
• Deployments that are done in other Power Virtual Server zone can be upgraded with any issue.

• Upgrade Sao Paulo 01 sao01 DC to PER. New deployments in the Sao Paulo 01 region makes use of PER.

• Do not upgrade to this version if previous deployments were made in Sao Paulo 01 sao01 Power Virtual Server zone as doing so corrupts the landscape due to the switch from Cloud Connections to PER.
• Use this version for New deployments in the Sao Paulo 01 sao01 Power Virtual Server zone.
• Deployments that are done in other Power Virtual Server zone can be upgraded with any issue.

• Upgrade Dallas 12 dal12 DC to PER. New deployments in the Dallas 12 region makes use of PER.

• Do not upgrade to this version if previous deployments were made in Dallas 12 dal12 Power Virtual Server zone as doing so corrupts the landscape due to the switch from Cloud Connections to PER.
• Use this version for New deployments in the Dallas 12 dal12 Power Virtual Server zone.
• Deployments that are done in other Power Virtual Server zone can be upgraded with any issue.

• Introducing the new import-workspace variant of Power Virtual Server with VPC landing zone deployable architecture. For more information see the Power Virtual Server with VPC landing zone import-workspace variation.

• Upgrade Frankfurt 1 eu-de-1 DC to PER. New deployments in the Frankfurt 1 region makes use of PER.

• Do not upgrade to this version if previous deployments were made in Frankfurt 1 eu-de-1 Power Virtual Server zone as doing so corrupts the landscape due to the switch from Cloud Connections to PER.
• Use this version for New deployments in the Frankfurt 1 eu-de-1 Power Virtual Server zone.
• Deployments that are done in other Power Virtual Server zone can be upgraded with any issue.

• Enable support for WDC07, MAD02, MAD04 and SAO04 PER datacenters for Power Virtual Server Workspace Variation only.
• Enable support for WDC07and SAO04 PER datacenters for Power Virtual Server Quickstart Variation.
• Upgrade Frankfurt 2 eu-de-2 DC to PER. New deployments in the Frankfurt 2 region makes use of PER.
• Fixes outputs of workspace when DNS, NTP and NFS services are set to false.

• Do not upgrade to this version if previous deployments were made in Frankfurt 2 eu-de-2 Power Virtual Server zone as doing so corrupts the landscape due to the switch from Cloud Connections to PER.
• Use this version for New deployments in the Frankfurt 2 eu-de-2 Power Virtual Server zone.
• Deployments that are done in other Power Virtual Server zone can be upgraded with any issue.

• Upgrade TF IBM provider version to 1.61.0
• Change default Power Virtual Server images for AIX and IBM i for all variations
• Quickstart flavour now has a tshirt size Custom (Configure in optional parameters) in the dropdown. This is used when custom_profile needs to be used for custom deployments.

• When upgrading to this version floating IPs are going to be deleted and recreated upon apply. This is due to a bug where the floating IPs were being created incorrectly in the Default resource group. Upon re-creation, the floating IPs will be created in the same resource group as the VSI.
• Accordingly, please plan before upgrading incase this change will cause disruption for whatever is using the floating IPs.
• 3 sleep resources will be deleted because of changes in the VPC landing zone module version

• Support MAD02 data center which is PER enabled.

• Support WDC06 data center which is PER enabled.

• Support all private Power Virtual Server CIDRs in ACL rule.
• Import any number of Power Virtual Server images, and in parallel.
• The clean_default_sg_acl input is included in the landing zone preset to clean the default sg rule for new deployments.
• Upgrade to ibm-sles-15-4-amd64-sap-applications-6 & ibm-redhat-8-6-amd64-sap-applications-4 on intel VSI landing zone for new deployments. This does not affect the previous DA version.

• Back up the data on the 10.20.10.4 private-svs-1 VSI in the /nfs directory before you upgrade to version 3.0.0.
• When you upgrade the full-stack solution, the Ansible roles are triggered again, the ACL rules are updated, and the NFS disk will be re-created.
• Schedule the upgrade.
  • The new landing zone version re-creates the 1 TB storage disk in a different resource group, so you will experience less down time.
  • When you upgrade, the deployable architecture will be down for about 20 minutes, and the Intel VSI will reboot.
• If you deployed the QuickStart variation, you might want to create another deployable architecture rather than upgrade. The VM and VPC subnets are re-created, which might affect demos and PoCs.

• Support RHEL 8.6 and SLES 15.4 images
• Support DAL10 data center which is PER enabled.

• Introducing the new quickstart variant of Power Virtual Server with VPC landing zone deployable architecture. For more information see Power Virtual Server with VPC landing zone quickstart variation

• Introducing Power Virtual Server with VPC landing zone
• The Power Virtual Server with VPC landing zone deployable architecture is released. You can use the deployable architecture to create an isolated Power Virtual Server landscape connected with VPC landing zone.