Groups
Groups
Sign in
Groups
Groups
Certificate Transparency Policy
Conversations
About
Send feedback
Help
Halloumi2025h2 and Gouda2025h2
35 views
Skip to first unread message
Pim van Pelt
unread,
Jan 7, 2026, 5:49:03 PM (3 days ago)
Jan 7
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Ct Policy, Ct Ops
Hoi folks,
The write window for these two logs has closed on 2026-01-01 and here's
our plan for these two production logs:
1. I am making a photocopy of them today, Gouda is a Sunlight log and
Halloumi is a TesseraCT log.
2. On Weds 14th, I will:
a) remove the write path for these (down the TesseraCT job, reload the
Sunlight job, removing the logshard entries from their YAML file)
b) Remove upstream *.
log.ct.ipng.ch
nginx entry for the write path.
c) Publish the ZIP files to our S3 cluster and index them.
d) Update
ct.ipng.ch
page and publish
https://ct.ipng.ch/archive/halloumi2025h2/
and
https://ct.ipng.ch/archive/gouda2025h2/
e) Send PR for
https://github.com/geomys/ct-archive/README.md
3. On Weds January 21st, I will:
a) Remove upstream *.
mon.ct.ipng.ch
read path nginx entry
b) Remove DNS entries for the log shards (
halloumi2025h2.mon.ct.ipng.ch
and
halloumi2025h2.log.ct.ipng.ch
4. On Weds January 28th, I will remove the ZFS dataset (zfs destroy
ssd-vol0/logs/halloumi2025h2)
Since this is the first time we're transitioning a completed logshard, I
welcome any feedback or tweaks to our proposed plan.
groet,
Pim (obo IPng CT Ops)
--
Pim van Pelt <
p...@ipng.ch
>
PBVP1-RIPE
https://ipng.ch/
Reply all
Reply to author
Forward
0 new messages