vcloud some more lessons learned: transfer volume

For my first vcloud cell I decided to make a seperate logical volume group that I could then export and share with other cloud cell. When I was done doing so I had the following result

A seperate logical volume in a seperate volume group
[root@abincloudhttp logs]# lvdisplay clouddata
--- Logical volume ---
LV Name /dev/clouddata/lvcloud
VG Name clouddata
LV UUID LCUjhy-vQxM-Taxn-0A2e-4ac7-F1UL-chl7dH
LV Write Access read/write
LV Status available
# open 1
LV Size 100.00 GB
Current LE 25599
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2

A new entry in fstab
[root@abincloudhttp logs]# cat /etc/fstab | grep clouddata
/dev/clouddata/lvcloud /opt/vmware/cloud-director/data/transfer/ ext3 defaults 1 2

And after everything was mounted via mount -a, a nice clean mount
[root@abincloudhttp logs]# df -h | grep transfer
99G 188M 94G 1% /opt/vmware/cloud-director/data/transfer

Also changed the export file
[root@abincloudhttp logs]# cat /etc/exports

(This is poor security ofcourse as I should have used my local subnet/subnetmask and no_root_squash is not really good anyway :))

When I tried to start up my cloud cell, I got a 404 warnings that the application was not available. Not knowing where to look I started to google and found that the logs are kept on a straightforward location

In my cell.log I saw some errors about the transfer directory. I then realised that vcloud, made a seperate user vcloud. However by manually creating another volume group, I overwritten the default ownerships a shown below
[root@abincloudhttp data]# ls -alh
total 44K
drwxr-xr-x 6 vcloud vcloud 4.0K Feb 25 10:45 .
drwxr-xr-x 19 vcloud vcloud 4.0K Feb 25 10:31 ..
drwx------ 3 vcloud vcloud 4.0K Feb 25 10:45 activemq
drwx------ 2 vcloud vcloud 4.0K Feb 25 10:31 generated-bundles
drwxr-xr-x 3 root root 4.0K Feb 24 10:51 transfer
drwx------ 2 vcloud vcloud 4.0K Feb 25 10:45 txlog

a simple chown vcloud:vcloud transfer and service vmware-vcd restart solved the problem :)

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.