-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Community Call on Docker, Kubernetes and more: collecting interested people #5373
Comments
Mentioning people I know that might be interested: (merged into the list below) More names (src). Please: if you are mentioned here but not interested, either hit "Unsubscribe" and/or leave a note. Generally interested@pdurbin Primarily interested in production usage@4tikhonov Primarily interested in development usageInterest in both dev and prod usage@donsizemore Unknown...@aculich |
I'm interested for development if not production. My beard turns greyer each day... |
Hey @mercecrosas, @djbrooke and @sbarbosadataverse, may I ask you to retweet my post to reach more people out there? Thanks! 😸 |
I'm interested for development/testing |
We're deploying multilingual DataverseEU instance on Google Cloud (demo server) and ready to share our experience with deployment on Kubernetes: |
I am interested too. |
Dear community, thank you for your interest on the topic of running Dataverse in Docker and/or Kubernetes. To have some kind of agenda to talk about in a call, I ask everybody to add comments and/or suggestions to https://docs.google.com/document/d/13h4zra_ugYH5IKMkj5tya1NwaFdC2FfWXBmGUxxAdn8, including your nick/name. I am eager to setup a poll for a timeslot for a call, but there is a chance that we could use next weeks community call and stay a little longer (if it takes place because of holidays). Please share your preferences if this doesn't fit. Cheers! |
This morning @djbrooke and I spoke about next week's community call on December 18th and we do plan to have it. (For anyone reading this who is unfamiliar with our community calls, please see https://dataverse.org/community-calls .) We like your idea of having those interested in discussing this issue to stay a little longer on the call. @poikilotherm please keep us posted on if you'll be sending a poll or using a community call. We appreciate all the organizational legwork you've done already! |
Hi all, I would love to attend but I have a final exam on the 18th and I would not be able to attend |
I don't have the bandwidth to add another project right now, sorry @poikilotherm ! |
Then let's just reuse an extension of the regular community call for now (anybody interested should just hangout longer). Depending on the echo from it maybe a separate call can be setup for next year... 😉 |
Happy New Year everyone 😄 The discussion from the call is logged here: https://docs.google.com/document/d/13h4zra_ugYH5IKMkj5tya1NwaFdC2FfWXBmGUxxAdn8/edit To paraphraze: people around in the call primarily seemed interested in production usage of Dataverse on Docker and Kubernetes. Just yesterday @pmauduit was asking on IRC about using it for dev purposes, too. Any feedback you are willing to provide here or in other places is very much appreciated. I would love to hear from you 😄 |
Cleaning up old issues. Since this was initially writen, things are moving in IQSS/dataverse-kubernetes. Please follow up there if you are interested. Closing this. |
Dear Dataverse users, sysadmins, devs, devops and anybody else,
from the community call on 12/4/2018 I got the impression that a follow up meeting on this topic might be a good idea.
If you are interested in using Dataverse on Docker and/or Kubernetes in production systems or during development, let's get in touch and talk. Community power! 💪
Please leave your feedback below and feel free to @mention more people you think that might be interested. On 12/12/2018 I will try to come up with a timeslot poll for all interested parties. And yes: timezones timezones timezones!
Please spread the word! 😄
The text was updated successfully, but these errors were encountered: