Power Virtual Server

Power Virtual Server

Explore the cloud-based infrastructure offering from IBM that enables businesses to run IBM Power workloads in a virtualized environment on IBM Cloud.


#Power
#Power
#IIBManufacturing
#Power
#Power
#AppConnectEnterprise(ACE)
 View Only

Infrastructure capacity dashboard to monitor the resources Power Virtual Server Private Cloud

By Anusha K posted yesterday

  

Contributors: 

Srikanth Joshi (srikanth.joshi@in.ibm.com 

1. IBM® Power® Virtual Server Overview 

IBM Power Virtual Server is a cloud-based offering that allows you to deploy virtual servers—also known as logical partitions (LPARs)—within minutes. It provides flexible, secure, and scalable compute capacity for enterprise workloads, both in IBM Cloud data centers and at client locations. 

Getting Started with IBM Power Virtual Server Figure 1. Getting Started with IBM Power Virtual Server. 

1.1 IBM Power Virtual Server in IBM data center  

IBM Power Virtual Server (PowerVS) provides cloud-based Power infrastructure hosted in IBM Cloud data centers with dedicated networking and SAN-attached Fiber Channel storage. Clients can select regions close to their own data centers for optimal performance. The PowerVS environment is isolated from other IBM Cloud servers, using secure internal networks while allowing connectivity to IBM Cloud or private clouds. This design preserves enterprise software certifications and ensures compatibility with existing on-premises Power infrastructure. 

1.2 IBM Power Virtual Server Private Cloud in Client Location 

IBM Power Virtual Server Private Cloud is an as-a-service solution that deploys a dedicated stack of compute, network, and storage infrastructure within your own data center, managed by IBM Site Reliability Engineers (SREs) via the IBM Cloud platform. This whole stack is referred as pod. Each pod is linked to an IBM Cloud Satellite location, enabling scalable expansion. It supports RHEL, SLESIBMi, and AIX® operating systems, allowing deployment of enterprise workloads such as Red Hat OpenShift for modern cloud-native applications for RHEL and SLES Operating systems. Also, Oracle workloads which are predominantly deployed on AIX Operating system 

2. IBM Power Virtual Server Private Cloud - Pod Infrastructure Summary 

With PowerVS Private cloud being deployed in client location, it is essential for clients to see how their PowerVS datacenter looks like, what is the consumption of cores, memory on each host, what is storage consumption etc. So, IBM has come up with a dashboard which gives overall capacity of PowerVS Private cloud pods. This document gives the details on the infrastructure details of pods in IBM Power Virtual Server Private Cloud, including location, pricing model, cores, memory, storage, and system types. 

A screenshot of a computer

AI-generated content may be incorrect.

Figure 2. Overview of the pod details 

2.1 Location 

  • Location provides the satellite location details of the pod. 

  • In the Power® Virtual Server interface, click Client Locations to view pod details. 

  • When Client Locations is selected, the following details are displayed: 

2.2 Pricing Model 

  • In IBM® Power® Virtual Server Private Cloud, you can view detailed pod information, including location, pricing model, available cores, available memory, and available storage. 

  • The pricing model indicates whether the pod is in subscription or metered mode. 

2.3 Cores 

  • The Core section includes data on total cores, reserved cores, allocated cores, and available cores. 

  • The Infrastructure Details section provides information at the high level about each Power® Virtual Server pod, including its satellite location, as well as details on cores, memory, and storage. 

2.4 Memory 

  • Memory shows total memory, reserved memory, allocated memory, and available memory. 

2.5 Storage 

  • Storage details include total and available storage capacity. 

  • The Storage Capacity section displays the storage pools available on the Power® Virtual Server pod. By selecting a pool, you can view detailed information such as total storage, allocated storage, and available storage. 

2.6 System Types 

  • The Capacity by System Type section displays all system types along with the number of systems available for each type. 

 

When Client Locations is selected, the following information is displayed: 
The Infrastructure Details section provides a high-level overview of each Power® Virtual Server pod, including its associated Satellite location, along with details such as cores, memory, and storage capacity. 

A screenshot of a computer

AI-generated content may be incorrect.

Figure 3. Core and Memory details of each pod 

The Storage Capacity section presents the storage pools available on the Power® Virtual Server pod. By selecting a specific pool, you can view detailed metrics, including total storage, allocated storage, and available storage.

A white rectangular object with a white stripe

AI-generated content may be incorrect.

Figure 4. Storage details of each pod 

The Capacity by System Type section provides a summary of all system types within the environment, along with the number of systems available for each type. 

Figure 5. Host details of each pod 

When a specific system type is selected, additional details are displayed, including the total number of systems available, as well as information on cores and memory. 

For each system, the following details are provided: 

  • Host MTMS: Refers to the Machine Type Model Serial (MTMS) for a unique identifier assigned to IBM for hardware such as Power Systems, storage devices, and servers. 

  • Machine Type: Identifies the hardware model. 

  • Model: Specifies the variant of the machine type. 

  • Serial Number: A unique identifier used for tracking and supporting purposes. 

  • Total Cores: Represents the total number of cores available in the system. 

  • Reserved Cores: Cores reserved for operational components (e.g., hypervisor, Virtual I/O Server). This capacity is fixed and excluded from billed usage. 

  • Allocated Cores: Cores currently assigned to provisioned resources; these contribute to billed charges. 

  • Available Cores: Unassigned cores that can be allocated for workload deployment. 

  • Total Memory: Represents the total memory capacity of the system. 

  • Reserved Memory: Memory reserved for operational purposes (e.g., hypervisor, Virtual I/O Server). This capacity is fixed and excluded from billed usage. 

  • Allocated Memory: Memory assigned to provisioned resources; contributes to billed charges. 

  • Available Memory: Unassigned memory available for future workload deployment. 

  • Utilization Indicators: Color-coded usage metrics:  

  • Red: 0–10% utilization 

  • Yellow: 10–30% utilization 

  • Green: 30–100% utilization 

When the available CPU and Memory are utilized between 0 to 10 percent, it is shown in red color. Refer to the highlighted host. 

Figure 6. Color coding based on resource utilization-Red 

When the available CPU and Memory are utilized between 10 to 30 percent, it is shown in yellow color. Refer to the highlighted host. 

Figure 7. Color coding based on resource utilization-Yellow 

When the available CPU and Memory are utilized between 30 to 100 percent, it is shown in green. color. Refer to the highlighted host. 

Figure 8. Color coding based on resource utilization-Green 

3. API

The below API retrieves the pod capacity details of a specific cloud instance in IBM Cloud Power Virtual Server. 

curl -X GET https://us-east.power-iaas.cloud.ibm.com/pcloud/v1/cloud-instances/$CLOUD_INSTANCE_ID/pod-capacity -H "Authorization: Bearer $TOKEN" -H "CRN: $CRN" -H "Content-Type: application/json" 

Output:

Figure 9. Pod capacity API response 

4. Use case 

This use case demonstrates how resource utilization is reflected on the client location page when a Virtual Server Instance consumes compute, memory, and storage resources in the Power Virtual Server Private Cloud. 

Step 1: Review the host details prior to creating a Virtual Server Instance in the Power Virtual Server Private Cloud. 

Figure 10. Cores and Memory before VM creation 

Step 2: Create a Virtual Server Instance in the Power Virtual Server Private Cloud. 

Figure 11. Virtual Server Instance in the Power Virtual Server Private Cloud  

Step 3: The host displays the resource utilization details on the client location page. 

Figure 12. Cores and Memory after VM creation 

Step 4: Perform a resize operation on the Virtual Server Instance in the Power Virtual Server Private Cloud. 

Figure 13. Virtual Server Instance resize operation in Power Virtual Server Private Cloud 

Step 5: Verify in the client location page that the reduced size is reflected correctly.

Figure 14. Core and Memory after VM resize operation. 

4. Summary
To summarize, IBM Power Virtual Server Private Cloud offers detailed insights into pod-level infrastructure capacity, especially in Client location deploymentsHere's what clients can monitor: 

  • Cores: Total physical and usable cores per pod. 

  • Memory: Total memory allocated and available. 

  • Storage:  

    • Capacity used vs. total available. 

    • Breakdown per storage controller. 

  • System Types 

    • Number of system units. 

    • MTMs of systems 

  • Rack and Satellite Location Info: For physical layout and redundancy planning. 

5. Reference Links 

0 comments
4 views

Permalink