Bug 1467514 - [RFE] Add "owner" field in Activation Key that will set the owner of the provisioned host automatically
[RFE] Add "owner" field in Activation Key that will set the owner of the prov...
Status: NEW
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Activation Keys (Show other bugs)
Unspecified Unspecified
low Severity low (vote)
: Unspecified
: --
Assigned To: Eric Helms
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-07-04 02:12 EDT by monish
Modified: 2018-04-01 01:54 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description monish 2017-07-04 02:12:03 EDT
1. Proposed title of this feature request  
[RFE] Add "owner" field in Activation Key that will set the owner of the provisioned host automatically.
2. Who is the customer behind the request?  
Name	:Eero TORRI
Account Name :	European Parliament
Phone	:3222832776
Email	 :eero.torri@europarl.europa.eu

    TAM customer: no
    SRM customer: no  
    Strategic: no 
3. What is the nature and description of the request?  

Currently hosts provisioned with satellite end up owned by the User who created them unless the operator goes to the last "Host" tab to set the correct  User / User Group as the owner. 
This makes life difficult in situation where servers are provisioned for others.

The Host Collection can be set with activation key. Similar to this, it would be interesting to create Activation Keys for different Users and organizational User Groups that would be the collective owners of the servers.

Detailed Description by Customer:

Operator (who belongs to department A in the organization hierarcy) creates a new server for department B with Satellite UI.
By default, the Owner field (in the Host object of Satellite) of the server will be set to the Operator person.  Most other parameters
of the server can be automatically set by the taxonomy, Host Groups and Activation Keys.  

In this scenario the Owner should be the User Group that contains system administrators of department B. None of the automatic configuration
mechanisms (Activation Key,  Hostgroup, parameters) seem to allow doing this automatically.  

In general, having the Operator person as the Owner (instead of a group of system administrators) is almost never the right thing to do
in large organizations.  

We use User Groups as Owner to limit the view to servers (like satellite 5 systemgroups) for our client departments with special filtered Role.

Current solution:
Operator will remember that server with HostGroup like  "/standard_el7/client1_base_server" and activation key "el7_virtual_client1" needs to have
the Owner manually assigned to User Group "Client1".

4. How would the customer like to achieve this? (List the functional requirements here)  
a) We can create an Activation Key that assigns the Owner exactly like there can be an Activation Key that assigns Host Collection (Activation keys are cheap)
b) Host  Group can assign the Owner (host groups are heavy but acceptable)
c) We create an Activation Key that assigns a Host Collection with the exact same name as the User Group of our client.  A homemade script
runs now and then to re-own the servers  in case Operator has forgotten to set the right owner.

Note You need to log in before you can comment on or make changes to this bug.