Okay for anyone still around, I was able to get this sorted, it appears that the initial file I was using was either corrupted or maybe a patch for an existing installation.

I've documented the process, copied below for reference. I won't be sharing IBMs RPM's on this post. You should be able to get these directly from IBM's website free of charge, but your mileage may vary.

Installing IBM Datapower on CentOS 8/9 or Rocky Linux 8/9 to your Hypervisor/Cloud Provider

Minimum System Requirements
• 4 vCPU
• 16 GiB RAM
• 80 GiB Disk Space
• 4 Network Interfaces – with DHCP or Statically Assigned IPs
• 2 Available Loop devices – Documented Below
• Default Partitioning will work, can be configured to meet any security requirements (separate LV for VAR for example)
• Installation without a GUI recommended with these below features
◦ “Server Installation” Option
▪ Guest Agents (Drivers for Hypervisor/Cloud recommended)
▪ Remote Management for Linux recommended – SSH and or Cockpit
• Root only account – User accounts are unnecessary
• Security Policy to adhere to any State/Fed requirements (may effect Installation Destination configuration – not documented here).

Configure Timezone and any other settings as required – no specific documentation needed

Sample User: root
Password: your-password

Upon installation check for updates and install a few required repositories.

sudo dnf update -y sudo dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm sudo dnf update -y sudo dnf search schroot sudo dnf install schroot ipvsadm kmod telnet -y

Post installation of dependencies we need to confirm our loop devices are configured.

Confirm what loop devices exist (likely there is only 1) so we’ll need to create some with the below.

List your loop devices:

ls -l /dev/loop* brw-r----- 1 rootls disk 7, 0 Jul 24 17:49 /dev/loop-control

We only have the loop-control device, so create two more loop devices with the below.

mknod -m660 /dev/loop1 b 7 8 mknod -m660 /dev/loop2 b 7 8

Confirm the devices are listed.

ls -l /dev/loop* brw-rw----. 1 root root 7, 8 Nov 27 08:10 /dev/loop1 brw-rw----. 1 root root 7, 8 Nov 27 08:10 /dev/loop2 crw-rw----. 1 root disk 10, 237 Nov 27 07:51 /dev/loop-control

Now transfer or download the Datapower and LibgCrypt RPMs to this system using something line wget or WinSCP depending on access. You can find libgcrypt here (https://rpmfind.net)

Once transferred, you may have to decompress the installation files.

tar -xf idg_lx10540.cd.ASL.prod.tar

Now we can install the program

sudo yum install idg_lx.10540.image.x86_64.rpm idg_lx10540.common.x86_64.rpm

Once installed, you’ll connect to the system via telnet on the system’s loopback address

telnet 127.0.0.1 2200 Initial login is: admin Initial Password is: admin

Confirm to all prompts with Y and then run/create and confirm a new password

You must restart the DataPower Gateway to make the Common Criteria policies effective.

idg# configure terminal;web-mgmt;admin-state enabled;local-address 0 9090;exit Global mode Modify Web management service configuration

Now you can go to the web console via your computer and using the primary IP address. In our example
https://ip-address:9090

You’ll use the login password you created while connected via SSH. You’ll have to create yet another new password.

Once the password is updated, you’ll be able to login and complete the setup by accepting the license agreement.

After accepting the licensing agreement the system will need to reboot. After logging in via SSH you’ll need to restart the web interface.

telnet 127.0.0.1 2200 admin <password> idg<config> idg <config> configure terminal;web-mgmt;admin-state enabled;local-address 0 9090;exit

That's the complete installation process from start to finish. The last step would be to setup initialization of the datapower service upon restart. I'll be working on this sometime this week probably so that the environment is fault tolerant.

@gotwf said in SAMIT: IBM Is Killing Off CentOS:

@scottalanmiller Yes. This I know. But this isn't bare metal but rather SmartOS hypervisor in a Triton datacenter. So I presume all is atop ZFS. I never delved deeper so honestly do not know.

Hopefully not, as ZFS isn't all that fast. But you need XFS touching WiredTiger... what's lower in the stack isn't what it is concerned with. You still control your own filesystem regardless of what the datacenter may or may not use elsewhere.

It was all formal, no education.

@scottalanmiller said in IBM z 14 Mainframe Released:

@travisdh1 said in IBM z 14 Mainframe Released:

@mlnews Sometimes you just have to wonder about marketing guys "New secure services with Java". Javascript maybe, but Java? That on top of the whole encryption thing, really people.

I'm sure they're amazing, just wish I had a need for one!

Actually Mainframes run insane amounts of traditional Java. Because Java is what replaced COBOL in financial applications and because mainframes are focused primarily on financial workloads, it's a very big deal there.

Ah. That'd explain it then. I'll grant that I'd rather deal with JAVA than COBOL!

Looking at the details page, here is a limitation depending on how you handle client accounts, or your own accounts.

What are the Lightsail service limits?
You can currently create up to 20 Lightsail instances, 5 static IPs, and 3 DNS domain zones in a Lightsail account.

But this is pretty cool. Ability to manage traffic before it hits your VPS:

Can I manage firewall settings for my instance?
.
You can control the data traffic for your instances by using the Lightsail firewall. From the Lightsail console, you can set rules about which ports of your instance are publicly accessible for different types of traffic.

@gjacobse The customer didn't get back to me, so I'm waiting on them.

Never saw that. And it doesn't seem to make any sense. And certainly doesn't make me want to use Linux. What a freaking weird ad.

It would not be unlikely for the power of this workstation to be comparable to more than the processing capabilities of a fully populated Proliant DL580 quad CPU Xeon server.

Which brings up an interesting point, this means that IBM has abandoned Lenovo, their long term partner and the owner of the old IBM brand. So, in a way, IBM no longer runs IBM! Which is not that shocking, since even in 2000 - 2001 they relied on Sun to provide their servers instead of eating their own dogfood.

Good point. I don't particularly doubt that it is there, just don't want to count unhatched chickens, you know? HP used to sell Proliants with the built in virtualization disabled via BIOS. Not that IBM would pull that, but without knowing that the feature is there for sure, it's something to look into.