Interesting article, only one thing was not so clear to me. At this moment I have only workload orchestrator pod and compute server on compute node. why is it handy to schedule all this pods below on compute node?
sas-compute-job-config-require-compute-label.yaml
sas-batch-pod-template-require-compute-label.yaml
sas-launcher-job-config-require-compute-label.yaml
sas-connect-pod-template-require-compute-label.yaml
... View more
hello @Wilbram-SAS , I have followed your workshop and have successfully established connection with Viya 4. I am now able to see the SAS 9.4 folders from Viya in the left panel of EG and also my mounted path in Viya. However when assigning caslibs they are not visible in the left panel. Is this correct or am I missing something? regards Karolina T
... View more
@NicolasRobert hello Nicolas, thank you for checking. We have just updated to version 2024.04. Our users have put the libraries in different tab Resources, and then you cannot start the compute session.
... View more
Thank you for this article. If adding more compute nodes, for example for SAS Studio, is it correct that you need more cores than memory? We are reconfiguring our resources in order to use SWO. Pls advise if possible the dependencies between CPU and memory or provide a link.
... View more
@NicolasRobert Thank you for providing clarity on this topic. I have a question: we have defined domains for oracle databases schemas. When we add such oracle database library to the compute context, then users who are not in the domain are not able to start the compute session in SAS Studio at all. Is this how the context supposed to work? We thought it will load the compute session without the library. We have added this library to the autoexec of the compute server. Then we have no problems and users can start compute session without this library if they have no permission for it. regards Karolina
... View more
Thank you very much for your answer and sharing of best practice. I see that actually batch server is suited perfectly for this. We have not used it yet. We were scheduling jobs in Jobs&Flows in SAS Environment Manager through the SAS Job Execution. However, there you cannot restart jobs easily, at least to my knowledge. Is it right that we should move from scheduling jobs in SAS Job Execution to scheduling in CLI through batch server in order to have the full functionality of SWO?
... View more
@FrederikV We would like to start to use SAS Workload Orchestrator but there is one question preventing it. We are not going to use preemption yet as you have program jobs in order for them to restart. We would like to schedule priority jobs however the other less important jobs are failing because they are too long in a pending state. What is best practice if you want these less important jobs to keep on running as well? Is extending the default time-out of compute session the best practice or are there another solutions? Is it possible to advise as we are eager to use these feature very soon.
... View more
@EdoardoRiva As we do not have experience yet with SAS Workload Orchestrator, we would like to know what the best practice is. We are not going to use preemption yet as you have to find out how to program jobs to restart. So if we schedule priority jobs and the other less important jobs fail because they are too long in a pending state, what is best practice if you want these less important jobs to run as well? Is extending the default time-out of compute session the best practice or are there another solutions? Is it possible to advise as we are eager to use these feature very soon.
... View more
@GillesChrzaszcz
As we do not have experience yet with SAs Workload Orchestrator, we would like to know what the best practice is. We are not going to use preemption yet as you have to find out how to program jobs to restart. So if we schedule priority jobs and the other less important jobs fail because they are too long in a pending state, what is best practice if you want these less important jobs to run as well? Is extending the default time-out of compute session the best practice of are there another solutions? Pls advise as we are eager to use these feature.
... View more
thank you very much Frederik, it seems that for batch jobs you can see the name of the job, but for jobs from SAS Studio submitted via Job Execution not. We can now stop searching how to change it, as SWO works like this. Thanks again.
... View more
@FrederikV thank you very much for this great explanation. I will try to make such a test with batch jobs as well. One thing, we would like to have the possibility to see the job name as it is cumbersome to identify jobs if the same user runs many of them. At this moment we have in workload orchestrator dashboard, the ID, Name and Pod name.
2778 sas-compute-server-a779372b-d810-490e-a9a4-d67d7bdadd3a sas-compute-server-a779372b-d810-490e-a9a4-d67d7bdadd3a-2778
What can be adjusted/configured to have a name of the job? thank you Karolina
... View more
