Re: [Server-devel] [XSCE] xovis on the XSCE 5.0
On 06/29/2014 12:33 AM, Tim Moody wrote: https://github.com/XSCE/xsce/pull/144 has been created. Martin, please review. Great work, Tim! I've just looked at the changes you have made to the xovis role (apologies for the delay) and left you a few comments on the pull request. I've also updated XSCE docs to include xovis and created a new pull request, which uses XSCE/master as the base: https://github.com/XSCE/xsce/pull/146 Cheers, Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XO Visualization Feature
On 06/04/2014 03:26 PM, Anish Mangal wrote: Hi Martin, I should point out that while I got it to install eventually, the first fail on the add admin user is a common problem I noticed across multiple installs.. The goes like this. ./runansible ... fails at add admin user ./runansible (again) goes past the step just fine, and install works as expected. Hi Anish, Tim updated the ansible playbook for xovis and merged it into master. I haven't seen this issue when testing the latest master. Could you please try again and see if the problem persists? Thanks, Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] sugarstats and xovis
On 06/22/2014 08:33 PM, Sameer Verma wrote: On Sun, Jun 22, 2014 at 7:41 AM, Tim Moody t...@timmoody.com wrote: does xovis supersede sugarstats? From what I understand, sugar-stats runs at the dbus level as opposed to the Journal metadata, which pulls data from the Journal backups. xovis relies on data that it can get as json, pushed into couchdb. So, while right now xovis uses json from Journal backups, it could be modified to do so from the RRD files that sugar-stats produces. That said, the data collected by sugar-stats is different, and needs to be filtered accordingly before it can be used sensibly by xovis. That's exactly right. Using sugar-stats data in XOvis was actually one of the things I began exploring while in Nepal, but didn't implement prior to my departure. I think adding that capability to XOvis would be very very useful. Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] sugarstats and xovis
On 06/24/2014 07:20 PM, Sameer Verma wrote: On Mon, Jun 23, 2014 at 9:32 PM, Martin Abente martin.abente.lah...@gmail.com wrote: Hello Sameer, The harvest-client serializes (using json) a subset of journal-objects metadata and then sends it to the harvest-server, which is basically a web-service plus a MySQL back-end. Great! Then we can perhaps add a method to process_journal_stats.py in XOVis to support Harvest. XOvis visualization relies on journal metadata being stored in couchdb in json, so it should be relatively straightforward to add a method to process_journal_stats.py to read data generated by harvest-client and store it in the db. Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] xovis on the XSCE 5.0
On 06/17/2014 08:49 PM, Sameer Verma wrote: On Tue, Jun 17, 2014 at 1:11 AM, Martin Dluhos mar...@gnu.org wrote: When installing with install_xovis.sh script, the script will output the command that you need to run. Since the db was created using an admin account, you need to pass the 'server' flag to the command including the couch credentials: ./process_journal_stats.py dbinsert xovis --deployment olpc --server http://admin:admin@127.0.0.1:5984 That works! https://twitter.com/sameerverma/status/478970452757327874 Very nice! ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] xovis on the XSCE 5.0
On 06/16/2014 05:41 AM, Sameer Verma wrote: On Sun, Jun 15, 2014 at 3:58 AM, Martin Dluhos mar...@gnu.org wrote: On 06/15/2014 02:41 AM, Sameer Verma wrote: Hi Martin, I installed xovis on the XSCE 5.0 running on a XO 1.75 (512MB RAM, consuming 405MB or so right now). I've successfully registered a few XOs with the server. I see the backups in /library/users/ I see that I have a /opt/xovis folder. Does the database insert into couchdb run via cron? If not, how do I push the metadats into couchdb? Currently, this needs to be done manually by running script process_journal_stats.py, which is in the repository. I updated the installation instructions in the README yesterday, which explains how to install and use XOvis: https://github.com/martasd/xovis See the Load existing deployment data into the database section in the README. Are the instructions clear? Got it. I ran ./process_journal_stats.py dbinsert xovis --deployment olpc and got the following. I'm running this as root. When installing with install_xovis.sh script, the script will output the command that you need to run. Since the db was created using an admin account, you need to pass the 'server' flag to the command including the couch credentials: ./process_journal_stats.py dbinsert xovis --deployment olpc --server http://admin:admin@127.0.0.1:5984 Delete xovis db if it exists and try it again. Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] xovis on the XSCE 5.0
On 06/15/2014 02:41 AM, Sameer Verma wrote: Hi Martin, I installed xovis on the XSCE 5.0 running on a XO 1.75 (512MB RAM, consuming 405MB or so right now). I've successfully registered a few XOs with the server. I see the backups in /library/users/ I see that I have a /opt/xovis folder. Does the database insert into couchdb run via cron? If not, how do I push the metadats into couchdb? Currently, this needs to be done manually by running script process_journal_stats.py, which is in the repository. I updated the installation instructions in the README yesterday, which explains how to install and use XOvis: https://github.com/martasd/xovis See the Load existing deployment data into the database section in the README. Are the instructions clear? Cheerios, Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] XSCE usage analysis: Malaysia Deployment
On 15.4.2014 19:06, George Hunt wrote: To some extent, it will depend on which services you are using in Malaysia. As starters: * /var/log/ -- has system messages, and all the squid cache stuff * /library/users -- will have all the XO client backups for all the XO's that have been registered with the server To visualize data Journal backup data from /library/users, you might be interested in using XOvis, an HTML/JS application I've been developing while at OLE Nepal. Please see the Github repo for instructions on how to install and use it: https://github.com/martasd/xovis Hope you find it useful. Best, Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] XSCE usage analysis: Malaysia Deployment
On 23.4.2014 16:49, tkk...@nurturingasia.com wrote: Thanks for the instructions. Let see if we could get that going. Let me know if you run into any issues with the installation, T.K.. Because of the default Fedora 18 partition limited space was reserved for the /library in our XSCE. This lead to error :-)and also ejabberd crash. How much space is available? Can the partition be enlarged? Cheers, Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] XO Visualization Feature
Hi everyone, I would like to give you an update about XOvis, XO data visualization application that I would like to integrate with XSCE. What is XOvis? It's so-called couchapp- an HTML/Js application that stored and served from a Couch database. The app uses HighCharts Javascript library to create charts from data gathered from XO Journal backups on XS. Recently, I have published a blog post on OLE's blog about deploying the app on schoolservers in Nepali schools: http://blog.olenepal.org/index.php/archives/842 There are two main parts of the application. First, there is a python script process_journal_stats.py, which access raw Journal backup data from /library/users and loads them into a couch database. This script lives in http://github.com/martasd/xo-stats Then there is the HTML/JS app itself, which visualizes the data stored in the browser. This is the couch app which is also stored in the database itself. To install the app, one simply needs to install CouchDB and then get the database either through so-called replication or loaded from a db dump. Thus far, I've been using Cloudant to host the database with the application, but have run into errors when trying to replicate it from there. I am currently in the process of setting up the publicly accessible instance on sunjammer, where much of Sugarlabs infrastructure is hosted, but before that's available the best option for installing the database is to load it from a db dump (which I fetch from my GitHub repo). To install the application, I've written deploy_xovis.sh, which I have now translated into ansible's language, so that it can be integrated with XSCE. I have tested it on 64 bit Fedora 18 and made sure it can be run idempotently there. Currently, I don't have access to other machines to test the feature on. I've added XOvis as a feature to http://wiki.laptop.org/go/XS_Community_Edition/Features#Features_Planned and just created a pull request on GitHub which includes the ansible role 'xovis' as well as its corresponding tag. I am looking forward to working to integrate this change with you! Cheers, Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [Sugar-devel] The quest for data
On 12.1.2014 10:12, Sameer Verma wrote: Has anyone created the wiki page as yet? Just created the wiki page: http://wiki.sugarlabs.org/go/Education_Team/Quest_for_Data Please help me expand it as you gather feedback from other deployments. Cheers, Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [Sugar-devel] The quest for data
On 7.1.2014 01:49, Sameer Verma wrote: On Mon, Jan 6, 2014 at 12:28 AM, Martin Dluhos mar...@gnu.org wrote: For visualization, I have explored using LibreOffice and SOFA, but neither of those were flexible to allow for customization of the output beyond some a few rudimentary options, so I started looking at various Javascript libraries, which are much more powerful. Currently, I am experimenting with Google Charts, which I found the easiest to get started with. If I run into limitations with Google Charts in the future, others on my list are InfoVIS Toolkit (http://philogb.github.io/jit) and HighCharts (http://highcharts.com). Then, there is also D3.js, but that's a bigger animal. Keep in mind that if you want to visualize at the school's local XS[CE] you may have to rely on a local js method instead of an online library. Yes, that's a very good point. Originally, I was only thinking about collecting and visualizing the information centrally, but there is no reason why it couldn't be viewed by teachers and school administrators on the schoolserver itself. Thanks for the warning. ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [Sugar-devel] The quest for data
On 10.1.2014 11:55, Anish Mangal wrote: Sorry for being late to the party. Clearly the quest for data is a commonly shared one, with many different approaches, questions, and reporting/results. One of the already mentioned solutions is the sugar-stats package, originally developed by Aleksey, which have now been part of dextrose-sugar builds for over a year, and the server side (xsce). http://wiki.sugarlabs.org/go/Platform_Team/Usage_Statistics The approach we followed was to collect as much data as possible without interfering with sugar-apis or code. The project has made slow progress on the visualization front, but the data collection front has already been field tested. I for one think there are a few technical trade-offs, which lead to larger strategy decisions: * Context v/s Universality ... Ideally we'd like to collect (activity) context specific data, but that requires tinkering with the sugar api itself and each activity. The other side is we might be ignoring the other types of data a server might be collecting ... internet usage and the various other logfiles in /var/log * Static v/s Dynamic ... Analyzing journal backups is great, but they are ultimately limited in time resolution due to the datastore's design itself. So the key question being what's valuable? ... a) Frequency counts of activities? b) Data such as upto the minute resolution of what activities are running, which activity is active (visible when), collaborators over time ... etc ... In my humble opinion, the next steps could be: 1 Get better on the visualization front. 2 Search for more context. Maybe arm the sugar-datastore to collect higher resolution data. I think that you are absolutely right, Anish. In my project, I am currently focused on the former point, but I am running into limitations regarding the data stored in the datastore. As Sameer suggested, let's create a wiki page with a list of the data that's the community finds important and then compare that list with what's currently collected in the datastore. ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] aliases for hacking on our XSCE school server
On 10/27/2013 02:20 PM, Samuel Greenfeld wrote: These are more of a user preference than anything necessary for XSCE to function. Exactly. Creating shell aliases should be each developer's business. Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XSCE | Proposing a quick turnaround 0.4.5 release
On 10/07/2013 09:51 PM, James Cameron wrote: Don't number it 0.4.5, instead number it 0.5, and push any plans you had for 0.5 out to 0.6. The sooner you get to 1.0 the more acceptable the version number will become. 0.4, based on the descriptions I see, is already 1.0 fodder. We have just discussed the XSCE Roadmap among those present at SF XSCE Hackathon. We have reached a consensus on the following schedule: 10/23: Design Freeze 11/14: Ansible migration completed and properly tested- release 0.5 (two days before Malaysia Summit) 12/6: Feature Freeze for 0.6 release 1/1: RC1 for 0.6 release 1/14: 0.6 Final release Does anyone have comments about or objections to this roadmap? Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] Supported Hardware Architectures
For the upcoming 0.5 release, we will be targeting the following hardware architectures: * Trim-Slice * XO-1.5, XO-1.75, X0-4 * i386 * x86_64 Feel free to provide XSCE support for other architectures, but these are the ones we believe are most useful to the user community. Martin ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] github workflow
On 10/23/2013 02:38 PM, George Hunt wrote: After some discussion at the sprint, I looked for documentation of the workflow as I understand it: https://www.atlassian.com/git/workflows#!workflow-forking https://www.atlassian.com/git/workflows#%21workflow-forking In case, the selected workflow doesn't show up for you as it didn't for me, the one we are using is Forking Workflow. ___ 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
