Changes

Jump to navigation Jump to search

Testing Environments (view source)

Revision as of 19:41, 5 March 2021

7,235 bytes added ,  19:41, 5 March 2021
→‎Contribs Testing
Line 1: Line 1:  +
{{Languages}}
 +
== Helpful Wiki Pages ==
 +
 +
* [https://wiki.contribs.org/Dashboard#tab=SME_Server_10_Alpha Development Dashboard]
 +
 +
* [https://wiki.contribs.org/SME_Server:Documentation:QA:Verification QA Verifications]
 +
 +
* [https://wiki.contribs.org/SME10.0_QA Koozali SME 10 QA]
 +
 +
* [https://wiki.contribs.org/Extrarepositories Extra Repositories] that may be needed for test scenarios
 +
 +
* [https://wiki.contribs.org/Simple_Package_Modification Simple Package Modification]
 +
* [https://wiki.contribs.org/index.php?title=Setting_up_RPM_Building_for_SME_Server Setting_up_RPM_Building_for_SME_Server]
 +
 
== Hardware ==
 
== Hardware ==
 
[http://www.koozali.org/home/hardware-compatibility Hardware Compatability]
 
[http://www.koozali.org/home/hardware-compatibility Hardware Compatability]
Line 6: Line 20:     
As a general rule just about any hardware will suffice as a Standalone test machines or as a host for a virtual environment.
 
As a general rule just about any hardware will suffice as a Standalone test machines or as a host for a virtual environment.
 +
 +
For sme10 a minimum of 4gb of RAM is recommended, you can try with less but may have issues when testing under load, eg backup and restores of large file sets.
 +
 +
== Install ISO for Testing or Bug Verification==
 +
Its simple for those who do this regularly, it can be a bloody mine pit for someone who doesn't 🙂 very easy to kill a test system and no way to get out but wipe and start again, please don't be put off, if nothing else it sure educates you on the blackmagic in koozali/sme
 +
 +
{{Warning box|Be aware you should never perform a full yum update with the /smetest and/or /smedev repos enabled it will almost certainly put your server in a state that may not be recoverable from..}}
 +
 +
1. Install current iso that is available from the Koozali webssite - [[SME Server:Download|Downloads]]
 +
 +
2. Once installed, use SSH, SSH access must be enabled with the /server-manager, set remote access to allow, from the cli run a # yum update (DO NOT enable any repos) there can be many mb of updates depending on age of iso, on occasion ie very very rarely smeserver-yum may also need updating first, it may be in smeupdates-testing or updates, so a heads up a quick look under the hood can save a world of grief, [http://mirror.canada.pialasse.com/releases/testing/10/ Koozali Repository] eg
 +
# yum update smeserver-yum --enablerepo=smeupdates-testing
 +
 +
3. Make sure to reboot/reconfig
 +
# signal-event post-upgrade; signal-event reboot
 +
 +
4. Best practice is to select a Bug that need verifying, See [[Dashboard|the Dashboard]] in the wiki, update the package with the updated rpm listed in the Bug 
 +
# yum update e-smith-base --enablerepo=smeupdates-testing (ONLY this)
 +
 +
5. Now for the fly in the ointment - sometimes, rarely, there will be a package in /smetest that fixes a borked update in smeupdates-testing, that situation can arise with any update, these will appear in smeupdates-testing eventually, it is alwways a good idea to check in /smetest for a later version of a package.
 +
 +
6. If you issue the following 
 +
# yum update --enablerepo=smeupdates-testing
 +
you will update ALL the packages that have been updated or added and need testing, every new/modified rpm - a danger Will Robinson moment if there ever was one - this not recommended but can be useful to carry out overall testing of the system or Contrib updates/import testing and verification BUT beware you could also kill your test box VM 🙂
 +
 +
=== Contribs Testing ===
 +
For testing of contribs a simple install and yum update should be sufficient to prepare the test environment, however it may also be necessary to also include a yum update from /smeupdates-testing as well, this will become apparent when attempting an install of an updated contrib.
 +
 +
Contribs for testing will usually be found in the /smedev /smetest repos, all will have a Bug to track the update.
 +
 +
https://bugs.contribs.org/show_bug.cgi?id=11272
 +
 +
yum install smeserver-nfs --enablerepo=smetest,smeupdates-testing 
 +
 +
*** Warning only install an updated contrib with a specific command referencing the /smedev and /smetest repos, NEVER just do a yum update --enablerepo=smedev,smetest this will most certainly render your system akin to a dead parrot.
 +
 +
Those contribs found in the /smetest repo will generally be able to be installed and tested for functionality, report all findings in associated Bug.  Those contribs in /smedev may still have a degree of instability and may install but not run, again all results to relevant bug.
 +
 +
Any contrib that has been moved to the sme10 contribs repo should be fully functional, again there will be a Bug that may still be open to track any issues, use it.
 +
 +
Have fun..always learning
    
== VM Setups ==
 
== VM Setups ==
    
===VirtualBox===
 
===VirtualBox===
 +
Content to be done
 +
 
====Microsoft Windows====
 
====Microsoft Windows====
 +
Content to be done
 +
 
==== MacOS ====
 
==== MacOS ====
 +
Very remiss of me (Terry Fage) in not mentioning the MacOS setup was captured and written up by Chris (I wont list his username unless he wants to) I simply copied pasted, we need more Chris's
 +
 
  Create a new Virtual Machine, choose 'Linux' as the type, 'Other Linux (64-bit)' as the version and set the memory to at least 1GB, ideally 2GB+ as ClamAV on its own needs ~1GB.
 
  Create a new Virtual Machine, choose 'Linux' as the type, 'Other Linux (64-bit)' as the version and set the memory to at least 1GB, ideally 2GB+ as ClamAV on its own needs ~1GB.
   Line 52: Line 113:  
[[File:Audio.jpg]]
 
[[File:Audio.jpg]]
   −
  Choose a 'bridged' network adapter and make sure it's attached to your host's main network connection. This way your VM will becaues like a normal machine on your network and you can SSH to it
+
  Choose a 'bridged' network adapter and make sure it's attached to your host's main network connection. This way your VM will because like a normal machine on your network and you can SSH to it
    
[[File:Networking.jpg]]
 
[[File:Networking.jpg]]
Line 63: Line 124:     
====Linux====
 
====Linux====
 +
Content to be done
    
=== Proxmox ===
 
=== Proxmox ===
Line 69: Line 131:  
* [https://pve.proxmox.com/wiki/Installation Installation]
 
* [https://pve.proxmox.com/wiki/Installation Installation]
   −
Install/configure Koozali SME9/10 VM on proxmox VE
+
Install Proxmox #.# to suitable hardware - see proxmox wiki for details of setup
 +
 
 +
Start Proxmox, login as root, before creating a new VM there needs to be a relevant iso image available from pve storage to act as a install CD/DVD, this and other OS isos needs to be uploaded to pve local storage
 +
 
 +
[[File:Uploadiso a.jpg|850px]]
 +
 
 +
Select upload button
 +
 
 +
[[File:Uploadiso.jpg|850px]]
 +
 
 +
Select a suitable iso and upload
 +
 
 +
[[File:Uploadiso2.jpg|850px]]
 +
 
 +
====Install/configure Koozali SME9/10 VM on proxmox VE====
 +
 
 +
If not already running Start Proxmox and login as root, Select Create VM button in top right corner
 +
 +
[[File:Openproxhome.jpg|850px]]
 +
 
 +
[[File:Newvm-name.jpg|850px]]
 +
 
 +
Enter name details of new VM
 +
 
 +
[[File:Newvm-name1.jpg|850px]]
 +
 
 +
Select CD/DVD image file to use as install source
 +
 
 +
[[File:Vm-CD-DVD1iso.jpg|850px]]
 +
 
 +
[[File:Vm-CD-DVD2iso.jpg|850px]]
 +
 
 +
VM System, safe to accept defaults
 +
 
 +
  [[File:System1.jpg|850px]]
 +
 
 +
Hard disk details, type/size - min of 10gb will suffice for a SME10 install
 +
 
 +
[[File:Hardisk.jpg|850px]]
 +
 
 +
  CPU depending on hardware the more the better - 1 Socket 2 cores sufficent
 +
 +
[[File:Cpu-cores.jpg|850px]]
 +
 
 +
Memory - minimum for sme10, 1024mb will operate sluggishly, 2048mb preferred minimum, 4096mb ideal
 +
 
 +
[[File:mem2048.jpg|850px]]
 +
 
 +
Network setting defaults are safe to use
 +
 
 +
[[File:Proxneteth.jpg|850px]]
 +
 
 +
Summary of settings
 +
 
 +
[[File:summary.jpg|850px]]
 +
 
 +
Additional Hardware, Add extra hardware, change hardware settings
 +
 +
[[File:Hardware.jpg|850px]]
 +
{{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:
 +
* Create a new network interface and call it '''vmbr1'''
 +
* Do NOT set IP address/subnet/bridge ports etc.
 +
* 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
 +
::MAC: 10:10:00:00:20:20 (as per your mac that you set)
 +
*After you have created the KVM add a second adaptor:
 +
**vmbr1 should have the following settings:
 +
::Model: virtio
 +
::MAC: should be the MAC of your main IP address
 +
 
 +
It doesn't matter which one is 0 or 1 as long as the settings are correct.
 +
 
 +
 +
 
 +
 +
[[File:Hardware2.jpg|850px]]
 +
 
 +
Select console and push start button, install will begin, interact as normal
 +
 
 +
[[File:sme10setup.jpg|850px]]
 +
 
 +
A standalone terminal window can be seletced by selecting from top right menu - console- no vnc
 +
 
 +
[[File:Terminal.jpg|850px]]
 +
 +
 +
[[Category:Developer]]
 +
 +
[[Category:SME Server Development Framework]]
 +
 +
[[Category:Development Tools]]
 +
 +
[[Category:SME9-Development]]
 +
 +
[[Category:SME10-Development]]
    
=== ESXi ===
 
=== ESXi ===
Retrieved from "https://wiki.koozali.org/Special:MobileDiff/38596...39159"

Navigation menu