DMTF DSP1081 Virtual System Migration Profile

1 2

Document Number: DSP1081 3

Date: 2010-02-05 4

Version: 1.0.0c 5

Work Group Version: 0.7.3 6

Virtual System Migration Profile 7

Information for work in progress version: 8

This document is subject to change at any time without further notice. 9

It expires on: 2010-07-31 10

Target version for final status: 1.0.0c 11

Provide any comments through the DMTF Feedback Portal: 12 0H0Hhttp://www.dmtf.org/standards/feedback/ 13

14

Document Type: Specification 15

Document Status: Work in Progress 16

Document Language: E 17

Virtual System Migration Profile

2 Work in progress - expires 2010-07-31 Version 1.0.0c

Copyright Notice 18

Copyright © 2010 Distributed Management Task Force, Inc. (DMTF). All rights reserved. 19

DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems 20 management and interoperability. Members and non-members may reproduce DMTF specifications and 21 documents for uses consistent with this purpose, provided that correct attribution is given. As DMTF 22 specifications may be revised from time to time, the particular version and release date should always be 23 noted. 24

Implementation of certain elements of this standard or proposed standard may be subject to third party 25 patent rights, including provisional patent rights (herein "patent rights"). DMTF makes no representations 26 to users of the standard as to the existence of such rights, and is not responsible to recognize, disclose, 27 or identify any or all such third party patent right, owners or claimants, nor for any incomplete or 28 inaccurate identification or disclosure of such rights, owners or claimants. DMTF shall have no liability to 29 any party, in any manner or circumstance, under any legal theory whatsoever, for failure to recognize, 30 disclose, or identify any such third party patent rights, or for such party’s reliance on the standard or 31 incorporation thereof in its product, protocols or testing procedures. DMTF shall have no liability to any 32 party implementing such standard, whether such implementation is foreseeable or not, nor to any patent 33 owner or claimant, and shall have no liability or responsibility for costs or losses incurred if a standard is 34 withdrawn or modified after publication, and shall be indemnified and held harmless by any party 35 implementing the standard from any and all claims of infringement by a patent owner for such 36 implementations. 37

For information about patents held by third-parties which have notified the DMTF that, in their opinion, 38 such patent may relate to or impact implementations of DMTF standards, visit 39 1H1Hhttp://www.dmtf.org/about/policies/disclosures.php. 40


Version 1.0.0c Work in progress - expires 2010-07-31 3

CONTENTS 41

Foreword ....................................................................................................................................................... 70H7 42 Introduction ................................................................................................................................................... 71H8 43 1 0BScope .................................................................................................................................................... 72H9 44 2 1BNormative references ............................................................................................................................ 73H9 45 3 2BTerms and definitions ............................................................................................................................ 74H9 46 4 3BSymbols and abbreviated terms.......................................................................................................... 75H11 47 5 4BSynopsis.............................................................................................................................................. 76H12 48 6 5BDescription .......................................................................................................................................... 77H13 49

6.1 13BVirtual system migration class schema..................................................................................... 78H13 50 6.2 14BVirtual system migration concepts ............................................................................................ 79H15 51

7 6BImplementation.................................................................................................................................... 80H16 52 7.1 15BVirtual system migration service ............................................................................................... 81H16 53 7.2 16BVirtual system migration capabilities......................................................................................... 82H16 54 7.3 17BMethod parameterization .......................................................................................................... 83H17 55 7.4 18BMigration settings representing capabilities.............................................................................. 84H18 56 7.5 19BCIM_ComputerSystem.ElementName...................................................................................... 85H21 57 7.6 20BVirtual system correlation ......................................................................................................... 86H21 58 7.7 21BIndications................................................................................................................................. 87H22 59

8 7BMethods............................................................................................................................................... 88H24 60 8.1 22BExtrinsic methods...................................................................................................................... 89H24 61 8.2 23BProfile conventions for operations ............................................................................................ 90H30 62

9 8BUse-cases ........................................................................................................................................... 91H34 63 9.1 24BDetection and inspection .......................................................................................................... 92H34 64 9.2 25BMigration operations ................................................................................................................. 93H38 65 9.3 26BIndication delivery ..................................................................................................................... 94H42 66

10 9BCIM elements ...................................................................................................................................... 95H51 67 10.1 27BCIM_AffectedJobElement ......................................................................................................... 96H52 68 10.2 28BCIM_AssociatedJobMethodResult............................................................................................ 97H52 69 10.3 29BCIM_ConcreteDependency ...................................................................................................... 98H53 70 10.4 30BCIM_ConcreteJob..................................................................................................................... 99H53 71 10.5 31BCIM_ComputerSystem.............................................................................................................. 100H54 72 10.6 32BCIM_ElementCapabilities ......................................................................................................... 101H54 73 10.7 33BCIM_Error ................................................................................................................................. 102H55 74 10.8 34BCIM_FilterCollection (Conditional/Optional) ............................................................................. 103H55 75 10.9 35BCIM_HostedService.................................................................................................................. 104H56 76 10.10 36BCIM_IndicationFilter .................................................................................................................. 105H56 77 10.11 37BCIM_MemberOfCollection ........................................................................................................ 106H56 78 10.12 38BCIM_MethodResult ................................................................................................................... 107H57 79 10.13 39BCIM_OwningCollectionElement ................................................................................................ 108H57 80 10.14 40BCIM_OwningJobElement .......................................................................................................... 109H58 81 10.15 41BCIM_RegisteredProfile.............................................................................................................. 110H58 82 10.16 42BCIM_ServiceAffectsElement ..................................................................................................... 111H59 83 10.17 43BCIM_SettingsDefineCapabilities ............................................................................................... 112H59 84 10.18 44BCIM_VirtualSystemMigrationCapabilities.................................................................................. 113H60 85 10.19 45BCIM_VirtualSystemMigrationService ........................................................................................ 114H60 86 10.20 46BCIM_VirtualSystemMigrationSettingData (Parameter) ............................................................. 115H61 87 10.21 47BCIM_VirtualSystemMigrationSettingData (Capabilities) ........................................................... 116H61 88 10.22 48BCIM_InstCreation ...................................................................................................................... 117H62 89 10.23 49BCIM_InstDeletion ...................................................................................................................... 118H62 90 10.24 50BCIM_InstMethodCall ................................................................................................................. 119H63 91 10.25 51BCIM_InstModification ................................................................................................................ 120H64 92

ANNEX A (Informative) Change Log ......................................................................................................... 121H65 93



94

Figures 95 2H 96 2HFigure 1 – Virtual System Migration Profile: Profile class diagram............................................................. 122H13 97 3HFigure 2 Instance diagram: Virtual system migration capabilities............................................................... 123H35 98 4HFigure 3 Instance diagram: Virtual system migration.................................................................................. 124H40 99 5HFigure 4 Virtual system migration related lifecycle indications – initiation .................................................. 125H47 100 6HFigure 5 Virtual system migration related lifecycle indications – progress ................................................. 126H49 101 7HFigure 6 Virtual system migration related lifecycle indications – completion.............................................. 127H51 102 103

Tables 104 Table 1 – Related Profiles........................................................................................................................... 128H12 105 Table 2 – Events Reported through Lifecycle Indications........................................................................... 129H23 106 Table 3 – CIM_VirtualSystemMigrationService.MigrateVirtualSystemToHost( ) Method: Parameters ...... 130H25 107 Table 4 – MigrateVirtualSystemToHost( ): Standard messages................................................................. 131H25 108 Table 5 – CIM_VirtualSystemMigrationService.MigrateVirtualSystemToHost( ) Method: Parameters ...... 132H26 109 Table 6 – MigrateVirtualSystemToSystem( ): Standard messages............................................................ 133H27 110 Table 7 – CIM_VirtualSystemMigrationService. CheckVirtualSystemIsMigratableToHost ( ) Method: 111

Parameters........................................................................................................................ 134H28 112 Table 8 – CheckVirtualSystemIsMigratableToHost( ): Standard messages............................................... 135H29 113 Table 9 – CIM_VirtualSystemMigrationService.CheckVirtualSystemIsMigratableToSystem( ) Method: 114

Parameters........................................................................................................................ 136H29 115 Table 10 – CheckVirtualSystemIsMigratableToSystem( ): Standard messages ........................................ 137H30 116 Table 11 – Operations: CIM_AffectedJobElement ..................................................................................... 138H31 117 Table 12 – Operations: CIM_AssociatedJobMethodResult ........................................................................ 139H31 118 Table 13 – Operations: CIM_ConcreteDependency................................................................................... 140H31 119 Table 14 – Operations: CIM_ElementCapabilities...................................................................................... 141H32 120 Table 15 – Operations: CIM_HostedService .............................................................................................. 142H32 121 Table 16 – Operations: CIM_MemberOfCollection..................................................................................... 143H32 122 Table 17 – Operations: CIM_OwningCollectionElement ............................................................................ 144H33 123 Table 18 – Operations: CIM_OwningJobElement ...................................................................................... 145H33 124 Table 19 – Operations: CIM_ServiceAffectsElement ................................................................................. 146H33 125 Table 20 – Operations: CIM_SettingsDefineCapabilities............................................................................ 147H34 126 Figure 2 Instance diagram: Virtual system migration capabilities............................................................... 148H35 127 Table 21 – CIM Elements: Virtual System Migration profile ....................................................................... 149H51 128 Table 22 – Association: CIM_AffectedJobElement..................................................................................... 150H52 129 Table 23 – Association: CIM_AssociatedJobMethodResult ....................................................................... 151H53 130 Table 24 – Association: CIM_ConcreteDependency .................................................................................. 152H53 131 Table 25 – Class: CIM_ConcreteJob .......................................................................................................... 153H54 132 Table 26 – Class: CIM_ComputerSystem................................................................................................... 154H54 133 Table 27 – Association: CIM_ElementCapabilities ..................................................................................... 155H55 134 Table 28 – Class: CIM_Error....................................................................................................................... 156H55 135 Table 29 – Class: CIM_FilterCollection (Conditional/Optional)................................................................... 157H56 136 Table 30 – Association: CIM_HostedService.............................................................................................. 158H56 137 Table 31 – Class: CIM_IndicationFilter ....................................................................................................... 159H56 138 Table 32 – Association: CIM_MemberOfCollection .................................................................................... 160H57 139 Table 33 – Class: CIM_MethodResult ........................................................................................................ 161H57 140 Table 34 – Association: CIM_OwningCollectionElement............................................................................ 162H58 141



Table 35 – Association: CIM_OwningJobElement...................................................................................... 163H58 142 Table 36 – Class: CIM_RegisteredProfile................................................................................................... 164H59 143 Table 37 – Association: CIM_ServiceAffectsElement................................................................................. 165H59 144 Table 38 – Association: CIM_SettingsDefineCapabilities........................................................................... 166H60 145 Table 39 – Class: CIM_VirtualSystemMigrationCapabilities....................................................................... 167H60 146 Table 40 – Class: CIM_VirtualSystemMigrationService ............................................................................. 168H60 147 Table 41 – Class: CIM_VirtualSystemMigrationSettingData (Parameter) .................................................. 169H61 148 Table 42 – Class: CIM_VirtualSystemMigrationSettingData (Capabilities) ................................................ 170H61 149 Table 43 – Indication: CIM_InstCreation..................................................................................................... 171H62 150 Table 44 – Indication: CIM_InstDeletion ..................................................................................................... 172H63 151 Table 45 – Indication: CIM_InstMethodCall ................................................................................................ 173H63 152 Table 46 – Indication: CIM_InstModification............................................................................................... 174H64 153 154



Foreword 155

This profile - the Virtual System Migration Profile (DSP1081) - was prepared by the System Virtualization, 156 Partitioning and Clustering Working Group of the DMTF. 157

DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems 158 management and interoperability. 159

The authors wish to acknowledge the following people. 160

• Editor: 161

– Michael Johanssen – IBM 162

• Participants from the DMTF System Virtualization, Partitioning and Clustering Working Group: 163

– Gareth Bestor – IBM 164

– Jim Fehlig – Novell 165

– Mark Hapner – Sun Microsystems, Inc. 166

– Ron Goering – IBM 167

– Steve Hand – Symantec Corporation 168

– Daniel Hiltgen – VMware Inc. 169

– Michael Johanssen – IBM 170

– Larry Lamers – VMware Inc. 171

– Andreas Maier - IBM 172

– Aaron Merkin – IBM 173

– John Parchem – Microsoft Corporation 174

– Shishir Pardikar – Citrix Systems Inc. 175

– Nihar Shah – Microsoft Corporation 176

– David Simpson – IBM 177

178



Introduction 179

The information in this specification should be sufficient for a provider or consumer of this data to identify 180 unambiguously the classes, properties, methods, and values that shall be instantiated and manipulated to 181 represent and manage the components described in this document. The target audience for this 182 specification is implementers who are writing CIM-based providers or consumers of management 183 interfaces that represent the components described in this document. 184



Virtual System Migration Profile 185

1 0BScope 186

This profile is a component DMTF management profile that extends the management capabilities of the 187 referencing profile by adding the support to manage the migration of virtual systems. The support 188 includes functionality to initiate and control migration operations, and feasibility checks for a potential 189 migration operation. 190

2 1BNormative references 191

The following referenced documents are indispensable for the application of this document. For dated 192 references, only the edition cited applies. For undated references, the latest edition of the referenced 193 document (including any amendments) applies. 194

8H8HDMTF DSP0004, CIM Infrastructure Specification 2.5 195 http://www.dmtf.org/standards/published_documents/DSP0004_2.5.pdf 196

9H9HDMTF DSP0200, CIM Operations over HTTP 1.3 197 http://www.dmtf.org/standards/published_documents/DSP0200_1.3.pdf 198

11H10HDMTF DSP1001, Management Profile Specification Usage Guide 1.0 199 http://www.dmtf.org/standards/published_documents/DSP1001_1.0.pdf 200

12H11HDMTF DSP1033, Profile Registration Profile 1.0 201 http://www.dmtf.org/standards/published_documents/DSP1033_1.0.pdf 202

13H12HDMTF DSP1042, System Virtualization Profile 1.0 203 http://www.dmtf.org/standards/published_documents/DSP1042_1.0.pdf 204

14H13HDMTF DSP1052, Computer System Profile 1.0 205 http://www.dmtf.org/standards/published_documents/DSP1052_1.0.pdf 206

15H14HDMTF DSP1054, Indications Profile 1.1 207 http://www.dmtf.org/standards/published_documents/DSP1054_1.1.pdf 208

16H15HDMTF DSP1057, Virtual System Profile 1.0 209 http://www.dmtf.org/standards/published_documents/DSP1052_1.0.pdf 210

17H16HSNIA SMI-S, Storage Management Initiative Specification 1.3.0 211 http://www.snia.org/tech_activities/standards/curr_standards/smi/SMI-S_Technical_Position_v1.3.0r5.zip 212 NOTE This profile refers to the following clause of SMI-S 1.3.0, Part2 Common Profiles: 213 Clause 26: Job Control Subprofile 1.3.0 214

18H17HDMTF dsp8026, System Virtualization Message Registry 1.0 215 http://schemas.dmtf.orgs/wbem/messageregistry/1/dsp8026_1.0.xml 216

19H18HISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards 217 http://isotc.iso.org/livelink/livelink.exe?func=ll&objId=4230456&objAction=browse&sort=subtype 218

3 2BTerms and definitions 219

For the purposes of this document, the following terms and definitions apply. For the purposes of this 220 document, the terms and definitions given in 22H19HDMTF DSP1033 and 23H20HDMTF DSP1001 also apply. 221



3.1 222 can 223 used for statements of possibility and capability, whether material, physical, or causal 224

3.2 225 cannot 226 used for statements of possibility and capability, whether material, physical, or causal 227

3.3 228 conditional 229 indicates requirements strictly to be followed in order to conform to the document and from which no 230 deviation is permitted when the specified conditions are met 231

3.4 232 mandatory 233 indicates requirements strictly to be followed in order to conform to the document and from which no 234 deviation is permitted 235

3.5 236 may 237 indicates a course of action permissible within the limits of the document 238

3.6 239 need not 240 indicates a course of action permissible within the limits of the document 241

3.7 242 optional 243 indicates a course of action permissible within the limits of the document 244

3.8 245 referencing profile 246 indicates a profile that owns the definition of this class and can include a reference to this profile in its 247 “Related Profiles” table 248

3.9 249 shall 250 indicates requirements strictly to be followed in order to conform to the document and from which no 251 deviation is permitted 252

3.10 253 shall not 254 indicates requirements strictly to be followed in order to conform to the document and from which no 255 deviation is permitted 256

3.11 257 should 258 indicates that among several possibilities, one is recommended as particularly suitable, without 259 mentioning or excluding others, or that a certain course of action is preferred but not necessarily required 260

3.12 261 should not 262 indicates that a certain possibility or course of action is deprecated but not prohibited 263



