A recording of the event and the next steps to start your contributions can be found here:
Customer Contributions to Knowledge Presentation
Let's get started!
Today we are pleased to announce another community release for docker support (version 3). As part of this enhancement now applying the patch and upgrade from a previously created container using Docker Orchestration scripts provided by OpenText for TeamSite, LiveSite, and OpenDeploy. We support 16.2 and 16.3 containerization using provided automation scripts. This release marks our third release of docker support for TeamSite, LiveSite, and OpenDeploy.
Please join us on this journey and 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 or Product>OTDN>Web Content Management (TeamSite)>TeamSite, LiveSite, OpenDeploy> Docker Automation>16.2.”
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?