You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/03/13 18:42:12 UTC
[jira] [Resolved] (CLOUDSTACK-108) VM should not be allowed to be
deployed on two Isolated Networks of an Account that were created from
DefaultNetworkOfferingwithSourceNATService.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alena Prokharchyk resolved CLOUDSTACK-108.
------------------------------------------
Resolution: Won't Fix
After talking to Alex Huang, resolving the bug as Wontfix (by design). CloudStack can't put the restriction User Networks' combinations used for VM Deployment, its up to the end user/domain admin. What we should do (and we do it already), we validate the network itself for conflicting IPs, invalid IPs/Vlans. User/Admin should make a decision himself whether the provided network combination would be valid for his vms.
> VM should not be allowed to be deployed on two Isolated Networks of an Account that were created from DefaultNetworkOfferingwithSourceNATService.
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-108
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-108
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: pre-4.0.0
> Reporter: Chandan Purushothama
> Assignee: Alena Prokharchyk
> Priority: Critical
> Fix For: 4.1.0
>
>
> ==================
> Steps to Reproduce:
> ==================
> 1. As a Regular User Account, Create two isolated guest networks using the "DefaultNetworkOfferingwithSourceNATService"
> 2. Deploy a VM on the two Isolated Networks.
> ============================================
> Observations on the User VM on Multiple Isolated Networks:
> ============================================
> [root@atoms-regnet-vm-2 ~]# ifconfig
> eth0 Link encap:Ethernet HWaddr 02:00:11:00:00:01
> inet addr:10.1.1.139 Bcast:10.1.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:9 errors:0 dropped:0 overruns:0 frame:0
> TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1397 (1.3 KiB) TX bytes:1337 (1.3 KiB)
> eth1 Link encap:Ethernet HWaddr 02:00:3B:18:00:07
> inet addr:10.1.1.42 Bcast:10.1.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:724 (724.0 b) TX bytes:768 (768.0 b)
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
> [root@atoms-regnet-vm-2 ~]# ip route
> 10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.139
> 10.1.1.0/24 dev eth1 proto kernel scope link src 10.1.1.42
> 169.254.0.0/16 dev eth1 scope link
> default via 10.1.1.1 dev eth1
> [root@atoms-regnet-vm-2 ~]#
> ==========================================
> User VM was deployed on the two networks given below:
> ==========================================
> mysql> select * from networks where id in (204,209) \G
> *************************** 1. row ***************************
> id: 204
> name: TestNetwork-atoms
> uuid: 6ebeed0b-7de9-4d7c-a00e-03b6ec134bd9
> display_text: TestNetwork-atoms
> traffic_type: Guest
> broadcast_domain_type: Vlan
> broadcast_uri: vlan://2487
> gateway: 10.1.1.1
> cidr: 10.1.1.0/24
> mode: Dhcp
> network_offering_id: 8
> physical_network_id: 200
> data_center_id: 1
> guru_name: ExternalGuestNetworkGuru
> state: Implemented
> related: 204
> domain_id: 1
> account_id: 3
> dns1: 72.52.126.11
> dns2: 72.52.126.12
> guru_data: NULL
> set_fields: 0
> acl_type: Account
> network_domain: atoms.lab.vmops.com
> reservation_id: 19899f50-8ed0-4280-8299-64be67b7127e
> guest_type: Isolated
> restart_required: 0
> created: 2012-09-12 00:59:37
> removed: NULL
> specify_ip_ranges: 0
> vpc_id: NULL
> *************************** 2. row ***************************
> id: 209
> name: TestNetwork-mol-atoms
> uuid: f79a9fdc-082c-46d2-8c20-83cd1f166cc9
> display_text: TestNetwork-mol-atoms
> traffic_type: Guest
> broadcast_domain_type: Vlan
> broadcast_uri: vlan://2483
> gateway: 10.1.1.1
> cidr: 10.1.1.0/24
> mode: Dhcp
> network_offering_id: 8
> physical_network_id: 200
> data_center_id: 1
> guru_name: ExternalGuestNetworkGuru
> state: Implemented
> related: 209
> domain_id: 1
> account_id: 3
> dns1: NULL
> dns2: NULL
> guru_data: NULL
> set_fields: 0
> acl_type: Account
> network_domain: molecules.lab.vmops.com
> reservation_id: 7f336007-8936-4223-84a6-79e4fb115a9e
> guest_type: Isolated
> restart_required: 0
> created: 2012-09-14 22:10:31
> removed: NULL
> specify_ip_ranges: 0
> vpc_id: NULL
> 2 rows in set (0.00 sec)
> mysql>
> =========
> Git Info:
> =========
> Git Revision: 03df2fa9dd45c938f72cd1866044b09d1b0cc978
> Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
--
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