I wrote a demo application which registers google appengine instances in
chef [1], specifically the opscode
platform<https://cookbooks.opscode.com/users/new>,
upon startup.  While the chef api is not 100% complete in jclouds, enough is
finished to start integrating.

       http://github.com/jclouds/jclouds-chef-googleappengine-demo

The status page shows all the instances of the current google app engine
application, which are registered in the opscode platform.

       http://jclouds-chef-demo.appspot.com/nodes/status.check

When this seems to hesitate, it is probably google firing up a new instance,
which implies a new node registration.  This is a simple demonstration.
More sophisticated applications can be built to use the databag concept in
chef to ensure that all dots between your cloud and non-cloud infrastructure
are connected [2].  You could even use the jclouds compute api to launch new
compute nodes (ex. ec2) and register them accordingly.

This demo requires a publicly available Chef 0.9.6 endpoint.  If you are
using the Opscode Platform, remember that you get 5 nodes for free.  Make
sure you clean up your nodes in the console when you are finished testing
[3].

I hope you like it!
-Adrian
founder jclouds

[1] http://wiki.opscode.com/display/chef/Home
[2] http://wiki.opscode.com/display/chef/Data+Bags
[3] https://manage.opscode.com/nodes

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Reply via email to