安裝桉樹所有的包之後，配clc、cc、nc端的xend.conf.sxp

# -*- sh -*- # # Xend configuration file. # # This example configuration is appropriate for an installation that # utilizes a bridged network configuration. Access to xend via http # is disabled. # Commented out entries show the default for that entry, unless otherwise # specified. #(logfile /var/log/xen/xend.log) #(loglevel DEBUG) (xend-http-server yes) (xend-unix-server yes) #(xend-tcp-xmlrpc-server no) #(xend-unix-xmlrpc-server yes) #(xend-relocation-server no) # The relocation server should be kept desactivated unless using a trusted # network, the domain virtual memory will be exchanged in raw form without # encryption of the communication. See also xend-relocation-hosts-allow option (xend-unix-path /var/lib/xend/xend-socket) # Port xend should use for the HTTP interface, if xend-http-server is set. #(xend-port 8000) # Port xend should use for the relocation interface, if xend-relocation-server # is set. #(xend-relocation-port 8002) # Address xend should listen on for HTTP connections, if xend-http-server is # set. # Specifying 'localhost' prevents remote connections. # Specifying the empty string '' (the default) allows all connections. #(xend-address '') (xend-address localhost) # Address xend should listen on for relocation-socket connections, if # xend-relocation-server is set. # Meaning and default as for xend-address above. #(xend-relocation-address '') # The hosts allowed to talk to the relocation port. If this is empty (the # default), then all connections are allowed (assuming that the connection # arrives on a port and interface on which we are listening; see # xend-relocation-port and xend-relocation-address above). Otherwise, this # should be a space-separated sequence of regular expressions. Any host with # a fully-qualified domain name or an IP address that matches one of these # regular expressions will be accepted. # # For example: # (xend-relocation-hosts-allow '^localhost$ ^.*/.example/.org$') # #(xend-relocation-hosts-allow '') (xend-relocation-hosts-allow '^localhost$ ^localhost//.localdomain$') # The limit (in kilobytes) on the size of the console buffer #(console-limit 1024) ## # To bridge network traffic, like this: # # dom0: fake eth0 -> vif0.0 -+ # | # bridge -> real eth0 -> the network # | # domU: fake eth0 -> vifN.0 -+ # # use # # (network-script network-bridge) # # Your default ethernet device is used as the outgoing interface, by default. # To use a different one (e.g. eth1) use # # (network-script 'network-bridge netdev=eth1') # # The bridge is named xenbr0, by default. To rename the bridge, use # # (network-script 'network-bridge bridge=<name>') # # It is possible to use the network-bridge script in more complicated # scenarios, such as having two outgoing interfaces, with two bridges, and # two fake interfaces per guest domain. To do things like this, write # yourself a wrapper script, and call network-bridge from it, as appropriate. # (network-script network-bridge) # The script used to control virtual interfaces. This can be overridden on a # per-vif basis when creating a domain or a configuring a new vif. The # vif-bridge script is designed for use with the network-bridge script, or # similar configurations. # # If you have overridden the bridge name using # (network-script 'network-bridge bridge=<name>') then you may wish to do the # same here. The bridge name can also be set when creating a domain or # configuring a new vif, but a value specified here would act as a default. # # If you are using only one bridge, the vif-bridge script will discover that, # so there is no need to specify it explicitly. # (vif-script vif-bridge) ## Use the following if network traffic is routed, as an alternative to the # settings for bridged networking given above. #(network-script network-route) #(vif-script vif-route) ## Use the following if network traffic is routed with NAT, as an alternative # to the settings for bridged networking given above. #(network-script network-nat) #(vif-script vif-nat) # Dom0 will balloon out when needed to free memory for domU. # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to. # If dom0-min-mem=0, dom0 will never balloon out. (dom0-min-mem 256) # In SMP system, dom0 will use dom0-cpus # of CPUS # If dom0-cpus = 0, dom0 will take all cpus available (dom0-cpus 0) # Whether to enable core-dumps when domains crash. #(enable-dump no) # The tool used for initiating virtual TPM migration #(external-migration-tool '') # The interface for VNC servers to listen on. Defaults # to 127.0.0.1 To restore old 'listen everywhere' behaviour # set this to 0.0.0.0 #(vnc-listen '127.0.0.1') # The default password for VNC console on HVM domain. # Empty string is no authentication. (vncpasswd '') # The default keymap to use for the VM's virtual keyboard # when not specified in VM's configuration (keymap 'en-us') # The VNC server can be told to negotiate a TLS session # to encryption all traffic, and provide x509 cert to # clients enalbing them to verify server identity. The # GTK-VNC widget, virt-viewer, virt-manager and VeNCrypt # all support the VNC extension for TLS used in QEMU. The # TightVNC/RealVNC/UltraVNC clients do not. # # To enable this create x509 certificates / keys in the # directory /etc/xen/vnc # # ca-cert.pem - The CA certificate # server-cert.pem - The Server certificate signed by the CA # server-key.pem - The server private key # # and then uncomment this next line # (vnc-tls 1) # # The certificate dir can be pointed elsewhere.. # # (vnc-x509-cert-dir /etc/xen/vnc) # # The server can be told to request & validate an x509 # certificate from the client. Only clients with a cert # signed by the trusted CA will be able to connect. This # is more secure the password auth alone. Passwd auth can # used at the same time if desired. To enable client cert # checking uncomment this: # # (vnc-x509-verify 1) # Allow probing of disk image file format. This is insecure! It lets # a malicious domU read any file in dom0. Applies only to fully # virtual domUs. Required for using formats other than raw. #(enable-image-format-probing no) # Number of seconds xend will wait for device creation #(device-create-timeout 100) # Strict checking when doing PCI passthrough; enabled by default #(pci-dev-assign-strict-check yes)

