The implementation instructions will be provided when servers are registered on CLN.

The kernel, of course, as well as other critical packages such as glibc, openssh, openssl, and zlib. httpd, mysql, php, and userspace packages will also be supported, as well as the cPanel, Plesk, and DirectAdmin control panels. Other supported packages include: acl, acpid, at, attr, audit, authconfig, basesystem, bash, bc, blktrace, bridge-utils, busybox, bzip2, crash, cyrus-imapd, cyrus-sasl, db4-utils, device-mapper, dhclient, dhcpv6, dmidecode, dos2unix, dovecot, ed, gcc, gd, gdb, glib2, groff, info, Iptstate, logrotate, lslk, lvm2, makedev, nfs4-acl-tools, nfs-utils, nspr, ntp, opensp, pam, perl, procmail, procps, python, rcs, rds-tools, rhnlib, rsync, rsyslog, setroubleshoot, setserial, setup, sos, stunnel, tzdata, vim, wget, yum-metadata-parser, yum-rhn-plugin.

For 1-500 servers running CentOS® 6, it’s $5* per server per month (*Require a 12-month commitment. For month-to-month subscriptions the price is $6 per server per month). For 500+ servers, it’s $3* per server per month (*Require a 12-month commitment. For month-to-month subscriptions the price is $3.6 per server per month). Billing will start the month after usage begins.

No, you will continue running CentOS®. We will just continue updating packages with security fixes.

As mentioned above, there is no OS migration, just a change in repository location. This can be done in-line, with no downtime, or any performance degradation.

As soon as we find or develop a new patch, we apply it to the appropriate package, listed above. Before each package goes into the production repository, we run several testing processes. We also maintain a stable beta repository that we use for testing.

Yes. You would continue using yum, as usual.