Difference between revisions of "SME Server:9.0Alpha"

From SME Server

Latest revision as of 10:26, 18 March 2017

	Note:
	This page is now obsolete, kept for reference only. see SME Server 9 Release Notes

SME 9 Alpha3 (March 12th 2013 version) ISO Testing

An overview of related SME9 development pages can be found here.

The process described on this page is the next major step by step cycle and a continuation of SME on CentOS.

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

Check the recent activity in the SME9 category:link
SME9 Bugs by type / status: link

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.

	Note:
	keep in mind you need to activate the PAE option of your virtualisation environment.

Download the SME9 Alpha ISO from here. Use the x86_64 version if your hardware supports it. If possible use something like ZSync which will transfer just the changes 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.

Reporting issues

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:

	Note:
	Now go and verify the FIXED SME Server 9 bugs, see Verification_Queue for the list and link to the process.

Log onto the server-manager.
Go into every panel, try every option on each panel. Look at /var/log/messages and any other relevant log file
The testing of the above step could be made more systematic if someone could document each step. SME9.0_QA This is a copy of the SME 8 QA page, it could be adapted for SME 9

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

Discussion, help and share

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. #SME_server on freenode

Tips

Re-enable ssh access

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)

config setprop sshd status enabled acccess public PermitRootLogin yes PasswordAuthentication yes
/sbin/e-smith/signal-event remoteaccess-update

easier access to the server manager

Enable easier access to the server manager if you prefer

config setprop httpd-admin ValidFrom all 
/sbin/e-smith/signal-event remoteaccess-update

Resources and references

Setting up a RPM Building environment under CentOS

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.

Retrieved from "https://wiki.koozali.org/index.php?title=SME_Server:9.0Alpha&oldid=32938"

Categories:

@@ Line 2: / Line 2: @@
 __TOC__
