Puppet required?
by Avram Lubkin
I was looking over the project and it looks interesting, much improved over
Spacewalk. I particularly like how different projects are used instead of
one monolithic project. There's just one thing that concerns me. It looks
like if I want to do provisioning I have to use Foreman and if I use
Foreman I have to use Puppet. Since Puppet requires ruby installed on all
clients I can't deploy it. This is due to a security requirement. I can't
add interpreters to a system unless I have a good justification. I can do
what puppet does without adding another interpreter, so I can't justify it.
I know there are lots of organizations that use puppet and probably install
Ruby to support it, but I've never worked with a group that would allow
that. Any plans to support CFengine or something similar that wouldn't
require another interpreter on the clients? Python is Okay too, since any
RHEL or RHEL-like system already has it.
Please reply all, not on the list.
Thanks,
Avram
10 years, 11 months
Initial repo sync from DVD?
by Guy Matz
Hello!
For now, my katello server is on a network that does not have direct
access to the internets . . . I do have a repo on DVD though, so I'm
wondering if it's possible to "repo sync" from a file URL instead of
http? e.g. file:///mnt ?
Thanks a lot,
Guy Matz
11 years
katello 1.3?
by Guy Matz
Hi! Again, thank you to all of the developers of katello! I am really,
really excited about being able to manage my repos this way!!
I am really looking forward to katello 1.3 as I believe its integration
of pulp v2 will allow me to manage debian repositories as well using
something like https://github.com/ekarlso/pulp_deb
Has anyone been able to manage a debian repo using a 1.3 pre-release?
Does anyone have any idea when 1.3 wil be released?
Thanks again!
Guy Matz
11 years, 1 month
Cross fedora version upgrades
by Justin Sherrill
Hi All,
With the upcoming Katello 1.3 release we are only support RHEL 6 &
Fedora 18, which means this is the first katello release that does not
continue support across a single Fedora version (Previously fedora
16). Katello 1.2 was released with upgrade instructions, but they did
not cover upgrading from Fedora 16 to Fedora 17 (so i am going to assume
it was not supported or tested). So keep in mind today that we really
do not have an official policy on upgrading across fedora versions.
Due to the volatile nature of Fedora upgrades (especially going from
fedora 16 to fedora 18 which uses two different upgrade mechanisms), I
am proposing to only support upgrades to from Katello 1.2 to 1.3 on RHEL 6.
What are people's thoughts on that?
Katello 1.3 is somewhat special in that katello 1.2 and 1.3 do not share
a fedora version in common, but going forward what are thoughts around
either:
a) Not supporting upgrades on fedora at all, only supported on RHEL 6
and CentOS 6.
b) Not supporting upgrades from/to different versions of fedora (i.e.
Katello 1.X to 1.Y is supported on Fedora N, but not from N to N+1)
c) Only supporting upgrades from/to different versions of fedora via
backup/import of data and certs.
Keep in mind that no matter what we choose, we can always re-evaluate
our policy due to user requests. To me testing two additional upgrade
scenarios is not worth the time unless people actually use these upgrade
paths.
My Vote is for a) (and here's why). If a user is using katello and
wanting to upgrade from one version to another across many months, they
are likely to want long term stability. Upgrading your operating system
to new major versions ever 6-12 months does not give you long term
stability. Most users that are interested in running a katello server
in production will not use Fedora simply due to the quick release cycle,
they will instead use RHEL or CentOS. which is where I think we need to
target our resources. So my vote would be to:
- Only support upgrades on RHEL and CentOS
- Support CentOS with each release and make sure it works (There are
reports that it does not work currently)
- Harden our backup/restore guide and utilities
Thoughts?
-Justin
11 years, 1 month
