Upgrading to IRIS 2025.1 will keep you up-to-date with the latest platform features and staying on the latest will make sure that you always have an active license.
If you're doing an evaluation, then you can get an evaluation license for 2024.1 via sales
That's right. There's no planned change in supported POWER processors. IBM does a good job of phasing out older processors with new versions of the OS.
When I do that exact same thing, I get different results. Have you pulled the latest version of the container?
docker pull containers.intersystems.com/intersystems/iris:latest-preview
...
docker inspect --format '{{ index .Config.Labels "com.intersystems.platform-version" }}' containers.intersystems.com/intersystems/iris:latest-preview
2025.1.0.204.0My apologies. The correct URL is https://community.intersystems.com/post/intersystems-reports-version-24…
"Common KVM Processor" is a generic CPU name that some virtualization systems provide to client VMs. You can typically override this in your hypervisor to tell the client system the actual CPU type. Unfortunately, the term "Common KVM Processor" doesn't tell us anything about your CPU's capabilities.
The URL that you're generating is the one to the webgateway. Do you have the webgateway running on port 443 of the same IP address as your IRIS server?
Are you pulling form a x86 or ARM machine? I've just pulled the image a dozen times from a number of networks without any problem from my x86-based machine. Which leaves it as either a problem with the ARM image, your network, or something on your machine (anti-virus system perhaps?)
Oracle Linux is supported via the corresponding Red Hat kit. For example, install the Red Hat 8 kit on Oracle Linux 8.
It's possible to do, but it gets really tricky with the current version of IRIS and IKO. The networking piece alone is very complex.
If you can, my advice is to wait for this to be added as an official feature of IRIS & IKO. The design that we've been working through involves making services in each cluster so that all the mirror members can see each other, which is a far simpler design than what you need to do today.
Sadly, IPM/ZPM is NOT (yet!) officially supported by InterSystems
IAM is not available with IRIS Community Edition due to licensing constraints. However, Kong Community Edition works great with IRIS Community Edition. No licenses required for either one.
Just this morning I announced the start of an early access program for Flexible Python Runtime. Here's the link - https://community.intersystems.com/post/join-flexible-python-runtime-ea…
If you're using Python with IRIS through the traditional client/server model - such as DB-API driver or the NativeAPI, you can update from the minimum Python version.
If you're using embedded python (that is, Python running in-process with IRIS), then the version of Python you can use is tied to your OS and can't (yet) be upgraded. They're listed here. We are currently working on the ability to upgrade the Python runtime used by embedded python - expect to hear more about that soon.
I love k9s!
Off the top of my head, I can think of customers running DataDog, Dynatrace, Splunk, and Cloud Watch. There are certainly others.
Along with these big vendors, you might also want to consider SigNoz
Ivy Bridge is the generation just before the cutoff, so you may need to upgrade your computer. We'll have more detailed information on the precise extensions require for 2024.1 when that's closer to release.
Your instincts are correct - IRIS will not install on unsupported processors and Apple silicon are ARM processors.
If you're using IRIS-first workflows for EP, then your Python language methods are journaled just like ObjectScript methods.
If you're using the various IRIS-first EP workflows (setting [language=python] on a method in a class or using Python for your stored procedures, etc), then the python code is stored along with the class. In that case, the python source is stored with your routines. Assuming you have them stored on your data server, then it'll work just as you'd expect.
If you're using a Python-first workflow (create myapp.py and `import iris` from there), you'll need to stage your .py files on all the servers.
Embedded Python was added in IRIS 2022.1 and you're running 2021.1. Can you upgrade the remote server?
There are two basic strategies:
1. Use the web gateway sidecar. This is my recommendation as it's the most straightforward.
2. Call the ObjectScript class that the metrics API uses directly from the shell. A real pain-in-the-neck, but it avoids having the sidecar.
Regarding the new topology.data.irisDatabases.seed field, the field is used to let you create databases that start with some starting data in them instead of the usual empty database. This is useful for applications that typically start with some basic information in them. Here's the link to the docs, if they help.
https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cl…
The Community Edition license is limited to 10GB. Here's the full list of license restrictions:
https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl…
On AIX, the OpenSSL package that comes with AIX is structured differently than in other operating systems. The OpenSSL 3.x package comes with implementations of OpenSSL 1.0.2, 1.1.1, and 3.0. Sadly, the OpenSSL 3.0 implementation which is included in AIX 7.3 TL1 is missing a few features that are critical to correct operation with IRIS. So, currently versions of IRIS use the OpenSSL 1.0.2 implementation. IBM is readying their updated package with the fixes to the OpenSSL 3.0 implementation included.
There's a repo in the community showing various ways to use the webgateway container with the IRIS container. PR's accepted!
https://github.com/intersystems-community/webgateway-examples
IRIS_ML contains the IntegratedML feature and the IRIS kit does not. IntegratedML takes a few additional gigs of disk space, so we give you the choice of the kit you'd like. There's no difference in licensing.
1. Get the NextResult() resultset
2. Get the Metadata from the resultset
The plan for new IRIS containers is to use YYYY.R format only. Let's walk through an example of a few releases for a hypothetical IRIS 2024.1 release.
| Release | Old Tag | New Tag |
| Initial GA | 2024.1.0.123.0 | 2024.1 |
| First maintenance | 2024.1.1.234.0 | 2024.1 |
| Security Fix | 2024.1.1.234.1 | 2024.1 |
This new scheme greatly simplifies your work to keep up with whatever mix of maintenance and security releases we provide. All you need to do is reference iris:2024.1 and you'll pick up the latest bug and security fixes without making any changes to your code.
As for the latest tag, we like the idea so much that we're giving you two. One that lets you get the latest release (iris:latest-cd) and one that lets you get the latest long-term-support release (iris:latest-em).
Unfortunately, there are significant bugs in the OpenSSL 3 available for AIX 7.3 that make running IRIS (or any other high user of OpenSSL) impossible. We have a build in-house from IBM that has fixed the problems that should be available to the public later in the year.