Infra related events message - review needed

This is a multi-part message in MIME format. --------------C2C1B6C457A9CCD4A0E14F7B Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, We had some confusion last week when I sent a message about an infrastructure related issue we have found and people thought I was reporting an error on OST so I decided that perhaps it would be a good idea to create a general message that would alert people on an on-going infra event and not just OST related issues. iBelow is the format I was thinking of using: ############################################## Subject: Ovirt CI - [Infrastructure Incident] [$Date] [$TIME] Hello, We encountered an incident that can suggest there is an ongoing infrastructure incident. Our team is currently investigating the issue and we will send a mail once we have more information or the issue is resolved. Issue summary: ################################################ Please let me know what you're ideas on this are and if the message is at all lacking in some way. Thanks. Dafna --------------C2C1B6C457A9CCD4A0E14F7B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p>Hi, <br> </p> <p>We had some confusion last week when I sent a message about an infrastructure related issue we have found and people thought I was reporting an error on OST so I decided that perhaps it would be a good idea to create a general message that would alert people on an on-going infra event and not just OST related issues. <br> </p> <p>iBelow is the format I was thinking of using:<br> </p> <p><span style="font-weight:normal;"> <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">############################################## </span></p> <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Subject: Ovirt CI - [Infrastructure Incident] [$Date] [$TIME] </span></p> <br> <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Hello, </span></p> <br> <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">We encountered an incident that can suggest there is an ongoing infrastructure incident. </span></p> <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Our team is currently investigating the issue and we will send a mail once we have more information or the issue is resolved. </span></p> <br> <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Issue </span><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">summary</span><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">: </span></p> <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"> </span></p> <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">################################################ </span></p> </span></p> <p>Please let me know what you're ideas on this are and if the message is at all lacking in some way. <br> </p> <p>Thanks. <br> </p> <p>Dafna</p> <p><br class="Apple-interchange-newline"> </p> </body> </html> --------------C2C1B6C457A9CCD4A0E14F7B--

On 8 November 2017 at 13:25, Dafna Ron <dron@redhat.com> wrote:
Hi,
Please let me know what you're ideas on this are and if the message is at all lacking in some way.
There should be some scoping of the issue. We don't want people to ignore CI flags when there is an issue that only affects OST checking... -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
participants (2)
-
Barak Korren
-
Dafna Ron