…are available here.
…are available here.
If you are participating in the Packaging Workshop on July 7th at the Penn State MacAdmins Conference, you may want to download some materials in advance when you aren’t competing with all the other people for limited conference Wi-Fi bandwidth. Note — don’t install these items — just download their installers and keep them handy for the workshop.
Google Chrome dmg:
Some optional things:
“Payload-free” packages — that is, Apple installer packages that do not have a file payload, but only run scripts, are a nice tool for OS X admins to have. They provide a convenient way to deliver and execute scripts as root. If you have a way to install packages on your managed machines, you can also run scripts as root by wrapping them in a “payload-free” package.
Rich Trouton has written up the basic procedure using the built-in `pkgbuild` tool: https://derflounder.wordpress.com/2012/08/15/creating-payload-free-packages-with-pkgbuild/
But payload-free packages built this way have a “feature” that can sometimes prove problematic. Flat packages built with
pkgbuild using the
--nopayload option do not leave receipts in the
pkgutil database. This means it can be difficult to determine if a given payload-free package has already been installed on a given machine.
This is especially annoying with Munki: by default, when installing a package, Munki uses the package’s receipt(s) to determine whether or not the package has been installed. Without that receipt, and with no other information, Munki can’t tell if the package has been installed.
Fortunately, it’s trivial to make a pseudo-payload-free package that leaves a receipt. All we need to do is specify an empty payload!
Here’s how we make a “true” payload-free package (that does not leave a receipt):
pkgbuild --nopayload --scripts /path/to/scripts_dir --identifier org.example.payloadfree --version 1.0 MyGreatPayloadFree.pkg
and here’s a “pseudo” payload-free package that does leave a receipt:
pkgbuild --root empty --scripts /path/to/scripts_dir --identifier org.example.payloadfree --version 1.0 MyGreatPayloadFree.pkg
That’s it! Instead of using the
--nopayload option, we create an empty directory and point the
--root option at it. The package is built with the empty payload, and when installed, the package leaves a receipt.
Imagr requires a web server (or servers) to get its workflows, images to restore, and packages to install.
In an earlier post, I described setting up an existing DeployStudio NBI for Imagr testing.
If you are testing Imagr, or even better, hoping to help with its development, you’ll need to configure a test server.
You’ll need a web server, and a way to get some files on it. I just used my existing Munki repo web server. I created a new folder called “testing” and copied a few packages into it. (For first-boot install, Imagr currently supports only flat packages. For immediate install, bundle packages are OK if they are at the root of a disk image/.dmg file.).
Next, create a configuration plist. There’s an example here: https://github.com/grahamgilbert/imagr#the-configuration-plist. Here’s another:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>password</key> <string>40e78b0d11c553be61645796fdb9438271a23ed8b4aadb253a9222c6e4c861e2dbc75139000b0709fc0c5ad66b0f2573e38a72a8f629e270e59530fc3159d8e4</string> <key>workflows</key> <array> <dict> <key>name</key> <string>Munki Bootstrap</string> <key>description</key> <string>Installs the required pkgs to begin a Munki bootstrap on restart.</string> <key>components</key> <array> <dict> <key>type</key> <string>package</string> <key>url</key> <string>http://munki/repo/testing/DA_adminaccount_1.5.pkg</string> <key>pre_first_boot</key> <true/> </dict> <dict> <key>type</key> <string>package</string> <key>url</key> <string>http://munki/repo/testing/DisableSetupAssistant.pkg</string> <key>pre_first_boot</key> <true/> </dict> <dict> <key>type</key> <string>package</string> <key>url</key> <string>http://munki/repo/testing/munkitools-188.8.131.521.pkg</string> <key>pre_first_boot</key> <true/> </dict> <dict> <key>type</key> <string>package</string> <key>url</key> <string>http://munki/repo/testing/munki_kickstart.pkg</string> <key>pre_first_boot</key> <true/> </dict> </array> </dict> </array> </dict> </plist>
The password is a hash for “LETMEIN”; you can certainly generate your own as explained here: https://github.com/grahamgilbert/imagr#password
The various URLs point to the pkgs I copied into the testing folder in my Munki repo share. Adjust as needed.
I saved this plist in the same folder as the testing pkgs as “testing.plist”. (Boring, I know.)
Make sure you can open it in a web browser before you continue — in my case it’s available
We are now done with the server config.
Boot a test client into the DeployStudio NBI that was configured as in my earlier post.
Open the Terminal.app.
We need to tell Imagr how to find the configuration plist, so:
defaults write com.grahamgilbert.Imagr serverurl http://munki/repo/testing/testing.plist
Make sure you replace the URL with the actual URL to the config plist you created.
Now launch Imagr:
And bask in your success (or grumble at your failure…)
The prolific Graham Gilbert is working on a new tool: https://github.com/grahamgilbert/imagr
Imagr is an application designed to be run from a NetInstall environment. It is able to restore a disk image and install packages on a target volume.
Though Graham claims it is not intended to be a replacement for DeployStudio, I think in time it could very well be exactly that, at least for many people/organizations.
Some exciting things about Imagr:
- It is open source! DeployStudio is free, but the source is closed. Open source means you can look at the code and see what it is doing. You can fix bugs and perhaps even help add features to the product.
- It’s written in Cocoa-Python, with much of the “interesting” tasks in Python — a language many OS X admins are familiar with.
- And most importantly: it does not require a specialized server: it can work with any plain-old web server. This means that you (potentially) can eliminate the last OS X device in your server room/data center. Almost every service of interest to OS X admins can be run on platforms other than OS X with the huge exception of a DeployStudio server. If Imagr can meet your imaging/machine build needs, you can finally get rid of that poor Mac mini sitting on a shelf in the server room.
Graham has posted detailed instructions on how to build a NetBoot image that contains Imagr. But if you just want to take a look and play with the tool, and you have an existing DeployStudio NBI with Python support included, you can play with Imagr without needing to build a new NBI. More importantly, you can test new versions (or work on the code yourself and test new versions you build) without having to build a new NBI each time.