[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13931973#comment-13931973
]
ASF subversion and git services commented on CLOUDSTACK-6232:
-
Commit 5685d145373ea05c7ceb152c4553953599b7369a in cloudstack's branch
refs/heads/master from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5685d14 ]
[CLOUDSTACK-6232] bridging allowed in isolated networks
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.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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13931993#comment-13931993
]
ASF subversion and git services commented on CLOUDSTACK-6232:
-
Commit f78e7ae51f55da17ed5ba239f99457ee8bc7c4d8 in cloudstack's branch
refs/heads/4.3-forward from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f78e7ae ]
[CLOUDSTACK-6232] bridging allowed in isolated networks
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.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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13932035#comment-13932035
]
Alena Prokharchyk commented on CLOUDSTACK-6232:
---
Daan, looks like we also has to change createVlanIpRange call in addition to
createNetwork, otherwise the fix would be partial. This call is executed when
the network is already created, and you want to extend its range.
Configuration ManagerImpl, public Vlan
createVlanAndPublicIpRange(CreateVlanIpRangeCmd cmd)
// If networkId is not specified, and vlan is Virtual or Direct
// Untagged, try to locate default networks
if (forVirtualNetwork) {
if (network == null) {
// find default public network in the zone
networkId =
_networkModel.getSystemNetworkByZoneAndTrafficType(zoneId,
TrafficType.Public).getId();
network = _networkModel.getNetwork(networkId);
} else if (network.getGuestType() != null ||
network.getTrafficType() != TrafficType.Public) {
throw new InvalidParameterValueException(Can't find Public
network by id= + networkId);
}
} else {
if (network == null) {
if (zone.getNetworkType() == DataCenter.NetworkType.Basic) {
networkId =
_networkModel.getExclusiveGuestNetwork(zoneId).getId();
network = _networkModel.getNetwork(networkId);
} else {
network =
_networkModel.getNetworkWithSecurityGroupEnabled(zoneId);
if (network == null) {
throw new InvalidParameterValueException(Nework id is
required for Direct vlan creation );
}
networkId = network.getId();
zoneId = network.getDataCenterId();
}
CHANGE THIS LINE BY ADDING :} else if (network.getGuestType() ==
null || network.getGuestType() == Network.GuestType.Isolated) {WITH
} else if (network.getGuestType() == null || (network.getGuestType() ==
Network.GuestType.Isolated
areServicesSupportedByNetworkOffering(ntwkOff.getId(), Service.SourceNat)))
throw new InvalidParameterValueException(Can't create direct
vlan for network id= + networkId + with type: + network.getGuestType());
}
}
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.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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13932088#comment-13932088
]
Daan Hoogland commented on CLOUDSTACK-6232:
---
Ah, that is what you meant. Let me look at it
On Wed, Mar 12, 2014 at 6:21 PM, Alena Prokharchyk (JIRA)
--
Daan
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.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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13932144#comment-13932144
]
ASF subversion and git services commented on CLOUDSTACK-6232:
-
Commit b5c8a56eeaa62cb1295993b43b11f1fb916949af in cloudstack's branch
refs/heads/master from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b5c8a56 ]
CLOUDSTACK-6232 allow expansion of ip on isolated networks as well
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.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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13932153#comment-13932153
]
ASF subversion and git services commented on CLOUDSTACK-6232:
-
Commit edf97ac86c94741ae8964b640bdfc0234929c1e4 in cloudstack's branch
refs/heads/4.3-forward from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=edf97ac ]
CLOUDSTACK-6232 allow expansion of ip on isolated networks as well
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.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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13932525#comment-13932525
]
ASF subversion and git services commented on CLOUDSTACK-6232:
-
Commit 9af90e319d3efe38c86712e3206984670f3625d7 in cloudstack's branch
refs/heads/4.3 from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9af90e3 ]
[CLOUDSTACK-6232] bridging allowed in isolated networks
(cherry picked from commit f78e7ae51f55da17ed5ba239f99457ee8bc7c4d8)
Signed-off-by: Animesh Chaturvedi anim...@apache.org
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.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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13932526#comment-13932526
]
ASF subversion and git services commented on CLOUDSTACK-6232:
-
Commit 6a6ec648099553a42f830dcd566eab2452428908 in cloudstack's branch
refs/heads/4.3 from [~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6a6ec64 ]
CLOUDSTACK-6232 allow expansion of ip on isolated networks as well
(cherry picked from commit edf97ac86c94741ae8964b640bdfc0234929c1e4)
Signed-off-by: Animesh Chaturvedi anim...@apache.org
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.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)
