spin up small vm for releng mobile dashboard

VERIFIED FIXED

Status

Infrastructure & Operations
RelOps
VERIFIED FIXED
6 years ago
4 years ago

People

(Reporter: bear, Assigned: MaRu)

Tracking

Details

(Whiteboard: [android][tegra][buildslaves])

(Reporter)

Description

6 years ago
Right now the current tegra dashboard is a parasite to one of the mobile talos web hosts and with the increase in tegra load it is starting to impact that service's ability to handle the talos load.

I would like to request a small vm that has a single cpu and a small disk for the short term use by the dashboard.  this vm will live as long as it takes to land the new releng dashboard.

Single CPU
Any linux OS
Small disk (current needs are < 250M but could grow to 500M)
(Reporter)

Updated

6 years ago
Whiteboard: [android][tegra][buildslaves]
How much memory does your vm require?
I assume that this should be located in mtv1 where the tegras are, correct?
Any special network requirements (my default assumption is that it just needs an IP on the releng vlan)?
(Reporter)

Comment 2

6 years ago
Can we start with the smallest "normal" memory profile?

releng only IP is great - all of the foopies will be sending this vm data every 15 minutes.

A detail I forgot is that it will need some kind of web server that releng people need to see.
Adding a web server (apache) means that we're talking a larger memory footprint than our smallest profile.  Let's start with the following and up (or decrease) the memory if required (but it won't increase the swap, so if you think you'll need more, please speak up now):

CentOS 5.5 vm on the mtv1 kvm cluster
20GB disk
1 CPU
2GB RAM
Build network IP
A/PTR: mobile-dashboard1.build.mtv1.mozilla.com
CNAMEs: mobile-dashboard1.build.mozilla.org, mobile-dashboard.build.mozilla.org

(that leaves us room to grow with more in the back end later if required)
Assignee: server-ops-releng → mlarrain
(Reporter)

Comment 4

6 years ago
(In reply to Amy Rich [:arich] [:arr] from comment #3)
> Adding a web server (apache) means that we're talking a larger memory
> footprint than our smallest profile.  Let's start with the following and up
> (or decrease) the memory if required (but it won't increase the swap, so if
> you think you'll need more, please speak up now):

This project does have the potential to "leak" feature wise, so yes your saner adjustments to my request make sense

> 
> CentOS 5.5 vm on the mtv1 kvm cluster
> 20GB disk
> 1 CPU
> 2GB RAM
> Build network IP
> A/PTR: mobile-dashboard1.build.mtv1.mozilla.com
> CNAMEs: mobile-dashboard1.build.mozilla.org,
> mobile-dashboard.build.mozilla.org
> 
> (that leaves us room to grow with more in the back end later if required)
(Assignee)

Comment 5

6 years ago
This VM is being created right now.
I've set the root pw on the vm to the releng root pw.  It's ready for you guys to puppetize.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Reporter)

Comment 7

6 years ago
Thanks, I've connected to the host successfully
(Reporter)

Updated

6 years ago
Status: RESOLVED → VERIFIED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.