Re: Xcat image capture issues

2012-03-16 Thread Dmitri Chebotarov
Evelio

What type of hardware d6100a is? If it doesn't have IPMI enabled motherboard or 
IPMI card, r* commands may not work. 
By the name I would guess it's Latitude d610...

Try rebooting manually just to test xCAT/PXE.

Thanks.

On Mar 15, 2012, at 12:03 , Evelio Quiros wrote:

 Hello,
 
 Yes, both listener.py and rootimg.gz are both located at
 /install/image/x86/installer_files/
 
 
 But NOWHERE on the documentation page does it mention a symlink between
 x86_64 and x86.
 
 Ok, I added the symlinks in both locations, and it did seem to accept it:
 
 nodeset d6100a image
 d6100a: image image-x86_64-rh5image-rh66-v0
 
 Which created this file in /tftpboot/pxelinux.cfg:
 
 
 lrwxrwxrwx 1 root root   6 Mar 15 11:36 0A19 - d6100a
 
 cat d6100a 
 #image image-x86_64-rh5image-rh66-v0
 DEFAULT xCAT
 LABEL xCAT
 KERNEL xcat/image/x86_64/vmlinuz
 APPEND initrd=xcat/image/x86_64/initrd.img
 imgurl=http://10.0.0.3//install/image/x86_64/installer_files/rootimg.gz
 image=/install/image/x86_64/rh5image-rh66-v0.img blocks=512 action=save
 installnic=eth0 reboot  noipv6
  IPAPPEND 2
 
 I did a tabedit to add the nodetype.supportedarchs.
 
 
 tabdump nodetype
 #node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
 compute,rh6.0,x86_64,compute,,,osi,,
 d6100a,image,x86,rh5image-rh66-v0,image,x86,x86_64,,,
 
 
 
 However, when I do this:
 rpower d6100a reset
 
 I get this:
 d6100a: Error: timeout
 
 So, I guess I must be missing something that tells xCAT where the machine
 is, and how to reach it.
 
 
 Al Q
 
 
 On 3/15/12 11:05 AM, Dmitri Chebotarov dcheb...@gmu.edu wrote:
 
 Evelio
 
 Could you please check that you have these files/folders as well?
 
 /install/image/x86/installer_files/listener.py
 /install/image/x86/installer_files/rootimg.gz
 
 Also, can you check that there are symlinks for x86 or x86_64 in
 /install/image/ and /tftpboot/xcat/image/, ie:
 
 $ ls -l
 x86
 x86_64 - x86
 
 Thanks.
 
 On Mar 15, 2012, at 9:56 , Evelio Quiros wrote:
 
 Thanks Dmitri,
 
 In following this article, I get to the bottom of the page, where I put
 in
 the 3 files needed for a stateless image.
 
 I place the 3 files in the located indicated, and when I run
 
 nodeset d6100a image
 
 I get this:
 
 Error: vmlinuz and initrd.img not found at /tftpboot/xcat/image/x86_64
 Error: Some nodes failed to set up image resources, aborting
 
 But vmlinuz and initrd.img are at /tftpboot/xcat/image/x86_64
 
 
 Is there something else that needs to happen first ?
 
 
 Also, the last step talks about NFS servers for the image store.
 Are these required ?
 
 Thanks for all your help,
 Al Quiros
 
 
 
 On 3/14/12 4:05 PM, Dmitri Chebotarov 4dim...@gmail.com wrote:
 
 Evelio 
 
 Please follow this article to add support for 'image' and 'install' :
 
 
 https://cwiki.apache.org/VCL/adding-support-for-partimage-and-partimage-
 ng
 -to-xcat-2x-unofficial.html
 
 Thanks. 
 
 -- 
 Dmitri Chebotarov
 
 
 On Wednesday, March 14, 2012 at 15:37 , Evelio Quiros wrote:
 
 Hello again,
 
 Dimitri, thanks for the advice.
 
 I have a question about these commands.
 Below, you wrote nodeset d6100a image,
 
 But there is no image argument for nodeset.
 Here is the man page:
 
 nodeset [-h|--help|-v|--version]
 nodeset noderange
 
 
 [install|shell|boot|runcmd=bmcsetup|netboot|iscsiboot|osimage=imagenam
 e
 |s
 tatelite]
 
 When I try the command as-is, I get this:
 
 
 nodeset d6100a image
 d6100a: Error: Unable to identify plugin for this command, check
 relevant
 tables: nodetype.os
 Error: Some nodes failed to set up image resources, aborting
 
 I have done tabdump on the various tables, and done tabedit to modify
 them
 to my environment.
 
 
 I know this is not an xCAT list, but your guidance would be
 appreciated.
 
 Thanks,
 Al Quiros
 
 
 
 On 3/13/12 4:45 PM, Dmitri Chebotarov dcheb...@gmu.edu
 (mailto:dcheb...@gmu.edu) wrote:
 
 Evelio,
 
 You should be able to capture image via xCAT before you can use
 VCL/xCAT.
 
 To capture image via xCAT:
 
 nodech d6100a nodetype.os=image nodetype.profile=rh5image-rh66-v0
 nodeset d6100a image - this will create PXEboot config file for
 d6100a:
 
 cat /tftpboot/pxelinux.cfg/d6100a-PXE-if-mac
 
 #image rh5image-rh66-v0
 DEFAULT xCAT
 LABEL xCAT
 KERNEL xcat/image/x86_64/vmlinuz
 APPEND initrd=xcat/image/x86_64/initrd.img
 
 
 imgurl=http://xcat-master/install/image/x86_64/installer_files/rootimg.
 gz
 image=/install/image/x86_64/rh5image-rh66-v0.img blocks=512
 action=save installnic=eth0 reboot noipv6
 IPAPPEND 2
 
 'tabdump nodetype' should look similar to this - note that arch is
 x86:
 
 
 
 #node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disab
 le
 ...
 d6100a,image,x86,rh5image-rh66-v0,image,x86,x86_64,,,
 ...
 
 Then do 'rpower d6100a reset'. This will restart d6100a and when node
 boots over PXE it will boot into
 http://xcat-master/install/image/x86_64/installer_files/rootimg.gz
 and,
 given that image works fine and maps NFS store OK, it dump hd image
 to
 

