Connecting Cloud Innovators: Building Community at .NEXT 2024
Thanks for the followup. For those just finding this thread We have implemented this in our corp services division and leverage it in conjunction with Docker + Nomad to provide a complete container solution that runs very well. Essentially we can declare the storage requirements in our nomad storage stanza, and the requested volume will be mounted if present, and created if missing. We then use the data protection feature to snapshot the data volumes so that we have a complete backup solution that works with containers. Pretty elegant all in all!
To be clear, nomad is our orchestration/scheduling system. We send it jobs, and it figures out the target computer, ensures the container is healthy and stays running, and handles canary. blue/green updates, etc. We are abosolutely NOT running without orchestration, and I'd like to make clear that I'd never recomend anyone do that beyond simple container testing.But I think your question may be more about why the hashi-tools vs a pre-bundled system like kubernetes/swarm/mesos? Well the answer is a good mental excersize for me, so buckle in :)Why Not Kubernetes?So this one has some very company specific history and needs that color this descision so I'll try to be transparent.When I started at this current company, Kubernetes was the incumbant. We had already deployed it in numerous locations multiple times. Remember that Kubernetes was(is) young at that time, I think we were using 1.2. It wasn't until after nearly a full year of failures we completely abandoned not just k8s, but _all_
Update: it seems this UPN restriction extends ot the service acocunts as well: I had ot update the service account to be a complete upn then things apparently kicked in.
"mature" is a relative term :) I think what were are doing is fairly mature compared to some, but as I'm still in the thick of things I feel like I have a long way to go still :)The blue green model you mention is a goal right now. We are hoping terraform will help us deliver that by allowing use to stand up the new farm (blue) then leverage nomad to drain/move containers and flip things over. But ... it's pure theory craft atm :)I'm upgrading to 5.5 now and have been working with Nutanix folks on getting the Nutanix terraform plugin so we can start really testing this, then we'll see how mature things are.The other big part of this is packer. RIght now we run packer in VM that has qemu installed (nested virutalization) then copy the resulting image to Nutanix using a script that logs into a CVM ... so I'm hoping to "borrow" some of the work you guys did getting a terraform module working and apply it to packer so that pain is alleviated as well :). But that's also ... well ... ph
This is one that's near and dear to my heart .... or at least to my buisness as we are container centric here. To restate the core question: "Should containers be treated differently, or do system administrator need to know when to deploy containers?" The TLDR version to this question is: [i]In order to recieve a benefit, containers need to be managed in a completely unique method when compared to traditional VMs.[/i] Schedulers, service discovery, and logging become mandetory baselines to a succesful container strategy, and even things as simple as backups need to be rethought to accomidate.We personally have embraced the Hashicorp tools over some of the more popular choices (kubernetes) to help deliver this vision:Packer allows us to build container hosts. It's set on a cronjob to rebuild an image once a month so that patching is always up-to-date. This is probably the most "traditional" tool in our arsenal.Nomad is a scheduler that we plug into our CI to actually deliver con
NVM ... i clicked a 2nd time and it opened fine .... browser woes! However, I did notice that this looks to be redhat tested only. Is there a Ubuntu version of this? Do we know if there is one in the works?In my company we are heavy docker users, but we use Ubuntu as the base, so it would be wonderful to try that.
DO we have a timeline for 5.0.2?I ask as I opened the ticket back in 5.0.0, was told it was identified, then my ticket was closed during 5.0.0.1, and now in 5.0.1 it's still not resolved ao was checking in to see if it "was just me".
Actually going through this process myself right now, but the sheer numberof manual clicks here is madening. So I've fallen back on Puppet.[url=https://github.com/justin-dynamicd/val-puppet/]https://github.com/justin-dynamicd/val-puppet/[/url] This module is a fork of one provided on the veeam site, and lets me configure linux boxes (centos/ubuntu) to download, install, and configure the backup desitnation adn schedule centrally from the puppet manifest. Ill be doing similar for a DSC based module for Windows next, but the shortterm work was more than worth getting centralized control and automatic installation on any box (jsut install the puppet agent on your image and it gets pushed on first run).Hope this helps others.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.