Re: Sysprep not running under windows 7
Hello Roger, The code you are running (version 2.1 and earlier) was actually written for Vista and does not support Sysprep. I attempted to add Vista Sysprep support when I wrote it and decided not to use it because Vista's Sysprep took an extremely long time to complete when an image was loaded. Sysprep seems to have been updated for Windows 7 and does not take as long to run, although it's still quite a bit longer than XP. The code in the repository has been updated to use Sysprep for Vista, 7, and 2008. VCL 2.2 will include this. Sorry for the confusion, Andy Roger Herling wrote: Here is the vcld.log output for the image capture. Am I missing something obvious here to get it to sysprerp? When I create the image use sysprep is set to yes
Re: Change image timeout
The command that is being executed to check the size should be: du -c /storage/x86/image/x86/winvista-Windows7FacStaff49-v0* Try running this. What output does it generate? The last line should look like: total The code appears to be finding the 'total' line but is either not parsing it correctly, not calculating the size correctly, or the du command isn't correct. Also, it would be helpful if you include the output from: ls -l /storage/x86/image/x86/winvista-Windows7FacStaff49-v0* -Andy Waldron, Michael H wrote: So you never answered whether you watched the capture occurring from the node console. Can you watch the console and see the capture running while monitoring the log that shows the capture file is size 0? What about any other error messages for the rest of the log capture for this imaging request? Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 -Original Message- From: Roger Herling [mailto:roger.herl...@marist.edu] Sent: Monday, May 10, 2010 4:18 PM To: vcl-dev@incubator.apache.org Subject: RE: Change image timeout yup Roger Herling Sr. Desktop Administrator Marist College PH: 845-575-3347 From: Waldron, Michael H mwald...@email.unc.edu To: 'vcl-dev@incubator.apache.org' vcl-dev@incubator.apache.org Date: 05/10/2010 04:17 PM Subject: RE: Change image timeout So you can do an ls -l /storage/x86/image/x86/winvista-Windows7FacStaff49-v0 and it shows some size? Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 -Original Message- From: Roger Herling [mailto:roger.herl...@marist.edu] Sent: Monday, May 10, 2010 4:03 PM To: vcl-dev@incubator.apache.org Subject: RE: Change image timeout The image is definately being captured and I can force the image to be used after it fails by manually undeleting it from the mysql database Roger Herling Sr. Desktop Administrator Marist College PH: 845-575-3347 From: Waldron, Michael H mwald...@email.unc.edu To: 'vcl-dev@incubator.apache.org' vcl-dev@incubator.apache.org Date: 05/10/2010 04:01 PM Subject: RE: Change image timeout From these lines in the log, it's indicating that the capture hasn't started: 12:31:01|9225|144:178|image|xCAT.pm:get_image_size(3146)|returning image size: 0 MB (4 bytes) 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1258)|image size is the same: 0=0, copy may be complete 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1238)|image copy not complete, sleeping for 30 seconds Notice the image size is 0 MB, meaning the partimage save isn't occurring. After 20 minutes of nothing being saved, it gives up. Can you watch the capture from the server console to verify that the PXE boot is running and that it's booting into the image capture mode? Do the log entries at the beginning of the imaging process show any errors? Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 -Original Message- From: Roger Herling [mailto:roger.herl...@marist.edu] Sent: Monday, May 10, 2010 3:25 PM To: vcl-dev@incubator.apache.org Subject: RE: Change image timeout 010-05-10 12:31:01|9225|144:178|image|xCAT.pm:_get_image_repository_path(3271)|returning repository path for vcl.is.marist.edu: /storage/x86/image/x86 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:get_image_size(3146)|returning image size: 0 MB (4 bytes) 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1258)|image size is the same: 0=0, copy may be complete 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1238)|image copy not complete, sleeping for 30 seconds 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1239)|attempt 38/40: image copy not complete, sleeping for 30 seconds 2010-05-10 12:31:06|7448|vcld:main(165)|lastcheckin time updated for management node 1: 2010-05-10 12:31:06 2010-05-10 12:31:11|7448|vcld:main(165)|lastcheckin time updated for management node 1: 2010-05-10 12:31:11 2010-05-10 12:31:16|7448|vcld:main(165)|lastcheckin time updated for management node 1: 2010-05-10 12:31:16 2010-05-10 12:31:21|7448|vcld:main(165)|lastcheckin time updated for management node 1: 2010-05-10 12:31:21 2010-05-10 12:31:26|7448|vcld:main(165)|lastcheckin time updated for management node 1: 2010-05-10 12:31:26 2010-05-10 12:31:31|7448|vcld:main(165)|lastcheckin time updated for management node 1: 2010-05-10 12:31:31 2010-05-10 12:31:32|9225|144:178|image|xCAT.pm:_nodeset_option(1697)|node4 in image image-x86-winvista-Windows7FacStaff49-v0-all state 2010-05-10 12:31:32|9225|144:178|image|xCAT.pm:capture_monitor(1246)|nodeset status for node4: image image-x86-winvista-Windows7FacStaff49-v0-all 2010-05-10
Re: Change image timeout
[r...@vcl ~]# du -c /storage/x86/image/x86/winvista-Windows7FacStaff49-v0* 4 /storage/x86/image/x86/winvista-Windows7FacStaff49-v0.tmpl 4 total [r...@vcl ~]# ls -l /storage/x86/image/x86/winvista-Windows7FacStaff49-v0* -rw-r--r-- 1 root root 352 May 10 12:09 /storage/x86/image/x86/winvista-Windows7FacStaff49-v0.tmpl Roger Herling Sr. Desktop Administrator Marist College PH: 845-575-3347 From: Andy Kurth andy_ku...@ncsu.edu To: vcl-dev@incubator.apache.org Date: 05/11/2010 09:06 AM Subject: Re: Change image timeout The command that is being executed to check the size should be: du -c /storage/x86/image/x86/winvista-Windows7FacStaff49-v0* Try running this. What output does it generate? The last line should look like: total The code appears to be finding the 'total' line but is either not parsing it correctly, not calculating the size correctly, or the du command isn't correct. Also, it would be helpful if you include the output from: ls -l /storage/x86/image/x86/winvista-Windows7FacStaff49-v0* -Andy Waldron, Michael H wrote: So you never answered whether you watched the capture occurring from the node console. Can you watch the console and see the capture running while monitoring the log that shows the capture file is size 0? What about any other error messages for the rest of the log capture for this imaging request? Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 -Original Message- From: Roger Herling [mailto:roger.herl...@marist.edu] Sent: Monday, May 10, 2010 4:18 PM To: vcl-dev@incubator.apache.org Subject: RE: Change image timeout yup Roger Herling Sr. Desktop Administrator Marist College PH: 845-575-3347 From: Waldron, Michael H mwald...@email.unc.edu To: 'vcl-dev@incubator.apache.org' vcl-dev@incubator.apache.org Date: 05/10/2010 04:17 PM Subject: RE: Change image timeout So you can do an ls -l /storage/x86/image/x86/winvista-Windows7FacStaff49-v0 and it shows some size? Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 -Original Message- From: Roger Herling [mailto:roger.herl...@marist.edu] Sent: Monday, May 10, 2010 4:03 PM To: vcl-dev@incubator.apache.org Subject: RE: Change image timeout The image is definately being captured and I can force the image to be used after it fails by manually undeleting it from the mysql database Roger Herling Sr. Desktop Administrator Marist College PH: 845-575-3347 From: Waldron, Michael H mwald...@email.unc.edu To: 'vcl-dev@incubator.apache.org' vcl-dev@incubator.apache.org Date: 05/10/2010 04:01 PM Subject: RE: Change image timeout From these lines in the log, it's indicating that the capture hasn't started: 12:31:01|9225|144:178|image|xCAT.pm:get_image_size(3146)|returning image size: 0 MB (4 bytes) 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1258)|image size is the same: 0=0, copy may be complete 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1238)|image copy not complete, sleeping for 30 seconds Notice the image size is 0 MB, meaning the partimage save isn't occurring. After 20 minutes of nothing being saved, it gives up. Can you watch the capture from the server console to verify that the PXE boot is running and that it's booting into the image capture mode? Do the log entries at the beginning of the imaging process show any errors? Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 -Original Message- From: Roger Herling [mailto:roger.herl...@marist.edu] Sent: Monday, May 10, 2010 3:25 PM To: vcl-dev@incubator.apache.org Subject: RE: Change image timeout 010-05-10 12:31:01|9225|144:178|image|xCAT.pm:_get_image_repository_path(3271)|returning repository path for vcl.is.marist.edu: /storage/x86/image/x86 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:get_image_size(3146)|returning image size: 0 MB (4 bytes) 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1258)|image size is the same: 0=0, copy may be complete 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1238)|image copy not complete, sleeping for 30 seconds 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1239)|attempt 38/40: image copy not complete, sleeping for 30 seconds 2010-05-10 12:31:06|7448|vcld:main(165)|lastcheckin time updated for management node 1: 2010-05-10 12:31:06 2010-05-10 12:31:11|7448|vcld:main(165)|lastcheckin time updated for management node 1: 2010-05-10 12:31:11 2010-05-10 12:31:16|7448|vcld:main(165)|lastcheckin time updated for management node 1:
Re: Incubator PMC/Board report for May 2010 (vcl-dev@incubator.apache.org)
Friendly reminder -- board report is due by tomorrow, Wednesday May 12. --kevan On May 1, 2010, at 10:00 AM, no-re...@apache.org wrote: Dear VCL Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for . The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/May2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: windows 64 bit support
Good info Mike. Hopefully the next release will make this a little less painful. - Install Windows-64 hotfix for Sysnative path to work. Yes. You'll need this: http://support.microsoft.com/kb/942589 If you can't run the following command on a 64-bit installation then things won't work: dir C:\Windows\Sysnative - Create symlinks for shutdown.exe, defrag.exe in system32 folder. The code will need to be checked for these and all other calls to .exe's in System32. This won't be a requirement in the next release. - Use the Windows_Server_2003 module in the OS table for winxp64 OS. Was this required so VMware would set the guestOS setting in the .vmx file to something that worked for 64-bit, or was there another reason? - Replace Sysprep and Broadcom drivers under /usr/local/vcl/tools/Windows_Server_2003 with 64-bit versions. We'll need to design the drivers directories out a little better. As of now, the tools/Windows_version/drivers directories are copied during image capture and there are no provisions for different architectures. If you want to run both 32 and 64-bit versions of the same Windows OS, the drivers for both will be copied. This could cause conflicts if Sysprep doesn't choose the correct driver. Also add 64-bit version of spdrvscn.exe. The requirement for spdrvscn.exe has been removed in the latest code but you'll need the correct version of this utility for 2.1 and earlier. This utility scans the driver .inf files and populates the DevicePath registry key with all of the paths it finds. The vcld Perl code now does this. The new code also automatically populates the mass storage section of sysprep.inf will the paths to all of the storage .inf's it finds. -Andy
Re: Incubator PMC/Board report for May 2010 (vcl-dev@incubator.apache.org)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The report is available here: https://cwiki.apache.org/VCL/2010-05-incubator-vcl-report.html If you have any feedback, please provide it soon. I'll post the report to the Incubator PMC later this afternoon. Josh On Tuesday May 11, 2010, Kevan Miller wrote: Friendly reminder -- board report is due by tomorrow, Wednesday May 12. --kevan On May 1, 2010, at 10:00 AM, no-re...@apache.org wrote: Dear VCL Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for . The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/May2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - -- - --- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAkvpaTUACgkQV/LQcNdtPQNCfQCePR22w2+EsLMGAtfLTQ8ntJBt 9QoAniTLBSC9dzfkURrAW9q6I8+8mIdU =XiDn -END PGP SIGNATURE-
RE: windows 64 bit support
I believe at the time, I chose the Windows_Server_2003 module for 64-bit XP because it seemed to be the closest match, and we aren't running any Windows Server 2003 here, so I knew it would be safe to place 64-bit drivers in there. And I wasn't smart enough to write my own module :) I haven't created a vmware-based 64-bit XP image, only bare metal. I wanted the 64-bit version so we could take advantage of all the memory on the bare metal images. Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 -Original Message- From: Andy Kurth [mailto:andy_ku...@ncsu.edu] Sent: Tuesday, May 11, 2010 10:15 AM To: vcl-dev@incubator.apache.org Subject: Re: windows 64 bit support Good info Mike. Hopefully the next release will make this a little less painful. - Install Windows-64 hotfix for Sysnative path to work. Yes. You'll need this: http://support.microsoft.com/kb/942589 If you can't run the following command on a 64-bit installation then things won't work: dir C:\Windows\Sysnative - Create symlinks for shutdown.exe, defrag.exe in system32 folder. The code will need to be checked for these and all other calls to .exe's in System32. This won't be a requirement in the next release. - Use the Windows_Server_2003 module in the OS table for winxp64 OS. Was this required so VMware would set the guestOS setting in the .vmx file to something that worked for 64-bit, or was there another reason? - Replace Sysprep and Broadcom drivers under /usr/local/vcl/tools/Windows_Server_2003 with 64-bit versions. We'll need to design the drivers directories out a little better. As of now, the tools/Windows_version/drivers directories are copied during image capture and there are no provisions for different architectures. If you want to run both 32 and 64-bit versions of the same Windows OS, the drivers for both will be copied. This could cause conflicts if Sysprep doesn't choose the correct driver. Also add 64-bit version of spdrvscn.exe. The requirement for spdrvscn.exe has been removed in the latest code but you'll need the correct version of this utility for 2.1 and earlier. This utility scans the driver .inf files and populates the DevicePath registry key with all of the paths it finds. The vcld Perl code now does this. The new code also automatically populates the mass storage section of sysprep.inf will the paths to all of the storage .inf's it finds. -Andy
Re: Change image timeout
I believe the problem is related to the Install Path setting for your management node: Management Nodes Edit Management Node Information Edit Based on the paths being used, I'm guessing yours is set to 'storage/x86'. Where does the partimage .gz file reside? If it actually resides in '/storage/image/x86' then change the Install Path setting to 'storage'. The .tmpl file residing in this directory may indicate another problem with the xCAT root path. Where is xCAT installed and which version of xCAT are you using? Search your log file for 'xCAT root path found:'. What path does this line contain? Regards, Andy Roger Herling wrote: [r...@vcl ~]# du -c /storage/x86/image/x86/winvista-Windows7FacStaff49-v0* 4 /storage/x86/image/x86/winvista-Windows7FacStaff49-v0.tmpl 4 total [r...@vcl ~]# ls -l /storage/x86/image/x86/winvista-Windows7FacStaff49-v0* -rw-r--r-- 1 root root 352 May 10 12:09 /storage/x86/image/x86/winvista-Windows7FacStaff49-v0.tmpl Roger Herling Sr. Desktop Administrator Marist College PH: 845-575-3347 From: Andy Kurth andy_ku...@ncsu.edu To: vcl-dev@incubator.apache.org Date: 05/11/2010 09:06 AM Subject: Re: Change image timeout The command that is being executed to check the size should be: du -c /storage/x86/image/x86/winvista-Windows7FacStaff49-v0* Try running this. What output does it generate? The last line should look like: total The code appears to be finding the 'total' line but is either not parsing it correctly, not calculating the size correctly, or the du command isn't correct. Also, it would be helpful if you include the output from: ls -l /storage/x86/image/x86/winvista-Windows7FacStaff49-v0* -Andy Waldron, Michael H wrote: So you never answered whether you watched the capture occurring from the node console. Can you watch the console and see the capture running while monitoring the log that shows the capture file is size 0? What about any other error messages for the rest of the log capture for this imaging request? Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 -Original Message- From: Roger Herling [mailto:roger.herl...@marist.edu] Sent: Monday, May 10, 2010 4:18 PM To: vcl-dev@incubator.apache.org Subject: RE: Change image timeout yup Roger Herling Sr. Desktop Administrator Marist College PH: 845-575-3347 From: Waldron, Michael H mwald...@email.unc.edu To: 'vcl-dev@incubator.apache.org' vcl-dev@incubator.apache.org Date: 05/10/2010 04:17 PM Subject: RE: Change image timeout So you can do an ls -l /storage/x86/image/x86/winvista-Windows7FacStaff49-v0 and it shows some size? Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 -Original Message- From: Roger Herling [mailto:roger.herl...@marist.edu] Sent: Monday, May 10, 2010 4:03 PM To: vcl-dev@incubator.apache.org Subject: RE: Change image timeout The image is definately being captured and I can force the image to be used after it fails by manually undeleting it from the mysql database Roger Herling Sr. Desktop Administrator Marist College PH: 845-575-3347 From: Waldron, Michael H mwald...@email.unc.edu To: 'vcl-dev@incubator.apache.org' vcl-dev@incubator.apache.org Date: 05/10/2010 04:01 PM Subject: RE: Change image timeout From these lines in the log, it's indicating that the capture hasn't started: 12:31:01|9225|144:178|image|xCAT.pm:get_image_size(3146)|returning image size: 0 MB (4 bytes) 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1258)|image size is the same: 0=0, copy may be complete 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1238)|image copy not complete, sleeping for 30 seconds Notice the image size is 0 MB, meaning the partimage save isn't occurring. After 20 minutes of nothing being saved, it gives up. Can you watch the capture from the server console to verify that the PXE boot is running and that it's booting into the image capture mode? Do the log entries at the beginning of the imaging process show any errors? Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 -Original Message- From: Roger Herling [mailto:roger.herl...@marist.edu] Sent: Monday, May 10, 2010 3:25 PM To: vcl-dev@incubator.apache.org Subject: RE: Change image timeout 010-05-10 12:31:01|9225|144:178|image|xCAT.pm:_get_image_repository_path(3271)|returning repository path for vcl.is.marist.edu: /storage/x86/image/x86 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:get_image_size(3146)|returning image size: 0 MB (4 bytes) 2010-05-10 12:31:01|9225|144:178|image|xCAT.pm:capture_monitor(1258)|image size is the same: 0=0, copy may be complete 2010-05-10
Re: Incubator PMC/Board report for May 2010 (vcl-dev@incubator.apache.org)
My one comment regards: A few people from the community have been contacted by PPMC members to see if they are interested in becoming committers. Wouldn't the following be more accurate? A few people from the community have been contacted by PPMC members encouraging them to become more involved in the project --kevan On May 11, 2010, at 10:26 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The report is available here: https://cwiki.apache.org/VCL/2010-05-incubator-vcl-report.html If you have any feedback, please provide it soon. I'll post the report to the Incubator PMC later this afternoon. Josh On Tuesday May 11, 2010, Kevan Miller wrote: Friendly reminder -- board report is due by tomorrow, Wednesday May 12. --kevan On May 1, 2010, at 10:00 AM, no-re...@apache.org wrote: Dear VCL Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for . The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/May2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - -- - --- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAkvpaTUACgkQV/LQcNdtPQNCfQCePR22w2+EsLMGAtfLTQ8ntJBt 9QoAniTLBSC9dzfkURrAW9q6I8+8mIdU =XiDn -END PGP SIGNATURE-
Linux base image creation
Hello All, I am trying to create an Ubuntu base image. I have followed the instructions as given in https://cwiki.apache.org/VCL/create-a-linux-base-image.html I am able to ssh on the private network(eth1) from my management node but I am unable to ssh on the public network(eth0). I start my ssh on public interface by /etc/init.d/ext_ssh start and it shows a message saying SSH started successfully but actually there is no ssh port which listens on public interface. Hence I am unable to ssh remotely. Are there any extra changes to be made for an ubuntu base image? Any input will be helpful! -- Thanks, Kiran
