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 <[email protected]> > wrote: > > 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]: > https://github.com/apache/incubator-brooklyn/blob/master/software/base/src/main/java/org/apache/brooklyn/entity/software/base/SameServerDriverLifecycleEffectorTasks.java#L97-L99 > > On 13 November 2015 at 16:28, Martin Harris <[email protected] >> 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]: >> https://github.com/apache/incubator-brooklyn/blob/master/software/base/src/main/java/org/apache/brooklyn/entity/software/base/SoftwareProcessImpl.java#L496-L521 >> >> Cheers >> >> -- >> Martin Harris >> Lead Software Engineer >> Cloudsoft Corporation Ltd >> www.cloudsoftcorp.com >> Mobile: +44 (0)7989 047-855 >> > > > > -- > Martin Harris > Lead Software Engineer > Cloudsoft Corporation Ltd > www.cloudsoftcorp.com > Mobile: +44 (0)7989 047-855
