Re: [Server-devel] XS testing for Chinese English XO

2009-05-18 Thread tkkang
Great. Looking forward to the link for the alpha 0.6 version for testing.


-Original Message-
From: Martin Langhoff [mailto:martin.langh...@gmail.com]
Sent: Monday, May 18, 2009 06:57 PM
To: tkk...@nurturingasia.com
Cc: Server-devel@lists.laptop.org
Subject: Re: [Server-devel] XS testing for Chinese English  XO

On Sun, May 17, 2009 at 2:53 PM, Martin Langhoff
martin.langh...@gmail.com wrote:
 4. Have not solved the problem of not chinese character in the ds-restore
 view. When downloaded to the chinese XOs machine it display the chinese
 activity normally.

 Can you send me a zipfile (privately) of an example datastore with chinese
 characters? I'm not good with SCIM ;-)

Thanks for the sample file! I can confirm this is a problem with the
0.5.2 version -- apologies. The 0.6 code, which displays the backups
in the Moodle UI, does the right thing -- it serves the correct utf-8
chars. Once I installed the fonts-chinese package, it displayed
perfectly in the listing.

I'll post a 0.6 alpha later in the day you can test :-)



m
-- 
 martin.langh...@gmail.com
 mar...@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff



___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


[Server-devel] XS testing for Chinese English XO

2009-05-17 Thread tkkang
Greeting. This is my first message to the list! I am working on getting a XS 
server working for deployment in China this summer.

Manage to do more testing to see if I could replicate problems I had 
previously. I can repeat the following with both the chinese and english XOs 
with a 0.52 XS that has yum updated:

1. User name with space (e.g. tk kang) have problems for the moodle account 
creation. When I click on the tk kang at the moodle interface it say no 
profile have been created. I check with the moodle admin account and it confirm 
that an account was not created with the machine serialID

2. When I change back to the normal name of tkkang a moodle account is 
created and works O.K.

3. Hence chinese names (double bytes) will have the same issue as describe 
above.  

4. Have not solved the problem of not chinese character in the ds-restore view. 
When downloaded to the chinese XOs machine it display the chinese activity 
normally.

For fun I created  video of the XS bootup and my testing environment.

http://www.youtube.com/watch?v=kpZBkNWdtIMfeature=channel_page

Cheers and hope to provide more test information as we go along.
 


___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] XS testing for Chinese English XO

2009-05-17 Thread Martin Langhoff
Hi T.K.Kang,

welcome to the list, and thanks for posting a detailed outline of the
problems you are seeing.

On Sun, May 17, 2009 at 2:46 PM, tkk...@nurturingasia.com wrote:

 Greeting. This is my first message to the list! I am working on getting a
 XS server working for deployment in China this summer.

 Manage to do more testing to see if I could replicate problems I had
 previously. I can repeat the following with both the chinese and english XOs
 with a 0.52 XS that has yum updated:

 1. User name with space (e.g. tk kang) have problems for the moodle account
 creation. When I click on the tk kang at the moodle interface it say no
 profile have been created. I check with the moodle admin account and it
 confirm that an account was not created with the machine serialID

 2. When I change back to the normal name of tkkang a moodle account is
 created and works O.K.



I tried this exact scenario, and I could not reproduce the problems you are
seeing. But now I realise that it tested it with the 0.6 development
version.

Can you try updating to the development version of the XS and re-attempting
the test? You can do update with the following command:

  yum --enablerepo=olpcxs-testing update

3. Hence chinese names (double bytes) will have the same issue as describe
 above.


Can you test this too with the dev version? I do think it works...



 4. Have not solved the problem of not chinese character in the ds-restore
 view. When downloaded to the chinese XOs machine it display the chinese
 activity normally.


Can you send me a zipfile (privately) of an example datastore with chinese
characters? I'm not good with SCIM ;-)


 For fun I created  video of the XS bootup and my testing environment.

 http://www.youtube.com/watch?v=kpZBkNWdtIMfeature=channel_page


cool




m
-- 
martin.langh...@gmail.com
mar...@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff  - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] XS testing (Tony Anderson)

2008-10-10 Thread Martin Langhoff
On Sat, Oct 11, 2008 at 6:17 AM, Greg Smith [EMAIL PROTECTED] wrote:
 I don't fully understand all the vagaries of access to root, but I do
 want to warn you about having any open ports or users with password
 authentication only.

 Be really careful about dictionary style attacks.

Agreed - xs will soon have SOTP, but in the meantime, very strong
passwords are recommended.

 ClamAV is also handy, especially if you have Web, PHP, SQL ports visible

