Xen XCP 1.0

Guideline
- What is Xen ?
- What is Xen XCP ?
- Who makes Xen XCP ?
- Who is using Xen XCP ?
1. What is Xen ?
The Xen hypervisor is a layer of software running directly on computer hardware replacing the operating system thereby allowing the computer hardware to run multiple guest operating systems concurrently. Support for x86, x86-64, Itanium, Power PC, and ARM processors allow the Xen hypervisor to run on a wide variety of computing devices and currently supports Linux, NetBSD, FreeBSD, Solaris, Windows, and other common operating systems as guests running on the hypervisor.
The Xen.org community develops and maintains the Xen hypervisor as a free solution licensed under the GNU General Public License.
2. What is Xen XCP ?
The meaning about XCP = Xen Cloup Plattform
Features
- Is an open source enterprise-ready server virtualization.
- Is a cloud computing platform.
- Consolidates server workloads.
- Enables power-saving.
- Enables cooling-saving.
- Decrease management costs.
- Hardware optimization.
- Improve IT realibility
Architecture

2. Who makes Xen XCP ?
Xen XCP use the Citrix Xen Hypervisor. Xen was developed by Citrix. Xen XCP is an open server virtualization powered by Citrix. You can use it as free there is not necesary any license.
3. Who is using Xen XCP ?
- Cloud providers
- Hosting services
- Data centers
Pictures from Xen XCP ISO Installation
Easy to install.


Bind9 Configuration files to deploy a local network name server alias "thor.loc":
/etc/bind/named.conf.local
zone "thor.loc" {
type master;
file "/etc/bind/db.thor.loc";
};
zone "1.168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.1.168.192";
};
/etc/bind/db.thor.loc
$TTL 24h
thor.loc. IN SOA DNS-01.thor.loc. root.thor.loc. (
1 ; Serial
3h ; Refresh
30m ; Retry
7d ; Expire
3h) ; Minimum TTL
; Nameservers
thor.loc. IN NS 192.168.1.103.
; Hosts
Web-01.thor.loc. IN A 192.168.1.100
Sql-01.thor.loc. IN A 192.168.1.101
File-01.thor.loc. IN A 192.168.1.102
DNS-01.thor.loc. IN A 192.168.1.103
Mail-01.thor.loc. IN A 192.168.1.104
Gateway-01.thor.loc. IN A 192.168.1.105
Debian-01.thor.loc. IN A 192.168.1.200
/etc/bind/db.1.168.192
$TTL 24h
1.168.192.in-addr.arpa. IN SOA DNS-01.thor.loc. root.thor.loc (
1 ; serial number
3h ; refresh time
30m ; retry time
7d ; expire time
3h) ; negative caching ttl
; Nameservers
1.168.192.in-addr.arpa. IN NS 192.168.1.103.
; Hosts
100.1.168.192.in-addr.arpa. IN PTR Web-01.thor.loc.
101.1.168.192.in-addr.arpa. IN PTR Sql-01.thor.loc.
102.1.168.192.in-addr.arpa. IN PTR File-01.thor.loc.
103.1.168.192.in-addr.arpa. IN PTR DNS-01.thor.loc.
104.1.168.192.in-addr.arpa. IN PTR Mail-01.thor.loc.
105.1.168.192.in-addr.arpa. IN PTR Gateway-01.thor.loc.
200.1.168.192.in-addr.arpa. IN PTR Debian-01.thor.loc.
/etc/resolv.conf
search thor.loc
nameserver 192.168.1.103
/etc/network/interfaces
# The primary network interface
auto eth1
iface eth1 inet static
address 192.168.1.103
network 192.168.1.0
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.1.1
dns-nameservers 192.168.1.103
Tags: Bind, Bind9, local, local network, name server, network, NS, Setup, using
bind, Debian, Linux, Uncategorized | salonso |
9:20 am |
Comments (0)