Tech-Gen

  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 volume...

  VMware Cloud Foundation APIs: Deploying VCF Automation Whilst VCF Automation is typically deployed during the initial VMware Cloud Foundation deployment phase via VCF Installer it is possible to skip the deployment initially for various reasons such as may you don’t have a use case initially or you want to deploy to a different network that is not available at the time. Under such scenarios you can easily deploy as a Day N task. In this post we will look at how the VCF Automation component can be deployed using the public APIs, this is achieved via the VCF Fleet Lifecycle Service which is tightly integrated into VCF Operations. VCF Fleet Lifecycle Service APIs Used VCF Fleet LCM Service APIs POST /api/v1/identity/token GET /fleet-lcm/v1/sddc-lcms POST /fleet-lcm/v1/components/validations POST /fleet-lcm/v1/components GET /fleet-lcm/v1/tasks/{taskId} Procedure Connect to a system that has access to the infrastructure and is capable of running CURL. Replace the values in the sample...

  Data Store housekeeping In today’s world of Virtualization, we love to thin provision and overcommit. Be vary of the limitations…. When a vSphere datastore becomes full, several issues can arise that may impact virtual machine (VM) operations and the overall performance of the environment: Virtual Machine Operations Halt : If the datastore is full, VMs running on it may not be able to perform operations that require additional storage space; in the worst case, this may affect the writing of new data. VMs will become unresponsive or crash. Snapshots and Backups Fail : Snapshot creation and backup operations will fail because there is no space to store the snapshot data or backup files. Performance Degradation : As the datastore nears full capacity, performance may decline due to insufficient space for swap files and other temporary files that VMs may require. Inability to Power On VMs : If a VM is powered off, it may not be possible to turn it back on if there is not enough space ...

  Access Hierarchy in vCenter Ever wondered how you can give a user access to some artifacts within a vCenter and then deny the same user access to other artifacts? The access hierarchy in vCenter is role-based , leveraging permissions applied at various object levels in the vSphere inventory. Here’s a breakdown Permissions = User/Group + Role + Object Access is granted when a user or group is assigned a role (set of privileges) on a specific inventory object (like a VM, cluster, or datastore). Hierarchical Structure of vCenter Inventory vCenter’s inventory is hierarchical and permission inheritance flows top-down unless explicitly disabled. Here’s the structure from top to bottom: vCenter Root │ ├── Datacenter(s) │ ├── Cluster(s) │ │ ├── Host(s) │ │ │ ├── VM(s) │ │ │ └── Resource Pools │ │ └── DRS/HA settings │ ├── Storage (Datastores, Datastore Clusters) │ └── Networking (Port Groups, dvSwitches) Inheritance Behavior Permissions propagate downward ...