W-16981289-VPC-Upgrade #751
Conversation
| @@ -0,0 +1,3 @@ | |||
| = Upgrade to CloudHub 2.0 | |||
|
|
|||
| Mulesoft is strategically migrating its deployment platforms into a unified runtime platform. This allows for an improved platform scaling, maintainance and operation, and provides agility y enabling you to to create your applications once and deploy anywhere. | |||
There was a problem hiding this comment.
This is internal strategy. From the customer's standpoint - please pick/summarize content from this page : https://docs.mulesoft.com/cloudhub-2/ch2-comparison
There was a problem hiding this comment.
Also, recommend having just a single document (so potentially remove this page altogether). Can move the introduction to a higher-level page when traffic switching / app upgrade functionality is delivered.
| @@ -0,0 +1,85 @@ | |||
| = VPC Upgrade to Private Space | |||
There was a problem hiding this comment.
CloudHub 1.0 VPC to CloudHub 2.0 Private Space Upgrade
| = VPC Upgrade to Private Space | ||
|
|
||
| //Overview | ||
| CloudHub VPC upgrade is an out-of-the-box tool and guided UI experience for an infrastructure upgrade to accelerate the migration of a VPC into a Private Space. |
There was a problem hiding this comment.
I would avoid calling the feature "CloudHub VPC Upgrade".
If you are looking to migrate your workloads from CloudHub 1.0 to CloudHub 2.0, you can kickstart your journey by first upgrading your CloudHub VPC to a CloudHub 2.0 Private Space using the in-product upgrade tool.
| // Benefits | ||
| This tool enables you to provision the infrastructure of a CloudHb 2.0 Private Space by cloning the existing configurations of eligible CloubHub VPCs, and carrying over any existing network connections, including TGWs and VPNs. | ||
|
|
||
| At the same time, this UI experience reduces migration time and costs by eliminating a two- to-three-month toil to obtain all the necessary infrastructure and security approvals on new network connections and CIDR blocks. |
There was a problem hiding this comment.
Delete - already incorporated above
| CloudHub VPC upgrade is an out-of-the-box tool and guided UI experience for an infrastructure upgrade to accelerate the migration of a VPC into a Private Space. | ||
|
|
||
| // Benefits | ||
| This tool enables you to provision the infrastructure of a CloudHb 2.0 Private Space by cloning the existing configurations of eligible CloubHub VPCs, and carrying over any existing network connections, including TGWs and VPNs. |
There was a problem hiding this comment.
The VPC to Private Space Upgrade tooling enables you to accelerate the creation of a CloudHub 2.0 Private Space by simply upgrading your existing CloudHub VPC. If you upgrade your CloudHub VPC into a Private Space instead of creating a new CloudHub 2.0 Private space, you can eliminate the time spent in acquiring new CIDR block, setting up new network connections, and configuring the private space from scratch.
The tool enables you to provision the infrastructure of a CloudHub 2.0 Private Space by cloning the existing configurations of an eligible CloubHub VPC while leveraging the same CIDR block. If your VPC has existing TGW or VPN network connections, they will be carried over to the upgraded CloudHub 2.0 Private Space, and available for communication with any new applications deployed into the upgraded CloudHub 2.0 Private Space.
Once your Private Space is created, proceed to incrementally migrate your applications from the CloudHub 1.0 VPC to the CloudHub 2.0 private space in a timely manner.
| The *Upgrade to CloudHub 2.0* window lists all VPCs that are eligible for upgrade. | ||
| . Click *Upgrade Now*, under the *Upgrade Status* column for the VPC you want to upgrade. | ||
| + | ||
| The *Upgrade to CloudHub 2.0* review page shows what elements are already available in your VPC and what elements are created during the upgrade. |
| . Click *Next* to continue. | ||
| . Provide a name for the new private space. | ||
| + | ||
| Optionally, you can specify reserved CIDRs to connect to your new private space. |
There was a problem hiding this comment.
Need to hyperlink to reserved cidrs docs
|
|
||
| Once the upgrade process completes, the private space is fully provisioned and you can start deploying applications to it. | ||
|
|
||
| You can continue to deployand manage applications into your VPC, but you can't change any VPC configurations. Make any infrastructure changes in the newly upgraded private space. |
There was a problem hiding this comment.
You can continue to deploy and manage applications in your VPC. However, after the upgrade, the CloudHub VPC will not allow any new infrastructure changes (such as environment or business group associations, changes to network connections and changes to Internal DNS). These changes will need to be made on the newly upgraded private space, going forward. These changes will also get applied to the CloudHub VPC for the duration of your upgrade.
The firewall rules configured at the VPC will be copied into the Private Space at the time of upgrade. Thereafter, you will have the flexibility to make additional changes to the Firewall rules both the VPC as well as the Private Space. To avoid configuration drift, ensure that any Firewall rule changes are made in both places for the duration of your migration.
|
|
||
| //after VPC Upgrade | ||
|
|
||
| Once the upgrade process completes, the private space is fully provisioned and you can start deploying applications to it. |
There was a problem hiding this comment.
Add: You can begin migrating your applications one by one by creating new applications in the CloudHub 2.0 Private Space and deleting the equivalent application in the CloudHub 1.0 VPC. Once you are finished upgrading all applications, please delete your VPC & any attached Dedicated Load Balancers on CloudHub 1.0.
| + | ||
| The *Upgrade to CloudHub 2.0* review page displays the configurations currently available in your VPC, as well as the configurations that are created during the upgrade. | ||
| + | ||
| image::upgrade-ch2-review-conf.png[] |
There was a problem hiding this comment.
Can you add alt text here? ["Upgrade to CloudHub 2.0 review page showing available configurations"]
(or whatever the image is...)
Co-authored-by: Hanna Nelson <[email protected]>
Co-authored-by: Hanna Nelson <[email protected]>
Co-authored-by: Hanna Nelson <[email protected]>
Co-authored-by: Hanna Nelson <[email protected]>
Co-authored-by: Hanna Nelson <[email protected]>
Co-authored-by: Hanna Nelson <[email protected]>
Co-authored-by: Hanna Nelson <[email protected]>
Co-authored-by: Hanna Nelson <[email protected]>
Co-authored-by: Hanna Nelson <[email protected]>
…in wil not be able to be upgraded.
[W-17251206] Add line for no Internal DNS settings
Writer's Quality Checklist
Before merging your PR, did you: