Bug 1370460

Copied from description section:

1. Proposed title of this feature request  
    Add 'host collection name' as a search parameter while creating filter with resource type = content host 

When creating a subnet via the hammer CLI, following options need to be exposed.
 Discovery Capsule
 Remote Execution
  
 
3. What is the nature and description of the request?  
   Currently while crating subnet there is no option for discovery capsule and remote execution 

   Customer would like to see these added.


4 How would the customer like to achieve this? (List the functional requirements here)  
    Customer would like to create subnet via hammer using the Discovery Capsule &  Remote Execution feature

  
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
    1 Goto Satellite terminal
    2 use hammer command to create subnet
    3 hammer subnet create --name="Subnet1" --remote-execution=""

  
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
    NO
  
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
    No
  
9. Is the sales team involved in this request and do they have any additional input?  
    No

10. List any affected packages or components.  
    Hammmer
  

11. Would the customer be able to assist in testing this functionality if implemented?  
    Yes

Created redmine issue http://projects.theforeman.org/issues/21231 from this bug

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

It is important to be able to set remote execution capsule via hammer as it is possible via UI. This is important in a workflow when you want to use ReX via capsules properly IMO.

As a workaround, you can use API to setup ReX capsule for subnet:

# curl --silent --insecure -u ...:... -X PUT -H 'Accept: application/json' -H 'Content-Type: application/json' https://localhost//api/v2/subnets/subnet-caps1 -d '{"subnet": {"remote_execution_proxy_ids": ["2"]}}'

Unfortunately, it is not shown when getting that subnet back:

# curl --silent --insecure -u ...:... -X GET -H 'Accept: application/json' https://localhost//api/v2/subnets/subnet-caps1 | json_reformat | grep -i -e rex -e remote
<nothing>

(In reply to Jan Hutař from comment #10)
> It is important to be able to set remote execution capsule via hammer as it
> is possible via UI. This is important in a workflow when you want to use ReX
> via capsules properly IMO.


Hello, it's been some time since the last comment on this RFE,
is it still needed?

(In reply to Ron Lavi from comment #16)
> Hello, it's been some time since the last comment on this RFE,
> is it still needed?

Hello. I think there is a generic promise that whatever can be done in UI, should be doable in CLI. I have not checked if this is still missing though. When needed, I'm using API workaround from comment #c11

Thanks Jan, I see that upstream issue already created: https://projects.theforeman.org/issues/21231
added to my team's backlog: https://issues.redhat.com/browse/SAT-11210