Where answers come from

Some pages can ask a language model questions. Set this up once; your choice is remembered in this browser for the whole site.

Model source
Use another source instead

Smallest-to-largest weight downloads. Qwen3.5 0.8B is our starting choice for page Q&A. GPU estimates are not total RAM: leave room for the browser, context and temporary buffers. Hardware changes speed and capacity; answers still need checking.

Session-only loading avoids saving model weights, uses extra RAM and downloads again after unloading. Turn it off to save downloads. Delete-data-on-exit or private browsing may impose a much smaller storage limit than the displayed estimate.

You sign in on OpenRouter; it gives this page a key for your account.

A free account does not make every model free. Choose a model with a listed :free variant; merely adding that suffix does not create one. Check free-model availability and pricing.

Chat

AI assistant, not Shawn Hartsock. It does not speak for him.

Inspect the page excerpt

Up to 4,800 characters, not the whole site. Recent conversation turns are retained within the model’s context limit.

Ask about this page, or just say hello.

Ready when you are.

Not saved or uploaded automatically. Closing keeps this conversation in this tab; changing pages starts a new one. Model replies can be wrong.

pyvmomi-tools and alarm ack & reset

Originally published .

There are going to be use cases like “Ack & Reset vCenter Alarm implementing hidden API method” these are going to be relatively common and yet reasonably outside the definition of an official API binding. To handle this I’ve created pyvmomi-tools as a project to distribute these kinds of additions to the official bindings.

We’ll record feature requests and after a number of these get implemented we’ll provide an official release that you can pull down with pip. The pyvmomi-tools project will be freer to explore techniques for working with vSphere that might not be officially supportable or might break between releases.

I will want to come up with a system of warnings to let you know when you are using an API that might not survive between vSphere releases or isn’t officially released and therefore isn’t covered by the very generous backwards compatibility guarantees that the rest of vSphere is.

But… that’s another topic…

Explore the map · Browse by topic and date