Hi,   I am not sure if I understand what is your purpose for this question... or if the idea of how Model Manager works.   The idea is that you will register and publish your models in the shape of a SAS Container (SCR), as it is a closed docker container that affects nothing and you can run it alongside other models (even similar models), without issues and you can score those models to pick and choose the best one and to improve them.   You need to bring your "files" to Model Manager so your model will be able to be included in the SAS Container and be able to be published and run and be scored.   In this sense, then, and if you don't load the model itself, what do you want to load exactly? How will it be scored?   Leaving all of those thoughts aside, you know you can query other sources, right? In that sense, you could query the contents of a blob, as example, and bring that data into files to the model. Again, a bit twisted, but the best attempt to answer to your question.   https://documentation.sas.com/doc/en/mascrtcdc/v_029/mascrtag/n15q5afwsfkjl5n1cfvcn7xz4x22.htm ... View more

Thanks @neetschase . I notice now the message "missing port in address" in your logs. Wondering if there is any port definition that is missing somewhere?   Also, I wonder if you check the configuration changes when there a new version of SAS Viya in the "What's new in Operations" guide. Could you please check: https://go.documentation.sas.com/doc/en/itopscdc/v_045/itopswn/n1s87rn4lff99wn16hodkkloq4zl.htm  https://go.documentation.sas.com/doc/en/itopscdc/v_045/itopswn/n1s87rn4lff99wn16hodkkloq4zl.htm#n00vrfgrsbh346n1g6scvhaw5nnq $deploy/sas-bases/docs/configure_connection_settings_for_sas_model_risk_management.htm $deploy/sas-bases/examples/sas-risk-cirrus-mrm/resources/README.md $deploy/sas-bases/docs/preparing_and_configuring_risk_cirrus_core_for_deployment.htm   Maybe check if the backup has a good definition for sas-risk-cirrus-core.   When everything else fails, I suggest to reach out to SAS Tech Support.   ... View more

@ahmedaldorr , have you got the chance to reach out to your SAS Tech Support, as advised in your query here? https://communities.sas.com/t5/Administration-and-Deployment/Compute-session-resetting-while-working-SAS-Studio-in-SAS-Viya-4/m-p/952417  ... View more

Hi there,   while the message seems to point to a specific aspect of the backup (consequence), the message might indicate that the actual issue is some kind of timeout.   Could you please check if this works for you?   https://communities.sas.com/t5/Administration-and-Deployment/backup-purge-job-fails/m-p/950777   I see more folks are having issues with backups with the latest update of Viya. ... View more

Nice one, and thanks @StuartRogers , as I saw more and more folks asking for the integration with Keycloak. Appreciated! ... View more

Hi @Ahmed_Dhaoui ,   I have not worked with it yet directly, but I can say that, in theory, it should work for as long as you keep attention to some details.   For as long as you implement High Availability, it should work fine: https://aws.amazon.com/blogs/apn/high-availability-and-observability-using-red-hat-advanced-cluster-management-for-kubernetes/   The idea is similar to Kubernetes Kosmos released by Scaleway or other solutions: https://www.scaleway.com/en/kubernetes-kosmos/   In short, you will have a split design of 1 K8s cluster for control, administration and load balancing of your different clusters, and then you have your separate clusters and namespaces. So in this sense, that technology will take care of all for you.   I mentioned there are some details to keep in mind, and it all falls down to the backups, state of storage/memory and what is synchronized between the different kinds and locations of storage on the clusters. The images/containers/namespaces should be replicated just fine. But the Persistent Volumes (local & Shared Storages) will need to ensure: 1- all memory data to be frequently backup (SAS Backup) 2- run periodically data integrity checks to ensure no broken or locked files and all files been properly synchronized across all storages   Little disclaimer here: Please do keep in mind that for as long as it has not been tested by SAS Institute and not documented, it will be not officially supported as such. ... View more

