Project

General

Profile

Actions

Feature #10799

open

Host locking

Added by Blaine Gardner almost 9 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

We have a number of simultaneous users of Foreman in our organization, many of whom use scripts to set up Foreman hosts via REST API. We would like to see the ability to 'lock' hosts for some period of time to ensure that users and scripts cannot interfere with each other's hosts.

We currently use machine owner as a best practice sort of lock, but this assumes that everyone follows the rules, which is not always the case. The ability to request a machine to be locked for some period of time (e.g. 15 minutes, 60 minutes, or forever) to a specific user would prevent accidental mis-management.


Related issues 2 (1 open1 closed)

Related to Foreman - Feature #13967: as a user, I would like to lock a host from reprovisioningNew03/01/2016Actions
Has duplicate Foreman - Feature #19343: Add concept of "system locking"Duplicate04/21/2017Actions
Actions #1

Updated by Dominic Cleal about 8 years ago

  • Related to Feature #13967: as a user, I would like to lock a host from reprovisioning added
Actions #2

Updated by Tom Caspy about 8 years ago

  • Assignee set to Tom Caspy
Actions #3

Updated by Dominic Cleal almost 7 years ago

Actions #4

Updated by Bryan Kearney almost 7 years ago

  • Bugzilla link set to 1319800
Actions #5

Updated by Ohad Levy over 6 years ago

  • Assignee deleted (Tom Caspy)
Actions

Also available in: Atom PDF