Skip to main content

How to Increase Size of the VCF Automation Transfer Share

 

How to Increase Size of the VCF Automation Transfer Share


When uploading VM OVA or ISO images to VCF Automation Content Library via the UI the file is first staged into tenant-manager-transfer-bucket S3 object store and only after it is fully uploaded it is pushed by the tenant-manager pod to the target vCenter. The bucket is residing on a shared volume attached to the VCF Automation service cluster and managed by seaweedfs pods. The volume is used also for backups, support bundles and other services.

By default the maximum size of the bucket (its quota) is 50 GB which might not be large enough for big uploads or if there is high concurrency where multiple images might need to be staged.

Let’s say we need to double the size to 100 GB. The resizing needs to be done in two steps:

  • Increase the shared volume size in VCF Operations > Lifecycle > Components > VCF Automation > Actions > Increase Storage size:

We see the shared storage is currently using three 75 GB volumes, so we will increase it to 125 GB. As there are 3 volumes in the group, we will actually consume additional 150 GB of storage.

  • The next step is to change the quota of the tenant-manager-transfer-bucket. This can be done via kubectl from the VCF Automation Services cluster (login as vmware-system-user and elevate to root via sudo – su) by patching the vcfa-bundle package deployment custom resource.
kubectl patch pd vcfa-bundle   -n prelude   --type='merge'   -p '{"spec": {"values": {"tenant_manager": {"transfer": {"seaweedfs": {"size": "100Gi"}}}}}}'

We can validate that the new quota has been set by logging into the seaweedfs-master pod and using weed shell.

root@vcfa-services-lcdpd [ ~ ]# kubectl exec -n vmsp-platform seaweedfs-master-0 -it -- bash
nobody [ /data ]$ weed shell
> s3.bucket.list
  prelude.db.vcfapostgres.wal-backup    size:6246148688 chunk:1978      quota:32212254720       usage:19.39%
  support-bundle        size:2601036459 chunk:16183     quota:64424509440       usage:4.04%
  support-bundle-1b0a57ea-16c4-4b69-ac16-7072cf7f0c82   size:10462923   chunk:1299      quota:10737418240       usage:0.10%
  support-bundle-a59b95e7-103e-4e68-ab2b-0137438b8c64   size:141208086  chunk:20216     quota:10737418240       usage:1.32%
  support-bundle-c4e07db0-58a9-3f6d-aafe-94456a6a3a35   size:1970348420 chunk:66383     quota:16106127360       usage:12.23%
  tenant-manager-transfer-bucket        size:247        chunk:0 quota:107374182400       usage:0.00%
  vcd-migrator.db.vcd-migrator-postgres.wal-backup      size:13576096   chunk:125       quota:10737418240       usage:0.13%
  vcfa-service-manager-storage-bucket   size:3431563383 chunk:1740      quota:53687091200       usage:6.39%
  velero        size:0  chunk:0

Comments

Post a Comment

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 ðŸ”¹ Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
Post a Comment
Read more