cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saksham Srivastava (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-1647) IP Reservation should not happen if the guest-vm cidr and network cidr is not same but their start ip and end ip are same.
Date Wed, 24 Apr 2013 05:33:16 GMT

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

Saksham Srivastava updated CLOUDSTACK-1647:
-------------------------------------------

    Status: Ready To Review  (was: In Progress)
    
> IP Reservation should not happen if the guest-vm cidr and network cidr is not same but
their start ip and end ip are same.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1647
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1647
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.2.0
>            Reporter: Abhinav Roy
>            Assignee: Saksham Srivastava
>             Fix For: 4.2.0
>
>
> Steps :-
> ======================
> 1. Create a guest network with Netscaler offering . Once the network is created you will
find the CIDR as something like 10.0.144.0/20.
> 2. Now implement the network and implement ip reservation by passing guestvmcidr as 10.0.151.0/20.
> Observation :-
> =====================
> The set of ips which come under the cidr 10.0.144.0/20
> Address:   10.0.144.0            00001010.00000000.1001 0000.00000000
> Netmask:   255.255.240.0 = 20    11111111.11111111.1111 0000.00000000
> Wildcard:  0.0.15.255            00000000.00000000.0000 1111.11111111
> =>
> Network:   10.0.144.0/20         00001010.00000000.1001 0000.00000000 (Class A)
> Broadcast: 10.0.159.255          00001010.00000000.1001 1111.11111111
> HostMin:   10.0.144.1            00001010.00000000.1001 0000.00000001
> HostMax:   10.0.159.254          00001010.00000000.1001 1111.11111110
> Hosts/Net: 4094                  (Private Internet)
> is same as the set of ips which come under the cidr 10.0.151.0/20
> Address:   10.0.151.0            00001010.00000000.1001 0111.00000000
> Netmask:   255.255.240.0 = 20    11111111.11111111.1111 0000.00000000
> Wildcard:  0.0.15.255            00000000.00000000.0000 1111.11111111
> =>
> Network:   10.0.144.0/20         00001010.00000000.1001 0000.00000000 (Class A)
> Broadcast: 10.0.159.255          00001010.00000000.1001 1111.11111111
> HostMin:   10.0.144.1            00001010.00000000.1001 0000.00000001
> HostMax:   10.0.159.254          00001010.00000000.1001 1111.11111110
> Hosts/Net: 4094                  (Private Internet)
> ----------------------------------
> Expected behaviour :-
> =================================
> In cases like these where the start ip and end ip of guest vm cidr and network cidr are
same, the reservation procedure should not go through and user should get a message mentioning
that.

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