You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by to...@inf.mit.bme.hu on 2015/02/02 15:56:47 UTC

Re: Base image creation issue VCL2.4

Dear Josh,
 
Thanks for the detailed description. I create a new OSinstalltype, because I would like to avoid mixing images. (For example VCL should never try starting a vmware image on XenServer, because the automatic image conversion is currently not working like vmware - kvm pair.)
 
I think it can be a possible solution for the selection problem, if the frontend first handles the two special type of computers(bare metal/lab), and any other OSInstalltype is Virtual Machine. This does not require any modification in the database schema. 
 
Br,
Aaron Toth

-----Josh Thompson <jo...@ncsu.edu> ezt írta: ----- 
Címzett: dev@vcl.apache.org
Feladó: Josh Thompson <jo...@ncsu.edu>
Dátum: 2015/01/27 04:10du.
Tárgy: Re: Base image creation issue VCL2.4

On Wednesday, January 21, 2015 11:35:25 AM toth.aron@inf.mit.bme.hu wrote:
> Frontend issue:
> I add a new provisioning type(XenServer) to the VCL(database), but on the
> frontend I cannot select it when I add new virtual machines to VCL.
> 
> I would like to request your assitance.
> 
> Br,
> Aaron Toth

Aaron,

Thanks for reporting this.  I apologize for the delayed response.  I've been 
focusing on making the install script more robust and also creating an upgrade 
script.

The frontend needs to know what computer types (blade, lab, or virtual) a 
provisioning type relates to.  This information is only somewhat in the 
database.  So, some of it is hard coded in the web code.

Provisioning types must be mapped to OS install types using the 
provisioningOSinstalltype table.  You can probably map your XenServer 
provisioning type to the vmware OS install type (I can't remember all the 
implications of what mapping to vmware would do, but the libvirt provisioning 
type is mapped to it.  So, I think xenserver could be as well.).  If so, it 
would then be picked up by the frontend as a selection on the Manage Computers 
page.  If you need to create a new OS install type to map it to, you'd need to 
modify getProvisioningTypes in utils.php by adding another if conditional in 
the while loop - something like:

if($row['type'] == 'xenserver')
   $types['virtualmachine'][$row['id']] = $row['prettyname'];

Another option is to get all of the information in the database.  However, I'd 
prefer not to do any database schema modifications this close to trying to get 
the 2.4 release out.

Josh
- -- 
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University

Re: Base image creation issue VCL2.4

Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aaron,

This is a good idea.  Ideally, the info should all be in the database so that 
the code doesn't have to be extended when a type is added.  However, at least 
having it default to the most popular type (virtual) is a good way to go.  I 
just did a commit that does this.

Thanks,
Josh

On Monday, February 02, 2015 3:56:47 PM toth.aron@inf.mit.bme.hu wrote:
> Dear Josh,
> 
> Thanks for the detailed description. I create a new OSinstalltype, because I
> would like to avoid mixing images. (For example VCL should never try
> starting a vmware image on XenServer, because the automatic image
> conversion is currently not working like vmware - kvm pair.)
> 
> I think it can be a possible solution for the selection problem, if the
> frontend first handles the two special type of computers(bare metal/lab),
> and any other OSInstalltype is Virtual Machine. This does not require any
> modification in the database schema.
> 
> Br,
> Aaron Toth
> 
> -----Josh Thompson <jo...@ncsu.edu> ezt írta: -----
> Címzett: dev@vcl.apache.org
> Feladó: Josh Thompson <jo...@ncsu.edu>
> Dátum: 2015/01/27 04:10du.
> Tárgy: Re: Base image creation issue VCL2.4
> 
> On Wednesday, January 21, 2015 11:35:25 AM toth.aron@inf.mit.bme.hu wrote:
> > Frontend issue:
> > I add a new provisioning type(XenServer) to the VCL(database), but on the
> > frontend I cannot select it when I add new virtual machines to VCL.
> > 
> > I would like to request your assitance.
> > 
> > Br,
> > Aaron Toth
> 
> Aaron,
> 
> Thanks for reporting this.  I apologize for the delayed response.  I've been
> focusing on making the install script more robust and also creating an
> upgrade script.
> 
> The frontend needs to know what computer types (blade, lab, or virtual) a
> provisioning type relates to.  This information is only somewhat in the
> database.  So, some of it is hard coded in the web code.
> 
> Provisioning types must be mapped to OS install types using the
> provisioningOSinstalltype table.  You can probably map your XenServer
> provisioning type to the vmware OS install type (I can't remember all the
> implications of what mapping to vmware would do, but the libvirt
> provisioning type is mapped to it.  So, I think xenserver could be as
> well.).  If so, it would then be picked up by the frontend as a selection
> on the Manage Computers page.  If you need to create a new OS install type
> to map it to, you'd need to modify getProvisioningTypes in utils.php by
> adding another if conditional in the while loop - something like:
> 
> if($row['type'] == 'xenserver')
>    $types['virtualmachine'][$row['id']] = $row['prettyname'];
> 
> Another option is to get all of the information in the database.  However,
> I'd prefer not to do any database schema modifications this close to trying
> to get the 2.4 release out.
> 
> Josh
> - --
> - -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
- -- 
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlTQ3a0ACgkQV/LQcNdtPQMFmACfVBxSWbYxz3mjwl6k3jbong+6
roAAni9gFOoLF61J0kMdsD3utjTRHP7c
=CS8M
-----END PGP SIGNATURE-----