Today we are pleased to announce docker support for TeamSite, LiveSite, and OpenDeploy version 16.3, about 2 to 3 weeks ago we had released support version 16.2. This release marks our second 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.

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?

Comments

  • The purpose of this release is to support CI/CD in the organization and accelerate development cycles. Yes, the automation does take care of setting up OD base on TeamSite site and OD receiver on LiveSite end. We do support persistent storage for TeamSite and LiveSite so you should be able to stop and start TS or LS without losing your data. Hope this helps clarify.

Sign In or Register to comment.