2
# Eucalyptus configuration.
5
# These are to instruct the init.d script on what to start.
8
# This variable points to where eucalyptus has been installed.
11
# This is the username that you would like eucalyptus to run as
12
EUCA_USER="eucalyptus"
14
# Uncomment this field if you do not plan on using the dynamic block
15
# store functionality of Eucalyptus
18
# This variable controls whether ws-security is enabled between
19
# eucalyptus components. The default settings provide secure
20
# connections between the Cloud, Cluster, and Node Controllers and we
21
# recommend that this feature remains enabled. If you wish to disable security,
22
# you must change this variable to "N" and manually configure the
23
# services.xml for both Cluster and Node Controllers (see documentation
25
ENABLE_WS_SECURITY="Y"
27
# This variable controls the level of logging output that appears in
28
# various eucalyptus log files. The options are, in descending order
29
# of verbosity, 'DEBUG, INFO, WARN, ERROR, and
30
# FATAL'. The default is DEBUG (everything).
34
# The following are Cloud Controller configuration options.
37
# The Cloud Controller needs 2 ports.
42
# These following are Cluster Controller configuration options.
45
# This is the port the Cluster Controller will be listening on.
48
# This option configures the Cluster Controller's scheduling policy.
49
# Currently, this option can be set to GREEDY (first node that is
50
# found that can run the VM will be chosen) or ROUNDROBIN (nodes are
51
# selected one after another until one is found that can run the VM).
52
SCHEDPOLICY="ROUNDROBIN"
54
# The list of Node Controllers the Cluster Controller will communicate with.
56
# If you are running Rocks, you can run "rocks list host" to
57
# find out the list of machines available to you (in our case we are
58
# interested in the VM Container kind).
61
# The name of the Node Controller service. Change this if you want
62
# to plug in your own Node Controller service.
63
NC_SERVICE="axis2/services/EucalyptusNC"
66
# The following are Node Controller configuration options.
69
# This is the port the Node Controller will be listening on.
72
# The hypervisor that the Node Controller will interact with in order
73
# to manage virtual machines. Currently, supported values are 'kvm'
77
# The maximum amount of memory Eucalyptus is allowed to use on the node:
78
# if you leave this commented out, Eucalyptus will use all available
79
# memory, otherwise it will use at most this value for ALL running instances.
82
# The maximum number of CPU/cores Eucalyptus is allowed to use on the
83
# node (at the moment we don't differentiate between cores and CPU). If
84
# you leave this commented out, Eucalyptus will use all available
85
# CPU/cores it can find.
88
# The size of the swap partition, in MB, for each instance started on the
89
# node (default is 512MB). If the maximum disk allowed for the instance
90
# is not big enough to accommodate the swap together with the root partition,
91
# then no swap is allocated. If there is extra room left, then an "ephemeral"
92
# partition will be created, available as /dev/sda3 inside the VM.
95
# Setting this to 1 disables the cleanup of instance files (root, kernel,
96
# ramdisk) for failed and terminated instances. This is not
97
# recommended for normal use, but it can be useful in debugging VM startup.
98
# MANUAL_INSTANCES_CLEANUP=0
101
# The following are options for image storage on the Node Controller
104
# This variable points to a directory which is used by the Node Controller
105
# to store images of running instances as well as local cached copies of
106
# images. The running images will be deleted after the instance is
107
# terminated, but the cached copies will persist, subject to LRU cache
108
# replacement and the NC_CACHE_SIZE size limit, below. So, this
109
# partition should be at least as big as the cache size (or the maximum
110
# space needed by all images, whichever is bigger) plus the maximum space
111
# needed by the maximum number of instances allowed on the node.
112
# This directory should be local to the Node Controller (as
113
# opposed to a NFS share) for performance reasons.
114
INSTANCE_PATH="not_configured"
116
# The maximum amount of disk space, in Megabytes, that Eucalyptus is
117
# allowed to use in the cache directory (INSTANCES_PATH/eucalyptus/cache).
118
# A generous size is recommended. Setting this to zero disables caching.
119
# NC_CACHE_SIZE=99999
122
# The following are networking options
125
# VNET_INTERFACE specifies the local physical ethernet interface that
126
# eucalyptus should use to manage the VM network. On the front-end,
127
# this should be set to the device that is attached to the same
128
# ethernet network as your nodes. On the nodes, this should be set to
129
# either the name of the bridge that has been set up by Xen (xenbr0,
130
# eth0, etc), or the physical ethernet device that is attached to the
131
# xen bridge (peth0, peth1, etc), depending on your xen configuration.
132
VNET_INTERFACE="peth0"
134
# (node setting only) VNET_BRIDGE should be set to the name of the
135
# bridge that xen has configured. This is typically named 'xenbr0,
136
# xenbr1, etc' on older Xen versions, and 'eth0, eth1, etc' on newer
137
# Xen versions. The command 'brctl show' will give you more
138
# information on your local bridge setup.
141
# This indicates where we have a dhcp server binary. We use it to provide
142
# the images with IPs: Eucalyptus provides its own configuration per
144
VNET_DHCPDAEMON="/usr/sbin/dhcpd3"
146
# Some systems have their DHCP daemon configured to run as a non-root
147
# user. If this is the case, set the name of that user here (by
148
# default, Eucalyptus will set up DHCPD configuration files and
149
# directories as owned by root).
152
# Following are example eucalyptus VM networking configurations.
153
# There are three modes to choose from (MANAGED, SYSTEM, or STATIC)
154
# and each has its own sub-options. The first mode (MANAGED)
155
# configured eucalyptus to fully manage the VM networks, and enables
156
# the ability to use security groups and dynamic public IP assignment.
157
# VNET_SUBNET should be set to an IP subnet that is free for
158
# eucalyptus to use (i.e. no other system connected to your network
159
# directly is configured with addresses from this subnet).
160
# VNET_NETMASK defines the size of the subnet. VNET_DNS should be set
161
# to a DNS server that your systems use (usually safe to use the same
162
# DNS that is configured on the front-end). VNET_ADDRSPERNET can be
163
# used to limit the number of instances that can be attached to each
164
# named security group simultaneously. Finally, VNET_PUBLICIPS should
165
# be set to any public IPs, that are currently unused, that can be
166
# dynamically assigned to VMs. Of these options, only VNET_PUBLICIPS
167
# can be left blank or undefined.
169
#VNET_SUBNET="192.168.0.0"
170
#VNET_NETMASK="255.255.0.0"
171
#VNET_DNS="your-dns-server-ip"
172
#VNET_ADDRSPERNET="32"
173
#VNET_PUBLICIPS="your-free-public-ip-1 your-free-public-ip-2 ..."
175
# If you would like eucalyptus to not manage the VM network at all,
176
# you can set VNET_MODE to SYSTEM. In this mode, VM interfaces are
177
# attached directly to your physical ethernet, at which point they
178
# will typically invoke a DHCP client to aquire an IP address. Use
179
# this mode if you wish to manage VM IPs yourself, or allow the VMs to
180
# pick up an IP from a non-eucalyptus managed DHCP server.
183
# If VNET_MODE is set to STATIC, you can manually configure a set of
184
# IP addresses that will be allocated to VMs at boot time in a first
185
# come, first served manner. VNET_SUBNET, VNET_NETMASK, and
186
# VNET_BROADCAST define your subnet (front-end must have an interface
187
# configured on this subnet). VNET_ROUTER defines the subnet's
188
# gateway. VNET_DNS is a nameserver address. It is usually safe to
189
# get these settings by examining your front-end network settings and
190
# duplicating them here. VNET_MACMAP is a list of mac address/IP
191
# address mappings that you would like to be allocated to VMs at run
192
# time (see example below for the format of this list).
194
#VNET_SUBNET="192.168.1.0"
195
#VNET_NETMASK="255.255.255.0"
196
#VNET_BROADCAST="192.168.1.255"
197
#VNET_ROUTER="192.168.1.1"
198
#VNET_DNS="192.168.1.1"
199
#VNET_MACMAP="AA:DD:11:CE:FF:ED=192.168.1.2 AA:DD:11:CE:FF:EE=192.168.1.3"