-
Notifications
You must be signed in to change notification settings - Fork 14
VMAM configuration
Home > Installation and configuration manuals > VMAM configuration
##mySettings.py
configuration options (common)
###General parameters
FLAG | Values | Comments |
---|---|---|
ISLAND_NAME |
String | Island/testbed name. Shown on the upper right corner of the Web frontend |
VTAM_IP |
String | VM AM host domain name/IP |
VTAM_PORT |
String | WebUI and XMLRPC TCP port (default:8445) |
XMLRPC_USER |
String | XMLRPC interface username |
XMLRPC_PASS |
String | XMLRPC interface username's password |
###Root (Island Manager) account information
FLAG | Values | Comments |
---|---|---|
ROOT_USERNAME |
String | VM AM's root username |
ROOT_PASSWORD |
String | VM AM's root password |
ROOT_EMAIL |
String | VM AM's root email |
###Database parameters
FLAG | Values | Comments |
---|---|---|
DATABASE_USER |
String | MySQL username |
DATABASE_PASSWORD |
String | MySQL password |
DATABASE_HOST |
String | MySQL host (e.g. 127.0.0.1) |
DATABASE_NAME |
String | VM AM database name. |
The configuration of the Agent is performed during the installation. The only important parameter to take into account is the XMLRPC_PASSWORD
, which is set during installation, and will be required when adding Servers to the Virtualization Aggregate Manager, in next section.
Servers currently in order to create VMs MUST have one available range (pool) of MAC addresses and IPs. This, in a common configuration, means that at least one global IP and MAC range is needed to be defined. Take a look at next section for details.
Global vs. non-global ranges
By default servers use ranges tagged as global without having to do any kind of configuration to the server (subscription). In other words, if they are not subscribed to any range in particular, they will use all the global ranges to obtain MACs and IPs, in a random order.
However, if the servers subscribe to one or more ranges, regardless of its nature (whether if they are global or not), VMs will be created from addresses contained only in the pool of subscribed ranges (in a random manner).
The global flag, accordingly, should be disabled by those ranges that are particular to one server, and that do not apply to the rest of the servers (for instance a local testing server out of the addressing of the testbed). In general, servers should use global ranges for simplicty and since they do not need this mechanism.
Remember that subscription to MAC ranges does not imply nor has any effect to IPv4 subscription to ranges (they are completely independent).
Take this into account while defining the ranges and configure the servers.
Creating the ranges...
From the UI Dashboard click on Network Settings IPv4 ranges and Create range to define a new IPv4 range. The parameters of the IPv4 Range will be used to configure the VMs networking, this is, they will use the Mask, GW and DNSs of the range which provides the IP.
Create as many ranges as needed. For IPv4 ranges
- Range name: Name to identify the range.
- Global range: Global/Not Global flag.
- Range start Ip: Beggining of the range.
- Range end Ip: End of the range.
- Network mask: Network mask to apply over the IPs.
- Gw: IP address of the default gateway for the VMs.
- Dns1: In OFELIA installations it is important the first DNS to be the OFELIA internal DNS (currently 10.216.24.2).
- Dns2
For Ethernet Ranges, the only parameters are:
- Range name
- Global range
- Start Mac Address: In OFELIA installations MACs have to be in the range 02:0Y:XX:XX:XX:XX, where Y is the island identifier, as agreed in WP4. Refer to WP4 documentation for details.
- End Mac Address
When necessary, you can add Exceptions to this ranges.
After they have been set -and in the case you need specially addressing schema for a specific server- you can edit the server to subscribe it to specific ranges.
Create a server from the Add a server link in the Dashboard or in the Administrate Servers page.
- UUID: Automatically generated.
- Enabled: Uncheck if you want to add the server but not make it available for use.
- Name: Server name
- OS Type: Server's OS type
- OS Distribution: Server's OS type
- OS Version: Server's OS version
- Virtualization Technology: hypervisor running in the server
-
URL of the Server Agent: URL where the Agent daemon in the Server is listening. It should be
https://DOMAIN_NAME:PORT/
, default PORT is9229
.
The advertisement RSpec of VTAM returns a list of free VMs (or "slots") per server. This requires direct SSH connection to the virtualization servers where XEN and OXAD are installed.
Requirements:
-
Generate pair of public/private keys and copy private key (default file under
$OCF_PATH
: "/opt/ofelia/server_id_rsa"):ssh-keygen -t rsa # Interact with program to generate keys cp -p ~/id_rsa /opt/ofelia/server_id_rsa
-
Ensure proper configuration in file "vt_manager/src/python/vt_manager/communication/geni/v3/utils/server_stats.py" (location of the server's private key and SSH port of virtualization servers):
server_ssh_port = 7373 priv_key_path = "/opt/ofelia/server_id_rsa"
- Overview
- Experimenting
-
Administering
- Installing
- Upgrading
-
Configuration
- Components
- Infrastructure
- Troubleshooting
- Theme manager
-
Contributing
- Developing
-
Reporting
- Issue tracker and Roadmap