61–70 of 117 posts
This doesn't seem cheap >> £0.001 Core per second That works out at over £2500 for a single core running for a month. And thats without memory costs etc...
That is very likely a display issue and they round up way way too much in that table. In the Pricing Example they use $0.0000125 per Core, which would make it ~33$ for a month for a single core, and double that if you include 1 GB of memory.
Pretty 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?
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.
As far as I understand, with services like AWS ECS you need to provision the infrastructure first and pay for its uptime, whereas this allows more ephemeral containers to be run with minimal setup, and you only pay for the compute time used
Would only be useful for short lived jobs, but a really nice idea none the less.
If this works as advertised, it's awesome. It's like AWS lambda, without language restrictions, CPU or RAM throttling, etc. Truly serverless
What'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…
I hear what you're saying, but don't under-estimate the value of "someone else runs it and gives me an SLA", which is a large part of what public clouds are really selling. :)
Earlier quoted context omitted.
You also incorrectly use "GB-s" in the Core Duration calculation in the Pricing Example: "30 Create Requests * 300 seconds * 1 Core * $0.0000125 / GB-s = $0.1125"
Good catch - thanks.
What'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…
the clear end goal here is that you have to deal with things like 'provisioning virtual disks' and 'doing ubuntu updates'. this whole virtualization thing received you of the burden of buying pci ethernet nics and rack mount brackets and provisioning cooling. but really this whole business of writing chef recipes and provisioning harnesses is really the same kind stuff. it seems important because you can't run withou…
Compare this: http://www.ec2instances.info/?cost_duration=monthly
To VPS hosting from providers like: https://www.packet.net/bare-metal/ https://cc.delimiter.com/cart/dedicatedcore-vps/
The value provided by the services being managed is large, but honestly, for a lot of well-built infrastructure pieces, there is a lot of trust already for the services to not go down. Most startups/lifestyle companies/small businesses/whatever couldn't bring down a Postgres instance on a reasonably-provisioned machine if they tried (and the app is written with at least a smidgen of thought towards performance)
Earlier quoted context omitted.
So what you are saying is the calculation for 1 core, 1GB of memory for 1 month would be: 0.0025 create + (0.0000125 1 core/second + 0.0000125 1GB memory/second) * 86400 seconds/day * 30 days/mo = $64.8025/mo Is that correct? $64.8025 per month is pretty steep for 1 core and 1GB of memory, I guess this is targeted at short-lived jobs.
Yes, the billing is specifically targeted around per-second execution. The containers can start within a few seconds, they allow for customization of CPU cores and memory, and they allow you to focus entirely on your container without having to worry about any VM management. Traditional VM-based infrastructure is still the way to go for long-running applications. This just opens a new avenue into using containers in…
What's nice about this is the directness of it. As far as I understand, with services like AWS ECS you need to provision the infrastructure first and pay for its uptime, whereas this allows more ephemeral containers to be run with minimal setup, and you only pay for the compute time used Would only be useful for short lived jobs, but a really nice idea none the less.
The container security model will almost certainly improve in the future, but for now I'm only ok with other people in my same company sharing the kernel, not incentivised attackers.
[edit]
I'm going to unfud my comment. Some further reading makes me think maybe they spin up something like kvm containers and use a minimal distribution such that they can get to "seconds". If it were me, I'd have pre-running instances of the base image that were ready for a customer to attach and own.
What'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…