Re: add custom script to image capture
anyone able to help with this Roger Herling Sr. Desktop Administrator Marist College PH: 845-575-3347 From: Roger Herling To: vcl-dev@incubator.apache.org Date: 05/24/2010 04:25 PM Subject: add custom script to image capture We have 2 pieces of software that need to be reset prior to an image capture currently the vcl runs through its first stages of image prep then reboots the blade and finishes the configuration and then shuts down for imaging. I need these scripts to run after that first reboot where would I put them and how can I configure the vcl code to run them for me? Roger Herling Sr. Desktop Administrator Marist College PH: 845-575-3347
Re: add custom script to image capture
You could try editing the OS module for whatever OS you are using in this case. You could also try configuring the scripts to run on boot on the image itself. On Tue, Jun 1, 2010 at 10:15 AM, Roger Herling wrote: > anyone able to help with this > > > Roger Herling > Sr. Desktop Administrator > Marist College > PH: 845-575-3347 > > > > From: > Roger Herling > To: > vcl-dev@incubator.apache.org > Date: > 05/24/2010 04:25 PM > Subject: > add custom script to image capture > > > > We have 2 pieces of software that need to be reset prior to an image > capture currently the vcl runs through its first stages of image prep then > > reboots the blade and finishes the configuration and then shuts down for > imaging. I need these scripts to run after that first reboot where would > I put them and how can I configure the vcl code to run them for me? > > > Roger Herling > Sr. Desktop Administrator > Marist College > PH: 845-575-3347 >
[mentors] guidelines for contributing large modifications
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (This message is to everyone in the community. I added [mentors] to the subject to help our mentors know it is of particular importance for them to read.) After reading "Reg: JIRA issue VCL-202" by Kiran N sent on May 28, I realized we need some guidelines for contributing large modifications to the project. This is the general work flow I'd like to see happen for large modifications. Please provide comments and suggestions. Everyone's input is welcome (and desired) -- if you are interested in becoming a committer, this would be a great place to step up involvement. (1) State on the vcl-dev list what modification you'd like to make. Some background on why the existing codebase doesn't work in your situation would be useful. Remember, when you modify existing code, it affects work being done by other contributors, which can result in imposing additional work on them. (2) Propose a plan on the vcl-dev list for making the modification. There may be others that want the same modification or something similar that can be incorporated at the same time. Those people can help develop the modification. On the other hand, the modification may have a very negative affect on some other part of the project. Also, this provides an opportunity for existing contributors (those who know the codebase well) to provide input on your plan. The plan needs to include how the modification will be maintained in the future - will you continue to maintain it; will existing contributors have to pick it up and maintain it? (3) Create a JIRA issue to track implementation of the plan and start developing. This provides a way for others to track work being done on the modification and ensures information about the modification will be added to the CHANGELOG when the next release is cut. Thanks Josh - -- - --- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAkwFJr0ACgkQV/LQcNdtPQNZqwCfYyeB99JT3vxuBs9+gpn+v5vs BWYAn2D5HK/Cvo1Kd5CtpEqFpsJBR8bo =dYgS -END PGP SIGNATURE-
Re: Reg: JIRA issue VCL-202
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kiran,
Wow - that's a lot of changes. We're in need of more committers, and it
sounds like you've done a lot of work already. So, this could be very
beneficial.
As I read this, I realized we (the Apache VCL community) don't have any
guidelines in place for contributing modifications that affect large portions
of the code. I just composed another message to this list titled "guidelines
for contributing large modifications" to establish some guidelines.
Before discussing your contributions further, lets wait on that process to get
worked out so that this can be contributed in a way that most benefits the
community.
Thanks,
Josh
On Friday May 28, 2010, Kiran N wrote:
> Hello All,
> I have been studying VCL code and I want to be a contributor to the VCL
> development. I will identify my work as related to JIRA issue VCL-202(in
> database) started by Milen Paskov. There are few things I have been working
> on and would like to share here.
>
>- Modified vcl.sql script to connect to Apache derby database and create
>the database with the tables and data as in mysql. Please find the
>vcl-derby.sql attached with this email.
>- I have been working on the PHP front end code so that it can connect
> to both mysql and Apache derby database. I am not sure if I need to
> contibute to this by creating a new JIRA issue number. Please advise on
> this. - Regarding changes to the PHP front end, I have coded a new
> 'param.php' file which changes the database data fetch or update
> statements based on the type of database. I also assigns/creates some
> global variables. As stated in JIRA issue VCL-202 , there are certain
> keywords ('user', 'end', 'order' and 'key')which cannot be used as
> database columns or table names in derby , I have created global variables
> which store the values of these keyword based on mysql/derby.
>- Apart from this in the code there are some small changes like
>DATA_FORMAT() , UNIX_TIMESTAMP() functions is not recognized in derby.
> So they have been changed accordingly. I am working on a document to
> provide the complete list of changes between mysql and derby from the PHP
> front end code perspective.
>- Regarding connecting PHP to Apache derby, db2 runtime client with
>ibm_db2 extension is used. PDO_ODBC is the data access interface for PHP
>which compiles directly against DB2 librraries for native access to DB2.
> PHP is complied with ibm_db2 extension and configured accordingly. Please
> refer to below links for better understanding.
>
> References:
> http://coffeecode.net/uploads/talks/phptropics-ibm_db2.pdf
> http://www.db2ude.com/?q=node/81
>
> I am working on providing more explanatory documents which would help doing
> the setup for testing and checking the connection of PHP with derby but
> this is the initial idea that i shared. Presently, I have done the setup
> and working on the PHP front end code. I will be sharing that also with
> you probably sometime next week.
> Please provide me feedback and suggestions on this! Let me know for any
> questions.
>
- --
- ---
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)
iEYEARECAAYFAkwFJs8ACgkQV/LQcNdtPQOqdACffPjcOW3GrgtDVDSdV27eGo4b
LIkAn1MJDxt2QWodgoYYK6ny3MMdwghu
=FrTq
-END PGP SIGNATURE-
Re: Reg: JIRA issue VCL-202
Thank you Josh!
The plan sounds good to me since there are actually lot of code changes and
its important we document that correctly.
I have a suggestion that while we are waiting for that , there are few
things I need access to:
There are some set of default images in database image table. I wanted to
initiate the process of making a reservation on any one of those images.
I needed that to test New reservation, Block reservation. So, in case there
is any captured image which is used by VCL for testing purposes please let
me know.This would in turn also need some computer table entries too.
Overall, I would be needing some additional test data for me to test all the
php files.
Please let me know what can be done on that!
Also I have submitted the ICLA form http://www.apache.org/licenses/#clas.
Please let me know if there is anything else I am supposed to do!
Any suggestions are welcome!
On Tue, Jun 1, 2010 at 11:27 AM, Josh Thompson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Kiran,
>
> Wow - that's a lot of changes. We're in need of more committers, and it
> sounds like you've done a lot of work already. So, this could be very
> beneficial.
>
> As I read this, I realized we (the Apache VCL community) don't have any
> guidelines in place for contributing modifications that affect large
> portions
> of the code. I just composed another message to this list titled
> "guidelines
> for contributing large modifications" to establish some guidelines.
>
> Before discussing your contributions further, lets wait on that process to
> get
> worked out so that this can be contributed in a way that most benefits the
> community.
>
> Thanks,
> Josh
>
> On Friday May 28, 2010, Kiran N wrote:
> > Hello All,
> > I have been studying VCL code and I want to be a contributor to the VCL
> > development. I will identify my work as related to JIRA issue VCL-202(in
> > database) started by Milen Paskov. There are few things I have been
> working
> > on and would like to share here.
> >
> >- Modified vcl.sql script to connect to Apache derby database and
> create
> >the database with the tables and data as in mysql. Please find the
> >vcl-derby.sql attached with this email.
> >- I have been working on the PHP front end code so that it can connect
> > to both mysql and Apache derby database. I am not sure if I need to
> > contibute to this by creating a new JIRA issue number. Please advise on
> > this. - Regarding changes to the PHP front end, I have coded a new
> > 'param.php' file which changes the database data fetch or update
> > statements based on the type of database. I also assigns/creates some
> > global variables. As stated in JIRA issue VCL-202 , there are certain
> > keywords ('user', 'end', 'order' and 'key')which cannot be used as
> > database columns or table names in derby , I have created global
> variables
> > which store the values of these keyword based on mysql/derby.
> >- Apart from this in the code there are some small changes like
> >DATA_FORMAT() , UNIX_TIMESTAMP() functions is not recognized in derby.
> > So they have been changed accordingly. I am working on a document to
> > provide the complete list of changes between mysql and derby from the
> PHP
> > front end code perspective.
> >- Regarding connecting PHP to Apache derby, db2 runtime client with
> >ibm_db2 extension is used. PDO_ODBC is the data access interface for
> PHP
> >which compiles directly against DB2 librraries for native access to
> DB2.
> > PHP is complied with ibm_db2 extension and configured accordingly.
> Please
> > refer to below links for better understanding.
> >
> > References:
> > http://coffeecode.net/uploads/talks/phptropics-ibm_db2.pdf
> > http://www.db2ude.com/?q=node/81
> >
> > I am working on providing more explanatory documents which would help
> doing
> > the setup for testing and checking the connection of PHP with derby but
> > this is the initial idea that i shared. Presently, I have done the setup
> > and working on the PHP front end code. I will be sharing that also with
> > you probably sometime next week.
> > Please provide me feedback and suggestions on this! Let me know for any
> > questions.
> >
> - --
> - ---
> 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)
>
> iEYEARECAAYFAkwFJs8ACgkQV/LQcNdtPQOqdACffPjcOW3GrgtDVDSdV27eGo4b
> LIkAn1MJDxt2QWodgoYYK6ny3MMdwghu
> =FrTq
> -END PGP SIGNATURE-
>
--
Thanks,
Kiran
Re: [mentors] guidelines for contributing large modifications
On Jun 1, 2010, at 8:26 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (This message is to everyone in the community. I added [mentors] to the subject to help our mentors know it is of particular importance for them to read.) After reading "Reg: JIRA issue VCL-202" by Kiran N sent on May 28, I realized we need some guidelines for contributing large modifications to the project. This is the general work flow I'd like to see happen for large modifications. Please provide comments and suggestions. Everyone's input is welcome (and desired) -- if you are interested in becoming a committer, this would be a great place to step up involvement. (1) State on the vcl-dev list what modification you'd like to make. Some background on why the existing codebase doesn't work in your situation would be useful. Remember, when you modify existing code, it affects work being done by other contributors, which can result in imposing additional work on them. (2) Propose a plan on the vcl-dev list for making the modification. There may be others that want the same modification or something similar that can be incorporated at the same time. Those people can help develop the modification. On the other hand, the modification may have a very negative affect on some other part of the project. Also, this provides an opportunity for existing contributors (those who know the codebase well) to provide input on your plan. The plan needs to include how the modification will be maintained in the future - will you continue to maintain it; will existing contributors have to pick it up and maintain it? (3) Create a JIRA issue to track implementation of the plan and start developing. This provides a way for others to track work being done on the modification and ensures information about the modification will be added to the CHANGELOG when the next release is cut. Seems reasonable to me. Regards, Alan
Re: [mentors] guidelines for contributing large modifications
Great start Josh ... +1 On Jun 1, 2010, at 11:26 AM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > (This message is to everyone in the community. I added [mentors] to the > subject to help our mentors know it is of particular importance for them to > read.) > > After reading "Reg: JIRA issue VCL-202" by Kiran N sent on May 28, I realized > we need some guidelines for contributing large modifications to the project. > This is the general work flow I'd like to see happen for large modifications. > > Please provide comments and suggestions. Everyone's input is welcome (and > desired) -- if you are interested in becoming a committer, this would be a > great place to step up involvement. > > (1) State on the vcl-dev list what modification you'd like to make. Some > background on why the existing codebase doesn't work in your situation would > be useful. Remember, when you modify existing code, it affects work being > done by other contributors, which can result in imposing additional work on > them. > > (2) Propose a plan on the vcl-dev list for making the modification. There > may > be others that want the same modification or something similar that can be > incorporated at the same time. Those people can help develop the > modification. On the other hand, the modification may have a very negative > affect on some other part of the project. Also, this provides an opportunity > for existing contributors (those who know the codebase well) to provide input > on your plan. The plan needs to include how the modification will be > maintained in the future - will you continue to maintain it; will existing > contributors have to pick it up and maintain it? > > (3) Create a JIRA issue to track implementation of the plan and start > developing. This provides a way for others to track work being done on the > modification and ensures information about the modification will be added to > the CHANGELOG when the next release is cut. > > Thanks > Josh > - -- > - --- > Josh Thompson > Systems Programmer > Advanced Computing | VCL Developer > North Carolina State University > > josh_thomp...@ncsu.edu > > my GPG/PGP key can be found at pgp.mit.edu > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.14 (GNU/Linux) > > iEYEARECAAYFAkwFJr0ACgkQV/LQcNdtPQNZqwCfYyeB99JT3vxuBs9+gpn+v5vs > BWYAn2D5HK/Cvo1Kd5CtpEqFpsJBR8bo > =dYgS > -END PGP SIGNATURE-
Re: ESXi host, local disk
I went ahead to switch it to NFS (helpful users have suggested it to me as work-arounds). I hope that I'm done with my initial image (given the logs entries, I think I'm done with the initial image creation - please point out if I'm wrong). This message might be more appropriate to vcl-user. === OUTPUT for vcld run on 2010-06-01 13:50:35 === 2010-06-01 13:50:35|13091|vcld:main(116)|vcld environment variable set to 1 for this process 2010-06-01 13:50:35|13091|utils.pm:rename_vcld_process(7901)|renamed process to 'vcld vcld' 2010-06-01 13:50:35|13091|utils.pm:get_management_node_info(6815)|management node info retrieved from database for managementnode 2010-06-01 13:50:35|13091|vcld:main(127)|retrieved management node information from database 2010-06-01 13:50:35|13091|vcld:main(140)|management_node_id environment variable set: 1 2010-06-01 13:50:35|13091|vcld:main(148)|management node checkin interval is 5 seconds 2010-06-01 13:50:35|13091|vcld:main(149)|vcld started on managementnode.local 2010-06-01 13:50:40|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:50:40 2010-06-01 13:50:45|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:50:45 2010-06-01 13:50:50|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:50:50 2010-06-01 13:50:55|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:50:55 2010-06-01 13:51:00|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:00 2010-06-01 13:51:05|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:05 2010-06-01 13:51:10|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:10 2010-06-01 13:51:15|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:15 2010-06-01 13:51:20|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:20 2010-06-01 13:51:25|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:25 2010-06-01 13:51:30|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:30 2010-06-01 13:51:35|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:35 2010-06-01 13:51:40|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:40 2010-06-01 13:51:45|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:45 2010-06-01 13:51:50|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:50 2010-06-01 13:51:55|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:51:55 2010-06-01 13:52:00|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:52:00 2010-06-01 13:52:05|13091|vcld:main(165)|lastcheckin time updated for management node 1: 2010-06-01 13:52:05 2010-06-01 13:52:05|13091|1:10|image|utils.pm:reservation_being_processed(9634)|computerloadlog 'begin' entry does NOT exist for reservation 10 2010-06-01 13:52:05|13091|1:10|image|utils.pm:reservation_being_processed(9686)|reservation is NOT currently being processed 2010-06-01 13:52:05|13091|1:10|image|vcld:main(276)|reservation 10 is NOT already being processed |13091|1:10|image| WARNING |13091|1:10|image| 2010-06-01 13:52:05|13091|1:10|image|utils.pm:get_request_info(5218)|preferredimageid is not set for computer id=2 |13091|1:10|image| ( 0) utils.pm, notify (line: 737) |13091|1:10|image| (-1) utils.pm, get_request_info (line: 5218) |13091|1:10|image| (-2) vcld, main (line: 280) 2010-06-01 13:52:05|13091|1:10|image|utils.pm:get_request_info(5354)|standalone affiliation found: Local 2010-06-01 13:52:05|13091|1:10|image|utils.pm:get_management_node_info(6815)|management node info retrieved from database for managementnode 2010-06-01 13:52:05|13091|1:10|image|vcld:main(281)|retrieved request information from database 2010-06-01 13:52:05|13091|1:10|image|utils.pm:get_management_node_info(6815)|management node info retrieved from database for managementnode 2010-06-01 13:52:05|13091|1:10|image|DataStructure.pm:is_parent_reservation(854)|returning true: parent reservation ID for this request: 10 2010-06-01 13:52:05|13091|1:10|image|utils.pm:update_request_state(2186)|request 1 state updated to: pending, laststate to: image 2010-06-01 13:52:05|13091|1:10|image|utils.pm:insertloadlog(4710)|inserted computer=2, begin, beginning to process, state is image 2010-06-01 13:52:05|13091|1:10|image|vcld:make_new_child(509)|loaded VCL::image module 2010-06-01 13:52:05|13095|1:10|image|vcld:make_new_child(582)|vcld environment variable set to 0 for this process 2010-06-01 13:52:05|13091|1:10|image|vcld:make_new_child(566)|current number of forked kids: 1 2010-06-01 13:52:05|13095|1:1
Re: ESXi host, local disk
I don't think you are quite there yet. VCL needs to be able to ssh into the image to perform some configuration. I am pretty sure the VM you are trying to capture an image of needs to be registered with the host and powered on. From the looks of the error below, the VM may not have been registered with the host. Or perhaps the Image you are trying to capture is a registered VM, but its name does not match the virtual machine VCL is looking for. 2010-06-01 13:52:28|13095|1:10|image|esx.pm:capture(661)|Powered off: Virtual Machine vmwarelinux-base10-v1 not found. I real issue again has to do with this error where VCL is unable to SSH into the VM. |13095|1:10|image| WARNING |13095|1:10|image| 2010-06-01 13:52:07|13095|1:10|image|utils.pm:run_ssh_command(6252)|attempt 1/3: failed to execute SSH command on vmwarelinux-base10-v1: echo vmwarelinux-base10-v1 > /root/currentimage.txt, exit status: 255, SSH exits with the exit status of the remote command or with 255 if an error occurred, output: |13095|1:10|image| ssh output (echo vmwar...): ssh: vmwarelinux-base10-v1: Name or service not known |13095|1:10|image| ( 0) utils.pm, notify (line: 737) |13095|1:10|image| (-1) utils.pm, run_ssh_command (line: 6252) |13095|1:10|image| (-2) esx.pm, capture (line: 650) |13095|1:10|image| (-3) image.pm, process (line: 162) |13095|1:10|image| (-4) vcld, make_new_child (line: 596) |13095|1:10|image| (-5) vcld, main (line: 341) On Tue, Jun 1, 2010 at 3:55 PM, My LinuxHAList wrote: > I went ahead to switch it to NFS (helpful users have suggested it to > me as work-arounds). > I hope that I'm done with my initial image (given the logs entries, I > think I'm done with the initial image creation - please point out if > I'm wrong). > > This message might be more appropriate to vcl-user. > > === > OUTPUT for vcld run on 2010-06-01 13:50:35 > === > 2010-06-01 13:50:35|13091|vcld:main(116)|vcld environment variable set > to 1 for this process > 2010-06-01 13:50:35|13091|utils.pm:rename_vcld_process(7901)|renamed > process to 'vcld vcld' > 2010-06-01 13:50:35|13091|utils.pm: > get_management_node_info(6815)|management > node info retrieved from database for managementnode > 2010-06-01 13:50:35|13091|vcld:main(127)|retrieved management node > information from database > 2010-06-01 13:50:35|13091|vcld:main(140)|management_node_id > environment variable set: 1 > 2010-06-01 13:50:35|13091|vcld:main(148)|management node checkin > interval is 5 seconds > 2010-06-01 13:50:35|13091|vcld:main(149)|vcld started on > managementnode.local > 2010-06-01 13:50:40|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:50:40 > 2010-06-01 13:50:45|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:50:45 > 2010-06-01 13:50:50|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:50:50 > 2010-06-01 13:50:55|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:50:55 > 2010-06-01 13:51:00|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:00 > 2010-06-01 13:51:05|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:05 > 2010-06-01 13:51:10|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:10 > 2010-06-01 13:51:15|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:15 > 2010-06-01 13:51:20|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:20 > 2010-06-01 13:51:25|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:25 > 2010-06-01 13:51:30|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:30 > 2010-06-01 13:51:35|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:35 > 2010-06-01 13:51:40|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:40 > 2010-06-01 13:51:45|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:45 > 2010-06-01 13:51:50|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:50 > 2010-06-01 13:51:55|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:51:55 > 2010-06-01 13:52:00|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:52:00 > 2010-06-01 13:52:05|13091|vcld:main(165)|lastcheckin time updated for > management node 1: 2010-06-01 13:52:05 > 2010-06-01 13:52:05|13091|1:10|image|utils.pm: > reservation_being_processed(9634)|computerloadlog > 'begin' entry does NOT exist for reservation 10 > 2010-06-01 13:52:05|13091|1:10|image|utils.pm: > reservation_being_processed(9686)|reservation > is NOT currently being processed > 2010-06-
Re: ESXi host, local disk
Ryan, thanks for the input and helpful discussion. I had a similar discussion with another helpful user on the topic. I think the management node was going to ssh into the vm machine to set ethernet to dhcpd, configure the sshd, shut it down, de-register it from vmware, etc. My original intention is that if I've properly setup the image; set ethernet to dhcpd, etc., then this would obviate the needs for the management node to login (and thus safely ignore the warnings). By having done what the management node going to do and put it in the image, will I be able to skip the step of having the management node to login to the image ? The process did copy over: ./golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1.vmx ./golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1.vmdk ./golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1-flat.vmdk Thanks On Tue, Jun 1, 2010 at 6:04 PM, Ryan Johnson wrote: > I don't think you are quite there yet. VCL needs to be able to ssh into the > image to perform some configuration. I am pretty sure the VM you are trying > to capture an image of needs to be registered with the host and powered on. > From the looks of the error below, the VM may not have been registered with > the host. Or perhaps the Image you are trying to capture is a registered > VM, but its name does not match the virtual machine VCL is looking for. > > 2010-06-01 13:52:28|13095|1:10|image|esx.pm:capture(661)|Powered off: > Virtual Machine vmwarelinux-base10-v1 not found. > > I real issue again has to do with this error where VCL is unable to SSH into > the VM. > > |13095|1:10|image| WARNING > |13095|1:10|image| 2010-06-01 > 13:52:07|13095|1:10|image|utils.pm:run_ssh_command(6252)|attempt 1/3: > failed to execute SSH command on vmwarelinux-base10-v1: echo > vmwarelinux-base10-v1 > /root/currentimage.txt, exit status: 255, SSH > exits with the exit status of the remote command or with 255 if an > error occurred, output: > |13095|1:10|image| ssh output (echo vmwar...): ssh: > vmwarelinux-base10-v1: Name or service not known > |13095|1:10|image| ( 0) utils.pm, notify (line: 737) > |13095|1:10|image| (-1) utils.pm, run_ssh_command (line: 6252) > |13095|1:10|image| (-2) esx.pm, capture (line: 650) > |13095|1:10|image| (-3) image.pm, process (line: 162) > |13095|1:10|image| (-4) vcld, make_new_child (line: 596) > |13095|1:10|image| (-5) vcld, main (line: 341) > > On Tue, Jun 1, 2010 at 3:55 PM, My LinuxHAList wrote: > >> I went ahead to switch it to NFS (helpful users have suggested it to >> me as work-arounds). >> I hope that I'm done with my initial image (given the logs entries, I >> think I'm done with the initial image creation - please point out if >> I'm wrong). >> >> This message might be more appropriate to vcl-user. >> >> === >> OUTPUT for vcld run on 2010-06-01 13:50:35 >> === >> 2010-06-01 13:50:35|13091|vcld:main(116)|vcld environment variable set >> to 1 for this process >> 2010-06-01 13:50:35|13091|utils.pm:rename_vcld_process(7901)|renamed >> process to 'vcld vcld' >> 2010-06-01 13:50:35|13091|utils.pm: >> get_management_node_info(6815)|management >> node info retrieved from database for managementnode >> 2010-06-01 13:50:35|13091|vcld:main(127)|retrieved management node >> information from database >> 2010-06-01 13:50:35|13091|vcld:main(140)|management_node_id >> environment variable set: 1 >> 2010-06-01 13:50:35|13091|vcld:main(148)|management node checkin >> interval is 5 seconds >> 2010-06-01 13:50:35|13091|vcld:main(149)|vcld started on >> managementnode.local >> 2010-06-01 13:50:40|13091|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-06-01 13:50:40 >> 2010-06-01 13:50:45|13091|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-06-01 13:50:45 >> 2010-06-01 13:50:50|13091|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-06-01 13:50:50 >> 2010-06-01 13:50:55|13091|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-06-01 13:50:55 >> 2010-06-01 13:51:00|13091|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-06-01 13:51:00 >> 2010-06-01 13:51:05|13091|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-06-01 13:51:05 >> 2010-06-01 13:51:10|13091|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-06-01 13:51:10 >> 2010-06-01 13:51:15|13091|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-06-01 13:51:15 >> 2010-06-01 13:51:20|13091|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-06-01 13:51:20 >> 2010-06-01 13:51:25|13091|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-06-01 13:51:25 >> 2010-06-01 13:51:30|13091|vcld:main(165)|lastcheckin time updated for >> management node 1: 2010-06-01 13:51:30 >> 2010-06-01 13:51:35|13091|vcld:main(165)|lastcheckin time updated f
