Re: VCL 2.3
Thank you. This worked. -- Dmitri Chebotarov Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging 223 Aquia Building, Ffx, MSN: 1B5 Phone: (703) 993-6175 Fax: (703) 993-3404 On Wednesday, May 2, 2012 at 7:53 , Aaron Coburn wrote: > Dmitri, > you can also set a default ItentityFile in the ssh configuration, i.e.: > > IdentityFile /etc/vcl/vcl.key > > Depending on how you want this set up (whether to apply only to certain hosts > or to be globally applicable), you can put this in /etc/ssh/ssh_config or in > /root/.ssh/config > > This can be a useful setting, especially for manually accessing VM nodes, > since you can then entirely omit the -i flag. > > Aaron > > > -- > Aaron Coburn > Systems Administrator and Programmer > Academic Technology Services, Amherst College > acob...@amherst.edu (mailto:acob...@amherst.edu) > > > > On May 1, 2012, at 10:50 PM, Dmitri Chebotarov wrote: > > > Andy > > > > $ssh_options doesn't have vcl.key. (ie. -i /path/to/vcl.key) > > I've changed the code to test it - added: > > > > $ssh_options = $ssh_options." -i /etc/vcl/vcl.key"; > > > > right before $ssh object is created and it seemed to communicated with host > > OK this time: > > > > ... > > 2012-05-01 22:38:16|1097|435:427|reload|OS.pm:(eval)(1946)|created > > Net::SSH::Expect object to control VMHOST1 > > 2012-05-01 22:38:16|1097|435:427|reload|OS.pm:(eval)(1947)|ssh_options: -o > > StrictHostKeyChecking=no -i /etc/vcl/vcl.key (<-- before the change > > $ssh_option was just '-o StrictHostKeyChecking=no') > > > > > > 2012-05-01 22:38:19|1097|435:427|reload|VIM_SSH.pm:initialize(138)|VIM > > executable available on VM host: vim-cmd > > 2012-05-01 > > 22:38:19|1097|435:427|reload|VIM_SSH.pm:initialize(140)|VCL::Module::Provisioning::VMware::VIM_SSH > > object initialized > > 2012-05-01 > > 22:38:19|1097|435:427|reload|VMware.pm:get_vmhost_api_object(1522)|created > > API object: VCL::Module::Provisioning::VMware::VIM_SSH > > 2012-05-01 22:38:19|1097|435:427|reload|VMware.pm:initialize(312)|VM host > > VMHOST1 will be controlled using vim-cmd via SSH > > 2012-05-01 22:38:19|1097|435:427|reload|VMware.pm:initialize(327)|VMware OS > > and API objects created for VM host VMHOST1: > > |1097|435:427|reload| VM host OS object type: VCL::Module::OS::Linux > > |1097|435:427|reload| VMware API object type: > > VCL::Module::Provisioning::VMware::VIM_SSH > > 2012-05-01 > > 22:38:19|1097|435:427|reload|VMware.pm:get_vmhost_product_name(6514)|VMware > > product being used on VM host VMHOST1: 'VMware ESXi 5.0.0 build-469512' > > 2012-05-01 > > 22:38:19|1097|435:427|reload|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call > > count: 1 (hostsvc/datastore/listsummary) > > 2012-05-01 > > 22:38:19|1097|435:427|reload|VIM_SSH.pm:_run_vim_cmd(208)|executed command > > on VM host VMHOST1: vim-cmd hostsvc/datastore/listsummary > > > > > > … > > > > I've double checked the setting for vcl.key under management node and it's > > present. > > > > Thank you. > > > > -- > > Dmitri Chebotarov > > Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging > > 223 Aquia Building, Ffx, MSN: 1B5 > > Phone: (703) 993-6175 > > Fax: (703) 993-3404 > > > > > > On Tuesday, May 1, 2012 at 21:47 , Dmitri Chebotarov wrote: > > > > > Andy, > > > > > > Here is the full log. > > > > > > Thank you. > > > > > > > > > > > > VCL::new object could not be created and initialized > > > > > > time: 2012-05-01 16:54:28 > > > caller: vcld:make_new_child(575) > > > ( 0) vcld, make_new_child (line: 575) > > > (-1) vcld, main (line: 350) > > > > > > management node: sand-vcl23 > > > reservation PID: 16065 > > > parent vcld PID: 15907 > > > request ID: 433 > > > reservation ID: 425 > > > request state/laststate: reload/reload > > > request start time: 2012-05-01 16:45:00 > > > request end time: 2012-05-01 17:05:00 > > > for imaging: no > > > log ID: none > > > computer: sandbox-vcl-4 > > > computer id: 46 > > > computer type: virtualmachine > > > computer eth0 MAC address: 00:50:56:00:10:08 > > > computer eth1 MAC address: 00:50:56:00:10:09 > > > computer private IP address: private-.5.14 > > > computer public IP address: public-.244 > > > computer in block allocation: no > > > provisioning module: VCL::Module::Provisioning::VMware::VMware > > > vm host: VMHOST1 > > > vm host ID: 5 > > > vm host computer ID: 85 > > > vm profile: VMware ESXi - local & network storage > > > vm profile VM path: /vmfs/volumes/local-datastore/runningImages > > > vm profile repository path: > > > vm profile datastore path: /vmfs/volumes/sandbox-Image-Library/baseImages > > > vm profile disk type: networkdisk > > > image: vmwarelinux-CentOSxCat69-v0 > > > image display name: CentOS 5.5 (persistent) > > > image ID: 69 > > > image revision ID: 72 > > >
Re: [DISCUSS] Graduation
I feel we have meet our diversity issue and also expect to add more committers over the next couple of months. I would positively support a vote for graduation. I agree on the other points mentioned. Status page needs to be updated. We can work on this part easily. The web site needs to be migrated off confluence. Has anyone researched other CMS options for the website. I think this would be a good community discussion thread. Which CMS, the layout, (content, documentation, design ideas, etc.) Aaron On Tue, May 1, 2012 at 12:44 PM, Andy Kurth wrote: > This thread is to discuss whether the Apache VCL community feels that > this incubating project is ready to proceed with the process to > graduate to a top level ASF project. There are several requirements > which must be met and steps completed in order to graduate. This > discussion thread is the first step towards graduation. Please review > the following pages. > http://incubator.apache.org/guides/graduation.html > http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator > > There are many items described in the ASF graduation documentation > which we have obviously satisfied (create a release, etc). The > following are issues that I feel either need to be addressed, would be > concerned about regarding board/mentor approval, or have been brought > up before. Please share your thoughts. Also, please review the ASF > graduation documentation and bring up anything else which might be a > concern. > > Status File: > (https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/vcl.xml) > This is not up to date and is missing information. Previous board > reports need to be added. News items need to be added containing the > string "new committer". Doing this will cause the numberCommittersNew > column on the "Status of the Clutch" page to turn green > (http://incubator.apache.org/clutch.html). > > Also, the list of commiters in the status file and project page hasn't > changed since Apache VCL started. The new committers obviously need > to be added. I'm not sure how the original list was decided upon, but > I feel several names should be removed since they have not contributed > any code and some have not been involved in the community at all. I > think the list should be Aaron Coburn, David Hutchins, Andy Kurth, > James O'Dell, Aaron Peeler, Josh Thompson. Also, Brian Bouterse > contributed some code a while ago. I'm not sure if he is still > interested in being a committer. > > Diversity: > ASF requirement: "The project is not highly dependent on any single > contributor (there are at least 3 legally independent committers and > there is no single company or entity that is vital to the success of > the project)." > This issue has been raised before. I feel we meet this requirement > and that the community is generally diverse, can govern itself, and be > self-sufficient. > > Website: > This is not necessarily a requirement for graduation but I feel that > it should be addressed prior to graduation. Our website/documentation > is pretty rough and really should be redesigned. I'm guessing the > board members will look at it prior to voting. In addition, there > will likely be a press release if/when we graduate and website views > will spike. This shouldn't hold up the graduation process, but I > would like agreement that this should be completed by graduation. > > Thank You, > Andy -- Aaron Peeler Program Manager Virtual Computing Lab NC State University All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.
Re: VCL 2.3
Dmitri, you can also set a default ItentityFile in the ssh configuration, i.e.: IdentityFile /etc/vcl/vcl.key Depending on how you want this set up (whether to apply only to certain hosts or to be globally applicable), you can put this in /etc/ssh/ssh_config or in /root/.ssh/config This can be a useful setting, especially for manually accessing VM nodes, since you can then entirely omit the -i flag. Aaron -- Aaron Coburn Systems Administrator and Programmer Academic Technology Services, Amherst College acob...@amherst.edu On May 1, 2012, at 10:50 PM, Dmitri Chebotarov wrote: > Andy > > $ssh_options doesn't have vcl.key. (ie. -i /path/to/vcl.key) > I've changed the code to test it - added: > > $ssh_options = $ssh_options." -i /etc/vcl/vcl.key"; > > right before $ssh object is created and it seemed to communicated with host > OK this time: > > ... > 2012-05-01 22:38:16|1097|435:427|reload|OS.pm:(eval)(1946)|created > Net::SSH::Expect object to control VMHOST1 > 2012-05-01 22:38:16|1097|435:427|reload|OS.pm:(eval)(1947)|ssh_options: -o > StrictHostKeyChecking=no -i /etc/vcl/vcl.key (<-- before the change > $ssh_option was just '-o StrictHostKeyChecking=no') > > > 2012-05-01 22:38:19|1097|435:427|reload|VIM_SSH.pm:initialize(138)|VIM > executable available on VM host: vim-cmd > 2012-05-01 > 22:38:19|1097|435:427|reload|VIM_SSH.pm:initialize(140)|VCL::Module::Provisioning::VMware::VIM_SSH > object initialized > 2012-05-01 > 22:38:19|1097|435:427|reload|VMware.pm:get_vmhost_api_object(1522)|created > API object: VCL::Module::Provisioning::VMware::VIM_SSH > 2012-05-01 22:38:19|1097|435:427|reload|VMware.pm:initialize(312)|VM host > VMHOST1 will be controlled using vim-cmd via SSH > 2012-05-01 22:38:19|1097|435:427|reload|VMware.pm:initialize(327)|VMware OS > and API objects created for VM host VMHOST1: > |1097|435:427|reload| VM host OS object type: VCL::Module::OS::Linux > |1097|435:427|reload| VMware API object type: > VCL::Module::Provisioning::VMware::VIM_SSH > 2012-05-01 > 22:38:19|1097|435:427|reload|VMware.pm:get_vmhost_product_name(6514)|VMware > product being used on VM host VMHOST1: 'VMware ESXi 5.0.0 build-469512' > 2012-05-01 22:38:19|1097|435:427|reload|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd > call count: 1 (hostsvc/datastore/listsummary) > 2012-05-01 22:38:19|1097|435:427|reload|VIM_SSH.pm:_run_vim_cmd(208)|executed > command on VM host VMHOST1: vim-cmd hostsvc/datastore/listsummary > > > … > > I've double checked the setting for vcl.key under management node and it's > present. > > Thank you. > > -- > Dmitri Chebotarov > Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging > 223 Aquia Building, Ffx, MSN: 1B5 > Phone: (703) 993-6175 > Fax: (703) 993-3404 > > > On Tuesday, May 1, 2012 at 21:47 , Dmitri Chebotarov wrote: > >> Andy, >> >> Here is the full log. >> >> Thank you. >> >> >> >> VCL::new object could not be created and initialized >> >> time: 2012-05-01 16:54:28 >> caller: vcld:make_new_child(575) >> ( 0) vcld, make_new_child (line: 575) >> (-1) vcld, main (line: 350) >> >> management node: sand-vcl23 >> reservation PID: 16065 >> parent vcld PID: 15907 >> request ID: 433 >> reservation ID: 425 >> request state/laststate: reload/reload >> request start time: 2012-05-01 16:45:00 >> request end time: 2012-05-01 17:05:00 >> for imaging: no >> log ID: none >> computer: sandbox-vcl-4 >> computer id: 46 >> computer type: virtualmachine >> computer eth0 MAC address: 00:50:56:00:10:08 >> computer eth1 MAC address: 00:50:56:00:10:09 >> computer private IP address: private-.5.14 >> computer public IP address: public-.244 >> computer in block allocation: no >> provisioning module: VCL::Module::Provisioning::VMware::VMware >> vm host: VMHOST1 >> vm host ID: 5 >> vm host computer ID: 85 >> vm profile: VMware ESXi - local & network storage >> vm profile VM path: /vmfs/volumes/local-datastore/runningImages >> vm profile repository path: >> vm profile datastore path: /vmfs/volumes/sandbox-Image-Library/baseImages >> vm profile disk type: networkdisk >> image: vmwarelinux-CentOSxCat69-v0 >> image display name: CentOS 5.5 (persistent) >> image ID: 69 >> image revision ID: 72 >> image size: 8192 MB >> use Sysprep: no >> root access: yes >> image owner ID: 1 >> image owner affiliation: Local >> image revision date created: 2012-02-09 15:11:37 >> image revision production: yes >> OS module: VCL::Module::OS::Linux >> user: vclreload >> user name: vcl reload >> user ID: 2 >> user affiliation: Local >> >> RECENT LOG ENTRIES FOR THIS PROCESS: >> 2012-05-01 >> 16:54:21|16065|433:425|reload|VMware.pm:initialize(267)|initializing >> VCL::Module::Provisioning::VMware::VMware object >> 2012-05-01 >> 16:54:21|16065|433:425|reload|Data
