diff options
author | Ewan Mellor <ewan@xensource.com> | 2007-03-09 00:35:29 +0000 |
---|---|---|
committer | Ewan Mellor <ewan@xensource.com> | 2007-03-09 00:35:29 +0000 |
commit | 35dc73888007d5317bb606ceecadb305d9fefb03 (patch) | |
tree | 7cd8a2a98ab3d979990f03fc61595a4a71ee50ec /docs/xen-api/presentation.tex | |
parent | 9e92a72fb5e29900dd1bc57cf0592d916a03a109 (diff) | |
download | xen-35dc73888007d5317bb606ceecadb305d9fefb03.tar.gz xen-35dc73888007d5317bb606ceecadb305d9fefb03.tar.bz2 xen-35dc73888007d5317bb606ceecadb305d9fefb03.zip |
Changed the example of linked references (Set(Ref(x)) <-> Ref(y)) to use VM and
VIFs rather than VM and VMGroups, now that we've deleted VMGroups.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
Diffstat (limited to 'docs/xen-api/presentation.tex')
-rw-r--r-- | docs/xen-api/presentation.tex | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/xen-api/presentation.tex b/docs/xen-api/presentation.tex index ba7ebdbde7..abc18bafe9 100644 --- a/docs/xen-api/presentation.tex +++ b/docs/xen-api/presentation.tex @@ -57,14 +57,14 @@ type $t_1$ to values of type $t_2$. \end{itemize} Note that there are a number of cases where {\em Ref}s are {\em doubly -linked\/}---e.g.\ a VM has a field called {\tt groups} of type -$(\mathit{VMGroup}~\mathit{Ref})~\mathit{Set}$; this field lists -the VMGroups that a particular VM is part of. Similarly, the VMGroups -class has a field called {\tt VMs} of type $(\mathit{VM}~{\mathit -Ref})~\mathit{Set}$ that contains the VMs that are part of a particular -VMGroup. These two fields are {\em bound together\/}, in the sense that -adding a new VMGroup to a VM causes the VMs field of the corresponding -VMGroup object to be updated automatically. +linked\/}---e.g.\ a VM has a field called {\tt VIFs} of type +$(\mathit{VIF}~\mathit{Ref})~\mathit{Set}$; this field lists +the network interfaces attached to a particular VM. Similarly, the VIF +class has a field called {\tt VM} of type $(\mathit{VM}~{\mathit +Ref})$ which references the VM to which the interface is connected. +These two fields are {\em bound together\/}, in the sense that +creating a new VIF causes the {\tt VIFs} field of the corresponding +VM object to be updated automatically. The API reference explicitly lists the fields that are bound together in this way. It also contains a diagram that shows |