I would use on init instead since host up is the trigger to put the application in the load balanced rotation. If you wait for hostup when the role scales there will be a breif disturbance for your clients because that app server wasn't truely ready to handle the load.
On Sep 4, 2009, at 7:24 AM, damonjebb <[email protected]> wrote: > > Hi Nick, > > I had hoped that the mount would happen as a result of the fstab > entry, but I suppose a script would be a relatively simple solution. > > Would you trigger this script on 'host up'? > > Thanks > Damon > > On Sep 4, 1:22 pm, Nickolas Toursky <[email protected]> wrote: >> Damon, >> >> You mount filesystems from your scripts, correct? >> >> Why not to check mountpoint exists and create this directory >> otherwise >> within your script? >> >> If you will unmount the external filesystem, its mountpoint will be >> included in the bundle. >> >> Its controlled by both Scalr scripts and Amazon AMI tools. >> >> Nick >> >> 2009/9/4 damonjebb <[email protected]>: >> >> >> >>> This is a bad thing becasue it requires a synchronisation of the >>> empty >>> mount point prior to making other changes that will often require >>> another synchronisation. When synchronisation and start up take >>> around an hour on average this is a significant inconvenience. >> >>> Is this something that is controlled by the scalr feature set or >>> Amazon? >> >>> Would I be right to think that unmounting the folder prior to >>> synchronising would allow it to be included in the image bundle? >> >>> Thanks >>> Damon >> >>> On Sep 4, 10:20 am, Nickolas Toursky <[email protected]> wrote: >>>> Damon, >> >>>> Mounted filesystems are not included into image bundle as well as >>>> their mountpoints. You should create them yourself before mount. >> >>>> Nick >> >>>> 2009/9/4 damonjebb <[email protected]>: >> >>>>> I'm not sure whether this is a scalr thing or amazon, but; I've >>>>> noticed on several occasions that the synchronisation of mounted >>>>> folders fails. To replicate... >> >>>>> 1) Create a new, empty folder as a mount point for NFS >>>>> 2) export an NFS share from another role >>>>> 3) mount the NFS share on the new empty folder. >>>>> 4) synchronise the role with the mounted folder >> >>>>> On restarting the role that had mounted the share the folder >>>>> created >>>>> for the mount does not exist and has to be recerated before the >>>>> mount >>>>> can be completed. >> >>>>> Thanks >>>>> Damon > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
