Re: [Server-devel] The three step XSCE demo

2013-11-23 Thread David Farning 
I'll add this and Miguel's info under
http://wiki.laptop.org/go/XS_Community_Edition/0.5/Hacking . I had to
order a new 8GB memory stick for my laptop. It was swapping really
badly with 4GB :(

On Fri, Nov 22, 2013 at 12:15 PM, Tim Moody  wrote:
> I take a middle of the road approach, using vbox, but not vagrant.
>
> Some time ago I created a vbox with a minimal FC18 64 bit install, which I
> call FC18-64Base and which I periodically yum update and into which I put my
> personal account, make myself a sudoer, etc., turn on sshd if necessary.
>
> I then did a vbox clone of the that vm and performed Miguel's setup - get
> git and ansible and update ansible, which I call XSCEAnsibleBase with two
> nics, one for wan and one for lan. A vbox clone takes a little over a
> minute.
>
> When I want to test the server I do a vbox clone of XSCEAnsibleBase and name
> it XSCEAnsibleTest (I usually generate new mac addresses to be safe).
>
> Then I git clone https://github.com/XSCE/xsce --depth 1 or my working
> branch.  (--depth 1 saves a lot of time on the git clone)
>
> I connect XSCEAnsibleTest to my home network on wan so I can ssh in and to
> an isolated access point on the lan to connect XOs.  I can also sftp into
> the server using my account.
>
> I am fortunate to have some XOs for testing, but I have also used SoaS,
> again running as a vbox vm.  In that case I could eliminate the extra access
> point and just connect the server and client vms on the lan side over a
> virtual network internal to vbox.  Awhile back I successfully ran three SoaS
> vms simultaneously on an old Dell laptop to test collaboration.
>
>
>
>> -Original Message- From: server-devel-requ...@lists.laptop.org
>> Sent: Friday, November 22, 2013 12:00 PM
>> To: server-devel@lists.laptop.org
>> Subject: Server-devel Digest, Vol 79, Issue 17
>>
>> Send Server-devel mailing list submissions to
>> server-devel@lists.laptop.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://lists.laptop.org/listinfo/server-devel
>> or, via email, send a message with subject or body 'help' to
>> server-devel-requ...@lists.laptop.org
>>
>> You can reach the person managing the list at
>> server-devel-ow...@lists.laptop.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Server-devel digest..."
>>
>>
>> Today's Topics:
>>
>>   1. Re: The three step XSCE demo! (Miguel Gonz?lez)
>>   2. Re: The three step XSCE demo! (David Farning)
>>   3. Re: The three step XSCE demo! (Thomas Gilliard)
>>
>>
>> --
>>
>> Message: 1
>> Date: Thu, 21 Nov 2013 19:27:42 +0100
>> From: Miguel Gonz?lez 
>> To: Anish Mangal 
>> Cc: server-devel 
>> Subject: Re: [Server-devel] The three step XSCE demo!
>> Message-ID:
>> 
>> Content-Type: text/plain; charset=UTF-8
>>
>> I'm going to describe in detail my current dev environment. Hopefully,
>> it could be useful for somebody.
>>
>>
>> Pre-requisites
>> 
>>
>> I'm using a VirtualBox and installing a virtual machine with Fedora18.
>>
>> I'm also use vagrant to automatically manage the virtual machine.
>> There packages available from its website [1]. I'm currently using
>> version 1.3.4.
>>
>>
>> Booting a fresh virtual machine
>> 
>>
>> The file Vagrantfile defines a basic image to download (= vagrant box)
>> and allows to add configuration details like network configuration.
>>
>> This is a simplified but fully functional version:
>>
>> ```ruby
>> # -*- mode: ruby -*-
>> # vi: set ft=ruby :
>>
>> VAGRANTFILE_API_VERSION = "2"
>>
>> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>>  config.vm.box = "fedora-18-x86_64"
>>  config.vm.box_url =
>>
>> "http://puppet-vagrant-boxes.puppetlabs.com/fedora-18-x64-vbox4210-nocm.box";
>>
>>  # config.vm.network :public_network
>>
>>  # config.ssh.forward_agent = true
>>
>>  config.vm.synced_folder ".", "/vagrant", :disabled => true
>>
>>   config.vm.provider :virtualbox do |vb|
>>   # vb.gui = true
>>   end
>>
>> end
>> ```
>>
>> With this command, vagrant downloads the basic image (only the first
>> time) and deploys and boots up the virtual machine:
>>
>> ```
>> $ vagrant up
>> ```
>>
>

Re: [Server-devel] The three step XSCE demo

2013-11-22 Thread Tim Moody 

Forgot to mention that on XSCEAnsibleBase you should also

wget http://xsce.activitycentral.com/downloads/xs-config-999-1.noarch.rpm

yum -y localinstall xs-config-999-1.noarch.rpm


Tim

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

Re: [Server-devel] The three step XSCE demo

2013-11-22 Thread Tim Moody 

I take a middle of the road approach, using vbox, but not vagrant.

Some time ago I created a vbox with a minimal FC18 64 bit install, which I 
call FC18-64Base and which I periodically yum update and into which I put my 
personal account, make myself a sudoer, etc., turn on sshd if necessary.


I then did a vbox clone of the that vm and performed Miguel's setup - get 
git and ansible and update ansible, which I call XSCEAnsibleBase with two 
nics, one for wan and one for lan. A vbox clone takes a little over a 
minute.


When I want to test the server I do a vbox clone of XSCEAnsibleBase and name 
it XSCEAnsibleTest (I usually generate new mac addresses to be safe).


Then I git clone https://github.com/XSCE/xsce --depth 1 or my working 
branch.  (--depth 1 saves a lot of time on the git clone)


I connect XSCEAnsibleTest to my home network on wan so I can ssh in and to 
an isolated access point on the lan to connect XOs.  I can also sftp into 
the server using my account.


I am fortunate to have some XOs for testing, but I have also used SoaS, 
again running as a vbox vm.  In that case I could eliminate the extra access 
point and just connect the server and client vms on the lan side over a 
virtual network internal to vbox.  Awhile back I successfully ran three SoaS 
vms simultaneously on an old Dell laptop to test collaboration.




-Original Message- 
From: server-devel-requ...@lists.laptop.org

Sent: Friday, November 22, 2013 12:00 PM
To: server-devel@lists.laptop.org
Subject: Server-devel Digest, Vol 79, Issue 17

Send Server-devel mailing list submissions to
server-devel@lists.laptop.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.laptop.org/listinfo/server-devel
or, via email, send a message with subject or body 'help' to
server-devel-requ...@lists.laptop.org

You can reach the person managing the list at
server-devel-ow...@lists.laptop.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Server-devel digest..."


Today's Topics:

  1. Re: The three step XSCE demo! (Miguel Gonz?lez)
  2. Re: The three step XSCE demo! (David Farning)
  3. Re: The three step XSCE demo! (Thomas Gilliard)


--

Message: 1
Date: Thu, 21 Nov 2013 19:27:42 +0100
From: Miguel Gonz?lez 
To: Anish Mangal 
Cc: server-devel 
Subject: Re: [Server-devel] The three step XSCE demo!
Message-ID:

Content-Type: text/plain; charset=UTF-8

I'm going to describe in detail my current dev environment. Hopefully,
it could be useful for somebody.


Pre-requisites


I'm using a VirtualBox and installing a virtual machine with Fedora18.

I'm also use vagrant to automatically manage the virtual machine.
There packages available from its website [1]. I'm currently using
version 1.3.4.


Booting a fresh virtual machine


The file Vagrantfile defines a basic image to download (= vagrant box)
and allows to add configuration details like network configuration.

This is a simplified but fully functional version:

```ruby
# -*- mode: ruby -*-
# vi: set ft=ruby :

VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
 config.vm.box = "fedora-18-x86_64"
 config.vm.box_url =
"http://puppet-vagrant-boxes.puppetlabs.com/fedora-18-x64-vbox4210-nocm.box";

 # config.vm.network :public_network

 # config.ssh.forward_agent = true

 config.vm.synced_folder ".", "/vagrant", :disabled => true

  config.vm.provider :virtualbox do |vb|
  # vb.gui = true
  end

end
```

With this command, vagrant downloads the basic image (only the first
time) and deploys and boots up the virtual machine:

```
$ vagrant up
```


Then, to access the vagrant virtual machine:

```
$ vagrant ssh
```

Installing XSCE


Inside the vm now it's possible to follow the install instructions
[2]. I'm copying them below:


Install git and ansible (for dependencies):

```
sudo su -
yum install -y git ansible
```

Update ansible to use a :

```
cd ~/
git clone https://github.com/ansible/ansible.git
cd ansible
git checkout 07b59da99
python setup.py install
```

Clone the XSCE git repo and run the actual setup:

```
cd ~/
git clone https://github.com/XSCE/xsce
cd xsce/
./runansible
```

XSCE autoconfigures itself according to the interfaces it detects. If
XSCE only detects one interface, as in this setup, it configures
itself in "appliance mode". But the service are not reachable because
`eth0` in the host machine is using a subnetwork.

One solutions is define a port forward for every service. Other
solution, the one I'm using currently is to add a new interface
**after installing XSCE**.

To do it, from the host machine I halt the vm, uncomment a line in
Vagrantfile and run again:

```
$ vagrant halt
$ vim Vagrantfile
... uncomment # config.vm.network :public_network
$ vagra

Re: [Server-devel] The three step XSCE demo!

2013-11-21 Thread Thomas Gilliard 


On 11/21/2013 12:46 PM, David Farning wrote:

Should I turn this into a wiki page?

On Thu, Nov 21, 2013 at 12:27 PM, Miguel González
 wrote:

I'm going to describe in detail my current dev environment. Hopefully,
it could be useful for somebody.


I have some pertenent  info here:
General Info:
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Advanced_Topics#XS_Community_Edition
XSCE and DXS VM's
http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Advanced_Topics#XSCE_in_VirtualBox

Tom Gilliard

Pre-requisites


I'm using a VirtualBox and installing a virtual machine with Fedora18.

I'm also use vagrant to automatically manage the virtual machine.
There packages available from its website [1]. I'm currently using
version 1.3.4.


Booting a fresh virtual machine


The file Vagrantfile defines a basic image to download (= vagrant box)
and allows to add configuration details like network configuration.

This is a simplified but fully functional version:

```ruby
# -*- mode: ruby -*-
# vi: set ft=ruby :

VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
   config.vm.box = "fedora-18-x86_64"
   config.vm.box_url =
"http://puppet-vagrant-boxes.puppetlabs.com/fedora-18-x64-vbox4210-nocm.box";

   # config.vm.network :public_network

   # config.ssh.forward_agent = true

   config.vm.synced_folder ".", "/vagrant", :disabled => true

config.vm.provider :virtualbox do |vb|
# vb.gui = true
end

end
```

With this command, vagrant downloads the basic image (only the first
time) and deploys and boots up the virtual machine:

```
$ vagrant up
```


Then, to access the vagrant virtual machine:

```
$ vagrant ssh
```

Installing XSCE


Inside the vm now it's possible to follow the install instructions
[2]. I'm copying them below:


Install git and ansible (for dependencies):

```
sudo su -
yum install -y git ansible
```

Update ansible to use a :

```
cd ~/
git clone https://github.com/ansible/ansible.git
cd ansible
git checkout 07b59da99
python setup.py install
```

Clone the XSCE git repo and run the actual setup:

```
cd ~/
git clone https://github.com/XSCE/xsce
cd xsce/
./runansible
```

XSCE autoconfigures itself according to the interfaces it detects. If
XSCE only detects one interface, as in this setup, it configures
itself in "appliance mode". But the service are not reachable because
`eth0` in the host machine is using a subnetwork.

One solutions is define a port forward for every service. Other
solution, the one I'm using currently is to add a new interface
**after installing XSCE**.

To do it, from the host machine I halt the vm, uncomment a line in
Vagrantfile and run again:

```
$ vagrant halt
$ vim Vagrantfile
... uncomment # config.vm.network :public_network
$ vagrant up
$ vagrant ssh
```

The guest machine has 2 interfaces, the internal subnet and another
bridged to the same LAN as the host

```
[vagrant@schoolserver ~]$ ip a
1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
 inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast
state UP qlen 1000
 link/ether 08:00:27:f0:90:8a brd ff:ff:ff:ff:ff:ff
 inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
 inet6 fe80::a00:27ff:fef0:908a/64 scope link
valid_lft forever preferred_lft forever
3: eth1:  mtu 1500 qdisc pfifo_fast
state UP qlen 1000
 link/ether 08:00:27:ca:fe:ca brd ff:ff:ff:ff:ff:ff
 inet 192.168.0.100/24 brd 192.168.0.255 scope global eth1
 inet6 fe80::a00:27ff:feca:feca/64 scope link
valid_lft forever preferred_lft forever
```

And now all the services can be accessed from the LAN by any device
for testing, in this case, using 192.168.0.100.


The main problem here is that running XSCE installation process again
(`./runansible`) will mess the configuration because **it will find 2
interfaces now**. So, before configuring the server again, disable
eth1:


```
[root@schoolserver xsce]# ifconfig eth1 down
[root@schoolserver xsce]# ./runansible
```


More..



- To begin with a new fresh virtual machine:

```
$ vagrant destroy
$ vagrant up
```


- Uncommenting `config.ssh.forward_agent = true` in Vagrantfile, it is
possible to write in a git repo from the guest using host's keys.


- Take a look to https://github.com/XSCE/xsce/pull/76 when we are
trying to simplify adding new *roles* (services) to XSCE.



1: http://downloads.vagrantup.com/

2: https://github.com/XSCE/xsce/blob/master/docs/INSTALL.rst

On Wed, Nov 20, 2013 at 11:01 AM, Anish Mangal
 wrote:

Hi Sebastian,

You should be able to download the image from here (Thanks to Thomas Gillard
for uploading the file):
http://people.sugarlabs.org/Tgillard/XSCE.ova

Please verify the md5sum once you have downloaded the file.
56a4f141b564b0d2bd65c543a5e585c6

About your question on dev environment I am ccing Santi and Miguel who can
answer

Re: [Server-devel] The three step XSCE demo!

2013-11-21 Thread David Farning 
Should I turn this into a wiki page?

On Thu, Nov 21, 2013 at 12:27 PM, Miguel González
 wrote:
> I'm going to describe in detail my current dev environment. Hopefully,
> it could be useful for somebody.
>
>
> Pre-requisites
> 
>
> I'm using a VirtualBox and installing a virtual machine with Fedora18.
>
> I'm also use vagrant to automatically manage the virtual machine.
> There packages available from its website [1]. I'm currently using
> version 1.3.4.
>
>
> Booting a fresh virtual machine
> 
>
> The file Vagrantfile defines a basic image to download (= vagrant box)
> and allows to add configuration details like network configuration.
>
> This is a simplified but fully functional version:
>
> ```ruby
> # -*- mode: ruby -*-
> # vi: set ft=ruby :
>
> VAGRANTFILE_API_VERSION = "2"
>
> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>   config.vm.box = "fedora-18-x86_64"
>   config.vm.box_url =
> "http://puppet-vagrant-boxes.puppetlabs.com/fedora-18-x64-vbox4210-nocm.box";
>
>   # config.vm.network :public_network
>
>   # config.ssh.forward_agent = true
>
>   config.vm.synced_folder ".", "/vagrant", :disabled => true
>
>config.vm.provider :virtualbox do |vb|
># vb.gui = true
>end
>
> end
> ```
>
> With this command, vagrant downloads the basic image (only the first
> time) and deploys and boots up the virtual machine:
>
> ```
> $ vagrant up
> ```
>
>
> Then, to access the vagrant virtual machine:
>
> ```
> $ vagrant ssh
> ```
>
> Installing XSCE
> 
>
> Inside the vm now it's possible to follow the install instructions
> [2]. I'm copying them below:
>
>
> Install git and ansible (for dependencies):
>
> ```
> sudo su -
> yum install -y git ansible
> ```
>
> Update ansible to use a :
>
> ```
> cd ~/
> git clone https://github.com/ansible/ansible.git
> cd ansible
> git checkout 07b59da99
> python setup.py install
> ```
>
> Clone the XSCE git repo and run the actual setup:
>
> ```
> cd ~/
> git clone https://github.com/XSCE/xsce
> cd xsce/
> ./runansible
> ```
>
> XSCE autoconfigures itself according to the interfaces it detects. If
> XSCE only detects one interface, as in this setup, it configures
> itself in "appliance mode". But the service are not reachable because
> `eth0` in the host machine is using a subnetwork.
>
> One solutions is define a port forward for every service. Other
> solution, the one I'm using currently is to add a new interface
> **after installing XSCE**.
>
> To do it, from the host machine I halt the vm, uncomment a line in
> Vagrantfile and run again:
>
> ```
> $ vagrant halt
> $ vim Vagrantfile
> ... uncomment # config.vm.network :public_network
> $ vagrant up
> $ vagrant ssh
> ```
>
> The guest machine has 2 interfaces, the internal subnet and another
> bridged to the same LAN as the host
>
> ```
> [vagrant@schoolserver ~]$ ip a
> 1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> inet6 ::1/128 scope host
>valid_lft forever preferred_lft forever
> 2: eth0:  mtu 1500 qdisc pfifo_fast
> state UP qlen 1000
> link/ether 08:00:27:f0:90:8a brd ff:ff:ff:ff:ff:ff
> inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
> inet6 fe80::a00:27ff:fef0:908a/64 scope link
>valid_lft forever preferred_lft forever
> 3: eth1:  mtu 1500 qdisc pfifo_fast
> state UP qlen 1000
> link/ether 08:00:27:ca:fe:ca brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.100/24 brd 192.168.0.255 scope global eth1
> inet6 fe80::a00:27ff:feca:feca/64 scope link
>valid_lft forever preferred_lft forever
> ```
>
> And now all the services can be accessed from the LAN by any device
> for testing, in this case, using 192.168.0.100.
>
>
> The main problem here is that running XSCE installation process again
> (`./runansible`) will mess the configuration because **it will find 2
> interfaces now**. So, before configuring the server again, disable
> eth1:
>
>
> ```
> [root@schoolserver xsce]# ifconfig eth1 down
> [root@schoolserver xsce]# ./runansible
> ```
>
>
> More..
> 
>
>
> - To begin with a new fresh virtual machine:
>
> ```
> $ vagrant destroy
> $ vagrant up
> ```
>
>
> - Uncommenting `config.ssh.forward_agent = true` in Vagrantfile, it is
> possible to write in a git repo from the guest using host's keys.
>
>
> - Take a look to https://github.com/XSCE/xsce/pull/76 when we are
> trying to simplify adding new *roles* (services) to XSCE.
>
>
>
> 1: http://downloads.vagrantup.com/
>
> 2: https://github.com/XSCE/xsce/blob/master/docs/INSTALL.rst
>
> On Wed, Nov 20, 2013 at 11:01 AM, Anish Mangal
>  wrote:
>> Hi Sebastian,
>>
>> You should be able to download the image from here (Thanks to Thomas Gillard
>> for uploading the file):
>> http://people.sugarlabs.org/Tgillard/XSCE.ova
>>
>> Please verify the md5sum once you have downloaded the file.
>> 56a4f141b564b0d2bd65c543a5e585c6
>>
>> About your question on dev environment I am ccing Santi and Miguel who can
>>

Re: [Server-devel] The three step XSCE demo!

2013-11-21 Thread Miguel González 
I'm going to describe in detail my current dev environment. Hopefully,
it could be useful for somebody.


Pre-requisites


I'm using a VirtualBox and installing a virtual machine with Fedora18.

I'm also use vagrant to automatically manage the virtual machine.
There packages available from its website [1]. I'm currently using
version 1.3.4.


Booting a fresh virtual machine


The file Vagrantfile defines a basic image to download (= vagrant box)
and allows to add configuration details like network configuration.

This is a simplified but fully functional version:

```ruby
# -*- mode: ruby -*-
# vi: set ft=ruby :

VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.box = "fedora-18-x86_64"
  config.vm.box_url =
"http://puppet-vagrant-boxes.puppetlabs.com/fedora-18-x64-vbox4210-nocm.box";

  # config.vm.network :public_network

  # config.ssh.forward_agent = true

  config.vm.synced_folder ".", "/vagrant", :disabled => true

   config.vm.provider :virtualbox do |vb|
   # vb.gui = true
   end

end
```

With this command, vagrant downloads the basic image (only the first
time) and deploys and boots up the virtual machine:

```
$ vagrant up
```


Then, to access the vagrant virtual machine:

```
$ vagrant ssh
```

Installing XSCE


Inside the vm now it's possible to follow the install instructions
[2]. I'm copying them below:


Install git and ansible (for dependencies):

```
sudo su -
yum install -y git ansible
```

Update ansible to use a :

```
cd ~/
git clone https://github.com/ansible/ansible.git
cd ansible
git checkout 07b59da99
python setup.py install
```

Clone the XSCE git repo and run the actual setup:

```
cd ~/
git clone https://github.com/XSCE/xsce
cd xsce/
./runansible
```

XSCE autoconfigures itself according to the interfaces it detects. If
XSCE only detects one interface, as in this setup, it configures
itself in "appliance mode". But the service are not reachable because
`eth0` in the host machine is using a subnetwork.

One solutions is define a port forward for every service. Other
solution, the one I'm using currently is to add a new interface
**after installing XSCE**.

To do it, from the host machine I halt the vm, uncomment a line in
Vagrantfile and run again:

```
$ vagrant halt
$ vim Vagrantfile
... uncomment # config.vm.network :public_network
$ vagrant up
$ vagrant ssh
```

The guest machine has 2 interfaces, the internal subnet and another
bridged to the same LAN as the host

```
[vagrant@schoolserver ~]$ ip a
1: lo:  mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 08:00:27:f0:90:8a brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
inet6 fe80::a00:27ff:fef0:908a/64 scope link
   valid_lft forever preferred_lft forever
3: eth1:  mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 08:00:27:ca:fe:ca brd ff:ff:ff:ff:ff:ff
inet 192.168.0.100/24 brd 192.168.0.255 scope global eth1
inet6 fe80::a00:27ff:feca:feca/64 scope link
   valid_lft forever preferred_lft forever
```

And now all the services can be accessed from the LAN by any device
for testing, in this case, using 192.168.0.100.


The main problem here is that running XSCE installation process again
(`./runansible`) will mess the configuration because **it will find 2
interfaces now**. So, before configuring the server again, disable
eth1:


```
[root@schoolserver xsce]# ifconfig eth1 down
[root@schoolserver xsce]# ./runansible
```


More..



- To begin with a new fresh virtual machine:

```
$ vagrant destroy
$ vagrant up
```


- Uncommenting `config.ssh.forward_agent = true` in Vagrantfile, it is
possible to write in a git repo from the guest using host's keys.


- Take a look to https://github.com/XSCE/xsce/pull/76 when we are
trying to simplify adding new *roles* (services) to XSCE.



1: http://downloads.vagrantup.com/

2: https://github.com/XSCE/xsce/blob/master/docs/INSTALL.rst

On Wed, Nov 20, 2013 at 11:01 AM, Anish Mangal
 wrote:
> Hi Sebastian,
>
> You should be able to download the image from here (Thanks to Thomas Gillard
> for uploading the file):
> http://people.sugarlabs.org/Tgillard/XSCE.ova
>
> Please verify the md5sum once you have downloaded the file.
> 56a4f141b564b0d2bd65c543a5e585c6
>
> About your question on dev environment I am ccing Santi and Miguel who can
> answer it best. It may depend on what part of the server you want to
> contribute to, but I think you should mostly be able to get away with just a
> VM image. I don't believe anyone has tried a chroot env (though I could be
> wrong) but it _might_ be possible.
>
> Also, for testing with real clients (like xo laptops) you are probably going
> to need something for the LAN side (an access point). There are a

Re: [Server-devel] The three step XSCE demo!

2013-11-20 Thread Anish Mangal 
On Wed, Nov 20, 2013 at 2:31 PM, David Farning  wrote:

> Can everybody sit back and have a tasty beverage of their choice to
> celebrate?
>
> On the surface, this email might seem simple. Below the surface this
> is a turning point in the project.
>
> "Actually I'm more interested in what a good dev environment would be
> in order to contribute."
>
> This is exactly what we have been targeting for that last year. A busy
> deployment support person who doesn't really can about the School
> Server or its technology. He just cares about how to build on XSCE to
> meet his specific deployment needs.
>
> If, and this is a very big if, we have done a good job designing the
> XSCE project and the XSCE product, Sebastian will find that it is more
> effective to do his work as an plug-in-service on XSCE rather than
> head off in his own.
>
> The open source theory behind this the notion of creating a modular
> and collaborative base which others use to solve their own specific
> problems.
>
> The business theory is that of Lead Users. (
> http://en.wikipedia.org/wiki/Lead_user ) As an upstream, we don't have
> a complete understanding of users needs and priorities. Working with
> lead users, enables us to understand and meet their individual needs
> while gather information to create abstract solutions which apply to
> other users as well.
>
> It looks like 0.5 is coming along nicely. There is a lot of green in
> the task matrix at
> http://wiki.laptop.org/go/XS_Community_Edition/0.5/Ansible_Progress .
>
> While there are several interesting features at
> http://wiki.laptop.org/go/XS_Community_Edition/Features for 0.6, there
> is no cohesive theme to 'unite' us together as a project. I would like
> to suggest that the theme for 0.6 is making XSCE as easy and desirable
> as possible for lead users like Sebastian.
>
> Much like the initial statement, "Actually I'm more interested in what
> a good dev environment would be in order to contribute." which seems
> simple, but is actually a tipping point for the project. Engaging lead
> users seems simple, yet is rather subtle. On first glace there is:
>

Welcome to the "we should make it simple and have awesome documentation"
pack :-)

While the hackers here crank out 0.5 (they have been writing crazy amounts
of code lately), lets try to figure out ways to do just what you mentioned,
by breaking into small actionable tasks and/or features. This process
actually started a few weeks ago (with the switch to github), but there's
tons more to do.


> 1. Documentation about the the project and it's technologies.
>

+1. I guess a wiki is the best place to do it, but we could think of more
interactive ways (like video tutorials etc. Miguel's github tutorial video
has already been viewed 27+ times http://www.youtube.com/watch?v=CEE85F3Zjcs
).


> 2. Simple ways to install,test, and develop XSCE.
>

1. There is some work being done here. Santi was working on a test script
that would run a battery of tests once the XSCE installs. I think that work
could resume post 0.5. Think of it as an automated commit-build-test env.
(I don't think there's a feature page for this yet).

2. Providing simple install images (VM appliances, XO images etc.) Again
could be worked upon post 0.5 (Again, don't think there is a feature page
yet).

3. Develop: It should already be easy to develop, thanks to ansible, save
for the documentation and the on-ramp part.

4. 


> 3. Simple ways to interact with the community and transfer knowledge
> and technology.
>
>
1. End user documentation (I want to approach this more as a process that
results in end user documentation, than a concentrated effort, since this
is going to be an ongoing thing). It is going to take a kickstart though.

2. Refer you to the crazy-ideas section here
http://lists.laptop.org/pipermail/server-devel/2013-October/006823.html :-)

3.  :-P


> More subtly, there are decisions about encapsulation. What does a new
> developer need to know to get started? What complexity should be
> hidden and what should be exposed to new developers via best
> practices, APIs, and community processes.
>
> The challenge is to create an on-ramp to engage a broader audience at
> a pace which enables them to use XSCE to meet their needs while
> avoiding the tendency to create a wall between 'us' them 'them.'
>
>
>
> On Tue, Nov 19, 2013 at 11:24 PM, Sebastian Silva
>  wrote:
> > Thanks that will be simpler. Actually I'm more interested in what a good
> dev
> > environment would be in order to contribute.
> > Do I need to make a fedora chroot?
> >
> > Regards,
> > Sebastian
> >
> > El 19/11/13 09:51, Anish Mangal escribió:
> >
> > I tried uploading it to xsce.activitycentral.com, but I ran out of
> space in
> > my user dir. Normally the appliance is 1.3G, but this also has 400mb of
> IIAB
> > test dataset.
> >
> > I'll give it another shot in another area where there is some free space,
> > and get back.
> >
> >
> > On Tue, Nov 19, 2013 at 7:24 PM, Sebastian

Re: [Server-devel] The three step XSCE demo!

2013-11-20 Thread Anish Mangal 
Hi Sebastian,

You should be able to download the image from here (Thanks to Thomas
Gillard for uploading the file):
http://people.sugarlabs.org/Tgillard/XSCE.ova

Please verify the md5sum once you have downloaded the file.
56a4f141b564b0d2bd65c543a5e585c6

About your question on dev environment I am ccing Santi and Miguel who can
answer it best. It may depend on what part of the server you want to
contribute to, but I think you should mostly be able to get away with just
a VM image. I don't believe anyone has tried a chroot env (though I could
be wrong) but it _might_ be possible.

Also, for testing with real clients (like xo laptops) you are probably
going to need something for the LAN side (an access point). There are a few
permutations here, but I will step back and let more the technical experts
converse :-)

Cheers,
Anish



On Wed, Nov 20, 2013 at 10:54 AM, Sebastian Silva  wrote:

>  Thanks that will be simpler. Actually I'm more interested in what a good
> dev environment would be in order to contribute.
> Do I need to make a fedora chroot?
>
> Regards,
> Sebastian
>
> El 19/11/13 09:51, Anish Mangal escribió:
>
> I tried uploading it to xsce.activitycentral.com, but I ran out of space
> in my user dir. Normally the appliance is 1.3G, but this also has 400mb of
> IIAB test dataset.
>
>  I'll give it another shot in another area where there is some free
> space, and get back.
>
>
> On Tue, Nov 19, 2013 at 7:24 PM, Sebastian Silva <
> sebast...@fuentelibre.org> wrote:
>
>> Hi
>> I tried this but google drive problematic to download from as it requires
>> to download from a browser. Not adequate for 1.6gb. Let me know if I can
>> pick it up from a regular download place. Why is it so big?
>>
>> Regards,
>> Sebastian
>>
>> El 17/11/13 20:48, Anish Mangal escribió:
>>
>>  Download the XSCE Virtualbox appliance from here
>>> https://docs.google.com/file/d/0B3eW2YPe6koIVXRVbDhSR0xXQ1U (approx 1.6
>>> GB)
>>>
>>
>>
>
>
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel

Re: [Server-devel] The three step XSCE demo!

2013-11-20 Thread David Farning 
Can everybody sit back and have a tasty beverage of their choice to celebrate?

On the surface, this email might seem simple. Below the surface this
is a turning point in the project.

"Actually I'm more interested in what a good dev environment would be
in order to contribute."

This is exactly what we have been targeting for that last year. A busy
deployment support person who doesn't really can about the School
Server or its technology. He just cares about how to build on XSCE to
meet his specific deployment needs.

If, and this is a very big if, we have done a good job designing the
XSCE project and the XSCE product, Sebastian will find that it is more
effective to do his work as an plug-in-service on XSCE rather than
head off in his own.

The open source theory behind this the notion of creating a modular
and collaborative base which others use to solve their own specific
problems.

The business theory is that of Lead Users. (
http://en.wikipedia.org/wiki/Lead_user ) As an upstream, we don't have
a complete understanding of users needs and priorities. Working with
lead users, enables us to understand and meet their individual needs
while gather information to create abstract solutions which apply to
other users as well.

It looks like 0.5 is coming along nicely. There is a lot of green in
the task matrix at
http://wiki.laptop.org/go/XS_Community_Edition/0.5/Ansible_Progress .

While there are several interesting features at
http://wiki.laptop.org/go/XS_Community_Edition/Features for 0.6, there
is no cohesive theme to 'unite' us together as a project. I would like
to suggest that the theme for 0.6 is making XSCE as easy and desirable
as possible for lead users like Sebastian.

Much like the initial statement, "Actually I'm more interested in what
a good dev environment would be in order to contribute." which seems
simple, but is actually a tipping point for the project. Engaging lead
users seems simple, yet is rather subtle. On first glace there is:
1. Documentation about the the project and it's technologies.
2. Simple ways to install,test, and develop XSCE.
3. Simple ways to interact with the community and transfer knowledge
and technology.

More subtly, there are decisions about encapsulation. What does a new
developer need to know to get started? What complexity should be
hidden and what should be exposed to new developers via best
practices, APIs, and community processes.

The challenge is to create an on-ramp to engage a broader audience at
a pace which enables them to use XSCE to meet their needs while
avoiding the tendency to create a wall between 'us' them 'them.'



On Tue, Nov 19, 2013 at 11:24 PM, Sebastian Silva
 wrote:
> Thanks that will be simpler. Actually I'm more interested in what a good dev
> environment would be in order to contribute.
> Do I need to make a fedora chroot?
>
> Regards,
> Sebastian
>
> El 19/11/13 09:51, Anish Mangal escribió:
>
> I tried uploading it to xsce.activitycentral.com, but I ran out of space in
> my user dir. Normally the appliance is 1.3G, but this also has 400mb of IIAB
> test dataset.
>
> I'll give it another shot in another area where there is some free space,
> and get back.
>
>
> On Tue, Nov 19, 2013 at 7:24 PM, Sebastian Silva 
> wrote:
>>
>> Hi
>> I tried this but google drive problematic to download from as it requires
>> to download from a browser. Not adequate for 1.6gb. Let me know if I can
>> pick it up from a regular download place. Why is it so big?
>>
>> Regards,
>> Sebastian
>>
>> El 17/11/13 20:48, Anish Mangal escribió:
>>
>>> Download the XSCE Virtualbox appliance from here
>>> https://docs.google.com/file/d/0B3eW2YPe6koIVXRVbDhSR0xXQ1U (approx 1.6 GB)
>>
>>
>
>
>
> ___
> Server-devel mailing list
> Server-devel@lists.laptop.org
> http://lists.laptop.org/listinfo/server-devel
>



-- 
David Farning
Activity Central: http://www.activitycentral.com
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel

Re: [Server-devel] The three step XSCE demo!

2013-11-19 Thread Sebastian Silva 
Thanks that will be simpler. Actually I'm more interested in what a good 
dev environment would be in order to contribute.

Do I need to make a fedora chroot?

Regards,
Sebastian

El 19/11/13 09:51, Anish Mangal escribió:
I tried uploading it to xsce.activitycentral.com 
, but I ran out of space in my user 
dir. Normally the appliance is 1.3G, but this also has 400mb of IIAB 
test dataset.


I'll give it another shot in another area where there is some free 
space, and get back.



On Tue, Nov 19, 2013 at 7:24 PM, Sebastian Silva 
mailto:sebast...@fuentelibre.org>> wrote:


Hi
I tried this but google drive problematic to download from as it
requires to download from a browser. Not adequate for 1.6gb. Let
me know if I can pick it up from a regular download place. Why is
it so big?

Regards,
Sebastian

El 17/11/13 20:48, Anish Mangal escribió:

Download the XSCE Virtualbox appliance from here
https://docs.google.com/file/d/0B3eW2YPe6koIVXRVbDhSR0xXQ1U
(approx 1.6 GB)





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

Re: [Server-devel] The three step XSCE demo!

2013-11-19 Thread Anish Mangal 
I tried uploading it to xsce.activitycentral.com, but I ran out of space in
my user dir. Normally the appliance is 1.3G, but this also has 400mb of
IIAB test dataset.

I'll give it another shot in another area where there is some free space,
and get back.


On Tue, Nov 19, 2013 at 7:24 PM, Sebastian Silva
wrote:

> Hi
> I tried this but google drive problematic to download from as it requires
> to download from a browser. Not adequate for 1.6gb. Let me know if I can
> pick it up from a regular download place. Why is it so big?
>
> Regards,
> Sebastian
>
> El 17/11/13 20:48, Anish Mangal escribió:
>
>  Download the XSCE Virtualbox appliance from here
>> https://docs.google.com/file/d/0B3eW2YPe6koIVXRVbDhSR0xXQ1U (approx 1.6
>> GB)
>>
>
>
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel

Re: [Server-devel] The three step XSCE demo!

2013-11-19 Thread Sebastian Silva 

Hi
I tried this but google drive problematic to download from as it 
requires to download from a browser. Not adequate for 1.6gb. Let me know 
if I can pick it up from a regular download place. Why is it so big?


Regards,
Sebastian

El 17/11/13 20:48, Anish Mangal escribió:
Download the XSCE Virtualbox appliance from here 
https://docs.google.com/file/d/0B3eW2YPe6koIVXRVbDhSR0xXQ1U (approx 
1.6 GB)


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

Re: [Server-devel] The three step XSCE demo!

2013-11-18 Thread Miguel González 
On Mon, Nov 18, 2013 at 2:48 AM, Anish Mangal  wrote:
> I didn't setup root login (or atleast don't know the password to it). So you
> won't be able to login to the XSCE once it's running. Should not be a huge
> issue just for end-user demo purposes.

It is a vagrant generated virtual machine so:

- the user/password are vagrant/vagrant
- user 'vagrant' is in sudoers group
- ssh access is possible using port  in localhost

I have an entry in .ssh/config so I can access using `ssh vagrant`:

Host vagrant
  HostName 127.0.0.1
  User vagrant
  Port 
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no
  PasswordAuthentication no
  IdentityFile "~/.vagrant.d/insecure_private_key"
  IdentitiesOnly yes
  LogLevel FATAL

The insecure private key is available Github [1].

1: https://github.com/mitchellh/vagrant/tree/master/keys


-- 
Miguel González
Activity Central: http://www.activitycentral.com
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel

[Server-devel] The three step XSCE demo!

2013-11-17 Thread Anish Mangal 
Hi,

Had some time on my hand this week to try out XSCE in a virtual
environment. It actually worked out pretty well, and now there's a working
appliance. Here's the three step XSCE demo!

*Step #1 - Download and install Virtualbox*

   - Head to https://www.virtualbox.org/wiki/Downloads to download the
   Virtualbox package for your OS.
   - Install instructions may vary for different platforms but should be
   pretty straightforward.

*Step #2 - Download and install the XSCE appliance*

   - Download the XSCE Virtualbox appliance from here
   https://docs.google.com/file/d/0B3eW2YPe6koIVXRVbDhSR0xXQ1U (approx 1.6
   GB)
   - *[optional]* Verify the md5sum to see if the image is not corrupt
   - 56a4f141b564b0d2bd65c543a5e585c6
   - Open Virtualbox. Go to File -> Import Appliance.
   - A dialog will appear asking you to "Open Appliance"
   - Select the file you just downloaded "b_1364170741.ova"
   - Click "Next" and then click "Import"
   - A new virtual machine will get created

*Step #3 - Play!*

   - Start the virtual machine just created. It will open a window, and an
   OS will appear to boot.
   - Wait till it boots. Once it has booted, a login prompt will appear in
   a text console. Your XSCE is now up and ready!
   - To test/demo, on the host OS (i.e., the one where you are running the
   virtualbox software in) open a browser
  - XSCE homepage: http://localhost:3380/
 - From the homepage you should be able to navigate to Internet In
 A Box. This image contains a test dataset.
 - The link to the moodle homepage will NOT work. To access moodle,
 go to http://localhost:3380/moodle/login/index.php. I am not able
 to login, and there seems some issue with the homepage loading.
  - Administrative GUI: http://localhost:9990 (username=root,
  password=admin)
  - Server monitoring tool - Munin:
http://localhost:3380/munin(username=admin, password=munindxs)
  - To check the authserver, go to http://localhost:5000/ (It will
  probably say "No Sugar platform detected, please register your laptop")

*Notes:*

   - This is only meant to be a quick demo to see what an XSCE is on your
   laptop/PC.
   - I didn't setup root login (or atleast don't know the password to it).
   So you won't be able to login to the XSCE once it's running. Should not be
   a huge issue just for end-user demo purposes.
   - This is just a weekend hack, I did based on a Vagrantfile supplied by
   Santi. At this moment, this is not officially supported or anything (but as
   far as I know in my testing, it works!)
   - If this is a useful thing to maintain (based on feedback to this
   thread :-) ) I (or somebody else) can propose this as a feature for 0.5/6.
   So there are officially supported demo appliances.
   - A wiki page is in the works.

Please try it out and let me know what you think of it!

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