#DevOps

In case you're planning on deploying IRIS For Health, or any of our containerized products, via the IKO on OpenShift, I wanted to share some of the hurdles we had to overcome.

As with any IKO based installation, we first need to deploy the IKO itself. However we were getting this error:

So it appears that this feature is still missing in 2022.1 (https://docs.intersystems.com/iris20221/csp/docbook/DocBook.UI.Page.cls?...).

Does anyone have any thoughts or ideas on how to create Namespace Package Mappings on deployment in a 'neat' way during automated deployment?

I want to start this project and wants to know the best practices, you guys using to arrange the project. I have done lot of mvc projects and API's in c#. But Intersystems is new to me. Please give me some suggestions like how can I Arrange the objects. Like for eg. Where can I store the productions objects like services,process and operations. will that be like under each resouces folder name? and what are the base classes, and how can I store them? basically please give me some idea about how Can I arrange them .

Thank you

Sai

The Istio Service Mesh is commonly used to monitor communication between services in applications. The "battle-tested" sidecar mode is its most common implementation. It will add a sidecar container to each pod you have in your namespace that has Istio sidecar injection enabled.

Hi Community,

Enjoy watching the new session recording from the InterSystems AI+ML Summit 2021:

⏯ AI+ML Summit Convergent Analytics – Healthcare Stream

https://www.youtube.com/embed/yDRZwK3maeQ
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

We released a new version of ZPM (Package Manager)

New in ZPM 0.2.14 release:

• Publishing timeout
• Embedded vars usage in module parameters
• Package installation from Github repo
• Transaction support for install, load and publish.

See the details below.

IAM - InterSystems API Manager is a great tool for monitoring your traffic. If you are trying to use it in your Kubernetes cluster you may have tried doing a deployment similar to this one:

Does anyone happen to have a sample Configuration (CPF) Merge file that includes Action parameters setting up authentication methods (e.g.

@Jeff Fried

Hi Jeff,

I reviewed the Ensemble 2018 support documentation
https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY...

And I did not find a restriction on the use of Ensemble 2018 installed on Docker with Openshift, but I received information that Intersystems would not support this installation case. That is true?

Hey Developers,

Watch this video to learn about observability of your InterSystems IRIS application with InterSystems System Alerting and Monitoring (SAM) and modern DevOps tooling:

⏯ Observability with InterSystems IRIS @ Global Summit 2022

https://www.youtube.com/embed/pJUm5GABMXU
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

In this article I'll show you how to set up in your laptop, very quickly, a cluster of IRIS nodes in sharding. It's not the goal of this article neither to talk about sharding in detail nor define a deployment of a production ready architecture, but to show how to set up quickly, in your own machine, a cluster of IRIS instances configured as shard nodes, with which you'll able to play and test this functionality. If you're insterested in knowing more about sharding in IRIS, take a look at the documentation clicking here.

First and foremost, I want to remark that IRIS sharding will allow us 2 things:

• Define, load and query shard tables, which data will be distributed transparently between the cluster's nodes
• Define federated tables, which offer a global and composed view of data belonging to different tables that will be physically stored in different distributed nodes

So, as I said, we let for other article playing with shard or federated tables, and just focus now in the previous step, that is, setting up the cluster of shard nodes.

Hi Community,

Please welcome the new video on InterSystems Developers YouTube:

⏯ Automating InterSystems IRIS Instances Configuration

https://www.youtube.com/embed/o-ujZctW2dg
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

I'm looking for a way to have an IRIS db distributed over several (hw) drives.
Without touching the internal data structures (e.g. mapping) !
Are there any options in file systems to achieve this "splitting" or "appending" ?

Historic background:

Hi Community,

Please welcome the new video on InterSystems Developers YouTube:

⏯ Best Practices for In-Platform AI

https://www.youtube.com/embed/K2xm6LIVA6U
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]