[BlueOnyx:22497] RHEL 8 Beta is out

[Ernie]

Hi All,
for for those that are keen, Redhat just announced the RHEL 8 Beta

https://developers.redhat.com/rhel8/

Not sure what impact it will have on BX or how long before CentOS has it.


- Ernie.

[Fungal Style]

Michael,

And the point I (and most likely everyone else) was waiting to read.. was at the end... migration... __

Sounds good and looks like you have a big task.

Regards
Brian

On 16/11/18, 1:46 pm, "Blueonyx on behalf of Michael Stauber" <blueonyx-***@mail.blueonyx.it on behalf of ***@blueonyx.it> wrote:

Hi Ernie,

Post by Ernie
for for those that are keen, Redhat just announced the RHEL 8 Beta
https://developers.redhat.com/rhel8/

Thank you. I've grabbed the ISO of it and will start some preliminary
development work for 5210R on it within the close future.

Post by Ernie
Not sure what impact it will have on BX or how long before CentOS has it.

I have no solid idea when the beta ends and when we can expect to see
the first releases of RHEL 8 and CentOS 8 respectively. But I guess it
might be a couple of months. Like sometime in Q1 of 2019. We'll see.

I poked a bit around in the RHEL-8-beta ISO to get an idea what we can
expect. Here are some ballpark figures:

- Kernel 4.18
- Perl 5.26.4
- PHP 7.1.20 and PHP-7.2.11 (the ISO has both)
- Apache 2.8.0
- Nginx 1.14.0
- Sendmail 8.15.2
- Dovecot 2.2.36
- MariaDB 10.3.10
- OpenSSL 1.1.1
- OpenSSH 7.8p1
- Systemd 239-8
- Python 2.7.15 plus Python 3.6.6
- RPM 4.14.2
- Glibc 2.28
- Glib2 2.56
- Java 1.8.0

As for the impact on BlueOnyx? I had already set the model number 5210R
aside for it and had done some preliminary checks of what would be
needed to port the GUI to any newer version of PHP.

Right now the core of the GUI (base-alpine) uses CodeIgniter v2.2.6
(which is EOL) and for 5210R we certainly want to use a newer version.
Such as the stable v3.1.9, which also supports PHP-7.1 and PHP-7.2 out
of the box.

But the fun starts right there:

Every GUI page is a CodeIgniter PHP class. PHP class names must start
with a capitalized character. Example: "TestClass" is fine, but
"testClass" is not. We already honored this religiously throughout the GUI.

Since CodeIgniter 3.0.0 the file names for these classes also *must*
have their leading character capitalized. Which we have not. A handfull
of Classes under /usr/sausalito/ui/ci/application/libraries/ and *all*
classes under /usr/sausalito/ui/ci/application/modules/ don't follow the
new mandatory naming conventions.

That means all of these must be renamed (and the CI routing tables must
be updated) and it must be checked that filename and classname are
identical both in name and capitalization.

That's around 250-300 PHP classes that need fixing right off the bat.

Plus there will be several things that changed behavior between PHP
versions and we're moving right from PHP-5.4.16 to PHP-7.2.11. That's
the biggest PHP version gap BlueOnyx *ever* had to bridge: We're moving
five *major* versions of PHP ahead in one go.

It's not *that* bad (I hope), as a lot of the heavy lifting of the GUI
is done by CodeIgniter itself or had been externalized into shared
libraries and PHP Classes that are re-used throughout the GUI. Still: I
expect to run into some unexpected glitches that need a fixing.

The next couple of challenges are adjusting the GUI to the updated
services. Like from Apache 2.4 to 2.8. Nginx is no surprise and we've
already go the same version on 5209R that RedHat brings in RHEL8.
Sendmail? Trivial changes. Dovecot? Good to go w/o changes. FTP? We
bring our own, so no surprises either. Making these adjustments should
be fairly quick, with the new Apache being the only real complication.

We'll drop Apache Tomcat in 5210R, though. It already doesn't work right
in 5209R and dragging that dead carcass over to 5210R makes no sense.

I think that by the end of this year or more probably in January 2019
I'll have a draft of 5210R ready that can quickly be adjusted to
whatever slightly modified realities we'll find once CentOS 8 is
officially out.

I'll get it covered.

FWIW: By that time I also hope to have "EasyMigrate" ready, so moving
from 5207R/5208R/5209R to 5210R should be easier and more comfortable
than doing it with CMU.