No. This is a bit of confusion -- ClamAV is for Linux machines that
want to protect Windows machines by filtering content. ClamAV does
_nothing_ for your linux machine. In particular, it does not protect
PHP or SQL engines.

cheers,



m
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] XS testing/deployment

2008-10-09 Thread Tim Moody
I couldn't ssh in until I did this step (with my credentials).  Do you plan 
to run this in an install script?  (I assume other prompted info such as 
root password and various config params are supplied automatically.)
  a.. Create an account for yourself (this is a test of basic network 
connectivity as well):
/etc/sysconfig/olpc-scripts/mkaccount wad 
http://dev.laptop.org/~wad/dsa_public_key
passwd wad

 Message: 2
 Date: Wed, 08 Oct 2008 11:11:06 +0545
 From: Tony Anderson [EMAIL PROTECTED]
 Subject: Re: [Server-devel] XS testing
 To: Martin Langhoff [EMAIL PROTECTED], Bryan Berry
 [EMAIL PROTECTED], [EMAIL PROTECTED]
 Message-ID: [EMAIL PROTECTED]
 Content-Type: text/plain; charset=ISO-8859-1; format=flowed

 Thanks for your point about the 'headless' server. The install usb must
 ensure that ssh access from an XO is sufficient to complete the install
 process. As far as I know all of our installed servers will be headless.

 This means the first two 'tests' should be changed:

  1. Reboot the server and log in as root.
  2. From an XO verify that it can connect with the server network.

 1. Reboot the server and log in as root from an XO using SSH.


___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] XS testing

2008-10-09 Thread Tony Anderson
At the moment, I am enabling password authentication for SSH. However, 
root login via SSH will not be possible. So this test would require the 
installer to log in as admin, for example. He would then su to root with 
the root password set by the install script, as needed.


As far as I know, we don't have a clear plan on how to implement key 
pairs. For example, the installer is likely to use the nearest available 
XO to administer the system. I suppose we could use the usb drive to set 
up .ssh on that XO. However, we wouldn't want the student with that XO 
to be the server administrator later on. If we shut down password 
authentication after the install, there is still the question of how a 
technician would access the server at the school in case of a subsequent 
problem.

Tony

___
Server-devel mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] XS testing

2008-10-09 Thread Martin Langhoff
On Fri, Oct 10, 2008 at 5:29 AM, Tony Anderson [EMAIL PROTECTED] wrote:
 At the moment, I am enabling password authentication for SSH. However,
 root login via SSH will not be possible. So this test would require the
 installer to log in as admin, for example. He would then su to root with
 the root password set by the install script, as needed.

There's a lot of diagnistics that can take place from an XO without
logging in... once SOTP is setup, we'll enable root logins via ssh
with passwords (from the SOTP set).

 As far as I know, we don't have a clear plan on how to implement key
 pairs.

No - we have the SOTP plan :-)

cheers,



m
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] XS testing

2008-10-09 Thread Tim Moody
How does the user get the SOTP pw list?

- Original Message - 
From: Martin Langhoff [EMAIL PROTECTED]
To: Tony Anderson [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; server-devel@lists.laptop.org
Sent: Thursday, October 09, 2008 6:48 PM
Subject: Re: [Server-devel] XS testing


 On Fri, Oct 10, 2008 at 5:29 AM, Tony Anderson [EMAIL PROTECTED] 
 wrote:
 At the moment, I am enabling password authentication for SSH. However,
 root login via SSH will not be possible. So this test would require the
 installer to log in as admin, for example. He would then su to root with
 the root password set by the install script, as needed.

 There's a lot of diagnistics that can take place from an XO without
 logging in... once SOTP is setup, we'll enable root logins via ssh
 with passwords (from the SOTP set).

 As far as I know, we don't have a clear plan on how to implement key
 pairs.

 No - we have the SOTP plan :-)

 cheers,



 m
 -- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff 

___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] XS testing

2008-10-09 Thread Martin Langhoff
On Fri, Oct 10, 2008 at 12:29 PM, Tim Moody [EMAIL PROTECTED] wrote:
 How does the user get the SOTP pw list?

OTP blueprint docs here http://wiki.laptop.org/go/School_server



m
-- 
 [EMAIL PROTECTED]
 [EMAIL PROTECTED] -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] XS testing

2008-10-07 Thread Tony Anderson
Thanks for your point about the 'headless' server. The install usb must 
ensure that ssh access from an XO is sufficient to complete the install 
process. As far as I know all of our installed servers will be headless.

