This post is more than 5 years old
2 Intern
•
706 Posts
0
5059
How can I upgrade VCSA resources?
Hi all,
I have checked VxRail management resouces and default VCSA resources are 4 vCPU, 16GB memory.
Now the sizing is for "Small Environment", I think.
Small enviromnent supported Virtual Machines up to 1,000, but VSAN supported VMs up to 6,400.
If I want to manage more than 1,000 VMs, how can I upgrade VCSA?
Shutdown and modify the resources by C# Clinet?
Is this supported? or Where can I get the information?
Best Regards.
alekseylib
14 Posts
0
April 20th, 2016 18:00
This is a great question. VXRAIL 3.0 appliance includes off the shelf Virtual Center Server (v6.0 Update 1b) release, so all of the guidelines that VMW already provides for our customers equally apply to any VXRAIL 3.0 deployment.
In VXRAIL 3.0, VCSA is deployed with embedded PSC, so when referring to the VMW documentation make sure to look at the recommended (memory / CPU / disk space) values for such configuration.
Memory and CPU sizes are listed here: http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-88571D8A-46E1-464D-A349-4DC43DCAF320.html
Disk Configuration sizes are listed here: http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-FB268055-5D36-4624-A64C-9800D3FCB689.html
The memory and CPU sizes could be adjusted by connecting VMware Client (thick) to the host that's running VCSA, powering it off, making the changes and powering it back on again. Unlike with the past releases, VC 6.0 will automatically make all of the adjustments needed to take advantage of all of the new memory. See http://www.virtuallyghetto.com/2015/02/dynamic-memory-resizing-for-vcenter-server-6-0.html for the details.
Increasing disk sizes is even easier as this change does not require for the VCSA VM to even get power cycled. See https://kb.vmware.com/kb/2126276 and http://www.virtuallyghetto.com/2015/02/increasing-disk-capacity-simplified-with-vcsa-6-0-using-lvm-autogrow.html for the details.
Nori_Ishitsuka
2 Intern
2 Intern
•
706 Posts
0
April 21st, 2016 19:00
Thank you for your kindness answer.
I've understood dynamic algorithm and it's very interesting.
But is the feature support on VxRail?
Because VxRail is appliance, so some vSphere feature is not support.
For example, we can't remove a node from VSAN cluster by vSphere standard procedure.
So I worry about the difference between Standard vSphere and VxRail.
Best Regards.
alekseylib
14 Posts
0
April 22nd, 2016 14:00
My original response did not provide the disk size changes needed for each one of the vmdks used for VCSA.
Below is the breakdown comparison of the disk sizes for each one of the VCSA sizes. (Tiny is not supported with VXRAIL, and is just there for reference).
Also, this breakdown is only applicable to VCSA with embedded PSC configuration that's used with VXRAIL 3.0 release.
Disk (VMDK)
Default Size
(Tiny VCSA)
Small
Medium
Large
Mount Point
Purpose
VMDK1
12GB
12GB
12GB
12GB
/ (10GB)
/boot (132MB)
SWAP (1GB)
Boot directory where the kernel images and boot load configurations go
VMDK2
1.3GB
1.3GB
1.3GB
1.3GB
/tmp
Temporary directory used to store temporary files generated or used by services from vCenter Server
VMDK3
25GB
25GB
50GB
50GB
SWAP
Swap directory used when the system is out of memory to swap to disk
VMDK4
25GB
50GB
50GB
100GB
/storage/core
Core directory where core dumps from VPXD process from the vCenter Server are stored,
VMDK5
10GB
10GB
25GB
25GB
/storage/log
Log directory where vCenter Server stores all logs for the environment
VMDK6
10GB
10GB
25GB
25GB
/storage/db
VMware Postgres database storage location
VMDK7
5GB
5GB
10GB
10GB
/storage/dblog
VMware Postgres database logging location
VMDK8
10GB
25GB
50GB
100GB
/storage/seat
Stats, Events and Tasks (SEAT) directory for VMware Postgres
VMDK9
1GB
1GB
10GB
10GB
/storage/netdump
VMware Netdump collector repository that stores ESXi dumps
VMDK10
10GB
10GB
25GB
25GB
/storage/autodeploy
VMware Auto Deploy repository that stores the thinpackages used for stateless booting of ESXi hosts
VMDK11
5GB
10GB
25GB
100GB
/storage/invsvc
VMware Inventory Service directory where the xDB, Inventory Service bootstrap configuration file, and tomcat configuration files reside
alekseylib
14 Posts
0
April 22nd, 2016 14:00
>> But is the feature support on VxRail?
This workflow is supported with VXRAIL. I'll work with our EMC counterparts (I work as an engineer for VMW on VXRAIL project) to make sure that we have something officially documented on EMC's support site.
>>Because VxRail is appliance, so some vSphere feature is not support.
That's correct, but that's because we want to use VXRAIL to abstract some operations from VC. For example, when you use VCD to manage your vSphere environments, you should not really make changes via VC as VCD would not know (or know too late) when something changed at the lower layers. Same logic applies to VXRAIL manager which is located one management layer above VC.
>>For example, we can't remove a node from VSAN cluster by vSphere standard procedure.
That's right because ESXi hosts are managed both by VC (lower layer) and VXRAIL Manager (upper layer), so the configurations changes have to be reflected in both layers.
ayas
Moderator
Moderator
•
6.7K Posts
0
October 17th, 2016 23:00
Hi ...sorry side attack
Woudl this whole story applicable to VxRail 3.5 as well ?
thanks !
aya