cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-1862) [Multiple IPs Per Nic] Add secondary ip info to the list portForwardiingRules
Date Tue, 23 Jul 2013 07:22:48 GMT

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

venkata swamybabu budumuru closed CLOUDSTACK-1862.
--------------------------------------------------


Have verified it on the latest build. Now the listPFRules API includes a field called vmguest
ip as mentioend below.

_	1374563431129
command	removeIpFromNic
id	5d07c169-3533-43ad-8b0a-e31e433781a2
response	json
sessionkey	Q181Lp2zuNhGRfutwWP3Jjer0Hg=
                
> [Multiple IPs Per Nic] Add secondary ip info to the list portForwardiingRules
> -----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1862
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1862
>             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 id # 94de31ebada689a766809e0b73faf567a079c79a
> - Advanced Zone 
>            Reporter: venkata swamybabu budumuru
>            Assignee: Jayapal Reddy
>             Fix For: 4.2.0
>
>
> Steps to reproduce :
> 1. Have latest master build with advanced zone having at least 1 xen cluster
> 2. Have at least one VM nic with secondary ip
> 3. create a PortForwarding Rule and verify listPortForwardingRules 
> Observations :
> > list portforwardingrules
> count = 1
> portforwardingrule:
> id = 65a71718-ec8b-4904-9627-4234d7f6e0cc
> cidrlist =
> ipaddress = 10.147.44.66
> ipaddressid = 60c40ec1-51fd-4b2a-8ae4-52280c06383e
> privateendport = 22
> privateport = 22
> protocol = tcp
> publicendport = 22
> publicport = 22
> state = Active
> tags:
> virtualmachinedisplayname = VM2
> virtualmachineid = 4a1cca0f-e564-4610-9734-b5c7c13de1c2
> virtualmachinename = VM2
> (i) output doesn't contain any info about the guest ip the PF is mapped to.
> Expected Result :
> (i) It will be easy for end user to find out which PF rules maps to which guest ip. without
this, it is difficult for end user to find out this info once the PF is created.

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