Open rajujith opened 1 month ago
It sounds like the global setting is being used as a platform maximum allowed instead of a default value which can be over ridden by the network offering. Might be a documentation issue instead of an implementation one. It's quite confusing tho.
It sounds like the global setting is being used as a platform maximum allowed instead of a default value which can be over ridden by the network offering. Might be a documentation issue instead of an implementation one. It's quite confusing tho.
It looks like an implementation issue to me, @alexandremattioli. Ideally, the network offering value should take effect over the global value.
@alexandremattioli @rajujith , would this be something that is to be controlled by the operator (whether it may be an overide by user or domain admin, or not)?
@alexandremattioli @rajujith , would this be something that is to be controlled by the operator (whether it may be an overide by user or domain admin, or not)?
@DaanHoogland Yes operator defines the network's rate limit on the network offering but it is ignored.
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
VPC guest network offering with custom network rate defined. KVM
SUMMARY
While there is a global configuration to set the network throttling for guest networks the more specific value on the offering should take precedence and it should be applied on the VR's guest interface. Instead the the global configuration value 'network.throttling.rate' is applied ignoring the vale in the network offering.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
With a 5000 Mbps set on the network offering the VR gets 1000Mbps network rate set from the global configuration.