[jira] [Updated] (VCL-539) Using VCL to provision POWER7 environment
[ https://issues.apache.org/jira/browse/VCL-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Venkatesh updated VCL-539: Attachment: (was: partimageng_pm.diff) Using VCL to provision POWER7 environment - Key: VCL-539 URL: https://issues.apache.org/jira/browse/VCL-539 Project: VCL Issue Type: New Feature Components: database, vcld (backend), web gui (frontend) Environment: POWER 7 as compute node Reporter: Sunil Venkatesh Labels: newbie, patch Attachments: Provisioning the POWER7 blades.docx, partimageng_postscript.diff, web_portal.diff This JIRA issue addresses changes done to different parts of VCL code to support provisioning a Power 7 instance.Parts of code that are affected are - partimage script, VCL script and the VCL database. All code changes are covered in the attached patch files, however changes done to database are just documented in a file, since these changes have to go into vcl.sql file of the apache-VCL-2.2.1-incubating package. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VCL-539) Using VCL to provision POWER7 environment
[ https://issues.apache.org/jira/browse/VCL-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Venkatesh updated VCL-539: Attachment: Provisioning the POWER7 blades.docx partimageng_postscript.diff web_portal.diff I am taking the patch file parthimageng_pm.diff off the JIRA issue, since these changes are specific to our university configuration and do not apply to all environments. Using VCL to provision POWER7 environment - Key: VCL-539 URL: https://issues.apache.org/jira/browse/VCL-539 Project: VCL Issue Type: New Feature Components: database, vcld (backend), web gui (frontend) Environment: POWER 7 as compute node Reporter: Sunil Venkatesh Labels: newbie, patch Attachments: Provisioning the POWER7 blades.docx, partimageng_postscript.diff, web_portal.diff This JIRA issue addresses changes done to different parts of VCL code to support provisioning a Power 7 instance.Parts of code that are affected are - partimage script, VCL script and the VCL database. All code changes are covered in the attached patch files, however changes done to database are just documented in a file, since these changes have to go into vcl.sql file of the apache-VCL-2.2.1-incubating package. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VCL-539) Using VCL to provision POWER7 environment
[ https://issues.apache.org/jira/browse/VCL-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Venkatesh updated VCL-539: Attachment: (was: Provisioning the POWER7 blades.docx) Using VCL to provision POWER7 environment - Key: VCL-539 URL: https://issues.apache.org/jira/browse/VCL-539 Project: VCL Issue Type: New Feature Components: database, vcld (backend), web gui (frontend) Environment: POWER 7 as compute node Reporter: Sunil Venkatesh Labels: newbie, patch Attachments: Provisioning the POWER7 blades.docx, partimageng_postscript.diff, web_portal.diff This JIRA issue addresses changes done to different parts of VCL code to support provisioning a Power 7 instance.Parts of code that are affected are - partimage script, VCL script and the VCL database. All code changes are covered in the attached patch files, however changes done to database are just documented in a file, since these changes have to go into vcl.sql file of the apache-VCL-2.2.1-incubating package. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VCL-539) Using VCL to provision POWER7 environment
[ https://issues.apache.org/jira/browse/VCL-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Venkatesh updated VCL-539: Attachment: (was: partimageng_postscript.diff) Using VCL to provision POWER7 environment - Key: VCL-539 URL: https://issues.apache.org/jira/browse/VCL-539 Project: VCL Issue Type: New Feature Components: database, vcld (backend), web gui (frontend) Environment: POWER 7 as compute node Reporter: Sunil Venkatesh Labels: newbie, patch Attachments: Provisioning the POWER7 blades.docx, partimageng_postscript.diff, web_portal.diff This JIRA issue addresses changes done to different parts of VCL code to support provisioning a Power 7 instance.Parts of code that are affected are - partimage script, VCL script and the VCL database. All code changes are covered in the attached patch files, however changes done to database are just documented in a file, since these changes have to go into vcl.sql file of the apache-VCL-2.2.1-incubating package. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VCL-539) Using VCL to provision POWER7 environment
[ https://issues.apache.org/jira/browse/VCL-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Venkatesh updated VCL-539: Attachment: (was: web_portal.diff) Using VCL to provision POWER7 environment - Key: VCL-539 URL: https://issues.apache.org/jira/browse/VCL-539 Project: VCL Issue Type: New Feature Components: database, vcld (backend), web gui (frontend) Environment: POWER 7 as compute node Reporter: Sunil Venkatesh Labels: newbie, patch Attachments: Provisioning the POWER7 blades.docx, partimageng_postscript.diff, web_portal.diff This JIRA issue addresses changes done to different parts of VCL code to support provisioning a Power 7 instance.Parts of code that are affected are - partimage script, VCL script and the VCL database. All code changes are covered in the attached patch files, however changes done to database are just documented in a file, since these changes have to go into vcl.sql file of the apache-VCL-2.2.1-incubating package. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Virtualization on POWER7
I have re-uploaded the files with the Grant license to ASF for inclusion in ASF works option selected. Please let me know if you have problems in integration. PS- Changes to database are mentioned in the attached documentation. Regards, Sunil On Fri, Nov 18, 2011 at 10:19 AM, Kevan Miller kevan.mil...@gmail.comwrote: On Nov 18, 2011, at 9:38 AM, Andy Kurth wrote: Thanks Sunil. It looks like you uploaded the files correctly to the Jira issue. Not quite correct… Note that there isn't an Apache Feather next to those files… This means the Grant license to ASF for inclusion in ASF works was not selected. This is not an absolute requirement. Just posting the files indicates that Sunil wishes to donat the files. However, clicking this button makes things quite explicit and is the preferred technique. --kevan
[jira] [Created] (VCL-539) Using VCL to provision POWER7 environment
Using VCL to provision POWER7 environment - Key: VCL-539 URL: https://issues.apache.org/jira/browse/VCL-539 Project: VCL Issue Type: New Feature Components: database, vcld (backend), web gui (frontend) Environment: POWER 7 as compute node Reporter: Sunil Venkatesh Fix For: 2.3 This JIRA issue addresses changes done to different parts of VCL code to support provisioning a Power 7 instance.Parts of code that are affected are - partimage script, VCL script and the VCL database. All code changes are covered in the attached patch files, however changes done to database are just documented in a file, since these changes have to go into vcl.sql file of the apache-VCL-2.2.1-incubating package. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VCL-539) Using VCL to provision POWER7 environment
[ https://issues.apache.org/jira/browse/VCL-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Venkatesh updated VCL-539: Attachment: Provisioning the POWER7 blades.docx partimageng_postscript.diff partimageng_pm.diff web_portal.diff 3 Patch files a short document Using VCL to provision POWER7 environment - Key: VCL-539 URL: https://issues.apache.org/jira/browse/VCL-539 Project: VCL Issue Type: New Feature Components: database, vcld (backend), web gui (frontend) Environment: POWER 7 as compute node Reporter: Sunil Venkatesh Labels: newbie, patch Fix For: 2.3 Attachments: Provisioning the POWER7 blades.docx, partimageng_pm.diff, partimageng_postscript.diff, web_portal.diff This JIRA issue addresses changes done to different parts of VCL code to support provisioning a Power 7 instance.Parts of code that are affected are - partimage script, VCL script and the VCL database. All code changes are covered in the attached patch files, however changes done to database are just documented in a file, since these changes have to go into vcl.sql file of the apache-VCL-2.2.1-incubating package. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VCL-539) Using VCL to provision POWER7 environment
[ https://issues.apache.org/jira/browse/VCL-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Venkatesh updated VCL-539: Fix Version/s: (was: 2.3) Using VCL to provision POWER7 environment - Key: VCL-539 URL: https://issues.apache.org/jira/browse/VCL-539 Project: VCL Issue Type: New Feature Components: database, vcld (backend), web gui (frontend) Environment: POWER 7 as compute node Reporter: Sunil Venkatesh Labels: newbie, patch Attachments: Provisioning the POWER7 blades.docx, partimageng_pm.diff, partimageng_postscript.diff, web_portal.diff This JIRA issue addresses changes done to different parts of VCL code to support provisioning a Power 7 instance.Parts of code that are affected are - partimage script, VCL script and the VCL database. All code changes are covered in the attached patch files, however changes done to database are just documented in a file, since these changes have to go into vcl.sql file of the apache-VCL-2.2.1-incubating package. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Virtualization on POWER7
Aaron, Attached is a document 2 patch files that reflect the changes that I have made to get VCL working on POWER7. If you need further information, please let me know about the same. Regards, Sunil On Sep 14, 2011, at 9:57 AM, Aaron Peeler wrote: Right. What I'm asking is would you be willing / interested in creating the powerVM VCL provisioning module? This could be similar to the kvm module, but using the powerVM commands. Also did you have Power7 working? Did you have to make any changes to the xCAT module? Or any new OS modules? Aaron On Tue, Sep 13, 2011 at 4:13 PM, Sunil Venkatesh suni...@umbc.edu wrote: Aaron, We would certainly be targeting the development towards the larger VCL community. But, this development is possible when the PowerVM package is made available. I would assume a module that is similar to the existing KVM module should serve the purpose. Regards, Sunil On Sep 13, 2011, at 3:16 PM, Aaron Peeler wrote: Sunil, I think this would be a great addition. While I've not used Power7 or PowerVM. I do know of some interest in VCL supporting this. The VCL community is looking for good committers. Would you be interested in developing this, not only for UMBC but for the larger VCL community? Given the work you've already done with Power7 and VCL with xCAT, it appears you have a pretty good understanding of the VCL code structure. Thanks, Aaron On Tue, Sep 13, 2011 at 1:45 PM, Sunil Venkatesh suni...@umbc.edu wrote: Dear all, As informed by Dr. Yesha, we @ UMBC are working on provisioning virtual nodes from the POWER7 blade. And, I wanted to update regarding the restrictions that I have come across in achieving the same. Virtualization with RedHat EL (RHEL) is not possible on POWER7 - 1. Latest version of RHEL - version 5 for power systems uses kernel version 2.6.18. However, KVM is only supported on kernels 2.6.24 or later. 2. Virtualization support in RHEL is available only under the x86 architectures. (http://www.redhat.com/rhel/server/virtualization_support.html#virt_matrix) The only way, is to make use of PowerVM (an IBM product). I spoke to the IBM Customer representative and he confirmed that the only way to perform virtualization on POWER is to make use of PowerVM. However, VCL does not have support for provisioning over PowerVM. I would like to know if it would be feasible to procure PowerVM and integrate it with the VCL framework. Please let us know your comments regarding the same. Regards, Sunil -- 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.
Virtualization on POWER7
Dear all, As informed by Dr. Yesha, we @ UMBC are working on provisioning virtual nodes from the POWER7 blade. And, I wanted to update regarding the restrictions that I have come across in achieving the same. Virtualization with RedHat EL (RHEL) is not possible on POWER7 - 1. Latest version of RHEL - version 5 for power systems uses kernel version 2.6.18. However, KVM is only supported on kernels 2.6.24 or later. 2. Virtualization support in RHEL is available only under the x86 architectures. (http://www.redhat.com/rhel/server/virtualization_support.html#virt_matrix) The only way, is to make use of PowerVM (an IBM product). I spoke to the IBM Customer representative and he confirmed that the only way to perform virtualization on POWER is to make use of PowerVM. However, VCL does not have support for provisioning over PowerVM. I would like to know if it would be feasible to procure PowerVM and integrate it with the VCL framework. Please let us know your comments regarding the same. Regards, Sunil
Power7 Virtualization
Dear all, Is there a way to perform virtualization or run a hypervisor on the Power7 architecture using the functionalities provided by VCL currently? Both Vmware and vbox mostly support the x86 architectures, however I didn't come across a mention of support for Power7 or related architecture mentioned anyplace. PowerVM has support for virtualization of certain flavors of Linux on Power 5,6 7 architectures, but this is not supported in VCL. I haven't determined if it can be integrated into the VCL system. Please provide your inputs regarding the Power7 virtualization. Regards, Sunil
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 suni...@umbc.edu 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
Josh, Could you provide me with the links to the resources of the VCL workshop? If there is a way to witness the workshop while it is in progress, that would help too. Regards, Sunil On Jul 7, 2011, at 2:03 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sunil, On Thursday July 07, 2011, Sunil Venkatesh wrote: Thanks Josh. My professor was asking about the details of VCL workshop in NC. Are you aware of these details? The workshop is hosted by NCSU. It takes people from an introduction to VCL to actually installing and managing it. It is already full, but I think recordings of the sessions may be available when it is over. Please bare with my comments inline. Responses also inline. On 7/7/11 11:13 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday July 05, 2011, Sunil Venkatesh wrote: Hi Josh, I was able to get the following things done in respect to getting VCL to work on POWER. 1. Made modifications in the xcat tables to get the capture process working with statelite images instead of stateless images. Particularly the noderes bootparams table. 2. Used partimage to capture the images (did NOT set usepartimageng to 1). -rw-r--r-- 1 root root0 Jul 5 16:38 compute.img.capturedone -rw-r--r-- 1 root root0 Jul 5 15:58 compute.img.capturefailed -rw--- 1 root root 6.5M Jul 5 16:07 compute-parta2.gz -rw--- 1 root root 679M Jul 5 16:10 compute-parta3.gz -rw--- 1 root root 23M Jul 5 16:38 compute-parta6.gz -rw-r--r-- 1 root root 512 Jul 5 16:07 compute-sda.mbr -rw-r--r-- 1 root root 363 Jul 5 16:07 compute-sda.sfdisk 2 partitions including the boot partition present on the blade were captured under /install/image/ppc64/. Initially, RHEL 5 was installed on a 600 GB partition due to which the capture process failed. The image of the partition was generated once the partition size was reduced to 6GB. Is it necessary for me to use partimage-ng instead of partimage itself? Are you asking if you need to use partimage-ng for partitions that are 600GB? If so, I don't really know. We've never dealt with partitions that large. Here, I am just asking if images captured using partimage are recognized by VCL or is it required that I use partimage-ng. From your earlier emails to Prem, I could notice that the only difference between partimage partimage-ng (after setting userpartimageng to 1) is the former generates images with .gz and the later generates .img. Am I right here? Also, I was able to get the 600GB partition captured, since the partition was empty, it resulted in a ~17MB image file. VCL can deploy images captured with both partimage and partimage-ng. At NCSU, we were going to switch to partimage-ng, which is why I added in support for it, but then we realized we'd have to upgrade all of our management nodes to xCAT2 at the same time or some of them wouldn't be able to deploy newly captured images that were captured with partimage-ng (the support for xCAT1.x can't deploy using partimage-ng). So, we just stuck with partimage. The captured file format between the two is different. When proceeding further with vcld --setup, the script was not able to find the images that were created using partimage. The options that are provided in the script does not allow for selecting an architecture other than x86/x86_64. You'll need to modify the vcld image.pm module. Look in /usr/local/vcl/lib/VCL. In image.pm, look for the function 'setup_capture_base_image'; then, find 'my @architecture_choices' and add 'ppc' as another option. As a matter of fact, I tried this step. But, the _get_image_repository_path function in /usr/local/vcl/lib/VCL/Module/Provisioning/xCAT.pm does not recognize the architecture when I choose ppc/ppc64 in the menu. On line 2922 in the same file, image_architecture is set to undefined. I think the list of supported architectures is stored in some mysql table. I haven't checked regarding this, i was trying to get VCL to recognize the images as x86/x86_64 by setting up soft links in the search paths of VCL. 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 Also, in the error log vcld is looking for /opt/xcat/share/xcat/install/image/rh5image-power010701bi34-v0.tmpl and cannot find the template file. Should the template file that needs to be accessed in this case be createimage.ppc64.tmpl? This is actually a check to make sure the image doesn't already exist before trying to capturing it. So, it is good that it doesn't find it. If possible, could you please provide me with the details of steps that take place here. If there are any documentation available regarding this, that would work too. U said image doesn't already exist before trying to capturing it, how
Re: [VCL 2.2.1] [Power7] Problem with image reservation
Thanks Josh. My professor was asking about the details of VCL workshop in NC. Are you aware of these details? Please bare with my comments inline. On 7/7/11 11:13 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday July 05, 2011, Sunil Venkatesh wrote: Hi Josh, I was able to get the following things done in respect to getting VCL to work on POWER. 1. Made modifications in the xcat tables to get the capture process working with statelite images instead of stateless images. Particularly the noderes bootparams table. 2. Used partimage to capture the images (did NOT set usepartimageng to 1). -rw-r--r-- 1 root root0 Jul 5 16:38 compute.img.capturedone -rw-r--r-- 1 root root0 Jul 5 15:58 compute.img.capturefailed -rw--- 1 root root 6.5M Jul 5 16:07 compute-parta2.gz -rw--- 1 root root 679M Jul 5 16:10 compute-parta3.gz -rw--- 1 root root 23M Jul 5 16:38 compute-parta6.gz -rw-r--r-- 1 root root 512 Jul 5 16:07 compute-sda.mbr -rw-r--r-- 1 root root 363 Jul 5 16:07 compute-sda.sfdisk 2 partitions including the boot partition present on the blade were captured under /install/image/ppc64/. Initially, RHEL 5 was installed on a 600 GB partition due to which the capture process failed. The image of the partition was generated once the partition size was reduced to 6GB. Is it necessary for me to use partimage-ng instead of partimage itself? Are you asking if you need to use partimage-ng for partitions that are 600GB? If so, I don't really know. We've never dealt with partitions that large. Here, I am just asking if images captured using partimage are recognized by VCL or is it required that I use partimage-ng. From your earlier emails to Prem, I could notice that the only difference between partimage partimage-ng (after setting userpartimageng to 1) is the former generates images with .gz and the later generates .img. Am I right here? Also, I was able to get the 600GB partition captured, since the partition was empty, it resulted in a ~17MB image file. When proceeding further with vcld --setup, the script was not able to find the images that were created using partimage. The options that are provided in the script does not allow for selecting an architecture other than x86/x86_64. You'll need to modify the vcld image.pm module. Look in /usr/local/vcl/lib/VCL. In image.pm, look for the function 'setup_capture_base_image'; then, find 'my @architecture_choices' and add 'ppc' as another option. As a matter of fact, I tried this step. But, the _get_image_repository_path function in /usr/local/vcl/lib/VCL/Module/Provisioning/xCAT.pm does not recognize the architecture when I choose ppc/ppc64 in the menu. On line 2922 in the same file, image_architecture is set to undefined. I think the list of supported architectures is stored in some mysql table. I haven't checked regarding this, i was trying to get VCL to recognize the images as x86/x86_64 by setting up soft links in the search paths of VCL. Also, in the error log vcld is looking for /opt/xcat/share/xcat/install/image/rh5image-power010701bi34-v0.tmpl and cannot find the template file. Should the template file that needs to be accessed in this case be createimage.ppc64.tmpl? This is actually a check to make sure the image doesn't already exist before trying to capturing it. So, it is good that it doesn't find it. If possible, could you please provide me with the details of steps that take place here. If there are any documentation available regarding this, that would work too. U said image doesn't already exist before trying to capturing it, how does VCL capture the images? does it make use of the images that are already generated using partimage? if so, in what places does it look for the images? Sorry for asking too many questions. I could trace the scripts to check the flow, but, that would take a lot of time. You have been really patient with all my queries, appreciate that. Thanks Sunil It sounds like you're almost there. Great work! Josh I have attached a log at the end of the mail. I am not sure where I have gone wrong with the VCL configuration. -Sunil - rh5image-power010701bi34-v0 image creation failed time: 2011-07-05 11:03:25 caller: image.pm:reservation_failed(385) ( 0) image.pm, reservation_failed (line: 385) (-1) image.pm, process (line: 167) (-2) vcld, make_new_child (line: 568) (-3) vcld, main (line: 346) management node: web1.bluegrit.cs.umbc.edu reservation PID: 9866 parent vcld PID: 19110 request ID: 30 reservation ID: 30 request state/laststate: image/image request start time: 2011-07-05 11:03:20 request end time: 2011-07-05 12:03:20 for imaging: no log ID: none computer: power01.bluegrit.cs.umbc.edu computer id: 2 computer type: blade computer eth0 MAC address:undefined computer eth1
Re: VCL xCAT2.x BladeCenter
Hi Josh/Prem, I was trying to get xcat working with the PPC. However, I couldn't find the partimage-ng binary on the ramdisk. Is there any place I could find this package? I have the partimage binaries that I downloaded off a website, but couldn't find partimage-ng in that package. I am using statelite to capture the image from the PPC blade. Regards, Sunil On 6/9/11 4:58 PM, Prem Kumar wrote: Josh, got it to work!!! 'usepartimageng=0' set it to 1. never mind about the link to download partimage-ng, i was under the impression, that i will have to install partimage-ng, then looked around to realize it already exists in rootimg.gz. sincere thanks for patiently helping, now moving to next step! regards, prem. On Thu, Jun 9, 2011 at 3:50 PM, Prem Kumarprem.it.ku...@gmail.com wrote: hi Josh, I need to add this to the documentation and should have mentioned it earlier. partimage can only capture a few file system types. I don't remember the exact list. I know it includes ext2/ext3 and ntfs. I also know that it cannot capture ext4 and anything involving LVM. That is part of why I included support for partimageng. If it doesn't natively know how to handle the file system, it will fall back to using dd to capture it. Search for 'usepartimageng=0' in the partimageng postscript and change it to =1 to switch to using partimageng. Is the file system to be captured either ext2 or ext3 and without having LVM invovled? file system involved is ext3 and without 'lvm'. so i am good on that. i could not find partimage-ng for download, could you point me to a genuine source, sourceforege doesn't have it. following is the link to /tmp/partimageng.log http://pastebin.com/YrbmsF99 also noticed following error from partimage log in /var/log [Can't read bit map block 0 from image] looking out for that errors tells me that it could be because of running partimage in 'gui' mode as opposed to batch, still looking for more reasons. meanwhile i will look for other errors and wait for link to partimage-ng. regards, prem.
Re: [VCL 2.2.1] [Power7] Problem with image reservation
Hi, Update ! I was able to fix the problem that I was facing with the scripts by disabling the firewall. But, I still have a problem with the command- nodeset nodename image Unless this error is fixed, I don't think partimage will work. Am I right here? Thanks, Sunil On Tue, Jun 21, 2011 at 3:13 PM, Sunil Venkatesh suni...@umbc.edu wrote: Josh, I have reached a point where I am able to boot the ppc using the statelite images created using genimage. But, I was wondering how significant the following command is. nodeset nodename image I got the same error that Prem had mentioned. power01: Error: Unable to identify plugin for this command, check relevant tables: nodetype.os Error: Some nodes failed to set up image resources, aborting I tried changing the 'os' field to 'image' under nodetype, that doesn't seem to help. I get the same error even after the change. 'arch' in my case is set to 'ppc64'. Also, I think partimage plugin needs to be changed to support the ppc architecture, from what you had mentioned in the other thread. I am not sure what the command 'nodeset nodename image' does, but, I am able to boot the statelite images by making changes to the yaboot configuration files. The ppc blade currently uses LVM, that needs to be replaced with ext2/ext3 from what I read from the other thread, am I right? Also, just out of curiosity I left the statelite image to boot with my current setting. I can see the xcat script throwing an error- /opt/xcat/xcatdsklspost: line 229: /xcatpost/getpostscript.awk: No such file or directory /tmp/mypostscript: line 16: updateflag.awk: command not found both getpostscript.awk updateflag.awk are not found in the rootimg created by genimage. Is there any place I could find these scripts? Also, please correct me if there is anything wrong with the procedure I am following. Thanks in advance. Regards, Sunil On 6/13/11 4:13 PM, Josh Thompson wrote: Sunil, From what I remember, I didn't have to do much to the rootimg.gz image to make it work. I created the files I supply before xCAT started using statelite instead of stateless. I think statelite uses NFS to mount the image, and stateless uses an image file downloaded to the node and run out of RAM. Since generating a statelite image is pretty straightforward use of xCAT, you may want to ask on the xcat-user email list for help with it. Unless you can have the admins of the other dhcp server on your network exclude the MAC addresses of your blades, you'll need to create a separate private network to control your VCL stuff, either physically or with VLANs. If they can exclude the MACs, you can set up the dhcp server on your management node to only answer to requests from your blades. Josh On Monday June 13, 2011, Sunil Venkatesh wrote: Josh, Again, Thank you for your valuable inputs. I have got to the point where I can get the compute node to boot using the stateless images. I had to manually configure the netboot since we already had a DHCP server which is not the same as our Management node. Since our setup is not in an isolated environment, I could not let xcat handle the dhcp netboot configuration (it messed up out network configuration when i let xcat handle it,we had 2 dhcp servers running at that point). Are you aware of any way to let xcat handle such scenarios? Although I am able to get the compute node to boot with the kernel image initrd, and NFS mount the rootimg that was generated using 'genimage', I am getting the following error on the compute node's console - FATAL error: could not get the entries from litefile table... after going thru the init-scripts, I found out 'xCATCmd' binary is not present in the rootimg. I am currently checking the xcat packages for its availability. If you know the procedure to get it onto the compute node, please let me know the same. Appreciate your support. Thanking you, Sunil On 6/8/11 9:02 AM, Josh Thompson wrote: Sunil, I don't recall seeing any documentation on those parts. I had to poke around looking at parts of xCAT to see how it worked. It's been a few years since I did that; so, I don't remember much about the process. My recommendation would be to start looking at things in the rootimg.gz image. Looking at it now, I see that /opt/xcat/xcatdsklspost gets run when rootimg.gz boots. It looks like it downloads all of the postscripts from the management node and then run getpostscript.awk which issues a command to xcatd to get the primary postscript for that machine. I've forgotten how xcatd then builds the primary postscript. I do remember that in the partimageng.pm module, I had it add the partimageng postscript. So, you'll really have to start digging through how the xcat postscript system works. Josh On Tuesday June 07, 2011, Sunil Venkatesh wrote: Josh, Is there any place I could find some details on ... /Once the compute
Re: [VCL 2.2.1] [Power7] Problem with image reservation
Josh, I have reached a point where I am able to boot the ppc using the statelite images created using genimage. But, I was wondering how significant the following command is. nodeset nodename image I got the same error that Prem had mentioned. power01: Error: Unable to identify plugin for this command, check relevant tables: nodetype.os Error: Some nodes failed to set up image resources, aborting I tried changing the 'os' field to 'image' under nodetype, that doesn't seem to help. I get the same error even after the change. 'arch' in my case is set to 'ppc64'. Also, I think partimage plugin needs to be changed to support the ppc architecture, from what you had mentioned in the other thread. I am not sure what the command 'nodeset nodename image' does, but, I am able to boot the statelite images by making changes to the yaboot configuration files. The ppc blade currently uses LVM, that needs to be replaced with ext2/ext3 from what I read from the other thread, am I right? Also, just out of curiosity I left the statelite image to boot with my current setting. I can see the xcat script throwing an error- /opt/xcat/xcatdsklspost: line 229: /xcatpost/getpostscript.awk: No such file or directory /tmp/mypostscript: line 16: updateflag.awk: command not found both getpostscript.awk updateflag.awk are not found in the rootimg created by genimage. Is there any place I could find these scripts? Also, please correct me if there is anything wrong with the procedure I am following. Thanks in advance. Regards, Sunil On 6/13/11 4:13 PM, Josh Thompson wrote: Sunil, From what I remember, I didn't have to do much to the rootimg.gz image to make it work. I created the files I supply before xCAT started using statelite instead of stateless. I think statelite uses NFS to mount the image, and stateless uses an image file downloaded to the node and run out of RAM. Since generating a statelite image is pretty straightforward use of xCAT, you may want to ask on the xcat-user email list for help with it. Unless you can have the admins of the other dhcp server on your network exclude the MAC addresses of your blades, you'll need to create a separate private network to control your VCL stuff, either physically or with VLANs. If they can exclude the MACs, you can set up the dhcp server on your management node to only answer to requests from your blades. Josh On Monday June 13, 2011, Sunil Venkatesh wrote: Josh, Again, Thank you for your valuable inputs. I have got to the point where I can get the compute node to boot using the stateless images. I had to manually configure the netboot since we already had a DHCP server which is not the same as our Management node. Since our setup is not in an isolated environment, I could not let xcat handle the dhcp netboot configuration (it messed up out network configuration when i let xcat handle it,we had 2 dhcp servers running at that point). Are you aware of any way to let xcat handle such scenarios? Although I am able to get the compute node to boot with the kernel image initrd, and NFS mount the rootimg that was generated using 'genimage', I am getting the following error on the compute node's console - FATAL error: could not get the entries from litefile table... after going thru the init-scripts, I found out 'xCATCmd' binary is not present in the rootimg. I am currently checking the xcat packages for its availability. If you know the procedure to get it onto the compute node, please let me know the same. Appreciate your support. Thanking you, Sunil On 6/8/11 9:02 AM, Josh Thompson wrote: Sunil, I don't recall seeing any documentation on those parts. I had to poke around looking at parts of xCAT to see how it worked. It's been a few years since I did that; so, I don't remember much about the process. My recommendation would be to start looking at things in the rootimg.gz image. Looking at it now, I see that /opt/xcat/xcatdsklspost gets run when rootimg.gz boots. It looks like it downloads all of the postscripts from the management node and then run getpostscript.awk which issues a command to xcatd to get the primary postscript for that machine. I've forgotten how xcatd then builds the primary postscript. I do remember that in the partimageng.pm module, I had it add the partimageng postscript. So, you'll really have to start digging through how the xcat postscript system works. Josh On Tuesday June 07, 2011, Sunil Venkatesh wrote: Josh, Is there any place I could find some details on ... /Once the compute node is booted with the stateless image, it uses NFS to mount some things from the management node, and then runs some xcat postscripts,/ I have the stateless images ready with partimage compiled for PPC. For the compute node (power 7) to boot using the stateless images, i need to configure the yaboot instead of pxeboot (which is specific to x86). I wanted to know where in the startup files the execution
Re: [VCL 2.2.1] [Power7] Problem with image reservation
Josh, Again, Thank you for your valuable inputs. I have got to the point where I can get the compute node to boot using the stateless images. I had to manually configure the netboot since we already had a DHCP server which is not the same as our Management node. Since our setup is not in an isolated environment, I could not let xcat handle the dhcp netboot configuration (it messed up out network configuration when i let xcat handle it,we had 2 dhcp servers running at that point). Are you aware of any way to let xcat handle such scenarios? Although I am able to get the compute node to boot with the kernel image initrd, and NFS mount the rootimg that was generated using 'genimage', I am getting the following error on the compute node's console - FATAL error: could not get the entries from litefile table... after going thru the init-scripts, I found out 'xCATCmd' binary is not present in the rootimg. I am currently checking the xcat packages for its availability. If you know the procedure to get it onto the compute node, please let me know the same. Appreciate your support. Thanking you, Sunil On 6/8/11 9:02 AM, Josh Thompson wrote: Sunil, I don't recall seeing any documentation on those parts. I had to poke around looking at parts of xCAT to see how it worked. It's been a few years since I did that; so, I don't remember much about the process. My recommendation would be to start looking at things in the rootimg.gz image. Looking at it now, I see that /opt/xcat/xcatdsklspost gets run when rootimg.gz boots. It looks like it downloads all of the postscripts from the management node and then run getpostscript.awk which issues a command to xcatd to get the primary postscript for that machine. I've forgotten how xcatd then builds the primary postscript. I do remember that in the partimageng.pm module, I had it add the partimageng postscript. So, you'll really have to start digging through how the xcat postscript system works. Josh On Tuesday June 07, 2011, Sunil Venkatesh wrote: Josh, Is there any place I could find some details on ... /Once the compute node is booted with the stateless image, it uses NFS to mount some things from the management node, and then runs some xcat postscripts,/ I have the stateless images ready with partimage compiled for PPC. For the compute node (power 7) to boot using the stateless images, i need to configure the yaboot instead of pxeboot (which is specific to x86). I wanted to know where in the startup files the execution of partimage and NFS mount is configured. Is it configured by the genimage command itself? Considering the way in which the nodes are configured in the network, it would not be a good idea to let xcat take care of configuring the details like DHCPD for netboot. So, I need to make changes to the configuration files manually, which is why this query came up. Thanks in advance. Regards, Sunil On 6/1/11 1:39 PM, Josh Thompson wrote: Sunil, The stateless image I refer to is what is actually booted on the compute node containing the image to be captured. It's called stateless because it is loaded completely in RAM and does not maintain any state when a reboot occurs. The partimage binary is part of this stateless image and actually runs on the compute node. It does not run on the management node. The management node does not have block level access to the disk on the compute node to be able to capture the image from the disk. I'll try to describe the process a little better. The management node issues a reboot command to the compute node. The compute node uses PXE to load and boot a kernel (vmlinuz), initial RAM disk (initrd.img), and a root filesystem (rootimg.gz) from the management node. All three of these together make up the stateless image. Once the compute node is booted with the stateless image, it uses NFS to mount some things from the management node, and then runs some xcat postscripts, one of which is the partimageng postscript. This postscript determines what partitions are on the compute node and, depending on how the postscript is configured, uses partimage or partimageng to capture an image of the compute node disk that is then saved to the management node. When it is finished capturing the image, it notifies xcat on the management node and then reboots. xcat reconfigures itself to tell the compute node to boot off of disk at next boot. When the compute node comes up, it uses PXE to ask the management node how to boot. The management node tells it to boot off of disk. I hope that clarifies how the system works. If any of it is unclear, please ask for further clarification. Josh On Wednesday June 01, 2011, Sunil Venkatesh wrote: Josh, I had one more clarification. partimage binaries run in the management node to capture an (stateless) image from the compute node right? In that case, is there a need for these binaries to go into the rootimg.gz?? My assumption is, partimage runs
Re: [VCL 2.2.1] [Power7] Problem with image reservation
Josh, Is there any place I could find some details on ... /Once the compute node is booted with the stateless image, it uses NFS to mount some things from the management node, and then runs some xcat postscripts,/ I have the stateless images ready with partimage compiled for PPC. For the compute node (power 7) to boot using the stateless images, i need to configure the yaboot instead of pxeboot (which is specific to x86). I wanted to know where in the startup files the execution of partimage and NFS mount is configured. Is it configured by the genimage command itself? Considering the way in which the nodes are configured in the network, it would not be a good idea to let xcat take care of configuring the details like DHCPD for netboot. So, I need to make changes to the configuration files manually, which is why this query came up. Thanks in advance. Regards, Sunil On 6/1/11 1:39 PM, Josh Thompson wrote: Sunil, The stateless image I refer to is what is actually booted on the compute node containing the image to be captured. It's called stateless because it is loaded completely in RAM and does not maintain any state when a reboot occurs. The partimage binary is part of this stateless image and actually runs on the compute node. It does not run on the management node. The management node does not have block level access to the disk on the compute node to be able to capture the image from the disk. I'll try to describe the process a little better. The management node issues a reboot command to the compute node. The compute node uses PXE to load and boot a kernel (vmlinuz), initial RAM disk (initrd.img), and a root filesystem (rootimg.gz) from the management node. All three of these together make up the stateless image. Once the compute node is booted with the stateless image, it uses NFS to mount some things from the management node, and then runs some xcat postscripts, one of which is the partimageng postscript. This postscript determines what partitions are on the compute node and, depending on how the postscript is configured, uses partimage or partimageng to capture an image of the compute node disk that is then saved to the management node. When it is finished capturing the image, it notifies xcat on the management node and then reboots. xcat reconfigures itself to tell the compute node to boot off of disk at next boot. When the compute node comes up, it uses PXE to ask the management node how to boot. The management node tells it to boot off of disk. I hope that clarifies how the system works. If any of it is unclear, please ask for further clarification. Josh On Wednesday June 01, 2011, Sunil Venkatesh wrote: Josh, I had one more clarification. partimage binaries run in the management node to capture an (stateless) image from the compute node right? In that case, is there a need for these binaries to go into the rootimg.gz?? My assumption is, partimage runs on the management node (an intel blade in our case) to capture a stateless image from a compute node (a power 7 blade) and stores these images under /install of the management node. Please correct me if I am wrong here. Regards, Sunil On 6/1/11 9:58 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday May 31, 2011, Sunil Venkatesh wrote: Hi, I used the steps that were mentioned under https://cwiki.apache.org/confluence/display/VCL/Adding+support+for+parti mag e+and+partimage- ng+to+xCAT+2.x+%28unofficial%29 to enable partimage support for xcat. I wasn't sure if I need to change references to x86 x86_64 (as directories) to reflect the ppc architecture, as the web page says The architecture for the node must always be set to x86 for this... I have with me the vmlinuz (kernel image) and initrd for the capture process. The 2 nodeset commands By this, do you mean you have vmlinuz and initrd for your power blades, not the ones linked to off of the page you listed above? If you do, that's a good start. However, you'll also need rootimg.gz. rootimg.gz is the root filesystem for the stateless image. It also contains the partimage and partimageng binaries. Assuming partimage or partimageng can actually capture partitions from power systems, you'll need to compile at least one of them to run on power. For the rootimg.gz image I provided, I compiled them statically so that I didn't have to worry about including any library dependencies in rootimg.gz. It would be a good idea to research how to use xcat's genimage command to generate stateless images to learn how to do this. If there's any part of the above that you don't fully understand, please ask me to clarify it. Until you have a stateless image that you can deploy to your power blades, there's no point in trying to debug any VCL specific items. Josh - -- - --- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP
Re: [VCL 2.2.1] [Power7] Problem with image reservation
Josh, Thank you for that detailed clarification. Appreciate your support. Regards, Sunil On 6/1/11 1:39 PM, Josh Thompson wrote: Sunil, The stateless image I refer to is what is actually booted on the compute node containing the image to be captured. It's called stateless because it is loaded completely in RAM and does not maintain any state when a reboot occurs. The partimage binary is part of this stateless image and actually runs on the compute node. It does not run on the management node. The management node does not have block level access to the disk on the compute node to be able to capture the image from the disk. I'll try to describe the process a little better. The management node issues a reboot command to the compute node. The compute node uses PXE to load and boot a kernel (vmlinuz), initial RAM disk (initrd.img), and a root filesystem (rootimg.gz) from the management node. All three of these together make up the stateless image. Once the compute node is booted with the stateless image, it uses NFS to mount some things from the management node, and then runs some xcat postscripts, one of which is the partimageng postscript. This postscript determines what partitions are on the compute node and, depending on how the postscript is configured, uses partimage or partimageng to capture an image of the compute node disk that is then saved to the management node. When it is finished capturing the image, it notifies xcat on the management node and then reboots. xcat reconfigures itself to tell the compute node to boot off of disk at next boot. When the compute node comes up, it uses PXE to ask the management node how to boot. The management node tells it to boot off of disk. I hope that clarifies how the system works. If any of it is unclear, please ask for further clarification. Josh On Wednesday June 01, 2011, Sunil Venkatesh wrote: Josh, I had one more clarification. partimage binaries run in the management node to capture an (stateless) image from the compute node right? In that case, is there a need for these binaries to go into the rootimg.gz?? My assumption is, partimage runs on the management node (an intel blade in our case) to capture a stateless image from a compute node (a power 7 blade) and stores these images under /install of the management node. Please correct me if I am wrong here. Regards, Sunil On 6/1/11 9:58 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday May 31, 2011, Sunil Venkatesh wrote: Hi, I used the steps that were mentioned under https://cwiki.apache.org/confluence/display/VCL/Adding+support+for+parti mag e+and+partimage- ng+to+xCAT+2.x+%28unofficial%29 to enable partimage support for xcat. I wasn't sure if I need to change references to x86 x86_64 (as directories) to reflect the ppc architecture, as the web page says The architecture for the node must always be set to x86 for this... I have with me the vmlinuz (kernel image) and initrd for the capture process. The 2 nodeset commands By this, do you mean you have vmlinuz and initrd for your power blades, not the ones linked to off of the page you listed above? If you do, that's a good start. However, you'll also need rootimg.gz. rootimg.gz is the root filesystem for the stateless image. It also contains the partimage and partimageng binaries. Assuming partimage or partimageng can actually capture partitions from power systems, you'll need to compile at least one of them to run on power. For the rootimg.gz image I provided, I compiled them statically so that I didn't have to worry about including any library dependencies in rootimg.gz. It would be a good idea to research how to use xcat's genimage command to generate stateless images to learn how to do this. If there's any part of the above that you don't fully understand, please ask me to clarify it. Until you have a stateless image that you can deploy to your power blades, there's no point in trying to debug any VCL specific items. 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) iEYEARECAAYFAk3mRYsACgkQV/LQcNdtPQNnVgCbB9ZFJn0+C45RC/g75RqGZY/j PZYAniP2Eam7nxgiDWUnp5sKPYPO4OMa =exBV -END PGP SIGNATURE-
[VCL 2.2.1] [Power7] Problem with image reservation
Hi, We are currently in the process of configuring VCL 2.2.1 to work on a Power 7 blade. Our current setup is: 1. A web-server that hosts the Database and the Web Code. The same server acts as the Management node. xCAT is configured as the provisioning module on this node. 2. Power7 is our compute node. 3. I used the command vcld --setup command to create/capture base image of RHEL 5 that is running on the Power7 blade (by specifying the IP address of Power7 blade when prompted for an address). The creation process failed as Xianqing Yu had mentioned to us earlier. Although, before it failed it created appropriate entries in the tables image, imagerevision and resource. I was able to Undelete the image from the web page and see it under New Reservations. I am facing similar problems that Mike Waldron had faced with the reservation. Even after making memory adjustment, I wasn't able to make a reservation. The time table shows all green (available), however, when I choose any entry from the list, it takes me directly to New Reservation page without any status/feedback. And, I don't see any reservations created when I check under Current Reservations. I am just assuming the groupings of Images and Computers are correct, is there anyway I could verify the same. Also, if there is any reference to how the grouping need to be done, please let me know of the same. Please do correct me if there is anything wrong with the system setup. Regards, Sunil Venkatesh Research Assistant, MC2 Lab, UMBC.