3.13 264 unspecified 265 indicates that this profile does not define any constraints for the referenced CIM element 266

3.14 267 implementation 268 a set of CIM providers that realize the classes specified by this profile 269

3.15 270 client 271 an application that exploits facilities specified by this profile 272

3.16 273 this profile 274 this DMTF management profile – the Virtual System Migration Profile 275

3.17 276 virtual system migration 277 the process of moving a virtual system from a source virtualization platform to a target virtualization 278 platform 279

3.18 280 conformant virtual system migration service 281 a service that provides virtual system migration facilities in conformance with this profile 282

3.1 283 virtual computer system 284 virtual system 285 the concept of virtualization as applied to a computer system 286

Other common industry terms are virtual machine, hosted computer, child partition, logical partition, 287 domain, guest, or container. 288

3.19 289 virtualization platform 290 virtualizing infrastructure provided by a host system enabling the provisioning and deployment of virtual 291 systems 292

3.20 293 virtual system migration task 294 a task that performs a particular virtual system migration 295

4 3BSymbols and abbreviated terms 296

3.21 297 CIM 298 Common Information Model 299

3.22 300 CIMOM 301 CIM object manager 302

3.23 303 RASD 304 CIM_ResourceAllocationSettingData 305



4.1 306 SLP 307 Service Location Protocol 308

3.24 309 VS 310 virtual system 311

3.25 312 VSSD 313 CIM_VirtualSystemSettingData 314

3.26 315 VS_MIGRATION_METHOD_CALL 316 the event that marks either the begin or the completion of a virtual system migration method call 317

3.27 318 VS_MIGRATION_JOB_CREATE 319 the event that marks a the creation of an instance of the CIM_ConcreteJob class representing a virtual 320 system migration task 321

3.28 322 VS_MIGRATION_JOB_CHANGE 323 the event that marks a change an instance of the CIM_ConcreteJob class representing a virtual system 324 migration task 325

3.29 326 VS_MIGRATION_JOB_DELETE 327 the event that marks the deletion of an instance of the CIM_ConcreteJob class representing a virtual 328 system migration task 329

5 4BSynopsis 330

Profile Name: Virtual System Migration Profile 331

Version: 1.0.0b 332

Organization: DMTF 333

CIM Schema Version: 2.20 334

Central Class: CIM_VirtualSystemMigrationService 335

Scoping Class: CIM_System 336

This profile is a component profile that defines the minimum object model needed to provide for the 337 migration of virtual systems. 338

182H175HTable 1 lists DMTF management profiles that this profile depends on. 339

Table 1 – Related Profiles 340

Profile Name Organization Version Relationship Description

157H283H Profile Registration DMTF 158H284H183H176H1.0.0 Mandatory The profile that specifies registered profiles.

285H Indications DMTF 286H184H177H1.1.0 Conditional ¹ The profile that specifies indications.



Profile Name Organization Version Relationship Description

Job Control SNIA 185H178H1.3.0 Conditional ² The subprofile that specifies job control.

¹ Condition: The implementation of 24H21HDMTF DSP1054 (186H179HIndications Profile) is required in the scope of the referencing profile if the indications defined in this profile are implemented; see 187H180H7.7.2. ² Condition: The implementation of 25H22HSNIA SMIS: 188H181H1.3.0, Part 2, Clause 26, (189H182HJob Control Subprofile) is required in the scope of this profile if all of the following conditions are met:

• one or more of the methods of the CIM_VirtualSystemMigrationService class as defined in this profile are implemented with asynchronous execution behavior; see 190H183H8.1.1, 191H184H8.1.2, 192H185H8.1.3 and 193H186H8.1.4

• one or more of the indications defined in this profile are implemented; see 194H187H7.7.2 and 195H188HTable 21 under "Indications"

6 5BDescription 341

The Virtual System Migration Profile specifies the modeling of virtual system migration. 342

6.1 13BVirtual system migration class schema 343

196H189HFigure 1 shows the class schema of this profile. It outlines the elements that are owned or specialized by 344 this profile, as well as the dependency relationships between elements of this profile and other profiles. 345 For simplicity in diagrams the prefix CIM_ has been removed from class and association names. 346

ComputerSystem ConcreteJob1 *

AffectedJobElement

1

*

Hos

tedD

epen

denc

y(S

ee "S

yste

m V

irtua

lizat

ion"

pro

file)

RegisteredProfile(See "Profile Registration Profile")

1 *

ReferencedProfile(See "Profile Registration" profile or referencing profile)

System(See referencing profile)

1

*

Elem

entC

onfo

rmsT

oPro

file

(See

"Pro

file

Reg

istra

tion"

pro

file)

VirtualSystemMigrationCapabilitiesVirtualSystemMigrationService * 1

ElementCapabilities

*

0..1ServiceAffectsElement

1

*

HostedService

1

*

ElementConformsToProfile(See "Profile Registration" profile)

VirtualSystemMigrationSettingData1..*

1 Settings-Define-Capabilities

FilterCollection1 *

ConcreteDependency

Indication Filter

1

*

MemberOf-Collection

InstCreation

InstModification

InstDeletion

InstMethodCall

MethodResult

1

0..1

AssociatedJobMethodResult

1

*OwningJobElement

IndicationService(See "Indications" profile)

1 *ElementConformsToProfile (See "Indications" profile)

1 *

OwningCollectionElement

CIM_Error

347 348

Figure 1 – Virtual System Migration Profile: Profile class diagram 349

This profile specifies the use of the following classes and associations: 350



• the CIM_VirtualSystemMigrationService class modeling the virtual system migration service 351

• the CIM_HostedService association modeling the hosting dependency between an instance of 352 the CIM_VirtualSystemMigrationService class representing a virtual system migration service 353 and the instance of the CIM_System class representing a host system 354

• the CIM_ServiceAffectsElement association modeling the relationship between an instance of 355 the CIM_VirtualSystemMigrationService class representing a virtual system migration service 356 and an instance of the CIM_ComputerSystem class representing a virtual system 357

• the CIM_VirtualSystemMigrationCapabilities class modeling the capabilities of a virtual system 358 migration service 359

• the CIM_VirtualSystemMigrationSettingData class 360

– modeling transient parameterization information in invocations of methods of the 361 CIM_VirtualSystemMigrationService class 362

– modelling capabilities expressing defaults and limitations applicable to the use of class 363 instances as parameter 364

• the CIM_SettingsDefineCapabilities association modeling the relation between virtual system 365 migration capabilities and defaults or limitations that apply to migration methods 366

• the CIM_ElementCapabilities association modeling the relationship between an instance of the 367 CIM_VirtualSystemMigrationService class representing a virtual system migration service and 368 and instance of the the CIM_VirtualSystemMigrationCapabilities class representing its 369 capabilities 370

• the CIM_ConcreteJob class modeling a virtual system migration task, the 371 CIM_OwningJobElement association modeling the relationship between a virtual system 372 migration service and a virtual system migration task, and the CIM_AffectedJobElement 373 association modeling the relationship between a virtual system migration task and the affected 374 virtual system 375

• the CIM_InstCreation, CIM_InstModification and CIM_InstDeletion indication classes modeling 376 notifications about lifecycle events of instances of the CIM_ConcreteJob class representing 377 virtual system migration tasks 378

• the CIM_InstMethodCall indication class modeling notifications about 379

– the initiation and termination of methods of the virtual system migration service 380

– the initiation and termination of virtual system migrations within the implementation that are 381 semantically equivalent to performing methods of the virtual system migration service 382

• the CIM_IndicationFilter class modeling criteria for the generation of indication instances 383

• the CIM_FilterCollection class and the CIM_MemberOfCollection association modeling 384 collections of indication filters, the CIM_ConcreteDependency association modeling the 385 relationship between a filter collection and a profile implementation and the 386 CIM_OwningCollectionElement association modeling the relationship between a filter collection 387 the indication service that owns the collection 388

• the CIM_Error class for the representation of error conditions occurring during the execution of 389 intrinsic operations or extrinsic methods 390

In general, any mention of a class in this document means the class itself or its subclasses. For example, 391 a statement such as “an instance of the CIM_VirtualSystemMigrationSettingData class” implies an 392 instance of the CIM_VirtualSystemMigrationSettingData class or of a subclass of the 393 CIM_VirtualSystemMigrationSettingData class. 394



6.2 14BVirtual system migration concepts 395

Virtual machine migration is the process of moving a virtual system from a source virtualization platform to 396 a target virtualization platform, such that after migration the virtual system can be used at the target 397 virtualization platform just as it was used at the source virtualization platform. 398

Three types of migration are distinguished: 399

• Static migration 400

• Dynamic migration 401

• Live migration 402

The implementation of a particular virtual system migration type depends on both the source and the 403 target virtualization platform. Consequently the set of implemented virtual system migration types is not a 404 static property of either source or target virtualization platform; instead the implementation of a particular 405 migration type needs to be determined dynamically by means of check methods that are modeled as part 406 of the virtual system migration service. 407

6.2.1 52BStatic migration 408

Static migration applies primarily to the virtual system definition. Subject virtual systems are considered to 409 be in the in the “Defined” virtual system state, that is, they are not instantiated and not performing work. 410

Static migration comprises activities such as 411

• validating that source and target virtualization platform are compatible 412

• validating that external connections, such as access to network and storage resources defined 413 for the virtual system at the source virtualization platform can be identically redefined at the 414 target virtualization platform 415

• redefining the virtual system at the target virtualization platform, including definition of external 416 connections 417

• moving persistent resources like the content of locally defined virtual disks from the source 418 virtualization platform to the target virtualization platform 419

• removing the virtual system from the source virtualization platform 420

6.2.2 53BDynamic migration 421

Dynamic migration applies to both the virtual system definition and to the virtual system instance. Subject 422 virtual systems may be in the “Defined”, “Active”, “Paused” or “Suspended” virtual system state. The 423 "Active" virtual system state implies that the virtual system is instantiated and actively performs tasks; but 424 while the virtual system may be active when a dynamic migration process is initiated, the virtual system 425 (including all of its virtual resources) is prevented from performing any activities for the complete duration 426 of the migration process. 427

Dynamic migration comprises of the activities required for static migration, but in addition requires 428 activities affecting the virtual system instance, like 429

• re-instantiating the virtual system at the target virtualization platform 430

• establishing external connections that were in effect for the virtual system at the source 431 virtualization platform identically at the target virtualization platform 432

• moving volatile resources like the content of virtual memory from the source virtualization 433 platform to the target virtualization platform 434



6.2.3 Live migration 435

Live migration applies to virtual system definition and virtual system instance. Subject virtual systems may 436 be in the “Defined”, “Active”, “Paused” or “Suspended” virtual system states, that is, they may be 437 instantiated and may continue performing work while the migration process is in progress. 438

Live migration comprises of activities required for static and for dynamic migration. It requires closer 439 coordination between source and target virtualization platform such that state changes resulting from 440 activities performed by the virtual system while the migration is in progress are captured. The integrity of 441 the virtual system, its components, and its external connections is maintained over the whole migration 442 process. External clients of software executed within the virtual system do not notice the ongoing 443 migration process aside from performance impacts. 444

6.2.4 55BEvents 445

Virtual system migration operations are inherently long running tasks. For that reason various events are 446 defined in this profile and incidences of these events may be reported by means of CIM Indications, 447 enabling a client application to monitor the lifecycle and progress of migration operations. Note that 448 events may be triggered by activities other than CIM operations such as operator interventions; 449 regardless of their origination events are reported by means of CIM Indications if indications defined in 450 this profile are implemented. 451

7 6BImplementation 452

This clause details the requirements related to classes and their properties for implementations of this 453 profile. The CIM Schema descriptions for any referenced element and its sub-elements apply. 454

The list of all methods covered by this profile is in clause 197H190H8. The list of all properties covered by this profile 455 is in clause 198H191H10. 456

In references to CIM Schema properties that enumerate values, the numeric value is normative and the 457 descriptive text following it in parenthesis is informational. For example, in the statement “If an instance of 458 the CIM_VirtualSystemMigrationCapabilities class contains the value 3 (MigrateVirtualSystemToSystem) 459 in an element of the SynchronousMethodsSupported[ ] array property”, the “value 3” is normative text and 460 “(MigrateVirtualSystemToSystem)” is descriptive text. 461

7.1 15BVirtual system migration service 462

The CIM_VirtualSystemMigrationService class is used to model virtual migration services. Each 463 conformant virtual system migration service shall be represented by one instance of the 464 CIM_VirtualSystemMigrationService class. 465

7.2 16BVirtual system migration capabilities 466

This subclause details the requirements related to representing the capabilities of a conformant virtual 467 system migration service. 468

7.2.1 56BGeneral 469

The CIM_VirtualSystemMigrationCapabilities class is used to model the capabilities of virtual migration 470 services. The capabilities of a conformant virtual system migration service shall be represented by an 471 instance of the CIM_VirtualSystemMigrationCapabilities class. That instance shall be associated to the 472 instance of the CIM_VirtualSystemMigrationService class representing the conformant virtual system 473 migration service (see 199H192H7.1) through an instance of the CIM_ElementCapabilities association. 474



7.2.2 57BIndication of method implementations 475

Values defined in the ValueMap qualifier of the SynchronousMethodsSupported[ ] and 476 AsynchronousMethodsSupported[ ] array properties of the CIM_VirtualSystemMigrationCapabilities class 477 shall designate corresponding methods of the CIM_VirtualSystemMigrationService class, as follows: 478

• The value 2 (MigrateVirtualSystemToHostSupported) shall designate the 479 MigrateVirtualSystemToHost( ) method 480

• The value 3 (MigrateVirtualSystemToSystemSupported) shall designate 481 MigrateVirtualSystemToSystem( ) method 482

• The value 4 (CheckVirtualSystemIsMigratableToHostSupported) shall designate the 483 CheckVirtualSystemIsMigratableToHost ( ) method 484

• The value 5 (CheckVirtualSystemIsMigratableToSystemSupported) shall designate the 485 CheckVirtualSystemIsMigratableToSystem( ) method 486

NOTE The methods MigrateVirtualSystemToHost( ) and CheckVirtualSystemIsMigratableToHost( ) are intended as 487 a transitional solution only until modeling of cluster support is available. 488

The following rules apply to the use of these values for elements of the SynchronousMethodsSupported[ ] 489 or AsynchronousMethodsSupported[ ] array properties in an instance of the 490 CIM_VirtualSystemMigrationCapabilities class that represents the capabilities of a virtual system 491 migration service: 492

• If a particular method is not implemented, the corresponding qualifier value shall not be present 493 as a value for an element in either array 494

• If a particular method is implemented with synchronous behavior, exactly one element of the 495 SynchronousMethodsSupported[ ] array property shall have the value that corresponds to that 496 method as defined in this subclause 497

• If a particular method is implemented with asynchronous behavior, exactly one element of the 498 AsynchronousMethodsSupported[ ] array property shall have the value that corresponds to that 499 method as defined in this subclause 500

NOTE The normative text requires that methods implementing both synchronous and asynchronous behavior are 501 indicated through both array properties. 502

NOTE A client discovers the fact that asynchronous execution of methods is implemented for one or more methods 503 by checking the value of the AsynchronousMethodsSupported[ ] array property in the instance of the 504 CIM_VirtualSystemMigrationCapabilities class representing the capabilities of a conformant virtual system 505 migration service is not NULL, and contains at least one non-NULL element. 506

7.3 17BMethod parameterization 507

Instances of the CIM_VirtualSystemMigrationSettingData class shall be supported as a value of the 508 MigrationSettingData parameter of methods of the CIM_VirtualSystemMigrationService class. If no 509 instance or an incomplete instance is provided by the client, default values shall be applied as specified 510 in 200H193H7.4 . 511

7.3.1 58BCIM_VirtualSystemMigrationSettingData.MigrationType (Parameter) 512

If specified, the value of the MigrationType property shall be used to determine the requested migration 513 type. If not specified, the respective default value shall be used to determine the migration type; 514 see 201H194H7.4.3 . 515

7.3.2 59BCIM_VirtualSystemMigrationSettingData.Priority (Parameter) 516

If specified, the value of the Priority property shall be used to determine the requested migration priority. If 517 not specified, the respective default value shall be used to determine the migration priority; see 202H195H7.4.4 . 518



7.3.3 60BCIM_VirtualSystemMigrationSettingData.Bandwidth (Parameter) 519

If specified, the value of the Bandwidth property shall be used to determine the requested bandwidth for 520 the migration process. If not specified, the respective default value shall be used to determine the 521 bandwidth; see 203H196H7.4.5 . 522

7.3.4 61BCIM_VirtualSystemMigrationSettingData.BandwidthUnit (Parameter) 523

If specified, the value of the BandwidthUnit property shall be used to determine the unit of the requested 524 bandwidth for the migration process. If not specified, the respective default value shall be used to 525 determine the bandwidth unit; see 204H197H7.4.6 . 526

