Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
openeuler
libvirt
提交
cc24589e
L
libvirt
项目概览
openeuler
/
libvirt
通知
3
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
L
libvirt
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
提交
cc24589e
编写于
2月 12, 2013
作者:
J
John Ferlan
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
api: Reword and clean lists for object description
上级
b8a0b631
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
40 addition
and
27 deletion
+40
-27
docs/api.html.in
docs/api.html.in
+40
-27
未找到文件。
docs/api.html.in
浏览文件 @
cc24589e
...
...
@@ -37,43 +37,56 @@
</p>
<p>
The figure above shows the five main objects exported by the API:
</p>
<ul>
<li>
virConnectPtr: represent a connection to an hypervisor.
</li>
<li>
virDomainPtr: represent one domain either active or defined (i.e.
existing as permanent config file and storage but not currently running
on that node). The function
<code
class=
'docref'
>
virConnectListDomains
</code>
allows to list all the IDs for the domains active on this hypervisor.
</li>
<li>
virNetworkPtr: represent one network either active or defined (i.e.
existing as permanent config file and storage but not currently activated.
The function
<code
class=
'docref'
>
virConnectListNetworks
</code>
allows to list all the virtualization networks activated on this node.
</li>
<li>
virStorageVolPtr: represent one storage volume, usually this is used
<li><code
class=
'docref'
>
virConnectPtr
</code>
<p>
Represents the connection to a hypervisor. Use one of the
<a
href=
"html/libvirt-libvirt.html#virConnectOpen"
>
virConnectOpen
</a>
functions to obtain connection to the hypervisor which is then used
as a parameter to other connection API's.
</p></li>
<li><code
class=
'docref'
>
virDomainPtr
</code>
<p>
Represents one domain either active or defined (i.e. existing as
permanent config file and storage but not currently running on that
node). The function
<code
class=
'docref'
>
virConnectListAllDomains
</code>
lists all the domains for the hypervisor.
</p></li>
<li><code
class=
'docref'
>
virNetworkPtr
</code>
<p>
Represents one network either active or defined (i.e. existing
as permanent config file and storage but not currently activated).
The function
<code
class=
'docref'
>
virConnectListAllNetworks
</code>
lists all the virtualization networks for the hypervisor.
</p></li>
<li><code
class=
'docref'
>
virStorageVolPtr
</code>
<p>
Represents one storage volume generally used
as a block device available to one of the domains. The function
<code
class=
"docref"
>
virStorageVolLookupByPath
</code>
allows to find
the object based on its path on the node.
</li>
<li>
virStoragePoolPtr: represent a storage pool, i.e. a logical area
which can be used to allocate and store storage volumes. The function
<code
class=
"docref"
>
virStoragePoolLookupByVolume
</code>
allows to find
the storage pool containing a given storage volume.
</li>
<code
class=
"docref"
>
virStorageVolLookupByPath
</code>
finds
the storage volume object based on its path on the node.
</p></li>
<li><code
class=
'docref'
>
virStoragePoolPtr
</code>
<p>
Represents a storage pool, which is a logical area
used to allocate and store storage volumes. The function
<code
class=
'docref'
>
virConnectListAllStoragePools
</code>
lists
all of the virtualization storage pools on the hypervisor. The function
<code
class=
"docref"
>
virStoragePoolLookupByVolume
</code>
finds
the storage pool containing a given storage volume.
</p></li>
</ul>
<p>
Most object manipulated by the library can also be represented using
<p>
Most object
s
manipulated by the library can also be represented using
XML descriptions. This is used primarily to create those object, but is
also helpful to modify or save their description back.
</p>
<p>
Domains, network and storage pools can be either
<code>
active
</code>
<p>
Domains, network
s,
and storage pools can be either
<code>
active
</code>
i.e. either running or available for immediate use, or
<code>
defined
</code>
in which case they are inactive but there is
a permanent definition available in the system for them. Based on this
th
a
y can be activated dynamically in order to be used.
</p>
<p>
Most
kind of object
can also be named in various ways:
</p>
th
e
y can be activated dynamically in order to be used.
</p>
<p>
Most
objects
can also be named in various ways:
</p>
<ul>
<li>
by their
<code>
name
</code>
, an user friendly identifier but
whose unicity cannot be guaranteed between two nodes.
</li>
<li>
by their
<code>
ID
</code>
, which is a runtime unique identifier
provided by the hypervisor for one given activation of the object,
but it becomes invalid once the resource is deactivated.
</li >
<li>
by their
<code>
UUID
</code>
, a 16 bytes unique identifier
<li><code>
name
</code>
<p>
A user friendly identifier but whose uniqueness
cannot be guaranteed between two nodes.
</p></li>
<li><code>
ID
</code>
<p>
A runtime unique identifier
provided by the hypervisor for one given activation of the object;
however, it becomes invalid once the resource is deactivated.
</p></li >
<li><code>
UUID
</code>
<p>
A 16 byte unique identifier
as defined in
<a
href=
"http://www.ietf.org/rfc/rfc4122.txt"
>
RFC 4122
</a>
,
which is guaranteed to be unique for long term usage and across a
set of nodes.
</li>
set of nodes.
</
p></
li>
</ul>
<h2><a
name=
"Functions"
>
Functions and naming
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录