You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by Mike Zaccardo <mi...@cloudsoftcorp.com> on 2015/09/28 17:30:30 UTC

Get `INSTALL_DIR` during `launch` phase?

Hi all,

I'm working on a blueprint[1] in which I'd like the `launch` phase to
invoke a start script that is added to `INSTALL_DIR`[2] during the
`install` phase.

Right now I'm facing a problem because the `launch` phase executes in
`RUN_DIR`[3], so the command fails since it cannot find the necessary
script file.

Is there a way to reference the `INSTALL_DIR` value in the `launch` phase
so I can get this to work?

Cheers,
Mike

[1]
https://github.com/mikezaccardo/brooklyn-zeppelin/blob/master/catalog.bom
[2]
INSTALL_DIR="/home/users/Mike/brooklyn-managed-processes/installs/VanillaSoftwareProcess_0.0.0"
[3]
RUN_DIR="/home/users/Mike/brooklyn-managed-processes/apps/nVmOMvpp/entities/VanillaSoftwareProcess_cMqHslpp"

-- 
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. 
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
 
This e-mail message is confidential and for use by the addressee only. If 
the message is received by anyone other than the addressee, please return 
the message to the sender by replying to it and then delete the message 
from your computer. Internet e-mails are not necessarily secure. Cloudsoft 
Corporation Limited does not accept responsibility for changes made to this 
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of 
viruses, it is the responsibility of the recipient to ensure that the 
onward transmission, opening or use of this message and any attachments 
will not adversely affect its systems or data. No responsibility is 
accepted by Cloudsoft Corporation Limited in this regard and the recipient 
should carry out such virus and other checks as it considers appropriate.

Re: Get `INSTALL_DIR` during `launch` phase?

Posted by Mike Zaccardo <mi...@cloudsoftcorp.com>.
Works great!

On Mon, Sep 28, 2015 at 10:45 AM Mike Zaccardo <
mike.zaccardo@cloudsoftcorp.com> wrote:

> Ah yes, of course!  Thanks, Svet!  I'll try it out right now.
>
> Cheers,
> Mike
>
> On Mon, Sep 28, 2015 at 10:34 AM Svetoslav Neykov <
> svetoslav.neykov@cloudsoftcorp.com> wrote:
>
>> Hi Mike,
>> I believe you can do
>>
>> shell.env:
>>     INSTALL_DIR: $brooklyn:attributeWhenReady("install.dir")
>>
>> in the config section and use it in your launch phase as $INSTALL_DIR.
>>
>> Svet.
>>
>>
>>
>> > On 28.09.2015 г., at 18:30, Mike Zaccardo <
>> mike.zaccardo@cloudsoftcorp.com> wrote:
>> >
>> > Hi all,
>> >
>> > I'm working on a blueprint[1] in which I'd like the `launch` phase to
>> > invoke a start script that is added to `INSTALL_DIR`[2] during the
>> > `install` phase.
>> >
>> > Right now I'm facing a problem because the `launch` phase executes in
>> > `RUN_DIR`[3], so the command fails since it cannot find the necessary
>> > script file.
>> >
>> > Is there a way to reference the `INSTALL_DIR` value in the `launch`
>> phase
>> > so I can get this to work?
>> >
>> > Cheers,
>> > Mike
>> >
>> > [1]
>> >
>> https://github.com/mikezaccardo/brooklyn-zeppelin/blob/master/catalog.bom
>> > [2]
>> >
>> INSTALL_DIR="/home/users/Mike/brooklyn-managed-processes/installs/VanillaSoftwareProcess_0.0.0"
>> > [3]
>> >
>> RUN_DIR="/home/users/Mike/brooklyn-managed-processes/apps/nVmOMvpp/entities/VanillaSoftwareProcess_cMqHslpp"
>> >
>> > --
>> > Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
>> > Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
>> >
>> > This e-mail message is confidential and for use by the addressee only.
>> If
>> > the message is received by anyone other than the addressee, please
>> return
>> > the message to the sender by replying to it and then delete the message
>> > from your computer. Internet e-mails are not necessarily secure.
>> Cloudsoft
>> > Corporation Limited does not accept responsibility for changes made to
>> this
>> > message after it was sent.
>> >
>> > Whilst all reasonable care has been taken to avoid the transmission of
>> > viruses, it is the responsibility of the recipient to ensure that the
>> > onward transmission, opening or use of this message and any attachments
>> > will not adversely affect its systems or data. No responsibility is
>> > accepted by Cloudsoft Corporation Limited in this regard and the
>> recipient
>> > should carry out such virus and other checks as it considers
>> appropriate.
>>
>>
>> --
>> Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
>>  Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
>>
>> This e-mail message is confidential and for use by the addressee only. If
>> the message is received by anyone other than the addressee, please return
>> the message to the sender by replying to it and then delete the message
>> from your computer. Internet e-mails are not necessarily secure. Cloudsoft
>> Corporation Limited does not accept responsibility for changes made to
>> this
>> message after it was sent.
>>
>> Whilst all reasonable care has been taken to avoid the transmission of
>> viruses, it is the responsibility of the recipient to ensure that the
>> onward transmission, opening or use of this message and any attachments
>> will not adversely affect its systems or data. No responsibility is
>> accepted by Cloudsoft Corporation Limited in this regard and the recipient
>> should carry out such virus and other checks as it considers appropriate.
>>
>

