Hi Vivek, Thank you for your response. I understand the scenarios you have explained but the issue I face right now is that portgroup for user VMs is not updated when network offering (with network rate difference) for that network is changed from ACS. I tried to show that here, https://youtu.be/Kdaad9c1Fq4
I've also gone through the code and on network offering change, currently ACS just stops and destroys the running VR, creates a new portgroup (for new network rate) and starts new VR on that portgroup. And user VMs continue running on the existing portgroup. Similarly, for different NICs of the VM, it can have different network rate depending on default and non-default NIC. eg: VM, v1 is created with a compute offering having network rate, 350Mbps It has three networks: n1 with network offering having network rate 400Mbps (default NIC) n2 with network offering having network rate 500Mbps n3 with network offering having no rate specified, defaulted to "network.throttling.rate" 200Mbps. "vm.network.throttling.rate" is set to 375Mbps Now, three nics of the VM will have portgroups with following network rates: NIC1 (default) - 350Mbps (taken from compute offering) NIC2 - 500Mbps (taken from n/w offering) NIC3 - 200Mbps(taken from n/w offering) Therefore, my point is both network rate from compute offering and value of vm.network.throttling.rate doesn't affect all the NICs of the VM and are honored just by the default NIC. Regards, Abhishek ________________________________ From: Vivek Kumar <vivek.ku...@indiqus.com.INVALID> Sent: 26 July 2021 15:32 To: CloudStack Users Mailing list <users@cloudstack.apache.org> Cc: d...@cloudstack.apache.org <d...@cloudstack.apache.org> Subject: Re: [DISCUSS] VMware network rate for network and VMs Hello Abhishek, Everything is useful and it completely depends on your requirements..! * Is having VM-level (using compute offering and global setting for VMs) useful? Having a higher network rate for VMs and a lower network rate for VRs(network) will make it useless. Ans - Yes definitely it's useful, so consider a scenerio where you want to provide a higher speed of data transfer between VMs in same network ( Guest traffic ) but lower speed for public traffic or may be on the different network. * Should there be a single portgroup in vCenter based on the network rate of VRs/network especially in the case when the network rate for VRs is lower? Ans - ACS create separate port group for each config, single port groups can't controller multiple QoS. So let's suppose if you create a VM with 500 Mbps network rate, ACS will create a port group and will put 500Mbps in network rate, so if you create other VMs under the same network and same compute offering it will out under the same, but the moment you change your network offering i.e 200 Mbps then it will create a separate port group with 200 Mbps network rate and will attach same to the VM. * Even while using different network rates, should there be consistency across different NICs of user VMs? Currently, compute offering and global setting only affects the default NIC of the user VMs. Ans- As I said, it create separate port group as per the network rate and VLAN. Regards Vivek Kumar On Mon, 26 Jul, 2021, 15:04 Abhishek Kumar, <abhishek.ku...@shapeblue.com> wrote: > Hi all, > > I've been working on fixing/refactoring VMware portgroup reconfigure on > network offering change, https://github.com/apache/cloudstack/pull/5181 > While working on it I found different portgroups on the same VLAN can be > used based on the different network rates used in the network offering of > the network and compute offering of the user VMs. Below are my findings: > > * Network offerings will control network rate only for VR(s) and > non-default NICs of the user VMs. > * Default network rate for VRs and non-default NICs of the user VMs > can be controlled by global setting, "network.throttling.rate". > > * For the default NIC of user VMs, the network rate is controlled by > the compute offerings of the VM. > > * For the default NIC of user VMs, the default network rate can be > controlled using the global setting,"vm.network.throttling.rate". > > So now my queries are: > > * Is having VM-level (using compute offering and global setting for > VMs) useful? Having a higher network rate for VMs and a lower network rate > for VRs(network) will make it useless. > * Should there be a single portgroup in vCenter based on the network > rate of VRs/network especially in the case when the network rate for VRs is > lower? > * Even while using different network rates, should there be > consistency across different NICs of user VMs? Currently, compute offering > and global setting only affects the default NIC of the user VMs. > > Please share your thoughts and ideas. It will be interesting to know how > others configure network throttling for networks and VMs. > > Regards, > Abhishek > > > > >
