Physical CPU (pCPU) and Virtual CPU (vCPU) Ratio in VMware vSphere ESXi Environment

I have some testings couple of times about this. In a Business Critical Applications, Telco Workloads Applications (Network Function Virtualisation (NFV)), or High CPU intensive applications (without high up and down intensity of CPU workloads), it is always recommended to do dimensioning of 1 vCPU compare to 1 pCPU. Regardless we have the performance benefit from Hyperthread technology around 25% because of the scheduling enhancement from intel processor.

For IT workloads (such as email, web apps, normal apps, etc) we can give better ratio such as 1 pCPU to 4 vCPU or even 1:10 or I also see some 1:20 of the production environments. Due to the VMs will not burst at the same time with a stable and long transactions per second.

These are some tests that I have for Network Function Virtualisation platform, we are pushing one of Telco workloads applications (messages) using Spirent as performance load tester to our VNF (telco VM) which run on the intel servers.

Known Fact for Host and VM during the Test:

  • Configuration of the Host = 20 cores x 2.297 GHz = 45,940 MHz
  • Configuration of the VM = 10 vCPU x 2.297 GHz = 22,297 MHz
  • Only 1 VM is powered on in the host (for testing purpose only to avoid contention)

Observation of Host CPU performance:

  • Max Host during Test Performance (Hz)= 12,992 MHz of total 45,940 MHz
  • Max Host during Test Performance (%)= 28.27 % of total 45,940 MHz

Observation of VM CPU performance:

  • Max VM during Test Performance (Hz)= 12,367 MHz of total 22,297 MHz
  • Max VM during Test Performance (%)= 53.83 % of total 22,297 MHz

Conclusion:

  • Percentage calculation is the same result as MHz calculation. Means, if we calculate percentage usage with total MHz then the result will be MHz usage.
  • CPU clock speed that will be needed by VNF vendor can be calculated based on MHz or percentage calculation, as long as the functionality is considered as apple to apple comparison (need to consider the number of modules/functionality).
  • From performance wise observation, this will also give better view that for NFV workloads, 1 to 1 mapping dimensioning is reflected between vCPU and pCPU —> 10 vCPU is almost the same as 10 pCPU (from MHz calculations usage scenario).

Notes:
Physical CPU is physical cores that is resides in the servers. Virtual CPU is logical cores that is resides in the VMs (can benefit the hyper thread technology).

 

Kind Regards,
Doddi Priyambodo

Update sequence for vSphere 6.0 and its compatible VMware products

Following our technical discussion regarding upgrade VMware environments, actually I already wrote about this topic in different thread  in this blog. But, I would like to emphasise again by using another KB from VMware. VMware has made available certain releases to address critical issues and architectural changes for several products to allow for continued interoperability:

  • vCloud Connector (vCC)
  • vCloud Director (vCD)
  • vCloud Networking and Security (VCNS, formerly vShield Manager)
  • VMware Horizon View
  • VMware NSX for vSphere (NSX Manager)
  • vCenter Operations Manager (vCOPs)
  • vCenter Server / vCenter Server Appliance
  • vCenter Infrastructure Navigator (VIN)
  • vCenter Site Recovery Manager (SRM)
  • vCenter Update Manager (VUM)
  • vRealize Automation Center (vRA, formerly known as vCloud Automation Center)
  • vRealize Automation Application Services (vRAS, formerly vSphere AppDirector)
  • vRealize Business, IT Cost Management (ITBM, formerly VMware IT Business Management)
  • vRealize Configuration Manager (VCM, formerly vCenter Configuration Manager)
  • vRealize Hyperic
  • vRealize Log Insight (vRLI)
  • vRealize Operations Manager (vROPs, formerly known as vCenter Operations Manager, vCOPs)
  • vRealize Orchestrator (vRO, formerly vCenter Orchestrator)
  • vSphere Big Data Extension (BDE)
  • vSphere Data Protection (VDP)
  • vSphere Replication (VR)
  • vSphere ESXi
  • vShield Edge / NSX Edge
  • vShield App / NSX Logical Firewall (NSX LFw)
  • vShield Endpoint / NSX Guest Introspection and Data Security (NSX Guest IDS)
This article only encompasses environments running vSphere and/or vCloud Suite 6.0 and VMware products compatible with vSphere 6.0.

