Closed Bug 1131120 Opened 10 years ago Closed 10 years ago

consider package repo mgmt options

Categories

(Socorro :: Infra, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dmaher, Unassigned)

References

()

Details

One of the potential side-effects of our move towards a more industrialised workflow for managing and deploying Socorro is an increased reliance on software packaging and distribution (i.e. .rpm and .deb repos). Some options: * createrepo * aptly (http://www.aptly.info/) * prm (https://github.com/dnbert/prm) * others? We may also wish to consider a 3rd-party package hosting services, the only one of which I can think of off the top of my head is https://packagecloud.io .
Another 3rd-party service: https://bintray.com/
We should defer this for now. It seems more like an optimization than a blocker.
Blocks: 1097891
No longer blocks: 1118288
PRM looked really promising; however, it appears to lack support for two critical items of interest to us: 1. Support for S3; https://github.com/dnbert/prm/issues/44 2. Support for actually building usable RPM repos; https://github.com/dnbert/prm/issues/38 Oh well.
For now we're going to self-host on S3. The real work here was in navigating the strange and arcane world of AWS ACL language, and in figuring out the relationship between bucket policies, IAM profiles, and EC2 nodes. I've worked through the elements (blog post to follow) and we now have a Yum repo at our disposal - there are even already packages in it. :) The workflow needs to be refined somewhat, but insofar as this bug is concerned, we're good to go.
Blocks: 1118288
No longer blocks: 1097891
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Blocks: 1137798
See Also: → 1168096
You need to log in before you can comment on or make changes to this bug.