[Meego-it] [MeeGo-community] IT Update

[David Greaves]

Keeping meego-it in the cc list

On 15/06/11 05:27, jukka.eklund at nokia.com wrote:
> Good stuff!
>
> What is the timeline of having the mentioned support for Community
> edition project? I guess something for fall still to ramp up regular
> operation?

Islam is working on this

> One thing I am slightly worried is that it creates more dependency on
> Nokia (to keep BOSS setup running). How do we mitigate that risk, any
> ideas?

Nokia aren't involved in keeping the BOSS setup running; BOSS is an 
opensource project with a completely independent deployment on the 
MeeGo.com infrastructure.

Clearly there's a general resourcing issue but I'm very optimistic that 
the systems development will continue.

> Jukka
>
> ________________________________________ From:
> meego-community-bounces at meego.com [meego-community-bounces at meego.com]
> on behalf of ext David Greaves [david at dgreaves.com] Sent: 15 June
> 2011 00:13 To: meego-it at lists.meego.com;
> meego-community at lists.meego.com Subject: [MeeGo-community] IT Update
>
> A few people have mentioned that the MeeGo IT group is one of the
> areas in MeeGo that needs to communicate better. I've drafted this
> update as a start. For this update only I've cross-posted to
> meego-community. In future I suggest we'll just post to the meego-it
> list. I also suggest follow-ups to the meego-it list.
>
> IT Update
>
> The MeeGo IT team looks after the infrastructure running MeeGo.com
> websites and services including the main site, wiki, conference,
> apps, news, Bugzilla, Community OBS, MXR, BOSS, ircbot, CAS, SDK, QA,
> Forums etc. We also manage DNS, LDAP, Nagios, backups and other
> internal services.
>
> We have over 50 virtual machines mainly running Debian Squeeze on top
> of opensuse 11.4 Xen hosts with LVM.
>
> Current outstanding projects :
>
> Migrate mailing lists Currently the meego.com mls are run on the old
> 'Softlayer' systems. The replacement OSU systems were setup a few
> weeks back but we got too close to the 1.2 release window and the
> conference so deferred the migration. The plan is to migrate these
> systems over the next couple of weeks.
>
> Monitoring We have a Nagios system in place and use Circonus to
> provide and 'external' view of MeeGo.com services. This is not fully
> deployed.
>
> Puppet Working on a puppet deployment template for OBS workers.
>
> Community OBS The Community OBS has just 5 worker machines (core has
> 35). We have ordered 3 more machines. The OBS is also running an
> oldish version of the OBS and we plan to upgrade that over the next
> 2-3 weeks. We are talking to the core OBS team to see if we can
> synchronise operational activities.
>
> CE Project We are setting up BOSS processes, an image-creation
> system, release and reporting capabilities for the CE team.
>
> Apps Project Apps was demoed at the conference and we plan to
> continue development of this (see below for communication update).
>
> EtherPad I proposed setting up a MeeGo etherpad service for people
> with a meego account. Eventually I hope this could be incorporated
> into the wiki editing system to allow collaborative editing.
> http://etherpad.com/ and http://piratepad.net/
>
> Communications Several people have pointed out that the IT team is
> poor at communicating.
>
> There are many excuses but the primary one is that we are running a
> complex system that needs to be kept secure. We are human beings and
> we will make mistakes; making a mistake in public means bad guys have
> the opportunity to attack in the (hopefully small) window until we
> fix it. Additionally the daily work we do is not particularly
> relevant to the MeeGo project (after all we manage openSuse and
> Debian systems).
>
> On the other hand the project *does* need to know what we're working
> on, what we're developing and planning. So what can we do:
>
> Participate in the CO review meetings to say what's happening.
>
> IRC : The team uses an invitation only channel to discuss day-to-day
> sysadmin and deployment work (including network and security issues)
> but I propose a new #meego-infra irc channel where people can
> discuss development and talk about systems and services. I'd like the
> main sysadmins and the admins and developers for various services
> (Bugzilla, OBS, BOSS, wiki, apps, irc ops, email etc) to try and be
> present on here during their working day. Please discuss and
> comment.
>
> email: The meego-it mailing list will be used for general IT
> announcements (although service specific announcements will be sent
> to the appropriate lists too - eg Bugzilla scheduled outages will go
> to -dev and -qa and probably others too) and can also be used as an
> alternative to irc for contacting the team. There is a
> "meego-distribution-tools" mailing list that may be suitable for
> general systems and tools
>
> David
>
> -- "Don't worry, you'll be fine; I saw it work in a cartoon once..."
> _______________________________________________ MeeGo-community
> mailing list MeeGo-community at meego.com
> http://lists.meego.com/listinfo/meego-community
> http://wiki.meego.com/Mailing_list_guidelines