Piloting Software Updates

[noah_swanson]

We've got one mac server. We're going to begin pushing software updates via this server, but we need to "pilot" these updates first. My question is, without a second server, or policies to execute this manually, is there a better way to push selected updates to a pre-defined group of computers? I've also toyed with the idea of disabling the client on all other systems then re-enabling once the pilot testing is done, however this is less-than desirable. At this point, it looks like I'll be creating policies for each piloted update which I'm not too thrilled about.

Any suggestions?

Thanks,
Noah Swanson
Imaging Specialist
Enterprise Desktop Services
Phone: 309-765-3153
SwansonNoah at johndeere.com

[bentoms]

Munki allows you to create separate catalogs so 1 can be used as a test catalog.

Regards,

Ben.

[nessts]

Two update servers, and your pilot group gets pointed at the second server…
--
Todd Ness
Technology Consultant/Non-Windows Services
Americas Regional Delivery Engineering
HP Enterprise Services

[noah_swanson]

Ideally yes. It's nearly impossible to get any server put in here, let alone a second mac server. In the past year alone, I've had 5 requests denied...

[bentoms]

even though you've only 1 server, you can do the below with: http://managingosx.wordpress.com/2011/05/04/introducing-reposado/

[rockpapergoat]

when you say "push," what do you mean? since the software update services doesn't push anything, do you intend to use policies to specify updates installed via casper?

the easiest way to do part of what you want is to setup reposado for mirroring software updates, add a testing branch, and assign clients to that test branch. reposado is available here: https://github.com/wdas/reposado

branching allows you to approve updates for your default or production branch separately, so your testing machines can get the newest updates first. once tested, you add those to the production branch.

as far as pushing the updates, you can use casper to "install all available" using either branch or specify individual updates, as needed.

the process is similar if you want to use munki for this. both methods aren't so much a push as a triggered pull, though.

[tlarkin]

Reposado (or whatever it is called) doesn't require OS X Server and can be used as an SUS. You may look into that.

-Tom

[nessts]

Or virtualize the second server on the first server…
--
Todd Ness
Technology Consultant/Non-Windows Services
Americas Regional Delivery Engineering
HP Enterprise Services

[rockpapergoat]

reposado is a more flexible option all around. doesn't require os x server, and does more than apple's service anyway.

[jarednichols]

Reposado's definitely where it's at. Hopefully Apple will keep their hands off it.

j
---
Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436