配置libvirt.conf

# Master libvirt daemon configuration file # # For further information consult http://libvirt.org/format.html # # NOTE: the tests/daemon-conf regression test script requires # that each "PARAMETER = VALUE" line in this file have the parameter # name just after a leading "#". ################################################################# # # Network connectivity controls # # Flag listening for secure TLS connections on the public TCP/IP port. # NB, must pass the --listen flag to the libvirtd process for this to # have any effect. # # It is necessary to setup a CA and issue server certificates before # using this capability. # # This is enabled by default, uncomment this to disable it #listen_tls = 0 # Listen for unencrypted TCP connections on the public TCP/IP port. # NB, must pass the --listen flag to the libvirtd process for this to # have any effect. # # Using the TCP socket requires SASL authentication by default. Only # SASL mechanisms which support data encryption are allowed. This is # DIGEST_MD5 and GSSAPI (Kerberos5) # # This is disabled by default, uncomment this to enable it. #listen_tcp = 1 # Override the port for accepting secure TLS connections # This can be a port number, or service name # #tls_port = "16514" # Override the port for accepting insecure TCP connections # This can be a port number, or service name # #tcp_port = "16509" # Override the default configuration which binds to all network # interfaces. This can be a numeric IPv4/6 address, or hostname # #listen_addr = "192.168.0.1" # Flag toggling mDNS advertizement of the libvirt service. # # Alternatively can disable for all services on a host by # stopping the Avahi daemon # # This is enabled by default, uncomment this to disable it #mdns_adv = 0 # Override the default mDNS advertizement name. This must be # unique on the immediate broadcast network. # # The default is "Virtualization Host HOSTNAME", where HOSTNAME # is subsituted for the short hostname of the machine (without domain) # #mdns_name = "Virtualization Host Joe Demo" ################################################################# # # UNIX socket access controls # # Set the UNIX domain socket group ownership. This can be used to # allow a 'trusted' set of users access to management capabilities # without becoming root. # # This is restricted to 'root' by default. unix_sock_group = "libvirt" # Set the UNIX socket permissions for the R/O socket. This is used # for monitoring VM status only # # Default allows any user. If setting group ownership may want to # restrict this to: unix_sock_ro_perms = "0777" # Set the UNIX socket permissions for the R/W socket. This is used # for full management of VMs # # Default allows only root. If PolicyKit is enabled on the socket, # the default will change to allow everyone (eg, 0777) # # If not using PolicyKit and setting group ownership for access # control then you may want to relax this to: unix_sock_rw_perms = "0770" # Set the name of the directory in which sockets will be found/created. #unix_sock_dir = "/var/run/libvirt" ################################################################# # # Authentication. # # - none: do not perform auth checks. If you can connect to the # socket you are allowed. This is suitable if there are # restrictions on connecting to the socket (eg, UNIX # socket permissions), or if there is a lower layer in # the network providing auth (eg, TLS/x509 certificates) # # - sasl: use SASL infrastructure. The actual auth scheme is then # controlled from /etc/sasl2/libvirt.conf. For the TCP # socket only GSSAPI & DIGEST-MD5 mechanisms will be used. # For non-TCP or TLS sockets, any scheme is allowed. # # - polkit: use PolicyKit to authenticate. This is only suitable # for use on the UNIX sockets. The default policy will # require a user to supply their own password to gain # full read/write access (aka sudo like), while anyone # is allowed read/only access. # # Set an authentication scheme for UNIX read-only sockets # By default socket permissions allow anyone to connect # # To restrict monitoring of domains you may wish to enable # an authentication mechanism here #auth_unix_ro = "none" # Set an authentication scheme for UNIX read-write sockets # By default socket permissions only allow root. If PolicyKit # support was compiled into libvirt, the default will be to # use 'polkit' auth. # # If the unix_sock_rw_perms are changed you may wish to enable # an authentication mechanism here #auth_unix_rw = "none" # Change the authentication scheme for TCP sockets. # # If you don't enable SASL, then all TCP traffic is cleartext. # Don't do this outside of a dev/test scenario. For real world # use, always enable SASL and use the GSSAPI or DIGEST-MD5 # mechanism in /etc/sasl2/libvirt.conf #auth_tcp = "sasl" # Change the authentication scheme for TLS sockets. # # TLS sockets already have encryption provided by the TLS # layer, and limited authentication is done by certificates # # It is possible to make use of any SASL authentication # mechanism as well, by using 'sasl' for this option #auth_tls = "none" ################################################################# # # TLS x509 certificate configuration # # Override the default server key file path # #key_file = "/etc/pki/libvirt/private/serverkey.pem" # Override the default server certificate file path # #cert_file = "/etc/pki/libvirt/servercert.pem" # Override the default CA certificate path # #ca_file = "/etc/pki/CA/cacert.pem" # Specify a certificate revocation list. # # Defaults to not using a CRL, uncomment to enable it #crl_file = "/etc/pki/CA/crl.pem" ################################################################# # # Authorization controls # # Flag to disable verification of client certificates # # Client certificate verification is the primary authentication mechanism. # Any client which does not present a certificate signed by the CA # will be rejected. # # Default is to always verify. Uncommenting this will disable # verification - make sure an IP whitelist is set #tls_no_verify_certificate = 1 # A whitelist of allowed x509 Distinguished Names # This list may contain wildcards such as # # "C=GB,ST=London,L=London,O=Red Hat,CN=*" # # See the POSIX fnmatch function for the format of the wildcards. # # NB If this is an empty list, no client can connect, so comment out # entirely rather than using empty list to disable these checks # # By default, no DN's are checked #tls_allowed_dn_list = ["DN1", "DN2"] # A whitelist of allowed SASL usernames. The format for usernames # depends on the SASL authentication mechanism. Kerberos usernames # look like username@REALM # # This list may contain wildcards such as # # "*@EXAMPLE.COM" # # See the POSIX fnmatch function for the format of the wildcards. # # NB If this is an empty list, no client can connect, so comment out # entirely rather than using empty list to disable these checks # # By default, no Username's are checked #sasl_allowed_username_list = ["joe@EXAMPLE.COM", "fred@EXAMPLE.COM" ] ################################################################# # # Processing controls # # The maximum number of concurrent client connections to allow # over all sockets combined. #max_clients = 20 # The minimum limit sets the number of workers to start up # initially. If the number of active clients exceeds this, # then more threads are spawned, upto max_workers limit. # Typically you'd want max_workers to equal maximum number # of clients allowed #min_workers = 5 #max_workers = 20 # Total global limit on concurrent RPC calls. Should be # at least as large as max_workers. Beyond this, RPC requests # will be read into memory and queued. This directly impact # memory usage, currently each request requires 256 KB of # memory. So by default upto 5 MB of memory is used # # XXX this isn't actually enforced yet, only the per-client # limit is used so far #max_requests = 20 # Limit on concurrent requests from a single client # connection. To avoid one client monopolizing the server # this should be a small fraction of the global max_requests # and max_workers parameter #max_client_requests = 5 ################################################################# # # Logging controls # # Logging level: 0 none, 4 errors, 3 warnings, 2 informations, 1 debug # basically 1 will log everything possible #log_level = 3 # Logging filters: # A filter allows to select a different logging level for a given category # of logs # The format for a filter is: # x:name # where name is a match string e.g. remote or qemu # the x prefix is the minimal level where matching messages should be logged # 1: DEBUG # 2: INFO # 3: WARNING # 4: ERROR # # Multiple filter can be defined in a single @filters, they just need to be # separated by spaces. # # e.g: # log_filters="3:remote 4:event" # to only get warning or errors from the remote layer and only errors from # the event layer. # Logging outputs: # An output is one of the places to save logging informations # The format for an output can be: # x:stderr # output goes to stderr # x:syslog:name # use syslog for the output and use the given name as the ident # x:file:file_path # output to a file, with the given filepath # In all case the x prefix is the minimal level, acting as a filter # 0: everything # 1: DEBUG # 2: INFO # 3: WARNING # 4: ERROR # # Multiple output can be defined , they just need to be separated by spaces. # e.g.: # log_outputs="3:syslog:libvirtd" # to log all warnings and errors to syslog under the libvirtd ident

