You would use deploy to create an individual repository (mini spin) for each server. At that point, content would be frozen. When you wanted to update the repository for that server, you would run deploy again to integrate, test and release new packages. -----Original Message----- From: centos-devel-bounces at centos.org [mailto:centos-devel-bounces at centos.org] On Behalf Of Les Mikesell Sent: Tuesday, April 22, 2014 11:08 AM To: The CentOS developers mailing list. Subject: Re: [CentOS-devel] ostree as a delivery model On Tue, Apr 22, 2014 at 11:49 AM, Kay Williams <kay at deployproject.org> wrote: > As a side note - the deploy tool (deployproject.org) can be used to > pull together a set of packages (essentially a lightweight spin), test > install and update, and deploy to one or more systems using standard > tools (anaconda, yum). It can also be used to script ostree creation > (or vm or ISO image creation, or ...) starting from the mini spin. Does the deploy tool make reproducible copies? And if so, does it require a frozen copy of a repository or the specific packages to do it? That is, if you have 6 different types of servers that are updated on different schedules, would you have to maintain 6 different repository mirrors, each frozen at the time each instance was tested and kept for as long as you might want to reproduce that tested system? Or does this even do updates at all? -- Les Mikesell lesmikesell at gmail.com _______________________________________________ CentOS-devel mailing list CentOS-devel at centos.org http://lists.centos.org/mailman/listinfo/centos-devel