-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(mis/portal): 集群停用功能 #1219
feat(mis/portal): 集群停用功能 #1219
Conversation
🦋 Changeset detectedLatest commit: a98768f The changes in this PR will be included in the next version bump. This PR includes changesets to release 18 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
a09515b
to
0f2d2f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
可以让测试来测试一下
apps/portal-web/src/components/errorPages/CLusterNotAvailablePage.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
功能不着急,研究一下进一步的改动
### 做了什么 增加依赖于管理系统的数据库及grpc-api接口的集群停用功能 管理员在管理系统中进行集群停用后,集群在scow中停用 停用后集群中数据不再更新,上线后账户/作业等数据如需同步需手动同步 **修改mis-web/portal-web下获取集群配置信息的方法为使用grpc api getClusterConfigsInfo, 不再在config.js下直接读取配置文件** ![image](https://github.com/PKUHPC/SCOW/assets/43978285/566de74d-da9c-4587-b7a0-e977881c3af6) ![image](https://github.com/PKUHPC/SCOW/assets/43978285/d7c3c991-5b30-4152-ab7a-c55e57d323a2) ![image](https://github.com/PKUHPC/SCOW/assets/43978285/ff19386f-41ce-4086-90c2-e621508ca1fa) ![image](https://github.com/PKUHPC/SCOW/assets/43978285/bd062972-2371-4e11-9b9b-33f2f47d9a01) ![image](https://github.com/PKUHPC/SCOW/assets/43978285/04e5bbe0-6229-4536-b1ae-e9465809f474) 如果正在访问的集群不存在或没有可以使用的集群 则页面报错或跳转无可用集群页面
做了什么
增加依赖于管理系统的数据库及grpc-api接口的集群停用功能
管理员在管理系统中进行集群停用后,集群在scow中停用
停用后集群中数据不再更新,上线后账户/作业等数据如需同步需手动同步
修改mis-web/portal-web下获取集群配置信息的方法为使用grpc api getClusterConfigsInfo, 不再在config.js下直接读取配置文件
如果正在访问的集群不存在或没有可以使用的集群
则页面报错或跳转无可用集群页面