Changes

From SME Server
Jump to navigationJump to search

Virtual SME Server (view source)

Revision as of 05:00, 1 September 2022

2,736 bytes added ,  05:00, 1 September 2022
→‎Proxmox configuration
Line 1: Line 1:  
{{Note box|WIP. Place holder page for all things related to using SME Server as a virtualized server. Please add any info you feel is useful and someone from the doc team will format it nicely, so please go ahead!}}
 
{{Note box|WIP. Place holder page for all things related to using SME Server as a virtualized server. Please add any info you feel is useful and someone from the doc team will format it nicely, so please go ahead!}}
−
{{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|A thorough understanding of SME Server, configuration and the virtualization system to be used 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. It's entirely practical to do so, and many installations have run satisfactorily in virtual hosts for many years, but you will generally be responsible for your own solutions!}}
    +
 +
<br />
 
=SME Server as a virtualized Guest server=
 
=SME Server as a virtualized Guest server=
 +
 +
==Examples: Available Virtual Machine hosts==
 +
 +
===Infrastructure-level===
 +
 +
*Proxmox VM Community edition
 +
*Linux KVM (Red Hat developed, available with various managment tools also on CentOS, Debian, Ubuntu etc.)
 +
*VMWare Enterprise (not free)
 +
*Citrix (not free)
 +
 +
===Desktop-level===
 +
 +
*VirtualBox
 +
*VMWare workstation (not free)
 +
*VMWare Fusion (Apple) (not free)
 +
*Parallels (Apple) (not free)
 +
*Linux KVM
 +
 +
===Cloud Hosting===
 +
 +
There are many different offerings, too many to explore here.
 +
 +
In general, setup, requirements and management will be similar for most of the above.
 +
 
==Considerations==
 
==Considerations==
   Line 15: Line 41:  
*Host CPU or emulate
 
*Host CPU or emulate
   −
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.
+
On Proxmox Host CPU mode is the most performant, but is self-evidently restrictive if you intend to be able to move the VM to a host with different host architecture!.
 +
 
    
*Sockets and cores
 
*Sockets and cores
 +
 +
Althose two sockets with one core and one socket with two cores produces the same number of cores, it may be treated differently by server licensing (e.g. Windows). This consideration does not apply to Koozali SME Server as a guest: one socket and multiple cores is typically chosen.
    
===Memory options===
 
===Memory options===
Line 97: Line 126:  
*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 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
   Line 118: Line 147:  
*10:10:00:00:20:20 - you DID set the MAC didn't you ?
 
*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 Gateway IP you can use for all your VMs : 62.210.0.1}}
    
===Proxmox configuration===
 
===Proxmox configuration===
Line 142: Line 171:  
It doesn't matter which one is 0 or 1 as long as the settings are correct.
 
It doesn't matter which one is 0 or 1 as long as the settings are correct.
   −
{{Note box|You still cannot set a different gateway IP in the console configuration due to subnet checking.}}
+
You might want to edit your /etc/network/interfaces
 +
auto vmbr1
 +
iface vmbr1 inet manual
 +
        bridge-ports none
 +
        bridge-stp off
 +
        bridge-fd 0
 +
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
 +
        # we assume external interface is eno1 here, adapt accordingly
 +
        post-up echo 1 > /proc/sys/net/ipv4/conf/eno1/proxy_arp
 +
        post-up echo 1 > /proc/sys/net/ipv4/conf/vmbr1/proxy_arp
 +
        post-up echo 1 > /proc/sys/net/ipv4/conf/vmbr1/forwarding
 +
        #uniq ip
 +
        post-up /sbin/ip route add VMIP.VMIP.VMIP.VMIP dev vmbr1
 +
        pre-down /sbin/ip route del VMIP.VMIP.VMIP.VMIP
 +
        # multiple routable IP subnet example
 +
        post-up /sbin/ip route add VMIP.VMIP.VMIP.VMIP/29 dev vmbr1
 +
        pre-down /sbin/ip route del VMIP.VMIP.VMIP.VMIP
    
After setup you can run:
 
After setup you can run:
Line 151: Line 196:  
  signal-event post-upgrade;signal-event reboot
 
  signal-event post-upgrade;signal-event reboot
   −
{{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 Configuration===
 +
Now do your standard SME installation.
 +
 
 +
<tabs container><tab name="For SME 10">
 +
* Install SME using ISO
 +
* choose install mode without LVM and RAID add this on boot options: nolvm noraid
 +
* Optionally you could use the Disk tool at the second screen if you want to put /home/e-smith/files in a different disk.
 +
* Enter the console at the end of installation.
 +
** set admin password
 +
** set domain and hostname
 +
** choose server-gateway (do not use server only if you use an IP accessible directly from the internet because Firewall is not designed for that in Server-Mode)
 +
** LAN: choose the dummy interface if you only have an interface, or the appropriate one for LAN
 +
** LAN: use all suggested setting or adapt to your needs
 +
** WAN: choose static mode
 +
** WAN: set the dedicated IP
 +
** WAN: set the Netmask with either 255.255.255.255 or 0.0.0.0 (MASK includes only your IP or MASK includes all IPs)
 +
** WAN: set the Gateway IP (as the Gateway will be quite different from the Server IP you need to have the MASK set as shown above to have it accepted.
 +
 
 +
signale-event post-upgrade; signal-event reboot
   −
===SME V8 Configuration===
+
enjoy
−
Now do your standard SME installation.
      +
</tab>
 +
<tab name="For SME 8">
 
<here would be a lot easier if we could force it to have a local IP first so you could ssh from Proxmox to SME and you could then use scp to copy files or a terminal to copy and paste>
 
<here would be a lot easier if we could force it to have a local IP first so you could ssh from Proxmox to SME and you could then use scp to copy files or a terminal to copy and paste>
   Line 241: Line 305:  
  LocalNetmask=255.255.255.0
 
  LocalNetmask=255.255.255.0
   −
===SME V9 Configuration===
+
</tab><tab name="For SME 9">
    
Things have changed slightly for v9
 
Things have changed slightly for v9
Line 262: Line 326:     
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
 +
</tab>
 +
</tabs>
    
==Xen==
 
==Xen==
Unnilennium
Super Admin, Wiki & Docs Team, Bureaucrats, Interface administrators, Administrators
3,249

edits

Retrieved from "https://wiki.koozali.org/Special:MobileDiff/39647...41650"

Navigation menu