10
10
This manual page describes the
12
command which is used to configure Eucalyptus.
12
command which is used to configure Eucalyptus. There are few component to
13
a Eucalyptus installation: the cloud controller (CLC), walrus, one or more
14
cluster controller (CC), one storage controller (SC) per CC and node
17
CLC is the endpoint for the client tool, and contains the administrative
18
UI (reachable at https://localhost:8443 on the CLC machine).
20
walrus is the S3 compatible storage for Eucalyptus.
22
CC controls a number of NCs, provisions the network for VMs.
24
SC gives EBS functionality to a cluster.
26
NC interact with the local hypervisor to start/stop/control instances.
36
.BI --enable\ {walrus|sc|cloud}
38
Service to enable at the next start time. Needs to be run on the machine
39
which has the service to start.
42
.BI --disable\ {walrus|sc|cloud}
44
Disable services, preventing them to be started.
47
.BI --register-cluster\ <name>\ <hostname>
49
Register a CC with the CLC. To allow provisioning of instances, at least
50
one CC is needed on a running Eucalyptus installation.
51
This command needs to be ran on the CLC machine, and the
52
CC machine (possibly the same machine) needs to be reachable. The keys
53
needs to be transferred from the CLC to the CC machine to enable
54
secure operation, and ssh is used, so this command may ask for a password.
56
The user need to choose a name per CC.
59
.BI --deregister-cluster\ <name>\ <hostname>
64
.BI --register-sc\ <CC>\ <hostname>
66
Register a SC with the CLC. The SC is needed to provide EBS support to a
67
cluster logically resides with the CC.
68
This command needs to be ran on the CLC machine, and the
69
SC machine (possibly the same machine) needs to be reachable. The keys
70
needs to be transferred from the CLC to the SC machine to enable
71
secure operation, and ssh is used, so this command may ask for a password.
73
There has to be a CC already registered, since the SC works in conjunction
77
.BI --deregister-sc\ <hostname>
79
Deregister a running SC. You will need to register another SC to
80
have EBS functionality for a named cluster.
83
running this command will invalidate volumes and snapshots which this SC
87
.BI --register-walrus\ <hostname>
89
Register a walrus with the CLC. A walrus is needed for a running Eucalyptus
90
installation. This command needs to be ran on the CLC machine, and the
91
walrus machine (possibly the same machine) needs to be reachable. The keys
92
needs to be transferred from the CLC to the walrus machine to enable
93
secure operation, and ssh is used, so this command may ask for a password.
96
.BI --deregister-walrus\ <hostname>
98
Deregister a running walrus. You will need to register another walrus to
99
have a functional Eucalyptus installation.
102
running this command will invalidate the uploaded and running images,
103
kernels and ramdisk! So you (and all the users) will have to upload new
107
.BI --register-nodes\ host\ [host ...]
109
Register NCs with a CC. NC and CC should be on the same network. This
110
command needs to be run the CC which will controll the NCs. The keys
111
needs to be transferred from the CC to the NC for enable secure operation,
112
and ssh is used, so this command may ask for a password.
115
.BI --deregister-nodes\ host\ [host ...]
117
Intruct the CC to ignore specified NCs.
122
List registered walruses. The command needs to be run on the CLC.
127
List registered storage controllers. The command needs to be run on the CLC.
132
List registered cluster controllers. The command needs to be run on the CLC.
135
.BI --instances\ <path>
137
The NC needs disk space to keep a copy of the running instances. Some
138
copies are cached for faster startup time. This instruct the NC to user
142
better be an empty directory, since the NC needs to initialized it every
148
Print the version of Eucalyptus.
153
This command needs to run as root, before the first-time startup or
154
Eucalyptus. Eucalyptus runs as an unprivileged user (EUCA_USER in config)
155
but to interact with hypervisor and disk image, it will need to escalate
156
privilege. To do so we use a command (euca_rootwrap) and this command set
160
.BI --check\ {nc|cc|cloud|sc|walrus}
162
This command is mainly used on the startup script for the specific
163
component, since it checks that the environment is properly setup for the
164
component (mainly permission on directory needs to be right for the
168
.BI --cc-port\ <port>
171
.BI --nc-port\ <port>
174
.BI --user\ <euca_user>
180
.BI --dhcp_user\ <user>
182
These commands modify eucalyptus.conf so the changes will be reflected at
183
the restart of the services.
187
Copyright © 2009 Eucalyptus Systems Inc. License GPLv3+: GNU GPL
188
version 3 or later <http://gnu.org/licenses/gpl.html>. This is free
189
software: you are free to change and redistribute it. There is NO
190
WARRANTY, to the extent permitted by law.
22
Eucalyptus Systems Inc.
193
Eucalyptus Systems Inc. <http://www.eucalyptus.com>
added
removed
tools/euca_conf.1
