Don’t worry, the Band Pic is still here too!
Don’t think this is the first time I’ve announced a user friendly video upload system for our WordPress but I think it’s looking ready to try it out – again. Below is a video that came from my cell phone … Continue reading
The Eustace High School 2011 Senior Video produced by Ms. Lancaster’s Audio/Video Production class is now on the Graduation Ceremonies playlist. If player is not showing below click “Continue Reading”. Use “Download” button to get your own copy (wait several moments for … Continue reading
This gallery contains 2 photos.
Eustace High School senior band members are enjoying a five day cruise to Cozumel and the Yucatan peninsula. All have reported extreme satisfaction with the food and are looking forward to elegant attire and lobster tonight. Internet onboard ship is … Continue reading
This gallery contains 14 photos.
[kaltura-widget uiconfid=”1727916″ entryid=”0_qtlkubln” width=”400″ height=”330″ addpermission=”2″ editpermission=”2″ align=”center” /] If you have some pics to share from the one act play, add them in a comment or new blog post. Check back & watch for video! VIDEO NOW AVAILABLE FOR … Continue reading
In January 2011, I assisted 4th grade teacher Amy Huggins in introducing her students to Google Presentations and using it collaboratively. The first presentation below is an example of their work which was done in groups of three. The second … Continue reading
by Rusty Meyners.
Original (or at least previous) publish date: Wednesday, 12 May 2010, 11:47 AM
Here's what didn't work and did work for us when testing the entire Freshman class of around 90 students simultaneously on netbooks with wireless connections.
Server install DID NOT work – obviously and decidedly so.
- It seemed the most natural way to do things and bandwidth considerations seemed to be the only issue flagged in the Pearson documentation. We had tested groups of class size or smaller in the past with barely tolerable results, usually not seeming to be related to bandwidth. Testing 90 simultaneously crapped out after less than 2 dozen connections. In this case we were using netbooks on wireless connections but no change in perfomance was noted on several that were plugged into ethernet. Best guess is that the program files did not play well when in use by so many users – NOT A GUESS is that critical files were easily broken in this scenario and re-install was the so-called "fix".
Proctor Caching DID work – apparently.
- We have no observation of how things would have performed without this but none of the problems we had indicated a problem with caching, particularly considering good performance after changes were made only to components other than this.
Local install DID work – WITH A TWIST
- After it appeared that a local install was the solution (the Pearson documenation DID NOT give any indication to this effect but phone support did) we successfully circumvented the need to perform a full install on each machine by merely copying the folder from the server installation to each local desktop (NOT an idea we got from phone support). It may be possible to to the same thing with a local install folder but be sure the proctor caching settings are correct and if necessary edit the configuration file for that purpose. No critical .ini files were broken on 90 local instances.
Some tips on this:
- Zip the folder and copy it by USB to the local desktop where it is then unzipped in a separate action and ready for use. It could be copied directly from network but might result in an annoying bottleneck. Attempting to unzip directly from the network share will probably aggravate the bottleneck and uzipping from the USB stick will also be slower than performing the separate actions. This makes a difference when prepping more than a class-sized group.
- If possible, set relevant temp-file paths (different on server vs. local installs) when performing the original install that you are going to copy. Not critical, because we performed an adjustment to each local computer and it wasn't horrendous (compared to running from server the previous day) but could be avoided. The correction is requested after logging in: just click Browse and the default path is normally suitable but if it doesn't work, just click "Skip Upload" (assuming student has no work to save yet).
- On our netbooks, there were two suitable resolution settings, changed by hot-key, however making this change after the test starts will trip the cheat-detector and require the test to be restarted. So try to confirm a correct resolution before hand.
- Because our netbooks are on full-time assignment to students, a special domain login was implemented to ensure a clean profile with less chance of junkware interference.
(Will put updates or link to them here
Now that this reminds me NOT to do network install (hard to believe I'd forgotten THAT), here are some things that immediately come to mind.
Will probably script the copying AND unzipping of files involved in "Local Install" as described above in #3 (WITH A TWIST).
- have recently used scripting for similar delivery from network shares with encouraging results
- 7z zip utility (free) has proven very efficient and effective for this and works well with scripting
After optimizing scripting and zip procedures, will likely retest these from network shares as well as USB or SD card delivery, to evaluate which is/are preferable.
by Rusty Meyners.
Recieved email request today for links to info about new Google Apps for Education account features & changes as well as Moodle-Google SSO integration. This is the reply:
by Rusty Meyners.
Why an "optimized" version of Khan Academy OFFLINE?
by Rusty Meyners.
Regarding Windows or Linux:
Moodle is a Linux native along with the majority of the available support. My duties, skills and salary are too Windows-dependent to devote the time to mastering Linux that I’d like; but having said that, I couldn’t personally recommend Windows for a Moodle.
Regarding the Virtual vs. “Real” question:
Our Moodle has been a Linux virt from day one around 2.5 years ago and I’d do it again exactly the same today. BUT it is on the OpenVZ flavor of virtualization which is quite different from the VMWare solution that most people default to.
FULL VIRTUALIZATION (and para-virt)
VMWare is one of many flavors of FULL virtualization which use processing and memory resources for a software imitation of the hardware components in an imaginary machine on which you install your system. Fully virtual machines for the most part do not even know they are not actual boxes of metal and silicon. A subset is “para-virtual” where the virt has special drivers and awareness that it can get more direct and efficient access to the “real” hardware. Other solutions including (Free/OpenSource) such as KVM (on Linux but able to host Windows) and XEN work in a similar fashion to VMWare.
OpenVZ only virtualizes or “partitions” the operating system and uses hardly any extra resources to do so. This keeps most of the advantages of virtualization and brings more benefits to the mix, especially in the way of performance. OpenVZ only works (last I heard) with Linux systems, though there is an expensive proprietary version for Windows that has gone by various names such as Virtuozzo and (I think) Containers(?). If you are using or even considering Linux implementation, getting familiar with OpenVZ would be an extremely valuable investment of your time, as I believe it almost never makes sense to virtualize Linux any other way. With OpenVZ I have can (and often do) have a production Moodle system running alongside a production KalturaCE, BackupPC, FOG and sandbox space for trying out any flavor of Linux system that catches my attention (Mahara is next on that list). Normally we have these spread out over several host boxes but the beauty of virtualization is the portability, disaster recovery and load balancing potential.
ProxMox is the actual “brand” of virtualization we use and it is Free/OpenSource with pay support options. It combines KVM Full Virtualization and OpenVZ OS Virtualization for multiple Linux AND Windows virts in the same host system and may be one of the fastest ways around to get into the virtualization business. It requires fairly new 64bit hardware with virtualization support which includes almost any decent server hardware you would be considering anyway. I would love to help anyone in education trying to get started with ProxMox.