配置前段clc、cc端的eucalyptus.conf

# # Eucalyptus configuration. #### # These are to instruct the init.d script on what to start. #### # This variable points to where eucalyptus has been installed. EUCALYPTUS="/" # This is the username that you would like eucalyptus to run as EUCA_USER="eucalyptus" # Uncomment this field if you do not plan on using the EBS (elastic # block store) functionality of Eucalyptus # DISABLE_EBS="Y" # EBS (elastic block store) functionality is implemented using iSCSI, # a layer-3 technology, unless iSCSI is disabled by setting this option to # "Y" or by commenting out the option, in which case EBS is implemented # using AOE (ATA-over-Ethernet), a layer-2 technology. DISABLE_ISCSI="N" # Uncomment this field if you do not plan on using the dynamic DNS # functionality of Eucalyptus DISABLE_DNS="Y" # This variable controls whether or not layer 2 tunnels are set up # between clusters in multi-cluster mode. # DISABLE_TUNNELING="N" # This variable controls whether or not layer 2 tunnels are set up # between clusters in multi-cluster mode. If you are running two CCs # on the same broadcast network (ethernet), tunneling should be # disabled. # DISABLE_TUNNELING="N" # This variable controls whether ws-security is enabled between # eucalyptus components. The default settings provide secure # connections between the Cloud, Cluster, and Node Controllers and we # recommend that this feature remains enabled. If you wish to disable security, # you must change this variable to "N" and manually configure the # services.xml for both Cluster and Node Controllers (see documentation # for more details). ENABLE_WS_SECURITY="Y" # This variable is used to pass extra options to eucalyptus-cloud # (such as heap size or JVM flags). CLOUD_OPTS="" # This variable controls the level of logging output that appears in # various eucalyptus log files. The options are, in descending order # of verbosity, 'DEBUG, INFO, WARN, ERROR, and # FATAL'. The default is DEBUG (everything). LOGLEVEL="DEBUG" #### # These following are Cluster Controller configuration options. #### # This is the port the Cluster Controller will be listening on. CC_PORT="8774" # This option configures the Cluster Controller's scheduling policy. # Currently, this option can be set to GREEDY (first node that is # found that can run the VM will be chosen), ROUNDROBIN (nodes are # selected one after another until one is found that can run the VM), # or POWERSAVE (nodes are put to sleep when they are not running VMs, # and reawakened when new resources are required. VMs will be placed # on the first awake machine, followed by machines that are asleep). SCHEDPOLICY="ROUNDROBIN" # Powersave options. POWER_IDLETHRESH is the number of seconds that a # node can remain idle (i.e. no running VMs) before a powerdown is # attempted. POWER_WAKETHRESH is the number of seconds that # Eucalyptus should wait after attempting a node wake-up before it # will consider the node actually down (and not waking up). POWER_IDLETHRESH="300" POWER_WAKETHRESH="300" # The list of Node Controllers the Cluster Controller will communicate with. # # If you are running Rocks, you can run "rocks list host" to # find out the list of machines available to you (in our case we are # interested in the VM Container kind). NODES="" # The name of the Node Controller service. Change this if you want # to plug in your own Node Controller service. NC_SERVICE="axis2/services/EucalyptusNC" #### # The following are Node Controller configuration options. #### # This is the port the Node Controller will be listening on. NC_PORT="8775" # The hypervisor that the Node Controller will interact with in order # to manage virtual machines. Currently, supported values are 'kvm' # and 'xen'. HYPERVISOR="xen" # The following three KVM-specific options determine whether the # hypervisor uses Virtio for specific types of I/O with the VM. # (To use VirtIO, the VM must have the appropriate drivers installed.) # If "1", use Virtio for EBS (elastic block store) volumes USE_VIRTIO_DISK="0" # If "1", use Virtio for the root file system disk USE_VIRTIO_ROOT="0" # If "1", use Virtio for the network card USE_VIRTIO_NET="0" # The maximum amount of memory, in Megabytes, that Eucalyptus is allowed to # allocate to instances on the node: if you leave this commented out or set # to 0, Eucalyptus may use all available memory for instances. # MAX_MEM=2048 # The maximum number of CPUs or cores Eucalyptus is allowed to allocate to # instances on the node (at the moment we don't differentiate between cores # and CPUs). If you leave this commented out, Eucalyptus will use all # available CPUs or cores it can find. If this value exceeds the number of # physical cores or CPUs, multiple instances may be sharing a core or CPU. # MAX_CORES="2" # The maximum amount of disk, in Gigabytes, that Eucalyptus is allowed to # allocate to instances on the node (this does not include the disk used # for the cache, which can be limited using NC_CACHE_SIZE). If this is # commented out or set to 0, Eucalyptus may use all available disk space on # the partition containing the INSTANCES directory. # MAX_DISK="100" # The size of the swap partition, in MB, for each instance started on the # node (default is 512MB). If the maximum disk allowed for the instance # is not big enough to accommodate the swap together with the root partition, # then no swap is allocated. If there is extra room left, then an "ephemeral" # partition will be created, available as /dev/sda3 inside the VM. # SWAP_SIZE=512 # Set the number of 'disk intensive operations' that are allowed to # take place in parallel on this machine. If this value is set too # high, we run the risk of driving the load on the machine too high # when multiple instances are started on this single node. The # default is 4. # CONCURRENT_DISK_OPS=4 # Setting this to 1 disables the cleanup of instance files (root, kernel, # ramdisk) for failed and terminated instances. This is not # recommended for normal use, but it can be useful in debugging VM startup. # MANUAL_INSTANCES_CLEANUP=0 #### # The following are options for image storage on the Node Controller #### # This variable points to a directory which is used by the Node Controller # to store images of running instances as well as local cached copies of # images. The running images will be deleted after the instance is # terminated, but the cached copies will persist, subject to LRU cache # replacement and the NC_CACHE_SIZE size limit, below. So, this # partition should be at least as big as the cache size (or the maximum # space needed by all images, whichever is bigger) plus the maximum space # needed by the maximum number of instances allowed on the node. # This directory should be local to the Node Controller (as # opposed to a NFS share) for performance reasons. INSTANCE_PATH="/usr/local/eucalyptus/" # The maximum amount of disk space, in Megabytes, that Eucalyptus is # allowed to use in the cache directory (INSTANCES_PATH/eucalyptus/cache). # A generous size is recommended. Setting this to zero disables caching. # NC_CACHE_SIZE=99999 #### # The following are networking options #### # The 2 variable VNET_PRIVINTERFACE and VNET_PUBINTERFACE specify the # local physical ethernet interfaces that eucalyptus should use to manage # the VM network. On the front-end, VNET_PRIVINTERFACE should be set to # the device that is attached to the same ethernet network as your nodes. # - VNET_PUBINTERFACE should be set to the device which is connected to # the 'public' network. If you have only one interface, these should # be set to the same value. On the nodes, both should be set to # either the name of the bridge that has been set up by Xen (xenbr0, # eth0, etc), or the physical ethernet device that is attached to the # xen bridge (peth0, peth1, etc), depending on your xen configuration. VNET_PUBINTERFACE="xenbr0" VNET_PRIVINTERFACE="xenbr0" # (node setting only) VNET_BRIDGE should be set to the name of the # bridge that xen has configured. This is typically named 'xenbr0, # xenbr1, etc' on older Xen versions, and 'eth0, eth1, etc' on newer # Xen versions. The command 'brctl show' will give you more # information on your local bridge setup. VNET_BRIDGE="xenbr0" # This indicates where we have a dhcp server binary. We use it to provide # the images with IPs: Eucalyptus provides its own configuration per # instance. VNET_DHCPDAEMON="/usr/sbin/dhcpd" # Some systems have their DHCP daemon configured to run as a non-root # user. If this is the case, set the name of that user here (by # default, Eucalyptus will set up DHCPD configuration files and # directories as owned by root). #VNET_DHCPUSER="root" # Following are example eucalyptus VM networking configurations. # There are four modes to choose from (MANAGED, MANAGED-NOVLAN, # SYSTEM, or STATIC) and each has its own sub-options. The first # modes (MANAGED, MANAGED-NOVLAN) configure eucalyptus to fully manage # the VM networks, and enables the ability to use security groups and # dynamic public IP assignment (with and without vlan tagging of # security group networks, respectively). VNET_SUBNET should be set # to an IP subnet that is free for eucalyptus to use (i.e. no other # system connected to your network directly is configured with # addresses from this subnet). VNET_NETMASK defines the size of the # subnet. VNET_DNS should be set to a DNS server that your systems # use (usually safe to use the same DNS that is configured on the # front-end). VNET_ADDRSPERNET can be used to limit the number of # instances that can be attached to each named security group # simultaneously. Finally, VNET_PUBLICIPS should be set to any public # IPs, that are currently unused, that can be dynamically assigned to # VMs. Of these options, only VNET_PUBLICIPS can be left blank or # undefined. If you are running in multi-cluster mode (more than one # CC), you should uncomment VNET_LOCALIP and set it to the local IP of # the CC that is accessible by all other CCs in the system. If # VNET_LOCALIP is unset, the CC will try to determine the list of all # IPs currently assigned to the machine at CC run time. If your CC # and CLC are on different machines, uncomment VNET_CLOUDIP and set it # to your cloud-contoller's IP address (must be an address that can be # reached by the CC). VNET_MODE="MANAGED" #VNET_SUBNET="192.168.0.0" #VNET_NETMASK="255.255.0.0" #VNET_DNS="your-dns-server-ip" #VNET_ADDRSPERNET="32" #VNET_PUBLICIPS="your-free-public-ip-1 your-free-public-ip-2 ..." #VNET_LOCALIP="your-public-interface's-ip" #VNET_CLOUDIP="your-cloud-controller's-ip" # If you would like eucalyptus to not manage the VM network at all, # you can set VNET_MODE to SYSTEM. In this mode, VM interfaces are # attached directly to your physical ethernet, at which point they # will typically invoke a DHCP client to aquire an IP address. Use # this mode if you wish to manage VM IPs yourself, or allow the VMs to # pick up an IP from a non-eucalyptus managed DHCP server. #VNET_MODE="SYSTEM" # If VNET_MODE is set to STATIC, you can manually configure a set of # IP addresses that will be allocated to VMs at boot time in a first # come, first served manner. VNET_SUBNET, VNET_NETMASK, and # VNET_BROADCAST define your subnet (front-end must have an interface # configured on this subnet). VNET_ROUTER defines the subnet's # gateway. VNET_DNS is a nameserver address. It is usually safe to # get these settings by examining your front-end network settings and # duplicating them here. VNET_MACMAP is a list of mac address/IP # address mappings that you would like to be allocated to VMs at run # time (see example below for the format of this list). #VNET_MODE="STATIC" #VNET_SUBNET="192.168.1.0" #VNET_NETMASK="255.255.255.0" #VNET_BROADCAST="192.168.1.255" #VNET_ROUTER="192.168.1.1" #VNET_DNS="192.168.1.1" #VNET_MACMAP="AA:DD:11:CE:FF:ED=192.168.1.2 AA:DD:11:CE:FF:EE=192.168.1.3"

