Doesn't work
Attempted to use this with the "Lean Chef Ralley" "Manage a Node with Chef Automate" lesson. UNUSABLE. After trying to do the setup and I get an internal server error and can download the starter kit or login to the automate console. Tried to login via command line as root and with the key I associated wit the server but still nothing.
Setup is getting error 500
Hi, after launch the ec2. I try to setup a new org. But after fullfill the form I get a 500 (Internal server error).
Looking in the logs a see the next:
"2017-12-04_21:16:33.32044 200.54.48.178 - - [04/Dec/2017:21:16:33 +0000] "POST /biscotti/setup/starter-kit HTTP/1.1" 500 30 0.0635
2017-12-05_12:50:52.23931 200.54.48.178 - - [05/Dec/2017:12:50:52 +0000] "GET /biscotti/ HTTP/1.1" 200 1780 0.0008
2017-12-05_12:50:52.44307 200.54.48.178 - - [05/Dec/2017:12:50:52 +0000] "GET /biscotti/assets/js/app.js HTTP/1.1" 200 393481 0.0013
2017-12-05_12:50:53.30506 200.54.48.178 - - [05/Dec/2017:12:50:53 +0000] "GET /biscotti/assets/images/icons/all.svg HTTP/1.1" 200 59 0.0005
2017-12-05_12:51:17.89212 200.54.48.178 - - [05/Dec/2017:12:51:17 +0000] "POST /biscotti/ HTTP/1.1" 303 - 0.0008
2017-12-05_12:51:18.08876 200.54.48.178 - - [05/Dec/2017:12:51:18 +0000] "GET /biscotti/setup HTTP/1.1" 200 6495 0.0011
2017-12-05_12:51:18.40693 200.54.48.178 - - [05/Dec/2017:12:51:18 +0000] "GET /biscotti/assets/images/icons/all.svg HTTP/1.1" 200 59 0.0006
2017-12-05_12:52:08.71659 2017-12-05 12:52:08 - Net::HTTPServerException - 409 "Conflict":
2017-12-05_12:52:08.71660 /opt/chef-marketplace/embedded/lib/ruby/2.4.0/net/http/response.rb:122:in `error!'
2017-12-05_12:52:08.71661 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/chef-13.4.19/lib/chef/http.rb:152:in `request'
2017-12-05_12:52:08.71661 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/chef-13.4.19/lib/chef/http.rb:131:in `post'
2017-12-05_12:52:08.71661 /opt/chef-marketplace/embedded/service/biscotti/lib/chef_server_setup.rb:41:in `create_org'
2017-12-05_12:52:08.71661 /opt/chef-marketplace/embedded/service/biscotti/app/extensions/starter_kit_dsl.rb:26:in `setup_chef_server'
2017-12-05_12:52:08.71661 /opt/chef-marketplace/embedded/service/biscotti/app/routes/setup.rb:13:in `block in '
2017-12-05_12:52:08.71663 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `call'
2017-12-05_12:52:08.71664 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1632:in `block
in compile!'
2017-12-05_12:52:08.71664 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (
3 levels) in route!'
2017-12-05_12:52:08.71664 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1010:in `route_
eval'
2017-12-05_12:52:08.71664 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:991:in `block (2 levels) in route!'
2017-12-05_12:52:08.71665 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1037:in `block in process_route'
2017-12-05_12:52:08.71665 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `catch'
2017-12-05_12:52:08.71665 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1035:in `process_route'
2017-12-05_12:52:08.71665 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:989:in `block in route!'
2017-12-05_12:52:08.71665 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `each'
2017-12-05_12:52:08.71666 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:988:in `route!'
2017-12-05_12:52:08.71666 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1094:in `block in dispatch!'
2017-12-05_12:52:08.71666 /opt/chef-marketplace/embedded/service/gem/ruby/2.4.0/gems/sinatra-2.0.0/lib/sinatra/base.rb:1073:in `block in invoke'
"
The version that I have been launch was: 1.7.39-1
Chef'ing up Liferay
What do you like best about the product?
I like chef because it uses DSL for configuration instead of XML, Rackspace supports it very well, etc. However the absolute best thing about Chef is the concept of recipes where you can get your platform up and configured extremely easily if that platform has a chef recipe. In addition most large platforms do have chef recipes so it's great! Also, I like that it;s open source
What do you dislike about the product?
Some of the things i dislike about chef, and this might jkust be a criticism of configuration management in general, is that you need pretty much a full team to support it. Sometimes I feel like it adds more complexity instead of kless.
What problems is the product solving and how is that benefiting you?
The biggest issue we are solving with Chef is the knowledge gap that exists in new employees when first learning out platforms. previous it would take months for new developers to become effective because they spend several months fighting with the platform, build tools, etc. Chef makes this much less of a hassle
Recommendations to others considering the product:
Learn it well before you try to incorporate it in your enterprise
looks stupid
Hi,
I have just launched 6 instances of this chef just to test. None of them worked. I dont even know how this exists. If you are the creator of this AMI contact me if you have another document to connect to your chef. Just a waste of time
Infrastructure as code never looked so intimidating and yet hopeful
What do you like best about the product?
The ability to code infrastructure and then run it in action from a single line command is amazing. Imagine spinning up not just 1, but an entire stack of services at once (a whole ecosystem). That's the power of Chef.
What do you dislike about the product?
The problems are myriad. Chef does not have an easy way to pick up for beginners. Most cookbooks are focused on Linux, not Windows. And whenever a deployment breaks, tracing it is a huge pain as there stacktrace is not very informative.
What problems is the product solving and how is that benefiting you?
Chef solves the problem of continuously updating and deploying your software ecosystem from scratch for different purposes and even clients. This helps to make infrastructure development verifiable and repeatable.
Best tool for unifying development environment in a large team.
What do you like best about the product?
Chef provides tools for for IT automation and after trying other tools. Its a master client model and is based in Ruby which was really helpful since we were also developing applications in Ruby on Rails.
The best thing about chef is the collection of modules and configuration recipes. Also, its based around Git which everyone is familiar with and 'Knife' tool is very helpful during installations.
What do you dislike about the product?
Learning curve is steep but since we were already using Ruby it was a bit easy for us. Apart from that, its a not a smiple tool, It can lead to very large code bases and complicated environments quickly. One needs to be aware of that. Also, it doesn't support push functionality which other alternatives does.
Chef documentation can also be a little sketchy from time to time. They are more focused on making it work than writing documentations and doesn't provide as much platform support as other alternatives does.
What problems is the product solving and how is that benefiting you?
We use chef's Application Automation tool 'Habitat' to unify the development enviroment among a large team which can be a disaster while working with frameworks like Ruby on Rails.
A workhorse for deployment and configuration
What do you like best about the product?
The ability to manage multiple environments easily.
What do you dislike about the product?
The domain specific language has a couple of small quirks.
What problems is the product solving and how is that benefiting you?
We used this to manage all of the hosts configurations and applications that we deployed. It was used for all aspects to manage log locations, configurations, and even some kernel level configurations.
Recommendations to others considering the product:
https://docs.chef.io/ is your friend! The domain specific language (DSL) can be very hard at times especially for those coming from a non-Ruby programming back-ground.
deploy made easy again
What do you like best about the product?
Previously to deploy a large application was suffering, always happened several problems. When I met Chef (while studying the vagrant) quickly deployed in my company. Chef is able to handle EVERYTHING related to creation of a dynamic infrastructure
What do you dislike about the product?
Nothing, all in Chef is exquisite, even the price is right. Of course you will have to study hard for put the tool into production, but it is a study that will be worth it.
What problems is the product solving and how is that benefiting you?
DevOps! In my company we had problems in the deployment of the tools. The time between the development and deployment was too long, now with Chef dramatically reduce the costs associated with deployment, and now we have the DevOps culture more strong
Recommendations to others considering the product:
Know that the documentation is extensive. It will take time to master the full tool, but the time spent will be saved in deploy
Powerful tool but difficult to get started with
What do you like best about the product?
Simplifies bootstrapping fleets of servers and managing required packages. Allows developers to build upon a library of packages from other developers so they don't need to start at the basics from scratch and can more quickly and easily start on the parts that really matter
What do you dislike about the product?
Very difficult and time consuming to set up and get started with; large learning curve; compatibility issues with little to no documentation
What problems is the product solving and how is that benefiting you?
Automating deployments, versioning deployment code, granular user permissions, scalable and highly available infrastructure and applications
Recommendations to others considering the product:
Consider as a possible solution for your DevOps build but also consider other tools like Ansible. You may very quickly become dependent on Chef once you implement it so make sure you like it and it meets your needs first. Team members with previous experience will be a huge plus to overcome the initial learning curve and setup time.
Automating deployment with Chef
What do you like best about the product?
Chef is a standard in automated deployment. Is used in Facebook and it's really REALLY powerful. It's a very serious thing about deployment automation and it's capabilities are huge. Maintains states (software, configuration...) of the entire cluster, and I'm talking about hundreds of nodes. Cookbooks are very popular and you can find them to do almost everything in the open source community.
What do you dislike about the product?
Chef is terribly complex to deploy by itself, not only needs a Chef Server that internally will install a RabbitMQ, a SQL database, a Nginx... it can really take a lot of resources of your machine.
Not only this, you need to install a daemon, Chef Client, on each Chef node you want to manage. Of course if this Client fails... your node is "lost" for Chef and you cannot manage it anymore until you restart the client.
What problems is the product solving and how is that benefiting you?
We were automating the installation of 8 to 10 linux packages over a set of 4 to 20 machines. We were using a "root" machine to start the installation and, using a web ui, let a user select a set of technologies to install them on the rest of the nodes.
Recommendations to others considering the product:
If you really, really need to manage a big set of nodes to do very complex things, you can give Chef a try (you also have Puppet). But if need something relatively simple I don't think is worth the effort. As I mention before, Chef is quite complex if you want to do simple things (maybe Ansible fits better in this case)