-- 
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. 
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
 
This e-mail message is confidential and for use by the addressee only. If 
the message is received by anyone other than the addressee, please return 
the message to the sender by replying to it and then delete the message 
from your computer. Internet e-mails are not necessarily secure. Cloudsoft 
Corporation Limited does not accept responsibility for changes made to this 
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of 
viruses, it is the responsibility of the recipient to ensure that the 
onward transmission, opening or use of this message and any attachments 
will not adversely affect its systems or data. No responsibility is 
accepted by Cloudsoft Corporation Limited in this regard and the recipient 
should carry out such virus and other checks as it considers appropriate.

Re: Get `INSTALL_DIR` during `launch` phase?

Posted by Mike Zaccardo <mi...@cloudsoftcorp.com>.
Ah yes, of course!  Thanks, Svet!  I'll try it out right now.

Cheers,
Mike

On Mon, Sep 28, 2015 at 10:34 AM Svetoslav Neykov <
svetoslav.neykov@cloudsoftcorp.com> wrote:

> Hi Mike,
> I believe you can do
>
> shell.env:
>     INSTALL_DIR: $brooklyn:attributeWhenReady("install.dir")
>
> in the config section and use it in your launch phase as $INSTALL_DIR.
>
> Svet.
>
>
>
> > On 28.09.2015 г., at 18:30, Mike Zaccardo <
> mike.zaccardo@cloudsoftcorp.com> wrote:
> >
> > Hi all,
> >
> > I'm working on a blueprint[1] in which I'd like the `launch` phase to
> > invoke a start script that is added to `INSTALL_DIR`[2] during the
> > `install` phase.
> >
> > Right now I'm facing a problem because the `launch` phase executes in
> > `RUN_DIR`[3], so the command fails since it cannot find the necessary
> > script file.
> >
> > Is there a way to reference the `INSTALL_DIR` value in the `launch` phase
> > so I can get this to work?
> >
> > Cheers,
> > Mike
> >
> > [1]
> >
> https://github.com/mikezaccardo/brooklyn-zeppelin/blob/master/catalog.bom
> > [2]
> >
> INSTALL_DIR="/home/users/Mike/brooklyn-managed-processes/installs/VanillaSoftwareProcess_0.0.0"
> > [3]
> >
> RUN_DIR="/home/users/Mike/brooklyn-managed-processes/apps/nVmOMvpp/entities/VanillaSoftwareProcess_cMqHslpp"
> >
> > --
> > Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
> > Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
> >
> > This e-mail message is confidential and for use by the addressee only. If
> > the message is received by anyone other than the addressee, please return
> > the message to the sender by replying to it and then delete the message
> > from your computer. Internet e-mails are not necessarily secure.
> Cloudsoft
> > Corporation Limited does not accept responsibility for changes made to
> this
> > message after it was sent.
> >
> > Whilst all reasonable care has been taken to avoid the transmission of
> > viruses, it is the responsibility of the recipient to ensure that the
> > onward transmission, opening or use of this message and any attachments
> > will not adversely affect its systems or data. No responsibility is
> > accepted by Cloudsoft Corporation Limited in this regard and the
> recipient
> > should carry out such virus and other checks as it considers appropriate.
>
>
> --
> Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
>  Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
>
> This e-mail message is confidential and for use by the addressee only. If
> the message is received by anyone other than the addressee, please return
> the message to the sender by replying to it and then delete the message
> from your computer. Internet e-mails are not necessarily secure. Cloudsoft
> Corporation Limited does not accept responsibility for changes made to this
> message after it was sent.
>
> Whilst all reasonable care has been taken to avoid the transmission of
> viruses, it is the responsibility of the recipient to ensure that the
> onward transmission, opening or use of this message and any attachments
> will not adversely affect its systems or data. No responsibility is
> accepted by Cloudsoft Corporation Limited in this regard and the recipient
> should carry out such virus and other checks as it considers appropriate.
>

