Re: Problem to create Base Image - VCL 2.2
Zapata
The problem may be related to a different language.
get_network_configuration is looking for line with word 'adapter' to determine
interface name (i.e. Ethernet adapter Local Area Connection), which is not
present in your case.
Windows.pm: get_network_configuration
# Find beginning of interface section
if ($line =~ /\A[^\s].*adapter (.*):\s*\Z/i) {
# Get the interface name
$interface_name = $1;
...
# Skip line if interface hasn't been found yet
next if !$interface_name;
Thanks.
On Jun 29, 2012, at 10:57 , Zapata Vivas Darío wrote:
Hi
I have installed VCL2.2 (-web code and data base in a public server
management node in a private server) but I have a problem to create the base
image.
When I execute the /usr/local/vcl/bin/vcld –setup command the vcld log shows
that the connection to the VM Host is ok in both vSphere_SDK and SSH but some
errors to create the base image are generated, this the output of the log:
2012-06-29 08:22:49|14875|utils.pm:insert_request(8443)|inserted new reload
request into request table, request id=31
2012-06-29 08:22:49|14875|utils.pm:insert_request(8474)|inserted new reload
request into reservation table, reservation id=31
2012-06-29
08:22:51|19357|31:31|image|utils.pm:reservation_being_processed(9010)|computerloadlog
'begin' entry does NOT exist for reservation 31
2012-06-29 08:22:51|19357|31:31|image|utils.pm:run_command(9082)|executed
command: pgrep -fl 'vcld [0-9]+:31 ', pid: 14895, exit status: 1, output:
2012-06-29
08:22:51|19357|31:31|image|utils.pm:is_management_node_process_running(9259)|process
is NOT running, identifier: 'vcld [0-9]+:31 '
2012-06-29
08:22:51|19357|31:31|image|utils.pm:reservation_being_processed(9031)|reservation
is NOT currently being processed
2012-06-29 08:22:51|19357|31:31|image|vcld:main(277)|reservation 31 is NOT
already being processed
2012-06-29
08:22:51|19357|31:31|image|utils.pm:get_request_info(4589)|standalone
affiliation found: Local
2012-06-29 08:22:51|19357|31:31|image|vcld:main(282)|retrieved request
information from database
2012-06-29
08:22:51|19357|31:31|image|DataStructure.pm:is_parent_reservation(943)|returning
true: parent reservation ID for this request: 31
2012-06-29
08:22:51|19357|31:31|image|utils.pm:update_request_state(2049)|request 31
state updated to: pending, laststate to: image
2012-06-29 08:22:51|19357|31:31|image|utils.pm:insertloadlog(3933)|inserted
computer=5, begin, beginning to process, state is image
2012-06-29 08:22:51|19357|31:31|image|vcld:make_new_child(510)|loaded
VCL::image module
2012-06-29 08:22:51|19357|31:31|image|vcld:make_new_child(567)|current number
of forked kids: 1
2012-06-29 08:22:51|14897|31:31|image|vcld:make_new_child(583)|vcld
environment variable set to 0 for this process
2012-06-29 08:22:51|14897|31:31|image|Module.pm:new(134)|constructor called,
class=VCL::image
2012-06-29 08:22:51|14897|31:31|image|Module.pm:new(156)|VCL::image object
created
2012-06-29 08:22:51|14897|31:31|image|State.pm:initialize(85)|obtained a
database handle for this state process, stored as $ENV{dbh}
2012-06-29 08:22:51|14897|31:31|image|State.pm:check_image_os(836)|no
corrections need to be made to image OS: vmwarewin7
2012-06-29
08:22:51|14897|31:31|image|DataStructure.pm:is_parent_reservation(943)|returning
true: parent reservation ID for this request: 31
2012-06-29
08:22:51|14897|31:31|image|utils.pm:rename_vcld_process(7183)|reservation
count: 1
2012-06-29
08:22:51|14897|31:31|image|utils.pm:rename_vcld_process(7202)|PARENTIMAGE: 1
2012-06-29
08:22:51|14897|31:31|image|utils.pm:rename_vcld_process(7203)|SUBIMAGE: 0
2012-06-29
08:22:51|14897|31:31|image|utils.pm:rename_vcld_process(7221)|renamed process
to 'vcld 31:31 image plantilla1 vmwarewin7-testt0335-v0 admin'
2012-06-29
08:22:51|14897|31:31|image|DataStructure.pm:is_parent_reservation(943)|returning
true: parent reservation ID for this request: 31
2012-06-29
08:22:51|14897|31:31|image|DataStructure.pm:is_parent_reservation(943)|returning
true: parent reservation ID for this request: 31
2012-06-29 08:22:51|14897|31:31|image|State.pm:initialize(118)|attempting to
load provisioning module: VCL::Module::Provisioning::VMware::VMware
2012-06-29
08:22:51|14897|31:31|image|State.pm:initialize(124)|VCL::Module::Provisioning::VMware::VMware
module loaded
2012-06-29 08:22:51|14897|31:31|image|Module.pm:new(134)|constructor called,
class=VCL::Module::Provisioning::VMware::VMware
2012-06-29
08:22:51|14897|31:31|image|Module.pm:new(156)|VCL::Module::Provisioning::VMware::VMware
object created
2012-06-29
08:22:51|14897|31:31|image|DataStructure.pm:_initialize(594)|computer ID
argument was specified, retrieving data for computer ID: 1
2012-06-29
08:22:52|14897|31:31|image|VMware.pm:get_vmhost_datastructure(923)|created
Re: RPM-ing VCL 2.2.1
Curtis, I'm not sure if this can help - here a link to building VMware SDK's rpm - http://www.firetooth.net/confluence/display/public/vSphere+Perl+SDK+and+CLI+RPM+Packages. Maybe VMware SDK rpm can be included as 4th package ... Thanks. On Jun 25, 2012, at 19:00 , Curtis C. wrote: Hi All, I've been working on an initial spec file for VCL 2.2.1. Currently I believe all the dependencies, CPAN modules included, can be obtained from the EPEL and RPMForge repositories. If the project is going to support RHEL and CentOS only then providing a RPM could allow you to remove the requirement to run (and maintain) the perl libs install script. Still a bit more work to do, but I thought I would send it along before I get too far to find out if anyone has suggestions/comments/criticisms. :) You can see it here: https://github.com/cybera/rpmspecs/blob/master/vcl.spec Right now it creates 3 packages: a main doc package (just contains the sql files right now), a web package, and a management node package. One question I have is about the: use VMware::Vix::Simple; use VMware::Vix::API::Constants in the VIX_API.pm file. Those libraries are not, AFAIK, distributed with VCL and the official install docs don't ask to have them installed either. But the rpmbuild process picks those modules up as requirements. Thanks, Curtis. -- 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 signature.asc Description: Message signed with OpenPGP using GPGMail
creating a base image
hi all, i'm having a problem creating a base windows 7 image and i'm wondering if it is because i'm using vcl 2.2.1 and esxi 5. the lines i think are relevant are below. any pointers would be appreciated. thanks. 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmhost_product_name(5405)|VMware product being used on VM host vclnode01: 'VMware ESXi 5.0.0 build-623860' 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(307)|product: VMware ESXi 5.0.0 build-623860, OS object: VCL::Module::OS::Linux::UnixLab 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 1 (hostsvc/datastore/listsummary) 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclnode01: vim-cmd hostsvc/datastore/listsummary 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_datastore_info(5531)|retrieved datastore info from VM host: |11089|10:10|image| datastore1 |11089|10:10|image| datastore2 |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_name(5848)|unable to determine datastore name from path: '/vmfs/volumes/local-datastore', path does not begin with any of the datastore paths: |11089|10:10|image| '[datastore2]' |11089|10:10|image| '/vmfs/volumes/datastore2' |11089|10:10|image| '/vmfs/volumes/4fd8b523-f4b9c22c-4f9b-001ec9aa4ba2' |11089|10:10|image| '[datastore1]' |11089|10:10|image| '/vmfs/volumes/datastore1' |11089|10:10|image| '/vmfs/volumes/4fcfadc7-c5fa2f69-3ffc-001ec9aa4ba2' |11089|10:10|image| ( 0) VMware.pm, _get_datastore_name (line: 5848) |11089|10:10|image| (-1) VMware.pm, _get_datastore_root_normal_path (line: 5685) |11089|10:10|image| (-2) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-3) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-4) VMware.pm, initialize (line: 313) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_root_normal_path(5687)|failed to determine datastore root normal path, unable to determine datastore name: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line: 5687) |11089|10:10|image| (-1) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-2) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-3) VMware.pm, initialize (line: 313) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_normal_path(5777)|unable to determine normal path, failed to determine datastore root normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_normal_path (line: 5777) |11089|10:10|image| (-1) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-2) VMware.pm, initialize (line: 313) |11089|10:10|image| (-3) Module.pm, new (line: 207) |11089|10:10|image| (-4) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-5) State.pm, initialize (line: 117) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmx_base_directory_path(2749)|unable to determine the vmx base directory path, failed to convert path configured in the VM profile to a normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, get_vmx_base_directory_path (line: 2749) |11089|10:10|image| (-1) VMware.pm, initialize (line: 313) |11089|10:10|image| (-2) Module.pm, new (line: 207) |11089|10:10|image| (-3) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-4) State.pm, initialize (line: 117) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(315)|unable to determine vmx base directory path on VM host vclnode01 |11089|10:10|image| ( 0) VMware.pm, initialize (line: 315) |11089|10:10|image| (-1) Module.pm, new (line: 207) |11089|10:10|image| (-2) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-3) State.pm, initialize (line: 117) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) vcld, make_new_child (line: 564) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|Module.pm:create_provisioning_object(431)|provisioning object could not be created, returning 0 |11089|10:10|image| ( 0) Module.pm, create_provisioning_object (line: 431) |11089|10:10|image| (-1) State.pm, initialize (line: 117) |11089|10:10|image| (-2) Module.pm, new (line: 207) |11089|10:10|image| (-3) vcld, make_new_child (line: 564) |11089|10:10|image| (-4) vcld, main (line: 346) |11089|10:10|image| WARNING
Re: creating a base image
Will ESXi 5.0 and VCL 2.2.1 work well together. Could please send VM host profile which is assigned to vclnode01 host? What do you have for 'Data Store Path' and 'VM path'? On vclnode01 host, where do you map datastore1 and datastore2? I think 'Data Store Path' and 'VM path' in the profile need to match paths for datastore1 and datastore2 on the VM host. Thanks. On Jun 29, 2012, at 12:31 , William Robinson wrote: hi all, i'm having a problem creating a base windows 7 image and i'm wondering if it is because i'm using vcl 2.2.1 and esxi 5. the lines i think are relevant are below. any pointers would be appreciated. thanks. 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmhost_product_name(5405)|VMware product being used on VM host vclnode01: 'VMware ESXi 5.0.0 build-623860' 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(307)|product: VMware ESXi 5.0.0 build-623860, OS object: VCL::Module::OS::Linux::UnixLab 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 1 (hostsvc/datastore/listsummary) 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclnode01: vim-cmd hostsvc/datastore/listsummary 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_datastore_info(5531)|retrieved datastore info from VM host: |11089|10:10|image| datastore1 |11089|10:10|image| datastore2 |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_name(5848)|unable to determine datastore name from path: '/vmfs/volumes/local-datastore', path does not begin with any of the datastore paths: |11089|10:10|image| '[datastore2]' |11089|10:10|image| '/vmfs/volumes/datastore2' |11089|10:10|image| '/vmfs/volumes/4fd8b523-f4b9c22c-4f9b-001ec9aa4ba2' |11089|10:10|image| '[datastore1]' |11089|10:10|image| '/vmfs/volumes/datastore1' |11089|10:10|image| '/vmfs/volumes/4fcfadc7-c5fa2f69-3ffc-001ec9aa4ba2' |11089|10:10|image| ( 0) VMware.pm, _get_datastore_name (line: 5848) |11089|10:10|image| (-1) VMware.pm, _get_datastore_root_normal_path (line: 5685) |11089|10:10|image| (-2) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-3) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-4) VMware.pm, initialize (line: 313) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_root_normal_path(5687)|failed to determine datastore root normal path, unable to determine datastore name: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line: 5687) |11089|10:10|image| (-1) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-2) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-3) VMware.pm, initialize (line: 313) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_normal_path(5777)|unable to determine normal path, failed to determine datastore root normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_normal_path (line: 5777) |11089|10:10|image| (-1) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-2) VMware.pm, initialize (line: 313) |11089|10:10|image| (-3) Module.pm, new (line: 207) |11089|10:10|image| (-4) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-5) State.pm, initialize (line: 117) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmx_base_directory_path(2749)|unable to determine the vmx base directory path, failed to convert path configured in the VM profile to a normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, get_vmx_base_directory_path (line: 2749) |11089|10:10|image| (-1) VMware.pm, initialize (line: 313) |11089|10:10|image| (-2) Module.pm, new (line: 207) |11089|10:10|image| (-3) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-4) State.pm, initialize (line: 117) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(315)|unable to determine vmx base directory path on VM host vclnode01 |11089|10:10|image| ( 0) VMware.pm, initialize (line: 315) |11089|10:10|image| (-1) Module.pm, new (line: 207) |11089|10:10|image| (-2) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-3) State.pm, initialize (line: 117) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) vcld, make_new_child (line: 564) |11089|10:10|image|
Re: RPM-ing VCL 2.2.1
Hi Everett, Have you looked at the automated installation scripts I posted? They are set up for inclusion in an rpm. Larry Dr. Larry Burton Associate Professor Department of Electronics, Computers, and Information Technology School of Technology North Carolina Agricultural and Technical State University -Everett Toews everett.to...@cybera.ca wrote: - To: vcl-user@incubator.apache.org, vcl-...@incubator.apache.org From: Everett Toews everett.to...@cybera.ca Date: 06/29/2012 11:24AM Subject: Re: RPM-ing VCL 2.2.1 Does anyone on the VCL core dev team have an interest in this? Should we create a JIRA issue for it? Regards, Everett On Mon, Jun 25, 2012 at 5:00 PM, Curtis C. serverasc...@gmail.com wrote: Hi All, I've been working on an initial spec file for VCL 2.2.1. Currently I believe all the dependencies, CPAN modules included, can be obtained from the EPEL and RPMForge repositories. If the project is going to support RHEL and CentOS only then providing a RPM could allow you to remove the requirement to run (and maintain) the perl libs install script. Still a bit more work to do, but I thought I would send it along before I get too far to find out if anyone has suggestions/comments/criticisms. :) You can see it here: https://github.com/cybera/rpmspecs/blob/master/vcl.spec Right now it creates 3 packages: a main doc package (just contains the sql files right now), a web package, and a management node package. One question I have is about the: use VMware::Vix::Simple; use VMware::Vix::API::Constants in the VIX_API.pm file. Those libraries are not, AFAIK, distributed with VCL and the official install docs don't ask to have them installed either. But the rpmbuild process picks those modules up as requirements. Thanks, Curtis. NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties.
Re: creating a base image
you are correct. right now those are set to the system defaults: VMware ESX - local network storage VM type:vmware ESXiImage:No Image Repository Path:null Datastore Path:/vmfs/volumes/nfs-datastore1 VM Path:/vmfs/volumes/local-datastore Virtual Switch 0:Private Virtual Switch 1:Public VM Disk:localdisk i'm updating the profile and will give it another shot. thanks! will On 06/29/2012 01:40 PM, Dmitri Chebotarov wrote: Will ESXi 5.0 and VCL 2.2.1 work well together. Could please send VM host profile which is assigned to vclnode01 host? What do you have for 'Data Store Path' and 'VM path'? On vclnode01 host, where do you map datastore1 and datastore2? I think 'Data Store Path' and 'VM path' in the profile need to match paths for datastore1 and datastore2 on the VM host. Thanks. On Jun 29, 2012, at 12:31 , William Robinson wrote: hi all, i'm having a problem creating a base windows 7 image and i'm wondering if it is because i'm using vcl 2.2.1 and esxi 5. the lines i think are relevant are below. any pointers would be appreciated. thanks. 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmhost_product_name(5405)|VMware product being used on VM host vclnode01: 'VMware ESXi 5.0.0 build-623860' 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(307)|product: VMware ESXi 5.0.0 build-623860, OS object: VCL::Module::OS::Linux::UnixLab 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(193)|vim-cmd call count: 1 (hostsvc/datastore/listsummary) 2012-06-29 12:08:30|11089|10:10|image|VIM_SSH.pm:_run_vim_cmd(208)|executed command on VM host vclnode01: vim-cmd hostsvc/datastore/listsummary 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_datastore_info(5531)|retrieved datastore info from VM host: |11089|10:10|image| datastore1 |11089|10:10|image| datastore2 |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_name(5848)|unable to determine datastore name from path: '/vmfs/volumes/local-datastore', path does not begin with any of the datastore paths: |11089|10:10|image| '[datastore2]' |11089|10:10|image| '/vmfs/volumes/datastore2' |11089|10:10|image| '/vmfs/volumes/4fd8b523-f4b9c22c-4f9b-001ec9aa4ba2' |11089|10:10|image| '[datastore1]' |11089|10:10|image| '/vmfs/volumes/datastore1' |11089|10:10|image| '/vmfs/volumes/4fcfadc7-c5fa2f69-3ffc-001ec9aa4ba2' |11089|10:10|image| ( 0) VMware.pm, _get_datastore_name (line: 5848) |11089|10:10|image| (-1) VMware.pm, _get_datastore_root_normal_path (line: 5685) |11089|10:10|image| (-2) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-3) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-4) VMware.pm, initialize (line: 313) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_datastore_root_normal_path(5687)|failed to determine datastore root normal path, unable to determine datastore name: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_datastore_root_normal_path (line: 5687) |11089|10:10|image| (-1) VMware.pm, _get_normal_path (line: 5775) |11089|10:10|image| (-2) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-3) VMware.pm, initialize (line: 313) |11089|10:10|image| (-4) Module.pm, new (line: 207) |11089|10:10|image| (-5) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:_get_normal_path(5777)|unable to determine normal path, failed to determine datastore root normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, _get_normal_path (line: 5777) |11089|10:10|image| (-1) VMware.pm, get_vmx_base_directory_path (line: 2743) |11089|10:10|image| (-2) VMware.pm, initialize (line: 313) |11089|10:10|image| (-3) Module.pm, new (line: 207) |11089|10:10|image| (-4) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-5) State.pm, initialize (line: 117) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:get_vmx_base_directory_path(2749)|unable to determine the vmx base directory path, failed to convert path configured in the VM profile to a normal path: /vmfs/volumes/local-datastore |11089|10:10|image| ( 0) VMware.pm, get_vmx_base_directory_path (line: 2749) |11089|10:10|image| (-1) VMware.pm, initialize (line: 313) |11089|10:10|image| (-2) Module.pm, new (line: 207) |11089|10:10|image| (-3) Module.pm, create_provisioning_object (line: 423) |11089|10:10|image| (-4) State.pm, initialize (line: 117) |11089|10:10|image| (-5) Module.pm, new (line: 207) |11089|10:10|image| WARNING |11089|10:10|image| 2012-06-29 12:08:30|11089|10:10|image|VMware.pm:initialize(315)|unable to determine vmx base directory path on VM host vclnode01 |11089|10:10|image| ( 0)
Re: RPM-ing VCL 2.2.1
On Fri, Jun 29, 2012 at 9:37 AM, Dmitri Chebotarov dcheb...@gmu.edu wrote: Curtis, I'm not sure if this can help - here a link to building VMware SDK's rpm - http://www.firetooth.net/confluence/display/public/vSphere+Perl+SDK+and+CLI+RPM+Packages. Maybe VMware SDK rpm can be included as 4th package ... Thanks Dmitri, I'll take a look. That might meet the dependency. That said, installing that rpm is not part of the official instructions so for most people that particular library will not be available. :) Thanks, Curtis. Thanks. On Jun 25, 2012, at 19:00 , Curtis C. wrote: Hi All, I've been working on an initial spec file for VCL 2.2.1. Currently I believe all the dependencies, CPAN modules included, can be obtained from the EPEL and RPMForge repositories. If the project is going to support RHEL and CentOS only then providing a RPM could allow you to remove the requirement to run (and maintain) the perl libs install script. Still a bit more work to do, but I thought I would send it along before I get too far to find out if anyone has suggestions/comments/criticisms. :) You can see it here: https://github.com/cybera/rpmspecs/blob/master/vcl.spec Right now it creates 3 packages: a main doc package (just contains the sql files right now), a web package, and a management node package. One question I have is about the: use VMware::Vix::Simple; use VMware::Vix::API::Constants in the VIX_API.pm file. Those libraries are not, AFAIK, distributed with VCL and the official install docs don't ask to have them installed either. But the rpmbuild process picks those modules up as requirements. Thanks, Curtis. -- 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
Re: RPM-ing VCL 2.2.1
On Fri, Jun 29, 2012 at 12:31 PM, Larry W Burton lwbur...@ncat.edu wrote: Hi Everett, Have you looked at the automated installation scripts I posted? They are set up for inclusion in an rpm. Hi Larry, I did come across your scripts on the wiki. At this point I was just using the official tar ball and the patch that is in the official instructions. Usually, AFAIK, RPMs only install the software and it's basic default configuration files. Once the package is installed then you could configure/initialize it with something like chef, puppet, ansible, etc, or your custom scripts. Thanks, Curtis. Larry Dr. Larry Burton Associate Professor Department of Electronics, Computers, and Information Technology School of Technology North Carolina Agricultural and Technical State University -Everett Toews everett.to...@cybera.ca wrote: - To: vcl-user@incubator.apache.org, vcl-...@incubator.apache.org From: Everett Toews everett.to...@cybera.ca Date: 06/29/2012 11:24AM Subject: Re: RPM-ing VCL 2.2.1 Does anyone on the VCL core dev team have an interest in this? Should we create a JIRA issue for it? Regards, Everett On Mon, Jun 25, 2012 at 5:00 PM, Curtis C. serverasc...@gmail.com wrote: Hi All, I've been working on an initial spec file for VCL 2.2.1. Currently I believe all the dependencies, CPAN modules included, can be obtained from the EPEL and RPMForge repositories. If the project is going to support RHEL and CentOS only then providing a RPM could allow you to remove the requirement to run (and maintain) the perl libs install script. Still a bit more work to do, but I thought I would send it along before I get too far to find out if anyone has suggestions/comments/criticisms. :) You can see it here: https://github.com/cybera/rpmspecs/blob/master/vcl.spec Right now it creates 3 packages: a main doc package (just contains the sql files right now), a web package, and a management node package. One question I have is about the: use VMware::Vix::Simple; use VMware::Vix::API::Constants in the VIX_API.pm file. Those libraries are not, AFAIK, distributed with VCL and the official install docs don't ask to have them installed either. But the rpmbuild process picks those modules up as requirements. Thanks, Curtis. NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties.
Re: RPM-ing VCL 2.2.1
Hi Curtis, You can do almost anything you wish in an RPM. My goal is to have a one-click VCL installation for basic first-time users. Your suggestions are appreciated. Larry Curtis C. wrote: On Fri, Jun 29, 2012 at 12:31 PM, Larry W Burton lwbur...@ncat.edu wrote: Hi Everett, Have you looked at the automated installation scripts I posted? They are set up for inclusion in an rpm. Hi Larry, I did come across your scripts on the wiki. At this point I was just using the official tar ball and the patch that is in the official instructions. Usually, AFAIK, RPMs only install the software and it's basic default configuration files. Once the package is installed then you could configure/initialize it with something like chef, puppet, ansible, etc, or your custom scripts. Thanks, Curtis. Larry Dr. Larry Burton Associate Professor Department of Electronics, Computers, and Information Technology School of Technology North Carolina Agricultural and Technical State University -Everett Toews everett.to...@cybera.ca wrote: - To: vcl-user@incubator.apache.org, vcl-...@incubator.apache.org From: Everett Toews everett.to...@cybera.ca Date: 06/29/2012 11:24AM Subject: Re: RPM-ing VCL 2.2.1 Does anyone on the VCL core dev team have an interest in this? Should we create a JIRA issue for it? Regards, Everett On Mon, Jun 25, 2012 at 5:00 PM, Curtis C. serverasc...@gmail.com wrote: Hi All, I've been working on an initial spec file for VCL 2.2.1. Currently I believe all the dependencies, CPAN modules included, can be obtained from the EPEL and RPMForge repositories. If the project is going to support RHEL and CentOS only then providing a RPM could allow you to remove the requirement to run (and maintain) the perl libs install script. Still a bit more work to do, but I thought I would send it along before I get too far to find out if anyone has suggestions/comments/criticisms. :) You can see it here: https://github.com/cybera/rpmspecs/blob/master/vcl.spec Right now it creates 3 packages: a main doc package (just contains the sql files right now), a web package, and a management node package. One question I have is about the: use VMware::Vix::Simple; use VMware::Vix::API::Constants in the VIX_API.pm file. Those libraries are not, AFAIK, distributed with VCL and the official install docs don't ask to have them installed either. But the rpmbuild process picks those modules up as requirements. Thanks, Curtis. NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties.
