infra/tickets

Fork 1

setup and provision older hw from iad2 in rdu3 #12677

New issue

Closed

opened 2025-07-21 21:50:46 +00:00 by kevin · 10 comments

kevin commented

2025-07-21 21:50:46 +00:00

Owner

We shipped the newest of our hardware from the old (iad2) datacenter to the new one (rdu3).

Now we need to configure and provision them. I have already done some, and can do more, but I think @gwmngilfen wanted to look at improving the process, etc.

Basically we need to:

reset admin password to the new one
Do any configuration we normally did for new hardware. Note that we can't just use the existing xml template probibly because these are various hardware types, not all the same as the new rdu3 hardware is. This would include power balancing, email alerts, host/domain name, etc
We may need additional kickstarts as some of these have different amounts of disks, etc.
Finally add them to ansible and provision them.

I've already added their mgmt to dhp. I've already added them in dns.

We could track things in a hackmd I guess for easy editing...

https://hackmd.io/-OpsqehASe-s7XfUpJYokQ

We shipped the newest of our hardware from the old (iad2) datacenter to the new one (rdu3). Now we need to configure and provision them. I have already done some, and can do more, but I think @gwmngilfen wanted to look at improving the process, etc. Basically we need to: * reset admin password to the new one * Do any configuration we normally did for new hardware. Note that we can't just use the existing xml template probibly because these are various hardware types, not all the same as the new rdu3 hardware is. This would include power balancing, email alerts, host/domain name, etc * We may need additional kickstarts as some of these have different amounts of disks, etc. * Finally add them to ansible and provision them. I've already added their mgmt to dhp. I've already added them in dns. We could track things in a hackmd I guess for easy editing... https://hackmd.io/-OpsqehASe-s7XfUpJYokQ

james commented

2025-07-22 18:58:30 +00:00

Member

Metadata Update from @james:

Issue priority set to: Waiting on Assignee (was: Needs Review)

**Metadata Update from @james**: - Issue priority set to: Waiting on Assignee (was: Needs Review)

kevin commented

2025-09-04 17:14:23 +00:00

Author

Owner

Progress is being made. :) Mostly by @gwmngilfen

kevin commented

2025-09-04 17:14:24 +00:00

Author

Owner

Metadata Update from @kevin:

Issue assigned to gwmngilfen

**Metadata Update from @kevin**: - Issue assigned to gwmngilfen

gwmngilfen commented

2025-09-10 13:22:32 +00:00

Member

Issue tagged with: sprint-0

gwmngilfen commented

2026-01-12 15:34:46 +00:00

Member

Metadata Update from @gwmngilfen:

Issue untagged with: sprint-0

**Metadata Update from @gwmngilfen**: - Issue **un**tagged with: sprint-0

kevin commented

2026-04-09 15:30:22 +00:00

Author

Owner

I'll see whats left here and try and finish up things... or at least get them to a state where we are happy.

kevin commented

2026-04-11 00:04:05 +00:00

Author

Owner

I updated firmware and installed buildhw-x86-05/06/07... filed a pr to add them to ansible. We can either have a freeze break or wait until after freeze.

infra/ansible#3277

I updated firmware and installed buildhw-x86-05/06/07... filed a pr to add them to ansible. We can either have a freeze break or wait until after freeze. https://forge.fedoraproject.org/infra/ansible/pulls/3277

gwmngilfen self-assigned this

2026-07-09 13:27:06 +00:00

gwmngilfen added this to the Sprint ( 2026-06-29 to 2026-07-12) project

2026-07-09 13:27:10 +00:00

gwmngilfen commented

2026-07-13 13:05:19 +00:00

Member

All the ones under "ready to go" are now done, leaving the STG P9 and the TBD hosts.

Note that buildhw-x86-11 seems to have ECC errors, and is getting 50% packet loss, we should check that.

All the ones under "ready to go" are now done, leaving the STG P9 and the TBD hosts. Note that buildhw-x86-11 seems to have ECC errors, and is getting 50% packet loss, we should check that.

gwmngilfen modified the project from Sprint ( 2026-06-29 to 2026-07-12) to Sprint ( 2026-07-13 to 2026-07-26)

2026-07-13 14:54:54 +00:00

gwmngilfen added

points

and removed

Priority

Waiting on Assignee

labels

2026-07-13 14:56:15 +00:00

kevin commented

2026-07-13 16:53:59 +00:00

Author

Owner

For the staging power9 we could just get this moved over to be another copr vmhost...

We can leave the TBD ones for now.

On -11, we could update firmware on it? If it's still erroring and having problems, we can just power it off and mark it for spare parts if we need them I think.

For the staging power9 we could just get this moved over to be another copr vmhost... We can leave the TBD ones for now. On -11, we could update firmware on it? If it's still erroring and having problems, we can just power it off and mark it for spare parts if we need them I think.

gwmngilfen closed this issue

2026-07-27 14:20:14 +00:00

gwmngilfen commented

2026-07-27 14:20:31 +00:00

Member

Closing this, just the p9 to go and it's being a pain :/