859
edits
Changes
From SME Server
Jump to navigationJump to searchno edit summary
== Installation options of a Virtual SME Server ==
== Installation options of a Virtual SME Server ==
=== Kernel options ===
=== Kernel options ===
* LVM (option nolvm)
*
== SME Server configuration settings ==
== SME Server configuration settings ==
=== 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|It is suggested that this is not required for RHEL/CentOS 6}}
You can check if your guest server can benefit from these boot options:
You can check if your guest server can benefit from these boot options:
Some assumptions:
Some assumptions:
;Your main IP address:
;Your main Proxmox server IP address:
* IP address 62.20.20.250
* IP address 62.20.20.250
* Netmask 255.255.255.0
* Netmask 255.255.255.0
* 200.30.30.1
* 200.30.30.1
* 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}}
=== Proxmox configuration ===
=== Proxmox configuration ===
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.}}
After setup you can run:
config set GatewayIP 62.210.0.1
/etc/e-smith/events/actions/update-ifcfg
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 V8 Configuration ===
=== SME V8 Configuration ===
}
}
EOF
EOF
(See below for SME v9 configuration)
If you have got it right then you should be able to run the following without error :
If you have got it right then you should be able to run the following without error :
LocalIP=192.168.98.1
LocalIP=192.168.98.1
LocalNetmask=255.255.255.0
LocalNetmask=255.255.255.0
=== SME V9 Configuration ===
Things have changed slightly for v9
Use the same db settings and templates as for v8.
You can make one small change to the template. Replace :
my $gw = $ExternalInterface{'Gateway'};
With
my $gw = $GatewayIP;
To update the config files you now need to run :
/etc/e-smith/events/actions/update-ifcfg
signal-event post-upgrade;signal-event reboot
Note that you will not see MAC addresses in the Internal Interface settings as you did in v8
== Xen ==
== Xen ==
== VMware ==
== VMware ==
* Contribs.org [[Vmware|Wiki page]] on installing VMware on SME Server
* 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.
* Interesting guide from [http://support.theenterprisecloud.com/kb/default.asp?id=355&Lang=1&SID= Verizon] on performance tuning.
