brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aled Sage <>
Subject Re: Child Entities
Date Fri, 13 Nov 2015 21:27:51 GMT

Svet's right: it's always been that way (since January 2014 when the 
functionality was added - c8fb5aac5b0c7f60ff98d6a9530d3aafb7e68edc).

See SoftwareProcessDriverLifecycleEffectorTasks.startProcessesAtMachine, 
which calls StartableMethods.startingChildren(entity(), machineS.get()) 
- i.e. with the machine-location rather than the 
MachineProvisioningLocation that it might have been passed when it was 
being started.

The most common use-case (I believe) for having a child entity of a 
SoftwareProcess is because you want to have additional things as part of 
that software process (e.g. you could have an entity for a logstash or 
NewRelic agent as a child). Hence we pass the machine to the child.

Is Svet's workaround good for you Martin? Or is your use-case different, 
meaning you really do need a different machine?


On 13/11/2015 16:36, Svetoslav Neykov wrote:
> Hi Martin,
> I believe this has always been the case, at least not changed recently. Spinning on the
same machine is more of a side effect from entities inheriting their parent's locations than
explicitly supporting this scenario.
> As a workaround you can configure the ports on the parent entity, it will add them to
the security group, while the child will inherit and use them.
> Svet.
>> On 13.11.2015 г., at 18:31, Martin Harris <>
>> P.S. for the SameServerEntity (which is used where you want multiple
>> entities installed on the same VM), the ports of the child entities *are*
>> added to the required ports[2]
>> [2]:
>> On 13 November 2015 at 16:28, Martin Harris <
>>> wrote:
>>> Hi All,
>>> I'm deploying an app where a SoftwareProcess (TomcatServer) is the child
>>> of a VanillaSoftwareProcess, but when I deploy it, both the TomcatServer
>>> and the VanillaSoftwareProcess are installed on the same VM. Is this new
>>> behaviour or has it changed? I thought it provisioned a new VM for the child
>>> One issue with this the problem that when deploying to AWS the ports
>>> required for the child aren't opened in the AWS security group [1]
>>> [1]:
>>> Cheers
>>> --
>>> Martin Harris
>>> Lead Software Engineer
>>> Cloudsoft Corporation Ltd
>>> Mobile: +44 (0)7989 047-855
>> -- 
>> Martin Harris
>> Lead Software Engineer
>> Cloudsoft Corporation Ltd
>> Mobile: +44 (0)7989 047-855

View raw message