Hey there, Maybe the unconference is a good opportunity to speak about Matterhorn Operations ? There are indeed quite a few topics we could discuss.
Here are a couple of ideas in addition to the upgrade path issue of this thread: -Simplifying current production environment -Services status notifications -Metrics -Ops Personas -Ops UI -Roadmap:Ops requirements -DevOps group ************* Jaime Gago Systems Engineer Entwine - Knowledge In Motion www.entwinemedia.com @entwinemedia on Twitter On Jan 27, 2012, at 4:01 PM, Olli Salo wrote: > > Hi Tobias, > >> So are you saying that you *do* need an upgrade path to 1.3? > At this moment, as we have told our pilot users that we're only piloting MH > and it's not production ready in our case, the answer is actually no: there > is no need for an upgrade path from 1.2 to 1.3 (in our case, that is). But > I'd very much want to take MH into production use, and that's where the > upgrade scripts become very important. You see: our colleagues in the > different Departments would come to our office with a baseball bat if we told > them that their videos in the production environment would be thrown to trash > after each upgrade. :) > > I personally hope that immediately after the release of 1.3 we could throw > our MH 1.2 pilot setup to trash and set it up again, this time using the > openjdk instead of Sun Java and maybe mysql instead of postgresql, if mysql > is the db that MH supports best. The idea behind this is to make our MH > servers more robust than in our 2011 pilot. At this phase we would very much > want to try any upgrade methods, if possible, and also report back possible > bugs, if we should find any. I mean: if there is a good soul who has the > knowledge and time to write the upgrade scripts then we'd be extremely > interested in giving them a try. And if I understood you right, Tobias, this > could maybe take place say... starting from 1.3? > > After the server hardening + upgrade testing we will most likely concentrate > our effort into first understanding how the roles work in MH 1.3 and then > trying to hook the MH 1.3 (or MH 1.4?) to our shibboleth identity provider > (maybe Fall 2012, if everything goes fine). This is all very preliminary yet, > as I haven't yet got the funds for this year nor I'm fully aware of how the > roles work in MH. :/ But like said, that's the plan and if everything should > go fine, it is indeed our hope that we'd be able to take MH into production > in within a year and a half or so. That said, I'd actually like to ask how > you others are using your MH setups. If I've understood it right some are > already running their MH servers in production. How in those cases you deal > with your existing media packages during the MH upgrades? Do you ingest it > all back into the newly set up servers or do you throw the vids to trash? :-) > > Tobias you're absolutely right about the open source -ideology. It is all > about giving what you have instead of demanding everything ready-made on a > silver plate. I really wish that we (me + my colleagues) too will be able to > commit something back to the MH project in the near future, as we see your > work _extremely valuable_ and want to make sure MH evolves not only because > your work but because everyone committing for the MH community. That said, > I'd like to emphasize that my intention was not to critisize - please forgive > me if I sounded like that - but simply utter my concern and anxiety. :) > > You guys have been working really hard with the MH 1.3. It looks really > awesome and that's why I'd like to thank you all who have been designing / > writing the code. :-) > > Schönen Feierabend! ;-) > > Yours, Olli > > > > > > If so, which version are you upgrading from? Another question would be when > you intend to move to 1.3.x or in other words, would it be possible to do > work on these scripts *after* the release of 1.3? >> >> Please note that I can't promise that somebody will actually start working >> on it. But if you are able to show commitment in one way or another, or at >> least ask in a nice way, that will certainly help motivate people that don't >> need the upgrade scripts themselves to invest time into them. At the end of >> the day, it's give and take that makes open source strong! >> >> Tobias >> >> On 27.01.2012, at 13:03, Olli Salo wrote: >> >>> thank you Tobias for your message. Even though the work isn't done yet with >>> the upgrade scripts, it is good to hear it has been discussed in dev >>> meetings. After all, one day the "honeymoon" of pilot use will be over in >>> our Universities and we start to use our MH installations as production >>> environments. That's the time when our sysadmins are either going to love >>> or hate MH. :-) >>> >>> I would gladly make the script if I was knowledgeable enough with coding. >>> However, I haven't been given too much of coding skills. :/ That is why I >>> can only comment this topic. But I wish our Uni will be able to commit to >>> the MH project some other way in the near future. >> >> >> _______________________________________________ >> Matterhorn-users mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > > > -- > Olli Salo > Tietotekniikkakeskus > Helsingin yliopisto > Tel: +358 9 191 21782 > Gsm: +358 50 407 5509 > Email: [email protected] > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
