Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Multi-disk management for IBM Systems Director VMControl: Part 1

Multi-disk management for virtual server using IBM Systems Director VMControl

Piyush Jain (piyushjain@in.ibm.com), Staff Software Engineer, IBM  
Piyush Jain
Piyush Jain is a Staff Software Engineer at IBM. He is currently working on VMControl under IBM Systems Director, a critical product in the IBM product portfolio. He has an overall experience of around 6 years and holds a bachelor's degree in Information Technology Engineering from Institute of Engineering and Technology (IET) Alwar, Rajasthan, India. You can contact him at piyushjain@in.ibm.com.

Summary:  IBM® Systems Director is a platform management solution that is used to manage physical and virtual systems. IBM Systems Director provides systems management personnel with a single pane of glass, helping reduce IT management complexity and cost. IBM Systems Director VMControl™ is an advanced plug-in installed on top of IBM Systems Director to provide virtualization capabilities. This tutorial talks about multi-disk management for virtual server using the VMControl Representational State Transfer (REST) application programming interfaces (APIs) and command-line interface (CLI).

View more content in this series

Date:  06 May 2013
Level:  Intermediate PDF:  A4 and Letter (419 KB | 23 pages)Get Adobe® Reader®

Comments:  

Multi-disk management while editing a virtual server through CLI

1. On the Power platform:

  • Edit virtual server customization:

    Customization parameters are unique, platform-specific properties that allow a user to customize the action that the user is performing. Customization parameters are available in many different types, but are all specified in a similar fashion. Use the lsvrtcap smcli command with the chvs option as specified below.

    The following example shows the customization parameters in a typical IBM Power Systems environment. Customization parameters for other platforms (such as KVM, z/VM, and so on) will be different. Additionally, there are different rules for retrieving customization on different platforms. For example, KVM requires the virtual server to be stopped in order to modify it. IBM Power Systems server allows you to modify an active virtual server, but only a subset of the properties will be available if the virtual server is stopped.



    Listing 27. Sample response representation
            
    Download
    
    

    Note: The customization properties for modifying a virtual server on KVM platform is not listed in the tutorial due to the constraints of the tutorial length, but included some real-time examples to add or remove disk while modifying virtual server on the KVM platform.

  • Add an existing disk to an existing virtual server:
    • Add an existing disk to an existing virtual server using npivdisks: This example illustrates how to use the npivdisks table parameter to add an existing disk to the existing virtual server.

      Listing 28. Sample response representation
              
      USERID@c598n34:~> smcli chvs -n VS3 -s "assigneddisks=addexistingdisk:npivdisks
      							[16424];diskpriority:1" -v
      Attempt to get capabilities.
      Attempt to modify virtual server 25710 (0x646e).
      Edit virtual server operation completed successfully.
      USERID@c598n34:~>
      

    • Add an existing disk to an existing virtual server using diskphysicalvolumes: This example illustrates how to use the diskphysicalvolumes table parameter to add an existing disk to the existing virtual server.

      Listing 29. Sample response representation
              
      USERID@c598n34:~> smcli chvs -n VS3 -s "assigneddisks=addexistingdisk:
      				diskphysicalvolumes[19501];diskpriority:1" -v
      Attempt to get capabilities.
      Attempt to modify virtual server 25710 (0x646e).
      Edit virtual server operation completed successfully.
      USERID@c598n34:~>
      

  • Add a new disk to an existing virtual server:
    • Add a new disk to an existing virtual server using storagepools: This example illustrates how to use the storagepools table parameter to add a new disk to the existing virtual server.

      Listing 30. Sample response representation
              
      USERID@c598n34:~> smcli chvs -n VS3 -s "assigneddisks=adddisklocation:
      	storagepools[16343];diskpriority:1;diskname:piyush_disk3;disksize:2" -v
      Attempt to get capabilities.
      Attempt to modify virtual server 25710 (0x646e).
      Edit virtual server operation completed successfully.
      USERID@c598n34:~>
      

  • Remove a disk from an existing virtual server:
    • Remove a disk from an existing virtual server using assigneddisks: This example illustrates how to remove a disk from an existing virtual server.

      Listing 31. Sample response representation
              
      USERID@c598n34:~> smcli chvs -A "assigneddisks=-25652" -n 0x646e -v
      Attempt to get capabilities.
      Attempt to modify virtual server 25710 (0x646e).
      Edit virtual server operation completed successfully.
      USERID@c598n34:~>
      


2. On the KVM platform:

  • Add an existing disk to an existing virtual server:
    • Add existing disk to an existing virtual server using existingdisks: This example illustrates how to use the existingdisks parameter table to add an existing disk to the existing virtual server.

      Listing 32. Sample response representation
              
      xnl1207:~ # smcli chvs -s "assigneddisks=addexistingdisk:existingdisks
      				[File/23382/18807];diskpriority:7" -n 0x7834 -v
      Attempt to get capabilities.
      Attempt to modify virtual server 30772 (0x7834).
      Edit virtual server operation completed successfully.
      xnl1207:~ #
      

  • Add a new disk to an existing virtual server:
    • Add a new disk to an existing virtual server using disklocationandsize: This example illustrates how to use the disklocationandsize table parameter to add a new disk to the existing virtual server.

      Listing 33. Sample response representation
              
      xnl1207:~ # smcli chvs -s "assigneddisks=adddisklocation:disklocationandsize
      		[18807];diskname:new6.3disk;disksize:1;virtualbustype:ide;
      		virtualdiskemulation:Hard Disk" -n 0x7834 -v
      Attempt to get capabilities.
      Attempt to modify virtual server 30772 (0x7834).
      Edit virtual server operation completed successfully.
      xnl1207:~ #
      

  • Remove a disk from an existing virtual server:
    • Remove a disk from an existing virtual server using assigneddisks: This example illustrates how to remove a disk from an existing virtual server.

      Listing 34. Sample response representation
              
      xnl1207:~ # smcli chvs -A "assigneddisks[751AF9A46B2C34128EEA164CDA6184DD]=
      					DataDiskRemoved:true" -n 0x7834 -v
      Attempt to get capabilities.
      Attempt to modify virtual server 30772 (0x7834).
      Edit virtual server operation completed successfully.
      xnl1207:~ #
      

5 of 7 | Previous | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=AIX and UNIX, Linux
ArticleID=900562
TutorialTitle=Multi-disk management for IBM Systems Director VMControl: Part 1
publish-date=05062013
author1-email=piyushjain@in.ibm.com
author1-email-cc=nissler@us.ibm.com