As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
I have a production server and a test server in a local network, and I want to deploy Alfresco 6 (ACS) in production in the production server and in test-dev environment in the server tests, but all is in local network no cloud.
anyone can help!
You can visit Deploying | Alfresco Documentation for the deployment.
Regards,
Kintu
ContCentric
thanks for your answer, but i found that docker-compose is not for
production, and that kubernities is for clustered machines (cloud),
should i use docker for local deployment then I use zip distributions
for Alfresco 6?
On Mon, Feb 18, 2019 at 3:06 PM kintu.barot@contcentric.com <
Why do you say Docker Compose is not for production?
... using Docker Compose. This deployment method is only supported for development and test environments from Deploying using Docker Compose | Alfresco Documentation
The compose file provided in acs-deployment is not supported for production without some hardenimg effort. Like Jeff, I would doubt there is a strict ban on using compose itself. Worth creating a support ticket to confirm.
Jeff, if I remember correctly GovRAMP does not allow Docker deployments without a specific exception being approved. In which case you can likely get an exception for K8s as well. Then use something like kop to deploy and manage your own K8s cluster.
My understanding to date is that it is not straight forward to maintain and secure a production K8s cluster. Guidance I’ve had is that customers should have strong in house K8s resources before attempting to deploy production systems on it.
I actually filed a ticket with support for one of my customers who had this same question. Support's response was basically that customers are going to run Alfresco in a variety of ways and they aren't going to refuse to support a customer based on their deployment option. If an issue cannot be reproduced using K8s, though, then it may be up to the customer to prove the issue isn't due to how they've deployed.
Support also said that they have not done any performance testing using Docker Compose.
Hello Jeff,
I am a paid customer and I am facing the same problem. After I worked with the support to fully install our customized Alfresco solution to AWS EKS (EFS) we faced an issue to upgrade the installation using K8s (Helm update). Support couldn't help me and answer my question for weeks (They told me they need to ask) then they closed the case.
We did our development and test using containers and right now we don't know how to proceed for our SaaS production service using Alfresco
I feel Alfresco is lost on this topic especially when we can read from the documentation:
“Alfresco Content Services is designed to be deployed using Docker images that are packaged in Helm charts (as a reference or basis for production deployments), or Docker Compose (for test and development environments only); there is no GUI installer.”
So no docker (as per the documentation) and no K8s (as per my installation with the support)
Is zip the only solution? The problem is that we saw our solution working well using K8s on AWS EKS until we tried to upgrade
Any comment will be appreciated
Thanks
Jamil, were you able to come up with a solution?
Jeff, I got an official email from Alfresco to confirm that only zip deployment is the solution.
Too frustrating... we will not do the deployment using zip method...our container images are ready
The following is from Alfresco University about the deployment methods:
(zip) "This method is suitable for those organizations that are not yet ready to move to a containerized deployment approach for Alfresco Content Services"
We are ready and we paid and did the full steps as explained on AWS EKS but it seems Alfresco is not ready!!!
__________
Good afternoon,
Following internal discussions, Alfresco recommends that you install Version 6 to run into production using distribution zip. Without the necessary helm knowledge and Kubernetes/EKS understanding on your side, we would not recommend using this deployment method in production until sufficient expertise is obtained.
Per Alfresco’s statement on github, https://github.com/Alfresco/acs-deployment
“Production environments:
Alfresco provides tested Helm charts as a “deployment template” for customers who want to take advantage of the container orchestration benefits of Kubernetes. These Helm charts are undergoingcontinual development and improvement, and should not be used “as is” for your production environments, but should help you save time and effort deploying Alfresco Content Services for your organisation.”
The Alfresco Documentation site provides guidelines on how to go about deploying Alfresco 6.0 using distribution zip:
I sincerely regret the frustration that you’ve been experiencing but I’m also keen to be as straightforward as possible and offer a solution that enables you to spin up Alfresco with HA/Clustering enabled as quickly as possible so that you start to see the return in your investment.
Please let us know how you would like to proceed.
