Bug 1434532 - New machine for Jenkins staging
Summary: New machine for Jenkins staging
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-21 16:28 UTC by Nigel Babu
Modified: 2017-03-27 16:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-27 16:40:17 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Nigel Babu 2017-03-21 16:28:41 UTC
Hello,

Can we have a Jenkins staging box? I'd say just needs about as much capacity as gerrit stage. Unless that's too much. Let's go with Centos 7. I'll be testing migration to Centos 7 + Upgrade to the latest version on the staging server.

Comment 1 Michael S. 2017-03-21 17:29:58 UTC
So the current jenkins box has 8G of ram, the current gerrit-stage has 2G. But jenkins seems to use 3G, so would 4G be ok (for memory).

Comment 2 Nigel Babu 2017-03-22 03:25:09 UTC
How about we make this machine the new Jenkins production and allocate disk and memory appropriately? That means the switch over can happen with minimal disruption.

Comment 3 Michael S. 2017-03-23 16:36:03 UTC
Sure, we can do that. So i would recommend 4G of ram, 

For the disk, it seems to be around 120G for /d, which old all the build, with right now 60G of disk being used, so let's make it 100G for the data partition and 10G for the system partition. 

And for CPU, we have 1 CPU, I do not think we need more than that.

Would it be ok ?

Comment 4 M. Scherer 2017-03-27 16:40:17 UTC
Ok so the server is installed as jenkins-stage.rht.gluster.org , and is running on the usual virt hosts.


Note You need to log in before you can comment on or make changes to this bug.