Project

General

Profile

Actions

Feature #31341

open

Deploy the foreman_scap_client as part of registration

Added by Marek Hulán about 4 years ago. Updated over 3 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Host registration
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Similarly how we deploy REX, we should deploy scap client if the host is configured to run it

Actions #1

Updated by Marek Hulán about 4 years ago

  • Related to Feature #30440: Simple & automatic host registration WF added
Actions #2

Updated by Marek Hulán about 4 years ago

The question is, should we encourage to use ansible/puppet for this or allow doing this as part of the registration. If so, we should do the same during provisioning.

Actions #3

Updated by Tomer Brisker about 4 years ago

  • Category set to Host registration
Actions #4

Updated by Leos Stejskal over 3 years ago

  • Related to deleted (Feature #30440: Simple & automatic host registration WF)
Actions #5

Updated by Leos Stejskal over 3 years ago

  • Priority changed from Normal to Low
  • Triaged changed from No to Yes
Actions #6

Updated by Ondřej Pražák over 3 years ago

We can bootstrap puppet agent, so puppet deployed policies can be configured the usual way.

1) register host into a hg with openscap proxy, scap client puppet module and policy
2) puppet agent runs and configures things

For ansible, this is a bit tricky. It would be good to have an ability (checkbox in registration form?) to run ansible roles after host is registered. This would be beneficial not only for openscap - the assumption is that if a user registers a host into hg with ansible roles, the desire is for the roles to be applied to the host.

Actions

Also available in: Atom PDF