[Spacewalk-list] ISS: Slave cannot see shared channels

sam at eventbase.net sam at eventbase.net
Sun Oct 20 10:13:46 UTC 2013


Hello all

I have been playing with ISS for a few hours now in an attempt to 
replace some (broken) custom scripting currently going on in our 
organisation.

However, I have hit a snag, and the mighty Google couldn't help me 
either. It currently seems that, what I'd like to achieve, is currently 
not possible. Though I'd like to be told otherwise.

My desired way of using ISS:

On my Spacewalk master, I have two channels in the "Default" org:
  - ProductA
  - ProductB

I then create three separate orgs. OrgA is only allowed to access 
ProductA, OrgB is only allowed to access ProductB. OrgC can see both 
products. To achieve this, I mark each of the product channels as 
*protected* and expose them only to the Orgs (customers) which are 
allowed to see them.

Each customer then has his own Spacewalk server to further distribute 
software within their company. Our current solution to bring packages 
from our main (master) Spacewalk server to their server involves a 
custom script and a username/password pair.
The script at the customer's site uses the username/password, tied to 
their Org, to make XML-RPC requests against our spacewalk to 
"listAllChannels", then "listLatestPackages", download them, and import 
them into their Spacewalk server. It "mirrors" the channels (lists the 
ones on our master, creates one with the same name).
This has historically been the cause of a number of issues.

Hence I am looking at ISS as this seems to have been designed to do 
exactly what I need. However, the issue I am having is that, a Slave can 
only see channels fully owned by the org I expose to them.

Even though OrgA has got access to channel ProductA in org Default, if I 
allow the slave at customer A access to OrgA, it cannot see the ProductA 
channel.

If, on my master, I log in as the org admin for OrgA and create a new 
channel, the slave can see it.

On my test setup I am running spacewalk 2.0 on CentOS 6.4 at both ends.

Should this be working? Am I missing a piece? Or are ISS slaves really 
not able to see shared channels?

Any help is greatly appreciated.

Regards

Samuel




More information about the Spacewalk-list mailing list