search

esmero / archipelago-deployment-live

A Cloud / Local production ready Archipelago Deployment using Docker / Kubernetes
GNU General Public License v3.0
3 stars 13 forks source link

Kubernetes v/s compose-cli #3

Open DiegoPino opened 3 years ago

DiegoPino commented 3 years ago

This is an easy one:

We will provide both options:

native kubernetes deployment and also https://github.com/docker/compose-cli since we want to support native containerized deployments on both AWS and Azure

But wanted to have your thoughts @dmer @giancarlobi

e.g for CLI and Azure we will go this route https://github.com/karolz-ms/actions-composecli-demo

dmer commented 3 years ago

Excellent! I know our devops folks are trying to move us in Kubernetes direction so if this is already in place that will help our timeline for sure. We've discussed looking at the Amazon Elastic Container Service, but that might be a bit further off.

noahwsmith commented 3 years ago

I'd be happy with any sort of native container deployment to AWS for our initial project. Azure isn't a priority for us, but I appreciate that you want to support both.

DiegoPino commented 3 years ago

Thanks. We already have Azure users and the service is actually simpler/cheaper to deploy than on AWS (so far) so we will go for both. Probably the main difference/question will be if we go for a static/configured container for main web or we keep our deployment which includes initial building. The main issue I see with the full Cloud ensemble is that containers become mostly monolithic, so adding after the fact new modules, etc and keeping track of that becomes more complex. Anyhow, still some work to do, will let you all know when we are ready

Hugs

dmer commented 3 years ago

@DiegoPino we're doing a little planning ahead for deployment and have a couple more questions about this repo - hope this is a fine place to put them! What is your current timeline for Kubernetes deployment? We're going to start work on deployment in about a month and will probably go the docker-compose route with github actions for the CI tools - unless Kubernetes is ready - we'd rather go that route since we're hoping to move ISLE deploys in that direction as well. Additionally we wanted to know if/what you have been thinking about logging - specifically the AWS logging services that we might feed logs to for management and access.

DiegoPino commented 3 years ago

@dmer Kubernetes deployment (sharing here) is planned for first week of March with RC2. Main use case for us is still Azure and our projects in that realm start then. There is a secondary need which is clustering IIIF image servers for high performance round-robin load balancing but Kubernetes also adds a lot of overhead to our storage config and deployment planning and we will not only need testing (still nice) but contributions in case things do not work as expected. Do you already have IT staff able to manage a Kubernetes production cluster? We don't (means I'm training myself) AWS logging. I would recommend for that a totally different ISSUE. We talk there what you mean with AWS logging services and which of the too many logs a system like these you want to push into that real. E.g we have https://github.com/esmero/archipelago-deployment/issues/86 for service level background logs that can replace any Drupal internal logs with a infinite set of possible plugins https://aws.amazon.com/blogs/developer/php-application-logging-with-amazon-cloudwatch-logs-and-monolog/

noahwsmith commented 3 years ago

"IT Staff" means me, Gavin, Hertzel and Don. We'll figure it out too, but we're heading that way with Islandora so it will be great for us if all our new projects land there.