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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] [Xend] Extend Xen-API with function to reset the

To: Stefan Berger <stefanb@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [Xend] Extend Xen-API with function to reset the policy
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Mon, 10 Dec 2007 20:47:40 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Dec 2007 12:48:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1197319388.10648.5.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1197319388.10648.5.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Dec 10, 2007 at 03:43:08PM -0500, Stefan Berger wrote:

> --- root.orig/xen-unstable.hg/docs/xen-api/xenapi-datamodel.tex
> +++ root/xen-unstable.hg/docs/xen-api/xenapi-datamodel.tex
> @@ -14735,6 +14735,45 @@ xs\_policystate
>  State information about the policy. In case an error occurred, the 'xs\_err'
>  field contains the error code. The 'errors' may contain further information
>  about the error.
> + \vspace{0.3cm}
> +\vspace{0.3cm}
> +\vspace{0.3cm}
> +\subsubsection{RPC name:~reset\_xspolicy}
> +
> +{\bf Overview:}
> +Attempt to reset the system's policy by installing the default policy.
> +Since this function is implemented as an update to the current policy, it
> +underlies the same restrictions. This function may fail if for example

This might have happened before, but I just noticed that the API docs
are being modified without any version control - or any indication of
when new things were added.

Programming against such API docs is generally a horrible experience as
you never have any idea what is there and what isn't.

Can we please start a changelog for the API, and version it
appropriately?

thanks
john

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel