## direct-io.hg

### changeset 14300:3f8f5854acf0

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>
author Ewan Mellor Fri Mar 09 00:35:29 2007 +0000 (2007-03-09) 2ff4a2a5a6e5 f421ccd1141f docs/xen-api/presentation.tex
line diff
     1.1 --- a/docs/xen-api/presentation.tex	Thu Mar 08 23:47:24 2007 +0000
1.2 +++ b/docs/xen-api/presentation.tex	Fri Mar 09 00:35:29 2007 +0000
1.3 @@ -57,14 +57,14 @@ type $t_1$ to values of type $t_2$.
1.4  \end{itemize}
1.5
1.6  Note that there are a number of cases where {\em Ref}s are {\em doubly
1.7 -linked\/}---e.g.\ a VM has a field called {\tt groups} of type
1.8 -$(\mathit{VMGroup}~\mathit{Ref})~\mathit{Set}$; this field lists
1.9 -the VMGroups that a particular VM is part of. Similarly, the VMGroups
1.10 -class has a field called {\tt VMs} of type $(\mathit{VM}~{\mathit 1.11 -Ref})~\mathit{Set}$ that contains the VMs that are part of a particular
1.12 -VMGroup. These two fields are {\em bound together\/}, in the sense that
1.13 -adding a new VMGroup to a VM causes the VMs field of the corresponding
1.14 -VMGroup object to be updated automatically.
1.15 +linked\/}---e.g.\ a VM has a field called {\tt VIFs} of type
1.16 +$(\mathit{VIF}~\mathit{Ref})~\mathit{Set}$; this field lists
1.17 +the network interfaces attached to a particular VM. Similarly, the VIF
1.18 +class has a field called {\tt VM} of type $(\mathit{VM}~{\mathit 1.19 +Ref})$ which references the VM to which the interface is connected.
1.20 +These two fields are {\em bound together\/}, in the sense that
1.21 +creating a new VIF causes the {\tt VIFs} field of the corresponding
1.22 +VM object to be updated automatically.
1.23
1.24  The API reference explicitly lists the fields that are
1.25  bound together in this way. It also contains a diagram that shows