Closed
Bug 1293321
Opened 9 years ago
Closed 9 years ago
Deployment Plan for Vendor Tarballs in SCL3
Categories
(bugzilla.mozilla.org :: Administration, task)
Tracking
()
RESOLVED
FIXED
People
(Reporter: dylan, Assigned: dylan)
References
Details
Attachments
(1 file)
|
775 bytes,
text/plain
|
Details |
We need to plan to deploy the vendor tarballs to SCL3 nodes.
The first issue is to figure out file deployment.
I think we can deploy a pre-compiled local directory.
Attached is a list of libraries that the binary perl modules are linked against. They all appear to be present in production. I know that RPMs can depend on libraries. the output of perl -V on centos 6 is nearly the same as SCL3's EL6, the only difference being some timestamps.
fubar: Is it a sound idea to rely on binaries built on centos 6 working under EL6?
Flags: needinfo?(klibby)
|
Assignee | |
Comment 1•9 years ago
|
||
The plan is to put a pre-compiled local directory on each node, at /opt/bmo/local.
I have done this on bugzilla-dev and the admin node as: sudo tar -C /opt -xvf vendor.tar.gz bmo/local/
where vendor.tar.gz is http://s3.amazonaws.com/moz-devservices-bmocartons/bmo/vendor.tar.gz
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(klibby)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•