Can you explain your considerations on why is that required for you to keep the old role? and why do you have to do sync to all so often? Maybe people here can offer alternatives when the whole picture is in front of us.
On Fri, Jul 24, 2009 at 5:29 PM, andrej <[email protected]> wrote: > > Agreed Donovan. I do not want to end up having tens of app roles after > a few months as I need to do sync fairly often (currently every 3-4 > days). > > It would be nice to have an option to keep the old instance after a > sync. Maybe a checkbox before confirming "sync to all". Nickolas? > > Thanks. > > > On Jul 24, 4:23 pm, Donovan Bray <[email protected]> wrote: > > That works if your actually trying to create a new role. But doesn't > > help if you are just trying to memorialize the changes you just made > > to the same role without causing an interruption of service. > > > > On Jul 24, 2009, at 3:38 AM, Nickolas Toursky <[email protected]> wrote: > > > > > > > > > Hi Andrej, > > > > > You can use 'Roles->Create new' option so the old instance will not be > > > shut down. > > > > > Nick > > > > > 2009/7/24 andrej <[email protected]>: > > > > >> I would like to keep old instance running after synchronize to all > > >> has > > >> finished rather then replace it with a new. Is it possible to setup > > >> this in Scalr? If not, how to do it? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
