[
https://issues.apache.org/jira/browse/VCL-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680684#comment-14680684
]
Andy Kurth commented on VCL-869:
--------------------------------
There are no longer any references to the vmtype table in the backend code.
I'd like to help work on the design if/when this is worked on. I want to
change how the code determines which provisioning module to use. Currently,
_computer.provisioningid_ is used. This is problematic when a pool of VMs can
be assigned to different types of hosts. It's easy to assign a VM to a KVM
host which was previously assigned to a VMware host or vice versa and forget to
change the _comptuer.provisioningid_ value.
I think there should be a deterministic link between a vmhost entry and its
virtualization type (VMware, KVM, etc). No link currently exists. This could
probably be accomplished by mapping the vmhost and provisioning tables or
adding a _vmhost.provisioningid_ column.
I would not add something like this to the vmprofile table because it could
introduce an issue similar to the one regarding the _computer.provisioningid_
column if a vmprofile was assigned to both VMware and KVM (or other) hosts.
> 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)
