You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Daan Hoogland (JIRA)" <ji...@apache.org> on 2014/04/23 14:08:16 UTC

[jira] [Closed] (CLOUDSTACK-6232) isolated network can no longer reserve ip range

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

Daan Hoogland closed CLOUDSTACK-6232.
-------------------------------------

    Resolution: Fixed

> isolated network can no longer reserve ip range
> -----------------------------------------------
>
>                 Key: CLOUDSTACK-6232
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6232
>             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, 4.3.0, 4.4.0
>            Reporter: Daan Hoogland
>            Assignee: Daan Hoogland
>            Priority: Blocker
>             Fix For: 4.3.0, 4.4.0
>
>
> We found a functionality that we use once in a while no longer is permitted in 4.2.1. It seems in line with the philosophy of cloudstack but is hurting our operation. In 4.1.1 we could add a bridged network with the following network offering:
> cno.traffictype = "GUEST"
> cno.guestiptype = "Isolated"
> cno.specifyipranges = True
> cno.specifyvlan = False
> cno.serviceproviderlist = [ { "service": "Connectivity", "provider": "NiciraNvp"},
>                             { "service": "UserData", "provider": "VirtualRouter"},
>                             { "service": "Dhcp", "provider": "VirtualRouter"} ]



--
This message was sent by Atlassian JIRA
(v6.2#6252)