brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-93) Entity is removed from the gui after being stopped
Date Wed, 26 Nov 2014 14:22:12 GMT


Aled Sage commented on BROOKLYN-93:

Ah, I misread - thought you were stopping brooklyn as well.

If you stop the top-level app (i.e. the entire blueprint), then that destroys it entirely,
freeing all resources. i.e. it is "unmanaged" and removed from AMP.
This should include stopping the installed app (i.e. no processes left running), but the installation
artifacts will be left.

If you stop entities contained within an app, then you are free to subsequently restart those

<I don't particularly like that difference (between stop at the top level and a sub-entity),
but it has proven simple to use so far (once you know the behaviour at least!) so on balance
I'm ok with it (versus the user having to explicitly expunge applications that they have stopped).>

For the persistence/rebind - I agree with your approach.
My concern is whether this (and downstream projects) have enough integration tests of "rebind"
for us to have confidence it will all work. We need to add more for various entities, I believe
- especially for downstream projects. Let's aim to get tests working with rebind, and ensure
our test coverage is good for this before we switch over!

> Entity is removed from the gui after being stopped
> --------------------------------------------------
>                 Key: BROOKLYN-93
>                 URL:
>             Project: Brooklyn
>          Issue Type: Bug
>    Affects Versions: 0.7.0-M1
>            Reporter: Hadrian Zbarcea
> I started ActiveMQ from the gui using a simple yaml, the basic stuff, all works fine.
However, if I stop it from the gui (stops fine) it is also removed from the gui with no possibility
to restart. The installed app is not removed from the target location (which is I assume expected).
> Is this the intended behavior? I would suspect not.

This message was sent by Atlassian JIRA

View raw message