随着公司的发展和技术的更迭,许多公司原有的基础架构难以满足现有的需求。在过去的几十年里,公司的数据呈指数级增长,由此衍生出来了数据分析的需求。随着消费者行为的转型,许多电商平台或者是零售行业的公司都迫切需要机器学习等技术来帮助理解消费者的行为方式以便于及时调整业务方向。
而在这种情况下,许多公司转向了谷歌云平台。谷歌云使用与谷歌搜索、谷歌学术、Youtube等相同的基础设施和技术,在数据分析和机器学习等领域拥有巨大的优势,使用谷歌云平台可以轻松使用Big Query分析PB级数据,也可以用Vertex AI 分析平台来进行机器学习,用较低的价格提供优质的服务。
如何从AWS搬迁到GCP,成为上述公司的关注重点和热门话题,本文将一个步骤一个步骤地分解,演示如何从AWS搬迁到GCP。
其主要的步骤包括:
- VPN 设置
- GCP 环境设置
- AWS 环境设置
- AWS 虚拟机中的迁移代理安装
- 迁移过程
详细内容请参考如下文所示。
1. VPN 设置
AWS 和 GCP 环境之间需要设置一个VPN通道
1.1 GCP设置VPC
1.1.1 创建vpc
名称随意,然后按照下图所示输入信息(区域按照自己的需要选择),其余默认。
![](https://pic2.zhimg.com/80/v2-723b13c00b30e88afd8f477c712ba295_720w.jpg)
1.1.2 创建外部IP
需要创建一个外部IP(区域选择和VPC一样的),用于aws设置网关
![](https://pic3.zhimg.com/80/v2-588fa72cae6adb8ad0f4824abc72cb9a_720w.jpg)
IP创建成功如下图:
![](https://pic3.zhimg.com/80/v2-739c511672069666043d99031bead5fa_720w.jpg)
1.2 AWS设置VPC
1.2.1 创建vpc
按照如下图所示红圈中填入信息创建vpc并创建子网,其余默认。
![](https://pic4.zhimg.com/80/v2-6cdc69df71b0e65d84430960e5c9b173_720w.jpg)
![](https://pic3.zhimg.com/80/v2-6e74c56a9557b5227428b82baddd4ce6_720w.jpg)
1.2.2 创建客户网关
输入名称和在GCP创建的IP地址
![](https://pic4.zhimg.com/80/v2-9e174e2ca74a5e156585ee61e3f0a103_720w.jpg)
1.2.3 创建并设置虚拟私有网关
创建虚拟私有网关:
![](https://pic1.zhimg.com/80/v2-cb3ff02203bef69c80a8456f6c9b5b70_720w.jpg)
右键单击虚拟私有网关,选择“附加到VPC”
![](https://pic4.zhimg.com/80/v2-5dd93c5458539cf4c543a99270e1b88f_720w.jpg)
选择前面创建的VPC,点击“附加到VPC”
![](https://pic4.zhimg.com/80/v2-7b121c5d25b3b1403471216c3fd7b4f7_720w.jpg)
1.2.4 创建站点到站点VPN连接
![](https://pic3.zhimg.com/80/v2-f452c7cc8636bd747f39eb67657d0726_720w.jpg)
按照下图所示创建(静态IP前缀:172.16.0.0/16是GCP的子网地址空间):
![](https://pic4.zhimg.com/80/v2-f9fe9addc6685a4660f0095baa93165f_720w.jpg)
1.2.5 下载配置文件
按照如下操作下载配置文件:
![](https://pic2.zhimg.com/80/v2-a86e54396fe8bfa42412982b5f026c15_720w.jpg)
![](https://pic4.zhimg.com/80/v2-0aaca633484299b61f3fad6130bf1eaf_720w.jpg)
配置文件后续会用到,请记住保存路径。
1.2.6 创建并配置路由表
![](https://pic1.zhimg.com/80/v2-1ff56a6ac7256f85597651ad036f52d0_720w.jpg)
![](https://pic1.zhimg.com/80/v2-9422629728e331c7ad96185521254460_720w.jpg)
创建完成后配置路由表:
![](https://pic1.zhimg.com/80/v2-44ebbc37c4e233216f65fbeaca139488_720w.jpg)
勾选“启用”,点击保存:
![](https://pic2.zhimg.com/80/v2-000df5cff626f451a66e8272b3341b89_720w.jpg)
编辑路由:
![](https://pic1.zhimg.com/80/v2-d42b802715b1f3305139d1cdd3d0de04_720w.jpg)
![](https://pic1.zhimg.com/80/v2-d42b802715b1f3305139d1cdd3d0de04_720w.jpg)
添加子网关联:
![](https://pic1.zhimg.com/80/v2-5fbee414a0e344987924a807834d7190_720w.jpg)
勾选两个子网,点击保存关联:
![](https://pic4.zhimg.com/80/v2-c64491fc81fd1ba738bb608d17585db7_720w.jpg)
1.3 GCP配置VPN
创建VPN
![](https://pic3.zhimg.com/80/v2-769cc1f0e94aa1c3f048485d12a4d49e_720w.jpg)
![](https://pic3.zhimg.com/80/v2-6bd2d34b4b8b480af0ea5c05f48afd92_720w.jpg)
打开1.2.5步骤下载的配置文件,找到对等IP和key填入(任选其中一个通道):
![](https://pic4.zhimg.com/80/v2-12f403a971de02816b96db3da21e5cab_720w.jpg)
再按照下图操作点击创建:
![](https://pic1.zhimg.com/80/v2-a6ab1957b2c6201474df79fcc4b86714_720w.jpg)
1.4 检查VPN连接
AWS端:
![](https://pic3.zhimg.com/80/v2-f5e3f3039133594202bce963056b0886_720w.jpg)
GCP端:
![](https://pic1.zhimg.com/80/v2-1aaf9795608829661886852520505468_720w.jpg)
通过虚拟机之间相互ping来验证VPN:
设置AWS安全组的入站规则:
![](https://pic1.zhimg.com/80/v2-47a12c2795f70aca2f371e72106daa04_720w.jpg)
设置GCP的防火墙规则:
![](https://pic4.zhimg.com/80/v2-88a6ed80f16fe7200c76a9aa31fb15d3_720w.jpg)
AWS虚拟机 ping通GCP虚拟机如下所示:
![](https://pic4.zhimg.com/80/v2-5225009b141feea6b9b8164b4d2edf5f_720w.jpg)
从GCP虚拟机ping通AWS虚拟机如下所示:
![](https://pic4.zhimg.com/80/v2-e31c8939cfdfe4001ede760703d13753_720w.jpg)
2. GCP环境设置
2.1 配置防火墙规则
按照下图配置GCP防火墙规则(AWS VPC CIDR 范围为 10.20.0.0/16,GCP VPC CIDR 范围为 172.16.0.0/16
Firewall rule | Description | Target tag | Source tag/IP | Protocol/Ports |
Allow-aws-connection(optional) | AWS to GCP VPC | Apply to all | AWS VPC CIDR Range | all |
velos-ce-backend | Encrypted migration data sent from Velostrata Backend to Cloud Extensions. |
fw-velostrata | AWS VPC CIDR Range | tcp:9111 |
velos-ce-control | Control plane between Cloud Extensions and Velostrata Manager. |
fw-velostrata | fw-velosmanager | tcp:443, 9111 |
velos-ce-cross | Synchronization between Cloud Extension nodes. |
fw-velostrata | fw-velostrata | all |
velos-console-probe | Allows the Velostrata Manager to check if the SSH or RDP console on the migrated VM is available. |
fw-workload | fw-velosmanager | tcp:22,3389 |
velos-manager-ssh | To access velo-manager | fw-velosmanager | Your Public IP(for ssh purpose),AWS VPC CIDR Range |
tcp:22 |
velos-webui | HTTP & HTTPS access to Velostrata Manager for web UI. |
fw-velosmanager | AWS VPC CIDR Range, GCP VPC CIDR Range, Your Public IP(for accessing velostrata UI) |
tcp:443,80 |
velos-workload | migrated workloads → velos edge for migration & syslog |
fw-velostrata | fw-workload | tcp:3260 udp:514 |
workload-rdp-ssh-allow | migrate workload access | fw-workload | Your Public IP(for ssh & RD purpose), AWS VPC CIDR Range |
tcp:22,3389 |
配置好如下图所示:
![](https://pic1.zhimg.com/80/v2-c86076bf3aa0bdbd0ed950bafbe409cc_720w.jpg)
2.2 创建和配置迁移管理器
![](https://pic1.zhimg.com/80/v2-370a569ae69ba0d789ea0a4ca4e7e3dc_720w.jpg)
![](https://pic2.zhimg.com/80/v2-a91d942bc010024d09a1eae272bdfe31_720w.jpg)
![](https://pic2.zhimg.com/80/v2-4f457657e7fad11fcc77314f792f1c71_720w.jpg)
填入网络标记后,服务账号处选择新建,输入服务账号名保存即可:
![](https://pic2.zhimg.com/80/v2-96d7ff5dc5e11daf912bc717508e2ef9_720w.jpg)
点击右边的生成密码,同时记录好账号和密码,后续会用到:
![](https://pic1.zhimg.com/80/v2-6948dea087390d17733f634fb66a617c_720w.jpg)
![](https://pic1.zhimg.com/80/v2-4f466c8c399e078bf0efaf6029fddf58_720w.jpg)
![](https://pic2.zhimg.com/80/v2-5742533c4372ce99d3c4c6fd492abb49_720w.jpg)
3. AWS环境设置
3.1 创建并配置堆栈
下载堆栈文件(https://cloud.google.com/migrate/compute-engine/docs/4.11/resources/downloads):
![](https://pic3.zhimg.com/80/v2-89f6fdc696ed30a5ad7d48956c1ab40e_720w.jpg)
解压缩得到json文件:
![](https://pic3.zhimg.com/80/v2-f3e5cb0447727e2955c40b70879d3666_720w.jpg)
在AWS控制台找到Cloud Formation,创建堆栈:
![](https://pic4.zhimg.com/80/v2-fd0f02833cdfd63f0341baaa80d46e63_720w.jpg)
上传前面解压得到的json文件:
![](https://pic1.zhimg.com/80/v2-25467de8683dc3e86688a0eef123e1fc_720w.jpg)
![](https://pic4.zhimg.com/80/v2-0f7b5940cea494cc9ebc44905266632f_720w.jpg)
![](https://pic1.zhimg.com/80/v2-7899a13e989729815b3f05874459b284_720w.jpg)
![](https://pic1.zhimg.com/80/v2-a5acac67041e66192a6857b5cd33d0e8_720w.jpg)
创建好如下图所示:
![](https://pic4.zhimg.com/80/v2-3d2b97287a3e9431745467327bb48367_720w.jpg)
3.2 创建IAM用户并加入VelosMgrGroup组
![](https://pic3.zhimg.com/80/v2-20153f550732103e243372f12a958a72_720w.jpg)
![](https://pic4.zhimg.com/80/v2-6f3fa0ae3cfdcea2c4ebc6d20263c29b_720w.jpg)
![](https://pic4.zhimg.com/80/v2-25d60f7ffd14b920e4f3f7ee001224b7_720w.jpg)
![](https://pic4.zhimg.com/80/v2-294f1df96eea64d536cbed585c9f83af_720w.jpg)
![](https://pic1.zhimg.com/80/v2-43e5e3be3c685f9ce8044eea1ab67c4c_720w.jpg)
创建完用户后,下载凭证(后续会用):
![](https://pic3.zhimg.com/80/v2-b5d0e63a581186b20908412aa4e1089e_720w.jpg)
4. AWS 虚拟机中的迁移代理安装
4.1 Windows虚拟机
在本地用远程工具打开AWS的虚拟机,下图以Windows2019为例:
![](https://pic1.zhimg.com/80/v2-d2f130a738257b7335796f5a8337b8dc_720w.jpg)
下载GCPpowershell模块 (https://cloud.google.com/migrate/compute-engine/docs/4.11/resources/downloads)
![](https://pic1.zhimg.com/80/v2-eb8bb62c098e39d764f307b76f5c95e4_720w.jpg)
安装:
![](https://pic1.zhimg.com/80/v2-6c9a26748dc7722a00f6a563c6872000_720w.jpg)
安装完成后,用管理员身份运行Windows PowerShell
![](https://pic4.zhimg.com/80/v2-5c770ecfbb27843e22856baf80ca66a7_720w.jpg)
复制以下命令到PowerShell运行:
Import-Module Velostrata.PowerShell
Connect-VelostrataManager
![](https://pic1.zhimg.com/80/v2-08e1690763d08b89a605f60ae3b9435c_720w.jpg)
接下来需要登录GCP的迁移管理器,Server为迁移管理器的内部IP(参考2.2章节的最后一张图);Username为”apiuser”,Password是前面创建并保存的(参考2.2章节的倒数第三张图)。
![](https://pic2.zhimg.com/80/v2-ec51a7ae824a0e11ac728f5a664a9bd5_720w.jpg)
复制以下命令到Powershell执行,会下载所需的安装包,按提示输入“Y”或者直接回车:
Get-help Connect-VelostrataManager
![](https://pic1.zhimg.com/80/v2-822252c19d260172d55a1b81df52a1c8_720w.jpg)
4.2 Linux虚拟机
登录Linux虚拟机,逐条执行以下命令:
wget https://storage.googleapis.com/velostrata-release/4.11.9/migrate-for-gce-prep-4.11.9-0.deb
sudo apt-get update
sudo apt --fix-broken install
sudo apt install multipath-tools*
sudo dpkg -i migrate-for-gce-prep-4.11.9-0.deb
sudo apt-get update && sudo apt-get install -f -y
![](https://pic4.zhimg.com/80/v2-6da573d255c50024f13bcddf57b1afdb_720w.jpg)
5. 迁移过程
5.1 登录云迁移平台
回到谷歌云控制台,找到迁移管理器的外部IP
![](https://pic2.zhimg.com/80/v2-5982fbeef4cc75a4dd4cc086942f4fd5_720w.jpg)
登录:
![](https://pic4.zhimg.com/80/v2-f565418acd32929341663a87b1624d03_720w.jpg)
仍然使用apiuser这个用户名和对应的密码登录,登录进来后选择“YES”启用StackDriver日志:
![](https://pic1.zhimg.com/80/v2-ffe2472e3b562e6e7326ae80a512e00c_720w.jpg)
![](https://pic3.zhimg.com/80/v2-84b13b1b70e57057117a938aa664956e_720w.jpg)
5.2 设置源云
![](https://pic3.zhimg.com/80/v2-61995ed2455e80b859cac7db246b1202_720w.jpg)
此处的两个key,在3.2章节最后的一张图中下载的文件,打开文件即可看到:
![](https://pic1.zhimg.com/80/v2-4e72953316594bdeee736287095401e4_720w.jpg)
![](https://pic2.zhimg.com/80/v2-86d12b6bff94274a6a7ef6b8b41200b1_720w.jpg)
5.3 设置目标云
在源云页面点击右上角的“HOME”返回首页,点击目标云:
![](https://pic2.zhimg.com/80/v2-4a7434f6c03eb0984e7f1c3d2829c3d1_720w.jpg)
创建云扩展,将创建2个需要500 GB SSD卷的VM。因此,请确保已将项目配额增加到至少 1 TB,查询方法:谷歌云控制台-IAM和管理-配额-SSD,如图:
![](https://pic1.zhimg.com/80/v2-141c6c84df93c99db7d9100ed965fa3c_720w.jpg)
开始创建云拓展,最后一项选择有权限创建VM的服务器账号:
![](https://pic4.zhimg.com/80/v2-e646ec0eea9c47431d1da659bac887db_720w.jpg)
接下来编辑“Cloud Extension”,最后一项当迁移的虚拟机数量少于或等于15台时选择“Small”,大于15台时选择“Large”:
![](https://pic1.zhimg.com/80/v2-b36e116d725a709d66a80e6382c40488_720w.jpg)
请选择该区域的两个不同区域,为两个区域选择相同的子网以降低复杂性。工作负荷子网是 VM 将迁移到的子网:
![](https://pic3.zhimg.com/80/v2-e440ee6f1801b598684d6a69dfe6f092_720w.jpg)
标签是将附加到运行迁移波次(工作负载 + 边缘节点)后创建的所有 VM 的标记:
![](https://pic2.zhimg.com/80/v2-809d636a065310081c97c21799c8befd_720w.jpg)
创建云拓展完成后,可以在谷歌云控制台-虚拟机实例看到两台刚创建好的边缘节点:
![](https://pic2.zhimg.com/80/v2-9cde3306bd273d4f8fc87803cae90465_720w.jpg)
分别点进去开启HTTP和HTTPS防火墙:
![](https://pic1.zhimg.com/80/v2-26c4450f73b16c7c321eca0f0c802b2c_720w.jpg)
![](https://pic2.zhimg.com/80/v2-11c9bedc4eb409e06c693aeb7120c601_720w.jpg)
5.4 设置迁移波
![](https://pic1.zhimg.com/80/v2-0ad7b4dbb6ff6d10605651b86457f5c4_720w.jpg)
![](https://pic1.zhimg.com/80/v2-782c68c92dc771b44c74859e11134974_720w.jpg)
单击“创建”按钮后,将下载一个 CSV 文件,其中包含要迁移的 AWS VM 的所有详细信息(如果文件内没有内容,请给虚拟机增加上图对应的标签后重试):
![](https://pic1.zhimg.com/80/v2-09c01fdaf8c27de56e759bd7b32fa728_720w.jpg)
打开文件,修改三个地方后保存:
①去掉第一列的“-“号;
②选择迁移到GCP后的实例类型;
③为实例命名。
![](https://pic4.zhimg.com/80/v2-86b0be06a1bf2984fcb5f40162079a9b_720w.jpg)
创建wave:
![](https://pic1.zhimg.com/80/v2-067d68ab09d7b6da7d0fd1af59cf1260_720w.jpg)
验证wave,稍等片刻如果状态变为Passed,则验证通过:
![](https://pic3.zhimg.com/80/v2-16d9562ad58497c578b52857fd1d39de_720w.jpg)
验证成功好才可以创建新作业:
![](https://pic2.zhimg.com/80/v2-dff479ca1a4a2f74e678acbfff2650d9_720w.jpg)
![](https://pic3.zhimg.com/80/v2-4dec111d5329780a40cdbc12e43be146_720w.jpg)
点击上图“Start”,迁移就会进行,点击监控可以看到进度(约40分钟):
![](https://pic4.zhimg.com/80/v2-a0c6dd0cda88cca9f0471e19b8ca0b77_720w.jpg)
![](https://pic2.zhimg.com/80/v2-228a47af50d94643b8baa38887d46f71_720w.jpg)
![](https://pic3.zhimg.com/80/v2-dda7ad8df0c1489ccdfa51ad678a3e36_720w.jpg)
![](https://pic2.zhimg.com/80/v2-17890f8afa365c403f7615b312f94015_720w.jpg)
![](https://pic2.zhimg.com/80/v2-3977d55d700abcf7589624b182a6d6e1_720w.jpg)
迁移成功后,回到GCP控制台找到实例,修改实例的外部地址以及开放防火墙端口:
![](https://pic2.zhimg.com/80/v2-6292a2821dd5f54a6fc05cbce0431dcd_720w.jpg)
完成配置后即可用远程连接工具登录外部地址(Linux也类似)。
以上为全部的迁移步骤,如在迁移过程中有任何问题,欢迎联系我们以获得谷歌云技术支持。
Cloud Ace 为亚洲最多据点的谷歌云高级合作伙伴,提供谷歌云、谷歌地图、谷歌Workspace、谷歌培训等服务。Cloud Ace 拥有200多位工程师,专为客户提供技术支持,24*7提供售后服务,欢迎联系我们!