In an environment with vSphere 6.0 and its compatible VMware products, perform the update sequence described in the Supported Update Sequence table.

Supported Update Sequence

Continue reading Update sequence for vSphere 6.0 and its compatible VMware products

Description about My VMware Home Lab in MacBook Pro

I just want to write this, as a personal note for me. Since I always forget when someone ask me this question about my Personal VMware Home Lab that I used to do some researches on-premise.

As described earlier in this post: http://bicarait.com/2015/09/12/penjelasan-mengenai-my-computer-home-lab-untuk-vmware-technology/
Currently I am adding another Home Lab for my research and demo to VMware customers.

MacBook Pro Retina 15-inch, OS X El Capitan (10.11.6), Quad Core 2.5 GHz Intel i7, 16 GB Memory, NVIDIA GeForce GT750M 2GB, 1 TB Flash Storage.

Detail Components:

  • I am using VMware Fusion Professional Version 8.1.1 to create Nested Virtualisation.
  • Control Server is using CentOS Linux 7 (control01.lab.bicarait.com)
    Function: NTP (ntpd), DNS (bind), LDAP (openldap), DHCP (dhcpd)
    IP: 172.16.159.142
    Username: root, Password: VMware1!
  • Shared Storage is using Openfiler 2.6 (storage01.lab.bicarait.com)
    Access: https://172.16.159.139:446/
    Username: openfiler, Password: password
    iSCSI: iqn.2006-01.com.openfiler:tsn.a7cd1aac2554 – “fusiondisk (/mnt/fusiondisk/)” using volume name “fusioniscsi1” size 100 GB – /dev/fusiondisk/fusioniscsi1 – iSCSI target: 172.16.159.139 port 3260 – datastore: ds_fusion_01
  • Virtualisation for Management Cluster is using ESXi 6.0 U2 (esxi01.lab.bicarait.com)
    IP: 172.16.159.141 (vmkernel management)
    Username: root, Password: VMware1!
  • Virtualisation for Payload Cluster is using ESXi 6.0 U2 (esxi02.lab.bicarait.com & esxi03.lab.bicarait.com)
    IP: 172.16.159.151 & 172.16.159.152 (vmkernel management)
    Username: root, Password: VMware1!
  • vCenter is using vCenter Appliance 6.0 U2 (vcsa01.lab.bicarait.com)
    IP: https://172.16.159.150/vsphere-client
    Username: administrator@vsphere.local, Password: VMware1!
  • Virtual Machines to Play with:
    PhotonVM01 – IP:  DHCP – Username: root, Password: VMware1!

This is the screenshot of my fusion environment:

screen-shot-2016-11-03-at-15-32-42

screen-shot-2016-11-04-at-15-11-52

 

Kind Regards,
Doddi Priyambodo

Installation and Documentation Guide for VMware SDDC Proof of Concept

POC Installation and Documentation generally available online both in VMware website and in different blogs, but these are some recommendations:

Google.com and VMware.com of course…

 

Kind Regards,
Doddi Priyambodo

Order to Start vCenter Service in Windows

Order to Start vCenter Service in Windows:

  1. VMware Directory Service
  2. VMware KDC Service
  3. VMware Certificate Service
  4. VMware Identity Management Service
  5. VMware Secure Token Service
  6. VMware VirtualCenter Server

Kind Regards,
Doddi Priyambodo

Berapa Lama untuk melakukan migrasi dari server Physical to Virtual (P2V)?

Pada saat kita memutuskan untuk melakukan konversi ke vSphere Virtual Machine, akan ada proses untuk melakukan konversi dari physical machine atau virtual machine yang sebelumnya.
Kita biasa sebut sebagai Pyhysical to Virtual (P2V) atau Virtual to Virtual (V2V).

Ketika kita ingin menggunakan P2V/V2V, maka metode konversi ini akan melalui jaringan data. Biasanya paling rendah antara source dan destination menggunakan 1Gbps koneksi.
Tetapi jika environment network ini di-share dan tidak dedicated, kemungkinan throughput yaitu antara 20GB s/d 50GB data yang bisa ditransfer dalam 1 jam (perlu dianalisa langsung pada environment customer).
Proses konversi hanya akan mengirim data yang ter-utilisasi saja, misal jika disk besarnya adalah 300 GB tetapi hanya terisi 100 GB, maka data yang dikirim hanya 100 GB saja.