配置nc端的eucalyptus.conf

# # Eucalyptus configuration. #### # These are to instruct the init.d script on what to start. #### # This variable points to where eucalyptus has been installed. EUCALYPTUS="/" # This is the username that you would like eucalyptus to run as EUCA_USER="eucalyptus" # Uncomment this field if you do not plan on using the EBS (elastic # block store) functionality of Eucalyptus # DISABLE_EBS="Y" # EBS (elastic block store) functionality is implemented using iSCSI, # a layer-3 technology, unless iSCSI is disabled by setting this option to # "Y" or by commenting out the option, in which case EBS is implemented # using AOE (ATA-over-Ethernet), a layer-2 technology. DISABLE_ISCSI="N" # Uncomment this field if you do not plan on using the dynamic DNS # functionality of Eucalyptus DISABLE_DNS="Y" # This variable controls whether or not layer 2 tunnels are set up # between clusters in multi-cluster mode. # DISABLE_TUNNELING="N" # This variable controls whether or not layer 2 tunnels are set up # between clusters in multi-cluster mode. If you are running two CCs # on the same broadcast network (ethernet), tunneling should be # disabled. # DISABLE_TUNNELING="N" # This variable controls whether ws-security is enabled between # eucalyptus components. The default settings provide secure # connections between the Cloud, Cluster, and Node Controllers and we # recommend that this feature remains enabled. If you wish to disable security, # you must change this variable to "N" and manually configure the # services.xml for both Cluster and Node Controllers (see documentation # for more details). ENABLE_WS_SECURITY="Y" # This variable is used to pass extra options to eucalyptus-cloud # (such as heap size or JVM flags). CLOUD_OPTS="" # This variable controls the level of logging output that appears in # various eucalyptus log files. The options are, in descending order # of verbosity, 'DEBUG, INFO, WARN, ERROR, and # FATAL'. The default is DEBUG (everything). LOGLEVEL="DEBUG" #### # These following are Cluster Controller configuration options. #### # This is the port the Cluster Controller will be listening on. CC_PORT="8774" # This option configures the Cluster Controller's scheduling policy. # Currently, this option can be set to GREEDY (first node that is # found that can run the VM will be chosen), ROUNDROBIN (nodes are # selected one after another until one is found that can run the VM), # or POWERSAVE (nodes are put to sleep when they are not running VMs, # and reawakened when new resources are required. VMs will be placed # on the first awake machine, followed by machines that are asleep). SCHEDPOLICY="ROUNDROBIN" # Powersave options. POWER_IDLETHRESH is the number of seconds that a # node can remain idle (i.e. no running VMs) before a powerdown is # attempted. POWER_WAKETHRESH is the number of seconds that # Eucalyptus should wait after attempting a node wake-up before it # will consider the node actually down (and not waking up). POWER_IDLETHRESH="300" POWER_WAKETHRESH="300" # The list of Node Controllers the Cluster Controller will communicate with. # # If you are running Rocks, you can run "rocks list host" to # find out the list of machines available to you (in our case we are # interested in the VM Container kind). NODES="" # The name of the Node Controller service. Change this if you want # to plug in your own Node Controller service. NC_SERVICE="axis2/services/EucalyptusNC" #### # The following are Node Controller configuration options. #### # This is the port the Node Controller will be listening on. NC_PORT="8775" # The hypervisor that the Node Controller will interact with in order # to manage virtual machines. Currently, supported values are 'kvm' # and 'xen'. HYPERVISOR="xen" # The following three KVM-specific options determine whether the # hypervisor uses Virtio for specific types of I/O with the VM. # (To use VirtIO, the VM must have the appropriate drivers installed.) # If "1", use Virtio for EBS (elastic block store) volumes USE_VIRTIO_DISK="0" # If "1", use Virtio for the root file system disk USE_VIRTIO_ROOT="0" # If "1", use Virtio for the network card USE_VIRTIO_NET="0" # The maximum amount of memory, in Megabytes, that Eucalyptus is allowed to # allocate to instances on the node: if you leave this commented out or set # to 0, Eucalyptus may use all available memory for instances. # MAX_MEM=2048 # The maximum number of CPUs or cores Eucalyptus is allowed to allocate to # instances on the node (at the moment we don't differentiate between cores # and CPUs). If you leave this commented out, Eucalyptus will use all # available CPUs or cores it can find. If this value exceeds the number of # physical cores or CPUs, multiple instances may be sharing a core or CPU. # MAX_CORES="2" # The maximum amount of disk, in Gigabytes, that Eucalyptus is allowed to # allocate to instances on the node (this does not include the disk used # for the cache, which can be limited using NC_CACHE_SIZE). If this is # commented out or set to 0, Eucalyptus may use all available disk space on # the partition containing the INSTANCES directory. # MAX_DISK="100" # The size of the swap partition, in MB, for each instance started on the # node (default is 512MB). If the maximum disk allowed for the instance # is not big enough to accommodate the swap together with the root partition, # then no swap is allocated. If there is extra room left, then an "ephemeral" # partition will be created, available as /dev/sda3 inside the VM. # SWAP_SIZE=512 # Set the number of 'disk intensive operations' that are allowed to # take place in parallel on this machine. If this value is set too # high, we run the risk of driving the load on the machine too high # when multiple instances are started on this single node. The # default is 4. # CONCURRENT_DISK_OPS=4 # Setting this to 1 disables the cleanup of instance files (root, kernel, # ramdisk) for failed and terminated instances. This is not # recommended for normal use, but it can be useful in debugging VM startup. # MANUAL_INSTANCES_CLEANUP=0 #### # The following are options for image storage on the Node Controller #### # This variable points to a directory which is used by the Node Controller # to store images of running instances as well as local cached copies of # images. The running images will be deleted after the instance is # terminated, but the cached copies will persist, subject to LRU cache # replacement and the NC_CACHE_SIZE size limit, below. So, this # partition should be at least as big as the cache size (or the maximum # space needed by all images, whichever is bigger) plus the maximum space # needed by the maximum number of instances allowed on the node. # This directory should be local to the Node Controller (as # opposed to a NFS share) for performance reasons. INSTANCE_PATH="/usr/local/eucalyptus/" # The maximum amount of disk space, in Megabytes, that Eucalyptus is # allowed to use in the cache directory (INSTANCES_PATH/eucalyptus/cache). # A generous size is recommended. Setting this to zero disables caching. # NC_CACHE_SIZE=99999 #### # The following are networking options #### # The 2 variable VNET_PRIVINTERFACE and VNET_PUBINTERFACE specify the # local physical ethernet interfaces that eucalyptus should use to manage # the VM network. On the front-end, VNET_PRIVINTERFACE should be set to # the device that is attached to the same ethernet network as your nodes. # - VNET_PUBINTERFACE should be set to the device which is connected to # the 'public' network. If you have only one interface, these should # be set to the same value. On the nodes, both should be set to # either the name of the bridge that has been set up by Xen (xenbr0, # eth0, etc), or the physical ethernet device that is attached to the # xen bridge (peth0, peth1, etc), depending on your xen configuration. VNET_PUBINTERFACE="xenbr0" VNET_PRIVINTERFACE="xenbr0" # (node setting only) VNET_BRIDGE should be set to the name of the # bridge that xen has configured. This is typically named 'xenbr0, # xenbr1, etc' on older Xen versions, and 'eth0, eth1, etc' on newer # Xen versions. The command 'brctl show' will give you more # information on your local bridge setup. VNET_BRIDGE="xenbr0" # This indicates where we have a dhcp server binary. We use it to provide # the images with IPs: Eucalyptus provides its own configuration per # instance. VNET_DHCPDAEMON="/usr/sbin/dhcpd" # Some systems have their DHCP daemon configured to run as a non-root # user. If this is the case, set the name of that user here (by # default, Eucalyptus will set up DHCPD configuration files and # directories as owned by root). #VNET_DHCPUSER="root" # Following are example eucalyptus VM networking configurations. # There are four modes to choose from (MANAGED, MANAGED-NOVLAN, # SYSTEM, or STATIC) and each has its own sub-options. The first # modes (MANAGED, MANAGED-NOVLAN) configure eucalyptus to fully manage # the VM networks, and enables the ability to use security groups and # dynamic public IP assignment (with and without vlan tagging of # security group networks, respectively). VNET_SUBNET should be set # to an IP subnet that is free for eucalyptus to use (i.e. no other # system connected to your network directly is configured with # addresses from this subnet). VNET_NETMASK defines the size of the # subnet. VNET_DNS should be set to a DNS server that your systems # use (usually safe to use the same DNS that is configured on the # front-end). VNET_ADDRSPERNET can be used to limit the number of # instances that can be attached to each named security group # simultaneously. Finally, VNET_PUBLICIPS should be set to any public # IPs, that are currently unused, that can be dynamically assigned to # VMs. Of these options, only VNET_PUBLICIPS can be left blank or # undefined. If you are running in multi-cluster mode (more than one # CC), you should uncomment VNET_LOCALIP and set it to the local IP of # the CC that is accessible by all other CCs in the system. If # VNET_LOCALIP is unset, the CC will try to determine the list of all # IPs currently assigned to the machine at CC run time. If your CC # and CLC are on different machines, uncomment VNET_CLOUDIP and set it # to your cloud-contoller's IP address (must be an address that can be # reached by the CC). VNET_MODE="MANAGED" #VNET_SUBNET="192.168.0.0" #VNET_NETMASK="255.255.0.0" #VNET_DNS="your-dns-server-ip" #VNET_ADDRSPERNET="32" #VNET_PUBLICIPS="your-free-public-ip-1 your-free-public-ip-2 ..." #VNET_LOCALIP="your-public-interface's-ip" #VNET_CLOUDIP="your-cloud-controller's-ip" # If you would like eucalyptus to not manage the VM network at all, # you can set VNET_MODE to SYSTEM. In this mode, VM interfaces are # attached directly to your physical ethernet, at which point they # will typically invoke a DHCP client to aquire an IP address. Use # this mode if you wish to manage VM IPs yourself, or allow the VMs to # pick up an IP from a non-eucalyptus managed DHCP server. #VNET_MODE="SYSTEM" # If VNET_MODE is set to STATIC, you can manually configure a set of # IP addresses that will be allocated to VMs at boot time in a first # come, first served manner. VNET_SUBNET, VNET_NETMASK, and # VNET_BROADCAST define your subnet (front-end must have an interface # configured on this subnet). VNET_ROUTER defines the subnet's # gateway. VNET_DNS is a nameserver address. It is usually safe to # get these settings by examining your front-end network settings and # duplicating them here. VNET_MACMAP is a list of mac address/IP # address mappings that you would like to be allocated to VMs at run # time (see example below for the format of this list). #VNET_MODE="STATIC" #VNET_SUBNET="192.168.1.0" #VNET_NETMASK="255.255.255.0" #VNET_BROADCAST="192.168.1.255" #VNET_ROUTER="192.168.1.1" #VNET_DNS="192.168.1.1" #VNET_MACMAP="AA:DD:11:CE:FF:ED=192.168.1.2 AA:DD:11:CE:FF:EE=192.168.1.3"

