You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by Svetoslav Neykov <sv...@cloudsoftcorp.com> on 2015/11/06 17:50:50 UTC
Creating a wrapper application for camp plans
Hi devs,
I propose that we change the rules for creating a wapper application for CAMP plans. There's an unexpected side effect presently where pointing to a catalog item and giving a top-level name to the plan will prevent unwrapping. It's surprising to users and even more so because it wasn't the case a few months ago.
For example the following catalog item:
brooklyn.catalog:
id: simpleApp
version: 1.0
displayName: Simple App
itemType: template
item:
services:
- type: my-simple-app
when started in the Application Wizard and given a name, equivalent to the following plan:
name: My App
services:
- type: "simpleApp:1.0"
will result in this hierarchy:
* My App (BasicApplication)
* Simple App (my-simple-app)
I propose that we change the logic such that the root level name will overwrite the child's name, so the hierarchy becomes:
* My App (my-simple-app)
There's a PR opened for this change at https://github.com/apache/incubator-brooklyn/pull/1007.
Svet.
Re: Creating a wrapper application for camp plans
Posted by Alex Heneveld <al...@cloudsoftcorp.com>.
+1
Best
Alex
On 6 Nov 2015 08:51, "Svetoslav Neykov" <sv...@cloudsoftcorp.com>
wrote:
> Hi devs,
>
> I propose that we change the rules for creating a wapper application for
> CAMP plans. There's an unexpected side effect presently where pointing to a
> catalog item and giving a top-level name to the plan will prevent
> unwrapping. It's surprising to users and even more so because it wasn't the
> case a few months ago.
>
> For example the following catalog item:
>
> brooklyn.catalog:
> id: simpleApp
> version: 1.0
> displayName: Simple App
> itemType: template
> item:
> services:
> - type: my-simple-app
>
> when started in the Application Wizard and given a name, equivalent to the
> following plan:
>
> name: My App
> services:
> - type: "simpleApp:1.0"
>
> will result in this hierarchy:
>
> * My App (BasicApplication)
> * Simple App (my-simple-app)
>
> I propose that we change the logic such that the root level name will
> overwrite the child's name, so the hierarchy becomes:
>
> * My App (my-simple-app)
>
>
> There's a PR opened for this change at
> https://github.com/apache/incubator-brooklyn/pull/1007.
>
> Svet.
>
>
>
Re: Creating a wrapper application for camp plans
Posted by Mike Zaccardo <mi...@cloudsoftcorp.com>.
+1 I ran into this when developing BDP and found it odd
On Mon, Nov 9, 2015, 01:57 John McCabe <jo...@johnmccabe.net> wrote:
> Much more concise, +1
>
> On Mon, 9 Nov 2015 at 09:33 Mark McKenna <ma...@cloudsoftcorp.com>
> wrote:
>
> > +1
> >
> > On Fri, 6 Nov 2015, 16:51 Svetoslav Neykov <
> > svetoslav.neykov@cloudsoftcorp.com> wrote:
> >
> > > Hi devs,
> > >
> > > I propose that we change the rules for creating a wapper application
> for
> > > CAMP plans. There's an unexpected side effect presently where pointing
> > to a
> > > catalog item and giving a top-level name to the plan will prevent
> > > unwrapping. It's surprising to users and even more so because it wasn't
> > the
> > > case a few months ago.
> > >
> > > For example the following catalog item:
> > >
> > > brooklyn.catalog:
> > > id: simpleApp
> > > version: 1.0
> > > displayName: Simple App
> > > itemType: template
> > > item:
> > > services:
> > > - type: my-simple-app
> > >
> > > when started in the Application Wizard and given a name, equivalent to
> > the
> > > following plan:
> > >
> > > name: My App
> > > services:
> > > - type: "simpleApp:1.0"
> > >
> > > will result in this hierarchy:
> > >
> > > * My App (BasicApplication)
> > > * Simple App (my-simple-app)
> > >
> > > I propose that we change the logic such that the root level name will
> > > overwrite the child's name, so the hierarchy becomes:
> > >
> > > * My App (my-simple-app)
> > >
> > >
> > > There's a PR opened for this change at
> > > https://github.com/apache/incubator-brooklyn/pull/1007.
> > >
> > > Svet.
> > >
> > >
> > >
> >
>
Re: Creating a wrapper application for camp plans
Posted by John McCabe <jo...@johnmccabe.net>.
Much more concise, +1
On Mon, 9 Nov 2015 at 09:33 Mark McKenna <ma...@cloudsoftcorp.com>
wrote:
> +1
>
> On Fri, 6 Nov 2015, 16:51 Svetoslav Neykov <
> svetoslav.neykov@cloudsoftcorp.com> wrote:
>
> > Hi devs,
> >
> > I propose that we change the rules for creating a wapper application for
> > CAMP plans. There's an unexpected side effect presently where pointing
> to a
> > catalog item and giving a top-level name to the plan will prevent
> > unwrapping. It's surprising to users and even more so because it wasn't
> the
> > case a few months ago.
> >
> > For example the following catalog item:
> >
> > brooklyn.catalog:
> > id: simpleApp
> > version: 1.0
> > displayName: Simple App
> > itemType: template
> > item:
> > services:
> > - type: my-simple-app
> >
> > when started in the Application Wizard and given a name, equivalent to
> the
> > following plan:
> >
> > name: My App
> > services:
> > - type: "simpleApp:1.0"
> >
> > will result in this hierarchy:
> >
> > * My App (BasicApplication)
> > * Simple App (my-simple-app)
> >
> > I propose that we change the logic such that the root level name will
> > overwrite the child's name, so the hierarchy becomes:
> >
> > * My App (my-simple-app)
> >
> >
> > There's a PR opened for this change at
> > https://github.com/apache/incubator-brooklyn/pull/1007.
> >
> > Svet.
> >
> >
> >
>
Re: Creating a wrapper application for camp plans
Posted by Mark McKenna <ma...@cloudsoftcorp.com>.
+1
On Fri, 6 Nov 2015, 16:51 Svetoslav Neykov <
svetoslav.neykov@cloudsoftcorp.com> wrote:
> Hi devs,
>
> I propose that we change the rules for creating a wapper application for
> CAMP plans. There's an unexpected side effect presently where pointing to a
> catalog item and giving a top-level name to the plan will prevent
> unwrapping. It's surprising to users and even more so because it wasn't the
> case a few months ago.
>
> For example the following catalog item:
>
> brooklyn.catalog:
> id: simpleApp
> version: 1.0
> displayName: Simple App
> itemType: template
> item:
> services:
> - type: my-simple-app
>
> when started in the Application Wizard and given a name, equivalent to the
> following plan:
>
> name: My App
> services:
> - type: "simpleApp:1.0"
>
> will result in this hierarchy:
>
> * My App (BasicApplication)
> * Simple App (my-simple-app)
>
> I propose that we change the logic such that the root level name will
> overwrite the child's name, so the hierarchy becomes:
>
> * My App (my-simple-app)
>
>
> There's a PR opened for this change at
> https://github.com/apache/incubator-brooklyn/pull/1007.
>
> Svet.
>
>
>