--
With best regards

Michael Stauber
_______________________________________________
Blueonyx mailing list
***@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx

[Ernie]

Hi Michael,
I grabbed the ISO too, it seems to have two php versions on it, 7.1 and 7.2
but the relase notes say 7.2 is what's distrubted with it

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html-single/8.0_beta_release_notes/


- Ernie.

Post by Fungal Style
Hi Ernie,

Post by Ernie
for for those that are keen, Redhat just announced the RHEL 8 Beta
https://developers.redhat.com/rhel8/

Thank you. I've grabbed the ISO of it and will start some preliminary
development work for 5210R on it within the close future.

Post by Ernie
Not sure what impact it will have on BX or how long before CentOS has it.

I have no solid idea when the beta ends and when we can expect to see
the first releases of RHEL 8 and CentOS 8 respectively. But I guess it
might be a couple of months. Like sometime in Q1 of 2019. We'll see.
I poked a bit around in the RHEL-8-beta ISO to get an idea what we can
- Kernel 4.18
- Perl 5.26.4
- PHP 7.1.20 and PHP-7.2.11 (the ISO has both)
- Apache 2.8.0
- Nginx 1.14.0
- Sendmail 8.15.2
- Dovecot 2.2.36
- MariaDB 10.3.10
- OpenSSL 1.1.1
- OpenSSH 7.8p1
- Systemd 239-8
- Python 2.7.15 plus Python 3.6.6
- RPM 4.14.2
- Glibc 2.28
- Glib2 2.56
- Java 1.8.0
As for the impact on BlueOnyx? I had already set the model number 5210R
aside for it and had done some preliminary checks of what would be
needed to port the GUI to any newer version of PHP.
Right now the core of the GUI (base-alpine) uses CodeIgniter v2.2.6
(which is EOL) and for 5210R we certainly want to use a newer version.
Such as the stable v3.1.9, which also supports PHP-7.1 and PHP-7.2 out
of the box.
Every GUI page is a CodeIgniter PHP class. PHP class names must start
with a capitalized character. Example: "TestClass" is fine, but
"testClass" is not. We already honored this religiously throughout the GUI.
Since CodeIgniter 3.0.0 the file names for these classes also *must*
have their leading character capitalized. Which we have not. A handfull
of Classes under /usr/sausalito/ui/ci/application/libraries/ and *all*
classes under /usr/sausalito/ui/ci/application/modules/ don't follow the
new mandatory naming conventions.
That means all of these must be renamed (and the CI routing tables must
be updated) and it must be checked that filename and classname are
identical both in name and capitalization.
That's around 250-300 PHP classes that need fixing right off the bat.
Plus there will be several things that changed behavior between PHP
versions and we're moving right from PHP-5.4.16 to PHP-7.2.11. That's
the biggest PHP version gap BlueOnyx *ever* had to bridge: We're moving
five *major* versions of PHP ahead in one go.
It's not *that* bad (I hope), as a lot of the heavy lifting of the GUI
is done by CodeIgniter itself or had been externalized into shared
libraries and PHP Classes that are re-used throughout the GUI. Still: I
expect to run into some unexpected glitches that need a fixing.
The next couple of challenges are adjusting the GUI to the updated
services. Like from Apache 2.4 to 2.8. Nginx is no surprise and we've
already go the same version on 5209R that RedHat brings in RHEL8.
Sendmail? Trivial changes. Dovecot? Good to go w/o changes. FTP? We
bring our own, so no surprises either. Making these adjustments should
be fairly quick, with the new Apache being the only real complication.
We'll drop Apache Tomcat in 5210R, though. It already doesn't work right
in 5209R and dragging that dead carcass over to 5210R makes no sense.
I think that by the end of this year or more probably in January 2019
I'll have a draft of 5210R ready that can quickly be adjusted to
whatever slightly modified realities we'll find once CentOS 8 is
officially out.
I'll get it covered.
FWIW: By that time I also hope to have "EasyMigrate" ready, so moving
from 5207R/5208R/5209R to 5210R should be easier and more comfortable
than doing it with CMU.
--
With best regards
Michael Stauber
_______________________________________________
Blueonyx mailing list
http://mail.blueonyx.it/mailman/listinfo/blueonyx

[Ernie]

Hi Michael,
you have to do this:

QUICKSTART INSTALLATION

1. Download the Binary DVD ISO file for your hardware architecture from the
location corresponding to your hardware architecture:

Intel/AMD 64-bit
https://red.ht/2ROrd80

IBM Power little endian
https://red.ht/2FnoQb6

IBM z Systems
https://red.ht/2RUif9k

ARM 64-bit
https://red.ht/2DmPZbn

Optionally, you can create bootable installation media on a USB drive or DVD,
using software on your computer and appropriate hardware . The exact series
of steps to create bootable installable media from an ISO image file varies,
depending on the operating system and application. Consult your application
documentation for the exact steps, taking care to ensure that the media is
created to be bootable.

2. Boot the system directly from the ISO files (if installing as a guest) or
from the newly created physical media or USB flash drive.

3. Follow instructions provided by the graphical installer to complete the
installation.


CONFIGURING A REMOTE BETA SOFTWARE SOURCE

Your system can be configured to install additional software packages that were
not selected at the time of initial installation. The recommended approach is to
configure remote repositories by following these steps:

1. Download the file ???rhel-8-beta.repo??? from
https://downloads.redhat.com/redhat/rhel/rhel-8-beta/rhel-8-beta.repo and
copy it to a temporary location (e.g. /tmp).

2. Edit the file locally and change ???enabled = 0??? to ???enabled = 1??? for the
architecture-specific repositories you want your RHEL 8 Beta installation to
have access to. Enable both rhel-8-for-$arch-baseos-beta-rpms and
rhel-8-for-$arch-appstream-beta-rpms for your specific architecture.

3. As the root user, copy this file to the following location:
/etc/yum.repos.d/

4. Clean the cache in Yum using the following command:
yum clean all

5. Re-create the Yum repository cache by typing the following command:
yum makecache

You are now ready to install additional software packages from the remote Beta
software location.


- Ernie.

Post by Fungal Style
Hi Ernie,

Post by Ernie
I grabbed the ISO too, it seems to have two php versions on it, 7.1 and 7.2
but the relase notes say 7.2 is what's distrubted with it

The ISO has both. I just did a minimal install (with optional
developer-tools checked as well) into a VirtualBox VM.
The resulting server has no PHP at all installed (no surprise). And now
I'm struggling to enable the YUM repositories. I only have a "RedHat
Developer" subscription with RedHat, which amounts to nothing. When I do
"subscription-manager register --auto-attach" and enter my credentials,
it won't allow me to attach any repositories.
https://developers.redhat.com/rhel8/install-rhel8-vbox/
# yum repolist
Updating Subscription Management repositories.
Red Hat Enterprise Linux 8 for x86_64 - AppStream Beta (RPMs)
Red Hat Enterprise Linux 8 for x86_64 - BaseOS Beta (RPMs)
Updating Subscription Management repositories.
This system is registered to Red Hat Subscription Management, but is not
receiving updates. You can use subscription-manager to assign subscriptions.
Updating Subscription Management repositories.
This system is registered to Red Hat Subscription Management, but is not
receiving updates. You can use subscription-manager to assign subscriptions.
No repositories available
The web portal https://access.redhat.com/management/systems/ shows the
system, but I can't assign any subscriptions either. Instead it says (in
German, I'm loosely translating it): "This system is fully up to date,
not covered by any subscriptions. You're not getting updates."
I'll unregister this install and do a reinstall to see how that goes. :-/
--
With best regards
Michael Stauber
_______________________________________________
Blueonyx mailing list
http://mail.blueonyx.it/mailman/listinfo/blueonyx

[Dirk Estenfeld]

Hello,

I think we can re-add Tomcat (if someone need it) by a docker image.
But maybe what you could add instead of tomcat is nodejs. I think this is
more up to date and will get more usable than tomcat.

Best regards,
Dirk

---

blackpoint GmbH – Friedberger Straße 106b – 61118 Bad Vilbel

Tel.: [phone]
Fax: [phone]
eMail: ***@blackpoint.de

Vertretungsberechtigt Dirk Estenfeld und Mario Di Rienzo HRB 50093 Frankfurt
am Main USt.-IdNr. de210106871

CRM on Demand – eine gute Idee

Besuchen Sie uns im Internet unter www.blackpoint.de
Problemlos Domains registrieren: www.edns.de
Einfach und günstig Daten sichern: www.back2web.de
Mitglied im:   