-- 
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. 
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
 
This e-mail message is confidential and for use by the addressee only. If 
the message is received by anyone other than the addressee, please return 
the message to the sender by replying to it and then delete the message 
from your computer. Internet e-mails are not necessarily secure. Cloudsoft 
Corporation Limited does not accept responsibility for changes made to this 
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of 
viruses, it is the responsibility of the recipient to ensure that the 
onward transmission, opening or use of this message and any attachments 
will not adversely affect its systems or data. No responsibility is 
accepted by Cloudsoft Corporation Limited in this regard and the recipient 
should carry out such virus and other checks as it considers appropriate.

Re: Get `INSTALL_DIR` during `launch` phase?

Posted by Svetoslav Neykov <sv...@cloudsoftcorp.com>.
Hi Mike,
I believe you can do

shell.env:
    INSTALL_DIR: $brooklyn:attributeWhenReady("install.dir")

in the config section and use it in your launch phase as $INSTALL_DIR.

Svet.



> On 28.09.2015 г., at 18:30, Mike Zaccardo <mi...@cloudsoftcorp.com> wrote:
> 
> Hi all,
> 
> I'm working on a blueprint[1] in which I'd like the `launch` phase to
> invoke a start script that is added to `INSTALL_DIR`[2] during the
> `install` phase.
> 
> Right now I'm facing a problem because the `launch` phase executes in
> `RUN_DIR`[3], so the command fails since it cannot find the necessary
> script file.
> 
> Is there a way to reference the `INSTALL_DIR` value in the `launch` phase
> so I can get this to work?
> 
> Cheers,
> Mike
> 
> [1]
> https://github.com/mikezaccardo/brooklyn-zeppelin/blob/master/catalog.bom
> [2]
> INSTALL_DIR="/home/users/Mike/brooklyn-managed-processes/installs/VanillaSoftwareProcess_0.0.0"
> [3]
> RUN_DIR="/home/users/Mike/brooklyn-managed-processes/apps/nVmOMvpp/entities/VanillaSoftwareProcess_cMqHslpp"
> 
> -- 
> Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. 
> Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
> 
> This e-mail message is confidential and for use by the addressee only. If 
> the message is received by anyone other than the addressee, please return 
> the message to the sender by replying to it and then delete the message 
> from your computer. Internet e-mails are not necessarily secure. Cloudsoft 
> Corporation Limited does not accept responsibility for changes made to this 
> message after it was sent.
> 
> Whilst all reasonable care has been taken to avoid the transmission of 
> viruses, it is the responsibility of the recipient to ensure that the 
> onward transmission, opening or use of this message and any attachments 
> will not adversely affect its systems or data. No responsibility is 
> accepted by Cloudsoft Corporation Limited in this regard and the recipient 
> should carry out such virus and other checks as it considers appropriate.


-- 
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. 
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
 
This e-mail message is confidential and for use by the addressee only. If 
the message is received by anyone other than the addressee, please return 
the message to the sender by replying to it and then delete the message 
from your computer. Internet e-mails are not necessarily secure. Cloudsoft 
Corporation Limited does not accept responsibility for changes made to this 
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of 
viruses, it is the responsibility of the recipient to ensure that the 
onward transmission, opening or use of this message and any attachments 
will not adversely affect its systems or data. No responsibility is 
accepted by Cloudsoft Corporation Limited in this regard and the recipient 
should carry out such virus and other checks as it considers appropriate.