ia64/xen-unstable

view tools/examples/xend-config.sxp @ 13616:ee1febe317f7

[XEND] Allow TCP XMLRPC address:port to be configured, if enabled.

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