Simple method to have a per-project debian repository
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	yuvipanda
	Jun 29 2015, 1:06 PM

Description

Currently people use labsdebrepo which is a file based repository on NFS. Find an alternative that does not depend on NFS.

	Project	Branch	Lines +/-	Subject
	operations/puppet	production	+53 -0	aptly: Add module + simple role

Status	Assigned	Task
Resolved	yuvipanda	T105720 Labs team reliability goal for Q1 2015/16
Declined	None	T104193 Find replacements for various things that people were using NFS for but should not have been (Tracking)
Resolved	• chasemp	T104194 Simple method to have a per-project debian repository

Having a simple to use aptly role might be an answer?

yuvipanda set Security to None.

Only requirement is that it's easy to add new packages and has super low overhead.

Change 230375 had a related patch set uploaded (by Yuvipanda):
aptly: Add module simple role

Change 230375 merged by Yuvipanda:
aptly: Add module simple role

Wooo!

So:

Setup role::aptly on a 'server' instance. The default name is $project-packages, but you can override this by setting (via hiera) role::aptly::client:servername.
Apply role::aptly::client across all instances in your project.

To add a new package, on the aptly server:

sudo aptly repo add <repo-name> <package-file> where repo name is by default $distribution-project (eg. jessie-tools, jessie-ores, etc)
sudo aptly publish update repo <repo-name>

Tada! :)

yuvipanda moved this task to Done on the Labs-Sprint-111 workboard.

@yuvipanda: Is there more work left to do here? Or should this task be closed as resolved?

• chasemp claimed this task.