6 ms·

Atlas General Availability

68 points by ipedrazas 11y ago

mmcclellan 11y ago
For any of us who have watched this team's output and quality and wondered _Why isn't this team being acquired?_, here is Hashicorp's play. Congrats to team on shipping. It will be interesting to see how all this plays out.
mrdrozdov 11y ago
$40 per node!
- ende 11y ago
  After 10. So more like $40 per 11 nodes, or $3.6
  - arikfr 11y ago
    But if I have 15, then it's $13.3 per node. And at my work place we have >100, which means >$36 per node. That's a lot.
    - ende 11y ago
      Yes it is.
- ipedrazas 11y ago
  thought the same! Pricing seems a bit Atlassian: almost free if you're small, very expensive if you are not.
  - peteretep 11y ago
    That sounds more like Github's Enterprise product, which used to be a cliff of a few thousand bucks to fall off, where private Bitbucket is a $1/user/month. Maybe Github's pricing is less unusual now.
    - BillinghamJ 11y ago
      Github is still incredibly expensive, for both Enterprise and Github.com.
- pquerna 11y ago
  While $40 per node might sound high, I think it is reasonable. I've worked on several products that are priced per node/server. Per-node a difficult proposition -- the price of "per server" of something varies wildly, for example a t1.micro is roughly $9.50 a month, while a m4.4xlarge is $738. $40 on 9.50 seems extreme, but $40 on $738, and Atlas is only a 5% of the cost of your server. But when your target customer is using high end instances, because they are creating more value for their company that way, a 5% upcharge for better management, can be justified. Mostly its because the team of ops/software engineers supporting production environment are going to cost more than the infrastructure anyways. Additionally, any large deal (>1000 nodes) is gonna get negotiated anyways, so public pricing is kinda a wash.
- lloydde 11y ago
  I appreciate the clear, up front pricing. How does the pricing compare to the competition?
deleted 11y ago
[deleted]
mrmrcoleman 11y ago
Congrats Mitchell + Anand + Kevin + team! Now send someone to softwarecircus.io to talk about it!
tptacek 11y ago
We use Vagrant for dev and Consul in our deployment and I still have no real idea of what Atlas is.
- seiji 11y ago
  Good rationale for not having the people who write the product promote the product. You're too close to remember everybody else doesn't know what things are. Based only on the leading description, it sounds like something trying to be a non-crap Docker replacement that was actually built from experience instead of just trying to capture a VC money waterfall? Atlas builds upon and unites our popular open source tooling to create a version control system for infrastructure. Automate, audit, and collaborate on infrastructure changes across any infrastructure provider. Though, looking more at this post, it's a "we did this product" post, not a post about the product: the product has become a polished, intuitive experience. That's nice? The actual product page starts with: Atlas unites HashiCorp development and infrastructure management tools to create a version control system for infrastructure. Automate, audit, and collaborate on infrastructure changes. Which, I'm still not sure. Atlas can be used for all its features, or features can be used individually. All components are HashiCorp open source tools that are hosted and run in Atlas. That's what it can do, but not what it do. Is this a side effect of SF startup culture? Do we forget everybody doesn't live inside our startups? As best I can tell, Atlas is their map (heh) of how all their pre-existing products work together, and you can buy one umbrella product/support instead of buying 4 individual products?
  - Gigablah 11y ago
    I'll take a stab at this. Atlas is an application that glues together four different projects by Hashicorp: Packer, Vagrant, Terraform and Consul. Packer creates virtual machine images (also has Docker support). Vagrant will create, provision and run them for you (so a bit of overlap with Packer there). Terraform is basically a platform agnostic version of Amazon CloudFormation (create and manage infrastructure via configuration). Consul is a service discovery solution. All of these tools used in conjunction can help you set up a machine, or a cluster of machines, on any supported provider, that will run your application images, all from a set of configuration files. More importantly, changes to your infrastructure and application environment are now a matter of editing configuration. Atlas places a UI in front of these tools and allows you to execute commands and monitor their status.
