Re: The New KVM Provisioning module
This is great. I'll try to have some more useful comments soon. :) Thanks Xianqing. Aaron On Thu, Aug 4, 2011 at 11:11 AM, Xianqing Yu wrote: > Hi VCL community, > > Sorry for the typo in previous email. > > I finish the new version of KVM provision module for VCL 2.2.1. I upload the > kvm.pm code to VCL JIRE. Please take a look at my code and let me know what > do you feel about it. The link is, > > https://issues.apache.org/jira/browse/VCL-339 > > Generally, the new version of KVM module contain these features, > > 1. The module will use libvirt API to manipulate the VM on KVM hosts. The > main reason behind this is that libvirt is widely used API, many people in > the community talked about this before, and libvirt support for different > hypervisors, such as KVM, Xen, Qemu, etc.. It would be easier to port this > module to support other hypervisor in future. > > 2. An setup script can help the users to setup KVM host much easier. The > attachment named kvmsetup is the script. I tested it on Fedora 9. Basically, > user need to install Fedora 9 (or use XCAT to install Fedora 9 on blade > automatically) and run the script as the root user. > > 3. Users don't have to use qemu-ifup and mac script. "qemu-ifup" is not > needed because of using lib-virt and "mac" is now included in kvm.pm. So > kvm.pm is the only file you need to add to VCL Management Machine. > > 4. Both "-flat.vmdk" and "img" image format are supported. So now both KVM > image and VMware ESXi image (flat.vmdk) can be provisioned on KVM host. > > 5. Misc code updated. > > > Thanks, > > Xianqing > -Original Message- From: Andy Kurth > Sent: Wednesday, August 03, 2011 02:14 PM > To: vcl-dev@incubator.apache.org > Subject: Re: The New KVM Provisioning module > > $self->data->get_image_os_install_type() should do it. > > On Wed, Aug 3, 2011 at 12:47 PM, Xianqing Yu > wrote: >> >> A quick question, do you know any function call can get OSinstalltype >> content for the target image? >> >> Thanks, >> >> Xianqing Yu >> >> -- >> Graduate Research Assistant, Cyber Defense Lab >> Department of Computer Science >> North Carolina State University, Raleigh, NC >> E-mail: x...@ncsu.edu >> >> -Original Message- From: Andy Kurth >> Sent: Wednesday, August 03, 2011 09:38 AM >> To: vcl-dev@incubator.apache.org >> Subject: Re: The New KVM Provisioning module >> >> I agree that entries should be added to OSinstalltype. I wouldn't >> include the 'kvm' hypervisor name in the name since the same type may >> be used by multiple hypervisors. The 'vmware' entry can probably be >> renamed to 'vmdk' and then used by both VMware and KVM. An entry can >> be added named something like 'img' or 'vm-img'. >> >> On Tue, Aug 2, 2011 at 5:00 PM, Xianqing Yu >> wrote: >>> >>> I think it is possible to handle both types: vmdk and img. I believe that >>> in >>> my kvm provisioning code, the code need some conditions to decide if >>> image >>> file is vmdk file or img file. For example, We can add "kvm-img" and >>> "kvm-vmware" into OSinstalltype table. If one image's OS module point to >>> "kvm-img" as OSinstalltype, then the code should consider the image as >>> "img" >>> image file, and vice verse. >>> >>> Thanks, >>> >>> Xianqing Yu >>> >>> -- >>> Graduate Research Assistant, Cyber Defense Lab >>> Department of Computer Science >>> North Carolina State University, Raleigh, NC >>> E-mail: x...@ncsu.edu >>> -Original Message- From: Aaron Peeler >>> Sent: Tuesday, August 02, 2011 02:39 PM >>> To: vcl-dev@incubator.apache.org >>> Subject: Re: The New KVM Provisioning module >>> >>> The imagename is related to the OS table. It's also dependent on the >>> the OS.moduleid, OS.installtype and the computer.provisioningid. We >>> might need to add new entries for this module, which isn't a problem. >>> Just need to decide on how to name it. >>> >>> Ideally I would like to see the libvirt/kvm module handle both types - >>> vmdk and img. >>> >>> Aaron >>> >>> >>> On Mon, Aug 1, 2011 at 11:13 AM, Xianqing Yu >>> wrote: Thanks for your suggestion. I have a question about define the image name and capture function. Currently my kvm module can support vmware esxi image format (.vmdk and flat.vmdk, so I can easily support existing flat.vmdk images by KVM). But I also want it to support other image formats, such as .img. I think we may need to define the name format both in VCL database and KVM module. Let's said there is an image named CentOS5, In VMDK format, In VCL database, it should be esx-CentOS5-v0, In image library, it should be files, esx-CentOS5-v0.vmdk and esx-CentOS5-v0-flat.vmdk. My question is that what its name should be when the image file is img format? My final goal is that make KVM module can support flat.vmdk and img file at the same time. Is that possible to do that? Or I should give one of them up? Tha
Re: [VCL 2.2.1] [Power7] Problem with image reservation
interesting it's prompting, which version of linux. The code is using: echo $passwd | /usr/bin/passwd -f $account --stdin sounds this it worked in the vcl code, so should also work at the cmdline. Aaron On Thu, Aug 4, 2011 at 12:49 PM, Sunil Venkatesh wrote: > Aaron, > > I wanted to try the ssh method to change the root password, but I stopped > short since it will ask for old password before changing to a new one. > However, I planning to create and make use of user accounts instead of > looking for the root password. > > Thank you for the input. > > Regards, > Sunil > > On Aug 4, 2011, at 12:27 PM, Aaron Peeler wrote: > >> Sunil, >> >> On #2. The VCL load process is to randomize the root (and >> administrator for windows) password. It should be in the vcld.log >> file, but an easier option might be to ssh into the node and set the >> root password to something you know when using xcat's rcons to look at >> the console. >> >> Aaron >> >> >> On Tue, Aug 2, 2011 at 2:17 PM, Sunil Venkatesh wrote: >>> Hi Josh, >>> >>> So, I was able to get the VCL to capture & restore the images on to the >>> Power7 blade without any errors. The VCL web portal shows the Power7 node >>> being loaded with the captured image. I was looking for some clarification >>> with a couple of things. >>> >>> 1. The web portal shows "Selection currently not available" when I intend >>> to make a reservation on the Power7 blade that I have been working with all >>> this while. >>> >>> 2. Once the image is loaded onto the blade, I am able to login from the >>> management node without a password. However, when I am using rcons to login >>> as root on the Power7 blade, it does not accept the root password I had >>> used during the OS installation. Does the root password get reset to a >>> default one? I was checking vcl/lib/VCL/Module/OS/Linux.pm if that is the >>> case. >>> >>> Thanks & Regards, >>> Sunil >>> >>> On Jul 7, 2011, at 2:03 PM, Josh Thompson wrote: >>> This and your next question are both deeper into the backend code that I've worked with. Andy or Aaron may be able to answer your questions further. Josh >>> >>> >> >> >> >> -- >> Aaron Peeler >> Program Manager >> Virtual Computing Lab >> NC State University >> >> 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. > > -- Aaron Peeler Program Manager Virtual Computing Lab NC State University 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.
Re: [VCL 2.2.1] [Power7] Problem with image reservation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sunil, If you change the password as root (or administrator on windows), you don't need the old password to set a new one. Josh On Thursday August 04, 2011, Sunil Venkatesh wrote: > Aaron, > > I wanted to try the ssh method to change the root password, but I stopped > short since it will ask for old password before changing to a new one. > However, I planning to create and make use of user accounts instead of > looking for the root password. > > Thank you for the input. > > Regards, > Sunil > > On Aug 4, 2011, at 12:27 PM, Aaron Peeler wrote: > > Sunil, > > > > On #2. The VCL load process is to randomize the root (and > > administrator for windows) password. It should be in the vcld.log > > file, but an easier option might be to ssh into the node and set the > > root password to something you know when using xcat's rcons to look at > > the console. > > > > Aaron > > > > On Tue, Aug 2, 2011 at 2:17 PM, Sunil Venkatesh wrote: > >> Hi Josh, > >> > >> So, I was able to get the VCL to capture & restore the images on to the > >> Power7 blade without any errors. The VCL web portal shows the Power7 > >> node being loaded with the captured image. I was looking for some > >> clarification with a couple of things. > >> > >> 1. The web portal shows "Selection currently not available" when I > >> intend to make a reservation on the Power7 blade that I have been > >> working with all this while. > >> > >> 2. Once the image is loaded onto the blade, I am able to login from the > >> management node without a password. However, when I am using rcons to > >> login as root on the Power7 blade, it does not accept the root password > >> I had used during the OS installation. Does the root password get reset > >> to a default one? I was checking vcl/lib/VCL/Module/OS/Linux.pm if that > >> is the case. > >> > >> Thanks & Regards, > >> Sunil > >> > >> On Jul 7, 2011, at 2:03 PM, Josh Thompson wrote: > >>> This and your next question are both deeper into the backend code that > >>> I've worked with. Andy or Aaron may be able to answer your questions > >>> further. > >>> > >>> Josh - -- - --- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk46zvEACgkQV/LQcNdtPQMnbwCeKas+RR+36HDGEBdnVQUH/Ts8 NG8An2f92p1k9Rsi/FNrz2PrikHUJGP3 =AafE -END PGP SIGNATURE-
Re: [VCL 2.2.1] [Power7] Problem with image reservation
Aaron, I wanted to try the ssh method to change the root password, but I stopped short since it will ask for old password before changing to a new one. However, I planning to create and make use of user accounts instead of looking for the root password. Thank you for the input. Regards, Sunil On Aug 4, 2011, at 12:27 PM, Aaron Peeler wrote: > Sunil, > > On #2. The VCL load process is to randomize the root (and > administrator for windows) password. It should be in the vcld.log > file, but an easier option might be to ssh into the node and set the > root password to something you know when using xcat's rcons to look at > the console. > > Aaron > > > On Tue, Aug 2, 2011 at 2:17 PM, Sunil Venkatesh wrote: >> Hi Josh, >> >> So, I was able to get the VCL to capture & restore the images on to the >> Power7 blade without any errors. The VCL web portal shows the Power7 node >> being loaded with the captured image. I was looking for some clarification >> with a couple of things. >> >> 1. The web portal shows "Selection currently not available" when I intend to >> make a reservation on the Power7 blade that I have been working with all >> this while. >> >> 2. Once the image is loaded onto the blade, I am able to login from the >> management node without a password. However, when I am using rcons to login >> as root on the Power7 blade, it does not accept the root password I had used >> during the OS installation. Does the root password get reset to a default >> one? I was checking vcl/lib/VCL/Module/OS/Linux.pm if that is the case. >> >> Thanks & Regards, >> Sunil >> >> On Jul 7, 2011, at 2:03 PM, Josh Thompson wrote: >> >>> This and your next question are both deeper into the backend code that I've >>> worked with. Andy or Aaron may be able to answer your questions further. >>> >>> Josh >> >> > > > > -- > Aaron Peeler > Program Manager > Virtual Computing Lab > NC State University > > 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.
Re: [VCL 2.2.1] [Power7] Problem with image reservation
Sunil, On #2. The VCL load process is to randomize the root (and administrator for windows) password. It should be in the vcld.log file, but an easier option might be to ssh into the node and set the root password to something you know when using xcat's rcons to look at the console. Aaron On Tue, Aug 2, 2011 at 2:17 PM, Sunil Venkatesh wrote: > Hi Josh, > > So, I was able to get the VCL to capture & restore the images on to the > Power7 blade without any errors. The VCL web portal shows the Power7 node > being loaded with the captured image. I was looking for some clarification > with a couple of things. > > 1. The web portal shows "Selection currently not available" when I intend to > make a reservation on the Power7 blade that I have been working with all this > while. > > 2. Once the image is loaded onto the blade, I am able to login from the > management node without a password. However, when I am using rcons to login > as root on the Power7 blade, it does not accept the root password I had used > during the OS installation. Does the root password get reset to a default > one? I was checking vcl/lib/VCL/Module/OS/Linux.pm if that is the case. > > Thanks & Regards, > Sunil > > On Jul 7, 2011, at 2:03 PM, Josh Thompson wrote: > >> This and your next question are both deeper into the backend code that I've >> worked with. Andy or Aaron may be able to answer your questions further. >> >> Josh > > -- Aaron Peeler Program Manager Virtual Computing Lab NC State University 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.
Re: The New KVM Provisioning module
Hi VCL community, Sorry for the typo in previous email. I finish the new version of KVM provision module for VCL 2.2.1. I upload the kvm.pm code to VCL JIRE. Please take a look at my code and let me know what do you feel about it. The link is, https://issues.apache.org/jira/browse/VCL-339 Generally, the new version of KVM module contain these features, 1. The module will use libvirt API to manipulate the VM on KVM hosts. The main reason behind this is that libvirt is widely used API, many people in the community talked about this before, and libvirt support for different hypervisors, such as KVM, Xen, Qemu, etc.. It would be easier to port this module to support other hypervisor in future. 2. An setup script can help the users to setup KVM host much easier. The attachment named kvmsetup is the script. I tested it on Fedora 9. Basically, user need to install Fedora 9 (or use XCAT to install Fedora 9 on blade automatically) and run the script as the root user. 3. Users don't have to use qemu-ifup and mac script. "qemu-ifup" is not needed because of using lib-virt and "mac" is now included in kvm.pm. So kvm.pm is the only file you need to add to VCL Management Machine. 4. Both "-flat.vmdk" and "img" image format are supported. So now both KVM image and VMware ESXi image (flat.vmdk) can be provisioned on KVM host. 5. Misc code updated. Thanks, Xianqing -Original Message- From: Andy Kurth Sent: Wednesday, August 03, 2011 02:14 PM To: vcl-dev@incubator.apache.org Subject: Re: The New KVM Provisioning module $self->data->get_image_os_install_type() should do it. On Wed, Aug 3, 2011 at 12:47 PM, Xianqing Yu wrote: A quick question, do you know any function call can get OSinstalltype content for the target image? Thanks, Xianqing Yu -- Graduate Research Assistant, Cyber Defense Lab Department of Computer Science North Carolina State University, Raleigh, NC E-mail: x...@ncsu.edu -Original Message- From: Andy Kurth Sent: Wednesday, August 03, 2011 09:38 AM To: vcl-dev@incubator.apache.org Subject: Re: The New KVM Provisioning module I agree that entries should be added to OSinstalltype. I wouldn't include the 'kvm' hypervisor name in the name since the same type may be used by multiple hypervisors. The 'vmware' entry can probably be renamed to 'vmdk' and then used by both VMware and KVM. An entry can be added named something like 'img' or 'vm-img'. On Tue, Aug 2, 2011 at 5:00 PM, Xianqing Yu wrote: I think it is possible to handle both types: vmdk and img. I believe that in my kvm provisioning code, the code need some conditions to decide if image file is vmdk file or img file. For example, We can add "kvm-img" and "kvm-vmware" into OSinstalltype table. If one image's OS module point to "kvm-img" as OSinstalltype, then the code should consider the image as "img" image file, and vice verse. Thanks, Xianqing Yu -- Graduate Research Assistant, Cyber Defense Lab Department of Computer Science North Carolina State University, Raleigh, NC E-mail: x...@ncsu.edu -Original Message- From: Aaron Peeler Sent: Tuesday, August 02, 2011 02:39 PM To: vcl-dev@incubator.apache.org Subject: Re: The New KVM Provisioning module The imagename is related to the OS table. It's also dependent on the the OS.moduleid, OS.installtype and the computer.provisioningid. We might need to add new entries for this module, which isn't a problem. Just need to decide on how to name it. Ideally I would like to see the libvirt/kvm module handle both types - vmdk and img. Aaron On Mon, Aug 1, 2011 at 11:13 AM, Xianqing Yu wrote: Thanks for your suggestion. I have a question about define the image name and capture function. Currently my kvm module can support vmware esxi image format (.vmdk and flat.vmdk, so I can easily support existing flat.vmdk images by KVM). But I also want it to support other image formats, such as .img. I think we may need to define the name format both in VCL database and KVM module. Let's said there is an image named CentOS5, In VMDK format, In VCL database, it should be esx-CentOS5-v0, In image library, it should be files, esx-CentOS5-v0.vmdk and esx-CentOS5-v0-flat.vmdk. My question is that what its name should be when the image file is img format? My final goal is that make KVM module can support flat.vmdk and img file at the same time. Is that possible to do that? Or I should give one of them up? Thanks, Xianqing Yu -- Graduate Research Assistant, Cyber Defense Lab Department of Computer Science North Carolina State University, Raleigh, NC E-mail: x...@ncsu.edu -Original Message- From: Andy Kurth Sent: Monday, August 01, 2011 09:02 AM To: vcl-dev@incubator.apache.org Subject: Re: The New KVM Provisioning module Hi Xianqing, Sounds great. I'd like to help with this too. I like the idea about making it generic. Since libvirt supports a few different things, I think a very generic libvirt.pm module inheriting from Provisioning.pm
Re: The New KVM Provisioning module
Hi David and Andy, I finish the new version of KVM provision module for VCL 2.2.1. I upload the kvm.pm code to VCL JIRE. Please take a look at my code and let me know what do you feel about it. The link is, https://issues.apache.org/jira/browse/VCL-339 Generally, the new version of KVM module contain these features, 1. The module will use libvirt API to manipulate the VM on KVM hosts. The main reason behind this is that libvirt is widely used API, many people in the community talked about this before, and libvirt support for different hypervisors, such as KVM, Xen, Qemu, etc.. It would be easier to port this module to support other hypervisor in future. 2. An setup script can help the users to setup KVM host much easier. The attachment named kvmsetup is the script. I tested it on Fedora 9. Basically, user need to install Fedora 9 (or use XCAT to install Fedora 9 on blade automatically) and run the script as the root user. 3. Users don't have to use qemu-ifup and mac script. "qemu-ifup" is not needed because of using lib-virt and "mac" is now included in kvm.pm. So kvm.pm is the only file you need to add to VCL Management Machine. 4. Both "-flat.vmdk" and "img" image format are supported. So now both KVM image and VMware ESXi image (flat.vmdk) can be provisioned on KVM host. 5. Misc code updated. Thanks, Xianqing -Original Message- From: Andy Kurth Sent: Wednesday, August 03, 2011 02:14 PM To: vcl-dev@incubator.apache.org Subject: Re: The New KVM Provisioning module $self->data->get_image_os_install_type() should do it. On Wed, Aug 3, 2011 at 12:47 PM, Xianqing Yu wrote: A quick question, do you know any function call can get OSinstalltype content for the target image? Thanks, Xianqing Yu -- Graduate Research Assistant, Cyber Defense Lab Department of Computer Science North Carolina State University, Raleigh, NC E-mail: x...@ncsu.edu -Original Message- From: Andy Kurth Sent: Wednesday, August 03, 2011 09:38 AM To: vcl-dev@incubator.apache.org Subject: Re: The New KVM Provisioning module I agree that entries should be added to OSinstalltype. I wouldn't include the 'kvm' hypervisor name in the name since the same type may be used by multiple hypervisors. The 'vmware' entry can probably be renamed to 'vmdk' and then used by both VMware and KVM. An entry can be added named something like 'img' or 'vm-img'. On Tue, Aug 2, 2011 at 5:00 PM, Xianqing Yu wrote: I think it is possible to handle both types: vmdk and img. I believe that in my kvm provisioning code, the code need some conditions to decide if image file is vmdk file or img file. For example, We can add "kvm-img" and "kvm-vmware" into OSinstalltype table. If one image's OS module point to "kvm-img" as OSinstalltype, then the code should consider the image as "img" image file, and vice verse. Thanks, Xianqing Yu -- Graduate Research Assistant, Cyber Defense Lab Department of Computer Science North Carolina State University, Raleigh, NC E-mail: x...@ncsu.edu -Original Message- From: Aaron Peeler Sent: Tuesday, August 02, 2011 02:39 PM To: vcl-dev@incubator.apache.org Subject: Re: The New KVM Provisioning module The imagename is related to the OS table. It's also dependent on the the OS.moduleid, OS.installtype and the computer.provisioningid. We might need to add new entries for this module, which isn't a problem. Just need to decide on how to name it. Ideally I would like to see the libvirt/kvm module handle both types - vmdk and img. Aaron On Mon, Aug 1, 2011 at 11:13 AM, Xianqing Yu wrote: Thanks for your suggestion. I have a question about define the image name and capture function. Currently my kvm module can support vmware esxi image format (.vmdk and flat.vmdk, so I can easily support existing flat.vmdk images by KVM). But I also want it to support other image formats, such as .img. I think we may need to define the name format both in VCL database and KVM module. Let's said there is an image named CentOS5, In VMDK format, In VCL database, it should be esx-CentOS5-v0, In image library, it should be files, esx-CentOS5-v0.vmdk and esx-CentOS5-v0-flat.vmdk. My question is that what its name should be when the image file is img format? My final goal is that make KVM module can support flat.vmdk and img file at the same time. Is that possible to do that? Or I should give one of them up? Thanks, Xianqing Yu -- Graduate Research Assistant, Cyber Defense Lab Department of Computer Science North Carolina State University, Raleigh, NC E-mail: x...@ncsu.edu -Original Message- From: Andy Kurth Sent: Monday, August 01, 2011 09:02 AM To: vcl-dev@incubator.apache.org Subject: Re: The New KVM Provisioning module Hi Xianqing, Sounds great. I'd like to help with this too. I like the idea about making it generic. Since libvirt supports a few different things, I think a very generic libvirt.pm module inheriting from Provisioning.pm makes sense: Package: VCL::Module::P
Re: [VCL 2.2.1] [Power7] Problem with image reservation
Sunil, I can respond to #1. I think you just have a permissions or mapping problem, but it may be something deeper. Please double check the following things through the web interface: -make sure the image is in an image group -make sure the image group is mapped to a computer group containing computers that are in the available state, have platformid set to the same thing it is set to for the image, and have RAM, procnumber, procspeed, and network greater than or equal to those settings for the image -make sure your user account has imageCheckOut at a node where the image group and computer group are available -make sure the computer group is mapped to a management node group that contains a management node that is actively checking in -make sure the computers in the computer group have a schedule assigned that is available during the time you have selected If all of that is correct, you'll need to look at isAvailable in utils.php to see where it is returning something < 1. Josh On Tue August 2 2011 2:17:59 pm Sunil Venkatesh wrote: > Hi Josh, > > So, I was able to get the VCL to capture & restore the images on to the > Power7 blade without any errors. The VCL web portal shows the Power7 node > being loaded with the captured image. I was looking for some clarification > with a couple of things. > > 1. The web portal shows "Selection currently not available" when I intend > to make a reservation on the Power7 blade that I have been working with > all this while. > > 2. Once the image is loaded onto the blade, I am able to login from the > management node without a password. However, when I am using rcons to > login as root on the Power7 blade, it does not accept the root password I > had used during the OS installation. Does the root password get reset to a > default one? I was checking vcl/lib/VCL/Module/OS/Linux.pm if that is the > case. > > Thanks & Regards, > Sunil > > On Jul 7, 2011, at 2:03 PM, Josh Thompson wrote: > > This and your next question are both deeper into the backend code that > > I've worked with. Andy or Aaron may be able to answer your questions > > further. > > > > Josh -- --- Josh Thompson Systems Programmer Virtual Computing Lab (VCL) North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at www.keyserver.net signature.asc Description: This is a digitally signed message part.
