MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"continue": {
"lecontinue": "20250417151132|291",
"continue": "-||"
},
"query": {
"logevents": [
{
"logid": 301,
"ns": 0,
"title": "In transit data security",
"pageid": 362,
"logpage": 362,
"params": {},
"type": "create",
"action": "create",
"user": "Adj",
"timestamp": "2026-01-18T04:14:18Z",
"comment": "Created page with \"All of the Fnordly web properties (this wiki, webmail, OpenStack API endpoints, etc) are hosted behind HAproxy daemon(s) running on the Internet facing firewall machines. While it would be nice to say that things are all covered by HAproxy doing TLS termination for us, defense in depth principles demand that '''all''' traffic that can be encrypted '''be''' encrypted. As such, traffic between the HAproxy endpoints and the internal web services is encrypted to, and web s...\""
},
{
"logid": 300,
"ns": 0,
"title": "IPv6 connectivity",
"pageid": 361,
"logpage": 361,
"params": {},
"type": "create",
"action": "create",
"user": "Adj",
"timestamp": "2025-12-22T19:22:32Z",
"comment": "Created page with \"At this writing, the home network infrastructure has 2 ISP connections. One from Comcast/Xfinity, the other from Allo Communications. Comcast supplies IPv4 and IPv6. Allo only provides IPv4, and if it does have plans to provide IPv6, they have not been well communicated. Plans are in progress to shut down the Comcast service, meaning no more native IPv6 for the home network. == Comcast/Xfinity == === Directly connected system (router/firewall) interface config === F...\""
},
{
"logid": 299,
"ns": 0,
"title": "Notes on VM building",
"pageid": 360,
"logpage": 360,
"params": {},
"type": "create",
"action": "create",
"user": "Adj",
"timestamp": "2025-07-26T18:11:40Z",
"comment": "Created page with \"What is says in the title. Here's what I run to start a Debian install with a virtio storage and network enabled UEFI virtual machine: sudo qemu-img create -f qcow2 /srv/vm-backing-store/padmeamadeus-0-vda.qcow2 64G sudo virt-install --name padmeamadeus-0 --memory 5120 --vcpus 2 --cpu host --cdrom ~/Downloads/debian-testing-amd64-20250726-netinst.iso --boot uefi --osinfo debian11 --disk /srv/vm-backing-store/padmeamadeus-0-vda.qcow2,bus=virtio --network bridge=br0,mod...\""
},
{
"logid": 298,
"ns": 0,
"title": "Ceph performance metrics",
"pageid": 359,
"logpage": 359,
"params": {},
"type": "create",
"action": "create",
"user": "Adj",
"timestamp": "2025-07-24T14:25:07Z",
"comment": "Created page with \"This has come up because the Sentinel 1 endpoint detection and response (EDR) agent is being installed across all our servers. In order to minimize potential customer impact we will: * Divide servers into three groups based on client IO sensitivity. Purely development environments being low sensitivity, and certain database workload being highly sensitive. S3 workloads will probably fall in the middle. * In each group, before S1 agent is installed and running, gather...\""
},
{
"logid": 297,
"ns": 0,
"title": "Rotating applications' Ceph S3 credentials",
"pageid": 358,
"logpage": 358,
"params": {},
"type": "create",
"action": "create",
"user": "Adj",
"timestamp": "2025-07-23T22:07:46Z",
"comment": "Created page with \"At $DAYJOB, some concern has been expressed that S3 client applications have no credential rotation. Which is probably fair. Here are some thoughts on the subject: * S3 bucket and object access is assigned to an abstraction called a \"user.\" * Users identify themselves to the storage not by presenting their name, but my means of an \"access key\" and \"secret key.\" The secret key is not sent across the wire to the S3 server. Instead it is used to sign any given request....\""
},
{
"logid": 296,
"ns": 0,
"title": "Backup and Recovery",
"pageid": 357,
"logpage": 357,
"params": {},
"type": "create",
"action": "create",
"user": "Adj",
"timestamp": "2025-06-01T15:01:45Z",
"comment": "Created page with \"== General thoughts == Accepted wisdom: * Three copies of your data * Two different media * One copy off site == Current state of affairs == (Early June 2025) There are 30+...\""
},
{
"logid": 295,
"ns": 0,
"title": "Hardware inventory",
"pageid": 356,
"logpage": 356,
"params": {},
"type": "create",
"action": "create",
"user": "Adj",
"timestamp": "2025-05-28T23:35:09Z",
"comment": "Created page with \"This is, at creation time, mostly for storage devices. There are ''many'' hard drives in the data center. And it might be nice to track them by serial number. Maybe... {|...\""
},
{
"logid": 294,
"ns": 0,
"title": "Powervault MD3060e",
"pageid": 355,
"logpage": 355,
"params": {},
"type": "create",
"action": "create",
"user": "Adj",
"timestamp": "2025-05-22T13:27:21Z",
"comment": "Created page with \"4U tall. And space for 60 3.5inch (or 2.5inch) drives inside. == Attaching to the network == Each of the two rear mounted \"enclousure management modules\" (\"EMMs\") has a seri...\""
},
{
"logid": 293,
"ns": 0,
"title": "Supermicro servers",
"pageid": 354,
"logpage": 354,
"params": {},
"type": "create",
"action": "create",
"user": "Adj",
"timestamp": "2025-05-19T15:50:25Z",
"comment": "Created page with \"== BMC notes == === Credentials === Can be set using <code>ipmitool user list</code> (to get the user's number) followed by <code>ipmitool user set password USERNUM passwordst...\""
},
{
"logid": 292,
"ns": 0,
"title": "Work in progress sofree.us 2025Q3 Ceph handson",
"pageid": 353,
"logpage": 353,
"params": {},
"type": "create",
"action": "create",
"user": "Adj",
"timestamp": "2025-05-12T20:37:38Z",
"comment": "Created page with \"== Timeframe == Per the title, Q3 of 2025. Some Saturday. Probably August or September. == Goals == Learners will install/configure a working Ceph cluster and gain some kn...\""
}
]
}
}