Closed Bug 1049519 Opened 7 years ago Closed 7 years ago
spare hp blades, new blade quote
Do we have any spare HP blades similar to the hgweb blades? (G7s, 12gb memory, 1 cpu) Can we also get a quote for new (G8?) blades, 2 cpu, 24gb memory. Two disk options: use the 600gb SAS drives that we got in bug 999659#c14 (so, blades w/ no disk), or new SSDs with around 600gb capacity. Thanks.
If we have spares we need them pretty desperately. This is for hgweb. Any chance today?
Here are the spares we have hot and ready to go: G6 - https://inventory.mozilla.org/en-US/systems/show/2047/ G1 - https://inventory.mozilla.org/systems/show/960/ G1 - https://inventory.mozilla.org/systems/show/450/
We'll take all those spares. Thanks dmoore!
Ashish found some standalone DL360 G7s, as well: [17:27:15] <@ashish> https://inventory.mozilla.org/systems/show/5263/ [17:27:19] <@ashish> https://inventory.mozilla.org/systems/show/5264/
G8 quote is out with the vendor, should get a reply by tomorrow.
Quote from vendor: 2 x Xeon E5-2620 (2.1GHz, 6-core) 32 GB RAM $2,895 per 600GB 6G SSDs are an additional $1,695 each from HP
hgweb9.dmz.scl3.mozilla.com -> https://inventory.mozilla.org/en-US/systems/show/5263/ KS with extra inodes per hg requirements, +puppetized, +rhn.
hgweb10.dmz.scl3.mozilla.com -> https://inventory.mozilla.org/en-US/systems/show/5264/ KS with extra inodes per hg requirements, +puppetized, +rhn. Both servers are added to monitoring as well. Dropping severity to not page oncall.
Severity: critical → normal
Taking bug for longer-term resolution.
Assignee: server-ops-dcops → dmoore
Current plan is to buy two new G8s, I believe. needinfo on laura for r+. longer term... all of the original eight hgweb nodes run out of warranty in February, so we'll work on a plan/budget for them at our arch meeting in September.
re-up/replacement of nodes coming out of warranty in bug 1077011. closing this one out.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.