Make authorize-user part of bastion deployment
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	epriestley
	May 15 2015, 1:47 AM

Revisions and Commits

	Restricted Diffusion Commit
	Restricted Diffusion Commit

		Status	Assigned	Task
		Resolved	epriestley	T8210 Phacility Cluster: Bastion host stopped responding
		Resolved	epriestley	T8206 Make authorize-user part of bastion deployment

epriestley raised the priority of this task from to Normal.

epriestley updated the task description. (Show Details)

epriestley moved this task to Do After Launch on the Phacility board.

epriestley added a subscriber: epriestley.

epriestley added a commit: Restricted Diffusion Commit.May 15 2015, 3:21 PM

epriestley added a commit: Restricted Diffusion Commit.May 15 2015, 4:56 PM

Deploying a bastion host now synchronizes account, key and sudoer state automatically.

The bin/remote authorize command is now obsolete.

I've updated the documentation.

(As a bonus, it looks like I fixed that prompting for new config file stuff, too.)

I also realigned the use of DNS. We now use:

This is more flexible and consistent than the old approach, and has a 90% shorter TTL.