Berikut ini adalah rumus transfer:
Jumlah Data yang ditransfer = Jumlah VM atau Server x Jumlah Besar Disk x Utilisasi Disk

Waktu yang dibutuhkan = Jumlah Data yang ditransfer / Estimasi Throughput

Contoh:
Jika data yang ditransfer besarnya adalah 10 TB, dan throughput adalah 50 GB/hour. Maka waktu yang dibutuhkan adalah 200 jam (8 jam). Dengan asumsi kecepatan pengiriman data stabil.

 

Kind Regards,
Doddi Priyambodo

Pertanyaan Teknis yang diajukan saat vSphere Design during Requirement Analysis

Saya coba merangkum sekilas saja mengenai beberapa pertanyaan teknis dasar yang biasa diajukan saat kita melakukan Requirement Analysis / Design Workshop engagement dengan customer.

Berikut ini adalah beberapa high level questions yang biasa saya ajukan, dan melakukan penggalian lebih dalam berdasarkan pertanyaan tersebut. (Note: ini adalah pertanyaan2 teknis, jadi bukan diajukan ke business person or C level. So, to find the correct audience is important)

  • Compute: To gather information regarding the planned target Compute infrastructure
  • Storage: To understand the current and expected storage landscape
  • vCenter: To describe the state of vCenter to manage the ESXi environment
  • Network: To gather information around current and target network infrastructure
  • Backup & Patching: To understand the current backup and patching methodology.
  • Monitor: To analyze current and expected the Monitoring processes
  • VM Workloads: To analyzie the details of the current physical workloads to be virtualized and consolidated
  • Security: To understand detail the current security practices.
  • Processes & Operations: To understand the current operation procedures and processes
  • Availlaibility & Disaster Recovery: to gather information on Business Continuity Processes

Breakdown lebih detail dari pertanyaan tersebut diatas, bisa saja dilakukan lebih detail, contohnya sebagai berikut:

  • Compute: tipe hardware, network, disk, merk, redundancy, processor, koneksi storage, booting, automation, scalability, dll
  • Storage: SAN/NAS/iSCSI/NFS/VSAN, IOps, Latency, storage technology, cloning/snapshot, replication, dll
  • vCenter: linked mode, appliance, database decision, disk size, cpu memory size, pre-requirements, dll
  • Network: leaf spine, backbone technology, bandwith, VLAN, VXLAN, teaming, VPC, link aggregation, distributed switch, vendors, dll
  • Backup and Patching: storage backup, 3rd party backup, VDP, VADP, Update Manager, dll
  • Monitor: items to monitor, centralized log server, performance, capacity, usage, tresshold, alert, placement, dll
  • VM Workloads: user growth, IOps, Tier1/Tier2/Tier3, mission critical, OS clustering, Java/Oracle/SQL Server/SAP, dll
  • Security: firewall ports, virus protection, distributed firewall, hardening system, lockdown mode, access, dll
  • Processes and Operations: SLA agreements, private/public/hybrid strategy, budget/scope constraint, unique processes, dll
  • Availability & DR: RPO, RTO, VMware HA, Fault Tolerance, Active-Active DC. Bandwith and Hops, priority protected VMs, dll

Semoga bermanfaat.

Kind Regards,
Doddi Priyambodo

Urutan dalam melakukan Backup untuk VMware vRealize Suite

Untuk sistem skala Enterprise, urutan backup adalah sesuatu yang penting untuk menjaga data consistency. Kita perlu menjamin bahwa dependency antara VM satu dengan yang lain selalu terjaga, sehingga pada saat recovery tidak ada data yang missing.

Jika anda mengimplementasikan backup secara otomatis, maka urutan backup ini dapat diatur di backup tools yang anda gunakan (ex: Symantec NetBackup)

Berikut ini adalah urutan backup yang direkomendasikan untuk dijalankan satu persatu pada saat  backup berlangsung:

  1. 1). vRealize Business
  2. 2). vRealize Log Insight
  3. 3). vRealize Operations Manager
  4. 4). vRealize Orchestrator
  5. 5). vRealize Automation (jika VRA arsitekturnya distributed, backup juga perlu berurutan)
    1. a). Proxy Agents
    2. b). DEM Workers
    3. c). DEM Orchestrator
    4. d). Manager Services (backup yang passive dulu, baru aktif)
    5. e). Websites (backup node1, node2, dst)
    6. f). vRealize Automation Appliance (backup secondary node, baru primary)
    7. g). SSO (Identity Appliance)
    8. h). PostgreSQL
    9. i). MS SQL
    10. j). Backup Load Balancers

