Red Hat Bugzilla – Bug 1296726
Provide an overview of how to configure and use remote management
Last modified: 2016-06-16 19:42:21 EDT
In Red Hat Satellite 6.2, it is now possible to schedule tasks on client machines. This is known as remote management.
A conceptual overview of remote management and procedures that outline how to configure and then work with this functionality must be added to the documentation.
Upstream bug component is Remote Actions
Moving to POST since upstream bug http://projects.theforeman.org/issues/10760 has been closed
Moving back to the documentation component.
wrt the above, what's the Sat6 equivalent of foreman-installer? Is that a viable option for Sat6, or should we only document manual installation? I also want to double-check because I know there was talk of renaming the installer commands in satellite 6.2.
Seems like a basic question but I don't have a test env available atm to test these things.
Is the following instruction valid for Sat6.2 or do we need to configure something else?
yum-config-manager --enable rhel-6-server-optional-rpms rhel-server-rhscl-6-rpms
I already have rhscl-6 but don't know about optional. That command doesn't appear to enable the repo. It doesn't appear in yum repolist. Did I miss something? I expect if I get this sorted it will answer Comment 12
(In reply to David O'Brien from comment #14)
> Is the following instruction valid for Sat6.2 or do we need to configure
> something else?
> yum-config-manager --enable rhel-6-server-optional-rpms
> I already have rhscl-6 but don't know about optional. That command doesn't
> appear to enable the repo. It doesn't appear in yum repolist. Did I miss
> something? I expect if I get this sorted it will answer Comment 12
ok, scratch this one. Use subscription-manager
subscription-manager repos --enable rhel-6-server-optional-rpms
But, I still get stuck here:
Enable the EPEL (Extra Packages for Enterprise Linux) and the Foreman repos:
`rpm -ivh http://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm`
`yum -y install http://yum.theforeman.org/releases/1.10/el6/x86_64/foreman-release.rpm`
Is this something we should be doing on a Satellite Server or Capsule? I'm guessing no, but don't know what the equivalent is. I'm pretty sure the second bit is already taken care of, but I still don't know where to get foreman-installer, or if I even need it.
Feel free to schedule an irc session to go over a few things if that'd be easier.
Is "job" a common and accepted term, and something we want to stick
with, when referring to jobs/tasks/whatever on remote hosts?
"In order to perform the job on a host, there needs to be a Smart
Proxy available to do the job."
What exactly constitutes a "job"? Is it just a command? A group or
sequence of commands? A script? Any of the above?
I know "cronjob" is perfectly legitimate, but I don't know if this is
the preferred term for Remote Management.
The job represents the script executed against a set of hosts. The template of the script is called 'Job Template'. The job is how we call it in the Remote Execution. If some other term is preferred, we would need to update the code firs.
Based on feedback from various sources, staying with "Job".
Still need-info on Comment 15 and Comment 16
No objections or alternatives offered so going ahead as planned and putting this in the User Guide.
Author: David O'Brien <email@example.com>
Date: Wed Feb 3 11:57:05 2016 +1000
bz1296726 Update section on Advanced Config
Start fleshing out advanced config options for remote management, in
this case how to specify which capsule to use.
From Ivan on foreman-dev:
As with all settings in 'Admin -> Settings' section, they can be pre-configured in /etc/foreman/settings.yaml. However, since we don't expose this options to the installer, the manual changes to the file would be overriten by the next run of the installer. Therefore the 'Admin -> Settings' (or `foreman-rake config` from a console) are preferable).
Based on foreman-dev comments it seems s/Remote Management/Remote Execution/ is happening.
Need to make sure we're consistent in the doc.
Followed up outstanding need-info requests on doc/dev sync this morning and cbillett is going to give things a push.
[bz1296726 a9c8dfb] bz1296726 Describe consequences of manual updates to config.
There are a few examples at the end of this section but I can't tell if they apply to delegation in general, or only to execute_template_invocation
When I get the thing installed myself I should be able to work it out.
[bz1296726 5eda3c2] bz1296726 Add section on delegating permissions.
Cancelling need-info for now. No 6.2 builds available so will try to get a katello install done to test stuff.
Note that this is now called Remote Execution and not Remote Management.
Assigning Stephen as the QA contact.
Been trying to get rex to work with snap2 server and separate host on laptops but so far it fails. Emailed sat6 list for info. dmac is going to try when he gets a later build installed (later today?).
Eventually found some missing bits and pieces (packages not installed by installer, ssh key not copied, etc.), and sorted them out. Not sure what the status will be by GA but can make it work now.
There is a demo here:
It shows how to view the output of job in real time. The buttons are a little different in Sat6.2 (on the Hosts tab the Actions column has "Host Detail" and not "Details"). If you click Host Detail you get exactly that - details about the host - and not live output of the job.
I don't see how to make this work.
(In reply to David O'Brien from comment #40)
> There is a demo here:
> It shows how to view the output of job in real time. The buttons are a
> little different in Sat6.2 (on the Hosts tab the Actions column has "Host
> Detail" and not "Details"). If you click Host Detail you get exactly that -
> details about the host - and not live output of the job.
> I don't see how to make this work.
ok, worked it out. You need to click the name of the host that you want to inspect.
In the section Monitoring the Remote Job I added a screenshot of how the output looks. I'm not sure how valuable this is atm, and it also has IP addresses in it. Future uncertain...
"You can use the remote_execution_ssh_user parameter" is refering to Host/Hostgroup parameters, as described in http://ccs-jenkins.gsslab.brq.redhat.com:8080/job/doc-Red_Hat_Satellite-6-User_Guide-branch-bz1296726/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#sect-Red_Hat_Satellite-User_Guide-Configuring_the_Provisioning_Environment-Parametersarameter
I went over the docs and it looks good now. ACK
As for the definite list, https://bugzilla.redhat.com/show_bug.cgi?id=1323658 covers it pretty well "(bulk actions on content hosts, package install, errata install)" so it's pakage and errata actions and it's either from single content host, or from the bulk actions
This content is now live on the Customer Portal.