Katello/Foreman/Pulp Integration Roadmap

Support
#1

Hi,

I'm seeking some clarification on how Foreman/Katello will integrate with
existing Foreman/Pulp environments. I'm unable to find any documentation.

We are already a Foreman 1.5/Pulp shop. We have dedicated Pulp servers
serving content in each of our datacenters. As I understand it, Katello
will include it's own bundled pulp-server which will be installed alongside
Foreman/Katello on the same host. This is not ideal in our environment
since we already have Pulp servers deployed. We have no desire to run both
Foreman/Katello and pulp-server on the same hosts. Will Katello allow us
to specify existing Pulp servers and be able to control them? I would
think this would be possible since the integration between Katello and Pulp
is likely through an API (pulp) anyways.

We currently align Puppet environments (ie, dev, qa, prod) with Pulp repos.
For instance, hosts in the "dev" environment get assigned a repository
named "rhel6-server-dev-x86_64" and so on. Yum definitions are dropped
onto each host by Puppet and the appropriate repos are assigned based on
the host's environment. I believe this is a bit different then the Katello
content-views based approach.

At the end of the day, I'm looking to see how I can make Katello fit into
our environment without having to re-engineer everything from the ground
up. Any advice or comments on this subject would be much appreciated.

Thanks,

Josh

#2

Howdy,

I'll split this up into Foreman and Pulp information.

For Foreman, we do not support nor have we tested attempting to deploy
Katello on top of an existing Foreman. Our first priority has been to get
Katello converted to an engine and fully functional at a deployment level.
There are some model connections and additional properties Katello adds
along with the structure of the deployment with respect to certs that make
this more difficult than other plugins. That being said, we have not had
any capacity to investigate if this would be possible and how we might do
it to date.

For Pulp, Katello stores data in Pulp in a way that represents how the data
is segmented into organizations and products within the Katello data model.
Further, we've not investigated a way to directly import the current data
in an existing Pulp. However, if you have an existing Pulp, you can treat
it as an external repository source to feed into your Katello. While remote
Pulp's should work, we have not had capacity to test the usage of an
existing or remote Pulp (outside of Pulp nodes). This may be possible if
the certs and server.conf are configured properly, and then at least while
you would need to import the repos into Katello, the packages would already
be on disk.

I hope this helps give some insight into the current landscape. We'd more
than welcome working with anyone that wants to try the above and appreciate
hearing how users would like to use the tools. Further, if you
have ideas on how we might take this we are more than happy to entertain.

If I've missed answering any specific questions let us know and we'll send
along further information.

Thanks,
Eric
Hi,

I'm seeking some clarification on how Foreman/Katello will integrate with
existing Foreman/Pulp environments. I'm unable to find any documentation.

We are already a Foreman 1.5/Pulp shop. We have dedicated Pulp servers
serving content in each of our datacenters. As I understand it, Katello
will include it's own bundled pulp-server which will be installed alongside
Foreman/Katello on the same host. This is not ideal in our environment
since we already have Pulp servers deployed. We have no desire to run both
Foreman/Katello and pulp-server on the same hosts. Will Katello allow us
to specify existing Pulp servers and be able to control them? I would
think this would be possible since the integration between Katello and Pulp
is likely through an API (pulp) anyways.

We currently align Puppet environments (ie, dev, qa, prod) with Pulp repos.
For instance, hosts in the "dev" environment get assigned a repository
named "rhel6-server-dev-x86_64" and so on. Yum definitions are dropped
onto each host by Puppet and the appropriate repos are assigned based on
the host's environment. I believe this is a bit different then the Katello
content-views based approach.

At the end of the day, I'm looking to see how I can make Katello fit into
our environment without having to re-engineer everything from the ground
up. Any advice or comments on this subject would be much appreciated.

Thanks,

Josh

··· -- 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.
#3

Hello all,

I am trying to register client with Fedora 20 OS but I am getting the
following error:

subscription-manager register --org="Name"
Username: XXXX
Password:
Network error, unable to connect to server. Please see
/var/log/rhsm/rhsm.log for

