1.1 --- a/tools/examples/Makefile	Tue Mar 13 18:13:11 2007 -0600
     1.2 +++ b/tools/examples/Makefile	Fri Mar 30 11:55:34 2007 +0100
     1.3 @@ -9,7 +9,9 @@ XENDOMAINS_SYSCONFIG = init.d/sysconfig.
     1.4  # Xen configuration dir and configs to go there.
     1.5  XEN_CONFIG_DIR = /etc/xen
     1.6  XEN_CONFIGS = xend-config.sxp
     1.7 +XEN_CONFIGS += xend-config-xenapi.sxp
     1.8  XEN_CONFIGS += xm-config.xml
     1.9 +XEN_CONFIGS += xm-config-xenapi.xml
    1.10  XEN_CONFIGS += xmexample1 
    1.11  XEN_CONFIGS += xmexample2
    1.12  XEN_CONFIGS += xmexample.hvm

     2.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.2 +++ b/tools/examples/xend-config-xenapi.sxp	Fri Mar 30 11:55:34 2007 +0100
     2.3 @@ -0,0 +1,195 @@
     2.4 +# -*- sh -*-
     2.5 +
     2.6 +#
     2.7 +# Xend configuration file.
     2.8 +#
     2.9 +
    2.10 +# This example configuration is appropriate for an installation that 
    2.11 +# utilizes a bridged network configuration. Access to xend via http
    2.12 +# is disabled.  
    2.13 +
    2.14 +# Commented out entries show the default for that entry, unless otherwise
    2.15 +# specified.
    2.16 +
    2.17 +#(logfile /var/log/xen/xend.log)
    2.18 +#(loglevel DEBUG)
    2.19 +
    2.20 +
    2.21 +# The Xen-API server configuration.  (Please note that this server is
    2.22 +# available as an UNSUPPORTED PREVIEW in Xen 3.0.4, and should not be relied
    2.23 +# upon).
    2.24 +#
    2.25 +# This value configures the ports, interfaces, and access controls for the
    2.26 +# Xen-API server.  Each entry in the list starts with either unix, a port
    2.27 +# number, or an address:port pair.  If this is "unix", then a UDP socket is
    2.28 +# opened, and this entry applies to that.  If it is a port, then Xend will
    2.29 +# listen on all interfaces on that TCP port, and if it is an address:port
    2.30 +# pair, then Xend will listen on the specified port, using the interface with
    2.31 +# the specified address.
    2.32 +#
    2.33 +# The subsequent string configures the user-based access control for the
    2.34 +# listener in question.  This can be one of "none" or "pam", indicating either
    2.35 +# that users should be allowed access unconditionally, or that the local
    2.36 +# Pluggable Authentication Modules configuration should be used.  If this
    2.37 +# string is missing or empty, then "pam" is used.
    2.38 +#
    2.39 +# The final string gives the host-based access control for that listener. If
    2.40 +# this is missing or empty, then all connections are accepted.  Otherwise,
    2.41 +# this should be a space-separated sequence of regular expressions; any host
    2.42 +# with a fully-qualified domain name or an IP address that matches one of
    2.43 +# these regular expressions will be accepted.
    2.44 +#
    2.45 +# Example: listen on TCP port 9363 on all interfaces, accepting connections
    2.46 +# only from machines in example.com or localhost, and allow access through
    2.47 +# the unix domain socket unconditionally:
    2.48 +#
    2.49 +   (xen-api-server ((9363 none)))
    2.50 +#                    (unix none)))
    2.51 +#
    2.52 +# Optionally, the TCP Xen-API server can use SSL by specifying the private
    2.53 +# key and certificate location:
    2.54 +#
    2.55 +#                    (9367 pam '' /etc/xen/xen-api.key /etc/xen/xen-api.crt)
    2.56 +#
    2.57 +# Default:
    2.58 +#   (xen-api-server ((unix)))
    2.59 +
    2.60 +
    2.61 +#(xend-http-server no)
    2.62 +#(xend-unix-server no)
    2.63 +#(xend-tcp-xmlrpc-server no)
    2.64 +#(xend-unix-xmlrpc-server yes)
    2.65 +#(xend-relocation-server no)
    2.66 +(xend-relocation-server yes)
    2.67 +
    2.68 +#(xend-unix-path /var/lib/xend/xend-socket)
    2.69 +
    2.70 +
    2.71 +# Address and port xend should use for the legacy TCP XMLRPC interface, 
    2.72 +# if xen-tcp-xmlrpc-server is set.
    2.73 +#(xen-tcp-xmlrpc-server-address 'localhost')
    2.74 +#(xen-tcp-xmlrpc-server-port 8006)
    2.75 +
    2.76 +# SSL key and certificate to use for the legacy TCP XMLRPC interface.
    2.77 +# Setting these will mean that this port serves only SSL connections as
    2.78 +# opposed to plaintext ones.
    2.79 +#(xend-tcp-xmlrpc-server-ssl-key-file  /etc/xen/xmlrpc.key)
    2.80 +#(xend-tcp-xmlrpc-server-ssl-cert-file /etc/xen/xmlrpc.crt)
    2.81 +
    2.82 +
    2.83 +# Port xend should use for the HTTP interface, if xend-http-server is set.
    2.84 +#(xend-port            8000)
    2.85 +
    2.86 +# Port xend should use for the relocation interface, if xend-relocation-server
    2.87 +# is set.
    2.88 +#(xend-relocation-port 8002)
    2.89 +
    2.90 +# Address xend should listen on for HTTP connections, if xend-http-server is
    2.91 +# set.
    2.92 +# Specifying 'localhost' prevents remote connections.
    2.93 +# Specifying the empty string '' (the default) allows all connections.
    2.94 +#(xend-address '')
    2.95 +#(xend-address localhost)
    2.96 +
    2.97 +# Address xend should listen on for relocation-socket connections, if
    2.98 +# xend-relocation-server is set.
    2.99 +# Meaning and default as for xend-address above.
   2.100 +#(xend-relocation-address '')
   2.101 +
   2.102 +# The hosts allowed to talk to the relocation port.  If this is empty (the
   2.103 +# default), then all connections are allowed (assuming that the connection
   2.104 +# arrives on a port and interface on which we are listening; see
   2.105 +# xend-relocation-port and xend-relocation-address above).  Otherwise, this
   2.106 +# should be a space-separated sequence of regular expressions.  Any host with
   2.107 +# a fully-qualified domain name or an IP address that matches one of these
   2.108 +# regular expressions will be accepted.
   2.109 +#
   2.110 +# For example:
   2.111 +#  (xend-relocation-hosts-allow '^localhost$ ^.*\\.example\\.org$')
   2.112 +#
   2.113 +#(xend-relocation-hosts-allow '')
   2.114 +(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
   2.115 +
   2.116 +# The limit (in kilobytes) on the size of the console buffer
   2.117 +#(console-limit 1024)
   2.118 +
   2.119 +##
   2.120 +# To bridge network traffic, like this:
   2.121 +#
   2.122 +# dom0: fake eth0 -> vif0.0 -+
   2.123 +#                            |
   2.124 +#                          bridge -> real eth0 -> the network
   2.125 +#                            |
   2.126 +# domU: fake eth0 -> vifN.0 -+
   2.127 +#
   2.128 +# use
   2.129 +#
   2.130 +# (network-script network-bridge)
   2.131 +#
   2.132 +# Your default ethernet device is used as the outgoing interface, by default. 
   2.133 +# To use a different one (e.g. eth1) use
   2.134 +#
   2.135 +# (network-script 'network-bridge netdev=eth1')
   2.136 +#
   2.137 +# The bridge is named xenbr0, by default.  To rename the bridge, use
   2.138 +#
   2.139 +# (network-script 'network-bridge bridge=<name>')
   2.140 +#
   2.141 +# It is possible to use the network-bridge script in more complicated
   2.142 +# scenarios, such as having two outgoing interfaces, with two bridges, and
   2.143 +# two fake interfaces per guest domain.  To do things like this, write
   2.144 +# yourself a wrapper script, and call network-bridge from it, as appropriate.
   2.145 +#
   2.146 +(network-script network-bridge)
   2.147 +
   2.148 +# The script used to control virtual interfaces.  This can be overridden on a
   2.149 +# per-vif basis when creating a domain or a configuring a new vif.  The
   2.150 +# vif-bridge script is designed for use with the network-bridge script, or
   2.151 +# similar configurations.
   2.152 +#
   2.153 +# If you have overridden the bridge name using
   2.154 +# (network-script 'network-bridge bridge=<name>') then you may wish to do the
   2.155 +# same here.  The bridge name can also be set when creating a domain or
   2.156 +# configuring a new vif, but a value specified here would act as a default.
   2.157 +#
   2.158 +# If you are using only one bridge, the vif-bridge script will discover that,
   2.159 +# so there is no need to specify it explicitly.
   2.160 +#
   2.161 +(vif-script vif-bridge)
   2.162 +
   2.163 +
   2.164 +## Use the following if network traffic is routed, as an alternative to the
   2.165 +# settings for bridged networking given above.
   2.166 +#(network-script network-route)
   2.167 +#(vif-script     vif-route)
   2.168 +
   2.169 +
   2.170 +## Use the following if network traffic is routed with NAT, as an alternative
   2.171 +# to the settings for bridged networking given above.
   2.172 +#(network-script network-nat)
   2.173 +#(vif-script     vif-nat)
   2.174 +
   2.175 +
   2.176 +# Dom0 will balloon out when needed to free memory for domU.
   2.177 +# dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.
   2.178 +# If dom0-min-mem=0, dom0 will never balloon out.
   2.179 +(dom0-min-mem 196)
   2.180 +
   2.181 +# In SMP system, dom0 will use dom0-cpus # of CPUS
   2.182 +# If dom0-cpus = 0, dom0 will take all cpus available
   2.183 +(dom0-cpus 0)
   2.184 +
   2.185 +# Whether to enable core-dumps when domains crash.
   2.186 +#(enable-dump no)
   2.187 +
   2.188 +# The tool used for initiating virtual TPM migration
   2.189 +#(external-migration-tool '')
   2.190 +
   2.191 +# The interface for VNC servers to listen on. Defaults
   2.192 +# to 127.0.0.1  To restore old 'listen everywhere' behaviour
   2.193 +# set this to 0.0.0.0
   2.194 +#(vnc-listen '127.0.0.1')
   2.195 +
   2.196 +# The default password for VNC console on HVM domain.
   2.197 +# Empty string is no authentication.
   2.198 +(vncpasswd '')

     3.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     3.2 +++ b/tools/examples/xm-config-xenapi.xml	Fri Mar 30 11:55:34 2007 +0100
     3.3 @@ -0,0 +1,43 @@
     3.4 +<!--
     3.5 +
     3.6 +Copyright (C) 2006 XenSource Inc.
     3.7 +
     3.8 +This library is free software; you can redistribute it and/or
     3.9 +modify it under the terms of version 2.1 of the GNU Lesser General Public
    3.10 +License as published by the Free Software Foundation.
    3.11 +
    3.12 +This library is distributed in the hope that it will be useful,
    3.13 +but WITHOUT ANY WARRANTY; without even the implied warranty of
    3.14 +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
    3.15 +Lesser General Public License for more details.
    3.16 +
    3.17 +You should have received a copy of the GNU Lesser General Public
    3.18 +License along with this library; if not, write to the Free Software
    3.19 +Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
    3.20 +
    3.21 +-->
    3.22 +
    3.23 +<!--
    3.24 +
    3.25 +This is a configuration file for xm; it should be placed in
    3.26 +/etc/xen/xm-config.xml.  If this file is missing, then xm will fall back to
    3.27 +the normal behaviour that's in Xen 3.0.4 and below.  The settings here are
    3.28 +most useful for experimenting with the Xen-API preview in Xen 3.0.4.
    3.29 +
    3.30 +-->
    3.31 +
    3.32 +<xm>
    3.33 +  <!-- The server element describes how to talk to Xend.  The type may be 
    3.34 +       Xen-API or LegacyXMLRPC (the default).  The URI is that of the
    3.35 +       server; you might try http://server:9363/ or
    3.36 +       httpu:///var/run/xend/xen-api.sock for the Xen-API, or
    3.37 +       httpu:///var/run/xend/xmlrpc.sock for the legacy server.
    3.38 +
    3.39 +       The username and password attributes will be used to log in if Xen-API
    3.40 +       is being used.
    3.41 +    -->
    3.42 +  <server type='Xen-API'
    3.43 +          uri='http://localhost:9363/'
    3.44 +          username='me'
    3.45 +          password='mypassword' />
    3.46 +</xm>