Re: [Server-devel] DXS github repository
Hi all server folks, There will be a mini demo at 1500 UTC on #schoolserver tomorrow showcasing some of the stuff we've been working on for DXS. It's still very early beta. This is in sync with proposing these features for XSCE-0.5. Some of the things in the short demo would be: * Ansible playbooks * Ajenti - GUI | Wondershaper - Bandwidth throttling * Github workflow for DXS * Transparent Client Authentication - How does Moodle magically log clients in, and how may it be scaled to other services * Munin A public DXS instance running on a XO-4 is temporarily setup at: http://schoolserver.alabamaxo.org Note: Please have an XO laptop with you, if you want to test out collaboration, and registration to the schoolserver. Cheers, Anish On Tue, Sep 3, 2013 at 2:34 PM, David Farning dfarn...@activitycentral.comwrote: Thanks anish, This reduces my freakout level by an order of magnitude :) At time my mental model fails me. I think of DXS as downstream to XSCE. I think of AC as doing less frequent releases than XSCE with the goal of increased stability. This release was inverted as DXS led the painful shift to ansible. If you are into such things. The affect of a downstream getting ahead of an upstream is remarkably similar to 'interest rate inversions.' http://www.investopedia.com/articles/basics/06/invertedyieldcurve.asp . Normal planning starts to go out the window. :) I would like to encourage Tim, George, and Jerry to play with and explore and test the code at https://github.com/activitycentral/dxs . We have three general approaches for upstreaming thing code: 1. Do a complete rebase to the DXS code when the XSCE 0.5 window open. While riskiest it minimizes the amount of duplicated effort. 2. Create a stepwise plan. While possible, is quite hard due to circular dependencies. :( 3. Keep the code separate. A couple of considerations: 1. Is it worth learning Ansible? While pretty easy to learn, read, and code, Ansible is yet another language to learn. 2. How does this affect 0.5 planning? How will the XSCE community determine priorities and goals for the release. Have fun and thanks for everything :) On Tue, Sep 3, 2013 at 1:23 PM, Anish Mangal an...@activitycentral.com wrote: Hi George, Jerry, Tim, et. al. Please have a look at the DXS github repository. We have been able to use ansible playbooks to install a School Server. One can try setting it up using the instructions in the INSTALL.rst file. We also added Ajenti as an admin GUI, there are separate instructions for that. Also included is Munin (i think on an experimental basis). Some things which are present in the XSCE-0.4 are missing in our repo, like Pathagar, or IIAB, or CUPS. Mostly, we wanted to be much more public with the code, and the development process, as we move beyond the XSCE-0.4 release. Ideally, I want to merge a majority (if not all) of this code with the upstream, so we all have a common base. Within AC (Santi, Miguel, Ajay, Myself) we will participate more openly with the XSCE project going forward. Anna already does a lot of work within the XSCE community :-) https://github.com/activitycentral/dxs Best, Anish ___ 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
[Server-devel] DXS github repository
Hi George, Jerry, Tim, et. al. Please have a look at the DXS github repository. We have been able to use ansible playbooks to install a School Server. One can try setting it up using the instructions in the INSTALL.rst file. We also added Ajenti as an admin GUI, there are separate instructions for that. Also included is Munin (i think on an experimental basis). Some things which are present in the XSCE-0.4 are missing in our repo, like Pathagar, or IIAB, or CUPS. Mostly, we wanted to be much more public with the code, and the development process, as we move beyond the XSCE-0.4 release. Ideally, I want to merge a majority (if not all) of this code with the upstream, so we all have a common base. Within AC (Santi, Miguel, Ajay, Myself) we will participate more openly with the XSCE project going forward. Anna already does a lot of work within the XSCE community :-) https://github.com/activitycentral/dxs Best, Anish ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] DXS github repository
Thanks anish, This reduces my freakout level by an order of magnitude :) At time my mental model fails me. I think of DXS as downstream to XSCE. I think of AC as doing less frequent releases than XSCE with the goal of increased stability. This release was inverted as DXS led the painful shift to ansible. If you are into such things. The affect of a downstream getting ahead of an upstream is remarkably similar to 'interest rate inversions.' http://www.investopedia.com/articles/basics/06/invertedyieldcurve.asp . Normal planning starts to go out the window. :) I would like to encourage Tim, George, and Jerry to play with and explore and test the code at https://github.com/activitycentral/dxs . We have three general approaches for upstreaming thing code: 1. Do a complete rebase to the DXS code when the XSCE 0.5 window open. While riskiest it minimizes the amount of duplicated effort. 2. Create a stepwise plan. While possible, is quite hard due to circular dependencies. :( 3. Keep the code separate. A couple of considerations: 1. Is it worth learning Ansible? While pretty easy to learn, read, and code, Ansible is yet another language to learn. 2. How does this affect 0.5 planning? How will the XSCE community determine priorities and goals for the release. Have fun and thanks for everything :) On Tue, Sep 3, 2013 at 1:23 PM, Anish Mangal an...@activitycentral.com wrote: Hi George, Jerry, Tim, et. al. Please have a look at the DXS github repository. We have been able to use ansible playbooks to install a School Server. One can try setting it up using the instructions in the INSTALL.rst file. We also added Ajenti as an admin GUI, there are separate instructions for that. Also included is Munin (i think on an experimental basis). Some things which are present in the XSCE-0.4 are missing in our repo, like Pathagar, or IIAB, or CUPS. Mostly, we wanted to be much more public with the code, and the development process, as we move beyond the XSCE-0.4 release. Ideally, I want to merge a majority (if not all) of this code with the upstream, so we all have a common base. Within AC (Santi, Miguel, Ajay, Myself) we will participate more openly with the XSCE project going forward. Anna already does a lot of work within the XSCE community :-) https://github.com/activitycentral/dxs Best, Anish ___ 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
