Skip to content
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

add doc of adjust-policy/cancellation-policy/renew #314

Merged
merged 4 commits into from
Jul 1, 2024

Conversation

yangj1211
Copy link
Collaborator

@georgemartin72
Copy link

Adding clear documentation for policies is crucial for transparency My NSFAS Login.

Signed-off-by: yangj1211 <[email protected]>
@@ -0,0 +1,21 @@
# 变配说明

当现有的数据库实例配置无法满足业务需求或存在资源浪费时,用户可以对实例进行细致的配置变更。包括增加或减少节点规格和节点数以应对数据量的增长或查询负载的变化,调整内存分配以优化缓存效率,修改存储设置以适应数据存储需求,更新安全策略以增强数据保护,以及实施高可用性措施以减少系统停机时间。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

当标准实例的配置相对于业务负载需求不足或过剩时,您可以通过更改计算节点的个数和大小来调整至更适合的配置。


# 变配规则

用户可以通过点击实例页面上的“变配”按钮来调整配置。提交后实例会显示“变配中”的标志,这通常需要几分钟的时间来完成变配。完成变配后,系统会分别生成变配前后的两个账单。变配前账单会优先扣除现金支付金额。如果产生退款,剩余金额将退回至您的账户余额。请注意,已使用的代金券不支持退还。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

开始变配时,好像就会生成账单,因为当时就要付款或退钱。而且只会生成一个账单,可以再确认下。

| ---- | ---- |
| 只提高节点规格/只加节点数/提高节点规格并加节点数 | 补交金额 = (新配置的月刊例价 - 旧配置月刊例价)/30/24×包年包月剩余时长|
| 只降低节点规格/只减节点数/降低节点规格并减节点数 |<ol><li> 实例实付现金金额 > 已消费金额:退款金额 = (订单实付现金金额 - 已消费金额) *新旧配置差比例</li><li>实例实付现金金额 <= 已消费金额(即含有代金券抵扣情况):退款金额 =0</li></ol><li>新旧配置差比例 =(原配置刊例价 - 新配置刊例价)/ 原配置刊例价</li>|
| 提高节点规格并减节点数/降低节点规格并加节点数 | 费用将根据实际使用的配置进行计算,最终收费以实际生成的账单为准。|
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这种情况也有公式,建议写成两行

@dengn dengn merged commit 42ba683 into matrixorigin:main Jul 1, 2024
1 check passed
@yangj1211 yangj1211 deleted the charge-policy branch July 9, 2024 06:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants