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 2015/08/10 21:58:45 UTC

[jira] [Commented] (VCL-869) remove computer.vmtypeid and add something to vmprofile

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

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

Commit 1695160 from [~arkurth] in branch 'vcl/trunk'
[ https://svn.apache.org/r1695160 ]

VCL-869
Removed $vmtype_name variable from vbox.pm. It was only being used in a notify message and the corresponding DataStructure.pm value no longer exists.

> remove computer.vmtypeid and add something to vmprofile
> -------------------------------------------------------
>
>                 Key: VCL-869
>                 URL: https://issues.apache.org/jira/browse/VCL-869
>             Project: VCL
>          Issue Type: Improvement
>          Components: database, vcld (backend), web gui (frontend)
>            Reporter: Josh Thompson
>             Fix For: 2.5
>
>
> computer.vmtypeid is not being used for anything and is not exposed via the web gui. So, it should be removed. The initial intent was to know what type of hypervisor was being used on a VM. It would be more useful to have this information assigned to each vmprofile instead. So, a field needs to be added to the vmprofile for this information. It would also require computer.provisioning to be either NULL or something generic like "virtual" for VMs. Then, the provisioning engine would be determined from the vmprofile where the VM happens to be assigned at the time.



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