jalfresi 11y ago
I've never used any of Hashicorps stuff (thought consul did arrive on my radar theother day..). Any recommendations? We use the Atlassian stack here (stash, bamboo, etc) and deploy to AWS (regular AMIs rather than any of that fancy docker stuff). Anything here we should look into?
- jtreminio 11y ago
  Vagrant has completely changed my development workflow. So much so that I created a FOSS that uses it and Puppet: https://puphpet.com https://puphpet.com
  - dkordik 11y ago
    That's an awesome project you've got there. Thanks for sharing!
- Ixiaus 11y ago
  I don't really use anything of Hashicorp's except for Vagrant. That his been fairly revolutionary for all of the teams I've brought it to. That is, Vagrant + Ansible. A repository of Ansible configuration scripts that can easily be slurped down to provision a Vagrant image means much more portable development environments. In the case of the company I'm currently at it's even more important because we have a firmware build system with a non-trivial configuration that would take days to replicate correctly (because of all the "missing pieces" required that the original developer forgot to write down when documenting the process post-setting it up).
- WestCoastJustin 11y ago
  Vagrant. Here's a little brain dump on it @ https://sysadmincasts.com/episodes/42-crash-course-on-vagrant-revised https://sysadmincasts.com/episodes/42-crash-course-on-vagran...
- imperialWicket 11y ago
  Packer is great for generating AMIs, particularly if you're already using some form of config mgmt. It will let you tie in your existing puppet/chef/salt/ansible/shell/etc. and output amis based on your config.
geerlingguy 11y ago
One question I have; with general availability, it seems they indicate packer builds inside of Atlas are free now? It was my understanding that this would be a paid product, so I have my workflow for the OSS vagrant boxes I build all local. If I can switch my workflow to build and store all the box versions inside of Atlas, that would save some time and effort...
- sethvargo 11y ago
  The Packer builds, Vagrant boxes, and Vagrant share are free
devhead 11y ago
Kudos to the team though, love the projects and will continue to support it as it continues to mature. There's still some pretty significant pain points, bit surprised they released already. Hope they get piles of cash to roll in for all their hard work.
bahador 11y ago
Huzzah! Excited to use Atlas on my current project. We're supposed to come onsite to talk with Kevin next week. Looking forward!

68 points by ipedrazas 11y ago

For any of us who have watched this team's output and quality and wondered _Why isn't this team being acquired?_, here is Hashicorp's play. Congrats to team on shipping. It will be interesting to see how all this plays out.

mrdrozdov 11y ago

$40 per node!

ende 11y ago
After 10. So more like $40 per 11 nodes, or $3.6
- arikfr 11y ago
  But if I have 15, then it's $13.3 per node. And at my work place we have >100, which means >$36 per node. That's a lot.
  - ende 11y ago
    Yes it is.
ipedrazas 11y ago
thought the same! Pricing seems a bit Atlassian: almost free if you're small, very expensive if you are not.
- peteretep 11y ago
  That sounds more like Github's Enterprise product, which used to be a cliff of a few thousand bucks to fall off, where private Bitbucket is a $1/user/month. Maybe Github's pricing is less unusual now.
  - BillinghamJ 11y ago
    Github is still incredibly expensive, for both Enterprise and Github.com.
pquerna 11y ago
While $40 per node might sound high, I think it is reasonable. I've worked on several products that are priced per node/server. Per-node a difficult proposition -- the price of "per server" of something varies wildly, for example a t1.micro is roughly $9.50 a month, while a m4.4xlarge is $738. $40 on 9.50 seems extreme, but $40 on $738, and Atlas is only a 5% of the cost of your server. But when your target customer is using high end instances, because they are creating more value for their company that way, a 5% upcharge for better management, can be justified. Mostly its because the team of ops/software engineers supporting production environment are going to cost more than the infrastructure anyways. Additionally, any large deal (>1000 nodes) is gonna get negotiated anyways, so public pricing is kinda a wash.
lloydde 11y ago
I appreciate the clear, up front pricing. How does the pricing compare to the competition?

deleted 11y ago

[deleted]

mrmrcoleman 11y ago

Congrats Mitchell + Anand + Kevin + team! Now send someone to softwarecircus.io to talk about it!

tptacek 11y ago

