Tim Serong

This is really excellent work, but it is, effectively, an entirely new letter. IMO a large part of the charm of the original is that is *is* a short, emotive,...

I saw the ssh problem when doing a reinstall of a swift-proxy node. swift-proxy was executing before swift-compute, so failed (ring files didn't exist yet), which meant the provisioner never...

Also on SLE15.

The warnings go away once you've made it past stage.2. `/srv/pillar/ceph/stack/stack.cfg` has various references to `{{ pillar.get('cluster') }}`, which won't be set initially.

Or, possibly not. The warnings disappeared for a couple of runs, then came back again (although with two less lines)...? ```` # salt-run state.orch ceph.stage.3 [WARNING ] Ignoring pillar stack...

...and then I ran stage 3 again, and the warnings had disappeared...

I honestly have no idea how I originally ended up with the mines out of date when running stage 3, but you might try `salt '*' mine.delete 'cephdisks.list'`, or even...

I've got most of an initial baseline engulf test in https://github.com/SUSE/DeepSea/pull/1387. It'll engulf the current cluster and make sure it's the same as what was originally deployed. I know that's...

No, it just pulls in the config file as-is, it doesn't rewrite that.

Also note that the import saves ceph.conf to /srv/salt/ceph/configuration/files/ceph.conf.import, and sets `configuration_init: default-import`, which makes DeepSea use the imported configuration file, rather than using DeepSea's default /srv/salt/ceph/configuration/files/ceph.conf.j2 template.