7.3.5 62BCIM_VirtualSystemMigrationSettingData.TransportType (Parameter) 527

If specified, the value of the TransportType property shall be used to determine the requested transport 528 type for the migration process. If not specified, the respective default value shall be used to determine the 529 transport type; see 205H198H7.4.7 . 530

7.3.6 63BCIM_VirtualSystemMigrationSettingData.OtherTransportType (Parameter) 531

The implementation of the OtherTransportType property is conditional. 532

Condition: The TransportType property is implemented, and the value of 1 (Other) is supported. 533

If the value of the TransportType property is 1 (Other), and the value of the OtherTransportType is 534 specified, the value of the OtherTransportType property shall be used to determine the requested 535 transport type for the migration process. If not specified, the respective default value shall be used to 536 determine the transport type; see 206H199H7.4.6 and 207H200H7.4.8. 537

7.4 18BMigration settings representing capabilities 538

This subclause specifies the use of the CIM_VirtualSystemMigrationSettingData class and the 539 CIM_SettingsDefineCapabilities association for the representation of default migration settings, and for 540 the representation of valid migration settings that are accepted by methods of the related virtual system 541 migration service. 542

7.4.1 64BDefault migration settings 543

An instance of the CIM_VirtualSystemMigrationCapabilities class representing capabilities of a 544 conformant virtual system migration service shall be associated to an instance of the 545 CIM_VirtualSystemMigrationSettingData class through an instance of the CIM_SettingsDefineCapabilities 546 association. 547

Properties in the instance of the CIM_SettingsDefineCapabilities association shall be set as follows: 548

• The value of the PropertyPolicy property shall be 0 (Independent) 549

• The value of the ValueRole property shall be 0 (Default) 550

• The value of the ValueRange property shall be 0 (Point) 551

The instance of the CIM_VirtualSystemMigrationSettingData class shall convey information about the 552 default migration settings that apply if one of the migration methods of the conformant virtual system 553 migration service is called and no value is provided for the MigrationSettingData parameter or if an 554 instance of the CIM_VirtualSystemMigrationSettingData class is provided as value of the 555 MigrationSettingData parameter, but not all properties were assigned values. 556



7.4.2 65BAdmissible migration settings 557

An implementation may provide instances of the CIM_VirtualSystemMigrationSettingData class that 558 describe admissible values or ranges of admissible values for methods of a virtual system migration 559 service. 560

If such instances are provided by an implementation, they shall be associated to the instance of the 561 CIM_VirtualSystemMigrationCapabilities class that describes the capabilities of the respective virtual 562 system migration service (see 208H201H7.2) through instances of the CIM_SettingsDefineCapabilities association 563 where properties shall be set as follows: 564

• The value of the PropertyPolicy property 565

– shall match 0 (Independent) if the properties of the referenced instance of the 566 CIM_VirtualSystemMigrationSettingData class apply without correlation, that is, each 567 property value applies regardless of other property values in the referenced instance 568

– shall match 1 (Correlated) if the properties of the referenced instance of the 569 CIM_VirtualSystemMigrationSettingData class apply with correlation, that is, each value 570 applies only in correlation to other property values in the referenced instance 571

• The value of the ValueRole property shall match 3 (Supported) 572

• The value of the ValueRange property shall match one of the following: 573

– 0 (Point) if the referenced instance of the CIM_VirtualSystemMigrationSettingData class 574 represents one particular admissible setting. A particular instance of the 575 CIM_VirtualSystemMigrationCapabilities class may have zero or more instances of the 576 CIM_VirtualSystemMigrationSettingData class associated this way, expressing a set of 577 admissible values. If such instances are provided, methods of the related virtual system 578 migration service shall accept instances of the CIM_VirtualSystemMigrationSettingData 579 class that match these instances. 580

– 1 (Minimums) if the numeric values in the referenced instance of the 581 CIM_VirtualSystemMigrationSettingData class represent minimum values; in this case, 582 NULL values and values of non-numeric properties shall be ignored. A particular instance 583 of the CIM_VirtualSystemMigrationCapabilities class may have at most one instance of the 584 CIM_VirtualSystemMigrationSettingData class associated this way, expressing the 585 admissible minimum. If such instance is provided, methods of the related virtual system 586 migration service shall accept instances of the CIM_VirtualSystemMigrationSettingData 587 class where the numeric values are above the minimum values as expressed by the 588 referenced instance. 589

– 2 (Maximums) if the numeric values in the referenced instance of the 590 CIM_VirtualSystemMigrationSettingData class represent maximum values; in this case, 591 NULL values and values of non-numeric properties shall be ignored. A particular instance 592 of the CIM_VirtualSystemMigrationCapabilities class may have at most one instance of the 593 CIM_VirtualSystemMigrationSettingData class associated this way, expressing the 594 admissible maximum. If such instance is provided, methods of the related virtual system 595 migration service shall accept instances of the CIM_VirtualSystemMigrationSettingData 596 class where the numeric values are below the maximum values as expressed by the 597 referenced instance. 598

– 3 (Increments) if the numeric values in the referenced instance of the 599 CIM_VirtualSystemMigrationSettingData class represent an increment; in this case, NULL 600 values and values of non-numeric properties shall be ignored. A particular instance of the 601 CIM_VirtualSystemMigrationCapabilities class may have at most one instance of the 602 CIM_VirtualSystemMigrationSettingData class associated this way, expressing the 603 admissible increment. If such instance is provided, a minimum and a maximum shall be 604 provided as specified in this subclause, and the increment shall apply between the 605 minimum and the maximum. If such instance is provided, methods of the related virtual 606 system migration service shall accept instances of the 607



CIM_VirtualSystemMigrationSettingData class where the numeric values are within the 608 range specified by the minimum and the maximum, and within that range match multiples 609 of the increment. 610

7.4.3 66BCIM_VirtualSystemMigrationSettingData.MigrationType (Capabilities) 611

The value of the MigrationType property shall convey the default migration type or an admissible 612 migration type applicable to migration processes initiated or checked through methods of a conformant 613 virtual system migration service. 614

7.4.4 67BCIM_VirtualSystemMigrationSettingData.Priority (Capabilities) 615

The value of the Priority property shall be used to convey the default priority or an admissible priority 616 applicable to migration processes initiated or checked through methods of a conformant virtual system 617 migration service. 618

7.4.5 68BCIM_VirtualSystemMigrationSettingData.Bandwidth (Capabilities) 619

The implementation of the Bandwidth property for the representation of the default bandwidth or an 620 admissible bandwidth is optional. 621

If implemented, the value of the Bandwidth property shall convey the default bandwidth or an admissible 622 bandwidth applicable to migration processes initiated or checked through methods of a conformant virtual 623 system migration service. 624

7.4.6 69BCIM_VirtualSystemMigrationSettingData.BandwidthUnit (Capabilities) 625

The implementation of the Bandwidth property for the representation of the default bandwidth or an 626 admissible bandwidth unit is conditional. 627

Condition: The BandwidthUnit property shall be implemented if the Bandwidth property for the 628 representation of the default bandwidth or of an admissible bandwidth is implemented; see 209H202H7.4.5 . 629

If implemented, the value of the BandwidthUnit property shall convey the default bandwidth unit 630 applicable to the value of the default bandwidth and for the bandwidth property in migration request if the 631 request does not specify a bandwidth unit. 632

7.4.7 70BCIM_VirtualSystemMigrationSettingData.TransportType (Capabilities) 633

The implementation of the TransportType property for the representation of the default transport type or 634 an admissible transport type is optional. 635

If implemented, the value of the TransportType property shall convey the default transport type applicable 636 to migration processes initiated or checked through methods of a conformant virtual system migration 637 service. 638

7.4.8 71BCIM_VirtualSystemMigrationSettingData.OtherTransportType (Capabilities) 639

The implementation of the OtherTransportType property for the representation of the default transport 640 type or an admissible transport type is conditional. 641

Condition: The TransportType property is implemented, and the value 1 (Other) is supported. 642

If the value of the TransportType property is 1 (Other), the value of the OtherTransportType property shall 643 be used to convey the default transport type applicable to migration processes initiated or checked 644 through methods of a conformant virtual system migration service. 645



7.5 19BCIM_ComputerSystem.ElementName 646

The implementation of the ElementName property is optional. 647

The value of the ElementName property in the instance of the CIM_ComputerSystem representing the 648 implicitly created target virtual system should be the same as the value of the ElementName property in 649 the instance of the CIM_ComputerSystem class representing the source virtual system. 650

7.6 20BVirtual system correlation 651

This subclause details requirement with respect to the correlation of the instances of the 652 CIM_ComputerSystem class representing the source and the migrated virtual system. 653

7.6.1 72BGeneral 654

The implementation of virtual system correlation is conditional. 655

Condition: The optional OtherIdentifyingInfo[ ] and IdentifyingDescriptions[ ] array properties as specified 656 by 26H23HDMTF DSP1052:210H203H1.0.0 ( 211H204HComputer System Profile), Subclause 10.1, for instances of the 657 CIM_ComputerSystem class representing virtual systems are implemented. 658

The new virtual system that is implicitly created as part of a virtual system migration process shall be 659 logically identical to the original virtual system. The logical identity relationship shall be represented 660 through values of the OtherIdentifyingInfo[ ] and IdentifyingDescriptions[ ] array properties such that at 661 least one value pair exposed by these properties in the instance of the CIM_ComputerSystem class 662 representing of the source virtual system is present in the instance of the CIM_ComputerSystem class 663 representing the target virtual system. 664

7.6.2 73BCIM_ComputerSystem.OtherIdentifyingInfo[ ] 665

The value of the OtherIdentifyingInfo[ ] array property in the instance of the CIM_ComputerSystem 666 representing the implicitly created migrated virtual system shall contain at least one element from the 667 value of the OtherIdentifyingInfo[ ] array property in the instance of the CIM_ComputerSystem class 668 representing the source virtual system. 669

7.6.3 74BCIM_ComputerSystem.IdentifyingDescriptions[ ] 670

The values of elements in the value of the IdentifyingDescriptions[ ] array property that have the same 671 array index as those elements of the value of the OtherIdentifyingInfo[ ] array property that match the 672 specification in 297H212H205H7.6.2 shall be identical in the instance of the CIM_ComputerSystem representing the 673 implicitly created migrated virtual system and the instance of the CIM_ComputerSystem class 674 representing the source virtual system. 675

7.6.4 75BExample 676

For example, if in the instance of the CIM_ComputerSystem class representing a source virtual system 677

• the value of the OtherIdentifyingInfo[ ] array property is { "CIM:GUID", "CIM:MAC", "CIM:Tag" } 678

• the value of the IdentifyingDescriptions array property is { "01234…", "0123456789AB", 679 "CustomTag" } 680

then these values compose three value pairs that each provides a unique correlatable identification of the 681 source virtual system. The requirements specified in 213H206H7.6.2 and 214H207H7.6.3 require that in the instance of the 682 CIM_ComputerSystem class representing the migrated virtual system, the values of the 683 OtherIdentifyingInfo[ ] array property and the IdentifyingDescriptions[ ] array property exhibit at least one 684 of the value pairs defined in the instance of the CIM_ComputerSystem class representing the source 685 virtual system. For example, if in the instance of the CIM_ComputerSystem class representing the 686 migrated virtual system 687



• the value of the OtherIdentifyingInfo[ ] array property is { "CIM:Tag" } 688

• the value of the IdentifyingDescriptions array property is { "CustomTag" } 689

then the requirement would be complied with. 690

7.7 21BIndications 691

The implementation of indications is optional. 692

This subclause details requirements for the implementation of indications. 693

7.7.1 76BEvents 694

27H24HDMTF DSP1054 (215H208HIndications Profile) defines indications as the means to communicate events. Possible 695 events related to virtual system migration are defined in this subclause. 696

7.7.1.1 107BVS_MIGRATION_METHOD_CALL 697

A VS_MIGRATION_METHOD_CALL event marks either the beginning or the completion of a virtual 698 system migration method call. 699

7.7.1.2 108BVS_MIGRATION_JOB_CREATE 700

A VS_MIGRATION_JOB_CREATE event marks the creation of an instance of the CIM_ConcreteJob 701 class representing a virtual system migration task. 702

7.7.1.3 109BVS_MIGRATION_JOB_CHANGE 703

A VS_MIGRATION_JOB_CHANGE event marks a change in a virtual system migration task that causes 704 one or more property value changes in the instance of the CIM_ConcreteJob class representing the task. 705 Examples are a state change or the successful execution of a major step. 706

7.7.1.4 110BVS_MIGRATION_JOB_DELETE 707

A VS_MIGRATION_JOB_DELETE event marks the deletion of an instance of the CIM_ConcreteJob class 708 representing a virtual system migration task. The lifetime of the instance of the CIM_ConcreteJob class 709 may exceed that of the task it represents such that task information is still available after the task 710 terminated. 711

7.7.2 77BLifecycle indications 712

The implementation of lifecycle indications is optional. If implemented, all of the following rules apply: 713

• The implementation of lifecycle indications for respective events shall be advertised through 714 instances of the CIM_IndicationFilter class (see 310H216H209H10.10) as members of the conditional/optional 715 indication filter collection (see 311H217H210H10.7) 716

• lifecycle indications shall be delivered for respective events according to the conditions 717 specified by the filter query in 312H218H211H7.7.2.10 and in conformance to the specifications provided by the 718 313H219H212HIndications Profile 719

7.7.2.1 111BSupported events 720

314H220H213HTable 2 shows the events that may be reported through lifecycle indications. 721



Table 2 – Events Reported through Lifecycle Indications 722

Event Requirement Query

VS_MIGRATION_METHOD_CALL Optional Select * From CIM_InstMethodCall Where SourceInstance ISA CIM_VirtualSystemMigrationService

VS_MIGRATION_JOB_CREATE Optional Select * From CIM_InstCreation Where SourceInstance ISA CIM_ConcreteJob

VS_MIGRATION_JOB_CHANGE Optional Select * From CIM_InstModification Where SourceInstance ISA CIM_ConcreteJob

VS_MIGRATION_JOB_DELETE Optional Select * From CIM_InstDeletion Where SourceInstance ISA CIM_ConcreteJob

7.7.2.2 112BCIM_InstIndication.CorrelatedIndications[ ] 723

The implementation of the CorrelatedIndications[ ] array property is conditional. 724

Condition: Lifecycle indications are implemented for reporting all of the following events: The 725 VS_MIGRATION_METHOD_CALL event, the VS_MIGRATION_JOB_CREATE and the 726 VS_MIGRATION_JOB_CHANGE event. 727

If the CorrelatedIndications[ ] array property is implemented, the value of the CorrelatedIndications[ ] 728 array property in the referencing indication shall contain one element with a value equal to the value of 729 the IndicationIdentifier property in the referenced indication, referencing a related indication in any of the 730 following cases: 731

• The instance of the CIM_InstMethodCall indication representing the initiation of a method call 732 shall reference the instance of the CIM_InstCreation indication representing the creation of the 733 virtual system migration task resulting from the method call 734

• The instance of the CIM_InstCreation indication representing creation of the virtual system 735 migration task resulting from a method call shall reference the instance of the 736 CIM_InstMethodCall indication representing the initiation of that method call 737

• The instance of the CIM_InstMethodCall indication representing the completion of a method call 738 shall reference the instance of the CIM_InstModification indication representing the state change 739 to “Complete” of the virtual system migration task related to the method call 740

• The instance of the CIM_InstModification indication representing the state change to “Complete” 741 of virtual system migration task related to a method call shall reference the instance of the 742 CIM_InstMethodCall indication representing the completion of that method call 743

7.7.2.3 113BCIM_InstIndication.IndicationFilterName 744

The value of the IndicationFilterName property in instances of the CIM_InstIndication class shall refer to 745 the Name property of the instance of the CIM_IndicationFilter class that effected delivery of the lifecycle 746 indication. The value shall be formatted as follows: 747

<OrgID>:<LocalID> 748

– <OrgID> shall include a copyrighted, trademarked, or otherwise unique name that is owned by 749 the business entity that is creating or defining the value or that is a registered ID assigned to the 750 business entity by a recognized global authority. In addition, to ensure uniqueness, <OrgID> 751 shall not contain a colon (:) 752

– <LocalID> is not further specified 753 Note This rule in effect constrains the structure of the value of the Name property in the CIM_IndicationFilter class 754

(see 315H221H214H7.7.2.9). 755



7.7.2.4 114BCIM_InstIndication.SourceInstance 756

The value of the SourceInstance property in instances of the CIM_InstIndication class shall contain an 757 embedded instance of the CIM_ConcreteJob class that captures the state of the represented virtual 758 system migration task at the time when the reported event occurred (as shown by the value of the 759 IndicationTime property). 760 NOTE Subclause 316H222H215H7.7.2.5 specifies a deviating rule for the specialized CIM_InstMethodCall class 761

