Appendix B. Data Types

This section contains the definition of attribute types defined within this model. The enumerated types may be either closed or open. For properties whose type defines a closed enumeration, one of the defined values MUST be chosen; any other value is not valid. For properties whose type defines an open enumeration, one of the defined values MAY be chosen, but nevertheless any other value compatible with the string type and with the recommended syntax is allowed. Before defining a new open enumeration value, it is recommended to apply the “GLUE2 Enumerations procedures and best practices” (http://redmine.ogf.org/projects/glue-wg/wiki/Enumerations_procedures_and_best_practices_v10). The enumeration values MUST be lower-case.

B.1. AccessLatency_t

Closed enumeration:

Value	Description
nearline	A file MAY have its only copies in a "nearly online" component of the storage system, typically a fully automated tape robot, but also a remote storage system could fit this qualification. Such a facility will need an unspecified amount of time to make a copy of the file available on the disk component of the container under consideration. When a file is not in use, its disk copies MAY be removed. Hence the system cannot guarantee that a file will be immediately available on disk
offline	A file MAY have its only copies in an offline component of the storage system, for example a tape library that is not connected to an automated tape robot. Hence an operator intervention MAY be needed to make a copy of a file available that has a lower latency
online	Files are always stored on a medium with an access time less than a minute (e.g., a disk)

B.2. AccType_t

Open enumeration:

Value	Description
GPU	GPU architecture
MIC	Intel MIC architecture
FPGA	Generic FPGA accelerator

B.3. AppEnvState_t

Open enumeration:

Value	Description
Installable	The application environment is not installed, but MAY be dynamically installed
installationfailed	The application environment was being installed, but the installation process failed
installedbroken	The application environment is installed, but the verification failed
installednotverified	The application environment is installed, but not yet verified
installedverified	The application environment is installed and successfully verified
installingautomatically	The application environment is not installed, but is being installed automatically
installingmanually	The application environment is not installed, but is being installed manually
notinstallable	The application environment is not installed and not installable
pendingremoval	The application environment is installed, but is due to be removedwill be removed as soon as possible
Removing	The application environment is installed, but it is being removed

B.4. ApplicationHandle_t

Open enumeration:

Value	Description
executable	Access based on running directly the main executable of the application (this MAY require set-up of the environment)
module	Access based on loading modules via Environment Modules (http://modules.sourceforge.net/)
path	Access based on using an explicit path where the software is installed on the file system
softenv	Access based on loading SoftEnv keys (http://www.mcs.anl.gov/systems/software/softenv/softenv-intro.html)

B.5. Benchmark_t

Open enumeration:

Value	Description
bogomips	BogoMips
cfp2006	SPEC CFP 2006 floating point benchmark
cint2006	SPEC CINT 2006 integer benchmark
linpack	LINPACK benchmark
specfp2000	SPECfp2000 floating point benchmark
specint2000	SPECint2000 integer benchmark

B.6. Capability_t

List of values initially drafted from [OMII-DJRA2.1, OGF-GFD80]. Open enumeration:

Value	Description
data.access.flatfiles	capacity of providing access to a flat file
data.access.relational	capacity of providing access to a relational data source
data.access.xml	capacity of providing access to an XML data source
data.management.diskimage	capacity of managing the creation of mountable disk images objects
data.management.file	capacity of managing the creation of files
data.management.genericobject	capacity of managing the creation of generic storage objects
data.management.replica	capacity of managing the creation of file replicas upon request
data.management.storage	capacity of managing a storage resource, from simple systems like disk-servers to complex hierarchical systems
data.management.transfer	capacity of managing a transfer of files from the start to the completion
data.naming.resolver	capacity of resolving one name to another (for example, search the associated abstract name to a certain human-oriented name)
data.naming.scheme	capacity of attaching names to data resources. (To evaluate if it should moved to the main category infrastructure instead of data). In OGSA, a three-level naming scheme is defined: (1) human-oriented name, (2) abstract name and (3) address
data.transfer	capacity of moving a file from one network location to another. It refers to the actual transfer (e.g., as performed by protocols like FTP, GridFTP, or HTTP)
executionmanagement.candidatesetgenerator	capacity of determining the set of resources in which a unit of work MAY execute
executionmanagement.dynamicvmdeploy	capacity of dynamically deploying a virtual machine image in a worker node
executionmanagement.executionandplanning	capacity of building schedules for jobs, that is, the capability of defining mappings between services and resources, possibly with time constraints
executionmanagement.jobdescription	capacity of letting users be able to describe a job submission request based on a machine-processable language
executionmanagement.jobexecution	capacity of executing a job or set of jobs.
executionmanagement.jobmanager	capacity of managing the execution of a job or set of jobs from start to finish
executionmanagement.reservation	capacity of managing reservation of resources for future usage
information.discovery	capacity of locating unknown resources or services, possibly satisfying a set of requirements
information.logging	capacity of recording data, often chronologically
information.model	capacity of modelling resources based on a community accepted definition
information.monitoring	capacity of periodically observing measurements, transform them and make available to users or other applications
information.provenance	capacity of providing long-term storage of information related to Grid activity and to let this information be accessed by users or other applications.
security.accounting	capacity of systematically recording, reporting, and analyzing the usage of resources
security.attributeauthority	capacity of associating a user with a set of attributes in a trusted manner to a relying party, by way of digitally signed assertions
security.authentication	capacity of providing authentication mechanisms for Grid users machine and services
security.authorization	capacity of handling authorization aspects, making authorization decisions about the subject and the requested mode of access based upon combining information from a number of distinct sources
security.credentialstorage	capacity of providing an online credential repository that allows users to securely obtain credentials when and where needed
security.delegation	capacity for a user to give a service the authority to undertake specific activities or decisions on its behalf
security.identymapping	capacity of mapping Grid-level credentials to local level credentials (e.g., mapping a user X.509 certificate into a UNIX account).

B.7. CloudComputingInstanceState_t

For the values of this type, we RECOMMEND the following syntax:

• namespace:state

• namespace:state:substate

Open enumeration:

Value	Description
bes:error	(a terminal state): the activity has failed due to some system error/failure event, such as failure of a computational resource that the activity was running on
bes:finished	(a terminal state): the activity has terminated successfully. Successful termination implies that the activity exited of its own accord rather than due to some failure in the BES or of the computational resources on which the activity was running. Note that a successfully terminating activity MAY nevertheless return an error code as its return value
bes:pending	the service has created a record for an activity but not yet instantiated it on a suitable computational resource or enabled it to start execution on such a resource
bes:running	the activity is executing on some computational resource
bes:terminated	(a terminal state): the client – which might be some system administrator (and hence not necessarily the client who originated the request to create the activity) – has issued a TerminateActivity request
bes:suspended	the activity is currently in suspended state. Some resources for the activity may be reserved into the the system, but no computing resources are utilized

For more information on the BES state model, see [BES].

B.8. CloudComputingInstanceType_t

Closed enumeration:

Value	Description
collectionelement	A VM submitted as part of a collection of individual VMs which do not communicate among them
parallelelement	A VM submitted as part of a collection of individual VM which communicate among them (ex. part of a computing cluster)
single	An individual stand-alone VM

B.9. CloudComputingManagerType_t

Open enumeration:

Value	Description
openstack	OpenStack
opennebula	OpenNebula
wnodes	WNoDeS
synnefo	Synnefo
cloudstack	Apache CloudStack
Vcloud	VMWare vCloud

B.10. CloudResourceName_t

Closed enumeration:

Value	Description
flavour	Resource flavour, comprensive of disk, CPU, ram, memory and network
network	Network usage (amount of kilobytes inbound/outbound from the VM network interfaces)
networkin	Network inbound usage (amount of kilobytes inbound from the VM network interfaces)
networkout	Network outbound usage (amount of kilobytes outbound from the VM network interfaces)
cpu	Number of vCPU associated to the VM. A vCPU seen by the OS is considered in use, even if it is in idle mode
gpu	Number of vGPU associated to the VM. A vGPU seen by the OS is considered in use, even if it is in idle mode
memory	RAM associated to the VM in MBs. Memory associated to the VM, and seen by the OS, is accounted even if free in the OS space.
storage	Storage associated to the VM in GBs. It includes all the type of storage associated to the VM, both block storage or ephemeral storage or OS disk image storage
ephemeralstorage	Ephemeral storage associated to the VM in GBs
blockstorage	Block storage associated to the VM in GBs. The entire amount of the block storage device disk is accounted, even if storage is not used by the OS
osdiskstorage	Storage associated to the VM Image OS disk in GB. The entire amount of the block storage device disk is accounted, even if storage is not used by the OS.
softwarelicense	License for the usage of software on the VM image disk. This shall include all the licensing prices for all the software installed in the VM besides the OS
oslicense	License for the usage of the OS on the VM image disk.

B.11. ComputingActivityState_t

For the values of this type, we RECOMMEND the following syntax:

• namespace:state

• namespace:state:substate

Open enumeration:

Value	Description
bes:failed	(a terminal state): the activity has failed due to some system error/failure event, such as failure of a computational resource that the activity was running on
bes:finished	(a terminal state): the activity has terminated successfully. Successful termination implies that the activity exited of its own accord rather than due to some failure in the BES or of the computational resources on which the activity was running. Note that a successfully terminating activity MAY nevertheless return an error code as its return value
bes:pending	the service has created a record for an activity but not yet instantiated it on a suitable computational resource or enabled it to start execution on such a resource
bes:running	the activity is executing on some computational resource
bes:terminated	(a terminal state): the client – which might be some system administrator (and hence not necessarily the client who originated the request to create the activity) – has issued a TerminateActivity request

For more information on the BES state model, see [BES].

This attribute type is an open enumeration. Examples of additional values are:

• a middleware provider is using its own state model defined before the BES specification:

  • NorduGrid defines the state accepting which MAY be represented as (see [ng-schema], page 28):

    • nordugrid:accepting

  • gLite WMS defines the state scheduled which MAY be represented as:

    • glite-wms:scheduled

  • gLite CREAM defines the state registered which MAY be represented as:

    • glite-cream:registered

    • (see https://edms.cern.ch/document/595770)

• a middleware provider defined an extension of BES state model which is not part of an official OGF specification

  • NorduGrid defined an extension the bes:pending by adding two substates:

    • nordugrid-bes:pending:accepting

    • nordugrid-bes:pending:accepted

B.12. ComputingActivityType_t

Closed enumeration:

Value	Description
collectionelement	A job submitted as part of a collection of individual jobs which do not communicate among them
parallelelement	A job submitted as part of a collection of individual jobs which communicate among them
single	An individual stand-alone job
workflownode	A job submitted as part of a workflow

B.13. ComputingManagerType_t

Open enumeration:

Value	Description
bqs	CC-IN2P3 Batch Queue System
condor	Condor
fork	Based on fork primitive
loadleveler	IBM LoadLeveler
lsf	Platform Load Sharing Facility
openpbs	Open PBS
sungridengine	Sun Grid Engine
torque	Torque
torquemaui	Torque with MAUI

B.14. ContactType_t

Open enumeration:

Value	Description
general	Contact for persons to ask about general issues
security	Contact for persons responsible for security
sysadmin	Contact for the system administrators
usersupport	Contact for user support

B.15. ContextualizationName_t

Open enumeration:

Value	Description
cloud-init	Ubuntu CloudInit
bash	Generic bash script

B.16. CPUMultiplicity_t

Closed enumeration:

Value	Description
multicpu-multicore	The execution environment is run by multiple physical CPUs with a multiple cores each
multicpu-singlecore	The execution environment is run by multiple physical CPUs with a single core each
singlecpu-multicore	The execution environment is run by a single physical CPU with multiple cores
singlecpu-singlecore	The execution environment is run by a single physical CPU with a single core

B.17. CPUVirtualizationT_t

Open enumeration:

Value	Description
emulation	Full virtualization with emulation
paravirtualization	Para-virtualization
hardware	Hardware assisted virtualization

B.18. DataStoreType_t

Open enumeration:

Value	Description
disk	The storage capacity is provided by magnetic disks
optical	The storage capacity is provided by optical disks
tape	The storage capacity is provided by magnetic tapes

B.19. DateTime_t

The DateTime_t is based on the extended ISO 8061 format:

• [-]CCYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm]

This data type maps the dateTime XSD simple type. We restrict this syntax to UTC time zone as follows:

• yyyy '-' mm '-' dd 'T' hh ':' mm ':' ss 'Z'

B.20. DiskVirtualizationT_t

Open enumeration:

Value	Description
qcow2	QCOW2
raw	RAW Image
vmdk	VMDK

B.21. DN_t

Distinguished Name as defined by RFC 4514 (http://www.rfc-editor.org/rfc/rfc4514.txt).

X.509 uses a X.500 namespace, represented as several Relative Domain-Names (RDNs) concatenated by forward-slashes. The final RDN is usually a single common name (CN), although multiple CNs are allowed.

B.22. EndpointAuthentication_t

Open enumeration:

Value	Description
none	No authentication is configured on the endpoint
x509	X590 authentication is configured
oidc	OpenID Connect authentication is configured
saml2	SAML 2.0 authentication is configured

B.23. EndpointHealthState_t

Closed enumeration:

Value	Description
critical	It was possible to check the state of the endpoint and either it was not running or it was above some "critical" threshold
ok	It was possible to check the state of the endpoint and it appeared to be functioning properly
other	It was possible to check the state of the endpoint, but this is not covered by the defined states
unknown	It was not possible to check the state of the endpoint
warning	It was possible to check the state of the endpoint, but it appeared to be above some "warning" threshold or did not appear to be working properly
downtime	It was possible to check the state of the endpoint, but it appeared to be on maintenance and may not work properly

B.24. EndpointTechnology_t

Open enumeration:

Value	Description
corba	The endpoint is implemented using CORBA technologies
jndi	The endpoint is implemented using JNDI
webservice	The endpoint is implemented as a Web Service

B.25. ExpirationMode_t

Closed enumeration:

Value	Description
neverexpire	Support for files with infinite lifetime: they MAY only be removed by authorized clients, not by the storage system itself
releasewhenexpired	Support for files that have finite lifetimes and on expiration will be removed by the storage system
warnwhenexpired	Support for files that have finite lifetimes, but on expiration cannot be removed by the storage system itself. The data content of an expired file MAY be deleted if it MAY be recovered from an archive. New store operations MAY fail for certain clients until (some of the) expired files have either been removed by authorized clients, or have had their lifetimes increased

B.26. ExtendedBoolean_t

Closed enumeration:

Value	Description
false	boolean false
true	boolean true
undefined	the value cannot be measured

B.27. HostAccessInfo_t

Closed enumeration:

Value	Description
none	No default credentials are present in the machine, access credentials shall be injected by the middleware
passwd	Pre-set username/password
rsa	Pre-set RSA key set

B.28. InterfaceName_t

Open enumeration:

Value	Description
ogf.bes	The Open Grid Forum Basic Execution Service
ogf.srm	The Open Grid Forum Storage Resource Manager

B.29. JobDescription_t

Open enumeration:

Value	Description
condor	Condor
egee:jdl	EGEE Job Description Language
globus:rsl	Globus RSL
nordugrid:xrsl	Nordugrid XSRL [XSRL]
ogf:jsdl:1.0	Job Description Submission Language 1.0

B.30. License_t

Open enumeration:

Value	Description
commercial	Commercial license
opensource	Open Source license approved by the OSI (Open Source Initiative)
unknown	Unknown license type

B.31. LocalID_t

The base type is the string with the following restrictions:

• first char in a-zA-Z

• following characters in [\w\-\.\:]

  • \w = [a-zA-Z_0-9]

B.32. NetworkInfo_t

Open enumeration:

Value	Description
100megabitethernet	Network based on 100 MBit/s Ethernet technology
gigabitethernet	Network based on 1 GBit/s Ethernet technology
infiniband	Network based on Infiniband technology
myrinet	Network based Myrinet technology

B.33. NetworkConfigurationProtocol_t

Open enumeration:

Value	Description
all	All protocols
tcp	TCP protocol
udp	UDP protocol
cmp	CMP protocol
ipsec	IPSec protocol

B.34. NetworkConfigurationDirection_t

Open enumeration:

Value	Description
inbound	Inbound connection
outbound	Outbound connection

B.35. NetworkConfigurationAddressRange_t

The base type is the string limited to the CIDR range address notation: like 192.168.0.0/16, fc00::/7 or 8.8.8.8./32:

B.36. NetworkConfigurationPort_t

The base type is the string limited to one of the following possible formats:

• Specification of a port: 80

• Specification of multiple ports: 80,443

• Specification of a range of ports: 25000:25009

B.37. NetworkType_t

Open enumeration:

Value	Description
public	Connection to an externally routable network, more networks can be available.
public_only	Exclusive connection to an externally routable network.
private	Connection a private network, more networks can be available.
private_only	Exclusive connection to a private network.

B.38. NetVirtualizationT_t

Open enumeration:

Value	Description
none	No network isolation
vswitch	vSwitch isolation
ebtables	EBtables isolation
vlan	VLAN isolation
firewall	Firewall isolation

B.39. OSFamily_t

Open enumeration:

Value	Description
linux	Family of operating systems based on Linux kernel
macosx	Family of operating systems based on MacOS X
solaris	Family of operating systems based on Solaris
windows	Family of operating systems based on Windows

B.40. OSName_t

Open enumeration:

Value	Description
aix	AIX
centos	CentOS
debian	Debian
fedoracore	RedHat Fedora
gentoo	Gentoo Linux
leopard	Mac OS X 10.5 (Leopard)
linux-rocks
mandrake	Mandrake
redhatenterpriseas	RedHat Enterprise Server
scientificlinux	Scientific Linux
scientificlinuxcern	Scientific Linux CERN
suse	SUSE
ubuntu	Ubuntu
windowsvista	Microsoft Windows Vista
windowsxp	Microsoft Windows XP

B.41. Period_t

Open enumeration:

Value	Description
once	The metric is calculated once in the lifetime of the service
asaccounted	The metric is calculated with the same granularity as it is accounted
daily	The metric is calculated daily
monthly	The metric is calculated monthly
yearly	The metric is calculated yearly

B.42. Platform_t

Open enumeration:

Value	Description
amd64	AMD 64bit architecture
i386	Intel 386 architecture
itanium	Intel 64-bit architecture
powerpc	PowerPC architecture
sparc	SPARC architecture

B.43. PolicyScheme_t

Open enumeration:

Value	Description
basic	The basic scheme
gacl	GridSite Access Control List

A policy scheme is defined by a syntax for rules and by a matching algorithm defining how a string MAY be matched against the published rules. For the basic policy scheme, the following syntax MUST be used (defined in EBNF form [EBNF]):

• BASIC RULE ::= ( DN_NAME | VO_NAME | ‘ALL’ )

• DN_RULE ::= ‘dn:’ DN_NAME

• VO_RULE ::= ‘vo:’ [a-zA-Z0-9-_\.]+

• DN_NAME ::=

As a matching algorithm, the basic scheme adopts the exact match (if at least one rule provides an exact match or the rule ‘ALL’ is present, then the subject is authorized to be mapped into the related share). More complex policy schemes SHOULD be defined in profile documents.

Examples of policies expressed using the basic syntax are:

• dn:/C=XX/O=YYYY/OU=Personal Certificate/L=ZZZZ/CN=NAME SURNAME

  • matches the user proving to have a certificate identified by this DN

• vo:/vo_a

  • matches all the users proving to be part of the vo_a

B.44. QualityLevel_t

Closed enumeration:

Value	Description
development	The component is under active development both in functionalities and interfaces
pre-production	The component has completed the development and passed the testing phase; it is being used in real world scenarios
production	The component completed the development and is considered stable for real world scenarios
testing	The component has completed the development phase and is under testing

B.45. ReservationPolicy_t

Closed enumeration:

Value	Description
mandatory	Jobs MUST be submitted only via advance reservation
none	No reservation is supported
optional	Jobs MAY be submitted via advance reservation, but this is not required

B.46. ResourceScope_t

Open enumeration:

Value	Description
any	Any scope (commercial or non-commercial)
commercial	Access by commercial organizations for commercial usage
noncommercial	Access by no-profit or public organizations for non-commercial usage
research	Access for research by any organization, commercial or non-commercial
noncommercialresearch	Access for research by no-profit or public organizations for non-commercial usage
Institutions	Access for public organization, institutions or governments for any scope
euonly	Access restricted to users of EU based countries
owncountryonly	Access restricted to users of the same country of the provider

B.47. RetentionPolicy_t

Open enumeration:

Value	Description
custodial	Low probability of loss
output	An intermediate level and is appropriate for data which MAY be replaced by lengthy or effort-full processes
replica	The highest probability of loss, but is appropriate for data for which a certain amount of loss MAY be tolerated, in particular when other copies MAY be accessed in a timely fashion

B.48. SchedulingPolicy_t

Open enumeration:

Value	Description
fairshare	Statistically guarantees the allocated share
fifo	First-In First-Out
random	Random choice

B.49. ServiceType_t

The RECOMMENDED syntax is in reverse-DNS prefix. The first element is a top-level domain, while the second element is a namespace (the namespace MAY be related to a middleware name, an organization or other concepts; org.ogf.glue is reserved for the OGF GLUE Working Group). The defining body SHOULD have a claim on the corresponding forward DNS name (e.g., org.nordugrid.arex SHOULD be defined by the owners of the nordugrid.org domain name).

Open enumeration:

Value	Description
org.ogf.glue*	Prefix reserved for the OGF GLUE Working Group
org.glite.fts	gLite File Transfer Service
org.glite.lb	gLite Logging and Booking Service
org.glite.wms	gLite Workload Management Service
org.nordugrid.arex	NorduGrid Resource Coupled Execution Service
org.nordugrid.isis	NorduGrid Information Index Service
org.nordugrid.storage	NorduGrid Storage Service
org.teragrid gridftp	TeraGrid GridFTP
org.teragrid.condor-g	TeraGrid Condor-g
org.teragrid.globus-mds4	TeraGrid Globus MDS 4
org.teragrid.gpfs	TeraGrid GPFS
org.teragrid.gsi-openssh	TeraGrid gsi-enabled openssh
org.teragrid.prewsgram	TeraGrid pre-WS Globus GRAM
org.teragrid.rft	TeraGrid Reliable File Transfer
org.teragrid.srb	TeraGrid Storage Resource Broker
org.teragrid.ws-delegation	TeraGrid WS-Delegation Service
org.teragrid.ws-gram	TeraGrid WS-GRAM Service
org.teragrid.ws-ogsadai	TeraGrid OGSA-DAI
org.cloud.iaas	Cloud Infrastructure-as-a-Service
org.cloud.saas	Cloud Storage-as-a-Service

B.50. ServingState_t

Closed enumeration:

Value	Description
closed	The endpoint is not accepting request nor is serving them
draining	The endpoint is not accepting requests, but is serving requests in the queue
production	The endpoint is both accepting and serving requests
queueing	The endpoint is accepting requests, but is not serving them

B.51. Staging_t

Closed enumeration:

Value	Description
none	No staging of files supported
stagingin	Automatic staging in of files supported
staginginout	Automatic staging in and out of files supported
stagingout	Automatic staging out of files supported

B.52. StorageAccessProtocol_t

Open enumeration:

Value	Description
afs	Andrew File System protocol
dcap	DCache access protocol
file	POSIX access
gsidcap	DCAP with GSI authentication
gsiftp	FTP with GSI authentication
gsirfio	RFIO with GSI authentication
http	HyperText Transfer Protocol
https	Secured HyperText Transfer Protocol
nfs	Network File System protocol
rfio	Remote File Input/Output protocol
root	File transfer protocol for the ROOT framework
xrootd	xrootd protocol

B.53. StorageCapacity_t

Open enumeration:

Value	Description
online	Available storage capacity accessible in less than a minute in normal operating conditions
installedonline	Online storage capacity including temporarily unavailable portions which would be accessible in less than a minute in normal operating conditions
nearline	Available storage capacity accessible in more than a minute and less than two days without human intervention in normal operating conditions
installednearline	Nearline storage capacity including temporarily unavailable portions which would be accessible in more than a minute and less than two days without human intervention in normal operating conditions
offline	Storage capacity possibly requiring human intervention for access in normal operating conditions
cache	Storage capacity accessible in less than a minute used internally by the storage system and not directly exposed to the user

B.54. StorageManagerType_t

Open enumeration:

Value	Description
castor	CERN Advanced STOrage manager, disk and tape management system
dcache	Disk Cache, disk managing system with ability to control tape backends (e.g., Enstore)
enstore	Tape Storage system, tape management system
gpfs	General Parallel File System, disk management system
sse	Smart Storage Element, disk management system
tsm	IBM Tivoli Storage Manager, disk and tape management system
swift	OpenStack SWIFT
cdmi-proxy	CDMI Proxy

B.55. VirtType_t

Open enumeration:

Value	Description
emulation	Full virtualization with emulation
paravirtualization	Para-virtualization
hardware	Hardware assisted virtualization
vgpu	NVidia vGPU