This means the first two 'tests' should be changed:

  1. Reboot the server and log in as root.
  2. From an XO verify that it can connect with the server network.

1. Reboot the server and log in as root from an XO using SSH.

I don't think it makes any difference in the implementation if the usb 
drive is used to install XS at the 'depot' or at the school. At the 
'depot', it may be desirable to have the servers boot from the network. 
As I understand it, this can be done using the same files used to create 
the usb drive.

Incidentally, one point in favor of a laptop as server is that it's 
battery may come in handy in schools with unstable power.

Tony

Martin Langhoff wrote:
 On Tue, Oct 7, 2008 at 7:04 AM, Tony Anderson [EMAIL PROTECTED] wrote:
 What I think we need urgently is a simple procedure someone in the field can
 use to verify an XS installation. It has to be simple and effective, because
 this person is also bringing up a school-set of XOs.
 
 This is great. I had not thought of this, but the moment Bryan
 mentioned I clicked with it. Excellent idea.
 
 Our model is that the installer has a usb drive with XS to install at the
 school. We hope that the embedded install script will provide a complete
 configuration including network, firewall, and Moodle.
 
 This is one of the possible scenarios, and likely to be common in
 pilots. In large deployments it makes sense to preinstall the XS image
 at HQ because
 
  - it can be done in parallel
  - OS install can be network-based
  - Additional content can be installed via the network
  - checks that the machine works while there's a good chance you have
 spare parts too! :-)
 
 Which is a long-winded way of saying: we need to take multiple
 scenarios into account. In some of the scenarios the user may not have
 root access or shell access. In some scenarios, the machine will be
 completely headless...
 
 The installer should
 then do things like:

 1. Reboot the server and log in as root.
 2. From an XO verify that it can connect with the server network.
 3. From an XO verify that the 'schoolserver' link on the browser displays
 the Moodle site page.
 4. From an XO verify that the browser can access the OLPC Wiki.
 5. Verify that the XO sees ejabberd (telepathy-gabble)
 6. Verify that two XOs connected via ejabberd can see and 'chat' with each
 other.
 7. Verify that an XO receives access denied attempting to download an exe
 file
 8. Verify that the XO can log in to a Moodle course with the correct student
 identification.
 
 Good list. Here's my challenge: I think we can do everything in the
 list without logging in / using the shell console at all on the XS.
 
 Naturally, I am hoping for suggestions of additional essential server
 capabilities that need to be tested (e.g. verifying backup/restore of the
 journal/datastore, access the library, install an activity).
 However, we need to be careful to keep it simple and avoid testing features.
 
 Agreed. If the tests are simple enough, they can even be performed by
 a teacher, which means that the local team has a goodtool to use
 before they send a technician to the field.
 
 So we'd have 2 sets:
  - tests you can run from an XO
  - addittional tests you can run if you have shell / root access
 
 what do you think?
 
 
 
 m

___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


[Server-devel] XS testing

2008-10-06 Thread Tony Anderson
Hi,

I think there are several levels of testing, e.g. regression, 
functional, and stress. I am not planning on anything special for any
of these.

What I think we need urgently is a simple procedure someone in the field 
can use to verify an XS installation. It has to be simple and effective, 
because this person is also bringing up a school-set of XOs.

Our model is that the installer has a usb drive with XS to install at 
the school. We hope that the embedded install script will provide a 
complete configuration including network, firewall, and Moodle. The 
installer should then do things like:

1. Reboot the server and log in as root.
2. From an XO verify that it can connect with the server network.
3. From an XO verify that the 'schoolserver' link on the browser 
displays the Moodle site page.
4. From an XO verify that the browser can access the OLPC Wiki.
5. Verify that the XO sees ejabberd (telepathy-gabble)
6. Verify that two XOs connected via ejabberd can see and 'chat' with 
each other.
7. Verify that an XO receives access denied attempting to download an 
exe file
8. Verify that the XO can log in to a Moodle course with the correct 
student identification.

Naturally, I am hoping for suggestions of additional essential server 
capabilities that need to be tested (e.g. verifying backup/restore of 
the journal/datastore, access the library, install an activity).
However, we need to be careful to keep it simple and avoid testing 
features. (For example, verifying that Moodle pops up a pdf correctly is 
not a test to determine if it is running. That test is needed back in 
the development lab.)

Tony


  Regarding the testing methods, I believe that Tony is hoping to hear
   that his work creating testing scripts won't be totally orphaned.

Oh, is he working on some? Fantastic! Tony, can you post your notes /
plans / intentions!  :-)


___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel