Re: [Server-devel] Moving toward headless install on trimslice
How does the os get onto the trimslice? How do you sudo if the only known user is not a sudoer? Date: Sat, 16 Nov 2013 12:12:33 -0500 From: George Hunt georgejh...@gmail.com To: XS Devel server-devel@lists.laptop.org Subject: [Server-devel] Moving toward headless install on trimslice for XSCE Message-ID: cadfccpv5g3dyxd5mh5qkyxr8hmlzca_dde+yzou73b0njm-...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 I'm wanting to do the following: - Get rid of the autologon to root at console tty. - Add a non privileged user (not a sudoer, not wheel), as we had pre-ansible, (user:admin,pw:12admin), so that the sshd config of permitrootlogon no can remain in place. - enable password authentication - Configure avahi to announce, so that in a trimslice situation, we can easily determine the remote sshd target ip. What do people think? ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Moving toward headless install on trimslice
On Sun, 2013-11-17 at 17:01 -0500, Tim Moody wrote: How does the os get onto the trimslice? zcat it onto a SDcard, How do you sudo if the only known user is not a sudoer? use su, and the default password setup in the image. Jerry Date: Sat, 16 Nov 2013 12:12:33 -0500 From: George Hunt georgejh...@gmail.com To: XS Devel server-devel@lists.laptop.org Subject: [Server-devel] Moving toward headless install on trimslice for XSCE Message-ID: cadfccpv5g3dyxd5mh5qkyxr8hmlzca_dde+yzou73b0njm-...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 I'm wanting to do the following: - Get rid of the autologon to root at console tty. - Add a non privileged user (not a sudoer, not wheel), as we had pre-ansible, (user:admin,pw:12admin), so that the sshd config of permitrootlogon no can remain in place. - enable password authentication - Configure avahi to announce, so that in a trimslice situation, we can easily determine the remote sshd target ip. What do people think? ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] Moving toward headless install on trimslice for XSCE
I'm wanting to do the following: - Get rid of the autologon to root at console tty. - Add a non privileged user (not a sudoer, not wheel), as we had pre-ansible, (user:admin,pw:12admin), so that the sshd config of permitrootlogon no can remain in place. - enable password authentication - Configure avahi to announce, so that in a trimslice situation, we can easily determine the remote sshd target ip. What do people think? ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] Re: XSCE Proposal | Moving to github and notifications
I like github, based upon my limited experience, because of its browsability. There will be new workflows that need to be established, but I'm willing for it. My sense of it is that this becoming a activitycentral project, which is ok with me. I'm glad when people start putting a shoulder to the wheel. We need to start adding value in the classroom as soon as possible, and github is an intermediate objective, but a distraction, from that objective. +1 for github george On Sun, Oct 13, 2013 at 2:11 PM, Anish Mangal an...@activitycentral.comwrote: *If* there is consensus on moving to github, should be think about making the switch before the hacksprint in SF? It might save us some time as then we would have set-up the buildbot, etc. On the other hand, if there isn't consensus, maybe the hacksprint would be a good opportunity to try github out. On Wed, Oct 9, 2013 at 8:30 AM, Martin Dluhos mar...@gnu.org wrote: On 10/09/2013 11:13 AM, Anish Mangal wrote: I think that it would be more appropriate to send notifications of merged pull requests rather than individual commits to avoid too much noise on the channel. Those who are interested can always follow the pull request link to access individual commits. I would prefer notifications for pull requests *both* when they are created and when they are merged. The creation of the pull request will sort of open a review and test window for people willing to do that, so notifying that event is necessary IMO. Very good point. I agree. ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] Re: XSCE Proposal | Moving to github and notifications
On Sun, 2013-10-13 at 18:20 -0400, Tim Moody wrote: +1 for the move. I guess you need to be careful with the timing so you don’t end up with the repo offline during the sprint, but if you feel confident in that then go for it. +1 motion carried, lets proceed. Now the question is working with merge requests, how are we going to handle that? Jerry ___ Change of Address timmo...@sympatico.ca is now t...@timmoody.com Please change your bookmarks. Thanks. ___ From: Anish Mangal Sent: Sunday, October 13, 2013 2:11 PM To: Martin Dluhos ; xsce-devel Cc: server-devel Subject: [XSCE] Re: [Server-devel] XSCE Proposal | Moving to github and notifications *If* there is consensus on moving to github, should be think about making the switch before the hacksprint in SF? It might save us some time as then we would have set-up the buildbot, etc. On the other hand, if there isn't consensus, maybe the hacksprint would be a good opportunity to try github out. On Wed, Oct 9, 2013 at 8:30 AM, Martin Dluhos mar...@gnu.org wrote: On 10/09/2013 11:13 AM, Anish Mangal wrote: I think that it would be more appropriate to send notifications of merged pull requests rather than individual commits to avoid too much noise on the channel. Those who are interested can always follow the pull request link to access individual commits. I would prefer notifications for pull requests *both* when they are created and when they are merged. The creation of the pull request will sort of open a review and test window for people willing to do that, so notifying that event is necessary IMO. Very good point. I agree. ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] Re: XSCE Proposal | Moving to github and notifications
Merge requests or as they are known in github, Pull requests (PR) can be committed to the main repo by the folks who have commit access. Normally the basic workflow is. * There is a main xsce repo. It's path would be xsce/xsce.git. * Developers create forks (or personal clones) of the repo, under their username. eg. gjh/xsce.git, or jvonau/xsce.git. * Typically the developer works on a branch per feature on their fork. So there might be a branch feature-xyz under m_anish/xsce.git. * When the feature is ready for merging, a Pull Request is created. Folks who have commit access to xsce/xsce.git get notified. * Some decision making mechanism takes place and the Pull Request is either merged or rejected. About Some decision making mechanism * I'd like to know how we do it currently, and what folks would be comfortable with, so we can try to follow it as closely as possible. * In DXS development, the the process we use is (just as an example): 1. Every developer has commit access to the main xsce repo. 2. The developer creating the pull request should not not be the one merging it. 3. The other developers in the team review and test the code, they accordingly leave comments of their review and test results against the pull request. 4. When there have been a total of two or more reviews/tests (combined), someone with the commit access merges the PR. One idea could be to have Jerry, George and Tim have commit access to the XSCE repo on github, and then they decide whom to add/remove from the accesslist and what process to follow for merging/rejecting PR's. Note, even if you don't have commit access, you can still create a fork, make a pull request, be notified of pull requests by others, and comment on them. Best, Anish On Sun, Oct 13, 2013 at 3:27 PM, Jerry Vonau jvo...@shaw.ca wrote: On Sun, 2013-10-13 at 18:20 -0400, Tim Moody wrote: +1 for the move. I guess you need to be careful with the timing so you don’t end up with the repo offline during the sprint, but if you feel confident in that then go for it. +1 motion carried, lets proceed. Now the question is working with merge requests, how are we going to handle that? Jerry ___ Change of Address timmo...@sympatico.ca is now t...@timmoody.com Please change your bookmarks. Thanks. ___ From: Anish Mangal Sent: Sunday, October 13, 2013 2:11 PM To: Martin Dluhos ; xsce-devel Cc: server-devel Subject: [XSCE] Re: [Server-devel] XSCE Proposal | Moving to github and notifications *If* there is consensus on moving to github, should be think about making the switch before the hacksprint in SF? It might save us some time as then we would have set-up the buildbot, etc. On the other hand, if there isn't consensus, maybe the hacksprint would be a good opportunity to try github out. On Wed, Oct 9, 2013 at 8:30 AM, Martin Dluhos mar...@gnu.org wrote: On 10/09/2013 11:13 AM, Anish Mangal wrote: I think that it would be more appropriate to send notifications of merged pull requests rather than individual commits to avoid too much noise on the channel. Those who are interested can always follow the pull request link to access individual commits. I would prefer notifications for pull requests *both* when they are created and when they are merged. The creation of the pull request will sort of open a review and test window for people willing to do that, so notifying that event is necessary IMO. Very good point. I agree. ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XSCE Proposal | Moving to github and notifications
Thx for the reply! On Tue, Oct 8, 2013 at 7:38 PM, Martin Dluhos mar...@gnu.org wrote: On 10/08/2013 03:08 PM, Anish Mangal wrote: Hi, One of the topics brought up in today's meeting was making the code and development process more visible. Can we have a discussion on this list and come to a conclusion on the proposals listed below. Thanks for sending the summary. I am including my thoughts inline. Proposal-1 : Shifting from redmine to github Pros: * Github offers a much better collaborative workflow with pull requests. * Github offers better code visibility and reviews in the GUI itself. This is a good move for both of the reasons you have listed above. This will lend more credibility to the project attracting the attention of more developers. Also make sure to add a link to the github page on schoolserver.org, so that it is immediately obvious where to access and browse the existing codebase. Proposal-2 : Notifications for source code commits to IRC. This is a well accepted practice to keep community members informed and involved about code changes and the development process. I think that it would be more appropriate to send notifications of merged pull requests rather than individual commits to avoid too much noise on the channel. Those who are interested can always follow the pull request link to access individual commits. I would prefer notifications for pull requests *both* when they are created and when they are merged. The creation of the pull request will sort of open a review and test window for people willing to do that, so notifying that event is necessary IMO. +1 to notifications related to pull requests rather than individual commits. Proposal-3 : Notifications for source code commits to the mailing list. This is a deliberate effort to again encourage better transparency, collaboration. Option-A : Send the notifications to server-devel. Since the mailing list is the single static archived place where everyone is subscribed, it makes sense to send notifications here. Option-B : Send to a separate mailing list. Those who are interested in development, may subscribe to it. Option-C : Github already offers the functionality to subscribe to updates. Individual users can sign up to get notified about updates to the repository. I vote for option C as there is no need to reinvent the wheel for existing functionality Github already offers. servel-devel should serve only for dev discussions, imho. Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XSCE Proposal | Moving to github and notifications
On 10/09/2013 11:13 AM, Anish Mangal wrote: I think that it would be more appropriate to send notifications of merged pull requests rather than individual commits to avoid too much noise on the channel. Those who are interested can always follow the pull request link to access individual commits. I would prefer notifications for pull requests *both* when they are created and when they are merged. The creation of the pull request will sort of open a review and test window for people willing to do that, so notifying that event is necessary IMO. Very good point. I agree. ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] XSCE Proposal | Moving to github and notifications
Hi, One of the topics brought up in today's meeting was making the code and development process more visible. Can we have a discussion on this list and come to a conclusion on the proposals listed below. Proposal-1 : Shifting from redmine to github * Move the xsce source code from the repository hosted on redmine to a repository hosted on github. * For open/public repositories, github offers an unlimited amount of members and collaboration. This comes at a zero dollar cost. * A xsce user will be created and the xsce repository hosted under it. All people who have commit access currently will have the same rights. * The buildbot will be pointed to the github repo, so builds will continue as usual. * Eg: DXS is on github, Sugar has been on github for quite a while. From the experience of DXS team (Me, Santi, Anna, Miguel), this is a recommended step. Pros: * Github offers a much better collaborative workflow with pull requests. * Github offers better code visibility and reviews in the GUI itself. * Here's an explanatory video that Miguel created: http://www.youtube.com/watch?v=CEE85F3Zjcs Proposal-2 : Notifications for source code commits to IRC. This is a well accepted practice to keep community members informed and involved about code changes and the development process. Proposal-3 : Notifications for source code commits to the mailing list. This is a deliberate effort to again encourage better transparency, collaboration. Option-A : Send the notifications to server-devel. Since the mailing list is the single static archived place where everyone is subscribed, it makes sense to send notifications here. Option-B : Send to a separate mailing list. Those who are interested in development, may subscribe to it. Option-C : Github already offers the functionality to subscribe to updates. Individual users can sign up to get notified about updates to the repository. Thoughts, Anish ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] A couple of thoughts about moving forward.
On Sun, Aug 11, 2013 at 9:47 PM, David Farning dfarn...@activitycentral.com wrote: Hey all, I would like to offer some reflections after the last couple of weeks. I stepped aside because I felt I was hindering the project more than helping it. I spent years being frustrated by Langoff's hold on OLPC-XS. Then after less than 8 months I found myself controlling the funding for the 6 person DXS team, creating the roadmap project specification, and doing much of the external communication. All of this while receiving dozens of emails and calls per week from deployments pressuring me to make XSCE and DXS different from what the core XSCE team was interested in doing. My shortcomings may have caused a split between XSCE and DXS. When David and I were discussing whether Ansible should be part of 0.4 XSCE, I felt a fear of creating a situation I have created many times before, in my life as a programmer. I tend to add more complexity than I have brain power to sort out during the debugging phase. So, now David has moved forward with DXS, with an aggressive schedule, adding features based upon customers requirements. And when he wants to incorporate DXS into the next revision, XSCE 0.5, the fear crops up again. I need help dealing with my fear of complexity. Are there any volunteers? In a sense it's the Red Hat, Fedora situation with a twist. The quick turnaround, feature development test bed, is the commercial enterprise. The volunteer, community based, effort is the slower moving, and more conservative. So now, our history, becomes our handicap. XSCE has not asked for much help from the people and the accumulated wisdom available on server-devel. But now I think we need that perspective. I don't want to have a hold on XSCE. I'm feeling like I need to pass the baton to someone, or a group of someones. I've been working hard at a volunteer job, and there just are no more hours in the day that I'm willing to devote to the XSCE enterprise. George It was not a recipe for community success :( So, I spent the last couple of weeks regrouping. If anyone has any suggestions for how they think I can help the community without becoming too smothering please let me know. I have been a little concerned about the relationship between the XSCE team and the DXS team. We put a pretty intense deadline of mid Oct for delivering commercially supported Dextrose Server. The goal of this division was to ensure the upstream XSCE team had the freedom to scratch their own itches while ensuring the downstream DXS team was focused on specific customer requirements. As a side effect it feels like there has become a gap between the teams. I would like to encourage Anna to step into the role of liaison between the two team. She can make sure that everyone is aware of what is happening. External communications hit a couple of rough patches over the past couple of weeks. While keeping the signal to noise ratio high, the use of a semi-private mailing list seemed to be hindering external awareness of what we were doing. Rather than ask the project to change, I decided to unsubscribe from this list and only remain subscribed to the server-devel list. The goal was to see how the projects was seen from the outside. My takeaway is that we should start to shift as many technical threads as possible to server-devel, there is a wealth of knowledge on that list. On planning and organization issues, the noise(passion) on server-devel might still might be a bit high for a young community like XSCE to handle without getting bogged down. I would suggest revisiting this decision one month prior to the release of 0.5. Good work everyone. Adolescents is a tough time for everyone especially community projects :) -- 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] [XSCE] A couple of thoughts about moving forward.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/08/2013 04:49 AM, George Hunt wrote: And when he wants to incorporate DXS into the next revision, XSCE 0.5, the fear crops up again. I need help dealing with my fear of complexity. Are there any volunteers? Hi George, If you missed the DXS/Ansible IRC demo a couple days ago, my impression was that Ansible was a fantastic, and STRAIGHT FORWARD, tool that is both more robust and simpler than bash scripting could hope to be. It also appeared that all the heavy porting from bash to ansible was already done by the DXS team. Maybe my outsider impression helps alleviate some of your fears. - -braddock -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSLMFSAAoJEHWLR/DQzlZu/QYIANABx31C2h0IdnMb4qcY1Mkl 4PpzBb32Gi/MDLsk196p0ZGdyMHZ/GFp58DY0ol7lGx+N8M2A44ulthQJV8LsdBu yExpJ7oMVBijsvjD6Bv7uycgjpqLQV7RsCL1MVPj5Z46wHzyiQzevVss4cCQ+/S2 Bs21BB7u8TLE60kXyRUZtPbzqwYJhT+2uSakpo3enbMyOq5tqgeQb7kTN6n0kyBt AOsy3A4lH097McHW7eJozFzYHoogBAOCxUL9x7YUmOWEwkjI9xYaaFPdn/p3ssla AtR4B464DQUSErknkb4MIir5EsMJUqs4DNMnGLA/elSkb1+7/DDqdiYwsEogX1A= =1dEz -END PGP SIGNATURE- ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] A couple of thoughts about moving forward.
On Sun, Sep 8, 2013 at 6:49 AM, George Hunt georgejh...@gmail.com wrote: On Sun, Aug 11, 2013 at 9:47 PM, David Farning dfarn...@activitycentral.com wrote: Hey all, I would like to offer some reflections after the last couple of weeks. I stepped aside because I felt I was hindering the project more than helping it. I spent years being frustrated by Langoff's hold on OLPC-XS. Then after less than 8 months I found myself controlling the funding for the 6 person DXS team, creating the roadmap project specification, and doing much of the external communication. All of this while receiving dozens of emails and calls per week from deployments pressuring me to make XSCE and DXS different from what the core XSCE team was interested in doing. My shortcomings may have caused a split between XSCE and DXS. When David and I were discussing whether Ansible should be part of 0.4 XSCE, I felt a fear of creating a situation I have created many times before, in my life as a programmer. I tend to add more complexity than I have brain power to sort out during the debugging phase. So, now David has moved forward with DXS, with an aggressive schedule, adding features based upon customers requirements. And when he wants to incorporate DXS into the next revision, XSCE 0.5, the fear crops up again. I need help dealing with my fear of complexity. Are there any volunteers? In a sense it's the Red Hat, Fedora situation with a twist. The quick turnaround, feature development test bed, is the commercial enterprise. The volunteer, community based, effort is the slower moving, and more conservative. So now, our history, becomes our handicap. XSCE has not asked for much help from the people and the accumulated wisdom available on server-devel. But now I think we need that perspective. I don't want to have a hold on XSCE. I'm feeling like I need to pass the baton to someone, or a group of someones. I've been working hard at a volunteer job, and there just are no more hours in the day that I'm willing to devote to the XSCE enterprise. Nine months ago I recommended you as release manager for XSCE and I stand by that recommendation today even though it has meant the AC lead Ansible work has lived out of tree for the last couple of months. The release manager has a tough (some might say impossible) job in community project. In a thriving community there will be a million people all clamoring that their work be committed NOW. The release manager must weigh the pros and cons before accepting a patch especially when it is significant. In this case you and Jerry said 'hold on, I don't see the value in this ansible stuff. That was the right decision at the time. It is the branch authors responsibility to prove the value of their work. Anish et. al. put their heads down and translate xs-conf to ansible. My reasoning for personally stepping back from participation in XSCE was to ensure credibility in the XSCE decision making process. I believe that porting xsce to ansible is the best way forward for the ecosystem, XSCE and AC. However, if it appeared that I was using my roles within XSCE to push an external agenda, XSCE would forever be tainted. As george says, there are a lot of skilled people reading these lists. Is Anyone willing to step up and help ensure that we have a neutral community that balances the (often passionate) needs of school server developers, deployers, and users. George It was not a recipe for community success :( So, I spent the last couple of weeks regrouping. If anyone has any suggestions for how they think I can help the community without becoming too smothering please let me know. I have been a little concerned about the relationship between the XSCE team and the DXS team. We put a pretty intense deadline of mid Oct for delivering commercially supported Dextrose Server. The goal of this division was to ensure the upstream XSCE team had the freedom to scratch their own itches while ensuring the downstream DXS team was focused on specific customer requirements. As a side effect it feels like there has become a gap between the teams. I would like to encourage Anna to step into the role of liaison between the two team. She can make sure that everyone is aware of what is happening. External communications hit a couple of rough patches over the past couple of weeks. While keeping the signal to noise ratio high, the use of a semi-private mailing list seemed to be hindering external awareness of what we were doing. Rather than ask the project to change, I decided to unsubscribe from this list and only remain subscribed to the server-devel list. The goal was to see how the projects was seen from the outside. My takeaway is that we should start to shift as many technical threads as possible to server-devel, there is a wealth of knowledge on that list. On planning and organization issues, the noise(passion) on server-devel might still might
Re: [Server-devel] [XSCE] A couple of thoughts about moving forward.
On Wed, Aug 28, 2013 at 11:37 PM, Anish Mangal an...@activitycentral.com wrote: Well, I was sort of hoping: You were sort of hoping what? -walter * We could start to have discussions and work around some/all of the topics as a community. Everyone here has way more expertise than me in many (if not all) of the topics I listed. We can build a much better server if we all can use our expertise in the relevant part of the server. This transcends the pure software-development aspect of XSCE. * As the 0.4 version of the XSCE is nearing release, it's a good time to start thinking about additions/changes for 0.5. One of the consistent efforts (and demands) has been to make the server code more manageable, and by extension, modular and scalable. * 0.2.1 was a drop-in replacement of the XS-0.6/7 * 0.3 involved a major reorganization to make the services more modular * 0.4 built upon that, by providing all the code in the same modular structure Within Activity Central, a team of developers (Santi, Miguel, Ajay, Anna) have been working on converting services available on the XSCE into ansible playbooks. The playbooks are written in a syntax which is *very easy to understand*, and the same playbook can be run on different platforms to produce the same effect. The playbooks can provide variables which may be integrated easily with other administration web-services (for example ajenti). I hope to share the code for the playbooks very soon, so anyone can have a look at and try them. We have been able to get a fully functional server up just by playbooks and reusing/restructuring the available XSCE (xs-config) code. As someone leading the Dextrose Server initiative, I would push for the inclusion of these playbooks in XSCE-0.5. There is long term value in learning a bit of ansible and being able to work at a higher abstraction level. Best, Anish On Wed, Aug 28, 2013 at 6:48 PM, Tim Moody t...@timmoody.com wrote: Thanks for making this public. What do you see as the next step? From: Anish Mangal Sent: Wednesday, August 28, 2013 6:16 PM To: xsce-de...@googlegroups.com ; server-devel ; Tim Moody Subject: Re: [XSCE] A couple of thoughts about moving forward. Hi Tim, et. al., Since it was requested that I share my conversations with various deployments over the summer yielded in form of potential requirements for the school server, I created this wiki page: https://sugardextrose.org/projects/xsce/wiki/Primary_considerations There's obviously more data available, but what you see is a filtered version of guidelines I think we should keep in mind while developing a school server. Do the points in there (summarized below) make sense? I intentionally created this page on the sugardextrose.org wiki. If it has greater acceptance community-wide, I'd be happy to move it to the main XSCE wiki. * Statistics * Content * Internet traffic shaping * Administration * Networking * Classroom and School management * Total Cost of Ownership * Power * Sneakernet - LAN - Internet * i18n Best, Anish -- Sig inserted by AutoHotkey ver. 1.1.11.01 (signature - first line) WLMail QuoteFix - http://www.dusko-lolic.from.hr/ (signature - second line) ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] A couple of thoughts about moving forward.
Hi Anish, I look forward to playing with the XSCE installed via Ansible. Will there be an install procedure, and cookbook, to try it out? George On Wed, Aug 28, 2013 at 11:37 PM, Anish Mangal an...@activitycentral.comwrote: Well, I was sort of hoping: * We could start to have discussions and work around some/all of the topics as a community. Everyone here has way more expertise than me in many (if not all) of the topics I listed. We can build a much better server if we all can use our expertise in the relevant part of the server. This transcends the pure software-development aspect of XSCE. * As the 0.4 version of the XSCE is nearing release, it's a good time to start thinking about additions/changes for 0.5. One of the consistent efforts (and demands) has been to make the server code more manageable, and by extension, modular and scalable. * 0.2.1 was a drop-in replacement of the XS-0.6/7 * 0.3 involved a major reorganization to make the services more modular * 0.4 built upon that, by providing all the code in the same modular structure Within Activity Central, a team of developers (Santi, Miguel, Ajay, Anna) have been working on converting services available on the XSCE into ansible playbooks. The playbooks are written in a syntax which is *very easy to understand*, and the same playbook can be run on different platforms to produce the same effect. The playbooks can provide variables which may be integrated easily with other administration web-services (for example ajenti http://ajenti.org/). I hope to share the code for the playbooks very soon, so anyone can have a look at and try them. We have been able to get a fully functional server up just by playbooks and reusing/restructuring the available XSCE (xs-config) code. As someone leading the Dextrose Server initiative, I would push for the inclusion of these playbooks in XSCE-0.5. There is long term value in learning a bit of ansible and being able to work at a higher abstraction level. Best, Anish On Wed, Aug 28, 2013 at 6:48 PM, Tim Moody t...@timmoody.com wrote: Thanks for making this public. What do you see as the next step? From: Anish Mangal Sent: Wednesday, August 28, 2013 6:16 PM To: xsce-de...@googlegroups.com ; server-devel ; Tim Moody Subject: Re: [XSCE] A couple of thoughts about moving forward. Hi Tim, et. al., Since it was requested that I share my conversations with various deployments over the summer yielded in form of potential requirements for the school server, I created this wiki page: https://sugardextrose.org/projects/xsce/wiki/Primary_considerations There's obviously more data available, but what you see is a filtered version of guidelines I think we should keep in mind while developing a school server. Do the points in there (summarized below) make sense? I intentionally created this page on the sugardextrose.org wiki. If it has greater acceptance community-wide, I'd be happy to move it to the main XSCE wiki. * Statistics * Content * Internet traffic shaping * Administration * Networking * Classroom and School management * Total Cost of Ownership * Power * Sneakernet - LAN - Internet * i18n Best, Anish -- Sig inserted by AutoHotkey ver. 1.1.11.01 (signature - first line) WLMail QuoteFix - http://www.dusko-lolic.from.hr/ (signature - second line) ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] A couple of thoughts about moving forward.
The code is moving to github as we speak/type :) On Thu, Aug 29, 2013 at 7:32 PM, George Hunt georgejh...@gmail.com wrote: Hi Anish, I look forward to playing with the XSCE installed via Ansible. Will there be an install procedure, and cookbook, to try it out? George On Wed, Aug 28, 2013 at 11:37 PM, Anish Mangal an...@activitycentral.com wrote: Well, I was sort of hoping: * We could start to have discussions and work around some/all of the topics as a community. Everyone here has way more expertise than me in many (if not all) of the topics I listed. We can build a much better server if we all can use our expertise in the relevant part of the server. This transcends the pure software-development aspect of XSCE. * As the 0.4 version of the XSCE is nearing release, it's a good time to start thinking about additions/changes for 0.5. One of the consistent efforts (and demands) has been to make the server code more manageable, and by extension, modular and scalable. * 0.2.1 was a drop-in replacement of the XS-0.6/7 * 0.3 involved a major reorganization to make the services more modular * 0.4 built upon that, by providing all the code in the same modular structure Within Activity Central, a team of developers (Santi, Miguel, Ajay, Anna) have been working on converting services available on the XSCE into ansible playbooks. The playbooks are written in a syntax which is *very easy to understand*, and the same playbook can be run on different platforms to produce the same effect. The playbooks can provide variables which may be integrated easily with other administration web-services (for example ajenti). I hope to share the code for the playbooks very soon, so anyone can have a look at and try them. We have been able to get a fully functional server up just by playbooks and reusing/restructuring the available XSCE (xs-config) code. As someone leading the Dextrose Server initiative, I would push for the inclusion of these playbooks in XSCE-0.5. There is long term value in learning a bit of ansible and being able to work at a higher abstraction level. Best, Anish On Wed, Aug 28, 2013 at 6:48 PM, Tim Moody t...@timmoody.com wrote: Thanks for making this public. What do you see as the next step? From: Anish Mangal Sent: Wednesday, August 28, 2013 6:16 PM To: xsce-de...@googlegroups.com ; server-devel ; Tim Moody Subject: Re: [XSCE] A couple of thoughts about moving forward. Hi Tim, et. al., Since it was requested that I share my conversations with various deployments over the summer yielded in form of potential requirements for the school server, I created this wiki page: https://sugardextrose.org/projects/xsce/wiki/Primary_considerations There's obviously more data available, but what you see is a filtered version of guidelines I think we should keep in mind while developing a school server. Do the points in there (summarized below) make sense? I intentionally created this page on the sugardextrose.org wiki. If it has greater acceptance community-wide, I'd be happy to move it to the main XSCE wiki. * Statistics * Content * Internet traffic shaping * Administration * Networking * Classroom and School management * Total Cost of Ownership * Power * Sneakernet - LAN - Internet * i18n Best, Anish -- Sig inserted by AutoHotkey ver. 1.1.11.01 (signature - first line) WLMail QuoteFix - http://www.dusko-lolic.from.hr/ (signature - second line) -- 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] [XSCE] A couple of thoughts about moving forward.
Hi Tim, et. al., Since it was requested that I share my conversations with various deployments over the summer yielded in form of potential requirements for the school server, I created this wiki page: https://sugardextrose.org/projects/xsce/wiki/Primary_considerations There's obviously more data available, but what you see is a filtered version of guidelines I think we should keep in mind while developing a school server. Do the points in there (summarized below) make sense? I intentionally created this page on the sugardextrose.org wiki. If it has greater acceptance community-wide, I'd be happy to move it to the main XSCE wiki. * Statistics * Content * Internet traffic shaping * Administration * Networking * Classroom and School management * Total Cost of Ownership * Power * Sneakernet - LAN - Internet * i18n Best, Anish ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] A couple of thoughts about moving forward.
Well, I was sort of hoping: * We could start to have discussions and work around some/all of the topics as a community. Everyone here has way more expertise than me in many (if not all) of the topics I listed. We can build a much better server if we all can use our expertise in the relevant part of the server. This transcends the pure software-development aspect of XSCE. * As the 0.4 version of the XSCE is nearing release, it's a good time to start thinking about additions/changes for 0.5. One of the consistent efforts (and demands) has been to make the server code more manageable, and by extension, modular and scalable. * 0.2.1 was a drop-in replacement of the XS-0.6/7 * 0.3 involved a major reorganization to make the services more modular * 0.4 built upon that, by providing all the code in the same modular structure Within Activity Central, a team of developers (Santi, Miguel, Ajay, Anna) have been working on converting services available on the XSCE into ansible playbooks. The playbooks are written in a syntax which is *very easy to understand*, and the same playbook can be run on different platforms to produce the same effect. The playbooks can provide variables which may be integrated easily with other administration web-services (for example ajentihttp://ajenti.org/ ). I hope to share the code for the playbooks very soon, so anyone can have a look at and try them. We have been able to get a fully functional server up just by playbooks and reusing/restructuring the available XSCE (xs-config) code. As someone leading the Dextrose Server initiative, I would push for the inclusion of these playbooks in XSCE-0.5. There is long term value in learning a bit of ansible and being able to work at a higher abstraction level. Best, Anish On Wed, Aug 28, 2013 at 6:48 PM, Tim Moody t...@timmoody.com wrote: Thanks for making this public. What do you see as the next step? From: Anish Mangal Sent: Wednesday, August 28, 2013 6:16 PM To: xsce-de...@googlegroups.com ; server-devel ; Tim Moody Subject: Re: [XSCE] A couple of thoughts about moving forward. Hi Tim, et. al., Since it was requested that I share my conversations with various deployments over the summer yielded in form of potential requirements for the school server, I created this wiki page: https://sugardextrose.org/projects/xsce/wiki/Primary_considerations There's obviously more data available, but what you see is a filtered version of guidelines I think we should keep in mind while developing a school server. Do the points in there (summarized below) make sense? I intentionally created this page on the sugardextrose.org wiki. If it has greater acceptance community-wide, I'd be happy to move it to the main XSCE wiki. * Statistics * Content * Internet traffic shaping * Administration * Networking * Classroom and School management * Total Cost of Ownership * Power * Sneakernet - LAN - Internet * i18n Best, Anish -- Sig inserted by AutoHotkey ver. 1.1.11.01 (signature - first line) WLMail QuoteFix - http://www.dusko-lolic.from.hr/ (signature - second line) ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Moving on
Friends, You may already have heard the news, but I wanted to take a moment to let you know that I have just concluded my tenure as Engineering Manager at One Laptop per Child Australia. It's been a rewarding three and a half years. I joined the organisation as its first technical resource and established the Engineering Department. We've created some innovative solutions, and most importantly it has all been tied closely into a holistic educational solution. I'm pleased to say that we've made a difference to the lives of thousands of children. This was not a proprietary effort - far from it. The community has been the backbone of everything we have achieved, and I owe a debt of gratitude to you all. Walter Bender will be taking over many of my responsibilities, so our community roots will certainly continue. I'm not sure what adventure lies next for me, but I hope to be able to make a positive contribution to the world in whatever I do. I'll be sticking around on the lists as a lurker. My srid...@laptop.org.au address will likely stop working in the near future, but you can continue to reach me personally: e-mail: srid...@dhanapalan.com LinkedIn: http://au.linkedin.com/in/sridhard All the best, Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] Moving on
Friends, You may already have heard the news, but I wanted to take a moment to let you know that I have just concluded my tenure as Engineering Manager at One Laptop per Child Australia. It's been a rewarding three and a half years. I joined the organisation as its first technical resource and established the Engineering Department. We've created some innovative solutions, and most importantly it has all been tied closely into a holistic educational solution. I'm pleased to say that we've made a difference to the lives of thousands of children. This was not a proprietary effort - far from it. The community has been the backbone of everything we have achieved, and I owe a debt of gratitude to you all. Walter Bender will be taking over many of my responsibilities, so our community roots will certainly continue. I'm not sure what adventure lies next for me, but I hope to be able to make a positive contribution to the world in whatever I do. I'll be sticking around on the lists as a lurker. My srid...@laptop.org.au address will likely stop working in the near future, but you can continue to reach me personally: e-mail: srid...@dhanapalan.com LinkedIn: http://au.linkedin.com/in/sridhard All the best, Sridhar ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Moving joyride to rawhide
Hi All, With the plans of releasing what is/was going to be 9.1.0 as based on Fedora 11 (rather than the original plans of Fedora 10) what is the plans on moving the joyride daily builds to pull in rawhide rather than Fedora 10? Is the plan for the 9.1.0 release (is it still going to be called that?) to be built from the existing OLPC build system (pilgrim?) or is there plans to move it to the Fedora system? If there are plans to move to the Fedora build system will it be able to sign the releases etc, or is this planned for sometime later? The reason I ask these questions is because its probably better to make the move sooner rather than later so people don't waste time testing and fixing things on Fedora 10 where it would be better to use the time with Fedora 11 so larger changes like python 2.6 etc can be tested. Sorry for the ramble. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Moving joyride to rawhide
2009/1/28 Peter Robinson pbrobin...@gmail.com: With the plans of releasing what is/was going to be 9.1.0 as based on Fedora 11 (rather than the original plans of Fedora 10) what is the plans on moving the joyride daily builds to pull in rawhide rather than Fedora 10? Is the plan for the 9.1.0 release (is it still going to be called that?) to be built from the existing OLPC build system (pilgrim?) or is there plans to move it to the Fedora system? If there are plans to move to the Fedora build system will it be able to sign the releases etc, or is this planned for sometime later? The reason I ask these questions is because its probably better to make the move sooner rather than later so people don't waste time testing and fixing things on Fedora 10 where it would be better to use the time with Fedora 11 so larger changes like python 2.6 etc can be tested. I believe that we want to build things using Fedora's tools -- we actually would like Fedora to build the releases in future. So, this means that pilgrim goes away, or that pilgrim gets adopted by Fedora (the former, I guess!). Some work may be needed on Fedora's build tools, but I was extremely pleased to hear that Sugar-on-a-stick is being built with standard Fedora tools, and we now have a (nearly?-)functional Soas XO image. Details like security, signing and updates remain to be figured out, I believe. For now, having a partially bootable image based on rawhide will be a great start. It would be best to use your time with OLPC-F11 preparation - I don't see the current joyride going anywhere. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Moving joyride to rawhide
Hi Peter, Hi All, With the plans of releasing what is/was going to be 9.1.0 as based on Fedora 11 (rather than the original plans of Fedora 10) what is the plans on moving the joyride daily builds to pull in rawhide rather than Fedora 10? As Daniel said, I think a better plan is to start using livecd-tools as our build system. I tried making what would be the first joyride F11 build in this thread: https://www.redhat.com/archives/fedora-olpc-list/2009-January/msg00081.html But I'm stuck with /dev/root not being created for an odd reason, could use some Fedora initrd knowledge. Once we have something that boots, I'd be happy to set up nightly automated builds using livecd-tools. Thanks! - Chris. -- Chris Ball c...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Moving joyride to use OLPC-3?
Hello, what is left to do before we can make joyride pull from the OLPC-3 branch? We made new sugar rpms a week ago and people still need to install them manually... August is 5 weeks away. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Personal Scripts moving to personal git space ?
Devel team, I'm in the process of both updating my scripts ( http://wiki.laptop.org/go/User:Ixo/Script ) to be under the better GPL , ( :] thanks Tony for the nudge!) and moving them into a better manageable personal git space. I tried to follow the directions at: http://wiki.laptop.org/go/Creating_a_personal_git_tree But alas, the response from ssh Permission denied (publickey). I'm guessing that I actually need to start a project on git, and submit a ssh-key before I can have access ? If a project is necessary, I have quite a number of 'in concept' ideas started at: http://wiki.laptop.org/go/User:Ixo/Project Anyone of which, someone could give me incentive enough to dive into and make the project start up :) Any thoughts or idea/feedback on any of the above ? :) - i X o ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Personal Scripts moving to personal git space ?
Ixo, But alas, the response from ssh Permission denied (publickey). This error message implies that git was unable to use your ssh-agent to log in dev. In order for git to be able to use your ssh-agent, you need to have the ssh-agent running and you need to set SSH_AUTH_SOCK to the value printed by ssh-agent when it starts. You also need to add your ssh keys to the agent. Michael P.S. - there's a handy script called 'keychain', available in most distributions, that will handle these details for you on session creation. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: API Change Notification: Moving Rainbow's Spool - #5033
Dear Everyone, This is your notification that I am about to commit the previously mentioned changes to sugar-datastore, rainbow, and olpc-utils. The current plan is that rainbow's spool will move into /home/olpc/isolation/1/ This way, fewer package changes are required (we can leave olpcrd alone) and we move closer to a version of rainbow that can be used on general linux distributions. I will send a final notification when all the changes have been made successfully or when I have reverted them if testing determines that I missed something. Please let me know if you have any questions about this process. Thanks! Michael We are about to begin committing On Wed, Jan 02, 2008 at 03:06:31PM -0500, Michael Stone wrote: Dear Everyone, This email is a notification that we would like to make an API change in order to make activity data persist across updates (#5033). The API change consists of moving '/activities' to '/security/1/activities'. I will send a second email when the changes begin to be committed into builds and a third email when we believe that they are working correctly. I would like to begin commiting changes tomorrow on Jan. 4. Please respond if you will be adversely impacted by this change. Best, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
API Change Notification: Moving Rainbow's Spool - #5033
Dear Everyone, This email is a notification that we would like to make an API change in order to make activity data persist across updates (#5033). The API change consists of moving '/activities' to '/security/1/activities'. I will send a second email when the changes begin to be committed into builds and a third email when we believe that they are working correctly. I would like to begin commiting changes tomorrow on Jan. 4. Please respond if you will be adversely impacted by this change. Best, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: API Change Notification: Moving Rainbow's Spool - #5033
SJ, To date, /security is used by the initramfs and firmware to store the developer key and activation lease. We also considered using it to communicate with the initramfs, e.g. to install a developer key found on a USB key but this has not been implemented. /activities arose to be Rainbow's 'spool directory', in which it records resource reservations (for uids and gids) and in which it stores the filesystem skeleton (home dirs, instance dirs, data dirs, and tmp dirs) used by the activities it is launching. Some details of /security are scattered throughout http://wiki.laptop.org/go/Firmware_Security Also, a decent idea of how the spool is constructed and used can be gleaned from the links in http://wiki.laptop.org/go/Taste_the_Rainbow#Activity_Launching specifically the configure_home() function and the check_spool() function at http://tinyurl.com/ys2nsb Does this suffice to satisfy your curiosity? Michael On Wed, Jan 02, 2008 at 09:13:15PM -0500, Samuel Klein wrote: Michael, Can you point me to docs that lay out what /activities and /security semantics are meant to be? Thanks, SJ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
