You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by Duncan Johnston-Watt <du...@blockchaintp.com> on 2018/06/05 21:28:45 UTC
Catalog items - Plans vs Configs
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 <+44%207771%20902653>
LinkedIn: https://linkedin.com/in/duncanjohnstonwatt
Re: Catalog items - Plans vs Configs
Posted by Geoff Macartney <ge...@cloudsoft.io>.
Ah, sorry Duncan, will add that to the issue!
Cheers
Geoff
On Thu, 7 Jun 2018 at 12:29 Duncan Johnston-Watt <du...@blockchaintp.com>
wrote:
> Geoff
>
> Thanks. I followed the document link you suggested but when I clicked on
> the embedded Catalog link[1] I discovered that this was broken. Maybe to
> Tool tips for "YAML Composer" and "Next" (Wizard) could be more specific in
> terms of where they get parameters from?
>
> [1] http://brooklyn.apache.org/v/latest/ops/catalog/
>
> Best
>
> Duncan
>
> On Thu, Jun 7, 2018 at 9:49 AM, Geoff Macartney <
> geoff.macartney@cloudsoft.io> wrote:
>
> > Hi Duncan
> >
> > there is some documentation at [1], but maybe not enough detail.
> >
> > I have raised the issue [2] to do something about this.
> >
> > Regards
> > Geoff
> > [1]
> > http://brooklyn.apache.org/v/latest/ops/gui/blueprints.
> > html#launching-from-the-catalog
> > [2] https://issues.apache.org/jira/browse/BROOKLYN-591
> >
> >
> > On Tue, 5 Jun 2018 at 22:28 Duncan Johnston-Watt <
> duncan@blockchaintp.com>
> > 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 <+44%207771%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 <+44%207771%20902653> <+44%207771%20902653>
> LinkedIn: https://linkedin.com/in/duncanjohnstonwatt
>
Re: Catalog items - Plans vs Configs
Posted by Duncan Johnston-Watt <du...@blockchaintp.com>.
Geoff
Thanks. I followed the document link you suggested but when I clicked on
the embedded Catalog link[1] I discovered that this was broken. Maybe to
Tool tips for "YAML Composer" and "Next" (Wizard) could be more specific in
terms of where they get parameters from?
[1] http://brooklyn.apache.org/v/latest/ops/catalog/
Best
Duncan
On Thu, Jun 7, 2018 at 9:49 AM, Geoff Macartney <
geoff.macartney@cloudsoft.io> wrote:
> Hi Duncan
>
> there is some documentation at [1], but maybe not enough detail.
>
> I have raised the issue [2] to do something about this.
>
> Regards
> Geoff
> [1]
> http://brooklyn.apache.org/v/latest/ops/gui/blueprints.
> html#launching-from-the-catalog
> [2] https://issues.apache.org/jira/browse/BROOKLYN-591
>
>
> On Tue, 5 Jun 2018 at 22:28 Duncan Johnston-Watt <du...@blockchaintp.com>
> 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 <+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 <+44%207771%20902653>
LinkedIn: https://linkedin.com/in/duncanjohnstonwatt
Re: Catalog items - Plans vs Configs
Posted by Geoff Macartney <ge...@cloudsoft.io>.
Hi Duncan
there is some documentation at [1], but maybe not enough detail.
I have raised the issue [2] to do something about this.
Regards
Geoff
[1]
http://brooklyn.apache.org/v/latest/ops/gui/blueprints.html#launching-from-the-catalog
[2] https://issues.apache.org/jira/browse/BROOKLYN-591
On Tue, 5 Jun 2018 at 22:28 Duncan Johnston-Watt <du...@blockchaintp.com>
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 <+44%207771%20902653> <+44%207771%20902653>
> LinkedIn: https://linkedin.com/in/duncanjohnstonwatt
>
Re: Catalog items - Plans vs Configs
Posted by Duncan Johnston-Watt <du...@blockchaintp.com>.
Andrew
Option #4 gets my vote as that is when it matters most. Appreciate it might
not be that simple in practice.
Best
Duncan
On Thu, Jun 7, 2018 at 11:06 AM, Andrew Kennedy <
andrew.kennedy@cloudsoftcorp.com> wrote:
> 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 <ge...@cloudsoft.io>
> 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@blockchaintp.com>
> > 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@blockchaintp.com> 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
>
--
Duncan Johnston-Watt
CEO, Blockchain Technology Partners <http://blockchaintp.com/>
Twitter: @duncanjw <https://twitter.com/duncanjw>
Mob: +44 777 190 2653 <+44%207771%20902653>
LinkedIn: https://linkedin.com/in/duncanjohnstonwatt
Re: Catalog items - Plans vs Configs
Posted by Andrew Kennedy <an...@cloudsoftcorp.com>.
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 <ge...@cloudsoft.io>
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 <du...@blockchaintp.com>
> 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@blockchaintp.com> 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
Re: Catalog items - Plans vs Configs
Posted by Geoff Macartney <ge...@cloudsoft.io>.
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 <du...@blockchaintp.com>
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@blockchaintp.com> 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 <+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 <+44%207771%20902653> <+44%207771%20902653>
> LinkedIn: https://linkedin.com/in/duncanjohnstonwatt
>
Re: Catalog items - Plans vs Configs
Posted by Duncan Johnston-Watt <du...@blockchaintp.com>.
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@blockchaintp.com> 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 <+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 <+44%207771%20902653>
LinkedIn: https://linkedin.com/in/duncanjohnstonwatt