using host tags AND storage tags, even if they are correctly assigned, deployments fail
- 主要语言
- Java
- 星标
- 3.1k
- 派生
- 1.4k
- 平均合并
- 6 天 19 小时
- 30 天内合并 PR
- 32
描述
> ok, when a deployment in a dedicated resource fails in general other resources will be queried to see if deployment is possible there. So the tagging problem is not specifc to the dedication (I think).
Ok, so then what would be the proper way to solve this issue? At the moment I found a working setup like this: both ssd storages, from both hosts, have the same tag, ssd, and both hdd storages have hdd. Offerings are created with storage tag. If I deploy a vm AND choose the host manually, it uses the correct storage, depending on the offering that I choose. This is ok, but I cannot find a way to have ACS choose the host automatically - if I use host tags AND storage tags, even if they are correctly assigned, all deployments fail.
_Originally posted by @tdtmusic2 in https://github.com/apache/cloudstack/discussions/11080#discussioncomment-13570015_
贡献指南
调研方向
检查 issue #11083 中关于部署和标签的讨论,以及关联的 pull request #13951 和原始讨论 #11080。当自动主机选择能够成功运行,同时遵循主机标签和存储标签(正如手动主机选择已经做到的那样)时,这项工作就完成了。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- java
- 领域
- cloud, infrastructure
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 25/100