Dice下部署Trantor底座服务
开始部署Trantor底座前请先完成前置准备
创建应用
在Dice的项目中新建 trantor-datastore 、 trantor-console 、 trantor-workspace 三个应用,并且在三个应用内创建 pipeline.yml 文件(文件内容一样)、 dice.yml 文件(文件内容见具体应用详情)。
!!!Trantor建议的部署结构是一个【研发态(trantor-console)】多个【运行态(trantor-workspace)】。!!!
!!!Trantor建议的部署结构是一个【研发态(trantor-console)】多个【运行态(trantor-workspace)】。!!!
!!!Trantor建议的部署结构是一个【研发态(trantor-console)】多个【运行态(trantor-workspace)】。!!!
环境与分支关系基于dice的分支规则:
开发环境:feature/develop
测试环境:develop
预发环境:relese/*
生成环境:master
- pipeline.yml
version: '1.1'stages:- stage: - git-checkout: params: depth: 1- stage: - release: params: dice_yml: ${git-checkout}/dice.yml- stage: - dice: params: time_out: 300 release_id_path: ${release}!!!以下三个应用中对应的
image请查看 底座镜像版本 !!!!!!以下三个应用中对应的
image请查看 底座镜像版本 !!!!!!以下三个应用中对应的
image请查看 底座镜像版本 !!!
trantor-datastore
新建 pipeline.yml 、dice.yml 文件。
pipeline.yml内容见上面
dice.yml内容中的镜像说明:
datastore的image对应底座镜像版本文档里的DataStore
- dice.yml
version: "2.0"services: datastore: image: "registry.cn-hangzhou.aliyuncs.com/terminus/datastore:${tag见底座镜像版本文档}" resources: cpu: 1 mem: 2048 deployments: replicas: 1 expose: - 80 ports: - 8080 health_check: exec: cmd: "curl -k http://127.0.0.1:8080/api/data/health"addons: api-gateway: plan: "api-gateway:basic" registercenter: plan: "registercenter:basic"envs: {}创建
dice.yml文件后可通过dice的可视化页面添加addon
MySQL必选
Redis部署多实例时 必选资源推荐配置:
开发环境:
datastore
cpu: 1 / mem: 2048 / replicas: 1
测试环境:
datastore
cpu: 1 / mem: 2048 / replicas: 1
预发环境:
datastore
cpu: 2 / mem: 4096 / replicas: 1
生产环境:
datastore
cpu: 4 / mem: 8192 / replicas: 4
具体资源配置可根据实际情况而定
trantor-console ( 研发态 )
新建 pipeline.yml 、dice.yml 文件。
pipeline.yml内容见上面
dice.yml内容中的镜像说明:
meta-store的image对应底座镜像版本文档里的MetaStore Develop
trantor-console的image对应底座镜像版本文档里的T-Console
- dice.yml
version: "2.0"services: meta-store: image: "registry.cn-hangzhou.aliyuncs.com/terminus/trantor-metastore:${tag见底座镜像版本文档}" ports: - 8080 resources: cpu: 1 mem: 2048 network: mode: "container" deployments: replicas: 1 expose: - 8080 health_check: http: port: 8080 path: "/actuator/health" duration: 1200 trantor-console: image: "registry.cn-hangzhou.aliyuncs.com/terminus/trantor-console:${tag见底座镜像版本文档}" ports: - 8099 resources: cpu: 0.5 mem: 1024 network: mode: "container" deployments: replicas: 1 expose: - 8099 health_check: http: port: 80 path: "/" duration: 120addons: api-gateway: plan: "api-gateway:basic" registercenter: plan: "registercenter:basic"envs: {}资源推荐配置:
开发环境:
meta-store
cpu: 1 / mem: 2048 / replicas: 1
trantor-console
cpu: 0.5 / mem: 1024 / replicas: 1
测试环境:
meta-store
cpu: 1 / mem: 2048 / replicas: 1
trantor-console
cpu: 0.5 / mem: 1024 / replicas: 1
预发环境:
meta-store
cpu: 2 / mem: 4096 / replicas: 1
trantor-console
cpu: 1 / mem: 2048 / replicas: 1
生产环境:
meta-store
cpu: 4 / mem: 8192 / replicas: 2
trantor-console
cpu: 2 / mem: 4096 / replicas: 2
trantor-workspace ( 运行态 )
新建 pipeline.yml 、dice.yml 文件。
pipeline.yml内容见上面
dice.yml内容中的镜像说明:
meta-store的image对应底座镜像版本文档里的MetaStore Runtime
trantor-portal的image对应底座镜像版本文档里的T-Workspace
- dice.yml
version: "2.0"services: meta-store: image: "registry.cn-hangzhou.aliyuncs.com/terminus/trantor-metastore:${tag见底座镜像版本文档}" ports: - 8080 resources: cpu: 1 mem: 2048 network: mode: "container" deployments: replicas: 1 expose: - 8080 health_check: http: port: 8080 path: "/actuator/health" duration: 1200 trantor-portal: image: "registry.cn-hangzhou.aliyuncs.com/terminus/trantor-workspace:${tag见底座镜像版本文档}" ports: - 8098 resources: cpu: 0.5 mem: 1024 network: mode: "container" deployments: replicas: 1 expose: - 8098 health_check: http: port: 80 path: "/" duration: 120addons: api-gateway: plan: "api-gateway:basic" registercenter: plan: "registercenter:basic"envs: {}资源推荐配置:
开发环境:
meta-store
cpu: 1 / mem: 2048 / replicas: 1
trantor-console
cpu: 0.5 / mem: 1024 / replicas: 1
测试环境:
meta-store
cpu: 1 / mem: 2048 / replicas: 1
trantor-console
cpu: 0.5 / mem: 1024 / replicas: 1
预发环境:
meta-store
cpu: 2 / mem: 4096 / replicas: 1
trantor-console
cpu: 1 / mem: 2048 / replicas: 1
生产环境:
meta-store
cpu: 4 / mem: 8192 / replicas: 2
trantor-console
cpu: 2 / mem: 4096 / replicas: 2
配置环境变量
环境变量可以再当前应用的 应用设置 / 部署中心/参数设置 / 对应环境 中进行配置

以下提供的环境变量为启动必填环境变量,其他可选环境变量见环境变量详细
!!!环境变量如果发生变更,需要重启整个应用!!!
!!!环境变量如果发生变更,需要重启整个应用!!!
!!!环境变量如果发生变更,需要重启整个应用!!!
trantor-datastore
[ { "Key": "MYSQL_DATABASE", "Value": "autumn_dev" }]
MYSQL_DATABASE根据对应环境修改后缀
trantor-console
[ { "Key": "ACL_MOCK", "Value": "true" }, { "Key": "USER_MOCK", "Value": "true" }, { "Key": "OSS_ENDPOINT", "Value": "-" }, { "Key": "OSS_REGION", "Value": "-" }, { "Key": "OSS_BUCKET", "Value": "-" }, { "Key": "OSS_AS", "Value": "-" }, { "Key": "OSS_AK", "Value": "-" }, { "Key": "OSS_ARN", "Value": "-" }, { "Key": "DS_PROJECT_ID", "Value": "trantor_console_dev" }, { "Key": "DEPLOYMENT_MODE", "Value": "STANDALOAN" }, { "Key": "TENANT_ENABLE", "Value": "true" }, { "Key": "TRANTOR_EVENT_ENABLED", "Value": "false" }, { "Key": "WORKSPACE_HIDDENS", "Value": "Bell" }, { "Key": "GATEWAY_PREFIX", "Value": "/-/trantor-console" }, { "Key": "GATEWAY_URL", "Value": "-" }, { "Key": "META_STORE_URL", "Value": "-/-/trantor-console/meta-store" }]
OSS相关信息根据实际情况配置 ( 不配置不影响启动 )
DS_PROJECT_ID根据对应环境修改后缀
GATEWAY_PREFIX由项目唯一标识加应用唯一标识组成,中间使用/连接
GATEWAY_URL可以在应用创建完成后在dice的微服务治理平台/对应项目的环境/API网关/流量入口管理/(统一域名入口)的绑定域名如果没有见下面的FAQ
META_STORE_URL由GATEWAY_URL+GATEWAY_PREFIX+meta-store组成,中间使用/连接
trantor-workspace
[ { "Key": "ACL_MOCK", "Value": "true" }, { "Key": "USER_MOCK", "Value": "true" }, { "Key": "OSS_ENDPOINT", "Value": "-" }, { "Key": "OSS_REGION", "Value": "-" }, { "Key": "OSS_BUCKET", "Value": "-" }, { "Key": "OSS_AS", "Value": "-" }, { "Key": "OSS_AK", "Value": "-" }, { "Key": "OSS_ARN", "Value": "-" }, { "Key": "DS_PROJECT_ID", "Value": "trantor_workspace_test" }, { "Key": "SLAVE_ACCESSKEY", "Value": "dev" }, { "Key": "TRANTOR_EVENT_ENABLED", "Value": "false" }, { "Key": "DEBUG", "Value": "true" }, { "Key": "GATEWAY_PREFIX", "Value": "/-/trantor-workspace" }, { "Key": "GATEWAY_URL", "Value": "-" }, { "Key": "META_STORE_URL", "Value": "-/-/trantor-workspace/meta-store" }]
OSS相关信息根据实际情况配置 ( 不配置不影响启动 )
DS_PROJECT_ID根据对应环境修改后缀
GATEWAY_PREFIX由项目唯一标识加应用唯一标识组成,中间使用/连接
GATEWAY_URL可以在应用创建完成后在dice的微服务治理平台/对应项目的环境/API网关/流量入口管理/(统一域名入口)的绑定域名如果没有见下面的FAQ
META_STORE_URL由GATEWAY_URL+GATEWAY_PREFIX+meta-store组成,中间使用/连接
启动流水线
在应用内的 流水线 选择对应分支的 默认流水线 **新建流水线**然后执行。

FAQ
**F:**微服务治理平台中没有对应环境或API网关信息。
**Q:**可以先跑流水线,Dice会自动创建 ( 创建完拿到值修改环境变量后需要重启应用 )。
