| Article Index |
|---|
| Xen mini-ISP architecture |
| Setting Basic Infrastruture |
| Installing a new VM |
| Network Infrastructure |
| Zones Security Model |
| Quick Start |
| Bugs, New Feature |
| All Pages |
Setting up basic Xen infrastructure
This guide is not a Xen quick start and I expect at this level that you already have Xen/domU up and running. If you're making test on a local workstation then installing XEN is quite straight forward with any current major distributions. With OpenSuSE this is as simple as going in YaST and click on Xen tab for Kubuntu an other Debian flavors aptget will do the job for you. Nevertheless If you are in a remote hosting environment, then it might unfortunately be more tricky, I posted a note on how to make this within OVH remote hosting environment that is available from here and that hopefully should be reusable within most of other hosting facilities.
Default Xen standard distribution provide three network scripts, unfortunately none of them is doing the we want we unfortunatly had to build one, that is downloadable from here Fridu-Script. Assuming that you install it at default /etc/xen/scripts location, you then need to update your xend-config file to call it. Note xend normal script only create only one bridge, this one will create as many bridge as needed.
| # # Xend configuration sample for Fridu-In-Xen # # The hosts allowed to talk to the relocation port. (xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$') # Start Fridu-In-Xen Script to Build 3 Zones (network-script 'Fridu-network.script xen-br1:10.10.1.1:255.255.255.0 xen-br2:10.10.2.1:255.255.255.0 xen-br3:10.10.3.1:255.255.255.0') # We use Xen standard bridge stript (vif-script 'vif-bridge bridge="xen-br1"') # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to. (dom0-min-mem 196) # If dom0-cpus = 0, dom0 will take all cpus available (dom0-cpus 0) |
You need one bridge per zone, but it is not mandatory to build them from xend. For testing purpose it is often easier to create/destroy them manually with Fridu-network.script as shown in next table and check result with ifconfig command.
/etc/xen/scripts/fridu-in-xen.sh start xen-br1:10.10.13.1:255.255.255.0 ifconfig xen-br1 |
Note: Xend when stopping does not remove unused bridges, it is not a problem, but may lead to confusion when making test. You should know that you don't have to reboot to remove bridges, Fridu script does not touch your main NIC also as soon as xend is stopped you can safely remove all unnecessary bridges. Note than default Xen network bridge rename and attach you main NIC, making deletion of bridges more sensitive. In order to clean bridge use following commands:
- /etc/init.d/xend stop ;# make send is stopped
- brctl show xen-br1 ;# make sure they is no interface attached
- ifconfig xen-br1 down ;# stop bridge interface name xen-br1
- brctl delbr xen-br1 ;# delete old bridge
Making the assumption that Xen is now ready and working check with "xm list" that domu-0 is running. If everything is OK you're ready for next phase.
Just wanted to point out that the two sets of 'Prev - Next' links at the footer of the page are slightly confusing. Maybe the bottom ones should be called 'Older/Newer Article'
BTW, this is a great resource. I will try to understand it and apply it in a similar scenario.
=========> Fulup respond ==============
I agree that having two next/prev link on the same page is confusing :( I kept Joomla default default config, which was not a good idea.
Conclusion: I removed the article/article navigation and kept only the on to browse current article.
Thank you for the TIP.