Dr Venu Murthy

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 52.0.234.85 52.0.234.85 Starting Chef Client, version 11.18.6 52.0.234.85 52.0.234.85 ================================================================================ 52.0.234.85 Chef encountered an error attempting to load the node data for "first1" 52.0.234.85 ================================================================================ 52.0.234.85 52.0.234.85 Unexpected Error: 52.0.234.85 ----------------- 52.0.234.85 Chef::Exceptions::JSON::ParseError: parse error: premature EOF 52.0.234.85 52.0.234.85                      (right here) ------^ 52.0.234.85 52.0.234.85 [2015-02-09T02:36:38-05:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out 52.0.234.85 Chef Client failed. 0 resources updated in 0.854925495 seconds 52.0.234.85 [2015-02-09T02:36:38-05:00] ERROR: parse error: premature EOF 52.0.234.85 52.0.234.85                      (right here) ------^ 52

While bootstrapping a redhat node which is on AWS EC2, which supports only the SSH identity file for authentication, I was getting the below error after this command  knife bootstrap 52.0.13.12 --ssh-user ec2-user --identity-file ~/.ssh/xyz.pem --node-name first1 --run-list 'recipe[some_thing]' Error 52.0.13.132 Installing Chef Client... 52.0.13.132   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current 52.0.13.132                                  Dload  Upload   Total   Spent    Left  Speed 100 18285  100 18285    0     0  48457      0 --:--:-- --:--:-- --:--:-- 48630 52.0.13.132 Downloading Chef 11 for el... 52.0.13.132 downloading https://www.opscode.com/chef/metadata?v=11&prerelease=false&nightlies=false&p=el&pv=7&m=x86_64 52.0.13.132   to file /tmp/install.sh.940/metadata.txt 52.0.13.132 trying curl... 52.0.13.132 url https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-11.18.6-1.el6

Today I wanted to play around hashing passwords and installing  bcrypt and got the below errors and the solution to this is as simple as running xcode-select --install and then pip install using elevated privilages     cc -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386 -g -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -DENABLE_DTRACE -DMACOSX -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -fwrapv -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch i386 -pipe -DUSE__THREAD -I/usr/include/ffi -I/usr/include/libffi -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c c/_cffi_backend.c -o build/temp.macosx-10.9-intel-2.7/c/_cffi_backend.o     c/_cffi_backend.c:13:10: fatal error: 'ffi.h' file not found     #include <ffi.h>              ^     1 error generated.     error: command 'cc' failed with exit status 1     Complete output from command /usr/bin/python -c "

When trying to access the instance's console from Horizon, that has been spun up we get the error, "the server refused the connection" Check the nova.conf file on the Controller node if you have a several node setup. novncproxy_base_url=http://127.0.0.1:6080/vnc_auto.html when you inspect the element from chrome, you can see that the instance console is trying to connect to the controller on that port. Doing a telnet from the box from where your are access on port 6080 should also fail, as that port might not be accessible from outside. Hence this is clearly issue with the port and if you are on Centos you might already have sensed the culprit! The IPTABLES! Adding a rule as as the one below and saving the tables should help access the console. ```iptables -I INPUT 7 -m state --state NEW -p tcp --dport 6080 -j ACCEPT``` ```service iptables save``` Hope this helps you, leave us those comments! Update This error can also come up if the novncproxy h

I completed reading the awesome Pheonix project book and as is normal for the lessons to fade away, I might forget all of it as the days go by, but the summary of what I loved the most in this book is Every work center is made up of four things.  The machine.  The man.  The method.  And the measures.  And one more First way helps us understand how to create fast flow of work from Dev to Ops.  Second way shows us how to shorten and amplify feedback ...  Third shows us how to create a culture that simultaneously foster  experimentation, learning from failure and understanding that repetition and practice are the  prerequisites to mastery.  Even though it was monotonous at times, and this book could have continued to be interesting until the last page if it could be shortened, but it was a great book and helped me to come across the master piece "The Goal" which I am reading now

"Don't use Chef or Puppet, use the native Heat for Openstack Config management" this statement from our peer led me to explore and find out that Heat can only be used for orchestration purpose, in that, it can bring up the virtual machines and the underlining support systems that they would need like routers and switches but would not be able to configure the instances that have come up, for this we would need to continue using Chef or Puppet or Ansible. "Heat primarily manages infrastructure, but the templates integrate well with software configuration management tools such as Puppet and Chef" https://wiki.op enstack.org/wik i/Heat Cloud Orchestration is not a replacement for server configuration tools such as Puppet and Chef. They are very complementary. You will continue to use Chef and Puppet to “template-ize” your server software configurations, while Cloud Orchestration and its HOT templates will help you create a full stack that includes all th

After having struggled through with various building blocks of OpenStack, Heat was a great relief. It's installation and integration was pretty smooth. One of the most helpful documents was this  one . By definition "The Orchestration service provides a template-based orchestration for describing a cloud application by running OpenStack API calls to generate running cloud applications." The templates enable you to create most OpenStack resource types, such as instances, floating IPs, volumes, security groups, users, and so on. Also, provides some more advanced functionality, such as instance high availability, instance auto-scaling, and nested stacks. By providing very tight integration with other OpenStack core projects, all OpenStack core projects could receive a larger user base. Components of the Orchestration service heat  command-line client. A CLI that communicates with the heat-api to run AWS CloudFormation APIs. End developers could als