Previous page

Next page

Locate page in Contents

Print this page

Virtuozzo VE Configuration

Prior to VZAgent version 4.0.0, there was a single type that was used to hold the VPS configuration information. That type was ve_configType. This has changed significantly.

Currently, there's a base type called env_configType (as you can see, the name is different). When compared to the old-style ve_configType, the new type is missing all of the Virtuozzo VE-specific parameters such as a list of QoS parameters for example. These parameters are now defined in a subtype called venv_configType, which extends the base type. When creating or editing a Virtuozzo VE, or when retrieving the configuration information for an existing VE, the venv_configType must be used. This means that the XML element at the root of the config structure must have the attribute specifying the data type being used, as shown in the following example:

<ns3:virtual_config xsi:type="ns4:venv_configType">

<ns3:hostname>myhost</ns3:hostname>

<ns3:name>Mycomputer</ns3:name>

<ns3:offline_management>1</ns3:offline_management>

<ns3:on_boot>1</ns3:on_boot>

<ns3:os_template>

<ns3:version>20061020</ns3:version>

<ns3:name>redhat-as3-minimal</ns3:name>

...

</ns3:virtual_config>

The namespaces used in the example above must be defined in the XML message header. For example, the venv_configType type belongs to the http://www.swsoft.com/webservices/vza/4.0.0/vzatypes namespace. You must include this information in the message header before you can use the type. The following is an example of a namespace declaration:

<packet xmlns:ns2="http://www.swsoft.com/webservices/vza/4.0.0/vzatypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="4.0.0">

If you look closer at the new venv_configType structure and compare it to the old env_configType, you'll also see that some of the parameters are no longer there. For example, such parameters as class_id (Virtuozzo license class), the nbh-related parameters, vzcache, and others are now obsolete and therefore have been removed from the type definition. Many parameters, however, have not changed and are used exactly as they were in the previous VZAgent version.

Some other changes to the configuration structure will require an additional effort on your part when porting existing applications. Because of the new features that have been added to Virtuozzo networking, the network interfaces are now specified in a completely different manner. In the previous version, the network interface was defined using the single interface element which contained the interface name, the network class ID, and the bandwidth rate. Now, to specify the network interface information, you must use the new net_device element that has more parameters and is designed to handle network interfaces of different types, including the new Virtuozzo virtual networks. So, if your existing applications handle the network interface parameters, IP addresses, and other network-related settings, all of this will have to be reprogrammed. The changes are not drastic. Once you have a grasp on the basic building blocks, you will be able to make the necessary changes in minutes.

Please send us your feedback on this help page