Now that we have basic puppetization of LE certs, we can start planning to deploy them in some limited places in production where we have existing commercial certs on renewal cycles.
Keep in mind the following situations are off the table (for now, here):
- This isn't about the junk redirect domains, that's in T133548
- If it's not a singular, direct, public-facing HTTP[S] host, it's out for now due to puppetization limitations
- 3rd party services/hosts are out, and I'm not looking at fundraising or labs specifically in this ticket either
- Wildcard certs (LE doesn't support)
Looking at our Ops cert renewal calendar and our globalsign account (where most certs come from), and keeping the above restrictions in mind, these seem to be the applicable cases we could LE-ify, ordered by their next commercial cert expiry:
|Cert||Expiry||Switched to LE|
I just turned on our first full-auto-puppeted LE certs today (for apt/ubuntu/mirrors, which had no certs at all before), which is an nginx host. I'm going test one other from the above list which is an Apache.
We can put off mass conversion of this list for a while (they don't start expiring until 2017 anyways) until we've had some history on the first hosts and are comfortable the LE situation is stable with auto-renewals and all that. So we're probably looking at ~60+ days out from now (circa late June or beyond) before we start converting the remaining services above to LE certs.