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?

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. 

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.

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.

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?

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.cls...

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.cls...

Hi!  

IRIS containers - including Community Edition - is available from the containers.intersystems.com.  The place to start is here.  The CE containers are also available from dockerhub here.

Telling you something you already know:  You've got some bad state in your container image or in the persistent storage. 

I think we'd need to see more to be able to help:
* What's the command you're using to run the container?  All the environment variables and mount points is super-important here
* What's the container you're running?  If its your own, maybe the Dockerfile would help

Here's an example I had put together in a different context.  It sets up a single IRIS instance with a WebGateway and IAM.  It also sets up TLS on the IAM instance.

apiVersion: intersystems.com/v1alpha1
kind: IrisCluster
metadata:
  name: fhir-iam
spec:
  imagePullSecrets:
    - name: icr-secret
  storageClassName: gp2
  licenseKeySecret:
    name: fhir-iris-key-secret
  configSource:
    name: fhir-iris-cpf
  tls:
    iam:
      secret:
        secretName: fhir-iam-tls
  topology:
    iam:
      image: containers.intersystems.com/intersystems/iam:3.0.2.0-4
    webgateway:  
      image: containers.intersystems.com/intersystems/webgateway:2022.1.0.209.0
      type: apache
      replicas: 1
      applicationPaths:
        - /csp/sys
        - /myfhirserver
        - /csp/healthshare
      alternativeServers: LoadBalancing
    data:
      image: containers.intersystems.com/intersystems/irishealth:2022.1.0.209.0
  serviceTemplate:
    spec:
      type: ClusterIP

It does not.  Here's the details on the community edition license:

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls...

It's a good question.  I had thought raising an irisbuiltins.SQLError would do the trick, but it still returns the wrapped exception you see.  I'll put in for an enhancement.

There is not.  Cache has not been ported to ARM64.  IRIS has ARM ODBC drivers if that's an option for your application.

Parameters aren't available in embedded python.  An easy workaround is to create a Property that reflects the parameter or to create an objectscript method to return the parameter.

I'm curious about the use case.

Glad to hear the interest in Python.

When you use embedded python, IRIS loads Python into memory in the process (via CPython).  The specific version of Python depends on your OS.  That's documented here:  https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.UI...

Loading Python into the IRIS process does just what you think it does - not a separate process and references in Python to ObjectScript objects are in-memory.  So there's no performance difference between using Embedded Python from IRIS or starting with a Python program and `import iris`.

The start.sh script just calls docker-compose up.  You should be able to do podman-compose up to start SAM.  The first time it runs, it needs to download the containers (you can see what they are in the docker-compose.yaml file) if you don't already have them in your local podman cache.

During normal runtime, SAM doesn't require access to the internet.  That said, I haven't personally tested SAM without internet access.

Good luck!  Let us know how it goes.

It sounds like you're looking for persistent storage, which means you want to use the Durable %SYS feature.  Here's the info to get you started:  https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls....

To answer your specific questions:

1. Yes, IRIS works with any StorageClass that your Kubernetes cluster has installed, including any storage class you might have created for EBS or EFS. If you haven't yet tried it, the InterSystems Kubernetes Operator can simplify deployments in Kubernetes.  Even if you don't use IKO in production, it's a good way to see how everything should be configured.  https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls...

2. IRIS 2022.1 also includes first-class support for AWS SQS.  You can use it in your Productions or use ObjectScript to send messages to it.  https://docs.intersystems.com/irislatest/csp/documatic/%25CSP.Documatic....