You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/09/30 20:09:35 UTC

[jira] [Commented] (VCL-636) Allow vCenter folder to be specified in VM profile

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

ASF subversion and git services commented on VCL-636:
-----------------------------------------------------

Commit 1628507 from [~jfthomps] in branch 'vcl/trunk'
[ https://svn.apache.org/r1628507 ]

VCL-174 - NAT - support for sites that have small IP address ranges
VCL-706 - Allow a Connect Method to Specify a Port Range or Port List
VCL-170 - option to power off blades after reservation - new reload module
VCL-636 - Allow vCenter folder to be specified in VM profile
VCL-758 - VCL timings - make various timings to be variables and edited by admin

update-vcl.sql:
-modified DropExistingConstraints, DropExistingIndices, AddUniqueIndex, Add2ColUniqueIndexIfNotExist, and Add3ColUniqueIndexIfNotExist: updated length of several CHAR fields in stored procedures; there were some problems with names getting truncated
-added populateConnectMethodPort - populates connectmethodport, drops connectmethod.port and connectmethod.protocol
-changed ALTER TABLE for computer.predictivemoduleid to AddColumnIfNotExists 
-added connectmethodport table
-added DropColumnIfExists for imagemeta.usergroupid
-added DropColumnIfExists for managementnode.predictivemoduleid
-added nathost table
-added natlog table
-added natmap table
-added natport table
-added DropColumnIfExists for vmhost.vmkernalnic
-added DropColumnIfExists for vmhost.vmwaredisk
-added AddColumnIfNotExists for vmprofile.folderpath
-added 'INSERT IGNORE INTO nathost' to populate nathost table with entries from managementnode table
-added INSERT IGNORE's for connectmethodport
-added INSERT IGNORE's for 'Site Configuration...' entries for usergroupprivtype table

vcl.sql:
-moved managementnode.predictivemoduleid to end of table
-removed connectmethod.port and connectmethod.protocol
-added connectmethodport table
-added nathost table
-added natlog table
-added natmap table
-added natport table
-removed port values from INSERTs for connectmethod table
-added INSERTs for 'Site Configuration...' entries for usergroupprivtype table

> Allow vCenter folder to be specified in VM profile
> --------------------------------------------------
>
>                 Key: VCL-636
>                 URL: https://issues.apache.org/jira/browse/VCL-636
>             Project: VCL
>          Issue Type: Improvement
>          Components: vcld (backend)
>    Affects Versions: 2.3
>            Reporter: Andy Kurth
>            Assignee: Andy Kurth
>            Priority: Minor
>             Fix For: 2.4
>
>
> There is no way to specify which vCenter folder VMs get created in.  This is different than the resource path.  This functionality is desired if VMs need to be created in a certain folder.  The code currently creates VMs in the first folder the API returns.  The vCenter user may not have permission to create VMs in this folder.



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