配置完畢，clc和cc端啟動服務

/etc/init.d/eucalyptus-cloud start

/etc/init.d/eucalyptus-cc start

註冊walrus、cluster和node

先註冊walrus：

[root@localhost nfs-euca]# euca_conf --register-walrus 192.168.1.171 Adding WALRUS host 192.168.1.171 Trying rsync to sync keys with "192.168.1.171"...The authenticity of host '192.168.1.171 (192.168.1.171)' can't be established. RSA key fingerprint is 4f:27:e4:82:dc:57:38:17:81:89:b6:69:d3:11:04:e1. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.1.171' (RSA) to the list of known hosts. Address 192.168.1.171 maps to localhost, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! root@192.168.1.171's password: done. SUCCESS: new walrus on host '192.168.1.171' successfully registered.

註冊叢集：

[root@localhost nfs-euca]# euca_conf --register-cluster CloudTest 192.168.1.171 Trying rsync to sync keys with "192.168.1.171"...Address 192.168.1.171 maps to localhost, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! root@192.168.1.171's password: done. SUCCESS: new cluster 'CloudTest' on host '192.168.1.171' successfully registered

註冊節點：

[root@localhost nfs-euca]# euca_conf --register-nodes 192.168.1.165 INFO: We expect all nodes to have eucalyptus installed in / for key synchronization. Trying rsync to sync keys with "192.168.1.165"...root@192.168.1.165's password: done.

