Katello support for Debian - how likely?

Hi,

What is the likelihood of Debian packages being supported by Katello?

http://projects.theforeman.org/issues/10478

Thanks,
Jamie.

As the bug says, the main blocker is deb support in Pulp. To my knowledge,
no one is currently working on that, although I hear it's mostly done and
just needs someone with good Apt/Dpkg knowledge to check it over and give
it some good testing. This may be incorrect, I just get rumours :wink:

Once that's done, the remaining work for Katello to support deb can be
figured out.

··· On 22 February 2016 at 10:05, JC wrote:

Hi,

What is the likelihood of Debian packages being supported by Katello?

Feature #10478: host debian repos - Katello - Foreman

Thanks Greg.

I'm interested in the roadmap for Katello (and here, particularly as it
relates to Debian support). We're trying to make Katello work for us, but
we're not clear where it's future lies in our organisation. To hijack my
own thread, another example is whether/when ansible will usurp puppet.

··· On 22 February 2016 at 10:09, Greg Sutcliffe wrote:

On 22 February 2016 at 10:05, JC mr.jamie.caldwell@gmail.com wrote:

Hi,

What is the likelihood of Debian packages being supported by Katello?

Feature #10478: host debian repos - Katello - Foreman

As the bug says, the main blocker is deb support in Pulp. To my knowledge,
no one is currently working on that, although I hear it’s mostly done and
just needs someone with good Apt/Dpkg knowledge to check it over and give
it some good testing. This may be incorrect, I just get rumours :wink:

Once that’s done, the remaining work for Katello to support deb can be
figured out.


You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/jIdXcUnXr0E/unsubscribe.
To unsubscribe from this group and all its topics, 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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

> Thanks Greg.
>
> I'm interested in the roadmap for Katello (and here, particularly as it
> relates to Debian support). We're trying to make Katello work for us, but
> we're not clear where it's future lies in our organisation. To hijack my
> own thread, another example is whether/when ansible will usurp puppet.
>

As stated, Katello's ability to manage a particular content type is tied to
Pulp's support for that content type. The more interest we see, the more we
as a project can work with the Pulp team to drive prioritization. I would
also encourage any users that are interested in directly voicing request to
the Pulp team via their mailing list (
https://www.redhat.com/mailman/listinfo/pulp-list) or issue tracker (
https://pulp.plan.io/projects/pulp_deb). Currently, the only other types
Pulp provides that Katello does not provide the user directly are
generic/file type (coming in Katello 3.0) and python.

Further, if supporting more content types is a priority that users would
like to see then hearing that is good to allow us to prioritize better.

Can you clarify what you mean by ansible usupring puppet? These two
entities can exist in a lot of contexts.

Eric

··· On Mon, Feb 22, 2016 at 5:18 AM, Jamie Caldwell wrote:

On 22 February 2016 at 10:09, Greg Sutcliffe greg.sutcliffe@gmail.com > wrote:

On 22 February 2016 at 10:05, JC mr.jamie.caldwell@gmail.com wrote:

Hi,

What is the likelihood of Debian packages being supported by Katello?

Feature #10478: host debian repos - Katello - Foreman

As the bug says, the main blocker is deb support in Pulp. To my
knowledge, no one is currently working on that, although I hear it’s
mostly done and just needs someone with good Apt/Dpkg knowledge to check
it over and give it some good testing. This may be incorrect, I just get
rumours :wink:

Once that’s done, the remaining work for Katello to support deb can be
figured out.


You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/jIdXcUnXr0E/unsubscribe.
To unsubscribe from this group and all its topics, 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 https://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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

Thanks Eric. Do you have a list of features that will make it into 3.0 and
a timeline for its release?

We're poised to invest more into the config. management of our estate. If
we keep Katello/Foreman at the centre, it would help to know which tool(s)
will (most likely) be available (within the delivered stack) in the future.

··· On 22 February 2016 at 13:41, Eric D Helms wrote:

On Mon, Feb 22, 2016 at 5:18 AM, Jamie Caldwell < > mr.jamie.caldwell@gmail.com> wrote:

Thanks Greg.

I’m interested in the roadmap for Katello (and here, particularly as it
relates to Debian support). We’re trying to make Katello work for us, but
we’re not clear where it’s future lies in our organisation. To hijack my
own thread, another example is whether/when ansible will usurp puppet.

As stated, Katello’s ability to manage a particular content type is tied
to Pulp’s support for that content type. The more interest we see, the more
we as a project can work with the Pulp team to drive prioritization. I
would also encourage any users that are interested in directly voicing
request to the Pulp team via their mailing list (
https://www.redhat.com/mailman/listinfo/pulp-list) or issue tracker (
https://pulp.plan.io/projects/pulp_deb). Currently, the only other types
Pulp provides that Katello does not provide the user directly are
generic/file type (coming in Katello 3.0) and python.

Further, if supporting more content types is a priority that users would
like to see then hearing that is good to allow us to prioritize better.

Can you clarify what you mean by ansible usupring puppet? These two
entities can exist in a lot of contexts.

Eric

On 22 February 2016 at 10:09, Greg Sutcliffe greg.sutcliffe@gmail.com >> wrote:

On 22 February 2016 at 10:05, JC mr.jamie.caldwell@gmail.com wrote:

Hi,

What is the likelihood of Debian packages being supported by Katello?

Feature #10478: host debian repos - Katello - Foreman

As the bug says, the main blocker is deb support in Pulp. To my
knowledge, no one is currently working on that, although I hear it’s
mostly done and just needs someone with good Apt/Dpkg knowledge to check
it over and give it some good testing. This may be incorrect, I just get
rumours :wink:

Once that’s done, the remaining work for Katello to support deb can be
figured out.


You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/jIdXcUnXr0E/unsubscribe.
To unsubscribe from this group and all its topics, 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 https://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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University


You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/jIdXcUnXr0E/unsubscribe.
To unsubscribe from this group and all its topics, 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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

I wouldn't expect either to be going away - Foreman tries to support as
many config management systems as it can. That's why you can add them via
plugins. Of course, Puppet has been part of core Foreman since day 1, but
the foreman_ansible plugin is getting huge interest at the moment, and I
expect it will be maintained going forward.

Greg

··· On 22 February 2016 at 14:18, Jamie Caldwell wrote:

We’re poised to invest more into the config. management of our estate. If
we keep Katello/Foreman at the centre, it would help to know which tool(s)
will (most likely) be available (within the delivered stack) in the future.

Thanks Greg.

··· On 23 February 2016 at 12:01, Greg Sutcliffe wrote:

On 22 February 2016 at 14:18, Jamie Caldwell mr.jamie.caldwell@gmail.com > wrote:

We’re poised to invest more into the config. management of our estate.
If we keep Katello/Foreman at the centre, it would help to know which
tool(s) will (most likely) be available (within the delivered stack) in the
future.

I wouldn’t expect either to be going away - Foreman tries to support as
many config management systems as it can. That’s why you can add them via
plugins. Of course, Puppet has been part of core Foreman since day 1, but
the foreman_ansible plugin is getting huge interest at the moment, and I
expect it will be maintained going forward.

Greg


You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/jIdXcUnXr0E/unsubscribe.
To unsubscribe from this group and all its topics, 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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.