apache / apache/cloudstack

API/UI: Support custom-constrained and custom-unconstrained offerings when creating a CKS cluster

オープン
#11,545 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る
component:api component:cks component:UI no-issue-activity type:improvement
主要言語
Java
スター
3.1k
フォーク
1.4k
平均マージ
6日 19時間
マージ済み PR(30日)
32

説明

### problem

Currently, users are unable to select the custom-constrained and custom-unconstrained offerings from the UI

And also it's not even possible from the API as we are excluding the custom offerings for cks cluster

```
localcloud) 🐱 > create kubernetescluster name=test zoneid=fb0bd189-c018-4897-8a2d-7f9b59b204da hypervisor=KVM kubernetesversionid=515fb765-38f3-4ca1-bd6d-18816b64418b serviceofferingid=7ebfd3b9-1b0e-44ca-b9ec-4ebeff9df06e size=1

🙈 Error: (HTTP 530, error code 9999) Given service offering ID: Service offering {"id":13,"name":"Large Instance-unconstrained","uuid":"7ebfd3b9-1b0e-44ca-b9ec-4ebeff9df06e"}. for WORKER nodes is not suitable for the Kubernetes cluster version KubernetesSupportedVersion {"id":1,"name":"cks-csi","semanticVersion":"1.33.1","uuid":"515fb765-38f3-4ca1-bd6d-18816b64418b"} - Custom service offerings are not supported for creating clusters, service offering ID: 7ebfd3b9-1b0e-44ca-b9ec-4ebeff9df06e

(localcloud) 🐱 > create kubernetescluster name=test zoneid=fb0bd189-c018-4897-8a2d-7f9b59b204da hypervisor=KVM kubernetesversionid=515fb765-38f3-4ca1-bd6d-18816b64418b
serviceofferingid=bdf374a9-c55b-46dc-b5c1-c8056beb8d10 size=1

🙈 Error: (HTTP 530, error code 9999) Given service offering ID: Service offering {"id":14,"name":"Large-Instance-constrained","uuid":"bdf374a9-c55b-46dc-b5c1-c8056beb8d10"}. for WORKER nodes is not suitable for the Kubernetes cluster version KubernetesSupportedVersion {"id":1,"name":"cks-csi","semanticVersion":"1.33.1","uuid":"515fb765-38f3-4ca1-bd6d-18816b64418b"} - Custom service offerings are not supported for creating clusters, service offering ID: bdf374a9-c55b-46dc-b5c1-c8056beb8d10

```

### versions

ACS 4.21, 4.20.1

### The steps to reproduce the bug

1. Navigate to service offering > compute offering > create a custom-constrained and custom-unconstrained offering.

Create a custom -constrained offering od 2 cpu and 2048 ram which is the minimum requirement for a cks cluster

2. Navigate to compute > kubernetes > create cks cluster

3. The custom-constrained and custom-unconstrained are listed

Image

Image

Image

...

### What to do about it?

User should be able to select the custom-constrained and custom-unconstrained offerings for a cks cluster.

As it would be beneficial for the end user to specify the CPU and memory during CKS creation

A similar box related to deploy instance should be displayed during cks creation

Image

Image

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

まず、API と UI を通じた CKS クラスターの作成を追跡し、custom-constrained および custom-unconstrained のサービスオファリングがどこで除外されているかに注目します。レポートに記載されたカスタムオファリングで問題を再現します。完了条件は、CKS 作成フローで両方のオファリングを選択でき、API に受け入れられることです。

索引モデルが issue の本文から書いたものです。

評価

技術スタック
java
領域
api, frontend
issue の種類
バグ
難易度
4/5
見積もり時間
3〜5日
活発さ
停滞
明瞭さ
おおむね明確
初心者へのやさしさ
35/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。