-== SME 9 Alpha (Feb 14 2013 version) ISO Testing ==
+{{note box| This page is now obsolete, kept for reference only. see [[SME Server:9.0|SME Server 9 Release Notes]]}}
+== SME 9 Alpha3 (March 12th 2013 version) ISO Testing ==
 An overview of related SME9 development pages can be found [[:Category:SME9-Development|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.
+The process described on this page is the next major step by step cycle and a continuation of [[SME_on_CentOS_6|SME on CentOS]].
 === 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 ===
 * Check the recent activity in the SME9 category:[http://bugs.contribs.org/bugs/buglist.cgi?action=wrap&product=SME%20Server%209.X&list_id=12948 link]
 * SME9 Bugs by type / status: [http://bugs.contribs.org/report.cgi?x_axis_field=bug_status&y_axis_field=target_milestone&product=SME+Server+9.X&format=table&action=wrap link]
 == Installing SME9 Alpha ==
 * 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.}}
-* 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/ '''here'''].  Use the x86_64 version if your hardware supports it. If possible use something like [[SME9Alpha#Zsync|ZSync]] which will transfer just the changes 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.
-:*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/
+== Reporting issues ==
-You can then do the following :
-{{tip box|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.
-* 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
-<pre>
-ifup eth0
-ifup eth1
-</pre>
-* enable ssh for access from Putty or other SSH client
-- enabling ssh now is not really needed, there isn't a long command to copy and paste anymore, so skip this if you like...This is also temporary, the hosts.allow file is templated and will be overwritten soon
-<pre>
-echo "ALL:ALL" >> /etc/hosts.allow
-service sshd reload
-</pre>
-* 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.
-<pre>
-wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682
-</pre>
-* 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:
-<pre style="white-space:normal;">
-yum --disablerepo=base,updates,extras upgrade --nogpg
-</pre>
-* post-upgrade / reboot
-<pre>
-/sbin/e-smith/signal-event post-upgrade
-/sbin/e-smith/signal-event reboot
-</pre>
-- NOTE: press the 'ESC' key to close the CentOS graphical splash screen with the blue/white bar at the bottom of the screen before it is all white - see [[bugzilla:7354]]
-* 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.
-* 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)
-<pre>
-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
-</pre>
-* Enable easier access to the server manager (modify as needed for your network)
-- I could not access the server manager from the console
-<pre>
-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
-</pre>
-Should be able to access https://yourserverip/server-manager/ now in a browser but seems that you have to log in here first - https://yourserverip/server-common/cgi-bin/login - Is that right?  I think I'm missing something...Someone fix this part of the instructions please :-) - Oh, it could be [[bugzilla:7254]] causing part of that problem...
-* 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:
-<pre>
-yum --enablerepo=smeupdates-testing upgrade
+<syntaxhighlight lang="Bash">
-</pre>
+yum --enablerepo=smeupdates-testing upgrade --nogpg
+</syntaxhighlight>
 == Some ideas for things to look for:==
+{{note box| Now go and verify the FIXED SME Server 9 bugs, see [[Verification_Queue]] for the list and link to the process.}}
-{{note box|
+* Log onto the server-manager.
-In this Alpha ISO there are going to be a lot of strange things that might appear '''before''' doing a configure and reboot.  Most of these things won't be of interest to us. Once we fix the configure and reboot part of the first-boot then we can really start looking at the issues that occur during install and first boot.
+* Go into every panel, try every option on each panel. Look at /var/log/messages and any other relevant log file
+* The testing of the above step could be made more systematic if someone could document each step. [[SME9.0_QA]] This is a copy of the SME 8 QA page, it could be adapted for SME 9
-If you notice any issues/bugs that occur '''after the initial config and reboot''' please continue to raise them.}}
@@ Line 109: / Line 54: @@
 == Discussion, help and share ==
-* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist] and in particular all threads starting with " SME on CentOS 6"
+* here are the current bugs that have been found
+{{#bugzilla:columns=id,status,cf_package:Package,summary |product=SME Server 9.X |status=!(CLOSED,VERIFIED) |sort=status,id |noresultsmessage="Well done guys, no more open bugs!"}}
+* Please consult/subscribe to the devs list for more information. [http://lists.contribs.org/mailman/listinfo/devinfo 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 [http://webchat.freenode.net?channels=SME_server&uio=Mj10cnVlJjk9dHJ1ZSYxMT03Mg13 here] to open the channel in a new browser window or tab.
+** 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. #SME_server on freenode
+== Tips ==
+==== Re-enable ssh access ====
+* 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">
+config setprop sshd status enabled acccess public PermitRootLogin yes PasswordAuthentication yes
+/sbin/e-smith/signal-event remoteaccess-update
+</syntaxhighlight>
+==== easier access to the server manager ====
+* Enable easier access to the server manager if you prefer
+<syntaxhighlight lang="Bash">
+config setprop httpd-admin ValidFrom all
+/sbin/e-smith/signal-event remoteaccess-update
+</syntaxhighlight>
 == Resources and references ==
 ==== Setting up a RPM Building environment under CentOS ====
 * [[Simple_Package_Modification|Simplest way to develop patches to submit]]
@@ Line 124: / Line 87: @@
-<noinclude>[[Category:Howto]][[Category:SME9-Development]]
+==== 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]] [[Category:SME Server Releases]]

Difference between revisions of "SME Server:9.0Alpha"

Latest revision as of 10:26, 18 March 2017

Contents

SME 9 Alpha3 (March 12th 2013 version) ISO Testing

User Feedback

Bugs

Installing SME9 Alpha

Reporting issues

Some ideas for things to look for:

Discussion, help and share

Tips

Re-enable ssh access

easier access to the server manager

Resources and references

Setting up a RPM Building environment under CentOS

Zsync

Navigation menu

Page actions

Page actions

Personal tools

Koozali SME Server

Recent activities

Koozali resources

Koozali SME Server wiki

Tools

Search