[SAC] [Hosting] {ns1, ns2}.osuosl.org RAID firmware upgrade Aug 10, 2017 10:30AM PDT (1730 UTC)

Oops, I just realized I had the wrong date in the subject. The correct date is August 10th at 10:30am.

···

On Wed, Aug 9, 2017 at 9:45 AM, Lance Albertson <lance@osuosl.org> wrote:

All,

I need to perform a RAID firmware upgrade on both ns1 and ns2 tomorrow at 10:30AM. This upgrade is required to resolve an issue we ran into as described in this CentOS bug [1]. I plan to to the steps described in this comment [2] to resolve the issue.

Here’s my plan for the upgrade:

  1. Bring down 140.211.166.130 on ns1 and move it to ns2
  2. Disable 140.211.166.130 from coming back up on ns1 during the upgrade as I require several reboots
  3. Do the upgrade tasks as described in [2].
  4. Once the fix is validated, move 140.211.166.130 back over to ns1 and re-enable it the network config

For ns2, I’ll do the same steps but moving its IP (140.211.166.131) to ns1. This should cause minimal downtime and outages for anyone using our DNS servers.

If you have any questions or concerns please let me know.

Also, just a friendly plug and reminder that our crowd funding campaign [3] has 16 days left!

Thanks-

[1] https://bugs.centos.org/view.php?id=13184
[2] https://bugs.centos.org/view.php?id=13184#c29499
[3] http://osl.io/crowdfunding

Lance Albertson

Director
Oregon State University | Open Source Lab

Lance Albertson

Director
Oregon State University | Open Source Lab

Unfortunately I couldn’t get the new firmware to kick in as it looks like I’m using a slightly different controller as described in the bug. I’ve backed out on the upgrade and brought ns1 back in. I’ll do more research and reschedule another outage once I figure out how to fix it properly.

Thanks-

···

On Wed, Aug 9, 2017 at 10:00 AM, Lance Albertson <lance@osuosl.org> wrote:

Oops, I just realized I had the wrong date in the subject. The correct date is August 10th at 10:30am.

On Wed, Aug 9, 2017 at 9:45 AM, Lance Albertson <lance@osuosl.org> wrote:

All,

I need to perform a RAID firmware upgrade on both ns1 and ns2 tomorrow at 10:30AM. This upgrade is required to resolve an issue we ran into as described in this CentOS bug [1]. I plan to to the steps described in this comment [2] to resolve the issue.

Here’s my plan for the upgrade:

  1. Bring down 140.211.166.130 on ns1 and move it to ns2
  2. Disable 140.211.166.130 from coming back up on ns1 during the upgrade as I require several reboots
  3. Do the upgrade tasks as described in [2].
  4. Once the fix is validated, move 140.211.166.130 back over to ns1 and re-enable it the network config

For ns2, I’ll do the same steps but moving its IP (140.211.166.131) to ns1. This should cause minimal downtime and outages for anyone using our DNS servers.

If you have any questions or concerns please let me know.

Also, just a friendly plug and reminder that our crowd funding campaign [3] has 16 days left!

Thanks-

[1] https://bugs.centos.org/view.php?id=13184
[2] https://bugs.centos.org/view.php?id=13184#c29499
[3] http://osl.io/crowdfunding

Lance Albertson

Director
Oregon State University | Open Source Lab

Lance Albertson

Director
Oregon State University | Open Source Lab

Lance Albertson

Director
Oregon State University | Open Source Lab