We use Vagrant for dev and Consul in our deployment and I still have no real idea of what Atlas is.
Atlas General Availability
11–20 of 38 posts
Re: Atlas General Availability
#12I'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?
Re: Atlas General Availability
#13I'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?
Vagrant has completely changed my development workflow.
So much so that I created a FOSS that uses it and Puppet: https://puphpet.com
Re: Atlas General Availability
#14One 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...
Re: Atlas General Availability
#15I'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?
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).
Re: Atlas General Availability
#16I'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?
Vagrant. Here's a little brain dump on it @ https://sysadmincasts.com/episodes/42-crash-course-on-vagran...
Re: Atlas General Availability
#17One 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...
The Packer builds, Vagrant boxes, and Vagrant share are free
Re: Atlas General Availability
#18I'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?
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.
Re: Atlas General Availability
#19We use Vagrant for dev and Consul in our deployment and I still have no real idea of what Atlas is.
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?
Re: Atlas General Availability
#20We use Vagrant for dev and Consul in our deployment and I still have no real idea of what Atlas is.
Great feedback. We've heard this and we've been making strides to improve it. For the most part, this is largely our own doing: we didn't do a good job at all of marketing Atlas to the open source community. There are various reasons for this, including not wanting the community to feel we were pushing commercializing onto them. Another reason is that as Atlas was in tech preview, we wanted to build more features and stabilize on the features we had. But we're carefully learning what the boundaries are and are spreading them a bit more.
If you're an open source user, the first thing that you can do is just go to atlas.hashicorp.com and see the features we add on top of the project you're already using. We now break down features by project being augmented.
Example: Vagrant augmentation: https://atlas.hashicorp.com/learn/vagrant
We have pages like that for all our tools.
We'll continue to improve this! Thanks for the feedback.
EDIT: Sorry, I was answering "why don't I know what Atlas is" versus the answer that was expected for "what is Atlas". The best answer for that is to use the homepage and click on the product (Vagrant, Packer, etc.) you use the most! http://atlas.hashicorp.com