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

Managing the Full Image Lifecycle in IBM PowerVS: Capture, Export and Import

By AnkapaNaidu Kunduru posted 10 hours ago

  

Introduction

IBM Power Virtual Server (PowerVS) makes VM lifecycle management easy with capture, export and import capabilities. These features allow you to create reusable VM images, migrate workloads across environments, and maintain consistent configurations for hybrid cloud strategies.

Why This Matters

In today’s hybrid cloud world, agility is everything. With PowerVS you can capture, export and import VMs effortlessly making it easier to keep your workloads portable, your data secure, and your business running smoothly. Whether you’re using Public or Private PowerVS, these features help you recover quickly from disruptions and migrate workloads without the headaches.

Key Advantages

  • Portability – Move workloads across PowerVS, on-premises and off-premises cloud platforms.
  • Business Continuity – Quick recovery during outages or disasters.
  • Secure Storage – Encrypted, redundant storage in IBM Cloud Object Storage.
  • Fast Deployment – Redeploy captured images for new environments.
  • Hybrid Cloud Ready – Seamless integration for workload mobility.
  • Cost Efficiency – Simplifies backup and migration processes.

How It Works

  1. Capture the VM

    • Use the IBM PowerVS UI or CLI to capture a running VM as a volume-backed image.
    • The image is stored on IBM Power storage (SAN).
  2. Export the Image

    • Choose the destination: Image Catalog, IBM Cloud Object Storage (COS) or both.
    • When exporting to COS:
      • VM volumes are packaged into an OVA file.
      • The OVA file is compressed using gzip and uploaded securely to COS.
  3. Import

    • Import the OVA file back into PowerVS or another environment.
    • Redeploy the captured image to create a clone VM with different configurations (e.g., network settings).

What Customers Will Notice

  • Easier VM management through UI/CLI.
  • Faster migration and deployment.
  • Reliable backups with secure storage.
  • Flexibility to clone VMs with different configurations.
  • Enterprise-grade security and compliance.