Re: Xcat image capture issues

2012-03-15 Thread Evelio Quiros
Thanks Dmitri,

In following this article, I get to the bottom of the page, where I put in
the 3 files needed for a stateless image.

I place the 3 files in the located indicated, and when I run

nodeset d6100a image

I get this:

Error: vmlinuz and initrd.img not found at /tftpboot/xcat/image/x86_64
Error: Some nodes failed to set up image resources, aborting

But vmlinuz and initrd.img are at /tftpboot/xcat/image/x86_64


Is there something else that needs to happen first ?


Also, the last step talks about NFS servers for the image store.
Are these required ?

Thanks for all your help,
Al Quiros



On 3/14/12 4:05 PM, Dmitri Chebotarov 4dim...@gmail.com wrote:

Evelio 

Please follow this article to add support for 'image' and 'install' :

https://cwiki.apache.org/VCL/adding-support-for-partimage-and-partimage-ng
-to-xcat-2x-unofficial.html

Thanks. 

-- 
Dmitri Chebotarov


On Wednesday, March 14, 2012 at 15:37 , Evelio Quiros wrote:

 Hello again,
 
 Dimitri, thanks for the advice.
 
 I have a question about these commands.
 Below, you wrote nodeset d6100a image,
 
 But there is no image argument for nodeset.
 Here is the man page:
 
 nodeset [-h|--help|-v|--version]
 nodeset noderange
 
[install|shell|boot|runcmd=bmcsetup|netboot|iscsiboot|osimage=imagename
|s
 tatelite]
 
 When I try the command as-is, I get this:
 
 
 nodeset d6100a image
 d6100a: Error: Unable to identify plugin for this command, check
relevant
 tables: nodetype.os
 Error: Some nodes failed to set up image resources, aborting
 
 I have done tabdump on the various tables, and done tabedit to modify
them
 to my environment.
 
 
 I know this is not an xCAT list, but your guidance would be appreciated.
 
 Thanks,
 Al Quiros
 
 
 
 On 3/13/12 4:45 PM, Dmitri Chebotarov dcheb...@gmu.edu
(mailto:dcheb...@gmu.edu) wrote:
 
  Evelio,
  
  You should be able to capture image via xCAT before you can use
VCL/xCAT.
  
  To capture image via xCAT:
  
  nodech d6100a nodetype.os=image nodetype.profile=rh5image-rh66-v0
  nodeset d6100a image - this will create PXEboot config file for
d6100a:
  
  cat /tftpboot/pxelinux.cfg/d6100a-PXE-if-mac
  
  #image rh5image-rh66-v0
  DEFAULT xCAT
  LABEL xCAT
  KERNEL xcat/image/x86_64/vmlinuz
  APPEND initrd=xcat/image/x86_64/initrd.img
  
imgurl=http://xcat-master/install/image/x86_64/installer_files/rootimg.gz
  image=/install/image/x86_64/rh5image-rh66-v0.img blocks=512
  action=save installnic=eth0 reboot noipv6
  IPAPPEND 2
  
  'tabdump nodetype' should look similar to this - note that arch is
x86:
  
  
#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
  ...
  d6100a,image,x86,rh5image-rh66-v0,image,x86,x86_64,,,
  ...
  
  Then do 'rpower d6100a reset'. This will restart d6100a and when node
  boots over PXE it will boot into
  http://xcat-master/install/image/x86_64/installer_files/rootimg.gz
and,
  given that image works fine and maps NFS store OK, it dump hd image to
  /install/image/x86_64/rh5image-rh66-v0.img .
  
  If it's successful then to install from the image:
  
  nodeset d6100a install
  
  'tabdump nodetype' should look similar to this - provmethod changes
from
  image to install:
  
  
#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
  ...
  d6100a,image,x86,rh5image-rh66-v0,install,x86,x86_64,,,
  ...
  
  If these steps work OK, then you can use VCL to capture bare-metal
image.
  VCL uses 'nodeset node image' and 'nodeset node install'
commands, so
  it's good idea to make them work before using VCL.
  
  Thanks.
  On Mar 13, 2012, at 16:11 , Evelio Quiros wrote:
  
   Hello Again,
   
   After trying again to capture a running image on a bare metal node,
