manual provisioner should carry out configuration for ssh-keys-per-user, machine-updates-authkeys

Bug #1215777 reported by Andrew Wilkins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
Low
Unassigned

Bug Description

From a review comment on manual provisioner:

"If/when ssh-keys-per-user, and machine-updates-authkeys, functionality
lands, this'll make manually provisioned machines second-class citizens. I think
we should aim to minimize the observable differences between manually and
automatically provisioned machines, really."

Revision history for this message
Andrew Wilkins (axwalk) wrote :

I think there might be cause for making this optional. I imagine some people might want to provision agents on the target machine, but not necessarily modify their SSH configuration (for security reasons).

John A Meinel (jameinel)
Changed in juju-core:
importance: Undecided → Low
status: New → Confirmed
summary: - manual provisioner must carry out configuration for ssh-keys-per-user,
+ manual provisioner should carry out configuration for ssh-keys-per-user,
machine-updates-authkeys
Curtis Hovey (sinzui)
Changed in juju-core:
status: Confirmed → Triaged
Curtis Hovey (sinzui)
tags: added: manual-provider ssh
Revision history for this message
Andrew Wilkins (axwalk) wrote :

We should just use cloud-init, or at least some new command using the cloud-init Python package. This would make manual provisioning more like everything else. See comments on lp:1238934.

Curtis Hovey (sinzui)
tags: added: ssh-provider
removed: manual-provider ssh
Curtis Hovey (sinzui)
tags: added: manual-provider
removed: ssh-provider
Changed in juju-core:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.