go to post Anton Umnikov · May 31, 2021 Longhorn requires at least three nodes by default and frankly makes no sense on a single-node setup. You might try to drop 'storageClassName: longhorn' from the PVC spec and skip the longhorn installation step.Also - check out https://community.intersystems.com/post/amazon-eks-and-iris-high-availab... for AWS EKS setup instructions.
go to post Anton Umnikov · May 14, 2021 You might want to add /usr/irissys/csp/bin/CSP.ini to the list of files to copy. Without it chances are CSP Gateway would not be authorized to communicate to IRIS.
go to post Anton Umnikov · Apr 14, 2021 acloud.guru is my #1 choice for pretty much all of the topics you mentioned. Materials there are good enough for any basic and intermediate level of certification. For advanced/professional level courses I sometimes go for extra content. Examples here: - https://learn.cantrill.io/ for Pro and Speciality - level courses on AWS - https://kodekloud.com/ for k8s Udemy would have some good materials too, but you need to be careful here... This platform would accept anyone who is willing to produce training videos, so the quality might vary. Look at the reviews and recommendations.
go to post Anton Umnikov · Apr 9, 2021 For a simple case (add a couple of classes to the USER namespace) - what would be space savings here?
go to post Anton Umnikov · Mar 19, 2021 I can't picture how "flaky networking" can introduce such a problem here. Longhorn (or any other k8s distributed storage) provides a Persistent Volume level of abstraction for your Deployments and Stateful Sets and takes care of appropriate failover and isolation.If you try to intentionally start multiple IRIS instances against the same volume, the situation would be similar to trying to start two IRIS instances on the same physical machine, mounting the same /mgr directory. Your usual IRIS-level protection (lck files) would kick in and only one IRIS instance would be able to successfully mount your mgr directory.
go to post Anton Umnikov · Mar 19, 2021 Michael, a similar solution (HA without mirroring) can be achieved natively with IRIS/Cache' on VMWare vSphere. Here is the article by @Murray Oldfield on this: https://community.intersystems.com/post/intersystems-data-platforms-and-... Essentially VMWare vSphere would take care of the compute and storage high availability across multiple hosts, playing the same role as k8s and Longhorn in this article. VMWare also advancing its own Kubernetes offering - you might want to take a look at project Tanzu.
go to post Anton Umnikov · Jan 25, 2021 Thanks @Luca Ravazzolo ! The snapshot feature is indeed pretty new. I even had to change the version from snapshot.storage.k8s.io/v1beta1 to snapshot.storage.k8s.io/v1 while working on the article.
go to post Anton Umnikov · Dec 8, 2020 s sc=##class(%ZEN.Auxiliary.jsonSQLProvider).%WriteJSONFromSQL("json","SELECT Name FROM Sample.Person")
go to post Anton Umnikov · Dec 7, 2020 Thanks, @Evgeny Shvarov ! I've updated the article to include ZPM install option
go to post Anton Umnikov · Jun 30, 2020 While the idea is essentially the same (REST API) - each cloud provider uses slightly different calls and signatures to access data in the storage bucket. So unlikely you'll find a single example that works for every provider. IRIS External Table contains Object Script implementation of the storage bucket adapters for AWS, Azure and Google Cloud. https://github.com/intersystems-community/IRIS-ExternalTable#using-cloud-adapters-outside-of-externaltable - would give you an idea on how to use adapters directly.
go to post Anton Umnikov · Apr 16, 2020 Open Source IRIS AWS CloudWatch integration https://openexchange.intersystems.com/package/CloudWatch-IRIS use the same MONITOR REST API, along with messages.log (former cconsole.log) as a data source.
go to post Anton Umnikov · Oct 18, 2019 Check out: https://github.com/intersystems-community/irisdemo-demo-appointmentsms/tree/master/appointmentsms-iris-atelier-project/AWS
go to post Anton Umnikov · May 6, 2019 "Widely" might be an overstatement for this particular discussion. Nor it equates it to any "Guidelines", official or de facto.In Atelier, if I migrate the code, originally written in Studio (or any other code, already residing on a server) it ends up in a predefined location which is not src
go to post Anton Umnikov · May 6, 2019 Funny thing that this repo is not following guidelines Evgeny referring to :)
go to post Anton Umnikov · May 6, 2019 Hmm... that document says nothing about how source code needs to be packaged for GitHub repos. And that's the part video refers to. What am I missing?
go to post Anton Umnikov · May 6, 2019 Where can I find these Code Guidelines, you are referring to at ~4:45?I am using Atelier and it doesn't put Classes and Routines under the src folder.Thanks!
