git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Catalog items - Plans vs Configs


Geoff,

I think there are a few options here for Duncan that we could implement:

1. If debugging (or debug log level is set) is enabled, be less aggressive
with GC of sensor data
2. Make GC timing and aggressiveness globally configurable
3. Make certain sensors non GCable by adding a sensor property to configure
them
4. Disable GC when en entity is on fire or other error condition occurs

WDYT? I think 4. is a good solution, but not sure how simple any of them
would be to implement?

Andrew.

On Thu, 7 Jun 2018 at 09:53 Geoff Macartney <geoff.macartney@xxxxxxxxxxxx>
wrote:

> Duncan,
>
> This is a normal behaviour with Brooklyn, as it doesn't retain the
> stdin/out/errs indefinitely. There have been discussions in the past about
> this but I don't think there was any consensus for particular changes to
> make.  Brooklyn developers, maybe it would be a good time to think about
> this again?
>
> Regards
> Geoff
>
> On Tue, 5 Jun 2018 at 23:51 Duncan Johnston-Watt <duncan@xxxxxxxxxxxxxxxx>
> wrote:
>
> > Not entirely unrelated but the discrepancy between the plan/config
> caused a
> > problem that was them compounded because by the time I was able to
> inspect
> > the live model *stderr* had been garbage collected even though the item
> in
> > question was on fire.
> >
> > If there is any issue deploying a blueprint garbage collecting the
> evidence
> > is the last thing Brooklyn should do.
> >
> > Best
> >
> > Duncan
> >
> > On Tue, Jun 5, 2018 at 10:28 PM, Duncan Johnston-Watt <
> > duncan@xxxxxxxxxxxxxxxx> wrote:
> >
> > > This is probably obvious to everyone else but when I inspect
> applications
> > > preloaded in a catalog I can see both a Plan and a Config associated
> with
> > > them.
> > >
> > > When I use +Application and select the catalog item corresponding to
> such
> > > an application I have two options -
> > >
> > > *Next (Wizard view)*
> > > Here the params are completed using the *Config* and unless I want to
> > > change them all I do at that point is select a location then deploy.
> > >
> > > *YAML Composer*
> > > Here I am presented with the *Plan* and have to add name/location etc.
> in
> > > the editor.
> > >
> > > Is this behaviour written up somewhere?
> > >
> > > Best
> > > --
> > > Duncan Johnston-Watt
> > > CEO, Blockchain Technology Partners <http://blockchaintp.com/>
> > >
> > > Twitter: @duncanjw <https://twitter.com/duncanjw>
> > > Mob: +44 777 190 2653 <07771%20902653> <+44%207771%20902653>
> <+44%207771%20902653>
> > > LinkedIn: https://linkedin.com/in/duncanjohnstonwatt
> > >
> > >
> >
> >
> > --
> > Duncan Johnston-Watt
> > CEO, Blockchain Technology Partners <http://blockchaintp.com/>
> >
> > Twitter: @duncanjw <https://twitter.com/duncanjw>
> > Mob: +44 777 190 2653 <07771%20902653> <+44%207771%20902653>
> <+44%207771%20902653>
> > LinkedIn: https://linkedin.com/in/duncanjohnstonwatt
> >
>
-- 

Andrew Kennedy ; Hyperledger Sawtooth / Apache Brooklyn ; @grkvlt ;
Cloudsoft Corporation Limited