Posting back just in case somebody else ends up with the same doubt. This is what I did to get it running without rebuilding.
1. After importing the standard Scalr roles, I cloned the required ones. For example app-apache64 role. 2. Then I edited the cloned role and removed all the AMI images. 3. I then added the already existing AMI. 4. Saved the role. Then recreated the farm and added the cloned role with my image attached. The instance was launched perfectly and all was fine. I didn't have to rebuild the image. Hope this is not breaking anything .. and could be useful reference for others also. Cheers Srini On Monday, September 23, 2013 2:53:52 PM UTC+5:30, Thomas Orozco wrote: > > Hey Srini, > > What's on those Roles? Are there role-level scripting rules, or is that > just AMIs? > > If it's only the AMIs, the safer way is probably to use Role import, yes. > > Cheers, > > > On Saturday, September 21, 2013 4:59:36 AM UTC+2, Srini wrote: >> >> Bump ... Can someone let me know what is the best way? Is it via the >> import non-Scalr role again or is there a better way? >> >> Srini >> >> On Friday, September 20, 2013 5:32:24 PM UTC+5:30, Srini wrote: >>> >>> I have a running Scalr setup with custom Roles/AMIs. If I setup a >>> totally new installation of Scalr (planning to do this as my version is >>> really old compared to what is current), how do I import my existing >>> roles/AMIs into the new setup of Scalr? Once the new version is up, I will >>> retire the old one. >>> >>> Cheers >>> Srini >>> >> -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