Confidentiality Notice:
This e-mail message, including any attachments,is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the sender
by reply e-mail and destroy all copies of the original message.


-----Ursprüngliche Nachricht-----
Von: Blueonyx <blueonyx-***@mail.blueonyx.it> Im Auftrag von Michael
Stauber
Gesendet: Freitag, 16. November 2018 03:37
An: ***@mail.blueonyx.it
Betreff: [BlueOnyx:22498] Re: RHEL 8 Beta is out - BlueOnyx 5210R
development starts

Hi Ernie,

Post by Ernie
for for those that are keen, Redhat just announced the RHEL 8 Beta
https://developers.redhat.com/rhel8/

Thank you. I've grabbed the ISO of it and will start some preliminary
development work for 5210R on it within the close future.

Post by Ernie
Not sure what impact it will have on BX or how long before CentOS has it.

I have no solid idea when the beta ends and when we can expect to see the
first releases of RHEL 8 and CentOS 8 respectively. But I guess it might be
a couple of months. Like sometime in Q1 of 2019. We'll see.

I poked a bit around in the RHEL-8-beta ISO to get an idea what we can
expect. Here are some ballpark figures:

- Kernel 4.18
- Perl 5.26.4
- PHP 7.1.20 and PHP-7.2.11 (the ISO has both)
- Apache 2.8.0
- Nginx 1.14.0
- Sendmail 8.15.2
- Dovecot 2.2.36
- MariaDB 10.3.10
- OpenSSL 1.1.1
- OpenSSH 7.8p1
- Systemd 239-8
- Python 2.7.15 plus Python 3.6.6
- RPM 4.14.2
- Glibc 2.28
- Glib2 2.56
- Java 1.8.0

As for the impact on BlueOnyx? I had already set the model number 5210R
aside for it and had done some preliminary checks of what would be needed to
port the GUI to any newer version of PHP.

Right now the core of the GUI (base-alpine) uses CodeIgniter v2.2.6 (which
is EOL) and for 5210R we certainly want to use a newer version.
Such as the stable v3.1.9, which also supports PHP-7.1 and PHP-7.2 out of
the box.

But the fun starts right there:

Every GUI page is a CodeIgniter PHP class. PHP class names must start with a
capitalized character. Example: "TestClass" is fine, but "testClass" is not.
We already honored this religiously throughout the GUI.

Since CodeIgniter 3.0.0 the file names for these classes also *must* have
their leading character capitalized. Which we have not. A handfull of
Classes under /usr/sausalito/ui/ci/application/libraries/ and *all* classes
under /usr/sausalito/ui/ci/application/modules/ don't follow the new
mandatory naming conventions.

That means all of these must be renamed (and the CI routing tables must be
updated) and it must be checked that filename and classname are identical
both in name and capitalization.

That's around 250-300 PHP classes that need fixing right off the bat.

Plus there will be several things that changed behavior between PHP versions
and we're moving right from PHP-5.4.16 to PHP-7.2.11. That's the biggest PHP
version gap BlueOnyx *ever* had to bridge: We're moving five *major*
versions of PHP ahead in one go.

It's not *that* bad (I hope), as a lot of the heavy lifting of the GUI is
done by CodeIgniter itself or had been externalized into shared libraries
and PHP Classes that are re-used throughout the GUI. Still: I expect to run
into some unexpected glitches that need a fixing.

The next couple of challenges are adjusting the GUI to the updated services.
Like from Apache 2.4 to 2.8. Nginx is no surprise and we've already go the
same version on 5209R that RedHat brings in RHEL8.
Sendmail? Trivial changes. Dovecot? Good to go w/o changes. FTP? We bring
our own, so no surprises either. Making these adjustments should be fairly
quick, with the new Apache being the only real complication.

We'll drop Apache Tomcat in 5210R, though. It already doesn't work right in
5209R and dragging that dead carcass over to 5210R makes no sense.

I think that by the end of this year or more probably in January 2019 I'll
have a draft of 5210R ready that can quickly be adjusted to whatever
slightly modified realities we'll find once CentOS 8 is officially out.

I'll get it covered.

FWIW: By that time I also hope to have "EasyMigrate" ready, so moving from
5207R/5208R/5209R to 5210R should be easier and more comfortable than doing
it with CMU.

--
With best regards

Michael Stauber