We use Vagrant for dev and Consul in our deployment and I still have no real idea of what Atlas is.

seiji 11y ago
Good rationale for not having the people who write the product promote the product. You're too close to remember everybody else doesn't know what things are. Based only on the leading description, it sounds like something trying to be a non-crap Docker replacement that was actually built from experience instead of just trying to capture a VC money waterfall? Atlas builds upon and unites our popular open source tooling to create a version control system for infrastructure. Automate, audit, and collaborate on infrastructure changes across any infrastructure provider. Though, looking more at this post, it's a "we did this product" post, not a post about the product: the product has become a polished, intuitive experience. That's nice? The actual product page starts with: Atlas unites HashiCorp development and infrastructure management tools to create a version control system for infrastructure. Automate, audit, and collaborate on infrastructure changes. Which, I'm still not sure. Atlas can be used for all its features, or features can be used individually. All components are HashiCorp open source tools that are hosted and run in Atlas. That's what it can do, but not what it do. Is this a side effect of SF startup culture? Do we forget everybody doesn't live inside our startups? As best I can tell, Atlas is their map (heh) of how all their pre-existing products work together, and you can buy one umbrella product/support instead of buying 4 individual products?
- Gigablah 11y ago
  I'll take a stab at this. Atlas is an application that glues together four different projects by Hashicorp: Packer, Vagrant, Terraform and Consul. Packer creates virtual machine images (also has Docker support). Vagrant will create, provision and run them for you (so a bit of overlap with Packer there). Terraform is basically a platform agnostic version of Amazon CloudFormation (create and manage infrastructure via configuration). Consul is a service discovery solution. All of these tools used in conjunction can help you set up a machine, or a cluster of machines, on any supported provider, that will run your application images, all from a set of configuration files. More importantly, changes to your infrastructure and application environment are now a matter of editing configuration. Atlas places a UI in front of these tools and allows you to execute commands and monitor their status.

jalfresi 11y ago

I've never used any of Hashicorps stuff (thought consul did arrive on my radar theother day..). Any recommendations? We use the Atlassian stack here (stash, bamboo, etc) and deploy to AWS (regular AMIs rather than any of that fancy docker stuff). Anything here we should look into?

jtreminio 11y ago
Vagrant has completely changed my development workflow. So much so that I created a FOSS that uses it and Puppet: https://puphpet.com https://puphpet.com
- dkordik 11y ago
  That's an awesome project you've got there. Thanks for sharing!
Ixiaus 11y ago
I don't really use anything of Hashicorp's except for Vagrant. That his been fairly revolutionary for all of the teams I've brought it to. That is, Vagrant + Ansible. A repository of Ansible configuration scripts that can easily be slurped down to provision a Vagrant image means much more portable development environments. In the case of the company I'm currently at it's even more important because we have a firmware build system with a non-trivial configuration that would take days to replicate correctly (because of all the "missing pieces" required that the original developer forgot to write down when documenting the process post-setting it up).
WestCoastJustin 11y ago
Vagrant. Here's a little brain dump on it @ https://sysadmincasts.com/episodes/42-crash-course-on-vagrant-revised https://sysadmincasts.com/episodes/42-crash-course-on-vagran...
imperialWicket 11y ago
Packer is great for generating AMIs, particularly if you're already using some form of config mgmt. It will let you tie in your existing puppet/chef/salt/ansible/shell/etc. and output amis based on your config.

geerlingguy 11y ago

One question I have; with general availability, it seems they indicate packer builds inside of Atlas are free now? It was my understanding that this would be a paid product, so I have my workflow for the OSS vagrant boxes I build all local. If I can switch my workflow to build and store all the box versions inside of Atlas, that would save some time and effort...

sethvargo 11y ago
The Packer builds, Vagrant boxes, and Vagrant share are free

devhead 11y ago

Kudos to the team though, love the projects and will continue to support it as it continues to mature. There's still some pretty significant pain points, bit surprised they released already. Hope they get piles of cash to roll in for all their hard work.

bahador 11y ago

Huzzah! Excited to use Atlas on my current project. We're supposed to come onsite to talk with Kevin next week. Looking forward!