Bagaimana? Cukup rumit bukan? Enggak ah, simple enough kok 🙂

Sekarang, setelah dibackup. Pasti akan direstore dan Power On the VM. Urutannya tinggal dibalik saja dari urutan backup keatas. Jadi tinggal dibaca dari bawah ke atas.

 

Kind Regards,
Doddi Priyambodo

Pengetesan Performance untuk Oracle Database (Oracle DB Stress Test)

Pengetesan performance untuk Oracle Database sering diperlukan untuk melakukan benchmark antara system yang ada, atau jika kita ingin mengganti ke system yang baru. Kita tidak ingin performance dengan system yang baru akan lebih buruk dengan system yang lama kan.

Berikut ini adalah beberapa cara yang biasa digunakan untuk melakukan pengetesan performance tersebut, selain dari mekanisme dibawah ini ada beberapa cara lain dengan menggunakan beberapa tools lain.

Stress test biasanya dilakukan oleh Application Team dan juga Oracle Database Administrator, dan didampingi oleh Infrastructure Administrator (Servers, Network, Storage)

Tuning dari semua sisi perlu dilakukan untuk memastikan  bahwa system yang di-test berjalan dengan baik, hal ini tidak bisa hanya dilihat dari satu sisi saja (ex: applications, middleware, database, operating system, servers, storage, network, firewalls, routers, dll).

  • Menggunakan tool SwingBench OLTP/DSS kits, Dell Quest Benchmark Factory – Ini adalah tool yang common di Oracle community untuk melakukan pengetesan workloads untuk OLTP (Online Transactions Processing) atau OLAP (Online Analytical Processing).
  • Menggunakan tool pengetesan workloads dari aplikasi menggunakan tool seperti HP Load Runner, IBM Rational Performance Tester, Apache JMeter, yang dibangun oleh pemilik aplikasi (karena harus mengetahui logic dari aplikasi untuk pembuatan test plan-nya). Ini adalah mekanisme yang direkomendasikan, tetapi membutuhkan effort yang lebih besar.
  • Melakukan pengetesan via Storage Benchmark Tool – SAN membutuhkan firmware upgrade, host drivers update, re-cabling, dan perubahan lain. Perubahan ini kadang dapat menyebabkan performance issues. Sebaiknya kita membuat I/O baseline terlebih dahulu dengan menggunakan beberapa tools ini :
    • Iometer
    • Linux/UNIX dd
    • Oracle ORION

 

Kind Regards,
Doddi Priyambodo

Key Factors to create Perfect Design for VMware vSphere Infrastructure

If you are doing vSphere Design right now. Please remember this AMPRS rule for your design document.

Always think your design decision based on these key factors. Availability, Manageability, Performance, Recoverability, and Security.

Especially if it is for Business Critical Application, then you MUST consider all these factors.

 

Design Quality Description
Availability Indicates the effect of a design choice on the ability of a technology and the related infrastructure to achieve highly available operation.

Key metrics: percent of uptime.

Manageability Indicates the effect of a design choice on the flexibility of an environment and the ease of operations in its management. Sub-qualities might include scalability and flexibility. Higher ratios are considered better indicators.

Key metrics:

·         Servers per administrator.

·         Clients per IT personnel.

·         Time to deploy new technology.

Performance Indicates the effect of a design choice on the performance of the environment. This does not necessarily reflect the impact on other technologies within the infrastructure.

·         Key metrics:

·         Response time.

·         Throughput.

Recoverability Indicates the effect of a design choice on the ability to recover from an unexpected incident which affects the availability of an environment.

Key metrics:

·         RTO – Recovery time objective.

·         RPO – Recovery point objective.

Security Indicates the ability of a design choice to have a positive or negative impact on overall infrastructure security. Can also indicate whether a quality has an impact on the ability of a business to demonstrate or achieve compliance with certain regulatory policies.

Key metrics:

·         Unauthorized access prevention.

·         Data integrity and confidentiality.

·         Forensic capabilities in case of a compromise.

 

Kind Regards,

Doddi Priyambodo