7.7.2.5 115BCIM_InstMethodCall.SourceInstance 762

The value of the SourceInstance property in instances of the CIM_InstMethodCall class shall contain an 763 embedded instance of the CIM_VirtualSystemMigrationService class in context of which the reported 764 method call was performed. 765

7.7.2.6 116BCIM_InstMethodCall.MethodName 766

The value of the MethodName property shall be the name of the method that was called on the instance 767 of the CIM_VirtualSystemMigrationService that is reported through the values of the SourceInstance and 768 SourceInstanceModelPath properties. 769

7.7.2.7 117BCIM_InstMethodCall.MethodParameters 770

The value of the MethodParameters property shall be the set of parameter values known at the point in 771 time the indication is reported. The value shall be formatted like an embedded instance, using the string 772 “__MethodParameters” as the predefined class name. 773

7.7.2.8 118BCIM_InstModification.PreviousInstance 774

Support of the PreviousInstance property is optional. 775

If implemented, the value of the PreviousInstance property in instances of the CIM_InstModification class 776 shall contain an embedded instance of the CIM_ConcreteJob class that captures the state of the 777 represented virtual system migration task at the time when the last reported lifecycle event occurred. 778

7.7.2.9 119BCIM_IndicationFilter.Name 779

The value of the CIM_IndicationFilter.Name property shall be conformant with the specification for the 780 IndicationFilterName property in the CIM_Indication class (see 317H223H216H7.7.2.3). 781

7.7.2.10 120BCIM_IndicationFilter.Query 782

The value of the CIM_IndicationFilter.Query property shall be set according to 318H224H217HTable 2 such that the 783 presence of an instance of the CIM_IndicationFilter class as member of the conditional/optional indication 784 filter collection (see 319H225H218H10.7) where the value for the Query property matches one of those shown in the 785 Query column in 320H226H219HTable 2 indicates that the optional support for reporting the event identified by the 786 corresponding element in the Event column through lifecycle indications is implemented. 787

8 7BMethods 788

This clause details the requirements for implementing intrinsic CIM operations and extrinsic methods for 789 the CIM elements defined by this profile. 790

The CIM Schema descriptions for any referenced method and its parameters apply. 791

8.1 22BExtrinsic methods 792

This subclause details specifications for extrinsic methods of the CIM_VirtualSystemMigrationService 793 class. 794



8.1.1 78BCIM_VirtualSystemMigrationService.MigrateVirtualSystemToHost( ) 795

NOTE The MigrateVirtualSystemToHost( ) method is intended as a transitional solution only until modeling of 796 cluster support is available. 797

The implementation of the MigrateVirtualSystemToHost( ) method is optional; if implemented, the 798 requirements defined in 227H220H7.2.2 apply. 799

Condition: The implementation of the MigrateVirtualSystemToHost( ) method is required if the 800 MigrateVirtualSystemToSystem( ) method is not implemented; see 228H221H8.1.2 . 801

229H222HTable 3 specifies detailed requirements for the MigrateVirtualSystemToHost( ) method. 802

Table 3 – CIM_VirtualSystemMigrationService.MigrateVirtualSystemToHost( ) Method: Parameters 803

Qualifiers Name Type Description/Values

IN ComputerSystem CIM_ComputerSystem REF

Reference to an instance of the CIM_ComputerSystem class representing the virtual system to be migrated.

IN DestinationHost string Address of the destination host; for the format see CIM Schema description.

IN MigrationSettingData string Embedded instance of the CIM_VirtualSystemMigrationSettingData class.

IN NewSystemSettingData string Embedded instance of the CIM_VirtualSystemSettingData class that replaces or adds property values for the virtual system after it is migrated.

IN NewResourceSettingData string[ ] Embedded instances of the CIM_ResourceAllocationSettingData class that replace or add property values for virtual resources.

OUT Job CIM_ConcreteJob REF A reference to the job that performs the task (NULL if the task is completed on return).

The method shall either return a return code or an exception. For return code values, see the CIM 804 schema description. 805

The implementation of standard messages is optional. 230H223HTable 4 specifies the optional standard messages 806 for the MigrateVirtualSystemToHost( ) method. 807

Table 4 – MigrateVirtualSystemToHost( ): Standard messages 808

(Return Code) MessageID Message Text

(6) DMTF SVPC0003 The virtual system named <Virtual_System_EN> does not exist.

(1) DMTF SVPC0004 The virtual system named <Virtual_System_Name> is in the <Virtual_System_State> state, but the requested operation requires one of the following virtual system states: <Required_Virtual_System_States>.

(1) DMTF SVPC0005 The virtual system named <Virtual_System_Name> has the virtual system type <Virtual_System_Type> state, but the requested operation requires one of the following virtual system types: <Required_Virtual_System_Types>.

(1) DMTF SVPC0006 The virtual system named <Virtual_System_Name> <Virtual_System_Config_Error> that prevent(s) the requested operation.

(1) DMTF SVPC0101 The file <File_Name_Name> <Unexpected_File_State>.




(1) DMTF SVPC0102 The file <File_Name_Name> <Failed_File_Operation>.

(4096) DMTF SVPC8001 The migration process migrating the virtual system named <Virtual_System_Name> from the host system named <Source_Host_Name> to the host system named <Target_Host_Name> has been initiated.

(1) DMTF SVPC8003 The migration process migrating the virtual system named <Virtual_System_Name> from the host system named <Source_Host_Name> to the host system named <Target_Host_Name> has failed.

(0) DMTF SVPC8004 The migration process migrating the virtual system named <Virtual_System_Name> from the host system named <Source_Host_Name> to the host system named <Target_Host_Name> has successfully completed.

(1) DMTF SVPC8020 The target host named <Target_Host_Name><Target_Host_State>.

(1) DMTF SVPC8021 The target virtual system named <Virtual_System_Name> already exists.

(1) DMTF SVPC8022 The target virtual system named <Virtual_System_Name> <Failed_Activity>.

(1) DMTF SVPC8023 The target virtual system named <Virtual_System_Name> <Configuration_Error>.

(1) DMTF SVPC8030 The resource requirements of the virtual system named <Virtual_System_Name> for the <Resource_Type> can not be satisfied at the target host system named <Target_Host_Name>.

(1) DMTF SVPC8040 The <Migration_Operation>( ) parameter <Parameter_Name> at index <Parameter_Index> is <Parameter_Error>; expected parameter value is <Parameter_Spec>.

(1) DMTF SVPC8041 The migration of the virtual system named <Virtual_System_Name> to the target host system named <Target_Host_Name> failed because a <Component_Error> <Component_RC> occurred.

(1) DMTF SVPC8042 The migration of the virtual system named <Virtual_System_Name> to the target host system named <Target_Host_Name> failed because a timeout occurred.

8.1.2 79BCIM_VirtualSystemMigrationService.MigrateVirtualSystemToSystem( ) 809

The implementation of the MigrateVirtualSystemToSystem( ) method is optional; if implemented, the 810 requirements defined in 231H224H7.2.2 apply. 811

232H225HTable 5 specifies detailed requirements for the MigrateVirtualSystemToSystem( ) method. 812

Table 5 – CIM_VirtualSystemMigrationService.MigrateVirtualSystemToHost( ) Method: Parameters 813




IN DestinationSystem CIM_System REF Reference to an instance of the CIM_System class representing the destination host.

IN MigrationSettingData String Embedded instance of the CIM_VirtualSystemMigrationSettingData class.

IN NewSystemSettingData String Embedded instance of the CIM_VirtualSystemSettingData class that replaces or adds property values for the



Qualifiers Name Type Description/Values virtual system after it is migrated.


OUT NewComputerSystem CIM_ComputerSystem REF

Reference to an instance of the CIM_ComputerSystem class representing the virtual computer system after it has been migrated.

OUT Job CIM_ConcreteJob REF A reference to the job that performs the task (NULL if the task is completed on return).


The implementation of standard messages is optional. 233H226HTable 6 specifies the optional standard messages 816 for the MigrateVirtualSystemToSystem( ) method. 817

Table 6 – MigrateVirtualSystemToSystem( ): Standard messages 818


(6) DMTF SVPC0003 The virtual system named <Virtual_System_Name> does not exist.




(1) DMTF SVPC0101 The file <File_Name_Name> <Unexpected_File_State>.

(1) DMTF SVPC0102 The file <File_Name_Name> <Failed_File_Operation>.

(4096) DMTF SVPC8001 The migration process migrating the virtual system named <Virtual_System_Name> from the host system named <Source_Host_Name> to the host system named <Target_Host_Name> has been initiated.

(1) DMTF SVPC8003 The migration process migrating the virtual system named <Virtual_System_Name> from the host system named <Source_Host_Name> to the host system named <Target_Host_Name> has failed.

(0) DMTF SVPC8004 The migration process migrating the virtual system named <Virtual_System_Name> from the host system named <Source_Host_Name> to the host system named <Target_Host_Name> has successfully completed.









(1) DMTF SVPC8040 The <Migration_Operation>( ) parameter <Parameter_Name> at index <Parameter_Index> is <Parameter_Error>; expected parameter value is <Parameter_Spec>.

(1) DMTF SVPC8041 The migration of the virtual system named <Virtual_System_Name> to the target host system named <Target_Host_Name> failed because a <Component_Error> <Component_RC> occurred.

(1) DMTF SVPC8042 The migration of the virtual system named <Virtual_System_Name> to the target host system named <Target_Host_Name> failed because a timeout occurred.

8.1.3 80BCIM_VirtualSystemMigrationService.CheckVirtualSystemIsMigratableToHost( ) 819

NOTE The CheckVirtualSystemIsMigratableToHost( ) method intended as a transitional solution only until modeling 820 of cluster support is available. 821

The implementation of the CheckVirtualSystemIsMigratableToHost( ) method is conditional; if 822 implemented, the requirements defined in 234H227H7.2.2 apply. 823

Condition: The implementation of the CheckVirtualSystemIsMigratableToHost( ) method is required if the 824 CheckVirtualSystemIsMigratableToSystem( ) method is not implemented; see 235H228H8.1.4 . 825

The method shall be implemented with synchronous behavior only. 327H229H 826

Table 7 specifies detailed requirements for the CheckVirtualSystemIsMigratableToHost( ) method. 827

Table 7 – CIM_VirtualSystemMigrationService. CheckVirtualSystemIsMigratableToHost ( ) Method: 828 Parameters 829




IN DestinationHost string Address of the destination host; for the format see CIM Schema description.




OUT IsMigratable boolean Method result indicating whether the source virtual system is migratable to the target host.


The implementation of standard messages is optional. 237H230HTable 8 specifies the optional standard messages 832 for the CheckVirtualSystemIsMigratableToHost( ) method. 833



Table 8 – CheckVirtualSystemIsMigratableToHost( ): Standard messages 834











8.1.4 81BCIM_VirtualSystemMigrationService.CheckVirtualSystemIsMigratableToSystem( ) 835

The implementation of the CheckVirtualSystemIsMigratableToSystem( ) method is optional; if 836 implemented, the requirements defined in 238H231H7.2.2 apply. 837

The method shall be implemented with synchronous behavior only. 838

172H329H239H232HTable 9 specifies detailed requirements for the CheckVirtualSystemIsMigratableToSystem( ) method. 839

Table 9 – CIM_VirtualSystemMigrationService.CheckVirtualSystemIsMigratableToSystem( ) 840 Method: Parameters 841




IN DestinationSystem CIM_System REF Reference to an instance of the CIM_System class representing the destination host.




OUT IsMigratable boolean Method result indicating whether the source



Qualifiers Name Type Description/Values virtual system is migratable to the target host.


Support of standard messages is optional. 240H233HTable 10 specifies the optional standard messages for the 844 CheckVirtualSystemIsMigratableToSystem( ) method. 845

Table 10 – CheckVirtualSystemIsMigratableToSystem( ): Standard messages 846











8.2 23BProfile conventions for operations 847

Support for operations for each profile class (including associations) is specified in the following 848 subclauses. Each subclause includes either a statement “All operations in the default list in subclause 173H330H241H234H8.2 849 are supported as described by 28H25HDMTF DSP0200 or a table listing all of the operations that are not 850 supported by this profile or where the profile requires behavior other than that described by 851 29H26HDMTF DSP0200. 852

The default list of operations is as follows: 853

• GetInstance 854

• Associators 855

• AssociatorNames 856

• References 857

• ReferenceNames 858

• EnumerateInstances 859

• EnumerateInstanceNames 860



A compliant implementation shall support all of the operations in the default list for each class, unless the 861 “Requirement” column states something other than Mandatory. 862

This profile defines methods in terms of 30H27HDMTF DSP0200 . 863

8.2.1 82BCIM_AffectedJobElement 864

245H235HTable 11 lists operations that either have special requirements beyond those from 31H28HDMTF DSP0200 or 865 shall not be implemented. 866

Table 11 – Operations: CIM_AffectedJobElement 867

Operation Requirement Messages

Associators Unspecified None

AssociatorNames Unspecified None

References Unspecified None

ReferenceNames Unspecified None

8.2.2 83BCIM_AssociatedJobMethodResult 868


Table 12 – Operations: CIM_AssociatedJobMethodResult 871






8.2.3 84BCIM_ConcreteDependency 872


Table 13 – Operations: CIM_ConcreteDependency 875






8.2.4 85BCIM_ConcreteJob 876

All operations in the default list in subclause 251H238H8.2 are supported as described by 34H31HDMTF DSP0200 . 877



8.2.5 86BCIM_ComputerSystem 878

All operations in the default list in subclause 253H239H8.2 are supported as described by 35H32HDMTF DSP0200 . 879

8.2.6 87BCIM_ElementCapabilities 880


Table 14 – Operations: CIM_ElementCapabilities 883






8.2.7 88BCIM_FilterCollection 884

All operations in the default list in subclause 257H241H8.2 are supported as described by 37H34HDMTF DSP0200. 885

8.2.8 89BCIM_HostedService 886


Table 15 – Operations: CIM_HostedService 889






8.2.9 90BCIM_IndicationFilter 890


8.2.10 91BCIM_MemberOfCollection 892


Table 16 – Operations: CIM_MemberOfCollection 895









8.2.11 92BCIM_MethodResult 896


8.2.12 93BCIM_OwningCollectionElement 898


Table 17 – Operations: CIM_OwningCollectionElement 901






8.2.13 94BCIM_OwningJobElement 902


Table 18 – Operations: CIM_OwningJobElement 905






8.2.14 95BCIM_RegisteredProfile 906


8.2.15 96BCIM_ServiceAffectsElement 908


Table 19 – Operations: CIM_ServiceAffectsElement 911









8.2.16 97BCIM_SettingsDefineCapabilities 912


Table 20 – Operations: CIM_SettingsDefineCapabilities 915






8.2.17 98BCIM_VirtualSystemMigrationCapabilities 916


8.2.18 99BCIM_VirtualSystemMigrationService 918


8.2.19 100BCIM_VirtualSystemMigrationSettingData 920


9 8BUse-cases 922

The following use-cases and object diagrams illustrate use of this profile. They are for informational 923 purposes only and do not introduce behavioral requirements for implementations of the profile. 924

9.1 24BDetection and inspection 925

This set of use-cases describe how to determine whether a conformant migration service is available for a 926 particular virtual system, and whether the virtual system is migratable to a particular target host system. 927 NOTE Use-cases describing the discovery of profile implementations and the detection of instances of the central 928

class are described in 50H47HDMTF DSP1033. 929

9.1.1 101BDetermine availability of migration services for a virtual system 930

Assumption: The client knows a reference to an instance of the CIM_ComputerSystem class that 931 represents a virtual system. 932

• The client resolves the CIM_ServiceAffectsElement association to find the instance of the 933 CIM_VirtualSystemMigrationService class that represents the virtual system migration service 934 that is responsible for the virtual system, invoking the intrinsic AssociatorNames( ) CIM 935 operation with parameter values set as follows: 936

– the value of the ObjectName parameter refers to the instance of the CIM_ComputerSystem 937 class that represents the virtual system 938



– the value of the AssocClass parameter is set to “CIM_ServiceAffectsElement” 939

– the value of the ResultClass parameter is set to “CIM_VirtualSystemMigrationService” 940

The result is a set of references containing one element referencing the 941 CIM_VirtualSystemMigrationService class representing virtual system migration services. 942

Result: The client knows virtual system migration services that are responsible for the virtual system; see 943 51H48HDMTF DSP1033 for recipes that describe the detection of profile conformant elements, i.e. a virtual 944 system migration service that is conformant to this profile. 945

9.1.2 102BDetermine the capabilities of a virtual system migration service 946

This use-case describes how to determine the capabilities of a virtual system migration service. 947

948 Figure 2 Instance diagram: Virtual system migration capabilities 949

