Subsections
This section is used to specify OpenNebula parameters,
necessary when using Haizea as an OpenNebula scheduling backend.
This section is required when:
- Option mode (in section [general])
is set to opennebula
- Valid values:
- Any string
- Required:
- Yes
- Description:
- Host where OpenNebula is running.
Typically, OpenNebula and Haizea will be installed
on the same host, so the following option should be
set to 'localhost'. If they're on different hosts,
make sure you modify this option accordingly.
- Valid values:
- An integer number
- Required:
- No
(default is 2633)
- Description:
- TCP port of OpenNebula's XML RPC server
- Valid values:
- True or False
- Required:
- No
- Description:
- This option is useful for testing and running experiments.
If set to True, Haizea will stop when there are no more leases
to process (which allows you to tun Haizea and OpenNebula unattended,
and count on it stopping when there are no more leases to process).
For now, this only makes sense if you're seeding Haizea with requests from
the start (otherwise, it will start and immediately stop).
- Valid values:
- True or False
- Required:
- No
- Description:
- This option is useful for testing.
If set to True, Haizea will fast-forward through time (note that this is
different that using the simulated clock, which has to be used with a tracefile;
with an Haizea/OpenNebula dry run, you will have to seed OpenNebula with requests
before starting Haizea). You will generally want to set stop-when-no-more-leases
when doing a dry-run.
IMPORTANT: Haizea will still send out enactment commands to OpenNebula. Make
sure you replace onevm with a dummy command that does nothing (or that reacts
in some way you want to test; e.g., by emulating a deployment failure, etc.)
Borja Sotomayor
2009-12-17