Good Day folks!
A few observations from testing Capsule isolation in 2.2 RC1.
- Capsule (isolated) instructions specify capsule-installer option
–qpid-router=true which is not a valid option in the current version of
capsule-installer.
(http://www.katello.org/docs/2.2/user_guide/capsules/index.html)
- qpid-dispatch-router is not installed by capsule-installer. It's
missing that dependency and it's associated configuration.
- capsule-certs-generate does not give correct configuration information
for an isolated capsule. Specifically, the "–reverse-proxy=true" switch.
- In Foreman, clicking on Smart-proxy -> Refresh features of a capsule
which should be isolated indicates it's trying to access the proxy on port
9090, which the isolated capsule documentation does not indicate it is
necessary. According to the capsule proxy documentation, it should be
accessing the capsule via 8443. Is 9090 still a requirement for an
isolated capsule?
(http://www.katello.org/docs/2.2/user_guide/capsules/index.html)
- It doesn't seem to transfer content from the Katello server to the
isolated capsule. May relate to the earlier notes. Still testing.
I'll try to re-test with RC2 or RC3.
Keep up the great work folks!
/Mike
> Good Day folks!
>
> A few observations from testing Capsule isolation in 2.2 RC1.
Hey,
Thanks for trying this out.
>
>
> - Capsule (isolated) instructions specify capsule-installer option
> --qpid-router=true which is not a valid option in the current version of
> capsule-installer.
> (http://www.katello.org/docs/2.2/user_guide/capsules/index.html)
> - qpid-dispatch-router is not installed by capsule-installer. It's
> missing that dependency and it's associated configuration.
For whatever reason it looks like the installer changes for this didn't
make the RC. It should make the next release of 2.2.
>
> - capsule-certs-generate does not give correct configuration information
> for an isolated capsule. Specifically, the "–reverse-proxy=true" switch.
> - In Foreman, clicking on Smart-proxy -> Refresh features of a capsule
> which should be isolated indicates it's trying to access the proxy on port
> 9090, which the isolated capsule documentation does not indicate it is
> necessary. According to the capsule proxy documentation, it should be
> accessing the capsule via 8443. Is 9090 still a requirement for an
> isolated capsule?
We use 8443 for RHSM, so the Capsule actually runs on 9090 instead of
the foreman default. I'll update the image, thanks.
> (http://www.katello.org/docs/2.2/user_guide/capsules/index.html)
> - It doesn't seem to transfer content from the Katello server to the
> isolated capsule. May relate to the earlier notes. Still testing.
Yea, without dispatch router, syncing a remote capsule from the Katello
won't work at all. Katello agent relies on connecting to it.
···
On Sat, Apr 04, 2015 at 01:05:56PM -0700, mkbrown@solutionsathand.ca wrote:
I’ll try to re-test with RC2 or RC3.
Keep up the great work folks!
/Mike
–
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