Assumption: The client knows a reference to an instance of the CIM_VirtualSystemMigrationService 950 class representing a virtual system migration service. 951

1) The client resolves the CIM_ElementCapabilities association to find the instance of the 952 CIM_VirtualSystemMigrationCapabilities class that represents the capabilities of the virtual 953 system migration service, invoking the intrinsic AssociatorNames( ) CIM operation with 954 parameter values set as follows: 955



– the value of the ObjectName parameter refers to the instance of the 956 CIM_VirtualSystemMigrationService class that represents the virtual system migration 957 service. In 283H254HFigure 2, that input instance is the instance VSMS. 958

– the value of the AssocClass parameter is set to “CIM_ElementCapabilities” 959

– the value of the ResultClass parameter is set to “CIM_VirtualSystemMigrationCapabilities” 960

The result is a set of references containing one element referencing the 961 CIM_VirtualSystemMigrationCapabilities class representing the capabilities of the virtual system 962 migration service. (284H255HFigure 2: The result is a reference to the instance VSMC.) 963

2) The client obtains the set of instances of the CIM_SettingsDefineCapabilities association that 964 associate the instance of the CIM_VirtualSystemMigrationCapabilities obtained in step 285H256H1) with 965 instances of the CIM_VirtualSystemMigrationSettingData class that describe various details of 966 the capabilities of the virtual system migration service, invoking the intrinsic References( ) 967 operation with parameter values set as follows: 968

– the value of the ObjectName parameter refers to the instance of the 969 CIM_VirtualSystemMigrationCapabilities obtained in step 286H257H1) class that represents the 970 virtual system migration service. ( 287H258HFigure 2: A reference to the instance VSMC). 971

– the value of the ResultClass parameter is set to “CIM_SettingsDefineCapabilities” 972

The result is a set of instances of the CIM_SettingsDefineCapabilities association that all 973 reference the input instance. ( 288H259HFigure 2: Association instances DEF, P2, P3, MINSSH, MAXSSH 974 and INCSSH). 975

3) For each association instance obtained in step 289H260H2), the client obtains the referenced instance of 976 the CIM_VirtualSystemMigrationSettingData class that is references by the association 977 instance, invoking the intrinsic GetInstance( ) operation with parameter values set as follows: 978

– the value of the InstanceName parameter is set to the value of the PartComponent 979 property taken from respective instance of the CIM_SettingsDefineCapabilities association 980 as obtained in step 290H261H2). 981

4) For each pair of instances of the CIM_SettingsDefineCapabilities association obtained in step 291H262H2) 982 and of the instance of the CIM_VirtualSystemMigrationSettingData class obtained in step 292H263H3) 983 (293H264HFigure 2: Pairs DEF/VSMD1, P2/VSMD2, P3/VSMD3, MINSSH/MN_SSH, MAXSSH/MX_SSH 984 and INCSSH/IN_SSH), the client inspects the properties values in the instance of the 985 CIM_SettingsDefineState association, as follows: 986

– If the value of the ValueRole property is 0 (Default) ( 294H265HFigure 2: Instance DEF), then the 987 reference instance of the CIM_VirtualSystemMigrationSettingData class represents the 988 default settings (295H266HFigure 2: Instance VSMDS1, indicating that live migration is used as a 989 default migration operation, along with a relative priority of 100, a bandwidth of 10 Megabit 990 per second and that the default transport protocol is "ssh".). 991

– If the value of the ValueRole property is 3 (Supported) and the value of the ValueRange 992 property is 0 (Point) (296H267HFigure 2: Instances P2 and P3), then the referenced instance of the 993 CIM_VirtualSystemMigrationSettingData class represents supported settings (297H268HFigure 2: 994 Instances VSMDS2 and VSMDS3). 995

– If the value of the ValueRole property is 3 (Supported) and the value of the ValueRange 996 property is 1 (Minimums) ( 298H269HFigure 2: Instance MINSSH), then the referenced instance of the 997 CIM_VirtualSystemMigrationSettingData class represents minimum supported settings 998 (299H270HFigure 2: Instance MN_SSH indicating a minimum bandwidth of 10 megabit per second for 999 the TransportType 2 (SSH). Note that in 300H271HFigure 2 the association instance MINSSH has set 1000 the value 1 (Correlated) for the PropertyPolicy property, indicating that all non-null values 1001 are correlated; thus the minimum setting only applies to the TransportType 2 (SSH), but 1002 not to other transport types). 1003



– If the value of the ValueRole property is 3 (Supported) and the value of the ValueRange 1004 property is 2 (Maximums) ( 301H272HFigure 2: Instance MAXSSH), then the referenced instance of 1005 the CIM_VirtualSystemMigrationSettingData class represents maximum supported settings 1006 (302H273HFigure 2: Instance MX_SSH, indicating a maximum bandwidth of 10000 megabit per 1007 second for the TransportType 2 (SSH). 1008

– If the value of the ValueRole property is 3 (Supported) and the value of the ValueRange 1009 property is 3 (Increments) ( 303H274HFigure 2: Instance INCSSH), then the referenced instance of 1010 the CIM_VirtualSystemMigrationSettingData class represents supported increment for 1011 settings (304H275HFigure 2: Instance IN_SSH, indicating that the admissible increment for bandwidth 1012 is 10 megabit per second.). 1013

Result: The client knows the capabilities of the virtual system migration service, in particular, which 1014 migration types and which transport types are supported, and what are the limitations the apply to the 1015 Bandwidth property and the Priority property if used as input instances for methods of the virtual system 1016 migration service. 1017

9.1.3 103BDetermine life migratability of a virtual system to a target virtualization platform 1018

Assumption: The client knows all of the following: 1019

• a reference to an instance of the CIM_ComputerSystem class that represents the virtual system 1020

• a reference to an instance of the CIM_VirtualSystemMigrationService class representing the 1021 responsible virtual system migration service; see 305H276H9.1.1 1022

• the IP address of the target virtualization platform 1023

The sequence of activities is as follows: 1024

1) The client invokes the extrinsic CheckVirtualSystemIsMigratableToHost( ) method on the 1025 instance of the CIM_VirtualSystemMigrationService, with parameter values set as follows: 1026

– the value of the ComputerSystem parameter refers to the instance of the CIM_Computer-1027 System class that represents the virtual system to be migrated 1028

– the value of the DestinationHost parameter is set to the IP address of the target 1029 virtualization platform 1030

– the value of the MigrationSettingData parameter contains an embedded instance of the 1031 CIM_VirtualSystemMigrationSettingData class, with property values set as follows: 1032

– the value of the MigrationType property is set to 2 (Live) 1033

– the value of the Priority property is not set, requesting a default priority 1034

– the value of the NewSystemSettingData parameter is set as required 1035

– the value of the NewResourceSettingData[ ] array parameter is set as required to modify 1036 virtual resource allocation that existed in the source virtual system or to add new resources 1037 into the migrated virtual system 1038

2) The implementation performs the requested check operation synchronously; the value of output 1039 parameters is set as follows: 1040

– The value of the return code is 0 (Completed with No Errors) 1041

– The value of the IsMigratable property is set to true. 1042

Result: The client knows that a migration of the virtual system to the target virtualization platform is 1043 potentially possible. If the value of the IsMigratable property had been false, that would indicate that a 1044 migration as requested would not be possible. 1045 NOTE The successful execution of the CheckVirtualSystemIsMigratableToHost( ) method does not ensure that a 1046

subsequent migration operation is successful as conditions such as resource availability may change 1047 substantially in short periods of time. 1048



9.1.4 104BDetermine lifecycle indication support 1049

Assumption: The client knows all of the following: 1050

• a reference to an instance of the CIM_RegisteredProfile class that represents an 1051 implementation of this profile 1052


1) The client resolves the CIM_ConcreteDependency association to find the instance of the 1054 CIM_FilterCollection class representing the conditional/optional filter collection that is related to 1055 the implementation of this profile, invoking the intrinsic Associators( ) CIM operation with 1056 parameter values set as follows: 1057

– the value of the ObjectName parameter refers to the instance of the CIM_RegisteredProfile 1058 class that represents the implementation of this profile 1059

– the value of the AssocClass parameter is set to “CIM_ConcreteDependency” 1060

– the value of the ResultClass parameter is set to “CIM_FilterCollection” 1061

The result of step 306H277H1) is a set of instances of the CIM_FilterCollection class. 1062

2) From the result set of step 307H278H1) the client eliminates all instances where the value of the 1063 CollectionName property is not “DMTF:Conditional/Optional” 1064

The result set of step 308H279H2) should be one instance representing the conditional/optional filter 1065 collection that is related to the implementation of this profile. 1066

3) From the result of step 309H280H2) the client resolves the CIM_MemberOfCollection association to find 1067 the instances of the CIM_IndicationFilter class that describe the set of implemented lifecycle 1068 indications in context of the implementation of this profile, invoking the intrinsic Associators( ) 1069 CIM operation with parameter values set as follows: 1070

– the value of the ObjectName parameter refers to the instance of the CIM_FilterCollection 1071 class obtained in step 310H281H2) 1072

– the value of the AssocClass parameter is set to “CIM_MemberOfCollection” 1073

– the value of the ResultClass parameter is set to “CIM_IndicationFilter” 1074

The result of step 311H282H3) is a set of instances of the CIM_IndicationFilter class. 1075

Result: The client knows the set of instances of the CIM_IndicationFilter class describing implemented 1076 lifecycle indications in context of the implementation of this profile. 1077

9.2 25BMigration operations 1078

This clause lists use-cases describing migration operations of virtual systems. 1079

9.2.1 105BLife migration 1080

Assumption: All of the following: 1081

• The client knows a reference to the instance of the CIM_ComputerSystem class that represents 1082 the source virtual system 1083

• The client knows a reference to the instance of the CIM_VirtualSystemMigrationService class 1084 that is responsible for the source virtual system; see 312H283H9.1.1 1085

• The client knows a reference to the instance of the CIM_System class that represents the target 1086 host system 1087

• The source virtual system is in a virtual system state that is acceptable by the selected type of 1088 migration operation 1089



• Optionally, the client may pre-check whether the source virtual system is migratable to the 1090 target virtualization platform; see 313H284H9.1.3. Note though that the migration may still fail. 1091


1) The client invokes the extrinsic MigrateVirtualSystemToSystem( ) method on the instance of the 1093 CIM_VirtualSystemMigrationService, with parameter values set as follows: 1094


– the value of the DestinationSystem parameter refers to the instance of the CIM_System 1097 class that represents the target host system 1098


– the value of the MigrationType property is set to 2 (Live) 1101


– the value of the NewSystemSettingData parameter is not set 1103

– the value of the NewResourceSettingData[ ] array parameter is not set 1104

2) The implementation initiates the requested operation as an asynchronous task; the value of 1105 output parameters is set as follows: 1106

– The value of the return code is 4096 (Method Parameters Checked – Job Started) 1107

– The value of the NewComputerSystem parameter is NULL 1108

– The value of the Job parameter refers to the instance of the CIM_ConcreteJob class that 1109 represents the ongoing migration operation. 1110

3) The client tracks the state of the ongoing migration operation by repeatedly obtaining the 1111 instance of the CIM_ConcreteJob class, invoking the intrinsic GetInstance( ) CIM operation with 1112 parameter values set as follows: 1113

– The value of the InstanceName parameter refers to the instance of the CIM_ConcreteJob 1114 class using the reference returned in step 314H285H2) 1115

The result is the instance of the CIM_ConcreteJob class. 1116

4) The client checks the value of the value of the JobState property in the instance of the 1117 CIM_ConcreteJob class. 1118

– If the value is one of 2 (New), 3 (Starting), 4 (Running) or 5 (Suspended), the client waits a 1119 certain amount of time and then continues repeating step 315H286H3). 1120

– If the value is 7 (Completed), the client continues with step a 1121

– If the value is one of 8 (Terminated), 9 (Killed) or 10 (Exception), the client continues with 1122 step x. 1123

– The interpretation of other values of the JobState property is undefined by this profile. 1124

5) The client resolves the CIM_AffectedJobElement association to find the instance of the 1125 CIM_ComputerSystem class that represents the migrated virtual system, invoking the intrinsic 1126 Associators( ) CIM operation with parameter values set as follows: 1127

– The value of the ObjectName parameter refers to the instance of the CIM_ConcreteJob 1128 class that represents the completed migration operation. 1129

– The value of the AssocClass parameter is set to “CIM_AffectedJobElement”. 1130

– The value of the ResultClass parameter is set to “CIM_ComputerSystem”. 1131



The result of this step is a set of instances of the CIM_ComputerSystem that represent the 1132 source virtual system and the target virtual system of the migration operation. From that set, the 1133 client drops the instance that represents the source virtual system, leaving the instance that 1134 represents the target virtual system. 1135

The use-case is completed in this case. 1136

6) The client invokes the extrinsic GetError( ) method on the instance of the CIM_ConcreteJob 1137 class. The method has no input parameters. 1138

On return, the value of the Error parameters is an embedded instance of the CIM_Error class 1139 that conveys details about the error. 1140

Result: The migration operation is completed. If the operation completed successfully, the client knows a 1141 reference to the instance of the CIM_ComputerSystem class representing the migrated virtual system. If 1142 the operation failed, the client knows an instance of the CIM_Error class conveying details about the 1143 failure. 1144

233H431H316H287HFigure 3 shows the situation before and after a successful migration operation . 1145

1146

Figure 3 Instance diagram: Virtual system migration 1147

Note The structure of the values of the Name key property in the instances of the CIM_ComputerSystem class is 1148 implementation dependent. This profile does not specify structure and content of any key properties. 1149



However, if implemented in accordance with 52H49HDMTF DSP1052: 317H288H1.0.0 ( 318H289HComputer System Profile) values of the 1150 IdentifyingDescriptions[ ] and the OtherIdentifyingInfo[ ] array properties reflect the fact that the migrated 1151 virtual system is in fact logically identical to the source virtual system by showing identical values for 1152 respective types of correlation properties as defined by 53H50HDMTF DSP1052: 319H290H1.0.0. For example, in 320H291HFigure 3 the 1153 logical identity is established by means of identical GUIDs by indicating with the value “CIM:GUID” for 1154 IdentifyingDescriptions[0] that GUIDs are used for identification, and providing identical values for the 1155 OtherIdentifyingInfo[0] for both the source and the target virtual system. 1156

9.2.2 106BStatic migration with request for additional resources 1157


• The client knows a reference to the instance of the CIM_ComputerSystem class that represents 1159 the source virtual system 1160

• The source virtual system has 2 GB of memory defined; this shall be increased to 5 GB as part 1161 of the migration operation 1162

• The client knows a reference to the instance of the CIM_VirtualSystemMigrationService class 1163 that is responsible for the source virtual system; see 321H292H9.1.1 1164

• The client knows a reference to the instance of the CIM_System class that represents the target 1165 host system 1166

• The source virtual system is migratable to the target virtualization platform; see 322H293H9.1.3 1167


1) The client invokes the extrinsic MigrateVirtualSystemToSystem( ) method on the instance of the 1169 CIM_VirtualSystemMigrationService, with parameter values set as follows: 1170


– the value of the DestinationSystem parameter refers to the instance of the CIM_System 1173 class that represents the target host system 1174


– the value of the MigrationType property is set to 4 (Restart) 1177


– the value of the NewSystemSettingData parameter is not set 1179

– the value of the NewResourceSettingData[ ] array parameter is set as follows: 1180

– exactly one array element containing a copy of the instance of the 1181 CIM_ResourceAllocationSettingData class that described the memory allocation with 1182 the definition of the source virtual system; see 54H51HDMTF DSP1057 (323H294HVirtual System 1183 Profile) how to obtain that instance 1184

– The value of the AllocationUnits property has a value of “bytes*10^9”, indicating that 1185 memory is allocated in units of Gigabyte (with 1 GB equal to 10^9 byte) 1186

– The value of the Reservation property shall be set to 5, indicating that the amount of 1187 memory in the virtual system definition shall be increased to 5 GB 1188

Note Other combinations of values of the AllocationUnits and the Reservation property may yield 1189 the same result. 1190

2) The implementation performs the requested operation as a synchronous task; the value of 1191 output parameters is set as follows: 1192

– The value of the return code is 0 (Completed with No Error) 1193



– The value of the NewComputerSystem parameter refers to the instance of the 1194 CIM_ComputerSystem class representing the migrated virtual system. 1195

– The value of the Job parameter is NULL. 1196

Result: The migration operation is completed, the client knows a reference to the instance of the 1197 CIM_ComputerSystem class representing the migrated virtual system. The definition for the virtual 1198 machines memory size is increased to the requested value. 1199

9.3 26BIndication delivery 1200


• The lifecycle indications are implemented for all events defined in this profile. 1202

• A client established itself as a listener destination with the conditional/optional filter collection; 1203 for details see respective use-cases in 55H52HDMTF DSP1054 (324H295HIndications Profile). 1204

