Thanks for your input Brian. I did stumble upon your post from 2010 before posting. It's a shame that ~3.5 years hasn't made a difference in the development. What did you end up using to tackle this?
http://www.redhat.com/archives/spacewalk-list/2010-November/msg00051.html On Wed, Mar 19, 2014 at 4:22 PM, Brian Collins <[email protected]> wrote: > We wanted to do this exact thing using Satellite. 99% of our hosts are > outside our network, behind NAT. And the answer has been a polite but > consistent, "The product can't do that, and there are no plans to make that > happen." > > > > So we use a different monitoring tool. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Justin Edmands > *Sent:* Wednesday, March 19, 2014 4:12 PM > *To:* [email protected] > *Subject:* [Spacewalk-list] Spacewalk Monitoring Scout to external/NATed > hosts > > > > Our Spacewalk environment is used to manage purely external devices. We > have them running fedora and use OSA (when it isn't blocked by the client) > to get mostly everything accomplished. I want to start using the Monitoring > Scout to give me more details about all of the systems. As it sits, not > much documentation exists in the Spacewalk world. I used RedHat Satellite > docs to get a better understanding of the tool. > > So how can I monitor the hosts out in the field? They are certainly all > NATed and work purely based on checking in. Just to clarify, monitoring > scout simply SSHs into your system on 4545 as nocpulse and executes a > command? > > I could be overlooking what OSA, or other RHN stuff, would do in this > case. > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
