Automation Suite
2023.10
False
- 概述
- 要求
- 推荐:部署模板
- 手动:准备安装
- 手动:准备安装
- 步骤 1:为离线安装配置符合 OCI 的注册表
- 步骤 2:配置外部对象存储
- 步骤 3:配置 High Availability Add-on
- 步骤 4:配置 Microsoft SQL Server
- 步骤 5:配置负载均衡器
- 步骤 6:配置 DNS
- 步骤 7:配置内核和操作系统级别设置
- 步骤 8:配置磁盘
- 步骤 9:配置节点端口
- 步骤 10:应用其他设置
- 步骤 12:验证并安装所需的 RPM 包
- 步骤 13:生成 cluster_config.json
- 证书配置
- 数据库配置
- 外部对象存储配置
- 预签名 URL 配置
- 符合 OCI 的外部注册表配置
- Disaster Recovery:主动/被动和主动/主动配置
- High Availability Add-on 配置
- 特定于 Orchestrator 的配置
- Insights 特定配置
- Process Mining 特定配置
- Document Understanding 特定配置
- Automation Suite Robot 特定配置
- 监控配置
- 可选:配置代理服务器
- 可选:在多节点 HA 就绪生产集群中启用区域故障恢复
- 可选:传递自定义 resolv.conf
- 可选:提高容错能力
- install-uipath.sh 参数
- 添加具有 GPU 支持的专用代理节点
- 为 Task Mining 添加专用代理节点
- 连接 Task Mining 应用程序
- 为 Automation Suite Robot 添加专用代理节点
- 步骤 15:为离线安装配置临时 Docker 注册表
- 步骤 16:验证安装的先决条件
- 手动:执行安装
- 安装后
- 集群管理
- 管理产品
- 集群管理门户入门
- 将对象存储从持久性卷迁移到原始磁盘
- 从集群内迁移到外部 High Availability Add-on
- 在对象存储之间迁移数据
- 将集群内对象存储迁移到外部对象存储
- 在主动/被动设置中手动切换到辅助集群
- Disaster Recovery:执行安装后操作
- 将现有安装转换为多站点设置
- 升级主动/被动或主动/主动部署准则
- 备份和还原主动/被动或主动/主动部署的准则
- Redirecting traffic for the unsupported services to the primary cluster
- 监控和警示
- 迁移和升级
- 特定于产品的配置
- 最佳实践和维护
- 故障排除
Redirecting traffic for the unsupported services to the primary cluster
Linux 版 Automation Suite 安装指南
上次更新日期 2024年4月19日
Redirecting traffic for the unsupported services to the primary cluster
You can install products that are not supported in Disaster Recovery with Active/Passive and Active/Active. However, you should take the following aspects into consideration:
-
In Active/Passive deployments, you cannot use these products when the second cluster is in use or active.
-
In Active/Active deployments, the traffic for the unsupported services in the secondary cluster must always be redirected to the primary cluster. To do that, run the following script on the secondary cluster only:
services=("aifabric" "actions" "bupproxyservice" "apps" "du" "testmanager" "roboticsops" "processes" "dataservice") existingJson=$(kubectl get wasmplugin uipath-routing-policy -n istio-system -o json) for service in "${services[@]}" do exists=$(echo "$existingJson" | jq -r ".spec.pluginConfig.forward_services[] | select(.name == \"$service\")") if [ -n "$exists" ]; then echo "Service '${service}' already exists. Skipping..." continue fi kubectl patch wasmplugin uipath-routing-policy -n istio-system --type='json' -p='[{"op": "add", "path": "/spec/pluginConfig/forward_services/-", "value": {"name": "'$service'", "paths": [""]}}]' echo "Service '${service}' forwarding rule added." doneRemove services
services=("aifabric" "actions" "bupproxyservice" "apps" "du" "testmanager" "roboticsops" "processes" "dataservice") existingJson=$(kubectl get wasmplugin uipath-routing-policy -n istio-system -o json) for service in "${services[@]}" do exists=$(echo "$existingJson" | jq -r ".spec.pluginConfig.forward_services[] | select(.name == \"$service\")") if [ -n "$exists" ]; then echo "Service '${service}' already exists. Skipping..." continue fi kubectl patch wasmplugin uipath-routing-policy -n istio-system --type='json' -p='[{"op": "add", "path": "/spec/pluginConfig/forward_services/-", "value": {"name": "'$service'", "paths": [""]}}]' echo "Service '${service}' forwarding rule added." doneRemove services