Errors:
return self.conn.request_post(url, params)
File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 557,
in request_post
return self._request("POST", method, params)
File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 457,
in _request
conn.request(request_type, handler, body=body, headers=headers)
File "/usr/lib64/python2.7/httplib.py", line 973, in request
self._send_request(method, url, body, headers)
File "/usr/lib64/python2.7/httplib.py", line 1007, in _send_request
self.endheaders(body)
File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 200,
in endheaders
httpslib.HTTPSConnection.endheaders(self, body)
File "/usr/lib64/python2.7/httplib.py", line 969, in endheaders
self._send_output(message_body)
File "/usr/lib64/python2.7/httplib.py", line 829, in _send_output
self.send(msg)
File "/usr/lib64/python2.7/httplib.py", line 791, in send
self.connect()
File "/usr/lib64/python2.7/site-packages/M2Crypto/httpslib.py", line 206,
in connect
raise socket.error, "Proxy connection failed: %d" % code
error: Proxy connection failed: 503

Is there python version problem? Any feedback helps

Thanks,

#4

Hi Eric,

Thanks for the reply. So, at this point, there is no way for me to install
the Katello engine on top of my existing Foreman installation.
Additionally, the only way to support external Pulp instances at this
point is to simply feed them into new repos on the Katello installation.

I think there should eventually be a way for existing Foreman users to
integrate the Katello engine without starting over from scratch. This is a
blocker for us. I also feel that there should be support for external Pulp
repos/servers since large enterprises often need to distribute their
software repositories across multiple locations and servers for scalability
and HA reasons (and don't want to deploy an entire Katello stack just to
serve content at every location).

I'm more than happy to test/help in anyway possible.

Thanks,

Josh

··· On Fri, May 23, 2014 at 12:27 PM, Eric D Helms wrote:

Howdy,

I’ll split this up into Foreman and Pulp information.

For Foreman, we do not support nor have we tested attempting to deploy
Katello on top of an existing Foreman. Our first priority has been to get
Katello converted to an engine and fully functional at a deployment level.
There are some model connections and additional properties Katello adds
along with the structure of the deployment with respect to certs that make
this more difficult than other plugins. That being said, we have not had
any capacity to investigate if this would be possible and how we might do
it to date.

For Pulp, Katello stores data in Pulp in a way that represents how the
data is segmented into organizations and products within the Katello data
model. Further, we’ve not investigated a way to directly import the current
data in an existing Pulp. However, if you have an existing Pulp, you can
treat it as an external repository source to feed into your Katello. While
remote Pulp’s should work, we have not had capacity to test the usage of an
existing or remote Pulp (outside of Pulp nodes). This may be possible if
the certs and server.conf are configured properly, and then at least while
you would need to import the repos into Katello, the packages would already
be on disk.

I hope this helps give some insight into the current landscape. We’d more
than welcome working with anyone that wants to try the above and appreciate
hearing how users would like to use the tools. Further, if you
have ideas on how we might take this we are more than happy to entertain.

If I’ve missed answering any specific questions let us know and we’ll send
along further information.

Thanks,
Eric
Hi,

I’m seeking some clarification on how Foreman/Katello will integrate with
existing Foreman/Pulp environments. I’m unable to find any documentation.

We are already a Foreman 1.5/Pulp shop. We have dedicated Pulp servers
serving content in each of our datacenters. As I understand it, Katello
will include it’s own bundled pulp-server which will be installed alongside
Foreman/Katello on the same host. This is not ideal in our environment
since we already have Pulp servers deployed. We have no desire to run both
Foreman/Katello and pulp-server on the same hosts. Will Katello allow us
to specify existing Pulp servers and be able to control them? I would
think this would be possible since the integration between Katello and Pulp
is likely through an API (pulp) anyways.

We currently align Puppet environments (ie, dev, qa, prod) with Pulp
repos. For instance, hosts in the “dev” environment get assigned a
repository named “rhel6-server-dev-x86_64” and so on. Yum definitions are
dropped onto each host by Puppet and the appropriate repos are assigned
based on the host’s environment. I believe this is a bit different then
the Katello content-views based approach.

At the end of the day, I’m looking to see how I can make Katello fit into
our environment without having to re-engineer everything from the ground
up. Any advice or comments on this subject would be much appreciated.

Thanks,

Josh

–
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.