This is an excellent question. A lot of folks/companies are having the same question.   The answer is exactly as @SASKiwi indicated.    Plenty of people are having that question even with what is documented in the policies of SAS Support, so I think the following will help everyone.   The FANS team in the Nordics have just made a presentation about it. Please do check the slide deck 1_SAS Release Update.pdf, in the following link! https://communities.sas.com/t5/SAS-Community-Nordic/FANS-nettverksm%C3%B8te-Generative-AI-nettverksm%C3%B8te-23-10-2024-Oslo/m-p/930402/thread-id/470       Please don't be afraid that the link and content are not in English - the slide deck is and it is actually really clear.   One last thing: those maintenances will be out of Standard Support, but still be covered by Limited Support. Something to keep in mind. ... View more

Hi @narfaoui ,   it is all indeed as @ChrisHemedinger explained.   Always when you add (virtualization) layers, you are placing an overhead of some degree: with virtual machines, with containers, cloud instances, etc.   The question is how much is significant and acceptable for your processes. For instance, all virtualization methods mentioned above are generally accepted nowadays - yet do mind that the penalty on performance still happens. The question is how much noticeable is, overall.   The only way to know is by having a good analysis of your workloads (SAS & non SAS) intended on those servers, and by aligning with an specialized representative from vendor or partner, whose most likely will ask you to expand on your information.     ... View more

Hi @paul-blu,   the number of reasons for this might be multiple. You could only get more information looking further in the logs. First of all, I would try the deployment at a different day/time. Azure workloads can make big differences when you are running a deployment - remember, it is all shared resources in most cases.   Second, if that would not work, I would try a different version of SAS. Maybe try with 2024.08 (24.08.01), or even better, the really newest ones: Stable 2024.11, Stable 2024.10 or LTS 2024.09 (which I guess it might be the one you tried but on Stable version?).   If nothing of this works, the best is to reach out to Tech Support.   Ps. Please do note that Azure is changing some requirements this month too. The last things I heard is about the Kubernetes version and the SKU type for public IP addresses. I don't think this would affect a deployment so early, but it is surely to keep in mind for the coming few months. If you have a subscription, you might have received the emails from Microsoft already with the notification. ... View more

I am not an SMTP server and probably it will depend on what kind of server you have and such. You can try wait to see if anyone can help you, but I personally would not keep my hopes up Witt that choice. If I would be you, I would reach out to your SMTP admins or your vendor tech support. Or chatGPT! ... View more

Hi @kumarsandip975 ,   there is no restriction as such in SAS. However you can customize as much as you want from the mail server point of view with rely lists and rules. ... View more

Hi @kumarsandip975 ,   while it is listed as a requirement (I would say reasons are obvious, but I will describe after), SMTP is not required as such. You can leave blank or put dummy values. You will be able to complete your installation. I think this answers the main question   About your secondary question, why is it needed: When you deploy SAS metadata, it is to send any kind of alert from the system. When you deploy the middle-tier, for the same reason, because Apache "needs" it.   But, perhaps, the main and actual reason do put proper data from the beginning, is because you want your SAS installation to set all up, at least to a basic level. If you don't, you can still add or change later, however the manual process might not update all where it is needed or not properly always.    Hope it makes sense ... View more

Good one! ... View more

I will leave aside for now SAS Model Manager, as this would require some training, but please do feel free to check other articles in the communities or videos in Youtube. I will focus on SAS Connect.   In the documentation, you can find: https://documentation.sas.com/doc/en/pgmsascdc/v_056/viyaconnref/n0ib6u4iq5qgb6n18fjian12gove.htm On the menu on the left you can find examples too.   Your idea might work. I think if you combine that idea with the rsubmit from SAS Studio, it would answer your needs, as it allows to include SAS code within SAS code, that would be launched separately. ... View more

Hi there @MMar , nice question.   Traditionally speaking, while not the most beautiful version, it works nicely: with SAS Connect sessions you can manage asynchronous and parallel sessions. In Viya 4, if you would have Model Manager, you could launch programs in separate pods (models) and define the order or synchronicity from a much more elegant and production-like manner, although it has the cost of using SAS Model Manager and infrastructure for publishing the models as pods.  ... View more