go to post Bob Kuszewski · May 26 Excellent article! A note for people using Kubernetes or Containers in the cloud: This same advice applies for Kubernetes-based and containers-based deployments. When you create a Kubernetes cluster you assign VM resources (NodeGroups, for example) and you'll want to use the advice in this article to create the right nodes and storageclass for your deployment.
go to post Bob Kuszewski · May 18 If you choose to create your own container for C/E, you're responsible for the container and for how it interacts with the host operating system. For example, InterSystems can't give you assistance with creating your Dockerfile or debugging any problems you might have with the container-storage interface. We will, of course, continue to support your usage of C/E. For example, questions about monitoring your queues or creating business operations. If you have detailed questions, please reach out to me.
go to post Bob Kuszewski · May 12 Looks interesting, but the GH repo either doesn't exist or isn't public. Can you check? Thanks!
go to post Bob Kuszewski · May 1 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
go to post Bob Kuszewski · May 1 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
go to post Bob Kuszewski · Mar 15 It does not. Here's the details on the community edition license: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls...
go to post Bob Kuszewski · Mar 15 From a container running in docker, you can always reference host.docker.internal which resolves to the hostname of your host. If you need an external IP address of the host, then you'll need to do something to pass in the ipaddress to the container
go to post Bob Kuszewski · Feb 13 Congrats everyone. There were so many worthy projects this time around that voting was really tricky.
go to post Bob Kuszewski · Feb 7 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.
go to post Bob Kuszewski · Jan 25 This is a temporary problem. We've having problems internally with our ARM container build servers and didn't want to hold up the preview release while we fix it. We expect these problems to be resolved before 2022.3's GA.
