Containers is Linux, even on Azure ;-)
Azure Container Instances
101–110 of 117 posts
Re: Azure Container Instances
#102If this works as advertised, it's awesome. It's like AWS lambda, without language restrictions, CPU or RAM throttling, etc. Truly serverless
This is only like AWS Lamda if a response time of a few seconds is acceptable to you. That's the time it takes to start up an instance according to the article.
FYI - AWS Lambda cold start times are also in the seconds [1]. I'm assuming Azure functions has the same limitation. After all, code has to be retrieved from storage over the network, environment set-up, and eventually, code needs to be run. This is a limitation of physics rather than software.
Re: Azure Container Instances
#103Earlier quoted context omitted.
Founder kicks in. The vision is to merge PaaS into IaaS, e.g. a microservice-native cloud. I want to ask more details of the upper-layer features you imagine. Thanks!
For small teams like the one I work in, and for solo work I have dabbled a bit in, I can imagine the following thought process if I have a git repo and sit down to think about how to best deploy it. - I start researching how to deploy this, but I don't care about optimizing for a lot of scale. I DO care a lot about iteration speed, integration with image registry + code repository + CI/testing services (ideally out o…
Thanks for the detailed input. They are tremendously valuable.
Part of the reason we chose to open source is that we want the community to innovate. We are continuing to build the feature set, however I need to say that the workflow varies from app to app. Therefore, by providing the base building block and allowing others to create different solutions, we could enable more options to the market.
Re: Azure Container Instances
#104I don't see why you need a container for your cloud instances. Puppet/Chef/Ansible are all much better solutions.
I built an internal tool where teammates submit some details and a fairly computationally heavy data processing task run and posts the summarised results back to a slack channel.
I use containers for this, because it's a really easy way to really quickly get access to compute instances (which vary in size from like 4gb ram to 100gb+ of ram depending on what the user submitted) really quickly and for really cheaply because I only pay for the time it actually runs, rather than renting out an EC2/VM instance all the time (which would either be underpowered, or end up costing too much), or build some frankenstein-ian thing to dynamically provision and spin up EC2 instances on demand, set them up and then shut them down/terminate them once they finish.
Re: Azure Container Instances
#105What's really got me excited lately is the combination of Ansible (for dirty work) and container orchestration systems like Kubernetes/Rancher/etc (also, tools that go from one orchestrated host to many like dokku and flynn). While I appreciate the competition from GCE and Azure, what I really want is a tool that will run in any one of their clouds, but offers the same ease-of-management, and lets me go from one clou…
This is part of the vision that we have with CoreOS Tectonic. Checkout the Tectonic Installer which helps to install to various cloud platforms[1] using Terraform and then Tectonic[2] helps to automate operational toil like upgrades, etc. [1] https://github.com/coreos/tectonic-installer [2] https://coreos.com/tectonic
Just a heads up -- some parts of the coreos site really make it seem like tectonic is only for enterprise -- it actually turned me off it while I was reading the documentation at https://coreos.com/kubernetes/docs/latest/
Right now my plan is to start with bare kubernetes just to cement understanding and then add rancher, before looking at any other higher level system (I mean there's stuff like helm out there, but it just seems to be too many levels above the ground for me at this point). I'm also using ansible right now (and relatively new to that too, but it's basically just fabric on steroids so I'm not too stressed about it), so I haven't started using terraform yet (but want to).
Re: Azure Container Instances
#106What's really got me excited lately is the combination of Ansible (for dirty work) and container orchestration systems like Kubernetes/Rancher/etc (also, tools that go from one orchestrated host to many like dokku and flynn). While I appreciate the competition from GCE and Azure, what I really want is a tool that will run in any one of their clouds, but offers the same ease-of-management, and lets me go from one clou…
> Terraform is basically this tool, but I want an even easier interface, terraform still feels somewhat too specific to me -- I don't want to even have to write config or specify some "aws" adapter that will make my config work on some provider. I want instant, multi-cloud (possibly) heroku, using only the network, hard-drive-space, ram, and lxc "primitives". This sounds very similar to some ideas I've been stewing o…
tl;dr - "Fullstack" developer who does my own ops for my own projects which are very varied (I've done small-time deploys/management for projects in/with python, node, go, haskell, ruby, postgres, rethinkdb). I try to iterate my infra as well as my technology stacks to find the best way to do things.
Sorry for the delay -- I've definitely had this at the back of my mind too, but with every advance made by cloud providers, I wonder if I could ever possibly get into that fight, especially since I'm not an expert at any of the cloud computing platforms -- Hashicorp seems to be doing amazing work in this area also, field seems to be full.
My background is basically that I really enjoy computers/programming and like to be self sufficient so I prefer a shallow (working) knowledge of all parts of the stack. I maintain a few VPSes and use them to host n-tier (where n is usually 2) projects. I'm always interested in the best way to do stuff and I use new projects to try stuff out.
Ops is particularly interesting to me because I've gone through a lot of iterations of how I did ops for my apps -- from SSH-in-and-do-stuff -> use-fabric-to-ssh-in-and-do-stuff -> dockerize & ship containers -> dockerized + systemd -> dockerize & registry (thanks to gitlab) + systemd + ansible. I've also used dokku and of course it blew my mind (I never used/wanted to pay for heroku), so while I stayed relatively low level, I was cognizant of what was happening a few levels up.
I saw kubernetes a few years ago and wasn't sure whether I wanted to go with it, but I've taken a fresh look over the last week and think it might be time to give it a try.
Side (controversial?) note - I think the time where it's acceptable for junior/mid-level developers to only know one part of the stack is dead. The only thing keeping these roles possible are the fungibility requirements for large corporations. Smaller, hungrier (almost literally) corporations can't afford to have some developer that is only an expert at writing python but never works on frontend code or deals with the database.
Re: Azure Container Instances
#107What's really got me excited lately is the combination of Ansible (for dirty work) and container orchestration systems like Kubernetes/Rancher/etc (also, tools that go from one orchestrated host to many like dokku and flynn). While I appreciate the competition from GCE and Azure, what I really want is a tool that will run in any one of their clouds, but offers the same ease-of-management, and lets me go from one clou…
Hey @hardwaresofton check out Cloud 66 https://www.cloud66.com/containers - Caveat... I work there :)
Hey thanks for the link! However I don't think Cloud66 is for me -- out of my price range for the small projects I build.
With respect, from what I can tell, most of the features of cloud66 are already included in Gitlab, and when I convert my current infrastructure to Kubernetes I can even start taking advantage of the auto-deploy-to-kubernetes features.
$49 / Month is a bit too much for me, but I don't think I'm the target anyway!
I'm also the kind that likes to run my own infrastructure and spend time on things I maybe shouldn't be spending time on :)
Re: Azure Container Instances
#108Does anyone know what service discovery, network security policy and ability to add multiple redundant copies of the same service this offers? I'm guessing it's powered heavily by kubernetes, so maybe that answers the question, but I'd be interested to know more about the details.
We have an open source project for this: github.com/hyperhq/hypernetes. Basically use k8s to schedule hypervisor-based secure containers.
Re: Azure Container Instances
#109Earlier quoted context omitted.
For small teams like the one I work in, and for solo work I have dabbled a bit in, I can imagine the following thought process if I have a git repo and sit down to think about how to best deploy it. - I start researching how to deploy this, but I don't care about optimizing for a lot of scale. I DO care a lot about iteration speed, integration with image registry + code repository + CI/testing services (ideally out o…
Thanks for the detailed input. They are tremendously valuable. Part of the reason we chose to open source is that we want the community to innovate. We are continuing to build the feature set, however I need to say that the workflow varies from app to app. Therefore, by providing the base building block and allowing others to create different solutions, we could enable more options to the market.
Yeah that makes sense. If there's enough of an enticement to adopt the infra service and you standardize the API at the bottom, any developments/contributions on top of it could co-exist and be more share-able. I'm reminded of the addon marketplace in Heroku. The underlying infra was consistent and general, which made third party plugins/addons/contributions easier (even to make money). Heroku ended up getting a lot of specialized support for platform customers that they probably couldn't have built out themselves.
I could totally see even seeding a possible 'marketplace' with your own services. Like perhaps Func as a service, powered by Hyper. And others also benefiting from the underlying infra being so simple. Why wouldn't a platform-provider use an infra service that's flexibly scalable on perf+price? They probably have the skillset on hand for that too and don't need any more finesse than already exists, beyond stability.
Anyway, that's just my own ramblings. Hope you're having fun with Hyper! It sure looks like a lot of love/tears went into it.
Re: Azure Container Instances
#110Pretty awesome this can be done in one command. At Kyso we deploy a lot of data-science images to GCP, it can be tricky. Is the API support for this coming?
API support is already there. The docs/SDKs need to be updated, but there are some examples here: https://github.com/Azure/aci-connector-k8s/blob/master/synch... https://github.com/Azure/aci-connector-k8s/blob/master/aci.t... Docs/SDK updates should roll out in the next 1-2 weeks.
The swagger spec for the preview API is here:
https://github.com/Azure/azure-rest-api-specs/tree/current/s...
Please send us feedback.