OSCER-USERS-L Archives

OSCER users

OSCER-USERS-L@LISTS.OU.EDU

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Type:
multipart/alternative; boundary="_000_BN9PR03MB618824E13AAD351A06B700C6BA472BN9PR03MB6188namp_"
Date:
Thu, 17 Oct 2024 01:39:51 +0000
Reply-To:
"Mueller, John P." <[log in to unmask]>
Subject:
From:
"Mueller, John P." <[log in to unmask]>
Message-ID:
In-Reply-To:
MIME-Version:
1.0
Sender:
OSCER users <[log in to unmask]>
Parts/Attachments:
text/plain (1788 bytes) , text/html (8 kB)
OSCER users,

The maintenance for OSCER systems has ended, and all systems should be operating normally.

Many thanks for your patience!

The OSCER Team
[log in to unmask]<mailto:[log in to unmask]>

From: OSCER users <[log in to unmask]> on behalf of Mueller, John P. <[log in to unmask]>
Date: Wednesday, October 16, 2024 at 7:58 AM
To: [log in to unmask] <[log in to unmask]>
Subject: Re: OSCER scheduled maintenance outage Wed Oct 16 8am-midnight CT
OSCER users,

Scheduled maintenance for ALL OSCER systems is now starting. Please save your work and log off. We expect them to be back online by midnight Oklahoma time. We'll send out another alert when the maintenance is complete.


The OSCER Team

[log in to unmask]<mailto:[log in to unmask]>

From: OSCER users <[log in to unmask]> on behalf of Neeman, Henry J. <[log in to unmask]>
Date: Thursday, October 10, 2024 at 11:53 AM
To: [log in to unmask] <[log in to unmask]>
Subject: OSCER scheduled maintenance outage Wed Oct 16 8am-midnight CT


OSCER users,


OSCER scheduled maintenance outage Wed Oct 16 8am-midnight CT

Affected systems: supercomputer, OURcloud, OURdisk, OURRstore,
OneOklahoma Friction Free Network (OFFN)



Specifically:



(1) Configure and restart all OpenStack virtualization physical servers,

including the supercomputer support Virtual Machines (VMs) and

OURcloud VMs running on those physical servers, to ensure

compatibility for automatic failover of VMs.



(All OSCER systems depend on OSCER's OpenStack environment.)



(2) Replace RAM sticks in several OpenStack virtualization application

servers.



If time permits, we might also do some other maintenance items.



We apologize for the inconvenience -- as always, our goal is to

make OSCER's capabilities even better.



The OSCER Team

[log in to unmask]


ATOM RSS1 RSS2