cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harikrishna Patnala (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-1787) [network throttling] Virtual Router Guest & Public throttling rates are not working as expected
Date Tue, 04 Jun 2013 14:07:42 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Harikrishna Patnala resolved CLOUDSTACK-1787.
---------------------------------------------

    Resolution: Invalid

This is expected to get the throttling rate from the global parameter network.throttling rate.

For DomR guest or public network first it looks into the service offering corresponding to
the DomR, if network rate is not given then it considers the global parameter value. If network
rate is mentioned in the service offering then it considers the value in service offering.

This also applies for the uservm default network.
                
> [network throttling] Virtual Router Guest & Public throttling rates are not working
as expected
> -----------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1787
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1787
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>         Environment: commit d7f9aa637ebc953928e3d601735bc01f6fcff828
> advanced zone with 1 xen cluster 
>            Reporter: venkata swamybabu budumuru
>            Assignee: Harikrishna Patnala
>             Fix For: 4.2.0
>
>         Attachments: api.log.tgz, vmops.log.tgz
>
>
> Environment info :
> Global Settings : 
> network.throttling.rate =  800 mbps (102400 kBytesps)
> vm.network.throttling.rate = 300 mbps (38400 kbps)
> service offering = host1.small2, network rate = 400 mbps (51200 kbps)
> (i) Create a network offering (in my case with name "Offering3Tag1") 
> Note : Make sure that nw_rate of above offering is set to 600 mb/s (76800 kbps)
> (ii) Create a network "network7" using the above offering i.e "Offering3Tag1"
> (iii) Create a network offering "Offering1Tag1" which is not set with any nw_rate value
manually.
> (iv) create a network "network1" using the above offering "Offering1Tag1"
> (v) deploy a VM using the above networks "network1" & "network2"
> (vi) Change the network rate for control system network offering to 700 mb/s (i.e. 89600
kbps)
> mysql> select * from network_offerings where system_only=1 and id=3\G
> *************************** 1. row ***************************
>                        id: 3
>                      name: System-Control-Network
>                      uuid: 97690306-203b-4b99-80bc-7037ed9bab9d
>               unique_name: System-Control-Network
>              display_text: System Offering for System-Control-Network
>                   nw_rate: 700
>                   mc_rate: 0
>              traffic_type: Control
>                      tags: NULL
>               system_only: 1
>              specify_vlan: 0
>       service_offering_id: NULL
>             conserve_mode: 1
>                   created: 2013-03-20 12:15:10
>                   removed: NULL
>                   default: 1
>              availability: Required
>      dedicated_lb_service: 1
> shared_source_nat_service: 0
>                  sort_key: 0
>  redundant_router_service: 0
>                     state: Enabled
>                guest_type: NULL
>        elastic_ip_service: 0
>        elastic_lb_service: 0
>         specify_ip_ranges: 0
>                    inline: 0
>             is_persistent: 0
> 1 row in set (0.00 sec)
> Observations :
> 1. Here is the snippet of qos info about Guest Instance
> [root@Rack1Pod1Host11 ~]# xe vif-list vm-name-label=i-3-14-VM params=all | grep qos
>           qos_algorithm_type ( RW): ratelimit
>         qos_algorithm_params (MRW): kbps: 51200
>     qos_supported_algorithms (SRO): 
>           qos_algorithm_type ( RW): ratelimit
>         qos_algorithm_params (MRW): kbps: 76800
>     qos_supported_algorithms (SRO): 
> 2. [root@Rack1Pod1Host11 ~]# xe vif-list vm-name-label=r-15-VM params=all| grep -i qos
>           qos_algorithm_type ( RW): ratelimit
>         qos_algorithm_params (MRW): kbps: 102400
>     qos_supported_algorithms (SRO): 
>           qos_algorithm_type ( RW): ratelimit
>         qos_algorithm_params (MRW): kbps: 89600
>     qos_supported_algorithms (SRO): 
>           qos_algorithm_type ( RW): ratelimit
>         qos_algorithm_params (MRW): kbps: 102400
>     qos_supported_algorithms (SRO): 
> 3. From the above output, it is evident that Guest's default network got "51200 kbps"
which is picked from the service offering i.e. "host1.small2" which is as expected. and the
non-default nic got 76800 kbps which is from network offering i.e. Offering3Tag1 which is
also expected.
> 4. From the above router related output, Control nic got the right qos value i.e. 89600
kbps from the control system network offering. This is expected.
> 5. but, the rest of the two router vifs i.e. public, guest got 102400 kbps as qos value
which is from the global setting network.throttling.rate. 
> Issue :
> As mentioned in observation (5), Guest and Public nics should get their qos value as
76800 kbps i.e. from the network offering "Offering3Tag1" and it should not acquire it from
global setting.
> Here is the reference to the document that talks about how throttling settings work in
cloudstack
> http://support.citrix.com/article/CTX132019

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message