註冊完可以檢視註冊資訊：

[root@localhost xiaonan]# euca_conf --list-walruses registered walruses:free walrus 192.168.1.171 [root@localhost xiaonan]# euca_conf --list-clusters registered clusters: CloudTest 192.168.1.171 [root@localhost xiaonan]# euca_conf --list-nodes registered nodes: 192.168.1.165 CloudTest

登入https://192.168.1.171:8443之後就會開啟eucalyptus頁面，使用者名稱admin密碼admin登入進去，在Credentials->Download Credentials之後，會下載一個euca2-admin-x509.zip的壓縮包，解壓縮之後，先匯入環境變數：

source eucarc

然後就嘗試上傳、更新和註冊核心了：

上傳核心：

[root@localhost registerImg]# euca-bundle-image -i vmlinuz-2.6.18-194.el5xen --kernel true Checking image Tarring image Encrypting image Splitting image... Part: vmlinuz-2.6.18-194.el5xen.part.0 Generating manifest /tmp/vmlinuz-2.6.18-194.el5xen.manifest.xml

更新核心：

[root@localhost registerImg]# euca-upload-bundle -b xiaonan_Test -m /tmp/vmlinuz-2.6.18-194.el5xen.manifest.xml Checking bucket: xiaonan_Test Creating bucket: xiaonan_Test Uploading manifest file Uploading part: vmlinuz-2.6.18-194.el5xen.part.0 Uploaded image as xiaonan_Test/vmlinuz-2.6.18-194.el5xen.manifest.xml

感覺自己機器速度變得異常慢，eucalyptus-clou程序佔用了cpu為56%，無法再繼續下去了，於是檢視下當前節點情況吧：

[root@localhost registerImg]# euca-describe-availability-zones verbose AVAILABILITYZONE CloudTest 192.168.1.171 AVAILABILITYZONE |- vm types free / max cpu ram disk AVAILABILITYZONE |- m1.small 0000 / 0000 1 128 2 AVAILABILITYZONE |- c1.medium 0000 / 0000 1 256 5 AVAILABILITYZONE |- m1.large 0000 / 0000 2 512 10 AVAILABILITYZONE |- m1.xlarge 0000 / 0000 2 1024 20 AVAILABILITYZONE |- c1.xlarge 0000 / 0000 4 2048 20 [root@localhost registerImg]# euca_conf --list-nodes

明顯不對啊，貌似節點都沒有註冊成功哦，都是0000.為什麼euca_conf --list-nodes時註冊資訊是有的，而使用euca-describe-availability-zones檢視就沒有節點呢，5555555555崩潰！只能再檢查相關配置項！