Difference between revisions of "SME Server:9.0Alpha"
From SME Server
Jump to navigationJump to search (Re-arrange some optional parts to the resource/tips section) |
|||
| Line 17: | Line 17: | ||
* We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external. | * We suggest you use a virtual machine, like Virtualbox - [https://www.virtualbox.org/wiki/Downloads]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external. | ||
{{note box| keep in mind you need to activate the PAE option of your virtualisation environment for playing with SME Server 9}} | {{note box| keep in mind you need to activate the PAE option of your virtualisation environment for playing with SME Server 9}} | ||
| − | * Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it. | + | * Download the SME9 Alpha ISO from [http://mirror.contribs.org/smeserver/releases/testing/9/iso/]. Use the x86_64 version if your hardware supports it. If possible use something like zsync which will transfer just the chages to the ISO and not the whole file itself : |
| − | |||
| − | If possible use something like zsync which will transfer just the chages to the ISO and not the whole file itself : | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
* Start the machine and choose the ISO image to boot from and install SME Server following the instructions. | * Start the machine and choose the ISO image to boot from and install SME Server following the instructions. | ||
| Line 41: | Line 24: | ||
* Login as root and enable networking: | * Login as root and enable networking: | ||
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address | - This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address | ||
| − | < | + | <syntaxhighlight lang="Bash"> |
ifup eth0 | ifup eth0 | ||
ifup eth1 | ifup eth1 | ||
| − | </ | + | </syntaxhighlight> |
* Configure SME9 repositories | * Configure SME9 repositories | ||
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. After the post-upgrade/reboot the proper yum configuration is enabled. | Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. After the post-upgrade/reboot the proper yum configuration is enabled. | ||
| − | < | + | <syntaxhighlight lang="Bash"> |
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682 | wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682 | ||
| − | </ | + | </syntaxhighlight> |
* Yum upgrade to the latest the e-smith and smeserver packages | * Yum upgrade to the latest the e-smith and smeserver packages | ||
- All the e-smith and smeserver packages needed are installed by the CD now, and bug [[bugzilla:7350]] is fixed with e-smith-base-5.4.0-10 so now the command is just: | - All the e-smith and smeserver packages needed are installed by the CD now, and bug [[bugzilla:7350]] is fixed with e-smith-base-5.4.0-10 so now the command is just: | ||
| Line 56: | Line 39: | ||
</pre> | </pre> | ||
* post-upgrade / reboot | * post-upgrade / reboot | ||
| − | < | + | <syntaxhighlight lang="Bash"> |
/sbin/e-smith/signal-event post-upgrade | /sbin/e-smith/signal-event post-upgrade | ||
/sbin/e-smith/signal-event reboot | /sbin/e-smith/signal-event reboot | ||
| − | </ | + | </syntaxhighlight> |
* When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot. | * When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot. | ||
* Configure the server | * Configure the server | ||
| − | - log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again. | + | - log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again. It has been seen that the server freezes on entering the first letter of the admin password, more info needed on this. |
| − | |||
| − | |||
| − | + | - Should be able to access https://yourserverip/server-manager/ now in a browser but due to [[bugzilla:7254]] you need to access it twice. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | / | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| Line 88: | Line 55: | ||
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away. | - If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away. | ||
- the repo smeupdates-testing is not enabled by default. At this point in the development process you will probably want those rpms. This will check what is available: | - the repo smeupdates-testing is not enabled by default. At this point in the development process you will probably want those rpms. This will check what is available: | ||
| − | < | + | <syntaxhighlight lang="Bash"> |
yum --enablerepo=smeupdates-testing upgrade --nogpg | yum --enablerepo=smeupdates-testing upgrade --nogpg | ||
| − | </ | + | </syntaxhighlight> |
== Some ideas for things to look for:== | == Some ideas for things to look for:== | ||
| Line 114: | Line 81: | ||
* There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-) | * There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-) | ||
** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab. ChatZilla is a good option for Firefox users. | ** You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab. ChatZilla is a good option for Firefox users. | ||
| + | |||
| + | == Tips == | ||
| + | |||
| + | * Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router) | ||
| + | <syntaxhighlight lang="Bash"> | ||
| + | db configuration setprop sshd status enabled | ||
| + | db configuration setprop sshd PermitRootLogin yes | ||
| + | db configuration setprop sshd acccess public | ||
| + | db configuration setprop sshd PasswordAuthentication yes | ||
| + | /sbin/e-smith/signal-event remoteaccess-update | ||
| + | </syntaxhighlight> | ||
| + | * Enable easier access to the server manager if you prefer (modify as needed for your network) | ||
| + | <syntaxhighlight lang="Bash"> | ||
| + | db configuration setprop httpd-admin access public | ||
| + | db configuration setprop httpd-admin PermitPlainTextAccess yes | ||
| + | db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' | ||
| + | /sbin/e-smith/signal-event remoteaccess-update | ||
| + | </syntaxhighlight> | ||
| + | |||
== Resources and references == | == Resources and references == | ||
| Line 124: | Line 110: | ||
* [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project] | * [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html From the Fedora project] | ||
| + | === Zsync === | ||
| + | |||
| + | *You can get it for Debian/Ubuntu with | ||
| + | sudo apt-get install zsync | ||
| + | |||
| + | *On CentOS/ RH you can get an RPM here http://pkgs.repoforge.org/zsync/ | ||
| + | |||
| + | You can then do the following : | ||
| + | <syntaxhighlight lang="Bash"> | ||
| + | zsync http://mirror.contribs.org/releases/testing/9/iso/x86_64/smeserver-9.0alpha1-x86_64.iso.zsync | ||
| + | zsync http://mirror.contribs.org/releases/testing/9/iso/i386/smeserver-9.0alpha1-i386.iso.zsync | ||
| + | </syntaxhighlight> | ||
| + | |||
| + | If the ISO changes, just run these commands again and it will propogate the changes, not the whole file. | ||
<noinclude>[[Category:Howto]][[Category:SME9-Development]] | <noinclude>[[Category:Howto]][[Category:SME9-Development]] | ||
Revision as of 23:14, 21 February 2013
Back to SME Server 9.0 Development
SME 9 Alpha1 (Feb 14 2013 version) ISO Testing
An overview of related SME9 development pages can be found here.
There have as of now been 2 versions of the SME9Alpha1 ISO - check the date, this is current as for the Feb 14 2013 version.
User Feedback
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)
Bugs
Installing SME9 Alpha
- We suggest you use a virtual machine, like Virtualbox - [1]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.
- Download the SME9 Alpha ISO from [2]. Use the x86_64 version if your hardware supports it. If possible use something like zsync which will transfer just the chages to the ISO and not the whole file itself :
- Start the machine and choose the ISO image to boot from and install SME Server following the instructions.
After first reboot
- Login as root and enable networking:
- This is a temporary measure, and should work if you have the a DHCP server giving your external adapter (usually eth1) an IP address
ifup eth0
ifup eth1
- Configure SME9 repositories
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. After the post-upgrade/reboot the proper yum configuration is enabled.
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682
- Yum upgrade to the latest the e-smith and smeserver packages
- All the e-smith and smeserver packages needed are installed by the CD now, and bug bugzilla:7350 is fixed with e-smith-base-5.4.0-10 so now the command is just:
yum --disablerepo=base,updates,extras upgrade --nogpg
- post-upgrade / reboot
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot
- When system boots up it will ask you if you want to restore from backup (say no) and enter a root password, etc, and will reboot.
- Configure the server
- log in as root and run 'console' and select 'configure this server', choose the desired configuration and then it ask you to reboot again. It has been seen that the server freezes on entering the first letter of the admin password, more info needed on this.
- Should be able to access https://yourserverip/server-manager/ now in a browser but due to bugzilla:7254 you need to access it twice.
- Save a snapshot in virtualbox so you can revert to this point if needed.
- Look for things to fix & Report bugs/problems
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away. - the repo smeupdates-testing is not enabled by default. At this point in the development process you will probably want those rpms. This will check what is available:
yum --enablerepo=smeupdates-testing upgrade --nogpg
Some ideas for things to look for:
- Services not starting
- Config files (templates) that need changes, especially if the major version of the package has changed
- Look in the various log files for clues to problems
- add more generic ideas here....specific issues to the bugtracker please
- here are the current bugs that have been found
"Well done guys, no more open bugs!"
- Please consult/subscribe to the devs list for more information. devinfo mailinglist
- There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)
- You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click here to open the channel in a new browser window or tab. ChatZilla is a good option for Firefox users.
Tips
- Re-enable ssh access (the lazy not-so-secure way, but I am assuming for this testing/dev scenario that your external IP is really a local address behind a router)
db configuration setprop sshd status enabled
db configuration setprop sshd PermitRootLogin yes
db configuration setprop sshd acccess public
db configuration setprop sshd PasswordAuthentication yes
/sbin/e-smith/signal-event remoteaccess-update
- Enable easier access to the server manager if you prefer (modify as needed for your network)
db configuration setprop httpd-admin access public
db configuration setprop httpd-admin PermitPlainTextAccess yes
db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0'
/sbin/e-smith/signal-event remoteaccess-update
Resources and references
Setting up a RPM Building environment under CentOS
- Simplest way to develop patches to submit
- Building using Mock
- Simple Package Modification
- On the CentOS wiki
- From the Fedora project
Zsync
- You can get it for Debian/Ubuntu with
sudo apt-get install zsync
- On CentOS/ RH you can get an RPM here http://pkgs.repoforge.org/zsync/
You can then do the following :
zsync http://mirror.contribs.org/releases/testing/9/iso/x86_64/smeserver-9.0alpha1-x86_64.iso.zsync
zsync http://mirror.contribs.org/releases/testing/9/iso/i386/smeserver-9.0alpha1-i386.iso.zsync
If the ISO changes, just run these commands again and it will propogate the changes, not the whole file.
