October 23, 2019, Rainbond released 5.1.8 version, this version of the update brings support for multiple IP gateway applications, the new features and fixes some BUG support for third-party components such as domain instance.
-
Rainbond: support enterprise application development, architecture, delivery and operation and maintenance of the whole process, by "non-invasive" seamless enterprise application architecture, the underlying resource can dock and manage IaaS, virtual machines and physical servers. What Rainbond that?
-
Release version: 5.1.8
-
Version update: Recommended
-
Updated range: application gateway, third-party components
Application gateway supports multiple IP
Application Gateway is? The only entrance into the external flow ?? tenant space application components, provide HTTP, HTTPs routing, TCP / UDP services, load balancing, advanced routing (A / B test, gray release) and other functions.
5.1.8 In the past, all TCP / UDP class strategy binding IP:PORTis 0.0.0.0:portsuch a port can only be used for a program. And multiple gateway node configuration is fully equivalent to port our server is limited (maximum 65535), thus bringing the maximum number of rules. In the current version we introduce a second variable IP address, all dynamic gateway node report available IP addresses for users to choose the current node, so as to bring the following capabilities:
-
Internal and external network isolation: internal and external network gateway node in a general point of integration, the south face of the network within the network, to the north face of the network outside the network. Presented by a different IP address, selecting a different IP address is formed outside the network isolation characteristics.
-
Gateway orientation: the need for a separate access entry for some users some service scenarios, such as a particular access network specific tenants or the like.
-
Cross-team communication: default is not direct communication between team services in the case, but it can communicate transit through the application gateway.
-
Virtual IP support: Virtual IP is changed, may migrate across multiple gateway service, supports directional binding virtual IP ports are flexible solution.
Examples of third-party components support domain name
Rainbond run outside the cluster, run from Rainbond lifecycle management, and on the network can communicate with components Rainbond cluster called third-party components. For example .net services, MySQL services running alone, or runs on Windows servers.
In the cloud computing environment, the various cloud service providers have introduced a number of cloud services, such as: Ali cloud 云数据库 RDS MySQL 版, 云数据库 Redis 版, 云数据库 MongoDB 版and Amazon Elasticsearch Servicethese cloud services provided by public network connection address is. 域名.
In order to facilitate the user to address instances 域名of third-party components added to Rainbond in, in this iteration, the third-party component on the basis of IP-only instance on the increase 域名实例. Rainbond ServiceMesh layer can be dynamically loaded resolve domain names and mailing address, third-party component health monitoring also adds support for domain names.
Other improvements and repair BUG
-
Application support with plug-in backup and recovery
-
Specification Product Description abstract # 266
-
Optimization of network failure showcase cloud application market pages offline mode.
-
When you create or update applications, there is the probability can not click on the "View Log" # 214
-
Multi-instance assembly-line volume reduction, component status kept into the startup # 460
-
Once bound custom domain name, modify the gateway policy options in its configuration, it will be considered illegal domain name, modification # 461
-
Application sharing services do not take effect after the other storage settings # 456
-
5.1.7 When creating the application could not be saved correctly ARG parameter # 453
-
Use svn created from a source platform to identify a path error # 444
-
The environment variable named testing question # 391
-
Failed to delete environment variables, operating unresponsive # 434
-
通过源码创建应用时，使用https连接，仓库地址前加空格平台会判定为ssh连接 #224
-
组件日志打印无缩进 #217
-
应用发布到应用市场时添加的应用图标无法预览 #215
-
.Netcore 语言源码构建，cmd 参数没有被传递导致运行异常 #447
安装
升级
升级要求和注意事项
-
V5.1.8版本支持从V5.1.2 - V5.1.7版本升级，如果你还未升级到V5.1.2版本，参考V5.1.x版本升级文档，先升级至V5.1.2版本：
grctl version, 例如5.1.7版本显示如下：grctl version v5.1.7-release-afa0e36-2019-09-11-00 -
升级过程会重启管理服务，因此单管理节点的集群会短暂影响控制台操作和应用访问，请选择合理的升级时间段。
-
升级过程脚本需要从集群获取节点数据，请务必在集群正常工作情况下进行升级。
-
升级前请备份控制台和数据中心数据库。
-
升级过程的主要耗时点是解压升级包和导入服务镜像的过程，根据你的服务器写入速度而定。
-
如果你手动调整过
/opt/rainbond/conf下的服务配置文件导致升级失败请到社区咨询。
下载 5.1.8 更新包
离线包镜像大小约1.3GB，需要保证当前集群磁盘可用空间至少不低于2G
# Rainbond 组件升级包 wget https://pkg.rainbond.com/offline/5.1/rainbond.images.2019-10-20-5.1.8.tgz -O /grdata/services/offline/rainbond.images.upgrade.5.1.8.tgz # 升级脚本包 wget https://pkg.rainbond.com/offline/5.1/rainbond-ansible.upgrade.5.1.8.tgz -O /grdata/services/offline/rainbond-ansible.upgrade.5.1.8.tgz
rm -rf /tmp/rainbond-ansible rm -rf /grdata/services/offline/upgrade mkdir -p /tmp/rainbond-ansible tar xf /grdata/services/offline/rainbond-ansible.upgrade.5.1.8.tgz -C /tmp/rainbond-ansible cd /tmp/rainbond-ansible/scripts/upgrade/ bash ./upgrade.sh
# 重新拉取rbd-api镜像 docker pull rainbond/rbd-api:v5.1.8-release # 修改镜像tag docker tag rainbond/rbd-api:v5.1.8-release goodrain.me/rbd-api:v5.1.8-release # 找到rbd-api配置文件/opt/rainbond/conf/master.yaml 修改-i指定的rbd-api镜像信息为goodrain.me/rbd-api:v5.1.8-release # 更新node节点上的服务 node service update # 此时重新查看组件运行使用的镜像版本应为修改后的镜像版本,查看集群状态健康，到此完成手动更新
升级如有问题，请至社区反馈
下面以rbd-api组件为例，升级后镜像版本停留在旧版本，手动更新单个组件
-
升级后以上镜像版本没有变化
升级常见问题排查
组件 版本 rbd-worker v5.1.8-release rbd-api v5.1.8-release rbd-app-ui v5.1.8-release rbd-chaos v5.1.8-release rbd-eventlog v5.1.8-release rbd-gateway v5.1.8-release rbd-monitor v5.1.8-release rbd-webcli v5.1.8-release rbd-mq v5.1.8-release -
执行
grctl cluster确定所有服务和节点运行正常 -
执行
grctl version命令 确认版本已升级到5.1.8 -
执行
dps命令查看以下组件运行使用的镜像版本是否为v5.1.8-release
平台升级完成验证
再次提醒，升级前系统比较运行正常，升级过程耗时取决于你的系统磁盘写入速度，脚本未成功之前请勿主动终止升级。
第一个管理节点执行下述命令升级平台
-