• A dynamic migration is initiated for a virtual server that is hosted by a conformant system. 1205 NOTE The mechanism that was used to initiate the migration operation is not relevant in context of this use-case. 1206

For example, the migration operation could be initiated through use of a ssh based remote command 1207 interface. Alternatively methods of the CIM_VirtualSystemMigrationService class as described in this profile 1208 could be used, but this is not a required prerequisite for the delivery of indications. 1209

As the migration operation is initiated, proceeds and finally completes, lifecycle indications are delivered 1210 to respectively registered listener destinations, as follows: 1211

1) As the virtual system migration operation is initiated, the implementation delivers a 1212 CIM_InstMethodCall indication to all respectively registered listeners, with essential property 1213 values442H set as follows: 1214

– the value of the SourceInstance property contains an embedded instance of the 1215 CIM_VirtualSystemMigrationService class representing the virtual system migration service 1216

– the value of the SourceInstanceModelPath property refers to the instance of the 1217 CIM_VirtualSystemMigrationService class representing the virtual system migration service 1218

– the value of the MethodName property is “MigrateVirtualSystemToSystem” 1219

– the value of the MethodParameters property is encoded as specified in 325H296H7.7.2.7, providing 1220 information about the values of the following method parameters: 1221

– the value of the ComputerSystem parameter referencing the instance of the 1222 CIM_ComputerSystem class representing the source virtual system 1223

– the value of the DestinationSystem parameter referencing the instance of the 1224 CIM_ComputerSystem class representing the target host system 1225

– if present, the value of the MigrationSettingData parameter 1226

– if present, the value of the NewSystemSettingData parameter 1227

– if present, the value of the NewResourceSettingData parameter 1228

– if already known, the value of the Job parameter referencing the instance of the 1229 CIM_ConcreteJob class representing the virtual system migration task 1230

2) As an asynchronous task is created to perform the virtual system migration operation, that 1231 asynchronous task is represented by an instance of the CIM_ConcreteJob class. In addition the 1232 implementation creates an instance of the CIM_MethodResult class where the value of the 1233 PreCallIndication property contains a copy of the instance of the CIM_InstMethodCall indication 1234 delivered in step 444H326H297H1) and associates that to the instance of the CIM_ConcreteJob class 1235 representing the asynchronous virtual system migration task via an instance of the 1236 CIM_AssociatedJobMethodResult association 1237



3) Along with the creation of the asynchronous virtual system migration task in step 327H298H2) the 1238 implementation delivers an instance of the CIM_InstCreation indication to all respectively 1239 registered listeners, with property values set as follows: 1240

– an element in the value of the CorrelatedIndications[ ] array property contains the value of 1241 the IndicationIdentifier property in the indication delivered in step 328H299H1); this allows the client to 1242 correlate the association presented in step 329H300H3) with that presented in step 330H301H1) 1243

– the value of the SourceInstance property contains as in embedded instance a copy of the 1244 instance of the CIM_ConcreteJob class created in step 331H302H2) 1245

– the value of the SourceInstanceModelPath property refers to the instance of the 1246 CIM_ConcreteJob class created in step 332H303H2) 1247

4) As the virtual system migration operation proceeds, any change of the asynchronous virtual 1248 system migration task causing a property value change in the instance of the CIM_ConcreteJob 1249 class representing the task, such as a state change or the completion of a certain percentage of 1250 the operation causes the implementation to deliver an instance of the CIM_InstModification 1251 indication to all respectively registered listeners, with property values set as follows: 1252

– the value of the SourceInstance property contains as in embedded instance the instance of 1253 the CIM_ConcreteJob class representing the virtual system migration task 1254

– the value of the SourceInstanceModelPath property refers to the instance of the 1255 CIM_ConcreteJob class representing the virtual system migration task 1256

– the value of the PreviousInstance property contains as in embedded instance the instance 1257 of the CIM_ConcreteJob class representing the virtual system migration task within the 1258 most recently delivered modification indication 1259

5) As the migration operation completes, the implementation delivers a CIM_InstMethodCall 1260 indication to all respectively registered listeners, with essential property values set as in step 333H304H1) 1261 above, and in addition: 1262

– the value of the MethodParameters property is encoded as specified in 334H305H7.7.2.7, providing 1263 information about the values of the following output method parameters: 1264

– the value of the NewComputerSystem parameter referencing the instance of the 1265 CIM_ComputerSystem class representing the migrated virtual system 1266

– the value of the Job parameter referencing the instance of the CIM_ConcreteJob 1267 class representing the virtual system migration task 1268

6) As the asynchronous virtual system migration task is completed, the implementation delivers an 1269 instance of the CIM_InstModification to all respectively registered listeners, with property values 1270 set as follows: 1271

– the value of the SourceInstance property contains as in embedded instance the instance of 1272 the CIM_ConcreteJob class representing the virtual system migration task 1273

– the value of the SourceInstanceModelPath property refers to the instance of the 1274 CIM_ConcreteJob class representing the virtual system 1275

– the value of the PreviousInstance property contains as in embedded instance the instance 1276 of the CIM_ConcreteJob class that represents the virtual system migration operation that 1277 was delivered with the most recent lifecycle indication 1278

Result: The client receives lifecycle indications indicating initiation, progress, and success of the 1279 migration operation. 1280

335H306HFigure 4, 336H307HFigure 5 and 337H308HFigure 6 show an example situation where various types of lifecycle indications are 1281 delivered in the process of a virtual system migration operation. A client monitors virtual system migration 1282 operations by having subscribed to the conditional/optional indication filter collection. 1283

The following tagged elements commonly show up in 338H309HFigure 4, 339H310HFigure 5 and 340H311HFigure 6: 1284



• CLIENT: The instance of the CIM_ListenerDestination class representing the client 1285

• RP_MIG_MGMT: The instance of the CIM_RegisteredProfile class representing an 1286 implementation of this profile 1287

• VS_MIGRATION_CONDOPT: The instance of the instance of the CIM_FilterCollection class 1288 representing the conditional/optional filter collection related to RP_MIG_MGMT 1289

• MGMT_SYS: The instance of the CIM_System class representing the management system 1290

• MGMT_VSMS: The instance of the CIM_VirtualSystemManagementService class representing 1291 the virtual system management service hosted at the management system 1292

• HOST5: The instance of the CIM_System class representing the source host system 1293

• HOST6: The instance of the CIM_System class representing the target host system 1294

• MIGVS: The instance of the CIM_ComputerSystem class representing the virtual system that is 1295 migrated; the virtual system is initially hosted by the source host system and in the process of 1296 this use-case is migrated to the target host system 1297

• VS61: The instance of the CIM_ComputerSystem class representing the new virtual system. 1298 This virtual system is created as part of the migration process and after completion of the 1299 migration process the virtual system is logically identical to the source virtual system 1300

• JOB_MIGRATE_MIGVS: The instance of the CIM_ConcreteJob class representing the virtual 1301 system migration task 1302

• MIG_RESULT: The instance of the CIM_MethodResult representing the method result 1303

341H312HFigure 4 shows the initiation of the migration operation. In this use-case it is assumed that the migration 1304 operation was initiated by means outside of CIM, for example by an operator command. Consequently 1305 the client does not instantaneously know about the virtual system migration operation (as it would if it had 1306 initiated the operation) but only becomes aware of virtual system operations by analyzing incoming 1307 indications. 1308

In 342H313HFigure 4 two instances of the CIM_IndicationFilter class are shown representing indication filters within 1309 the conditional/optional filter collection: 1310

• VS_MIGRATION_METHOD_CALL_FILTER: The instance of the CIM_IndicationFilter class 1311 representing a filter for “method call” indications resulting from either 1312

– method invocations on a virtual system migration service that is represented by an 1313 instance of the CIM_VirtualSystemMigrationService class, or 1314

– processing of otherwise initiated activities within the implementation that are semantically 1315 equivalent to CIM method invocations 1316

This is described by the value of the Query property that selects those instances of the 1317 CIM_InstMethodCall indication that represent method invocations on instances of the 1318 CIM_VirtualSystemMigrationService class. 1319

As the filter is defined in context RP_MIG_MGMT, it will deliver only method call indications in 1320 context of MGMT_VSMS. 1321

• VS_MIGRATION_JOB_CREATE_FILTER: The instance of the CIM_IndicationFilter class 1322 representing a filter for “create instance” indications resulting from the creation of virtual system 1323 migration tasks that are represented by instances of the CIM_ConcreteJob class. The filter is 1324 described by the value of the Query property that selects those instances of the 1325 CIM_InstCreation indication that represent the creation of instances of the CIM_ConcreteJob 1326 class. 1327

As the filter is defined in context RP_MIG_MGMT, it will deliver only lifecycle indications 1328 representing the lifecycle of virtual system migration tasks. 1329



On the left side of 343H314HFigure 4 two indication instances are shown: 1330

• VS_MIGRATION_METHOD_BEGIN: The instance of the CIM_InstMethodCall indication 1331 reporting the invocation of a virtual system migration operation. This indication instance 1332 matches the VS_MIGRATION_METHOD_CALL_FILTER. 1333

• JOB_MIGRATE_MIGVS_CREATE: The instance of the CIM_InstCreation indication reporting 1334 the creation of a virtual system migration task represented by JOB_MIGRATE_MIGVS. This 1335 indication instance matches the VS_MIGRATION_TASK_CREATE_FILTER. 1336

Essential indication properties are described in more detail below in order to clarity their usage in a client 1337 context: 1338

• the value of the IndicationIdentifier property uniquely identifies an indication in the scope of one 1339 WBEM server; this is particularly important for correlation of various related indication instances 1340

• the value of the CorrelatedIndications[ ] array property enables correlating multiple indication 1341 instances to one event. In the case shown in 344H315HFigure 4 both the indication instances tagged 1342 VS_MIGRATION_METHOD_BEGIN and JOB_MIGRATE_MIGVS_CREATE are related to the 1343 initiation of a virtual system migration operation, and for that reason reference each other. A 1344 client may use that information to complete its knowledge about a reported event. For example 1345 the client may use the relationship between method invocation and job to relate later state 1346 changes of the job to the progress of the method execution 1347

• the value of the IndicationFilterName property references the instance of the 1348 CIM_IndicationFilter class that caused the indication to be triggered. This use-case assumes 1349 that the client had subscribed to the conditional/optional filter collection specified in this profile. 1350 The client may apply the use-case 345H316H9.1.4 to obtain the member instances of the 1351 CIM_IndicationFilter class and then compare the value of the IndicationFilterName property 1352 from a received instance of the CIM_Indication class against the value of the Name property of 1353 each of the collection members, thereby detecting the indication filter that caused the indication 1354 to be delivered. 1355

Note that in 346H317HFigure 4 it is assumed that HOST_MGMT represents a central management system where 1356 the WBEM server hosting the implementation of this profile resides. In this case the same implementation 1357 namespace is used for elements in context of HOST_MGMT and HOST5. On the other hand HOST6 1358 exists on a separate WBEM server. 1359



1360



Figure 4 Virtual system migration related lifecycle indications – initiation 1361



RegisteredOrganization = 2 (DMTF)RegisterdName = "Virtual System Migration"RegisteredVersion = "1.0"

RP_MIG_MGMT : RegisteredProfile

Name = "<OrgID>:00A3CA92E7513A23"Query = "Select * From CIM_InstModification Where SourceInstance ISA CIM_ConcreteJob AND PreviousInstance ISA CIM_ConcreteJob AND SourceInstance <> PreviousInstance"QueryLanguage = "DMTF:CQL"

VS_MIGRATION_JOB_CHANGE_FILTER : IndicationFilter

InstanceID = "<OrgID>:00A3CA928E810FA3"CollectionName = "DMTF:Conditional/Optional"

VS_MIGRATION_CONDOPT : FilterCollectionConcreteDependency

MemberOfCollection

INDSERV : IndicationService(See "Indications Profile")

ServiceAffectsElement


Protocol = 2 (CIM-XML)Destination = <Reference to listener>PersistenceType = 2 (Permanent)

CLIENT : ListenerDestination(See "Indications Profile")

FilterCollectionSubscription (See "Indications Profile")

IndicationIdentifier = "<OrgID>:00A3CA92B430A61F"CorrelatedIndications[] = NULLIndicationFilterName = "<OrgID>:00A3CA92E7513A23"SourceInstance = "<Copy of JOB_MIGRATE_MIGVS>"SourceInstanceModelPath = "<Reference to JOB_MIGRATE_MIGVS>"PreviousInstance = "<Copy of JOB_MIGRATE_MIGVS at time of last modification indication delivery>"

JOB_MIGRATE_MIGVS_CHANGE50 : InstModification

Interop Namespace – WBEM Server I

Filters are instantiated in theInterop Namespace and optionally in the

Implementation Namespace

Name = "<OrgID>:AC03C:XLIIU:0AR77:DZ7A2:V6B13"ElementName = "HOST6"

HOST6 : System

Name = "<OrgID>:UZAC3:BB8HU:98J2W:RX87V:PM00W"ElementName = "MIGVS"IdentifyingDescriptions[0] = "CIM:GUID"OtherIdentifyingInfo[0] = "8A53...UO09"

VS61 : ComputerSystem

HostedDependency

Implementation Namespace – WBEM Server I

Name = "<OrgID>:00A3CA92A0419E0C"ElementName = "HOST5"

HOST5 : System

MGMT_VSMS : VirtualSystemMigrationService

Name = "<OrgID>:00A3CA92F88CAB1B"ElementName = "MIGVS"IdentifyingDescriptions[0] = "CIM_GUID"OtherIdentifyingInfo[0] = "8A53...UO09"

MIGVS : ComputerSystem

HostedService

HostedDependency

AffectedJobElement

ElementConformsToProfile

HostedService (See "Indications Profile")

Name = "<OrgID>:00A3CA928FA126E3"ElementName = "HOST_MGMT"

MGMT_SYS : System

ServiceAffectsElementClusterMember(See "System Cluster Profile")

Implementation Namespace – WBEM Server II

Cross Namespace associations

Other indication filters

OwningJobElement

InstanceID = "<OrgID>:00A3CA92A8EFA992"PreCallIndication = <Copy of VS_MIGRATION_INIT>PostCallIndication = NULL

MIG_RESULT : MethodResult


Migration of virtual system represented by MIGVS

The virtual system represented by VS61 was implicitly created as part of the migration processBlue marked properties were carried over from MIGVS

(in this use-case)

matches filter

mod

ifica

tion

trigg

ers

even

t

JobState = 4 (Running)PercentComplete = 50TimeBeforeRemoval = "00000000000500.000000:000"

JOB_MIGRATE_MIGVS : ConcreteJob

1362



Figure 5 Virtual system migration related lifecycle indications – progress 1363

347H318HFigure 5 shows the situation where the migration of MIGVS from HOST5 to HOST6 is about 50 percent 1364 complete. For this event the implementation delivers JOB_MIGRATE_MIGVS_CHANGE50 as shown on 1365 the right side of 348H319HFigure 5. As this indication instance contains an embedded instance of and a reference to 1366 JOB_MIGRATE_MIGVS, the client may correlate the progress indication instance to the previously 1367 delivered lifecycle indication JOB_MIGRATE_MIGVS_CREATE that was shown in 349H320HFigure 4. 1368

350H321HFigure 5 shows a new virtual system: 1369

• VS61: The instance of the CIM_ComputerSystem class representing the new virtual system that 1370 has been created in the scope of the HOST6. Note that while the migration operation in fact 1371 yields a new virtual system, that this virtual system is logically identical to the virtual system 1372 tagged MIGVS in scope of HOST5. This is expressed by identical value pairs in the 1373 IdentifyingDescriptions[ ] and the OtherIdentifyingInfo[ ] array properties where both virtual 1374 system representations have the identical GUIDs. 1375

As in the virtual system migration operation is still in progress as shown in 351H322HFigure 5, 1376 JOB_MIGRATE_MIGVS is shown to affect both MIGVS and VS61. 1377

352H323HFigure 6 shows the situation where the migration operation is complete. 1378

The following indications are delivered: 1379

• VS_MIGRATION_METHOD_END: The instance of the CIM_InstMethodCall indication reporting 1380 the completion of a virtual system migration operation. This indication instance matches the 1381 VS_MIGRATION_METHOD_CALL_FILTER. 1382

• JOB_MIGRATE_MIGVS_READY: The instance of the CIM_InstModification indication reporting 1383 the state change of the virtual system migration task represented by JOB_MIGRATE_MIGVS to 1384 complete (as indicated by the value 7 (Complete) for the JobState property). This indication 1385 instance matches the VS_MIGRATION_TASK_CREATE_FILTER. 1386

As the virtual system migration is complete the source virtual system represented by MIGVS as shown in 1387 353H324HFigure 4 and 354H325HFigure 5 does no longer exist as shown in 355H326HFigure 6. It was stated above that the virtual 1388 system represented by VS61 is now logically identical to the original virtual system represented by 1389 MIGVS. 1390

