Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 30 Apr 2015 07:05:06 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12824254.1430137127000.31992.1430377506238@Atlassian.JIRA>
In-Reply-To: <JIRA.12824254.1430137127000@Atlassian.JIRA>
References: <JIRA.12824254.1430137127000@Atlassian.JIRA>
 <JIRA.12824254.1430137127590@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-8406) Don't allow creating shared
 network offering with userdata service and VR as the provider without DHCP
 service
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521019#comment-14521019 ] 

ASF subversion and git services commented on CLOUDSTACK-8406:
-------------------------------------------------------------

Commit 4b2ce34bc9931b3fd9ea99ffc2f19b15f1606c05 in cloudstack's branch refs/heads/master from Jayapal
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4b2ce34 ]

CLOUDSTACK-8406: Fixed selecting userdata as VR with dhcp service


> Don't allow creating shared network offering with userdata service and VR as the provider without DHCP service
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8406
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8406
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.5.1
>            Reporter: Sanjeev N
>
> Don't allow creating network offering with userdata service and VR as the provider without DHCP service.
> If we create shared network offering without DHCP service and with VR as the userdata service provider then user vm will not be able to access the userdata from VR since it gets the IP address from the external dhcp server.
> VM and VR might be in a different network so VM would not be able to access VR to fetch the userdata from VR.
> So it would be better not to allow this combination while creating network offering.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)