venkata swamybabu budumuru created CLOUDSTACK-2959:
------------------------------------------------------
Summary: [PortableIPrange] it is good show ip ranges rather
individual ip list as part of listPortableIpRanges response
Key: CLOUDSTACK-2959
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2959
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 # 673b293d75419a4b76379092db2b204cdc6160a4
Reporter: venkata swamybabu budumuru
Assignee: Murali Reddy
Fix For: 4.2.0
Steps to reproduce:
1. Have the latest CloudStack setup with at least 1 region and 1 advanced zone.
2. create the following portable IP range
start ip : 10.147.54.100
end ip : 10.147.54.103
vlan : 54
netmask : 10.147.54.1
3. fire listPortableIpRange and check for the response.
Observations :
(i) currently listPortableIpRanges shows both ranges as well as each individual
IP and it makes it little difficult to quickly find out the ip ranges.
(ii) it will be good to show only ip ranges if there is no special requirement
for listing out all the individual ips. even if it is required then adding
another flag as param will make the response simple.
Here is the snippet of listPortableIpRanges response:
count = 2
portableiprange:
id = 6bddb4af-97f3-416e-b64a-0c0211113987
endip = 10.147.54.102
gateway = 10.147.54.1
netmask = 255.255.255.0
portableipaddress:
ipaddress = 10.147.54.100
state = Free
================================================================================
ipaddress = 10.147.54.101
state = Free
================================================================================
ipaddress = 10.147.54.102
state = Free
================================================================================
regionid = 1
startip = 10.147.54.100
vlan = 54
Attaching all the required logs along with db dump to the bug.
--
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