653
edits
Changes
From SME Server
Jump to navigationJump to searchbits
{{Level|Developer|Thorough understanding of SME Server, configuration and virualization is required. Do not deploy in a production environment unless you are very confident you have the skills to manage and troubleshoot and find root causes of possible issues.}}
{{Level|Developer|Thorough understanding of SME Server, configuration and virualization is required. Do not deploy in a production environment unless you are very confident you have the skills to manage and troubleshoot and find root causes of possible issues.}}
= SME Server as a virtualized Guest server =
=SME Server as a virtualized Guest server=
== Considerations ==
==Considerations==
*Storage: Local, NAS, iSCSI, LVM, Raid
*Network: LAN/WAN, VLAN, VPN, Bandwith,
*Out of band access (VNC, SPICE)
=='Hardware' configuration of a Virtual SME Sever==
===CPU===
*Host CPU or emulate
* To balloon or to not to balloon
On Proxmox Host CPU mode is the most performant, but is restrictive if you intend to be able to move the VM to differnet host hardware.
=== Network options ===
*Sockets and cores
* Virtio driver or legacy driver?
* Bridge, NAT or Route?
===Memory options===
* Bandwidth options
*To balloon or to not to balloon: for Linux guests yes, at present avoid for WIndows guests
===Disk options===
*Virtio driver or legacy driver: On Proxmox for Linux use VirtIO
*Disk types pros and cons
*Disk I/O options
===Network options===
*Virtio driver or legacy driver?
*Bridge, NAT or Route?
*Bandwidth options
== Installation options of a Virtual SME Server ==
==Installation options of a Virtual SME Server==
=== Kernel options ===
===Kernel options===
*
*
== SME Server configuration settings ==
==SME Server configuration settings==
=== NTPD ===
===NTPD===
Timing related options are important within Virtual Guests and to the amount of 'pressure' it puts on the host and level/increasing CPU usage of the host and guest. By default SME Server uses the NTP deamon for 'timing' related matters, but by default is focussed on the above mentioned 1000HZ, hence the kernel option 'divider=10', thus reducing the timing cycles/context switching requests on the host. See the above VMWare document mentioned (Way at the bottom).
Timing related options are important within Virtual Guests and to the amount of 'pressure' it puts on the host and level/increasing CPU usage of the host and guest. By default SME Server uses the NTP deamon for 'timing' related matters, but by default is focussed on the above mentioned 1000HZ, hence the kernel option 'divider=10', thus reducing the timing cycles/context switching requests on the host. See the above VMWare document mentioned (Way at the bottom).
to activate the new configuration. This will adjust /etc/ntp.conf to 'better' settings for a virtual guest. By setting the above value to 'disabled' and expand the template, the NTP service and configuration will revert back to SME Server defaults.
to activate the new configuration. This will adjust /etc/ntp.conf to 'better' settings for a virtual guest. By setting the above value to 'disabled' and expand the template, the NTP service and configuration will revert back to SME Server defaults.
=== Clock/frequency ===
===Clock/frequency===
As per suggestions in [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006427 this article from VmWare] and this one from [https://blogs.oracle.com/fatbloke/entry/speeding_up_your_linux_guests Oracle] on virtual Linux Guests, adjusting the guest Frequency will improve the guests speed.
As per suggestions in [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006427 this article from VmWare] and this one from [https://blogs.oracle.com/fatbloke/entry/speeding_up_your_linux_guests Oracle] on virtual Linux Guests, adjusting the guest Frequency will improve the guests speed.
{{Note box|We need to come up with a template fragment for grub.conf to make kernel options survive events.}}
{{Note box|We need to come up with a template fragment for grub.conf to make kernel options survive events.}}
== Tools/utilities ==
==Tools/utilities==
=== iotop ===
===iotop===
top like utility to monitor the guest I/O (performance)
top like utility to monitor the guest I/O (performance)
yum install iotop
yum install iotop
=== cpu info ===
===cpu info===
Detailed info on the guest cpu(s)
Detailed info on the guest cpu(s)
cat /proc/cpuinfo
cat /proc/cpuinfo
== Proxmox ==
==Proxmox==
* Interesting [http://pve.proxmox.com/wiki/SMEServer_KVM article] on installing SME Server as guest on Proxmox
*Interesting [http://pve.proxmox.com/wiki/SMEServer_KVM article] on installing SME Server as guest on Proxmox
=== SME v8 and v9 on Proxmox at Online.net ===
===SME v8 and v9 on Proxmox at Online.net===
This is based on work by Daniel here: https://wikit.firewall-services.com/doku.php/tuto/virtualisation/netwok_conf_sur_dedibox
This is based on work by Daniel here: https://wikit.firewall-services.com/doku.php/tuto/virtualisation/netwok_conf_sur_dedibox
=== Online.net configuration ===
===Online.net configuration===
{{Warning box|You need a second IP (failover) address. Assign it to your server and make sure you set the MAC for this IP before you do anything else - '''failure to do so may block your network !!'''<br />
{{Warning box|You need a second IP (failover) address. Assign it to your server and make sure you set the MAC for this IP before you do anything else - '''failure to do so may block your network !!'''<br />
''The problem is that your IP is NOT on the same network range as your gateway so we have to fool the system.''
''The problem is that your IP is NOT on the same network range as your gateway so we have to fool the system.''
Some assumptions:
Some assumptions:
;Your main Proxmox server IP address:
;Your main Proxmox server IP address:
* IP address 62.20.20.250
* Netmask 255.255.255.0
*IP address 62.20.20.250
* Gateway 62.20.20.1
*Netmask 255.255.255.0
*Gateway 62.20.20.1
;Your secondary IP address :
;Your secondary IP address :
* 200.30.30.1
* 10:10:00:00:20:20 - you DID set the MAC didn't you ?
*200.30.30.1
*10:10:00:00:20:20 - you DID set the MAC didn't you ?
{{Note box|Proxmox now have a single IP you can use for all your VMs : 62.210.0.1}}
{{Note box|Proxmox now have a single IP you can use for all your VMs : 62.210.0.1}}
=== Proxmox configuration ===
===Proxmox configuration===
{{Note box|Make sure you set your default keyboard - it makes life much easier!!}}
{{Note box|Make sure you set your default keyboard - it makes life much easier!!}}
We will use the '''vmbr0''' that is set up, but we need to create a dummy one so we can put SME in server/gateway mode and use Daniels scripts:
We will use the '''vmbr0''' that is set up, but we need to create a dummy one so we can put SME in server/gateway mode and use Daniels scripts:
* Create a new network interface and call it '''vmbr1'''
* Do NOT set IP address/subnet/bridge ports etc.
*Create a new network interface and call it '''vmbr1'''
* Create your KVM for SME. Make sure that you give it two network adaptors - one is '''vmbr0''' and one is '''vmbr1'''
*Do NOT set IP address/subnet/bridge ports etc.
** vmbr0 should have the following settings :
*Create your KVM for SME. Make sure that you give it two network adaptors - one is '''vmbr0''' and one is '''vmbr1'''
**vmbr0 should have the following settings :
::Model: virtio
::Model: virtio
::MAC: 10:10:00:00:20:20 (as per your mac that you set)
::MAC: 10:10:00:00:20:20 (as per your mac that you set)
*After you have created the KVM add a second adaptor:
*After you have created the KVM add a second adaptor:
**vmbr1 should have the following settings:
**vmbr1 should have the following settings:
::Model: virtio
::Model: virtio
::MAC: should be the MAC of your main IP address
::MAC: should be the MAC of your main IP address
{{Warning box|The following sections for v8 and v9 should no longer be relevant with the inclusion of the virtual adaptor code in SME server now}}
{{Warning box|The following sections for v8 and v9 should no longer be relevant with the inclusion of the virtual adaptor code in SME server now}}
=== SME V8 Configuration ===
===SME V8 Configuration===
Now do your standard SME installation.
Now do your standard SME installation.
you can use your second IP address for the external interface, but you will have to set a subnet mask and gateway IP that it likes e.g.:
you can use your second IP address for the external interface, but you will have to set a subnet mask and gateway IP that it likes e.g.:
:IP : 200.30.30.1
:IP : 200.30.30.1
:Subnet : 255.255.255.0
:Subnet : 255.255.255.0
LocalNetmask=255.255.255.0
LocalNetmask=255.255.255.0
=== SME V9 Configuration ===
===SME V9 Configuration===
Things have changed slightly for v9
Things have changed slightly for v9
Note that you will not see MAC addresses in the Internal Interface settings as you did in v8
Note that you will not see MAC addresses in the Internal Interface settings as you did in v8
== Xen ==
==Xen==
== QEMU/KVM ==
==QEMU/KVM==
<br />
<br />
== Virtualbox ==
==Virtualbox==
===High I/O causing filesystem corruption===
===High I/O causing filesystem corruption===
== OpenNode ==
==OpenNode==
See this [http://forums.contribs.org/index.php?topic=50994 forum] post
See this [http://forums.contribs.org/index.php?topic=50994 forum] post
You will find help in the opennode's wiki and forum.
You will find help in the opennode's wiki and forum.
= SME Server as a Host server =
=SME Server as a Host server=
== Phpvirtualbox ==
==Phpvirtualbox==
*[[Phpvirtualbox]] SME Contrib
* Contribs.org [[Vmware|Wiki page]] on installing VMware on SME Server
==VMware==
*Contribs.org [[Vmware|Wiki page]] on installing VMware on SME Server
*[[VMware_Tools|Wiki page]] on installing SME Server as a VMWare guest
*Interesting guide from [http://support.theenterprisecloud.com/kb/default.asp?id=355&Lang=1&SID= Verizon] on performance tuning.
[[Category:Virtualisation]]
[[Category:Virtualisation]]
[[Category:Howto]]
[[Category:Howto]]
