Return-Path: <issues-return-72185-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 084A3200B54
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Thu, 14 Jul 2016 08:14:22 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 06E3B160A7C; Thu, 14 Jul 2016 06:14:22 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 765D5160A6A
	for <archive-asf-public@cust-asf.ponee.io>; Thu, 14 Jul 2016 08:14:21 +0200 (CEST)
Received: (qmail 55805 invoked by uid 500); 14 Jul 2016 06:14:20 -0000
Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cloudstack.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cloudstack.apache.org>
List-Post: <mailto:issues@cloudstack.apache.org>
List-Id: <issues.cloudstack.apache.org>
Reply-To: dev@cloudstack.apache.org
Delivered-To: mailing list issues@cloudstack.apache.org
Received: (qmail 55792 invoked by uid 500); 14 Jul 2016 06:14:20 -0000
Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org
Received: (qmail 55789 invoked by uid 99); 14 Jul 2016 06:14:20 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jul 2016 06:14:20 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 76C9B2C02A3
	for <cloudstack-issues@incubator.apache.org>; Thu, 14 Jul 2016 06:14:20 +0000 (UTC)
Date: Thu, 14 Jul 2016 06:14:20 +0000 (UTC)
From: "Priyank Parihar (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12918699.1449205237000.24727.1468476860483@Atlassian.JIRA>
In-Reply-To: <JIRA.12918699.1449205237000@Atlassian.JIRA>
References: <JIRA.12918699.1449205237000@Atlassian.JIRA> <JIRA.12918699.1449205237882@arcas>
Subject: [jira] [Assigned] (CLOUDSTACK-9104) VM naming convention in case
 vmware is used
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Thu, 14 Jul 2016 06:14:22 -0000


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-9104?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Priyank Parihar reassigned CLOUDSTACK-9104:
-------------------------------------------

    Assignee: Priyank Parihar

> VM naming convention in case vmware is used
> -------------------------------------------
>
>                 Key: CLOUDSTACK-9104
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-910=
4
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>            Reporter: Priyank Parihar
>            Assignee: Priyank Parihar
>
> ISSUE
> =3D=3D=3D=3D=3D=3D
> VM naming convention in case vmware is used.
> Description
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> User with different account cannot create VMs with the same name, which w=
as possible earlier (I am not sure in which CCP version). That time naming =
convention used was like this =E2=80=9CI-<user-id>-<Display-Name>=E2=80=9D
> Currently if vm.instancename.flag is set to true the VM name will be exac=
tly as display name given.=20



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