Note that while the virtual system migration task represented by JOB_MIGRATE_VS may be destroyed 1391 already that JOB_MIGRATE_MIGVS with the associated MIG_RESULT still is required to exist beyond 1392 the lifetime of the migration task for a duration as specified by the value of the TimeBeforeRemoval 1393 property. This enables the client to obtain the state of the task even after its completion. 1394



RegisteredOrganization = 2 (DMTF)RegisterdName = "Virtual System Migration"RegisteredVersion = "1.0"

RP_MIG_MGMT : RegisteredProfile

Name = "<OrgID>:00A3CA92A019F5C9"Query = "Select * CIM_InstDeletion Where SourceInstance ISA CIM_ConcreteJob"QueryLanguage = "DMTF:CQL"

VS_MIGRATION_JOB_DELETE_FILTER : IndicationFilter

InstanceID = "<OrgID>:00A3CA928E810FA3"CollectionName = "DMTF:Conditional/Optional"

VS_MIGRATION_CONDOPT : FilterCollectionConcreteDependency

INDSERV : IndicationService(See "Indications Profile")


Protocol = 2 (CIM-XML)Destination = "<Reference to listener>"PersistenceType = 2 (Permanent)

CLIENT : ListenerDestination(See "Indications Profile")

FilterCollectionSubscription (See "Indications Profile")

IndicationIdentifier = "<OrgID>:00A3CA92EB7994A2"CorrelatedIndications[] = { "<OrgID:00A3CA92A6187A02"}IndicationFilterName = "<OrgID>:00A3CA92E7513A23"SourceInstance = "<Copy of JOB_MIGRATE_MIGVS>"SourceInstanceModelPath = "<Reference to JOB_MIGRATE_MIGVS>"PreviousInstance = "<Copy of JOB_MIGRATE_MIGVS at time of last modification indication delivery>"

JOB_MIGRATE_MIGVS_READY : InstModification

Interop Namespace – WBEM Server I

Filters are instantiated in theInterop Namespace and optionally in the

Implementation Namespace

Name = "<OrgID>:AC03C:XLIIU:0AR77:DZ7A2:V6B13"ElementName = "HOST6"

HOST6 : System

Implementation Namespace – WBEM Server I

Name = "<OrgID>:00A3CA92A0419E0C"ElementName = "HOST5"

HOST5 : System

MGMT_VSMS : VirtualSystemMigrationServiceHostedService

ElementConformsToProfile

HostedService (See "Indications Profile")

Name = "<OrgID>:00A3CA928FA126E3"ElementName = "HOST_MGMT"

MGMT_SYS : System

ClusterMember(See "System Cluster Profile")

Implementation Namespace – WBEM Server II

Cross Namespace associations

Other indication filters

InstanceID = "<OrgID>:00A3CA92A8EFA992"PreCallIndication = "<Copy of VS_MIGRATION_INIT>"PostCallIndication = "<Copy of VS_MIGRATION_END>"

MIG_RESULT : MethodResult


OwningJobElement

Name = "<OrgID>:UZAC3:BB8HU:98J2W:RX87V:PM00W"ElementName = "MIGVS"IdentifyingDescriptions[0] = "CIM:GUID"OtherIdentifyingInfo[0] = "8A53...UO09"

VS61 : ComputerSystem

HostedDependency

AffectedJobElement

ServiceAffectsElement

matches filter

IndicationIdentifier = "<OrgID>:00A3CA92A6187A02"CorrelatedIndications[] = { "<OrgID:00A3CA92EB7994A2"}IndicationFilterName = "<OrgID>:00A3CA92E7513A22"SourceInstance = "<Copy of MGMT_VSMS>"SourceInstanceModelPath = "<Reference to MGMT_VSMS>"MethodName = "MigrateVirtualSystemToSystem"MethodParameters = "__MethodParameters: ComputerSystem=\"<Reference to MIGVS>\", DestinationSystem=\"<Reference to HOST6>\", ... NewComputerSystem=\"<Reference to VS61>\" Job=\"<Reference to JOB_MIGRATE_MIGVS>\"ReturnValue = "0"ReturnValueType = 9 (uint32)Error[ ] = NULLPreCall = False

VS_MIGRATION_METHOD_END : InstMethodCall

JobState = 7 (Completed)PercentComplete = 100TimeBeforeRemoval = "00000000000500.000000:000"

JOB_MIGRATE_MIGVS : ConcreteJob

matches filter

Name = "<OrgID>:00A3CA92E7513A22"Query = Select * From CIM_InstMethodCall Where SourceInstance ISA CIM_VirtualSystemMigrationService"QueryLanguage = "DMTF:CQL"

VS_MIGRATION_METHOD_CALL_FILTER : IndicationFilter

Name = "<OrgID>:00A3CA92E7513A23"Query = "Select * From CIM_InstModification Where SourceInstance ISA CIM_ConcreteJob AND PreviousInstance ISA CIM_ConcreteJob AND SourceInstance <> PreviousInstance"QueryLanguage = "DMTF:CQL"

VS_MIGRATION_JOB_CHANGE_FILTER : IndicationFilter

1395



Figure 6 Virtual system migration related lifecycle indications – completion 1396

1397

10 9BCIM elements 1398

356H327HTable 21 lists CIM elements that are defined or specialized for this profile. Each CIM element shall be 1399 implemented as described in 357H328HTable 21. The CIM schema descriptions for any referenced element and its 1400 sub-elements apply. 1401

Clauses 358H329H7 ( 359H330HImplementation) and 360H331H8 (361H332HMethods) may impose additional requirements on these elements. 1402

Table 21 – CIM Elements: Virtual System Migration profile 1403

Element Requirement Notes

Classes

CIM_AffectedJobElement Conditional See 362H333H10.1

CIM_AssociatedJobMethodResult Conditional See 363H334H10.2

CIM_ConcreteDependency Conditional See 364H335H10.3

CIM_ConcreteJob Conditional See 365H336H10.4

CIM_ComputerSystem Conditional See 366H337H10.5

CIM_ElementCapabilities Mandatory See 367H338H10.6

CIM_Error Conditional See 368H339H10.7

CIM_FilterCollection (Conditional/Optional) Conditional See 369H340H10.8

CIM_HostedService Mandatory See 370H341H10.993H

CIM_IndicationFilter (Lifecycle) Optional See 371H342H10.10

CIM_MemberOfCollection Conditional See 372H343H10.11

CIM_MethodResult Conditional See 373H344H10.12

CIM_OwningCollectionElement Conditional See 374H345H10.13

CIM_OwningJobElement Conditional See 375H346H10.14

CIM_RegisteredProfile Mandatory See 376H347H10.15

CIM_ServiceAffectsElement Mandatory See 377H348H10.16

CIM_SettingsDefineCapabilities Mandatory See 378H349H10.17

CIM_VirtualSystemMigrationCapabilities Mandatory See 379H350H10.18

CIM_VirtualSystemMigrationService Mandatory See 380H351H10.19

CIM_VirtualSystemMigrationSettingData (Parameter)

Mandatory See 381H352H10.20

CIM_VirtualSystemMigrationSettingData (Capabilities)

Mandatory See 382H353H10.21

Indications

Select * CIM_InstCreation Where SourceInstance ISA CIM_ConcreteJob

Conditional Query Language: CQL Lifecycle indication representing the VS_MIGRATION_JOB_CREATE event

See 383H354H10.22




Select * CIM_InstDeletion Where SourceInstance ISA CIM_ConcreteJob

Conditional Query Language: CQL. Lifecycle indication representing the VS_MIGRATION_JOB_DELETE event

See 384H355H10.23

Select * CIM_InstMethodCall Where SourceInstance ISA CIM_VirtualSystemMigrationService

Conditional Query Language: CQL. Lifecycle indication representing the VS_MIGRATION_METHOD_CALL event. See 385H356H10.24

Select * CIM_InstModification Where SourceInstance ISA CIM_ConcreteJob AND PreviousInstance ISA CIM_ConcreteJob ANDSourceInstance <> PreviousInstance

Conditional Query Language: CQL. Lifecycle indication representing the VS_MIGRATION_JOB_CHANGE event. See 386H357H10.25

10.1 27BCIM_AffectedJobElement 1404

The implementation of the CIM_AffectedJobElement association is conditional. 1405

Condition: The CIM_AffectedJobElement association shall be implemented if one or more of the methods 1406 of the CIM_VirtualSystemMigrationService class is implemented with asynchronous execution behavior; 1407 see 387H358H8.1.1, 388H359H8.1.2, 389H360H8.1.3 and 390H361H8.1.4 . 1408

The CIM_AffectedJobElement association shall be instantiated between the instance of the 1409 CIM_ConcreteJob class representing a virtual system migration task and instances of the 1410 CIM_ComputerSystem class representing the source and the target virtual systems that are affected by 1411 the virtual system migration task. 1412

391H362HTable 22 lists the requirements for elements of this association. These requirements are in addition to 1413 those specified in the CIM Schema and – if implemented - in 56H53HSNIA SMIS:392H363H1.3.0, Part 2, Clause 26, ( 393H364HJob 1414 Control Subprofile) 1415

Table 22 – Association: CIM_AffectedJobElement 1416

Elements Requirement Notes

AffectedElement Mandatory Key: Value shall reference the instance of the CIM_ ComputerSystem class

Cardinality: 1..2

AffectingElement Mandatory Key: Value shall reference the instance of the CIM_ConcreteJob class

Cardinality: 1

ElementEffects[ ] Mandatory Value shall have exactly one element that has the value 1 (Other).

OtherElementEffectsDescription[ ] Mandatory Value shall have exactly one element that has the value “Virtual System Migration”.

10.2 28BCIM_AssociatedJobMethodResult 1417

The implementation of the CIM_AssociatedJobMethodResult association is conditional. 1418

Condition: The CIM_AssociatedJobMethodResult association shall be implemented if one or more of the 1419 methods of the CIM_VirtualSystemMigrationService class is implemented with asynchronous execution 1420 behavior; see 394H365H8.1.1, 395H366H8.1.2, 396H367H8.1.3 and 397H368H8.1.4 . 1421



The CIM_AssociatedJobMethodResult association shall be instantiated between the instance of the 1422 CIM_ConcreteJob class representing a virtual system migration task and the instance of the 1423 CIM_MethodResult class representing the related method invocation. 1424

398H369HTable 23 lists the requirements for elements of this association. These requirements are in addition to 1425 those specified in the CIM Schema, and – if implemented - in 57H54HSNIA SMIS:399H370H1.3.0, Part 2, Clause 26, ( 400H371HJob 1426 Control Subprofile). 1427

Table 23 – Association: CIM_AssociatedJobMethodResult 1428


Job Mandatory Key: Value shall reference the instance of the CIM_ Concrete job class

Cardinality: 1

JobParameters Mandatory Key: Value shall reference the instance of the CIM_MethodResult class

Cardinality: 1

10.3 29BCIM_ConcreteDependency 1429

The implementation of the CIM_ConcreteDependency association is conditional. 1430

Condition: The CIM_ConcreteDependency association shall be implemented if indications are 1431 implemented; see 401H372H7.7.2 . 1432

The CIM_ConcreteDependency association shall be instantiated for lifecycle indications between the 1433 instance of the CIM_RegisteredProfile class representing an implementation of this profile and the 1434 instance of the CIM_FilterCollection class representing the conditional/optional indication filter collection. 1435

402H373HTable 24 list the requirements for elements of this association. These requirements are in addition to 1436 those specified in the CIM Schema and in 58H55HDMTF DSP1054 (403H374HIndications Profile). 1437

Table 24 – Association: CIM_ConcreteDependency 1438


Antecedent Mandatory Key: Value shall reference the instance of the CIM_RegisteredProfile class

Cardinality: 1

Dependent Mandatory Key: Value shall reference the instance of the CIM_FilterCollection class

Cardinality: *

10.4 30BCIM_ConcreteJob 1439

The implementation of the CIM_ConcreteJob class is conditional. 1440

Condition: The CIM_ConcreteJob class shall be implemented if one or more of the methods of the 1441 CIM_VirtualSystemMigrationService class is implemented with asynchronous execution behavior; see 1442 404H375H8.1.1, 405H376H8.1.2, 406H377H8.1.3 and 407H378H8.1.4 . 1443

Instances of the CIM_ConcreteJob class shall represent asynchronous virtual system migration tasks. 1444



408H379HTable 25 lists the requirements for elements of this class. These requirements are in addition to those 1445 specified in the CIM Schema and - if implemented - in 59H56HSNIA SMIS:409H380H1.3.0, Part 2, Clause 26, ( 410H381HJob Control 1446 Subprofile). 1447

Table 25 – Class: CIM_ConcreteJob 1448

Element Requirement Description

JobState Mandatory See CIM Schema

TimeOfLastStateChange Mandatory See CIM Schema

10.5 31BCIM_ComputerSystem 1449

The implementation of the CIM_ComputerSystem class is conditional. 1450

Condition: The implementation of the CIM_ComputerSystem class shall be further constrained as 1451 specified in this clause beyond the requirements specified in 60H57HDMTF DSP1057:411H382H1.0.0 (412H383HVirtual System 1452 Profile), Subclause 10.2, and in 61H58HDMTF DSP1052:413H384H1.0.0 ( 414H385HComputer System Profile), Subclause 10.1 if the 1453 optional array properties OtherIdentifyingInfo[ ] and IdentifyingDescriptions[ ] array properties as specified 1454 by the 62H59HDMTF DSP1052:415H386H1.0.0, Subclause 10.1 for instances of the CIM_ComputerSystem class 1455 representing virtual systems are implemented. 1456

Instances of the CIM_ComputerSystem class shall be used for the representation of the source and the 1457 target virtual system of a virtual system migration process. 1458

416H387HTable 26 lists the requirements for elements of this class. 1459

Table 26 – Class: CIM_ComputerSystem 1460

Element Requirement Description

ElementName Optional See 417H388H7.5

IdentifyingDescriptions[ ] Conditional See 418H389H7.6.2

OtherIdentifyingInfo[ ] Conditional See 419H390H7.6.3

10.6 32BCIM_ElementCapabilities 1461

The CIM_ElementCapabilities association shall be instantiated between an instance of the 1462 CIM_VirtualSystemMigrationService class representing a virtual system migration service that is 1463 conformant with this profile and an instance of the CIM_VirtualSystemMigrationCapabilities class 1464 representing the capabilities of that virtual system migration service. 1465



420H391HTable 27 lists the requirements for elements of this association. 1466

Table 27 – Association: CIM_ElementCapabilities 1467


ManagedElement Mandatory Key: Value shall reference the instance of the CIM_VirtualSystemMigrationService class

Cardinality: *

Capabilities Mandatory Key: Value shall reference the instance of the CIM_VirtualSystemMigrationCapabilities class

Cardinality: *

10.7 33BCIM_Error 1468

The implementation of the CIM_Error class is conditional. 1469

Condition: The CIM_Error class shall be implemented if standard messages are implemented; see 421H392H8.1.1, 1470 422H393H8.1.2, 423H394H8.1.3, 424H395H8.1.4 and subclauses of 425H396H8.2 . 1471

Instances of the CIM_Error class shall be used to convey detailed error information if the execution of 1472 extrinsic methods or of intrinsic generic operations fails. 1473


Table 28 – Class: CIM_Error 1475


MessageID Mandatory Value shall identify the standard message conveyed through the instance of the CIM_Error class.

Message Mandatory Value shall contain the formatted standard message.

MessageArguments Mandatory Value shall contain the dynamic content of the message.

ErrorSource Conditional Value shall identify the primary entity that caused the error condition.

10.8 34BCIM_FilterCollection (Conditional/Optional) 1476

The implementation of the conditional/optional CIM_FilterCollection is conditional. 1477

Condition: The CIM_FilterCollection class shall be implemented for the representation of the 1478 conditional/optional filter collection if any indications are implemented; see 427H398H7.7.2 . 1479

An instance of the CIM_FilterCollection in the Interop namespace shall represent the conditional/optional 1480 indication filter collection related to this profile. A copy of that instance may exist in an implementation 1481 namespace. 1482

428H399HTable 29 lists the requirements for elements of this class if modeling the conditional/optional indication 1483 filter collection. These requirements are in addition to those specified in the CIM Schema and in 1484 63H60HDMTF DSP1054 (429H400HIndications Profile). 1485



Table 29 – Class: CIM_FilterCollection (Conditional/Optional) 1486


InstanceID Mandatory Key

CollectionName Mandatory Value shall be “DMTF:Conditional/Optional”

10.9 35BCIM_HostedService 1487

The CIM_HostedService association shall be instantiated between the instance of the CIM_System class 1488 representing a host system and the instance of the CIM_VirtualSystemMigrationService class 1489 representing a conformant virtual system migration service. 1490


