ia64/xen-unstable

annotate tools/examples/xend-config.sxp @ 12606:ee70bf177981

Added configuration for authentication through Xen-API -- it can now be set
to use PAM, or to be turned off entirely, on a listener by listener basis.

Listen on a different unix domain socket for the Xen-API server, so that it
can co-exist with the others.

Signed-off-by: Ewan Mellor <ewan@xensource.com>
author Ewan Mellor <ewan@xensource.com>
date Tue Nov 28 11:31:46 2006 +0000 (2006-11-28)
parents 6206685650f5
children ee1febe317f7
rev   line source
emellor@7467 1 # -*- sh -*-
emellor@7467 2
emellor@7467 3 #
mjw@1723 4 # Xend configuration file.
emellor@7467 5 #
mjw@1723 6
nivedita@8404 7 # This example configuration is appropriate for an installation that
nivedita@8404 8 # utilizes a bridged network configuration. Access to xend via http
nivedita@8404 9 # is disabled.
emellor@7467 10
emellor@7467 11 # Commented out entries show the default for that entry, unless otherwise
emellor@7467 12 # specified.
emellor@7467 13
kaf24@11316 14 #(logfile /var/log/xen/xend.log)
emellor@7467 15 #(loglevel DEBUG)
mjw@1723 16
ewan@12606 17
ewan@12606 18 # The Xen-API server configuration. (Please note that this server is
ewan@12606 19 # available as an UNSUPPORTED PREVIEW in Xen 3.0.4, and should not be relied
ewan@12606 20 # upon).
ewan@12604 21 #
ewan@12604 22 # This value configures the ports, interfaces, and access controls for the
ewan@12604 23 # Xen-API server. Each entry in the list starts with either unix, a port
ewan@12604 24 # number, or an address:port pair. If this is "unix", then a UDP socket is
ewan@12604 25 # opened, and this entry applies to that. If it is a port, then Xend will
ewan@12606 26 # listen on all interfaces on that TCP port, and if it is an address:port
ewan@12606 27 # pair, then Xend will listen on the specified port, using the interface with
ewan@12606 28 # the specified address.
ewan@12606 29 #
ewan@12606 30 # The subsequent string configures the user-based access control for the
ewan@12606 31 # listener in question. This can be one of "none" or "pam", indicating either
ewan@12606 32 # that users should be allowed access unconditionally, or that the local
ewan@12606 33 # Pluggable Authentication Modules configuration should be used. If this
ewan@12606 34 # string is missing or empty, then "pam" is used.
ewan@12604 35 #
ewan@12606 36 # The final string gives the host-based access control for that listener. If
ewan@12606 37 # this is missing or empty, then all connections are accepted. Otherwise,
ewan@12606 38 # this should be a space-separated sequence of regular expressions; any host
ewan@12606 39 # with a fully-qualified domain name or an IP address that matches one of
ewan@12606 40 # these regular expressions will be accepted.
ewan@12604 41 #
ewan@12606 42 # Example: listen on TCP port 9363 on all interfaces, accepting connections
ewan@12606 43 # only from machines in example.com or localhost, and allow access through
ewan@12606 44 # the unix domain socket unconditionally:
ewan@12604 45 #
ewan@12606 46 # (xen-api-server ((9363 pam '^localhost$ example\\.com$')
ewan@12606 47 # (unix none)))
ewan@12604 48 #
ewan@12604 49 # Default:
ewan@12604 50 # (xen-api-server ((unix)))
ewan@12604 51
ewan@12606 52
emellor@7467 53 #(xend-http-server no)
emellor@9425 54 #(xend-unix-server no)
emellor@9425 55 #(xend-tcp-xmlrpc-server no)
emellor@9425 56 #(xend-unix-xmlrpc-server yes)
emellor@7467 57 #(xend-relocation-server no)
emellor@7467 58 (xend-relocation-server yes)
emellor@7467 59
emellor@7467 60 #(xend-unix-path /var/lib/xend/xend-socket)
mjw@4095 61
emellor@7467 62 # Port xend should use for the HTTP interface, if xend-http-server is set.
emellor@7467 63 #(xend-port 8000)
emellor@7467 64
emellor@7467 65 # Port xend should use for the relocation interface, if xend-relocation-server
emellor@7467 66 # is set.
emellor@7467 67 #(xend-relocation-port 8002)
emellor@7467 68
emellor@7467 69 # Address xend should listen on for HTTP connections, if xend-http-server is
emellor@7467 70 # set.
mjw@1723 71 # Specifying 'localhost' prevents remote connections.
emellor@7467 72 # Specifying the empty string '' (the default) allows all connections.
emellor@7467 73 #(xend-address '')
nivedita@8404 74 #(xend-address localhost)
mjw@1723 75
emellor@7467 76 # Address xend should listen on for relocation-socket connections, if
emellor@7467 77 # xend-relocation-server is set.
emellor@7467 78 # Meaning and default as for xend-address above.
emellor@7467 79 #(xend-relocation-address '')
emellor@8326 80
emellor@8326 81 # The hosts allowed to talk to the relocation port. If this is empty (the
emellor@8326 82 # default), then all connections are allowed (assuming that the connection
emellor@8326 83 # arrives on a port and interface on which we are listening; see
emellor@8326 84 # xend-relocation-port and xend-relocation-address above). Otherwise, this
emellor@8326 85 # should be a space-separated sequence of regular expressions. Any host with
emellor@8326 86 # a fully-qualified domain name or an IP address that matches one of these
emellor@8326 87 # regular expressions will be accepted.
emellor@8326 88 #
emellor@8326 89 # For example:
ewan@12208 90 # (xend-relocation-hosts-allow '^localhost$ ^.*\\.example\\.org$')
emellor@8326 91 #
emellor@8326 92 #(xend-relocation-hosts-allow '')
kfraser@11071 93 (xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
mjw@4095 94
emellor@7441 95 # The limit (in kilobytes) on the size of the console buffer
emellor@7467 96 #(console-limit 1024)
emellor@7441 97
emellor@7557 98 ##
emellor@7557 99 # To bridge network traffic, like this:
emellor@7557 100 #
emellor@7557 101 # dom0: fake eth0 -> vif0.0 -+
emellor@7557 102 # |
emellor@7557 103 # bridge -> real eth0 -> the network
emellor@7557 104 # |
emellor@7557 105 # domU: fake eth0 -> vifN.0 -+
emellor@7557 106 #
emellor@7557 107 # use
emellor@7557 108 #
emellor@7557 109 # (network-script network-bridge)
emellor@7557 110 #
emellor@8821 111 # Your default ethernet device is used as the outgoing interface, by default.
emellor@8821 112 # To use a different one (e.g. eth1) use
emellor@7557 113 #
emellor@7557 114 # (network-script 'network-bridge netdev=eth1')
emellor@7557 115 #
emellor@7557 116 # The bridge is named xenbr0, by default. To rename the bridge, use
emellor@7557 117 #
emellor@7557 118 # (network-script 'network-bridge bridge=<name>')
emellor@7557 119 #
emellor@7557 120 # It is possible to use the network-bridge script in more complicated
emellor@7557 121 # scenarios, such as having two outgoing interfaces, with two bridges, and
emellor@7557 122 # two fake interfaces per guest domain. To do things like this, write
emellor@7557 123 # yourself a wrapper script, and call network-bridge from it, as appropriate.
emellor@7557 124 #
emellor@7557 125 (network-script network-bridge)
kaf24@3431 126
emellor@7557 127 # The script used to control virtual interfaces. This can be overridden on a
emellor@7557 128 # per-vif basis when creating a domain or a configuring a new vif. The
emellor@7557 129 # vif-bridge script is designed for use with the network-bridge script, or
emellor@7557 130 # similar configurations.
emellor@7557 131 #
emellor@7557 132 # If you have overridden the bridge name using
emellor@7557 133 # (network-script 'network-bridge bridge=<name>') then you may wish to do the
emellor@7557 134 # same here. The bridge name can also be set when creating a domain or
emellor@7557 135 # configuring a new vif, but a value specified here would act as a default.
emellor@7557 136 #
emellor@7557 137 # If you are using only one bridge, the vif-bridge script will discover that,
emellor@7557 138 # so there is no need to specify it explicitly.
emellor@7557 139 #
emellor@7557 140 (vif-script vif-bridge)
emellor@7557 141
emellor@7557 142
emellor@7557 143 ## Use the following if network traffic is routed, as an alternative to the
emellor@7557 144 # settings for bridged networking given above.
emellor@7557 145 #(network-script network-route)
emellor@7557 146 #(vif-script vif-route)
emellor@7557 147
emellor@7557 148
emellor@7557 149 ## Use the following if network traffic is routed with NAT, as an alternative
emellor@7557 150 # to the settings for bridged networking given above.
emellor@7557 151 #(network-script network-nat)
emellor@7557 152 #(vif-script vif-nat)
emellor@7557 153
mjw@1723 154
kaf24@5932 155 # Dom0 will balloon out when needed to free memory for domU.
kaf24@5932 156 # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.
kaf24@5932 157 # If dom0-min-mem=0, dom0 will never balloon out.
iap10@8218 158 (dom0-min-mem 196)
kaf24@5932 159
cl349@6916 160 # In SMP system, dom0 will use dom0-cpus # of CPUS
kaf24@5932 161 # If dom0-cpus = 0, dom0 will take all cpus available
kaf24@5932 162 (dom0-cpus 0)
emellor@7467 163
emellor@7467 164 # Whether to enable core-dumps when domains crash.
emellor@7467 165 #(enable-dump no)
emellor@9727 166
emellor@9727 167 # The tool used for initiating virtual TPM migration
emellor@9727 168 #(external-migration-tool '')
ewan@12191 169
ewan@12191 170 # The interface for VNC servers to listen on. Defaults
ewan@12191 171 # to 127.0.0.1 To restore old 'listen everywhere' behaviour
ewan@12191 172 # set this to 0.0.0.0
ewan@12191 173 #(vnc-listen '127.0.0.1')
ewan@12191 174
ewan@12191 175 # The default password for VNC console on HVM domain.
ewan@12191 176 # Empty string is no authentication.
ewan@12191 177 (vncpasswd '')