[Announcement]: New feature: Smart Proxy visibility on Foreman

Support
1

Hey all,
TL;DR - we are creating a new feature: "Smart Proxy visibility" which will
display important data from the proxy.

Preface: Up until now, we have no visibility on what is going on in our
proxies. We'd like to change that and display more information and data
from the proxy(ies)

A while ago, Ohad has posted wireframes to this feature [1
<https://dl.dropboxusercontent.com/u/5892944/Capsule-2015-11-02.pdf>] and
we will be basing this feature on those wireframes.

So, we came up with a few user stories we'd like to share with you and hear
your comments on
As you may notice, some of the data already exists in the Foreman - we will
aggregate it into the Proxy's context. Other data, will be created by this
feature.
One of the goals of this feature is to become pluggleable to other proxy
plugins, so the can send their own data (for instance, in the openscap
plugin - send when was the last successful / failed report)
Here are some of the user stories we will start with (would love to hear
your comments):

Proxy status:

  • As a user I would like to know if the proxy is up and running
  • As a user I would like to know if the Proxy's available plugins are up
    and running and if they are not running why they did not load

Overall plugability:

  • As a foreman developer I would like to add tabs / extensions to the
    proxy page (there's already some work started in host aspects PR, we need
    to check it and possibly reuse)
  • As a foreman developer I'd like to have way of extending the data
    returned from smart proxy api
  • As a User I would like to update proxy index page with proxy status

Overall Proxy

  • As a user I would like to consume the additional information via the
    API.
  • As a user I would like to consume the additional information via
    hammer.

DNS

  • As a user I would like to see what domains are managed by this proxy

Puppet

  • As a User I would like to know when was the last time puppet master
    reported
  • As a User I would like to know how many puppet classes are on the
    puppet-proxy

Content (Katello)

··· - - As a user I would like to know the current sync status (progress bar etc) - As a User I would like to know the amount of packages that are on the proxy - As a User I would like to see the used / avail disk space for content - As a user I would like to see how many lifecycle environments are distributed on the proxy - As a User I would like to know the puppet environments deployed on the proxy. (or maybe the number of classess etc). - As a User I would like to cancel running sync on a proxy

We’d love to hear comments, insights and what is important to you in the
proxy visibility.

Thanks!

[1] https://dl.dropboxusercontent.com/u/5892944/Capsule-2015-11-02.pdf

2

Cool stuff! Some comments though:

  1. I've seen that PDF before :stuck_out_tongue: - IIRC we said then that as wireframes
    go, it's very downstream specific. Can we do some wireframes for
    upstream (core) usage? It'd be nice to see some examples of these
    stories.

  2. Following on from (1), if the wireframes are redone for core, then
    it follows that this work must be extendable by plugins so Katello can
    add to it. Are you planning to use Facets for this, or some other
    method?

  3. Some DHCP/TFTP stories would be nice, just to round out the feature
    set. How about:

  • stories based on the dhcp_browser plugin, such as seeing a list of
    current leases, zones, pools, ip allocation percentage, status of the
    dhcp service, etc
  • status of tftp - not sure what we need here? local changes to the
    pxelinux.cfg/default file shown? disk space in $TFTPROOT?
3

> Cool stuff! Some comments though:
>
> 1) I've seen that PDF before :stuck_out_tongue: - IIRC we said then that as wireframes
> go, it's very downstream specific. Can we do some wireframes for
> upstream (core) usage? It'd be nice to see some examples of these
> stories.
>
> 2) Following on from (1), if the wireframes are redone for core, then
> it follows that this work must be extendable by plugins so Katello can
> add to it. Are you planning to use Facets for this, or some other
> method?
>
> 3) Some DHCP/TFTP stories would be nice, just to round out the feature
> set. How about:
>
> * stories based on the dhcp_browser plugin, such as seeing a list of
> current leases, zones, pools, ip allocation percentage, status of the
> dhcp service, etc
> * status of tftp - not sure what we need here? local changes to the
> pxelinux.cfg/default file shown? disk space in $TFTPROOT?

For TFTP, it'd be really handy to see a list of hosts with PXE entries
in pxelinux.cfg, and maybe the ability to preview the file itself. It'd
save an SSH session.

··· On Mon, Dec 07, 2015 at 01:44:16PM +0000, Greg Sutcliffe wrote:

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

4

The only thing I can add to this, if the Puppet proxy is going to show when
the last successful run happened can that somehow be exposed to the API.
My monitoring folks have been after me for a while to figure out a way of
divining that piece of info.

··· On Mon, Dec 7, 2015 at 9:17 AM Stephen Benjamin wrote:

On Mon, Dec 07, 2015 at 01:44:16PM +0000, Greg Sutcliffe wrote:

Cool stuff! Some comments though:

  1. I’ve seen that PDF before :stuck_out_tongue: - IIRC we said then that as wireframes
    go, it’s very downstream specific. Can we do some wireframes for
    upstream (core) usage? It’d be nice to see some examples of these
    stories.

  2. Following on from (1), if the wireframes are redone for core, then
    it follows that this work must be extendable by plugins so Katello can
    add to it. Are you planning to use Facets for this, or some other
    method?

  3. Some DHCP/TFTP stories would be nice, just to round out the feature
    set. How about:

  • stories based on the dhcp_browser plugin, such as seeing a list of
    current leases, zones, pools, ip allocation percentage, status of the
    dhcp service, etc
  • status of tftp - not sure what we need here? local changes to the
    pxelinux.cfg/default file shown? disk space in $TFTPROOT?

For TFTP, it’d be really handy to see a list of hosts with PXE entries
in pxelinux.cfg, and maybe the ability to preview the file itself. It’d
save an SSH session.

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

5

> From: "Peter Berghold" <salty.cowdawg@gmail.com>
> To: foreman-users@googlegroups.com
> Sent: Monday, December 7, 2015 9:44:43 AM
> Subject: Re: [foreman-users] [Announcement]: New feature: Smart Proxy visibility on Foreman
>
> The only thing I can add to this, if the Puppet proxy is going to show when
> the last successful run happened can that somehow be exposed to the API.
> My monitoring folks have been after me for a while to figure out a way of
> divining that piece of info.

This should be possible already in the host's api. GET /api/v2/hosts/:id

'last_report' will have the last time Foreman received a report,
and 'puppet_status' will tell you the status of the run.

'global_status_label' in 1.10 has a descriptive status that might be interesting too.

··· ----- Original Message -----

On Mon, Dec 7, 2015 at 9:17 AM Stephen Benjamin stephen@redhat.com wrote:

On Mon, Dec 07, 2015 at 01:44:16PM +0000, Greg Sutcliffe wrote:

Cool stuff! Some comments though:

  1. I’ve seen that PDF before :stuck_out_tongue: - IIRC we said then that as wireframes
    go, it’s very downstream specific. Can we do some wireframes for
    upstream (core) usage? It’d be nice to see some examples of these
    stories.

  2. Following on from (1), if the wireframes are redone for core, then
    it follows that this work must be extendable by plugins so Katello can
    add to it. Are you planning to use Facets for this, or some other
    method?

  3. Some DHCP/TFTP stories would be nice, just to round out the feature
    set. How about:

  • stories based on the dhcp_browser plugin, such as seeing a list of
    current leases, zones, pools, ip allocation percentage, status of the
    dhcp service, etc
  • status of tftp - not sure what we need here? local changes to the
    pxelinux.cfg/default file shown? disk space in $TFTPROOT?

For TFTP, it’d be really handy to see a list of hosts with PXE entries
in pxelinux.cfg, and maybe the ability to preview the file itself. It’d
save an SSH session.

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.