UI Behavior:

  • Capture VM:
    • Navigate to Virtual Server Instances → Select VM → Capture.
    • Choose destination (Image Catalog, Cloud Object Storage, or both).
    • while selecting COS or Both you need to Specify region, bucket name, and optional folder. Provide HMAC access key & secret access key
    • Select the Generate checksum file toggle button to generate a checksum file. A checksum file is created and placed in the IBM Cloud Object Storage bucket along with the exported image. The checksum file name is based on the name of the image file and has the file extension .sha256. Use the command shasum -a 256 to ensure that the copied file is correct.

      If you are creating your own image, you can create a checksum image and place it with your own image in the same bucket. One of the ways to generate the checksum image is by using the command shasum -a 256 <filename> or sha256sum <filename>.
      Note: Generating a checksum file might add extra time to the image capture and export process.

    • UI automatically handles packaging into OVA and compression.
  • Export Image:
    • From Image Catalog, select image → Export to COS.
    • Specify region, bucket name and provide HMAC access key & secret key.
    • Progress and status are shown visually.
  • Import Image:
    • From Image Catalog, click Import → Provide COS bucket details.
    • Specify region, bucket name, and optional folder. Provide HMAC access key & secret access key.
    • UI validates and imports the OVA file.

      Use cases:
      1.1 GUI-Based Method for VM Capture & Export


      Navigate to Virtual Server Instances → Select VM → Capture.

      Select volumes and then go to Next page

      Choose destination (Image Catalog, Cloud Object Storage or both).

      while selecting COS or Both you need to Specify region, bucket name, Image Name. Provide HMAC access key & secret access key


      1.2 GUI-Based Method for Export 

      From Image Catalog, select image → Export to COS.

      Specify region, bucket name and provide HMAC access key & secret key

      1.3
      GUI-Based Method for Import

      From Image Catalog, click Import → Provide COS bucket details.

      Specify Image, region, Image Filename, bucket name and Provide HMAC access key & secret access key.

      Give custom image name, tier, storage pool and select import image option

      Find your newly exported image by completing either one of the following tasks:

      • If you chose to capture and export your volume-backed image to Cloud Object Storage, go to your Cloud Object Storage bucket.

      • If you chose to capture and export your volume-backed image to the image catalog, go to Boot images.

      2.1 Add a capture pvm-instance to the jobs queue using API Method

      curl -X POST https://us-east.power-iaas.cloud.ibm.com/pcloud/v2/cloud-instances/$CLOUD_INSTANCE_ID/pvm-instances/$PVM_INSTANCE_ID/capture -H "Authorization: Bearer $TOKEN" -H "CRN: $CRN" -H "Content-Type: application/json" -d '{
              "captureName": "Capture_File_1",
              "captureDestination": "both",
              "cloudStorageRegion": "us-east",
              "cloudStorageImagePath": "XYZ_Bucket",
              "cloudStorageAccessKey": "XXXX-XXXX-XXXX-XXXX",
              "cloudStorageSecretKey": "XXXX-XXXX-XXXX-XXXX"
            }'

      2.2 Add image export job to the jobs queue using API Method

      curl -X POST https://us-east.power-iaas.cloud.ibm.com/pcloud/v2/cloud-instances/$CLOUD_INSTANCE_ID/images/$IMAGE_ID/export -H "Authorization: Bearer $TOKEN" -H "CRN: $CRN" -H "Content-Type: application/json" -d '{
              "Region": "us-east",
              "bucketName": "XYZ_Bucket",
              "AccessKey": "XXXX-XXXX-XXXX-XXXX",
              "SecretKey": "XXXX-XXXX-XXXX-XXXX"
            }
      2.3 Create an cos-image import job using API Method
      curl -X POST https://us-east.power-iaas.cloud.ibm.com/pcloud/v1/cloud-instances/$CLOUD_INSTANCE_ID/cos-images -H "Authorization: Bearer $TOKEN" -H "CRN: $CRN" -H "Content-Type: application/json"
        -d '{
              "imageName": "my-image-catalog-name",
              "region": "us-east",
              "imageFilename": "my-os-image-file.ova.gz",
              "bucketName": "my-cos-bucket-name",
              "accessKey": "my-cos-bucket-access-key",
              "secretKey": "my-cos-bucket-secret-key",
              "storageType": "tier3"    
              "storagePool": "StoragePool-3"
              "storageAffinity": {
                "affinityPolicy": "affinity",
                "affinityPVMInstance": "testVM3", 
              }
            }'

      3.1 Using CLI Capture VM

      ibmcloud pi instance capture create INSTANCE_ID --destination DEST --name NAME [--access-key KEY] [--image-path PATH] [--region REGION] [--secret-key KEY] [--user-tags USER_TAG1[,USER_TAGn]] [--volumes VOLUME1[,VOLUMEn]]

      3.2 Using CLI Export Image
      ibmcloud pi image export IMAGE_ID --access-key KEY --bucket BUCKET_NAME --region REGION_NAME --secret-key KEY

      3.3 Using CLI Import Image

      ibmcloud pi image-import --name IMAGE_NAME --source COS_BUCKET_NAME \
         --access-key ACCESS_KEY --secret-key SECRET_KEY --region REGION

      Additional CLI Options for Managing VM capture, Export and Import operations


      To view the job status or details, run the below commands from the CLI.

      Find your newly exported image by completing either one of the following tasks:

      • To see your newly exported image in the image catalog, use the ibmcloud pi image-list-catalog command:

        ibmcloud pi image-list-catalog [--long] [--json]

      • To see your newly exported image in Cloud Object Storage, use the ibmcloud cos list-objects command:

        ibmcloud cos list-objects --bucket BUCKET_NAME [--delimiter DELIMITER] [--encoding-type METHOD] [--prefix PREFIX] [--starting-token TOKEN] [--page-size SIZE] [--max-items NUMBER] [--region REGION] [--json]



      Known Limitations:
      • The VM capture, image export, and image import features are restricted to one operation at a time per Power Virtual Server workspace. If one of these operations is submitted successfully, then another new operation (VM Capture, Image Export, and Image Import) cannot be submitted until the previous operation is complete.
      • The maximum image size that you can export to Cloud Object Storage is 10 TB. If you select large volumes, the export process can take a significantly long time.

      Reference:

      https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-capturing-exporting-vm
      https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-importing-boot-image
      Power Cloud API | IBM Cloud API Docs
      Power Cloud CLI | IBM Cloud CLI Docs


0 comments
1 view

Permalink