I
   get
   a failure message:
   Any ideas ?
   
   Al Q
   
   
   Added new image to database: 'rh6'
   image.name (http://image.name): rh5image-rh66-v0
   image.id: 6
   imagerevision.id: 6
   imagemeta.id: 3
   resource.id: 16
   
   
   
-
   --
   -
   Inserted imaging request to the database:
   request ID: 1
   reservation ID: 1
   
   This process will now display the contents of the vcld.log file if
the
   vcld
   daemon is running. If you do not see many lines of additional
output,
   exit
   this
   process, start the vcld daemon, and monitor the image capture
process by
   running
   the command:
   tail -f /var/log/vcld.log | grep '1:1'
   
   
   
-
   --
   -
   2012-03-13 16:03:34|2012|vcld:main(167)|lastcheckin time updated for
   management node 1: 2012-03-13 16:03:34
   2012-03-13 
16:03:39|6899|utils.pm:setup_get_array_choice(9947)|choices
   argument:
   2012-03-13 16:03:39|2012|vcld:main(167)|lastcheckin time updated for
   management node 1: 2012-03-13 16:03:39
   2012-03-13 16:03:44|2012|vcld:main(167)|lastcheckin time updated for
   management node 1: 2012-03-13 16:03:44
   2012-03-13 

Re: Xcat image capture issues

2012-03-15 Thread Dmitri Chebotarov
Evelio

Could you please check that you have these files/folders as well?

/install/image/x86/installer_files/listener.py
/install/image/x86/installer_files/rootimg.gz

Also, can you check that there are symlinks for x86 or x86_64 in 
/install/image/ and /tftpboot/xcat/image/, ie:

$ ls -l
x86
x86_64 - x86

Thanks.

On Mar 15, 2012, at 9:56 , Evelio Quiros wrote:

 Thanks Dmitri,
 
 In following this article, I get to the bottom of the page, where I put in
 the 3 files needed for a stateless image.
 
 I place the 3 files in the located indicated, and when I run
 
 nodeset d6100a image
 
 I get this:
 
 Error: vmlinuz and initrd.img not found at /tftpboot/xcat/image/x86_64
 Error: Some nodes failed to set up image resources, aborting
 
 But vmlinuz and initrd.img are at /tftpboot/xcat/image/x86_64
 
 
 Is there something else that needs to happen first ?
 
 
 Also, the last step talks about NFS servers for the image store.
 Are these required ?
 
 Thanks for all your help,
 Al Quiros
 
 
 
 On 3/14/12 4:05 PM, Dmitri Chebotarov 4dim...@gmail.com wrote:
 
 Evelio 
 
 Please follow this article to add support for 'image' and 'install' :
 
 https://cwiki.apache.org/VCL/adding-support-for-partimage-and-partimage-ng
 -to-xcat-2x-unofficial.html
 
 Thanks. 
 
 -- 
 Dmitri Chebotarov
 
 
 On Wednesday, March 14, 2012 at 15:37 , Evelio Quiros wrote:
 
 Hello again,
 
 Dimitri, thanks for the advice.
 
 I have a question about these commands.
 Below, you wrote nodeset d6100a image,
 
 But there is no image argument for nodeset.
 Here is the man page:
 
 nodeset [-h|--help|-v|--version]
 nodeset noderange
 
 [install|shell|boot|runcmd=bmcsetup|netboot|iscsiboot|osimage=imagename
 |s
 tatelite]
 
 When I try the command as-is, I get this:
 
 
 nodeset d6100a image
 d6100a: Error: Unable to identify plugin for this command, check
 relevant
 tables: nodetype.os
 Error: Some nodes failed to set up image resources, aborting
 
 I have done tabdump on the various tables, and done tabedit to modify
 them
 to my environment.
 
 
 I know this is not an xCAT list, but your guidance would be appreciated.
 
 Thanks,
 Al Quiros
 
 
 
 On 3/13/12 4:45 PM, Dmitri Chebotarov dcheb...@gmu.edu
 (mailto:dcheb...@gmu.edu) wrote:
 
 Evelio,
 
 You should be able to capture image via xCAT before you can use
 VCL/xCAT.
 
 To capture image via xCAT:
 
 nodech d6100a nodetype.os=image nodetype.profile=rh5image-rh66-v0
 nodeset d6100a image - this will create PXEboot config file for
 d6100a:
 
 cat /tftpboot/pxelinux.cfg/d6100a-PXE-if-mac
 
 #image rh5image-rh66-v0
 DEFAULT xCAT
 LABEL xCAT
 KERNEL xcat/image/x86_64/vmlinuz
 APPEND initrd=xcat/image/x86_64/initrd.img
 
 imgurl=http://xcat-master/install/image/x86_64/installer_files/rootimg.gz
 image=/install/image/x86_64/rh5image-rh66-v0.img blocks=512
 action=save installnic=eth0 reboot noipv6
 IPAPPEND 2
 
 'tabdump nodetype' should look similar to this - note that arch is
 x86:
 
 
 #node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
 ...
 d6100a,image,x86,rh5image-rh66-v0,image,x86,x86_64,,,
 ...
 
 Then do 'rpower d6100a reset'. This will restart d6100a and when node
 boots over PXE it will boot into
 http://xcat-master/install/image/x86_64/installer_files/rootimg.gz
 and,
 given that image works fine and maps NFS store OK, it dump hd image to
 /install/image/x86_64/rh5image-rh66-v0.img .
 
 If it's successful then to install from the image:
 
 nodeset d6100a install
 
 'tabdump nodetype' should look similar to this - provmethod changes
 from
 image to install:
 
 
 #node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
 ...
 d6100a,image,x86,rh5image-rh66-v0,install,x86,x86_64,,,
 ...
 
 If these steps work OK, then you can use VCL to capture bare-metal
 image.
 VCL uses 'nodeset node image' and 'nodeset node install'
 commands, so
 it's good idea to make them work before using VCL.
 
 Thanks.
 On Mar 13, 2012, at 16:11 , Evelio Quiros wrote:
 
 Hello Again,
 
 After trying again to capture a running image on a bare metal node,
 I
 get
 a failure message:
 Any ideas ?
 
 Al Q
 
 
 Added new image to database: 'rh6'
 image.name (http://image.name): rh5image-rh66-v0
 image.id: 6
 imagerevision.id: 6
 imagemeta.id: 3
 resource.id: 16
 
 
 
 -
 --
 -
 Inserted imaging request to the database:
 request ID: 1
 reservation ID: 1
 
 This process will now display the contents of the vcld.log file if
 the
 vcld
 daemon is running. If you do not see many lines of additional
 output,
 exit
 this
 process, start the vcld daemon, and monitor the image capture
 process by
 running
 the command:
 tail -f /var/log/vcld.log | grep '1:1'
 
 
 
 -
 --
 -
 2012-03-13 16:03:34|2012|vcld:main(167)|lastcheckin time updated for
 management node 1: 2012-03-13 16:03:34
 2012-03-13 
 

Re: Xcat image capture issues

2012-03-15 Thread Evelio Quiros
Hello,

Yes, both listener.py and rootimg.gz are both located at
/install/image/x86/installer_files/


But NOWHERE on the documentation page does it mention a symlink between
x86_64 and x86.

Ok, I added the symlinks in both locations, and it did seem to accept it:

nodeset d6100a image
d6100a: image image-x86_64-rh5image-rh66-v0

Which created this file in /tftpboot/pxelinux.cfg:


lrwxrwxrwx 1 root root   6 Mar 15 11:36 0A19 - d6100a

cat d6100a 
#image image-x86_64-rh5image-rh66-v0
DEFAULT xCAT
LABEL xCAT
 KERNEL xcat/image/x86_64/vmlinuz
 APPEND initrd=xcat/image/x86_64/initrd.img
imgurl=http://10.0.0.3//install/image/x86_64/installer_files/rootimg.gz
image=/install/image/x86_64/rh5image-rh66-v0.img blocks=512 action=save
installnic=eth0 reboot  noipv6
  IPAPPEND 2

I did a tabedit to add the nodetype.supportedarchs.


tabdump nodetype
#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
compute,rh6.0,x86_64,compute,,,osi,,
d6100a,image,x86,rh5image-rh66-v0,image,x86,x86_64,,,



However, when I do this:
rpower d6100a reset

I get this:
d6100a: Error: timeout

So, I guess I must be missing something that tells xCAT where the machine
is, and how to reach it.


Al Q


On 3/15/12 11:05 AM, Dmitri Chebotarov dcheb...@gmu.edu wrote:

Evelio

Could you please check that you have these files/folders as well?

/install/image/x86/installer_files/listener.py
/install/image/x86/installer_files/rootimg.gz

Also, can you check that there are symlinks for x86 or x86_64 in
/install/image/ and /tftpboot/xcat/image/, ie:

$ ls -l
x86
x86_64 - x86

Thanks.

On Mar 15, 2012, at 9:56 , Evelio Quiros wrote:

 Thanks Dmitri,
 
 In following this article, I get to the bottom of the page, where I put
in
 the 3 files needed for a stateless image.
 
 I place the 3 files in the located indicated, and when I run
 
 nodeset d6100a image
 
 I get this:
 
 Error: vmlinuz and initrd.img not found at /tftpboot/xcat/image/x86_64
 Error: Some nodes failed to set up image resources, aborting
 
 But vmlinuz and initrd.img are at /tftpboot/xcat/image/x86_64
 
 
 Is there something else that needs to happen first ?
 
 
 Also, the last step talks about NFS servers for the image store.
 Are these required ?
 
 Thanks for all your help,
 Al Quiros
 
 
 
 On 3/14/12 4:05 PM, Dmitri Chebotarov 4dim...@gmail.com wrote:
 
 Evelio 
 
 Please follow this article to add support for 'image' and 'install' :
 
 
https://cwiki.apache.org/VCL/adding-support-for-partimage-and-partimage-
ng
 -to-xcat-2x-unofficial.html
 
 Thanks. 
 
 -- 
 Dmitri Chebotarov
 
 
 On Wednesday, March 14, 2012 at 15:37 , Evelio Quiros wrote:
 
 Hello again,
 
 Dimitri, thanks for the advice.
 
 I have a question about these commands.
 Below, you wrote nodeset d6100a image,
 
 But there is no image argument for nodeset.
 Here is the man page:
 
 nodeset [-h|--help|-v|--version]
 nodeset noderange
 
 
[install|shell|boot|runcmd=bmcsetup|netboot|iscsiboot|osimage=imagenam
e
 |s
 tatelite]
 
 When I try the command as-is, I get this:
 
 
 nodeset d6100a image
 d6100a: Error: Unable to identify plugin for this command, check
 relevant
 tables: nodetype.os
 Error: Some nodes failed to set up image resources, aborting
 
 I have done tabdump on the various tables, and done tabedit to modify
 them
 to my environment.
 
 
 I know this is not an xCAT list, but your guidance would be
appreciated.
 
 Thanks,
 Al Quiros
 
 
 
 On 3/13/12 4:45 PM, Dmitri Chebotarov dcheb...@gmu.edu
 (mailto:dcheb...@gmu.edu) wrote:
 
 Evelio,
 
 You should be able to capture image via xCAT before you can use
 VCL/xCAT.
 
 To capture image via xCAT:
 
 nodech d6100a nodetype.os=image nodetype.profile=rh5image-rh66-v0
 nodeset d6100a image - this will create PXEboot config file for
 d6100a:
 
 cat /tftpboot/pxelinux.cfg/d6100a-PXE-if-mac
 
 #image rh5image-rh66-v0
 DEFAULT xCAT
 LABEL xCAT
 KERNEL xcat/image/x86_64/vmlinuz
 APPEND initrd=xcat/image/x86_64/initrd.img
 
 
imgurl=http://xcat-master/install/image/x86_64/installer_files/rootimg.
gz
 image=/install/image/x86_64/rh5image-rh66-v0.img blocks=512
 action=save installnic=eth0 reboot noipv6
 IPAPPEND 2
 
 'tabdump nodetype' should look similar to this - note that arch is
 x86:
 
 
 
#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disab
le
 ...
 d6100a,image,x86,rh5image-rh66-v0,image,x86,x86_64,,,
 ...
 
 Then do 'rpower d6100a reset'. This will restart d6100a and when node
 boots over PXE it will boot into
 http://xcat-master/install/image/x86_64/installer_files/rootimg.gz
 and,
 given that image works fine and maps NFS store OK, it dump hd image
to
 /install/image/x86_64/rh5image-rh66-v0.img .
 
 If it's successful then to install from the image:
 
 nodeset d6100a install
 
 'tabdump nodetype' should look similar to this - provmethod changes
 from
 image to install:
 
 
 
#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disab
le
 ...
 d6100a,image,x86,rh5image-rh66-v0,install,x86,x86_64,,,
 ...

Re: Xcat image capture issues

2012-03-14 Thread Evelio Quiros
Hello again,

Dimitri, thanks for the advice.

I have a question about these commands.
Below, you wrote nodeset d6100a image,

But there is no image argument for nodeset.
Here is the man page:

  nodeset [-h|--help|-v|--version]
  nodeset noderange
[install|shell|boot|runcmd=bmcsetup|netboot|iscsiboot|osimage=imagename|s
tatelite]

When I try the command as-is, I get this:


nodeset d6100a image
d6100a: Error: Unable to identify plugin for this command, check relevant
tables: nodetype.os
Error: Some nodes failed to set up image resources, aborting

I have done tabdump on the various tables, and done tabedit to modify them
to my environment.


I know this is not an xCAT list, but your guidance would be appreciated.

Thanks,
Al Quiros



On 3/13/12 4:45 PM, Dmitri Chebotarov dcheb...@gmu.edu wrote:

Evelio,

You should be able to capture image via xCAT before you can use VCL/xCAT.

To capture image via xCAT:

nodech  d6100a  nodetype.os=image nodetype.profile=rh5image-rh66-v0
nodeset d6100a image - this will create PXEboot config file for d6100a:

cat /tftpboot/pxelinux.cfg/d6100a-PXE-if-mac

   #image rh5image-rh66-v0
   DEFAULT xCAT
   LABEL xCAT
   KERNEL xcat/image/x86_64/vmlinuz
   APPEND initrd=xcat/image/x86_64/initrd.img
imgurl=http://xcat-master/install/image/x86_64/installer_files/rootimg.gz
image=/install/image/x86_64/rh5image-rh66-v0.img   
blocks=512
action=save installnic=eth0 reboot  noipv6
   IPAPPEND 2

'tabdump nodetype' should look similar to this - note that arch is x86:

#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
...
d6100a,image,x86,rh5image-rh66-v0,image,x86,x86_64,,,
...

Then do 'rpower d6100a reset'. This will restart d6100a and when node
boots over PXE it will boot into
http://xcat-master/install/image/x86_64/installer_files/rootimg.gz and,
given that image works fine and maps NFS store OK, it dump hd image to
/install/image/x86_64/rh5image-rh66-v0.img .

If it's successful then to install from the image:

nodeset d6100a install

'tabdump nodetype' should look similar to this - provmethod changes from
image to install:

#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
...
d6100a,image,x86,rh5image-rh66-v0,install,x86,x86_64,,,
...

If these steps work OK, then you can use VCL to capture bare-metal image.
VCL uses 'nodeset node image' and 'nodeset node install' commands, so
it's good idea to make them work before using VCL.

Thanks.
On Mar 13, 2012, at 16:11 , Evelio Quiros wrote:

 Hello Again,
 
 After trying again to capture a running image on a bare metal node, I
get
 a failure message:
 Any ideas ?
 
 Al Q
 
 
 Added new image to database: 'rh6'
   image.name: rh5image-rh66-v0
   image.id: 6
   imagerevision.id: 6
   imagemeta.id: 3
   resource.id: 16
 
 
-
--
 -
 Inserted imaging request to the database:
 request ID: 1
 reservation ID: 1
 
 This process will now display the contents of the vcld.log file if the
vcld
 daemon is running. If you do not see many lines of additional output,
exit
 this
 process, start the vcld daemon, and monitor the image capture process by
 running
 the command:
 tail -f /var/log/vcld.log | grep '1:1'
 
 
-
--
 -
 2012-03-13 16:03:34|2012|vcld:main(167)|lastcheckin time updated for
 management node 1: 2012-03-13 16:03:34
 2012-03-13 16:03:39|6899|utils.pm:setup_get_array_choice(9947)|choices
 argument:
 2012-03-13 16:03:39|2012|vcld:main(167)|lastcheckin time updated for
 management node 1: 2012-03-13 16:03:39
 2012-03-13 16:03:44|2012|vcld:main(167)|lastcheckin time updated for
 management node 1: 2012-03-13 16:03:44
 2012-03-13 16:03:48|6899|utils.pm:insert_request(8358)|inserted new
reload
 request into request table, request id=1
 2012-03-13 16:03:48|6899|utils.pm:insert_request(8389)|inserted new
reload
 request into reservation table, reservation id=1
 2012-03-13 16:03:50|2012|vcld:main(167)|lastcheckin time updated for
 management node 1: 2012-03-13 16:03:49
 2012-03-13 
 
16:03:50|2012|1:1|image|utils.pm:reservation_being_processed(8938)|comput
er
 loadlog 'begin' entry does NOT exist for reservation 1
 2012-03-13 16:03:50|2012|1:1|image|utils.pm:run_command(9010)|executed
 command: pgrep -fl 'vcld [0-9]+:1 ', pid: 7004, exit status: 0, output:
 2012-03-13 
 
16:03:50|2012|1:1|image|utils.pm:is_management_node_process_running(9192)
|p
 rocess is NOT running, identifier: 'vcld [0-9]+:1 '
 2012-03-13 
 
16:03:50|2012|1:1|image|utils.pm:reservation_being_processed(8959)|reserv
at
 ion is NOT currently being processed
 2012-03-13 16:03:50|2012|1:1|image|vcld:main(278)|reservation 1 is NOT
 already being processed
 2012-03-13 
 16:03:50|2012|1:1|image|utils.pm:get_request_info(4520)|standalone
 affiliation found: Local
 2012-03-13 

Re: Xcat image capture issues

2012-03-14 Thread Dmitri Chebotarov
Evelio 

Please follow this article to add support for 'image' and 'install' :

https://cwiki.apache.org/VCL/adding-support-for-partimage-and-partimage-ng-to-xcat-2x-unofficial.html

Thanks. 

-- 
Dmitri Chebotarov


On Wednesday, March 14, 2012 at 15:37 , Evelio Quiros wrote:

 Hello again,
 
 Dimitri, thanks for the advice.
 
 I have a question about these commands.
 Below, you wrote nodeset d6100a image,
 
 But there is no image argument for nodeset.
 Here is the man page:
 
 nodeset [-h|--help|-v|--version]
 nodeset noderange
 [install|shell|boot|runcmd=bmcsetup|netboot|iscsiboot|osimage=imagename|s
 tatelite]
 
 When I try the command as-is, I get this:
 
 
 nodeset d6100a image
 d6100a: Error: Unable to identify plugin for this command, check relevant
 tables: nodetype.os
 Error: Some nodes failed to set up image resources, aborting
 
 I have done tabdump on the various tables, and done tabedit to modify them
 to my environment.
 
 
 I know this is not an xCAT list, but your guidance would be appreciated.
 
 Thanks,
 Al Quiros
 
 
 
 On 3/13/12 4:45 PM, Dmitri Chebotarov dcheb...@gmu.edu 
 (mailto:dcheb...@gmu.edu) wrote:
 
  Evelio,
  
  You should be able to capture image via xCAT before you can use VCL/xCAT.
  
  To capture image via xCAT:
  
  nodech d6100a nodetype.os=image nodetype.profile=rh5image-rh66-v0
  nodeset d6100a image - this will create PXEboot config file for d6100a:
  
  cat /tftpboot/pxelinux.cfg/d6100a-PXE-if-mac
  
  #image rh5image-rh66-v0
  DEFAULT xCAT
  LABEL xCAT
  KERNEL xcat/image/x86_64/vmlinuz
  APPEND initrd=xcat/image/x86_64/initrd.img
  imgurl=http://xcat-master/install/image/x86_64/installer_files/rootimg.gz
  image=/install/image/x86_64/rh5image-rh66-v0.img blocks=512
  action=save installnic=eth0 reboot noipv6
  IPAPPEND 2
  
  'tabdump nodetype' should look similar to this - note that arch is x86:
  
  #node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
  ...
  d6100a,image,x86,rh5image-rh66-v0,image,x86,x86_64,,,
  ...
  
  Then do 'rpower d6100a reset'. This will restart d6100a and when node
  boots over PXE it will boot into
  http://xcat-master/install/image/x86_64/installer_files/rootimg.gz and,
  given that image works fine and maps NFS store OK, it dump hd image to
  /install/image/x86_64/rh5image-rh66-v0.img .
  
  If it's successful then to install from the image:
  
  nodeset d6100a install
  
  'tabdump nodetype' should look similar to this - provmethod changes from
  image to install:
  
  #node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
  ...
  d6100a,image,x86,rh5image-rh66-v0,install,x86,x86_64,,,
  ...
  
  If these steps work OK, then you can use VCL to capture bare-metal image.
  VCL uses 'nodeset node image' and 'nodeset node install' commands, so
  it's good idea to make them work before using VCL.
  
  Thanks.
  On Mar 13, 2012, at 16:11 , Evelio Quiros wrote:
  
   Hello Again,
   
   After trying again to capture a running image on a bare metal node, I
   get
   a failure message:
   Any ideas ?
   
   Al Q
   
   
   Added new image to database: 'rh6'
   image.name (http://image.name): rh5image-rh66-v0
   image.id: 6
   imagerevision.id: 6
   imagemeta.id: 3
   resource.id: 16
   
   
   -
   --
   -
   Inserted imaging request to the database:
   request ID: 1
   reservation ID: 1
   
   This process will now display the contents of the vcld.log file if the
   vcld
   daemon is running. If you do not see many lines of additional output,
   exit
   this
   process, start the vcld daemon, and monitor the image capture process by
   running
   the command:
   tail -f /var/log/vcld.log | grep '1:1'
   
   
   -
   --
   -
   2012-03-13 16:03:34|2012|vcld:main(167)|lastcheckin time updated for
   management node 1: 2012-03-13 16:03:34
   2012-03-13 16:03:39|6899|utils.pm:setup_get_array_choice(9947)|choices
   argument:
   2012-03-13 16:03:39|2012|vcld:main(167)|lastcheckin time updated for
   management node 1: 2012-03-13 16:03:39
   2012-03-13 16:03:44|2012|vcld:main(167)|lastcheckin time updated for
   management node 1: 2012-03-13 16:03:44
   2012-03-13 16:03:48|6899|utils.pm:insert_request(8358)|inserted new
   reload
   request into request table, request id=1
   2012-03-13 16:03:48|6899|utils.pm:insert_request(8389)|inserted new
   reload
   request into reservation table, reservation id=1
   2012-03-13 16:03:50|2012|vcld:main(167)|lastcheckin time updated for
   management node 1: 2012-03-13 16:03:49
   2012-03-13 
   
   16:03:50|2012|1:1|image|utils.pm:reservation_being_processed(8938)|comput
   er
   loadlog 'begin' entry does NOT exist for reservation 1
   2012-03-13 16:03:50|2012|1:1|image|utils.pm:run_command(9010)|executed
   command: pgrep -fl 'vcld [0-9]+:1 ', pid: 7004, exit status: 0, output:
   2012-03-13 
   
   

Re: Xcat image capture issues

2012-03-13 Thread Dmitri Chebotarov
Evelio,

You should be able to capture image via xCAT before you can use VCL/xCAT. 

To capture image via xCAT:

nodech  d6100a  nodetype.os=image nodetype.profile=rh5image-rh66-v0
nodeset d6100a image - this will create PXEboot config file for d6100a:

cat /tftpboot/pxelinux.cfg/d6100a-PXE-if-mac

#image rh5image-rh66-v0
DEFAULT xCAT
LABEL xCAT
KERNEL xcat/image/x86_64/vmlinuz
APPEND initrd=xcat/image/x86_64/initrd.img 
imgurl=http://xcat-master/install/image/x86_64/installer_files/rootimg.gz 
image=/install/image/x86_64/rh5image-rh66-v0.img   blocks=512 
action=save installnic=eth0 reboot  noipv6
IPAPPEND 2

'tabdump nodetype' should look similar to this - note that arch is x86:

#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
...
d6100a,image,x86,rh5image-rh66-v0,image,x86,x86_64,,,
...

Then do 'rpower d6100a reset'. This will restart d6100a and when node boots 
over PXE it will boot into  
http://xcat-master/install/image/x86_64/installer_files/rootimg.gz and, given 
that image works fine and maps NFS store OK, it dump hd image to 
/install/image/x86_64/rh5image-rh66-v0.img .

If it's successful then to install from the image:

nodeset d6100a install

'tabdump nodetype' should look similar to this - provmethod changes from image 
to install:

#node,os,arch,profile,provmethod,supportedarchs,nodetype,comments,disable
...
d6100a,image,x86,rh5image-rh66-v0,install,x86,x86_64,,,
...

If these steps work OK, then you can use VCL to capture bare-metal image. 
VCL uses 'nodeset node image' and 'nodeset node install' commands, so it's 
good idea to make them work before using VCL.

Thanks.
On Mar 13, 2012, at 16:11 , Evelio Quiros wrote:

 Hello Again,
 
 After trying again to capture a running image on a bare metal node, I get
 a failure message:
 Any ideas ?
 
 Al Q
 
 
 Added new image to database: 'rh6'
   image.name: rh5image-rh66-v0
   image.id: 6
   imagerevision.id: 6
   imagemeta.id: 3
   resource.id: 16
 
 ---
 -
 Inserted imaging request to the database:
 request ID: 1
 reservation ID: 1
 
 This process will now display the contents of the vcld.log file if the vcld
 daemon is running. If you do not see many lines of additional output, exit
 this
 process, start the vcld daemon, and monitor the image capture process by
 running
 the command:
 tail -f /var/log/vcld.log | grep '1:1'
 
 ---
 -
 2012-03-13 16:03:34|2012|vcld:main(167)|lastcheckin time updated for
 management node 1: 2012-03-13 16:03:34
 2012-03-13 16:03:39|6899|utils.pm:setup_get_array_choice(9947)|choices
 argument:
 2012-03-13 16:03:39|2012|vcld:main(167)|lastcheckin time updated for
 management node 1: 2012-03-13 16:03:39
 2012-03-13 16:03:44|2012|vcld:main(167)|lastcheckin time updated for
 management node 1: 2012-03-13 16:03:44
 2012-03-13 16:03:48|6899|utils.pm:insert_request(8358)|inserted new reload
 request into request table, request id=1
 2012-03-13 16:03:48|6899|utils.pm:insert_request(8389)|inserted new reload
 request into reservation table, reservation id=1
 2012-03-13 16:03:50|2012|vcld:main(167)|lastcheckin time updated for
 management node 1: 2012-03-13 16:03:49
 2012-03-13 
 16:03:50|2012|1:1|image|utils.pm:reservation_being_processed(8938)|computer
 loadlog 'begin' entry does NOT exist for reservation 1
 2012-03-13 16:03:50|2012|1:1|image|utils.pm:run_command(9010)|executed
 command: pgrep -fl 'vcld [0-9]+:1 ', pid: 7004, exit status: 0, output:
 2012-03-13 
 16:03:50|2012|1:1|image|utils.pm:is_management_node_process_running(9192)|p
 rocess is NOT running, identifier: 'vcld [0-9]+:1 '
 2012-03-13 
 16:03:50|2012|1:1|image|utils.pm:reservation_being_processed(8959)|reservat
 ion is NOT currently being processed
 2012-03-13 16:03:50|2012|1:1|image|vcld:main(278)|reservation 1 is NOT
 already being processed
 2012-03-13 
 16:03:50|2012|1:1|image|utils.pm:get_request_info(4520)|standalone
 affiliation found: Local
 2012-03-13 16:03:50|2012|1:1|image|vcld:main(283)|retrieved request
 information from database
 2012-03-13 
 16:03:50|2012|1:1|image|DataStructure.pm:is_parent_reservation(991)|returni
 ng true: parent reservation ID for this request: 1
 2012-03-13 
 16:03:50|2012|1:1|image|utils.pm:update_request_state(1991)|request 1
 state updated to: pending, laststate to: image
 2012-03-13 16:03:50|2012|1:1|image|utils.pm:insertloadlog(3875)|inserted
 computer=1, begin, beginning to process, state is image
 2012-03-13 16:03:50|2012|1:1|image|vcld:make_new_child(515)|loaded
 VCL::image module
 2012-03-13 16:03:50|2012|1:1|image|vcld:make_new_child(539)|current number
 of forked kids: 1
 2012-03-13 16:03:50|7018|1:1|image|vcld:make_new_child(555)|vcld
 environment variable set to 0 for this process
 2012-03-13 

Xcat image capture issues

2012-03-07 Thread Evelio Quiros
Hello,

After working a while with VmWare images, we have started experimenting with 
Xcat bare metal images. To accommodate the added level of complexity with Xcat, 
I created a  separate development environment with VCL and some dell 6100 high 
density nodes. I have installed RHEL 6.1 with Xcat on all the nodes. Following 
the instructions on the doc page, I installed partimage to the xcat 
installation. I think its correct, except that these are not IBM blades, so I 
am unsure how to build a stateless image on this hardware. Just attempting to 
capture the image as-is failed, and the error messages are below. Is there 
any more documentation on this process, and how to make Xcat work with VCL? 
Being new to Xcat, I guess that I am missing some background material on what 
is supposed to happen here. For example, the error log states that /opt/xcat 
does not exist, but it does exist on the node I was attempting to capture.  
Does Xcat need to be on the management node too ?

The information I am using is located at:

http://sourceforge.net/apps/mediawiki/xcat/index.php?title=Setting_Up_a_Linux_xCAT_Mgmt_Node

And

https://cwiki.apache.org/VCL/adding-support-for-partimage-and-partimage-ng-to-xcat-2x-unofficial.html

Any other information available ?

Thanks,
Al Quiros
Florida International University

**

Error message from my attempt at capturing the image below:

VCL::image object could not be created and initialized

time: 2012-03-07 14:49:31
caller: vcld:make_new_child(571)
( 0) vcld, make_new_child (line: 571)
(-1) vcld, main (line: 346)

management node: vcldev01.p.fiu.edu
reservation PID: 12372
parent vcld PID: 2044

request ID: 1
reservation ID: 1
request state/laststate: image/image
request start time: 2012-03-07 14:49:30
request end time: 2012-03-07 15:49:30
for imaging: no
log ID: none

computer: 6100a
computer id: 1
computer type: blade
computer eth0 MAC address: undefined
computer eth1 MAC address: undefined
computer private IP address: 10.0.0.25
computer public IP address: 10.106.128.14
computer in block allocation: no
provisioning module: VCL::Module::Provisioning::xCAT2

image: rh5image-rh6xcat5-v0
image display name: rh6xcat
image ID: 5
image revision ID: 5
image size: 1450 MB
use Sysprep: yes
root access: yes
image owner ID: 1
image owner affiliation: Local
image revision date created: 2012-03-07 14:49:29
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:
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'id' key for 
VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'PID' key for 
VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'DURATION' key for 
VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'PPID' key for 
VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'datemodified' key 
for VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'RESERVATIONCOUNT' 
key for VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'end' key for 
VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'stateid' key for 
VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'PARENTIMAGE' key 
for VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'checkuser' key for 
VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'preload' key for 
VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'NOTICEINTERVAL' key 
for VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'start' key for 
VCL::image object from arguments
2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'logid' key for 
VCL::image object from arguments
2012-03-07 
14:49:31|12372|1:1|image|Module.pm:create_mn_os_object(361)|VCL::Module::OS::Linux::ManagementNode
 module loaded
2012-03-07 
14:49:31|12372|1:1|image|Module.pm:new(196)|VCL::Module::OS::Linux::ManagementNode
 object created for image not set, address: 2417400
2012-03-07 14:49:31|12372|1:1|image|DataStructure.pm:_automethod(834)|data 
structure updated: $self-request_data-{reservation}{0}{computer}{hostname}
|12372|1:1|image| computer_hostname = vcldev01.p.fiu.edu
2012-03-07 14:49:31|12372|1:1|image|DataStructure.pm:_automethod(834)|data 
structure updated: $self-request_data-{reservation}{0}{computer}{NODENAME}

Re: Xcat image capture issues

2012-03-07 Thread Andy Kurth
xCAT should be installed on the management node.  It doesn't need to
be installed on other machines.  There are a few different xCAT
installation instruction pages on their site.  You may want to start
with this simpler one:
http://sourceforge.net/apps/mediawiki/xcat/index.php?title=Basic_Install_DHCP

-Andy

On Wed, Mar 7, 2012 at 3:16 PM, Evelio Quiros evq...@fiu.edu wrote:
 Hello,

 After working a while with VmWare images, we have started experimenting with
 Xcat bare metal images. To accommodate the added level of complexity with
 Xcat, I created a  separate development environment with VCL and some dell
 6100 high density nodes. I have installed RHEL 6.1 with Xcat on all the
 nodes. Following the instructions on the doc page, I installed partimage to
 the xcat installation. I think its correct, except that these are not IBM
 blades, so I am unsure how to build a stateless image on this hardware. Just
 attempting to capture the image as-is failed, and the error messages are
 below. Is there any more documentation on this process, and how to make Xcat
 work with VCL? Being new to Xcat, I guess that I am missing some background
 material on what is supposed to happen here. For example, the error log
 states that /opt/xcat does not exist, but it does exist on the node I was
 attempting to capture.  Does Xcat need to be on the management node too ?

 The information I am using is located at:

 http://sourceforge.net/apps/mediawiki/xcat/index.php?title=Setting_Up_a_Linux_xCAT_Mgmt_Node

 And

 https://cwiki.apache.org/VCL/adding-support-for-partimage-and-partimage-ng-to-xcat-2x-unofficial.html

 Any other information available ?

 Thanks,
 Al Quiros
 Florida International University

 **

 Error message from my attempt at capturing the image below:

 VCL::image object could not be created and initialized
 
 time: 2012-03-07 14:49:31
 caller: vcld:make_new_child(571)
 ( 0) vcld, make_new_child (line: 571)
 (-1) vcld, main (line: 346)
 
 management node: vcldev01.p.fiu.edu
 reservation PID: 12372
 parent vcld PID: 2044

 request ID: 1
 reservation ID: 1
 request state/laststate: image/image
 request start time: 2012-03-07 14:49:30
 request end time: 2012-03-07 15:49:30
 for imaging: no
 log ID: none

 computer: 6100a
 computer id: 1
 computer type: blade
 computer eth0 MAC address: undefined
 computer eth1 MAC address: undefined
 computer private IP address: 10.0.0.25
 computer public IP address: 10.106.128.14
 computer in block allocation: no
 provisioning module: VCL::Module::Provisioning::xCAT2

 image: rh5image-rh6xcat5-v0
 image display name: rh6xcat
 image ID: 5
 image revision ID: 5
 image size: 1450 MB
 use Sysprep: yes
 root access: yes
 image owner ID: 1
 image owner affiliation: Local
 image revision date created: 2012-03-07 14:49:29
 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:
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'id' key for
 VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'PID' key for
 VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'DURATION' key
 for VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'PPID' key for
 VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'datemodified'
 key for VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set
 'RESERVATIONCOUNT' key for VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'end' key for
 VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'stateid' key for
 VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'PARENTIMAGE' key
 for VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'checkuser' key
 for VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'preload' key for
 VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'NOTICEINTERVAL'
 key for VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'start' key for
 VCL::image object from arguments
 2012-03-07 14:49:31|12372|1:1|image|Module.pm:new(172)|set 'logid' key for
 VCL::image object from arguments
 2012-03-07
 14:49:31|12372|1:1|image|Module.pm:create_mn_os_object(361)|VCL::Module::OS::Linux::ManagementNode
 module loaded
 2012-03-07