We invite you to contribute by engaging on a special focus forum: TeamSite, LiveSite, and OpenDeploy - Docker. To obtain the automation for Docker, log in to MySupport, navigate to Product>OTDN>Web Content Management (TeamSite)>TeamSite, LiveSite, OpenDeploy> Docker Automation>16.3.
Why OpenDeploy in the same image as LSDS?
I have read the readme files for building a LSDS container and looked at the docker build files (https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objid=69762670&objaction=browse). Why would OpenDeploy be placed in the LSDS container? Am I correct that by having the OD receiver in the LSDS container, the expectation is TeamSite (OD base) will deploy content to the container and not a persistent storage solution like NFS mount points or a SAN?
My view of containers is they are transient in nature. Container platforms like Kubernetes and OpenShift are set up to spin containers up and down automatically for a variety of reasons. If my assumption above is correct, how can one be confident that when a new container is spun up, all of the proper content is present in the container?