Re: [VCL 2.2.1] [Power7] Problem with image reservation
-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. > 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. > 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. 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: > computer eth1 MAC address: > computer private IP address: 172.20.106.1 > computer public IP address: 172.20.106.1 > computer in block allocation: no > provisioning module: VCL::Module::Provisioning::xCAT2 > > image: rh5image-power010701bi34-v0 > image display name: power010701bi > image ID: 34 > image revision ID: 34 > image size: 1450 MB > use Sysprep: yes > root access: yes > image owner ID: 1 > image owner affiliation: Local > image revision date created: 2011-07-05 11:03:25 > image revision production: yes > OS module: VCL::Module::OS::Linux > > user: admin > user name: vcl admin > user ID: 1 > user affiliation: Local > > RECENT LOG ENTRIES FOR THIS PROCESS: > 2011-07-05 > 11:03:25|9866|30:30|image|Module.pm:create_os_object(304)|VCL::Module::OS: > :Linux OS object created for rh5image-power010701bi34-v0, address: 88fb070 > 2011-07-05 11:03:25|9866|30:30|image|xCAT.pm:initialize(110)|XCATROOT > environment variable is not set, using /opt/xcat 2011-07-05 > 11:03:25|9866|30:30|image|xCAT.pm:initialize(128)|xCAT root path found: > /opt/xcat 2011-07-05 > 11:03:25|9866|30:30|image|xCAT.pm:initialize(130)|xCAT module initialized > 2011-07-05 11:03:25|9866|30:30|image|xCAT2.pm:initialize(110)|XCATROOT > environment variable is not set, using /opt/xcat 2011-07-05 > 11:03:25|9866|30:30|image|xCAT2.pm:initialize(128)|xCAT root path found: > /opt/xcat 2011-07-05 > 11:03:25|9866|30:30|image|xCAT2.pm:initialize(130)|xCAT module initialized > 2011-07-05 > 11:03:25|9866|30:30|image|Module.pm:create_provisioning_object(420)|VCL::M > odule::Provisioning::xCAT2 module loaded 2011-07-
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: computer eth1 MAC
Re: [VCL 2.2.1] [Power7] Problem with image reservation
-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 does VCL capture the images? does it make > use of
