Bug #17323

Use compute resource certificate to allow SSH provisioning

Added by Daniel Lobato Garcia 7 months ago. Updated 6 months ago.

Status:Closed
Priority:Normal
Assigned To:Daniel Lobato Garcia
Category:-
Target version:Foreman - Team Daniel - iteration 6
Difficulty: Pull request:https://github.com/theforeman/foreman_azure/pull/8
Bugzilla link:
Story points-
Velocity based estimate-

Description

Problem:

SSH provisioning does not work. Only PXE provisioning is possible through smart proxies in an Azure network.
The reason is that the setSSHWaitForResponse does not come with support for using keys other than the foreman user ones.

Solution:

The certificate passed on to the Azure compute resource can be used to SSH provision these machines as soon as they get a public IP.
The vm_user attribute that's passed on to Azure via fog will be the username, and sudo is allowed in most Azure images.

Associated revisions

Revision d48167ca
Added by Daniel Lobato García 7 months ago

Fixes #17323 - Allow SSH provisioning with CR cert

Problem:

SSH provisioning does not work. Only PXE provisioning is possible
through smart proxies in an Azure network.
The reason is that the setSSHWaitForResponse does not come with support
for using keys other than the foreman user ones.

Solution:

The certificate passed on to the Azure compute resource can be used to
SSH provision these machines as soon as they get a public IP.
The vm_user attribute that's passed on to Azure via fog will be the
username, and sudo is allowed in most Azure images.

History

#1 Updated by Daniel Lobato Garcia 7 months ago

  • Status changed from New to Closed
  • Assigned To set to Daniel Lobato Garcia
  • Pull request https://github.com/theforeman/foreman_azure/pull/8 added

#2 Updated by Daniel Lobato Garcia 6 months ago

  • Target version set to Team Daniel - iteration 6

Also available in: Atom PDF