# WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/

 Home Products Support Community News

# xen-changelog

## [Xen-changelog] [xen-unstable] Changed the example of linked references

 To: xen-changelog@xxxxxxxxxxxxxxxxxxx [Xen-changelog] [xen-unstable] Changed the example of linked references (Set(Ref(x)) <-> Ref(y)) to use VM and Xen patchbot-unstable Fri, 09 Mar 2007 11:30:14 -0800 Fri, 09 Mar 2007 11:30:02 -0800 www-data@xxxxxxxxxxxxxxxxxx BK change log , , xen-devel@xxxxxxxxxxxxxxxxxxx xen-changelog-bounces@xxxxxxxxxxxxxxxxxxx
 # HG changeset patch # User Ewan Mellor # Date 1173400529 0 # Node ID 3f8f5854acf005d200f3eee46498fc2d1e5506ba # Parent 2ff4a2a5a6e5286a92d26c330564d943f95d2552 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 --- docs/xen-api/presentation.tex | 16 ++++++++-------- 1 files changed, 8 insertions(+), 8 deletions(-) diff -r 2ff4a2a5a6e5 -r 3f8f5854acf0 docs/xen-api/presentation.tex --- a/docs/xen-api/presentation.tex Thu Mar 08 23:47:24 2007 +0000 +++ b/docs/xen-api/presentation.tex Fri Mar 09 00:35:29 2007 +0000 @@ -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 _______________________________________________ Xen-changelog mailing list Xen-changelog@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-changelog 
 Current Thread [Xen-changelog] [xen-unstable] Changed the example of linked references (Set(Ref(x)) <-> Ref(y)) to use VM and, Xen patchbot-unstable <=