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