Hi guys… I know that this is not exactly the right forum… but I need
some information on the libvirt implementation in foreman, on the foreman
used in Satellite6 (1.7+)…
to me it seems like Satellite/Foreman is using the "old" api command
"virConnectOpen"… when trying to connect to a libvirt based Compute
Resource… and not the new "virConnectOpenAuth", which is needed for
authentication…
This might have been fixed in newer versions of foreman… but I just need
to figure out in which piece of code this is located… so I can change it…
Anyone able to help me out??
> Hi guys… I know that this is not exactly the right forum… but I need
> some information on the libvirt implementation in foreman, on the foreman
> used in Satellite6 (1.7+)…
> to me it seems like Satellite/Foreman is using the "old" api command
> "virConnectOpen"… when trying to connect to a libvirt based Compute
> Resource… and not the new "virConnectOpenAuth", which is needed for
> authentication…
> This might have been fixed in newer versions of foreman… but I just need
> to figure out in which piece of code this is located… so I can change it…
>
the current upstream (in fog) [1] that uses the ruby binding uses
Libvirt::open_auth
which is using virConnectOpenAuth - see [2].
the same method is also used in older versions of fog/foreman/satellite
(e.g. see [3])
···
On Wed, Nov 25, 2015 at 2:49 PM, Martin Juhl wrote:
>
> Regards
> Martin
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>