Hello all,
It's the time to present myself. My name is Marek and I'm working for one big software company right now. Before I was in HP support, administrating HP-UX, linux and few AIXs. I really want help you to maintenance fedora project infrastructures, basically from admin side, but maybe form devel as well.
I think that it's maybe a good idea to build an escalation paths for infrastructure, to assure that at any time, there will be someone to fix things or get in touch with someone who can in case of problems.
Let me know how can I help and what do you think about my idea.
Marek Mahut wrote:
Hello all,
It's the time to present myself. My name is Marek and I'm working for one big software company right now. Before I was in HP support, administrating HP-UX, linux and few AIXs. I really want help you to maintenance fedora project infrastructures, basically from admin side, but maybe form devel as well.
I think that it's maybe a good idea to build an escalation paths for infrastructure, to assure that at any time, there will be someone to fix things or get in touch with someone who can in case of problems.
Its not a bad idea really except everything will ever get fixed right away or will escalate to me I think. I'm typically notified though last night didn't have my phone on :) Having said that though, some volunteers may want to be called. Thats entirely up to them.
One thing that may be good is to create a sysadmin list with the appropriate timezone everyone is in.
-Mike
Mike McGrath wrote:
Marek Mahut wrote:
Hello all,
It's the time to present myself. My name is Marek and I'm working for one big software company right now. Before I was in HP support, administrating HP-UX, linux and few AIXs. I really want help you to maintenance fedora project infrastructures, basically from admin side, but maybe form devel as well.
I think that it's maybe a good idea to build an escalation paths for infrastructure, to assure that at any time, there will be someone to fix things or get in touch with someone who can in case of problems.
Its not a bad idea really except everything will ever get fixed right away or will escalate to me I think. I'm typically notified though last night didn't have my phone on :) Having said that though, some volunteers may want to be called. Thats entirely up to them. One thing that may be good is to create a sysadmin list with the appropriate timezone everyone is in.
In fact, and maybe with pages or cell numbers (for sms only, of course) too. I propose to do it as static html page, in case wiki goes down ;)
On Mon, 2007-06-04 at 23:30 +0200, Marek Mahut wrote:
In fact, and maybe with pages or cell numbers (for sms only, of course) too.
Maybe we can enable an alias (of sorts) for sysadmin paging. For example, kwade-page (at) fedoraproject.org would send to an SMS page number that I can specify in FAS.
The reason is to let us set strict and harsh spamassassin rules behind those aliases. Or perhaps an SMS is not passed through the alias channel unless it is sent from an email address that is on record for a FAS account holder. Or perhaps it is an even smaller list of people who can use that SMS, a specific set of From: email addresses and SMS numbers.
Personally, I want to know when infrastructure I have a stake in is having problems, but I don't want to be nagged by nagios. So, these are definitely escalation paths that need a human involved, probably one who has seen/heard of the problem and is sure it is real. Similarly, when I detect a problem that really needs intervention, I want a way to know that someone with a key and an interest knows about it. That for me was the most frustrating part of the F7 launch, when the first few days passed and problems arose, I was never sure it had anyone's attention and so stuff languished that had an easy resolution.
Even volunteers have good reason to want an early and useful page. Arriving Just In Time is not only good for one's hero profile, it also helps keep five minute solutions from being three hour problems.
- Karsten
Karsten Wade wrote:
On Mon, 2007-06-04 at 23:30 +0200, Marek Mahut wrote:
In fact, and maybe with pages or cell numbers (for sms only, of course) too.
Maybe we can enable an alias (of sorts) for sysadmin paging. For example, kwade-page (at) fedoraproject.org would send to an SMS page number that I can specify in FAS.
The reason is to let us set strict and harsh spamassassin rules behind those aliases. Or perhaps an SMS is not passed through the alias channel unless it is sent from an email address that is on record for a FAS account holder. Or perhaps it is an even smaller list of people who can use that SMS, a specific set of From: email addresses and SMS numbers.
Personally, I want to know when infrastructure I have a stake in is having problems, but I don't want to be nagged by nagios. So, these are definitely escalation paths that need a human involved, probably one who has seen/heard of the problem and is sure it is real. Similarly, when I detect a problem that really needs intervention, I want a way to know that someone with a key and an interest knows about it. That for me was the most frustrating part of the F7 launch, when the first few days passed and problems arose, I was never sure it had anyone's attention and so stuff languished that had an easy resolution.
Even volunteers have good reason to want an early and useful page. Arriving Just In Time is not only good for one's hero profile, it also helps keep five minute solutions from being three hour problems.
I'll add whoever wants to be added. We can also work a formal tree now if need be.
Don't make me regret this :-/
https://admin.fedoraproject.org/pager
-Mike
i think it would be wise to get Auth there... Or you will be wake up by lots of spammers :/
Paulo
On 6/13/07, Mike McGrath mmcgrath@redhat.com wrote:
Karsten Wade wrote:
On Mon, 2007-06-04 at 23:30 +0200, Marek Mahut wrote:
In fact, and maybe with pages or cell numbers (for sms only, of course) too.
Maybe we can enable an alias (of sorts) for sysadmin paging. For example, kwade-page (at) fedoraproject.org would send to an SMS page number that I can specify in FAS.
The reason is to let us set strict and harsh spamassassin rules behind those aliases. Or perhaps an SMS is not passed through the alias channel unless it is sent from an email address that is on record for a FAS account holder. Or perhaps it is an even smaller list of people who can use that SMS, a specific set of From: email addresses and SMS numbers.
Personally, I want to know when infrastructure I have a stake in is having problems, but I don't want to be nagged by nagios. So, these are definitely escalation paths that need a human involved, probably one who has seen/heard of the problem and is sure it is real. Similarly, when I detect a problem that really needs intervention, I want a way to know that someone with a key and an interest knows about it. That for me was the most frustrating part of the F7 launch, when the first few days passed and problems arose, I was never sure it had anyone's attention and so stuff languished that had an easy resolution.
Even volunteers have good reason to want an early and useful page. Arriving Just In Time is not only good for one's hero profile, it also helps keep five minute solutions from being three hour problems.
I'll add whoever wants to be added. We can also work a formal tree now if need be.
Don't make me regret this :-/
https://admin.fedoraproject.org/pager
-Mike
Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Paulo Santos wrote:
i think it would be wise to get Auth there... Or you will be wake up by lots of spammers :/
I'm not sure I want to add auth unless I have to because the auth system is something thats known to have issue in the past. I do want to add a time based buffer though, 1 page / minute or so.
-Mike
Mike McGrath wrote:
Paulo Santos wrote:
i think it would be wise to get Auth there... Or you will be wake up by lots of spammers :/
I'm not sure I want to add auth unless I have to because the auth system is something thats known to have issue in the past. I do want to add a time based buffer though, 1 page / minute or so.
K, that parts added now at least :) limit one page every 2 minutes.
-Mike
Hey Mike,
Mike McGrath wrote:
Karsten Wade wrote:
On Mon, 2007-06-04 at 23:30 +0200, Marek Mahut wrote:
In fact, and maybe with pages or cell numbers (for sms only, of course) too.
Maybe we can enable an alias (of sorts) for sysadmin paging. For example, kwade-page (at) fedoraproject.org would send to an SMS page number that I can specify in FAS.
The reason is to let us set strict and harsh spamassassin rules behind those aliases. Or perhaps an SMS is not passed through the alias channel unless it is sent from an email address that is on record for a FAS account holder. Or perhaps it is an even smaller list of people who can use that SMS, a specific set of From: email addresses and SMS numbers.
Personally, I want to know when infrastructure I have a stake in is having problems, but I don't want to be nagged by nagios. So, these are definitely escalation paths that need a human involved, probably one who has seen/heard of the problem and is sure it is real. Similarly, when I detect a problem that really needs intervention, I want a way to know that someone with a key and an interest knows about it. That for me was the most frustrating part of the F7 launch, when the first few days passed and problems arose, I was never sure it had anyone's attention and so stuff languished that had an easy resolution.
Even volunteers have good reason to want an early and useful page. Arriving Just In Time is not only good for one's hero profile, it also helps keep five minute solutions from being three hour problems.
I'll add whoever wants to be added. We can also work a formal tree now if need be.
Don't make me regret this :-/
It's also a good idea to mention your time zone.
Personally, I want to know when infrastructure I have a stake in is having problems, but I don't want to be nagged by nagios.
Then read about it expo-facto like the rest of the world.
infrastructure@lists.fedoraproject.org