Brooklyn Persistence Style Adoption

Hey folks, *Context:* After having used brooklyn extensively and also reading the persistence documentation, I see that based on brooklyn.properties or CLI parameters brooklyn can either persist its state to localhost or to the cloud (using jclouds). *Question:* I want to emulate the same behavio

Re: Repository splitting script

i think leave it `brooklyn/software/winrm` in the old hierarchy, and in the new hierarchy `brooklyn-server/software/winrm` alongside `brooklyn/software/base` `locations/*` is intended for implementations of `Location` --a On 9 December 2015 at 22:36, John McCabe wrote: > Does locations/winrm

Re: Repository splitting script

Does locations/winrm sound reasonable? (rather than reverting back to /core) On Wed, Dec 9, 2015 at 5:19 PM, Aled Sage wrote: > +1 > > Let's move winrm to brooklyn-server. > > > > On 09/12/2015 16:56, Hadrian Zbarcea wrote: > >> That should be (or at least become) a soft dependency, not a hard o

[GitHub] incubator-brooklyn pull request: Fix MySQL artefact name in line w...

Github user alasdairhodge closed the pull request at: https://github.com/apache/incubator-brooklyn/pull/998 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

Re: [DISCUSS] new repos and project migration

Hi, Better late than never :) I'd like to to vote -1 for the module brooklyn-server. I think brooklyn-base is a better name. brooklyn-server implies we should always have a server inside. What if we have non-rest cli but a native java cli? I am concerned a little about the build process. I suppo

Re: Repository splitting script

+1 Let's move winrm to brooklyn-server. On 09/12/2015 16:56, Hadrian Zbarcea wrote: That should be (or at least become) a soft dependency, not a hard one. That aside, the winrm piece probably belongs in server. Hadrian On 12/09/2015 11:27 AM, John McCabe wrote: Alex, all, (fyi Hadrian/Cipr

[GitHub] incubator-brooklyn pull request: GeoDns improvements

GitHub user sjcorbett opened a pull request: https://github.com/apache/incubator-brooklyn/pull/1096 GeoDns improvements A variety of improvements to the geo-DNS entities. In particular: * Entities whose service state is not `RUNNING` are automatically excluded from the pool of t

Re: Repository splitting script

That should be (or at least become) a soft dependency, not a hard one. That aside, the winrm piece probably belongs in server. Hadrian On 12/09/2015 11:27 AM, John McCabe wrote: Alex, all, (fyi Hadrian/Ciprian), * fix pom files on result of `rearrange-incubator.sh` script so it builds (mak

Re: Repository splitting script

Alex, all, (fyi Hadrian/Ciprian), > * fix pom files on result of `rearrange-incubator.sh` script so it builds >>> (make this a diff / git cherry-pick we can just apply once all PRs are >>> merged?) >>> >> John also said to me that he would take a look at this problem. He was >> temporarily preven

Re: Repository splitting script

Richard, All - It occurs to me it is nice and simple if we are able to say that for each new repo, the history is: * the relevant subset of the incubator repo history * followed by a `git mv /* .` with message saying "migration from incubator to new multi-repo structure complete" From an a

Build failed in Jenkins: incubator-brooklyn-master-windows #382

See Changes: [geoff.macartney] Fix assertions for 'succeeds eventually' behaviour. -- [...truncated 463 lines...] [INFO]

[GitHub] incubator-brooklyn pull request: removed incubator from mirror dow...

GitHub user johnmccabe opened a pull request: https://github.com/apache/incubator-brooklyn/pull/1095 removed incubator from mirror download urls Resulting mirror links resolve for the source and dist downloads on the generated site. You can merge this pull request into a Git reposi

[GitHub] incubator-brooklyn pull request: Fix assertions for 'succeeds even...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-brooklyn/pull/1094 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the fe

[GitHub] incubator-brooklyn pull request: Fix assertions for 'succeeds even...

Github user aledsage commented on the pull request: https://github.com/apache/incubator-brooklyn/pull/1094#issuecomment-163157422 Build failure looks unrelated, and an infrastructure thing ("Internal error: java.lang.IllegalStateException: Invalid object ID 19 iota=66"). Note