Table 30 – Association: CIM_HostedService 1492


Antecedent Mandatory Key: Value shall reference the instance of the CIM_ System class

Cardinality: 1

Dependent Mandatory Key: Value shall reference the instance of the CIM_VirtualSystemMigrationService class

Cardinality: 1

10.10 36BCIM_IndicationFilter 1493

The implementation of the CIM_IndicationFilter class is optional. 1494

If implemented, instances of the CIM_IndicationFilter class shall represent filters for lifecycle indications 1495 as specified in 431H402H7.7.2; the presence of such instances indicates the presence of the implementation of 1496 respective optional indications. 1497

432H403HTable 31 lists the requirements for elements of this class if modeling lifecycle indication filters. These 1498 requirements are in addition to those specified in the CIM Schema and in 64H61HDMTF DSP1054 (433H404HIndications 1499 Profile). 1500

Table 31 – Class: CIM_IndicationFilter 1501


CreationClassName Mandatory Key

Name Mandatory Key; see 434H405H7.7.2.9

SystemCreationClassName Mandatory Key

SystemName Mandatory Key

Query Mandatory See 435H406H7.7.2.10

QueryLanguage Mandatory Value shall be set to “DMTF:CQL”

10.11 37BCIM_MemberOfCollection 1502

The implementation of the CIM_MemberOfCollection association is conditional. 1503



Condition: The CIM_MemberOfCollection association shall be implemented if indications are 1504 implemented; see 436H407H7.7.2 . 1505

The CIM_MemberOfCollection association shall be instantiated for lifecycle indications between the 1506 instance of the CIM_FilterCollection class representing the conditional/optional filter collection for lifecycle 1507 indications (see 437H408H10.7) and any instance of the CIM_IndicationFilter class representing an indication filter 1508 for lifecycle indications (see 438H409H10.10). 1509

439H410HTable 32 lists the requirements for elements of this association. These requirements are in addition to 1510 those specified in the CIM Schema and in 65H62HDMTF DSP1054 (440H411HIndications Profile). 1511

Table 32 – Association: CIM_MemberOfCollection 1512


Collection Mandatory Key: Value shall reference the instance of the CIM_FilterCollection class

Cardinality: 1

Member Mandatory Key: Value shall reference the instance of the CIM_IndicationFilter class

Cardinality: *

10.12 38BCIM_MethodResult 1513

The implementation of the CIM_MethodResult class is conditional. 1514

Condition: The CIM_MethodResult class shall be implemented if one or more of the methods of the 1515 CIM_VirtualSystemMigrationService class is implemented with asynchronous execution behavior; see 1516 441H412H8.1.1, 442H413H8.1.2, 443H414H8.1.3 and 444H415H8.1.4 . 1517

The CIM_MethodResult class shall represent invocations of methods of the 1518 CIM_VirtualSystemMigrationService that are executed asynchronously. 1519

563H445H416HTable 33 lists the requirements for elements of this class. These requirements are in addition to those 1520 specified in the CIM Schema, and - if implemented - in 66H63HSNIA SMIS:446H417H1.3.0, Part 2, Clause 26, ( 447H418HJob Control 1521 Subprofile). 1522

Table 33 – Class: CIM_MethodResult 1523



PreCallIndication Mandatory Value shall be an embedded instance of the CIM_InstMethodCall indication representing pre-execution values

PostCallIndication Conditional If method execution is complete, value shall be an embedded instance of the CIM_InstMethodCall indication representing post-execution values

10.13 39BCIM_OwningCollectionElement 1524

The implementation of the CIM_OwningCollectionElement association is conditional. 1525

Condition: The CIM_OwningCollectionElement association shall be implemented if any indications are 1526 implemented; see 448H419H7.7.2 . 1527



The CIM_OwningCollectionElement association shall be instantiated for lifecycle indications between the 1528 instance of the CIM_IndicationService class representing the indication service and the instance of the 1529 CIM_FilterCollection class representing the conditional/optional filter collection for lifecycle indications 1530 (see 449H420H10.7). 1531

450H421HTable 34 lists requirements for elements of this association. These requirements are in addition to those 1532 specified in the CIM Schema and in 67H64HDMTF DSP1054 (451H422HIndications Profile). 1533

Table 34 – Association: CIM_OwningCollectionElement 1534


OwningElement Mandatory Key: Value shall reference the instance of the CIM_IndicationService class

Cardinality: 1

OwnedElement Mandatory Key: Value shall reference the instance of the CIM_FilterCollection class

Cardinality: *

10.14 40BCIM_OwningJobElement 1535

The implementation of the CIM_OwningJobElement association is conditional. 1536

Condition: The CIM_OwningJobElement association shall be implemented if one or more of the methods 1537 of the CIM_VirtualSystemMigrationService class is implemented with asynchronous execution behavior; 1538 see 452H423H8.1.1, 453H424H8.1.2, 454H425H8.1.3 and 455H426H8.1.4 . 1539

The CIM_OwningJobElement association shall be instantiated between the instance of the 1540 CIM_VirtualSystemMigrationService class representing a conformant virtual system migration service and 1541 the instance of the CIM_ConcreteJob class representing a virtual system migration task that is owned by 1542 the service. 1543

456H427HTable 35 lists requirements for elements of this association. These requirements are in addition to those 1544 specified in the CIM Schema and - if implemented - in 68H65HSNIA SMIS:457H428H1.3.0, Part 2, Clause 26, ( 458H429HJob Control 1545 Subprofile). 1546

Table 35 – Association: CIM_OwningJobElement 1547


OwningElement Mandatory Key: Value shall reference the instance of the CIM_VirtualSystemMigrationService class

Cardinality: 1

OwnedElement Mandatory Key: Value shall reference the instance of the CIM_ConcreteJob

Cardinality: *

10.15 41BCIM_RegisteredProfile 1548

459H430HTable 36 lists the requirements for elements of this class. These requirements are in addition to those 1549 specified by 69H66HDMTF DSP1033:460H431H1.0.0 ( 461H432HProfile Registration Profile). 1550



Table 36 – Class: CIM_RegisteredProfile 1551


RegisteredOrganization Mandatory Value shall be set to 2 (DMTF)

RegisteredName Mandatory Value shall be set to "Virtual System Migration"

RegisteredVersion Mandatory Value shall be set to the version of this profile: "1.0.0".

10.16 42BCIM_ServiceAffectsElement 1552

The CIM_ServiceAffectsElement association shall be instantiated between instances of the 1553 CIM_ComputerSystem class representing a virtual system and an instance of the 1554 CIM_VirtualSystemMigrationService class representing a conformant virtual system migration service that 1555 is capable of managing migration operations for the virtual system. 1556


Table 37 – Association: CIM_ServiceAffectsElement 1558


AffectedElement Mandatory Key: Value shall reference the instance of the CIM_ComputerSystem class representing the virtual system

Cardinality: *

AffectingElement Mandatory Key: Value shall reference the instance of the CIM_VirtualSystemMigrationService class representing the conformant managing virtual system migration service

Cardinality: 1

ElementEffects[ ] Mandatory Value shall have exactly one element with the value set to 5 (Manages)

AssignedSequence Mandatory Value shall reflect the requested priority of a requested (pending) or ongoing migration operation

10.17 43BCIM_SettingsDefineCapabilities 1559

The CIM_SettingsDefineCapabilities association shall be instantiated between an instance of the 1560 CIM_VirtualSystemMigrationCapabilities class representing capabilities of a conformant virtual system 1561 migration service and an instance of the CIM_VirtualSystemMigrationSettingData class representing 1562 default values for operations of the service. 1563




Table 38 – Association: CIM_SettingsDefineCapabilities 1565


GroupComponent Mandatory Key: Value shall reference the instance of the CIM_VirtualSystemMigrationCapabilities class representing capabilities of a conformant virtual system migration service.

Cardinality: 1

PartComponent Mandatory Key: Value shall reference the instance of the CIM_VirtualSystemMigrationSettingData class representing default migration settings

Cardinality: 1..*

PropertyPolicy Mandatory See 464H435H7.4.1 for default migration settings and 465H436H7.4.2 for admissible migration settings.

ValueRole Mandatory See 466H437H7.4.1 for default migration settings and 467H438H7.4.2 for admissible migration settings.

ValueRange Mandatory See 468H439H7.4.1 for default migration settings and 469H440H7.4.2 for admissible migration settings.

10.18 44BCIM_VirtualSystemMigrationCapabilities 1566

The CIM_VirtualSystemMigrationCapabilities class represents capabilities of one or more virtual system 1567 migration services. 1568


Table 39 – Class: CIM_VirtualSystemMigrationCapabilities 1570



AsynchronousMethodsSupported[ ] Mandatory See 471H442H7.2.2

SynchronousMethodsSupported[ ] Mandatory See 472H443H7.2.2

DestinationHostsFormatsSupported[ ]

Conditional Required if the optional CheckVirtualSystemIsMigratableToHost( ) method (see 473H444H8.1.2) and/or the optional MigrateVirtualSystemToHost( ) method (see 474H445H8.1.4) are implemented.

10.19 45BCIM_VirtualSystemMigrationService 1571

The CIM_VirtualSystemMigrationService class models a virtual system migration service. 1572

Instances of the CIM_VirtualSystemMigrationService shall represent virtual system migration services 1573 that are conformant with this profile. 1574


Table 40 – Class: CIM_VirtualSystemMigrationService 1576




CreationClassName Mandatory Key

Name Mandatory Key

SystemCreationClassName Mandatory Key

SystemName Mandatory Key

MigrateVirtualSystemToHost( ) Conditional See 476H447H8.1.1

MigrateVirtualSystemToSystem( ) Optional See 477H448H8.1.2

CheckVirtualSystemIsMigratableToHost( )

Conditional See 478H449H8.1.3

CheckVirtualSystemIsMigratableToSystem( )

Optional See 268H588H479H450H8.1.4

NOTE The MigrateVirtualSystemToHost( ) method and the CheckVirtualSystemIsMigratableToHost( ) method are intended as a transitional solution only until modeling of cluster support is available.

10.20 46BCIM_VirtualSystemMigrationSettingData (Parameter) 1577

Instances of the CIM_VirtualSystemMigrationSettingData class shall represent the parameterization of 1578 operations of the CIM_VirtualSystemMigrationService class. 1579

480H451HTable 41 lists the requirements for elements of this class if used as a parameter of methods of the 1580 CIM_VirtualSystemMigrationService class. 1581

Table 41 – Class: CIM_VirtualSystemMigrationSettingData (Parameter) 1582


InstanceID Mandatory Key: Shall be NULL

MigrationType Optional See 481H452H7.3.1

Priority Optional See 482H453H7.3.2

Bandwidth Optional See 483H454H7.3.3

BandwidthUnit Optional See 484H455H7.3.4

TransportType Optional See 485H456H7.3.5

OtherTransportType Conditional See 486H457H7.3.6

10.21 47BCIM_VirtualSystemMigrationSettingData (Capabilities) 1583

Instances of the CIM_VirtualSystemMigrationSettingData class shall represent default values that apply 1584 to method invocations of the CIM_VirtualSystemMigrationService class. Instances of the 1585 CIM_VirtualSystemMigrationSettingData class may represent admissible values for method invocations of 1586 the CIM_VirtualSystemMigrationService class if referenced by instances of the 1587 CIM_SettingsDefineCapabilities association where the value of the ValueRole property is either 0 1588 (Default) or 3 (Supported). 1589 272H592H 1590

487H458HTable 42 contains the requirements for instances of this class if used as default value expressing 1591 capabilities of the CIM_VirtualSystemMigrationService class. 1592

Table 42 – Class: CIM_VirtualSystemMigrationSettingData (Capabilities) 1593





MigrationType Mandatory See 488H459H7.4.3

Priority Mandatory See 489H460H7.4.4

Bandwidth Optional See 490H461H7.4.5

BandwidthUnit Conditional See 491H462H7.4.6

TransportType Optional See 492H463H7.4.7

OtherTransportType Conditional See 493H464H7.4.8

10.22 48BCIM_InstCreation 1594

The implementation of the CIM_InstCreation indication is conditional. 1595

Condition: The CIM_InstCreation indication shall be implemented if indications (see 494H465H7.7.2) are 1596 implemented reporting the VS_MIGRATION_JOB_CREATE event; this implies that the 1597 CIM_IndicationFilter class for filtering this type of indication is implemented (see 495H466H10.10 for the 1598 CIM_IndicationFilter class and 496H467H7.7.2.10 for the value of the Query property). 1599

497H468HTable 43 contains the requirements for this case. These requirements are in addition to those specified in 1600 the CIM Schema and in the 607H498H469HIndications Profile. 1601

Table 43 – Indication: CIM_InstCreation 1602


IndicationIdentifier Mandatory Value shall contain a unique identification of the indication instance; for the format see CIM Schema definition.

CorrelatedIndications[ ] Conditional See 499H470H7.7.2.2

IndicationTime Mandatory Value shall contain the time of the reported VS_MIGRATION_JOB_CREATE event

PerceivedSeverity Mandatory Value shall be 2 (Information)

IndicationFilterName Mandatory See 500H471H7.7.2.3

SourceInstance Mandatory See 501H472H7.7.2.4

SourceInstanceModelPath Mandatory Value shall refer to the instance of the CIM_ConcreteJob class copied into the SourceInstance parameter

SourceInstanceHost Optional Value should contain the host name or IP address of the source host system

10.23 49BCIM_InstDeletion 1603

The implementation of the CIM_InstDeletion indication is conditional. 1604

Condition: The CIM_InstDeletion indication shall be implemented if any indications (see 502H473H7.7.2) are 1605 implemented reporting the VS_MIGRATION_JOB_DELETE event; this implies that the 1606 CIM_IndicationFilter class for filtering this type of indication is implemented (see 503H474H10.10 for the 1607 CIM_IndicationFilter class and 504H475H7.7.2.10 for the value of the Query property). 1608

505H476HTable 44 contains the requirements for this case. These requirements are in addition to those specified in 1609 the CIM Schema and in 70H67HDMTF DSP1054 (506H477HIndications Profile). 1610



Table 44 – Indication: CIM_InstDeletion 1611



CorrelatedIndications[ ] Conditional See 507H478H7.7.2.2

IndicationTime Mandatory Value shall contain the time of the reported VS_MIGRATION_JOB_DELETE event






10.24 50BCIM_InstMethodCall 1612

The implementation of the CIM_InstMethodCall indication is conditional. 1613

Condition: The CIM_InstMethodCall indication shall be implemented if any indications (see 619H510H481H7.7.2) are 1614 implemented reporting the VS_MIGRATION_METHOD_CALL event; this implies that the 1615 CIM_IndicationFilter class for filtering this type of indication is implemented (see 620H511H482H10.10 for the 1616 CIM_IndicationFilter class and 621H512H483H7.7.2.10 for the value of the Query property). 1617


Table 45 – Indication: CIM_InstMethodCall 1620



CorrelatedIndications[ ] Mandatory Unspecified

IndicationTime Mandatory Value shall contain the time of the reported VS_MIGRATION_JOB_CHANGE event




SourceInstanceModelPath Mandatory Value shall refer to the instance of the CIM_VirtualSystemMigrationService class copied into the SourceInstance parameter


MethodName Mandatory See 517H488H7.7.2.6

MethodParameters Mandatory See 518H489H7.7.2.7



ReturnValue Conditional Condition: Value of the PreCall property is FALSE - For value definition see CIM Schema

ReturnValueType Conditional Condition: Value of the PreCall property is FALSE - For value definition see CIM Schema

Error[ ] Optional See CIM Schema

PreCall Mandatory See CIM Schema

10.25 51BCIM_InstModification 1621

The implementation of the CIM_InstModification indication is conditional. 1622

Condition: The CIM_InstModification indication shall be implemented if any indications (see 519H490H7.7.2) are 1623 implemented reporting the VS_MIGRATION_JOB_CHANGE event; this implies that the 1624 CIM_IndicationFilter class for filtering this type of indication is implemented (see 520H491H10.10 for the 1625 CIM_IndicationFilter class and 521H492H7.7.2.10 for the value of the Query property). 1626


Table 46 – Indication: CIM_InstModification 1629



CorrelatedIndications[ ] Mandatory Unspecified

IndicationTime Mandatory Value shall contain the time of the reported VS_MIGRATION_JOB_CHANGE event






PreviousInstance Optional See 526H497H7.7.2.8

1630



ANNEX A 1631 (Informative) 1632

1633 Change Log 1634

1635 Version Date Description

1.0.0a 11/13/2008 Initial creation.

1.0.0b 09/03/2009 Work in progress release ending 12/31/2009

1.0.0c 02/04/2010 Work in progress release ending 07/31/2010 (wgv 0.7.2)

1636

DMTF DSP1081 Virtual System Migration Profile

Documents

Transcript of DMTF DSP1081 Virtual System Migration Profile