Repository navigation
Conversation
- Network Throttling: update the precedence table and text so a user instance's compute offering rate applies to every NIC, and router guest NICs use the router system offering first - Add "Throttling the Public Gateway of a VPC": VPC offering public network rate, vpc.public.network.throttling.rate fallback, refresh on restart with cleanup, migrateVPC, redundant VPC and upgrade notes - Add VPC offering and VPC details screenshots - Note the new public rate in the VPC offering and restart VPC sections - Add vpc.public.network.throttling.rate to the zone settings table
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Contradictory rate-fallback guidance can direct administrators to configure the wrong setting.
Review effort: Balanced
Findings: 2
Open (2)
What changed in this PR
Documents CloudStack 24.0 network throttling changes, including VPC public gateway limits and updated instance/router rate precedence.
Changes:
- Updates rate precedence and fallback guidance.
- Adds VPC public gateway configuration, screenshots, restart behavior, and upgrade notes.
- Links VPC administration guidance and documents the zone-level setting.
| File | Description |
|---|---|
| source/installguide/configuration.rst | Adds the VPC public throttling setting. |
| source/adminguide/service_offerings.rst | Explains updated precedence and VPC gateway throttling. |
| source/adminguide/networking/virtual_private_cloud_config.rst | Links throttling guidance and explains cleanup requirements. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
- Separate the NULL fallback for instances (vm.network.throttling.rate) from router guest networks (system offering, guest network offering, network.throttling.rate) - Fix the VMware egress paragraph: an unset compute offering rate falls back to vm.network.throttling.rate, not the network offering - Upgrade note: running instances and routers keep their backfilled limits and adopt the new rules when next started; existing VPCs are reported as unlimited while their routers keep the previous limit until a restart with cleanup - Note that the VPC detail is refreshed only on restart with cleanup, while a router restarted by other means may pick up a new global value - Remove an unused label and use Mbps in the VPC public rate steps
|
@blueorangutan docbuild |
|
@sudo87 a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
|
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/687. (QA-JID 549) |
|
@blueorangutan docbuild |
|
@sudo87 a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
|
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/687. (QA-JID 550) |
- Upgrade note: the new precedence applies to existing instances when stopped and started and to routers when recreated with cleanup; a restart without cleanup keeps the router NIC rates; rates can go up or down - Drop the claim that existing VPC routers keep a previous public limit and the stop/start wording for the router public NIC
- Replace the long upgrade note with a "Network Rates After Upgrading" subsection: existing rates are kept, new rules apply to existing instances and routers when they are next started - Note that the rate shown for a NIC is not read from the hypervisor - Shorten the paragraph on when a VPC's public rate is updated
|
@blueorangutan docbuild |
|
@sudo87 a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
|
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/687. (QA-JID 551) |
|
thank you @rajujith for the review. |
Doc PR for this apache/cloudstack#13325
📚 Documentation preview 📚: https://cloudstack-documentation--687.org.readthedocs.build/en/687/