Hello Carlos, Thanks for the reply.
Carlos, would you mind sharing with me how your Jenkins job is set up? Are you using pre/post build scripts? Are these using the JClouds api? I have thought of doing this job using our CI Server, but I was hoping I could write a java class that could do it all. Thank you so much again for the help! Neil On Sat, Jan 25, 2014 at 1:38 AM, Carlos Ospina <[email protected]>wrote: > Hello Neil. > I believe the best way to do steps 3-6 is to use a Continuous integration > server like Hudson or Jenkins. > I do this very often and works like a charm. > The Balancer tasks can also be automated with the CI server > On Jan 24, 2014 8:55 PM, "Neil Corbet" <[email protected]> wrote: > >> Hello All, >> >> I am new to JClouds and I am hoping that maybe someone can help point me >> in the right direction. >> >> I have a basic use case. I need to do the following: >> >> 1. Grab a Load Balancer >> 2. Disable the nodes one by one to take them out of the load balancer. >> 3. Shut down an app server ( tomcat ) on each node >> 4. Update a war file. >> 5. Restart App Server >> 6. Run a selenium based smoke test to make sure the app deployed fine. >> 7. Add the node back to the load balancer. >> >> All of this is in the Rackspace cloud. Linux based servers. >> >> So far, I can do numbers 1 and 2 with no problem. Where I am struggling >> is getting from the Node to the NodeMetadata so that I can get the Public >> address so I can use the ScriptBuilder to perform steps 3, 4, and 5. >> >> I am using the CloudLoadBalancerApi to get my balancer by zone and name. >> I then get the NodeApi to get the nodes and I can disable them fine. >> >> I just dont know what to do from here because I need the public address >> for the script builder and ssh. >> >> Am I on the right track, or is there an easier way to do this? >> >> Thanks, >> Neil >> >
