cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kishan Kavala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4177) F5-SRX-Inline: User is charged with more usages charges in case of F5-SRX-Inline mode
Date Thu, 08 Aug 2013 06:57:47 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733213#comment-13733213
] 

Kishan Kavala commented on CLOUDSTACK-4177:
-------------------------------------------

This is as per design in earlier releases. The stats are reported separately for LB and FW
in inline mode also. Users will still have the flexibility to pick only one as per his requirement.
We can revisit the design in next release
                
> F5-SRX-Inline: User is charged with more usages charges in case of F5-SRX-Inline mode
> -------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4177
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4177
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Kishan Kavala
>             Fix For: Future
>
>
> F5-SRX-Inline: current_bytes_sent is not updated in user_statistics table in case of
LB
> Steps to Reproduce:
> ===============
> Bringup Advanced zone setup with at-least
> 1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB with
"Share" LB Isolation mode and "Inline" mode and rest of the services are provided by VR.
> 2. Add SRX device
> 3. Add F5 device 
> 4.Deploy couple of guest vms using above NO
> 5.Acquire one public IP address and configure LB and assign both the guest vms created
at step4 to it.
> 6.Open firewall ports to allow the traffic
> 7.Generate some traffic using public IP address acquired.
> 8.Wait for the ExternalNetworkUsageCmd to execute , ExternalNetworkUsageAnswer will be
received. Verify the stats present in the usage answer received and stats added to user_statistics
table.
> Observations:
> ===========
> Following is the usage answer received from F5 device:
> 2012-12-10 15:12:33,318 DEBUG [agent.transport.Request] (DirectAgent-256:null) Seq 5-434569246:
Processing:  { Ans: , MgmtId: 6896543072287, via: 5, Ver: v1, Flags: 10, [{"ExternalNetworkResourceUsageAnswer":{"ipBytes":{"10.147.52.236":[2845,4458],"10.0.144.174":[986,864]},"guestVlanBytes":{},"result":true,"wait":0}}]
}
> 10.0.144.174 is the guest IP selected on configured for LB on F5.
> mysql> select * from user_statistics where device_type="ExternalLoadBalancer";
> +----+----------------+------------+-------------------+-----------+----------------------+------------+--------------------+----------------+------------------------+--------------------+--------------------+----------------+
> | id | data_center_id | account_id | public_ip_address | device_id | device_type    
     | network_id | net_bytes_received | net_bytes_sent | current_bytes_received | current_bytes_sent
| agg_bytes_received | agg_bytes_sent |
> +----+----------------+------------+-------------------+-----------+----------------------+------------+--------------------+----------------+------------------------+--------------------+--------------------+----------------+
> |  3 |              1 |          2 | 10.147.48.6       |         5 | ExternalLoadBalancer
|        204 |                  0 |              0 |                    864 |            
     0 |                  0 |              0 |
> +----+----------------+------------+-------------------+-----------+----------------------+------------+--------------------+----------------+------------------------+--------------------+--------------------+----------------+
> 1 row in set (0.00 sec)
> Above table shows current_bytes-received as 864 and current_bytes_sent as 0 whereas usage
answer shows both "10.0.144.174":[986,864]

--
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