id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc
138	autoinstallers shouldn't fail if primary is down	geofft		"For a couple of reasons including being able to get to the server where your cronjob runs, ssh scripts always reaches a single machine (the ""primary""), which is also where user-run services on high ports run. However, none of the autoinstallers that ssh to scripts particularly care about getting to this single server; they're just setting up a webapp that you're going to be accessing via the load-balanced HTTP protocol anyway. This causes an unneeded single point of failure in the autoinstall process. Same with the signup process -- any server can add you and your vhost to LDAP. The intent of multimaster replication is, again, to avoid a single point of failure.

It would be cool if by some mechanism the autoinstallers were robust to the primary failing and not accepting SSH connections, and they could simply log in to any running scripts server to complete the install. The most obvious solution that occurs to me is to add another SSH port that's in the same load-balancing pool as HTTP(S), but you could also do evil things with client-side overcleverness, etc."	enhancement	new	normal		autoinstallers