Discussion:
IT meeting 10 Aug
David Greaves
2011-08-10 12:47:35 UTC
Permalink
Some suggestions for tonights IT conf call.

* I propose new IT bug structure:

1. Rename existing IT Bugs as 'Private IT Bugs'
2. New IT Bugs to allow public requests to be trackable
I propose that the general rule is that we create a private task for any bugs
that are internally generated operational tasks (as we do today) and also
tracking tasks for public requests that need some degree of confidential handling.
I agree there are bug trackers for individual components. The intention here is
for tasks that need some kind of IT activity. It's likely that some bugs raised
in 'General' will be moved to this section.

(It may be time to rethink:
https://bugs.meego.com/enter_bug.cgi?classification=MeeGo%20Community%20Infrastructure
)

* Core OBS admin
I propose that the meego.com superadmins who have root to everything (DNS, www,
email, LDAP and auth systems etc) are also allowed root acces to the core OBS.
(Probably with the exception of the signer)

We should discuss adding the core OBS config to dcp (shouldn't hurt)

* Monitoring
What's the situation and plan on monitoring.

* Forum/Email integration
http://forum.meego.com/showthread.php?t=3829&page=3
So Mike has a request to add the emails for the forum.
(Nb this whole task is the kind of bug I'd like to see as a public bug)

David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
David Greaves
2011-08-10 18:36:10 UTC
Permalink
Post by David Greaves
Some suggestions for tonights IT conf call.
1. Rename existing IT Bugs as 'Private IT Bugs'
2. New IT Bugs to allow public requests to be trackable
I propose that the general rule is that we create a private task for any bugs
that are internally generated operational tasks (as we do today) and also
tracking tasks for public requests that need some degree of confidential handling.
I agree there are bug trackers for individual components. The intention here is
for tasks that need some kind of IT activity. It's likely that some bugs raised
in 'General' will be moved to this section.
https://bugs.meego.com/enter_bug.cgi?classification=MeeGo%20Community%20Infrastructure
)
We decided to discuss this on the list and make a decision next week.
Post by David Greaves
* Core OBS admin
I propose that the meego.com superadmins who have root to everything (DNS, www,
email, LDAP and auth systems etc) are also allowed root acces to the core OBS.
(Probably with the exception of the signer)
We should discuss adding the core OBS config to dcp (shouldn't hurt)
David to ping Anas and Dawn again on Friday.
Post by David Greaves
* Monitoring
What's the situation and plan on monitoring.
Max has written a puppet setup to deploy nagios monitoring. We agreed to use
puppet for this task

* TODO Deploy Nagios using Puppet

We tried Circonus (external monitoring service) a while back. Felt nice, no
issues with it but no time to examine it further.
We need to add more metrics and notifications

* TODO Extend external monitoring via Circonus
* TODO Find a way to fund Circonus (sensibly, via LF)
Post by David Greaves
* Forum/Email integration
http://forum.meego.com/showthread.php?t=3829&page=3
So Mike has a request to add the emails for the forum.
(Nb this whole task is the kind of bug I'd like to see as a public bug)
Actually there is a nice public bug:
https://bugs.meego.com/show_bug.cgi?id=20533

It seems we now need to:
* Setup imap on forums (cyrus)
* Point the aliases at imap
* Enable plugin on forum
* Blocker is the lists move and MX record change

Additional issues:

Final move of the mailing lists needs the MX record moved. We agreed to do this
ASAP.

We discussed formeego.com and openly invited all members of current MeeGo IT
team to participate fully - treating the formeego.org infrastructure as an
extension of the MeeGo infrastructure as far as the community is concerned.

David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
Stefano Mosconi
2011-08-11 07:01:49 UTC
Permalink
Post by David Greaves
We tried Circonus (external monitoring service) a while back. Felt nice, no
issues with it but no time to examine it further.
We need to add more metrics and notifications
* TODO Extend external monitoring via Circonus
* TODO Find a way to fund Circonus (sensibly, via LF)
Also Adam took on the task to investigate with LF if they could provide this
kind of external monitoring for our services.

Stefano

Loading...