Mirantis fuel which is a member of the OpenStack Big Tent, has already become one of the leading installers for OpenStack and provides that a pluggable architecture you can add new capabilities to your environments. XenServer fuel plugin aims to use the XenServer open source hypervisor (versions greater than 6.5 SP1) supportable to allow as Compute provider with Mirantis OpenStack in a commercial manner.
to be more precise, we want to achieve the following main objectives: adapt the user interface
- in the installation
- install the required plug-ins and other conditions
- routing control networks access to dom0
- update the XenServer OpenStack integration
- Replace give test image
Customizing the user interface
Mirantis fuel is highly GUI-based. Written as a single application web page in JavaScript, the user can easily select OpenStack release, hypervisor type, network or storage backends and additional OpenStack services like Murano or Sahara, by an assistant. More detailed specific settings can be configured in a list of categorized Settings tabs. You can even drag and drop the network interfaces. Generally, in fuel UI configuration has been redesigned, it is to make it truly user friendly.
Moreover Mirantis fuel even provides a control plane in order to customize the user interface. As long as you follow a scheme as openstack.yaml, users can define their own OpenStack release. In Mirantis 8.0 users can also define their own resource type components.yaml. a hypervisor type "XenServer" is shot in the picture above defined. And if you select it, the following wizards and the setting tabs will be displayed based on your choice and the incompatible list described in components.yaml. This feature is very useful as OpenStack setup is complicated and there are many restrictions. With the non-compliant list, users are prevented from making the wrong decisions.
restrictions provides addition, Mirantis also provides a path input in the web interface to add. In environment_config.yaml we define text fields for XenServer asking credentials, because we need to XenServer hosts ssh patches apply later, is presented in the in the web interface to the user.
configuration XenServer
For now in Mirantis fuel, there are only three built-in hypervisor types that are QEMU, KVM and VMware; XenServer is not enabled by default. Our solution is to run the application with Qemu hypervisor and configure XenServer to use if all the conditions have been settled. change the hypervisor type, is quite simple; The following settings are added to start /etc/nova/nova-compute.conf and new Nova Services
[DEFAULT] = compute_driver xenapi.XenAPIDriver [xenserver] connection_url = http :. //169.254. 0.1 connection_username = "root" connection_password = "XENSERVER_PASSWORD" But to do the time of the change, could be difficult. Fortunately Mirantis provides a flexible fuel hook mechanism based on Puppet task dependencies. Once it is done, the new hypervisor type will reflect in the horizon below.
Install required plugins
However, the hypervisor-type change is only the first step. Communication between XAPI and Nova services must be created as shown in the following figure. So we need to install some plugins.
Usually, the best way to apply patches to XenServer hosts, or, more precisely, Dom0 is the modified files to pack XenServer additional package in one and call xe CLI to install.
xe-install additional Pack /tmp/novaplugins-liberty.iso Nevertheless, it is important that the various components are installed in the correct order. The main steps can be install-pv tool install-dpkg-dependencies and install-sup Pack. To see the task dependencies as follows:
- id: 'install-pv tool' role: ['compute'] required_for: ['compute-post-deployment'] requires: ['post_deployment_start'] - id: 'install-dpkg -dependencies role: ['compute'] required_for: ['compute-post-deployment'] requires: ['post_deployment_start'] - id: 'install-sup pack' role: ['compute'] required_for: ['post_deployment_end'] requires: ['install-pv-tool', 'install-dpkg-dependencies'] For more information on Fuel hook mechanism can be found in deployment_tasks.yaml. internal
Re-routing control networks
in XenServer Host Management Network (aka himn.) is a special internal network uses for communication between the compute VM and the Dom0 that he runs. The himn has the following characteristics: ..
- There is a built-in network isolated from the others
- It is invisible in XenCenter, because it should not normally need to be changed
- It provides DHCP service on the network, at a fixed dom0 IP address 169.254.0.1
of himn for internal use is ideal and you don 't expend effort on the one device. More importantly, Dom0 must have access to OpenStack control networks, and do compute nodes. If we transfer control packets over himn, this will be easier than setting up additional interfaces for Dom0. And in a sense Dom0 and compute node can as a unit be considered.
In order to mask the full use of to make himn and ensure that the dom0 management networks can access up by Mirantis OpenStack, we need to compute VM configure packages of dom0 techniques NAT. Here is the code. We create iptable rules in compute nodes:
sed -is / # net.ipv4.ip_forward / net.ipv4.ip_forward / g /etc/sysctl.conf sysctl -p / etc / sysctl. conf iptables -t nat -A POSTROUTING -o br memory -j MASQUERADE iptables -A FORWARD -i br memory -o eth3 -m state --state RELATED, ESTABLISHED -j ACCEPT iptables -A FORWARD -i eth3 -o br- storage -j ACCEPT iptables -t nat -A POSTROUTING -o br-mgmt -j MASQUERADE iptables -A FORWARD -i br-mgmt -o eth3 -m state --state RELATED, ESTABLISHED -j iptables ACCEPT -A FORWARD -i -o eth3 br-mgmt j ACCEPT br-br-storage and mgmt reflect OpenStack storage network management and networks. They are the OpenStack control networks we are talking about. Then we change the default gateway in Dom0 for these two subnets:
route add -net netmask gw route add -net netmask gw updating the OpenStack integration
This plugin can also be used to deliver bug fixes and new features that are designed to OpenStack trunk, but are of great importance for Mirantis 8.0 OpenStack deployment, based on a stable branch of OpenStack:
- neutron plugins: neutron support for XenServer has been introduced in upstream in Mitaka, do not necessarily reflect Mirantis fuel 8, uses the freedom .
- NoVNC Proxy Configuration: The server XenServer VNC runs on Dom0 but Mirantis fuel assumes the default that it runs in computing nodes
- Guest Console Logs :. Enabling serial console guests to control a script board, requires the use and care of the logs do not take unlimited space
- Drive Config configuration: .. Config drive for file injection on the default option should be set instead libguestfs the default setting for other QEMU-based hypervisor is
- validation for hotfix: XenServer additional package XS65ESP1013 must otherwise virtual block device to be installed (VBD) could be connections mapped incorrectly
replacing the test image
the standard test image. "Testvm" is a Qemu specific cirros must be compatible with a replaced with XenServer.
Please be aware that the fuel-health check, which will be treated in the next chapter, always receives the test image "testvm", as the name is hard-coded.
wget http://ca.downloads.xensource.com/OpenStack/cirros-0.3.4-x86_64-disk.vhd.tgz views create image- --name "testvm" - container format ovf --disk format vhd --Property vm_mode = "xen" --visibility public --file "cirros-0.3.4-x86_64 disk.vhd. tgz" in the latest XenServer fuel plugin 3.1 (corresponding MOS 8.0) testvm image in plugin for the event was embedded the insert has no Internet connection.
health check
Fuel Health Check or OpenStack Testing Framework (OSTF), is one of the biggest advantages of fuel. Fuel health check to go through the following categories of automated tests, and usually last 20 to 40 minutes to appreciate the availability of a deployed environment.
testing Sanity function tests HA Platform Services function tests Cloud Validation Tests Tests configuration testing If all goes well, you will receive a summary report as below:
Where to download
XenServer fuel plugin has been validated since fuel 6.1 and listed in the fuel plug-in catalog. This also applies where recommended most to download it.
And the XenCenter himn plugin to find repo under the GitHub account Citrix OpenStack.
The source code for the plug-ins mentioned above is available git are .openstack.org and github.com.
0 Komentar