Hi Graham, I don't have a complete answer for you now as this isn't my particular area of expertise, but I can get you started and will ask around for more information in order to provide a fuller answer.
I believe this functionality can be achieved using a combination of an effector and the `ServiceReplacer` policy. Here are two examples[1][2] of this policy in use. My understanding is that the service could be replaced with a new instance running an upgraded version, on demand. I will confirm this. I hope this helps for starters. Cheers, Mike [1] https://brooklyn.apache.org/v/latest/start/policies.html [2] https://brooklyn.apache.org/v/latest/java/topology-dependencies.html On Tue, Jul 19, 2016 at 2:20 PM Graham Ashby <[email protected]> wrote: > I've been investigating using Brooklyn with our product. I've been > impressed with the out of box capabilities, plus the ease of extending it. > > However, one thing I haven't seen addressed in the documentation is how > you patch running systems. Say I have a composite application that has a > number of subsidiary applcations. Now of those, there are a number of > replicated components tat all need upgrading. How do I do this? I would > have the blueprint for the entire system. How do I indicate that certain > parts need updating? I don't want to have to tear down the existing > system, and rebuild a new one. > > Sorry if this is muddled -- I'm new to Brooklyn. > > Thanks > Graham Ashby > IBM Canada > >
