Watch this Ask the Expert session to learn the benefits of project containers and how to create and run them using SAS Event Stream Processing clients. You’ll see how containerized models simplify the promotion and lifecycle management of event stream processing models.
You will:
The questions from the Q&A segment held at the end of the webinar are listed below and the slides from the webinar are attached.
Q&A
Can I access the container images created in one environment from another environment?
Technically, yes, it's just a standard container. The images are pushed to a container registry and can be accessed within ESM or directly if there are no network restrictions and the correct credentials are available.
Is ESP Project containers supported in both Viya and Standalone ESP deployment?
Yes. This feature is available in both the deployments
How can it simplify deployment, integration, promotion and lifecycle management of ESP models?
The software, the project, the artifacts and basically anything needed to successfully run a project is inside the project container. So, you don't need any shared folder or PV between all different customer environments like QA, UAT, Production etc. Because of the immutable nature of containers, there is no risk to have someone touching the model file between test and production and corrupt the project. If a single artifact changes then it is a new version, so it a new container will be produced. We're bringing simplicity for deployment as well as using standard docker image that can easily integrate with customer’s existing CI/CD pipeline and promotional workflows. No additional software or artifacts to manage. In that respect, this simplifies the whole model life cycle.
Can ESP project containers run on standalone docker engines?
Yes, it is OCI compliant and can be run in standalone docker engines.
What is the difference between project containers and ESP Edge? Which one do you suggest?
The ESP server on cloud and edge uses the same exact software. The only difference is in the way it is shipped which makes it easier to install it and run it on the bare OS. Here one needs to set up the operating system, install the software, and then also have a process to manage and run project. But with project containers, one simply needs to deploy and run it. No need to configure/ manage anything extra as container has everything it needs. ESP Edge is probably going to be legacy, not from a technical point of view, but container is more modern and flexible. In Edge, the customizations like adding specific drivers and operating system are possible. You can do the same on the container. Even devices with NVIDIA etc. can run containers. But with the simple life cycle/ deployment management/ upgrade etc. container is recommended in most cases.
Can project containers help to save cost in running ESP projects?
Yes. You don't need all the platform or even any additional UI apps. You don't need the full ESP server components. You just have a container with a smaller footprint as it only contains the necessary software dependencies. So, in terms of simpler infrastructure and process management lot of time and money is saved.
Recommended Resources
Project Containers Documentation
Please see additional resources in the attached slide deck.
Want more tips? Be sure to subscribe to the Ask the Expert board to receive follow up Q&A, slides and recordings from other SAS Ask the Expert webinars.
Calling all data scientists and open-source enthusiasts! Want to solve real problems that impact your company or the world? Register to hack by August 31st!
Ready to level-up your skills? Choose your own adventure.
Your Home for Learning SAS
SAS Academic Software
SAS Learning Report Newsletter
SAS Tech Report Newsletter