[Aries Subsystem] initial provisioning with subsystems ?

[Cristiano Gavião <cv...@gmail.com>]

Hello,

I've been playing with Aries Subsystem for some time. In all my experiments
I install the .esa artifacts using console commands that delegate to the
subsystem service.

Now I would like to experiment with a deliverable product that embeds some
.esa files.

So, how would be the best strategy to deal with such case?

thanks for any tip.

Cristiano

Re: [Aries Subsystem] initial provisioning with subsystems ?

[Cristiano Gavião <cv...@gmail.com>]

Hi Stephan, thanks for the info sharing.

We have played with FileInstall but we decided to go to another path too.
Local files didn't support our expectations.
Right now we are testing the Initial Provisioning spec. There is a
implementation in org.eclipse.equinox.ip. we are trying to create a
solutions using it and Aether to get the artifacts remotely.

best,

Cristiano



2013/8/19 Siano, Stephan <st...@sap.com>

>  Hi,****
>
> ** **
>
> We have also tried to go that path, however this thing seems to be
> orphaned. It cannot be built with the released version of the subsystem
> implementation, however we are currently trying to fix this for our own
> little implementation.****
>
> ** **
>
> Unfortunately it is rather difficult to find out whether a file is a
> subsystem artifact or not (both the .esa extension and the subsystem
> manifest are optional). We have made the installer feel responsible for all
> .esa files, which is fine for our test purposes. Also the logic when to
> start a subsystem (especially after an update is not clean there).****
>
> ** **
>
> Best regards****
>
> Stephan****
>
> ** **
>
> *From:* Cristiano Gavião [mailto:cvgaviao@gmail.com]
> *Sent:* Sonntag, 18. August 2013 17:48
> *To:* user@aries.apache.org
> *Subject:* Re: [Aries Subsystem] initial provisioning with subsystems ?***
> *
>
> ** **
>
> Well, I could find the solution...  :)****
>
> aries subsystem provides the bundle org.apache.aries.subsystem.install
> that provides an implementation of
> org.apache.felix.fileinstall.ArtifactInstaller.****
>
> So I just needed to setup fileinstall properly.****
>
> regards,****
>
> Cristiano****
>
> ** **
>
> 2013/8/18 Cristiano Gavião <cv...@gmail.com>****
>
> Hello,****
>
> I've been playing with Aries Subsystem for some time. In all my
> experiments I install the .esa artifacts using console commands that
> delegate to the subsystem service.****
>
> ** **
>
> Now I would like to experiment with a deliverable product that embeds some
> .esa files.****
>
> So, how would be the best strategy to deal with such case?
>
> thanks for any tip.****
>
> Cristiano
> ****
>
> ** **
>
>
>
>
> --
> "Tudo vale a pena se a alma não é pequena..." ****
>



-- 
"Tudo vale a pena se a alma não é pequena..."

Re: [Aries Subsystem] initial provisioning with subsystems ?

[Cristiano Gavião <cv...@gmail.com>]

Yep, I was with that impression when I didn't see the subsystem-install in
the maven central repository.




2013/8/19 John W Ross <jw...@us.ibm.com>

> The following subsystems related projects in SVN are currently not
> maintained and might be deleted in the future (particularly
> subsystem-scope-* as this is obsolete functionality).
>
> subsystem-example
> subsystem-executor
> subsystem-install
> subsystem-scope-*
>
> If subsystem-install is providing value, please feel free to offer any
> contributions that have made it so.
>
> With regard to identifying subsystem files, note that there is also a
> reserved MIME type: application/vnd.osgi.subsystem.
>
> John
>
>
> >
> > RE: [Aries Subsystem] initial provisioning with subsystems ?
>
> >
> > Hi,
> >
> > We have also tried to go that path, however this thing seems to be
> > orphaned. It cannot be built with the released version of the
> > subsystem implementation, however we are currently trying to fix
> > this for our own little implementation.
> >
> > Unfortunately it is rather difficult to find out whether a file is a
> > subsystem artifact or not (both the .esa extension and the subsystem
> > manifest are optional). We have made the installer feel responsible
> > for all .esa files, which is fine for our test purposes. Also the
> > logic when to start a subsystem (especially after an update is not
> > clean there).
> >
> > Best regards
> > Stephan
> >
> > From: Cristiano Gavião [mailto:cvgaviao@gmail.com <cv...@gmail.com>]
> > Sent: Sonntag, 18. August 2013 17:48
> > To: user@aries.apache.org
> > Subject: Re: [Aries Subsystem] initial provisioning with subsystems ?
> >
> > Well, I could find the solution...  :)
> > aries subsystem provides the bundle
> > org.apache.aries.subsystem.install that provides an implementation
> > of org.apache.felix.fileinstall.ArtifactInstaller.
> > So I just needed to setup fileinstall properly.
> > regards,
> > Cristiano
> >
> > 2013/8/18 Cristiano Gavião <cv...@gmail.com>
> > Hello,
> > I've been playing with Aries Subsystem for some time. In all my
> > experiments I install the .esa artifacts using console commands that
> > delegate to the subsystem service.
> >
> > Now I would like to experiment with a deliverable product that
> > embeds some .esa files.
> > So, how would be the best strategy to deal with such case?
> >
> > thanks for any tip.
> > Cristiano
> >
> >
> >
> >
> > --
> > "Tudo vale a pena se a alma não é pequena..."
>
>


-- 
"Tudo vale a pena se a alma não é pequena..."

Re: [Aries Subsystem] initial provisioning with subsystems ?

[Cristiano Gavião <cv...@gmail.com>]

Stephan,

I think that you could use the MiME type when you are creating the .esa
file.

The Zip api let you set this kind of header information in the generated
artifact.

regards,

Cristiano


2013/8/20 Siano, Stephan <st...@sap.com>

>  Hi John,****
>
> ** **
>
> How do I get the MIME type from the
> org.apache.felix.fileinstall.ArtifactInstaller interface? Furthermore I am
> not sure whether this really belongs to Aries-Subsystems as (at least our
> implementation) has only references to felix-fileinstall and the osgi
> enterprise spec (but not to the aries implementation). ****
>
> ** **
>
> I can post it here or contribute it, but I am not sure whether this is
> interesting enough for it (and the implementation of the canHandle method
> is far from perfect.****
>
> ** **
>
> Best regards****
>
> Stephan****
>
> ** **
>
> *From:* John W Ross [mailto:jwross@us.ibm.com]
> *Sent:* Montag, 19. August 2013 14:55
> *To:* user@aries.apache.org
> *Subject:* RE: [Aries Subsystem] initial provisioning with subsystems ?***
> *
>
> ** **
>
> The following subsystems related projects in SVN are currently not
> maintained and might be deleted in the future (particularly
> subsystem-scope-* as this is obsolete functionality).
>
> subsystem-example
> subsystem-executor
> subsystem-install
> subsystem-scope-*
>
> If subsystem-install is providing value, please feel free to offer any
> contributions that have made it so.
>
> With regard to identifying subsystem files, note that there is also a
> reserved MIME type: application/vnd.osgi.subsystem.
>
> John
>
>
> >
> > RE: [Aries Subsystem] initial provisioning with subsystems ?
> >
> > Hi,
> >
> > We have also tried to go that path, however this thing seems to be
> > orphaned. It cannot be built with the released version of the
> > subsystem implementation, however we are currently trying to fix
> > this for our own little implementation.
> >
> > Unfortunately it is rather difficult to find out whether a file is a
> > subsystem artifact or not (both the .esa extension and the subsystem
> > manifest are optional). We have made the installer feel responsible
> > for all .esa files, which is fine for our test purposes. Also the
> > logic when to start a subsystem (especially after an update is not
> > clean there).
> >
> > Best regards
> > Stephan
> >
> > From: Cristiano Gavião [mailto:cvgaviao@gmail.com <cv...@gmail.com>]
> > Sent: Sonntag, 18. August 2013 17:48
> > To: user@aries.apache.org
> > Subject: Re: [Aries Subsystem] initial provisioning with subsystems ?
> >
> > Well, I could find the solution...  :)
> > aries subsystem provides the bundle
> > org.apache.aries.subsystem.install that provides an implementation
> > of org.apache.felix.fileinstall.ArtifactInstaller.
> > So I just needed to setup fileinstall properly.
> > regards,
> > Cristiano
> >
> > 2013/8/18 Cristiano Gavião <cv...@gmail.com>
> > Hello,
> > I've been playing with Aries Subsystem for some time. In all my
> > experiments I install the .esa artifacts using console commands that
> > delegate to the subsystem service.
> >
> > Now I would like to experiment with a deliverable product that
> > embeds some .esa files.
> > So, how would be the best strategy to deal with such case?
> >
> > thanks for any tip.
> > Cristiano
> >
> >
> >
> >
> > --
> > "Tudo vale a pena se a alma não é pequena..." ****
>



-- 
"Tudo vale a pena se a alma não é pequena..."

RE: [Aries Subsystem] initial provisioning with subsystems ?

["Siano, Stephan" <st...@sap.com>]

Hi John,

The subsystem-install in the svn is completely broken - it doesn't even compile. ArtifactInstaller is the interface installers for the felix file installer need to provide. The question about the MIME-Type means the following:
The felix file installer installs file. How do I get this MIME-Type from a file in the file system?

The implementation does not have any hard dependencies to any subsystem implementation it just uses the OSGi subsystem API (essentially it references the root subsystem as a service and installs all subsystems into that). I am not sure how useful our code is. We only use it for test purposes, so we have no tests and the whole thing is about 50 lines of code (plus one blueprint descriptor).

Best regards
Stephan

From: John W Ross [mailto:jwross@us.ibm.com]
Sent: Mittwoch, 21. August 2013 14:41
To: user@aries.apache.org
Subject: RE: [Aries Subsystem] initial provisioning with subsystems ?


Hi Stephan,

>
> RE: [Aries Subsystem] initial provisioning with subsystems ?
>
> Hi John,
>
> How do I get the MIME type from the
> org.apache.felix.fileinstall.ArtifactInstaller interface?

I don't think I've ever even looked at subsystem-install. It's basically a relic from an initial subsystems POC a few years ago. I'm even less familiar with ArtifactInstaller.

> Furthermore I am not sure whether this really belongs to Aries-
> Subsystems as (at least our implementation) has only references to
> felix-fileinstall and the osgi enterprise spec (but not to the aries
> implementation).

If you mean you have hard dependencies on some other subsystems implementation, then you're right. If you mean you just use the OSGi Subsystems API without caring about the underlying implementation, then that should be okay.

>
> I can post it here or contribute it, but I am not sure whether this
> is interesting enough for it (and the implementation of the
> canHandle method is far from perfect.

It's up to you. If you think others could benefit from the work, and are willing to agree to the Apache license, then you may wish to consider it. I'm completely in the dark about what the state of subsystem-install was before your work. If it was completely broken and useless, then a contribution might be particularly helpful. If you do decide you might want to contribute something, I'd recommend opening up a JIRA for discussion.

>
> Best regards
> Stephan
>
> From: John W Ross [mailto:jwross@us.ibm.com]
> Sent: Montag, 19. August 2013 14:55
> To: user@aries.apache.org<ma...@aries.apache.org>
> Subject: RE: [Aries Subsystem] initial provisioning with subsystems ?
>
> The following subsystems related projects in SVN are currently not
> maintained and might be deleted in the future (particularly
> subsystem-scope-* as this is obsolete functionality).
>
> subsystem-example
> subsystem-executor
> subsystem-install
> subsystem-scope-*
>
> If subsystem-install is providing value, please feel free to offer
> any contributions that have made it so.
>
> With regard to identifying subsystem files, note that there is also
> a reserved MIME type: application/vnd.osgi.subsystem.
>
> John
>
>
> >
> > RE: [Aries Subsystem] initial provisioning with subsystems ?
> >
> > Hi,
> >
> > We have also tried to go that path, however this thing seems to be
> > orphaned. It cannot be built with the released version of the
> > subsystem implementation, however we are currently trying to fix
> > this for our own little implementation.
> >
> > Unfortunately it is rather difficult to find out whether a file is a
> > subsystem artifact or not (both the .esa extension and the subsystem
> > manifest are optional). We have made the installer feel responsible
> > for all .esa files, which is fine for our test purposes. Also the
> > logic when to start a subsystem (especially after an update is not
> > clean there).
> >
> > Best regards
> > Stephan
> >
> > From: Cristiano Gavião [mailto:cvgaviao@gmail.com]
> > Sent: Sonntag, 18. August 2013 17:48
> > To: user@aries.apache.org<ma...@aries.apache.org>
> > Subject: Re: [Aries Subsystem] initial provisioning with subsystems ?
> >
> > Well, I could find the solution...  :)
> > aries subsystem provides the bundle
> > org.apache.aries.subsystem.install that provides an implementation
> > of org.apache.felix.fileinstall.ArtifactInstaller.
> > So I just needed to setup fileinstall properly.
> > regards,
> > Cristiano
> >
> > 2013/8/18 Cristiano Gavião <cv...@gmail.com>>
> > Hello,
> > I've been playing with Aries Subsystem for some time. In all my
> > experiments I install the .esa artifacts using console commands that
> > delegate to the subsystem service.
> >
> > Now I would like to experiment with a deliverable product that
> > embeds some .esa files.
> > So, how would be the best strategy to deal with such case?
> >
> > thanks for any tip.
> > Cristiano
> >
> >
> >
> >
> > --
> > "Tudo vale a pena se a alma não é pequena..."

RE: [Aries Subsystem] initial provisioning with subsystems ?

[John W Ross <jw...@us.ibm.com>]

Hi Stephan,

>
> RE: [Aries Subsystem] initial provisioning with subsystems ?
>
> Hi John,
>
> How do I get the MIME type from the
> org.apache.felix.fileinstall.ArtifactInstaller interface?

I don't think I've ever even looked at subsystem-install. It's basically a
relic from an initial subsystems POC a few years ago. I'm even less
familiar with ArtifactInstaller.

> Furthermore I am not sure whether this really belongs to Aries-
> Subsystems as (at least our implementation) has only references to
> felix-fileinstall and the osgi enterprise spec (but not to the aries
> implementation).

If you mean you have hard dependencies on some other subsystems
implementation, then you're right. If you mean you just use the OSGi
Subsystems API without caring about the underlying implementation, then
that should be okay.

>
> I can post it here or contribute it, but I am not sure whether this
> is interesting enough for it (and the implementation of the
> canHandle method is far from perfect.

It's up to you. If you think others could benefit from the work, and are
willing to agree to the Apache license, then you may wish to consider it.
I'm completely in the dark about what the state of subsystem-install was
before your work. If it was completely broken and useless, then a
contribution might be particularly helpful. If you do decide you might want
to contribute something, I'd recommend opening up a JIRA for discussion.

>
> Best regards
> Stephan
>
> From: John W Ross [mailto:jwross@us.ibm.com]
> Sent: Montag, 19. August 2013 14:55
> To: user@aries.apache.org
> Subject: RE: [Aries Subsystem] initial provisioning with subsystems ?
>
> The following subsystems related projects in SVN are currently not
> maintained and might be deleted in the future (particularly
> subsystem-scope-* as this is obsolete functionality).
>
> subsystem-example
> subsystem-executor
> subsystem-install
> subsystem-scope-*
>
> If subsystem-install is providing value, please feel free to offer
> any contributions that have made it so.
>
> With regard to identifying subsystem files, note that there is also
> a reserved MIME type: application/vnd.osgi.subsystem.
>
> John
>
>
> >
> > RE: [Aries Subsystem] initial provisioning with subsystems ?
> >
> > Hi,
> >
> > We have also tried to go that path, however this thing seems to be
> > orphaned. It cannot be built with the released version of the
> > subsystem implementation, however we are currently trying to fix
> > this for our own little implementation.
> >
> > Unfortunately it is rather difficult to find out whether a file is a
> > subsystem artifact or not (both the .esa extension and the subsystem
> > manifest are optional). We have made the installer feel responsible
> > for all .esa files, which is fine for our test purposes. Also the
> > logic when to start a subsystem (especially after an update is not
> > clean there).
> >
> > Best regards
> > Stephan
> >
> > From: Cristiano Gavião [mailto:cvgaviao@gmail.com]
> > Sent: Sonntag, 18. August 2013 17:48
> > To: user@aries.apache.org
> > Subject: Re: [Aries Subsystem] initial provisioning with subsystems ?
> >
> > Well, I could find the solution...  :)
> > aries subsystem provides the bundle
> > org.apache.aries.subsystem.install that provides an implementation
> > of org.apache.felix.fileinstall.ArtifactInstaller.
> > So I just needed to setup fileinstall properly.
> > regards,
> > Cristiano
> >
> > 2013/8/18 Cristiano Gavião <cv...@gmail.com>
> > Hello,
> > I've been playing with Aries Subsystem for some time. In all my
> > experiments I install the .esa artifacts using console commands that
> > delegate to the subsystem service.
> >
> > Now I would like to experiment with a deliverable product that
> > embeds some .esa files.
> > So, how would be the best strategy to deal with such case?
> >
> > thanks for any tip.
> > Cristiano
> >
> >
> >
> >
> > --
> > "Tudo vale a pena se a alma não é pequena..."

RE: [Aries Subsystem] initial provisioning with subsystems ?

["Siano, Stephan" <st...@sap.com>]

Hi John,

How do I get the MIME type from the org.apache.felix.fileinstall.ArtifactInstaller interface? Furthermore I am not sure whether this really belongs to Aries-Subsystems as (at least our implementation) has only references to felix-fileinstall and the osgi enterprise spec (but not to the aries implementation).

I can post it here or contribute it, but I am not sure whether this is interesting enough for it (and the implementation of the canHandle method is far from perfect.

Best regards
Stephan

From: John W Ross [mailto:jwross@us.ibm.com]
Sent: Montag, 19. August 2013 14:55
To: user@aries.apache.org
Subject: RE: [Aries Subsystem] initial provisioning with subsystems ?


The following subsystems related projects in SVN are currently not maintained and might be deleted in the future (particularly subsystem-scope-* as this is obsolete functionality).

subsystem-example
subsystem-executor
subsystem-install
subsystem-scope-*

If subsystem-install is providing value, please feel free to offer any contributions that have made it so.

With regard to identifying subsystem files, note that there is also a reserved MIME type: application/vnd.osgi.subsystem.

John


>
> RE: [Aries Subsystem] initial provisioning with subsystems ?
>
> Hi,
>
> We have also tried to go that path, however this thing seems to be
> orphaned. It cannot be built with the released version of the
> subsystem implementation, however we are currently trying to fix
> this for our own little implementation.
>
> Unfortunately it is rather difficult to find out whether a file is a
> subsystem artifact or not (both the .esa extension and the subsystem
> manifest are optional). We have made the installer feel responsible
> for all .esa files, which is fine for our test purposes. Also the
> logic when to start a subsystem (especially after an update is not
> clean there).
>
> Best regards
> Stephan
>
> From: Cristiano Gavião [mailto:cvgaviao@gmail.com]
> Sent: Sonntag, 18. August 2013 17:48
> To: user@aries.apache.org<ma...@aries.apache.org>
> Subject: Re: [Aries Subsystem] initial provisioning with subsystems ?
>
> Well, I could find the solution...  :)
> aries subsystem provides the bundle
> org.apache.aries.subsystem.install that provides an implementation
> of org.apache.felix.fileinstall.ArtifactInstaller.
> So I just needed to setup fileinstall properly.
> regards,
> Cristiano
>
> 2013/8/18 Cristiano Gavião <cv...@gmail.com>>
> Hello,
> I've been playing with Aries Subsystem for some time. In all my
> experiments I install the .esa artifacts using console commands that
> delegate to the subsystem service.
>
> Now I would like to experiment with a deliverable product that
> embeds some .esa files.
> So, how would be the best strategy to deal with such case?
>
> thanks for any tip.
> Cristiano
>
>
>
>
> --
> "Tudo vale a pena se a alma não é pequena..."

RE: [Aries Subsystem] initial provisioning with subsystems ?

[John W Ross <jw...@us.ibm.com>]

The following subsystems related projects in SVN are currently not
maintained and might be deleted in the future (particularly
subsystem-scope-* as this is obsolete functionality).

subsystem-example
subsystem-executor
subsystem-install
subsystem-scope-*

If subsystem-install is providing value, please feel free to offer any
contributions that have made it so.

With regard to identifying subsystem files, note that there is also a
reserved MIME type: application/vnd.osgi.subsystem.

John


>
> RE: [Aries Subsystem] initial provisioning with subsystems ?
>
> Hi,
>
> We have also tried to go that path, however this thing seems to be
> orphaned. It cannot be built with the released version of the
> subsystem implementation, however we are currently trying to fix
> this for our own little implementation.
>
> Unfortunately it is rather difficult to find out whether a file is a
> subsystem artifact or not (both the .esa extension and the subsystem
> manifest are optional). We have made the installer feel responsible
> for all .esa files, which is fine for our test purposes. Also the
> logic when to start a subsystem (especially after an update is not
> clean there).
>
> Best regards
> Stephan
>
> From: Cristiano Gavião [mailto:cvgaviao@gmail.com]
> Sent: Sonntag, 18. August 2013 17:48
> To: user@aries.apache.org
> Subject: Re: [Aries Subsystem] initial provisioning with subsystems ?
>
> Well, I could find the solution...  :)
> aries subsystem provides the bundle
> org.apache.aries.subsystem.install that provides an implementation
> of org.apache.felix.fileinstall.ArtifactInstaller.
> So I just needed to setup fileinstall properly.
> regards,
> Cristiano
>
> 2013/8/18 Cristiano Gavião <cv...@gmail.com>
> Hello,
> I've been playing with Aries Subsystem for some time. In all my
> experiments I install the .esa artifacts using console commands that
> delegate to the subsystem service.
>
> Now I would like to experiment with a deliverable product that
> embeds some .esa files.
> So, how would be the best strategy to deal with such case?
>
> thanks for any tip.
> Cristiano
>
>
>
>
> --
> "Tudo vale a pena se a alma não é pequena..."

RE: [Aries Subsystem] initial provisioning with subsystems ?

["Siano, Stephan" <st...@sap.com>]

Hi,

We have also tried to go that path, however this thing seems to be orphaned. It cannot be built with the released version of the subsystem implementation, however we are currently trying to fix this for our own little implementation.

Unfortunately it is rather difficult to find out whether a file is a subsystem artifact or not (both the .esa extension and the subsystem manifest are optional). We have made the installer feel responsible for all .esa files, which is fine for our test purposes. Also the logic when to start a subsystem (especially after an update is not clean there).

Best regards
Stephan

From: Cristiano Gavião [mailto:cvgaviao@gmail.com]
Sent: Sonntag, 18. August 2013 17:48
To: user@aries.apache.org
Subject: Re: [Aries Subsystem] initial provisioning with subsystems ?

Well, I could find the solution...  :)
aries subsystem provides the bundle org.apache.aries.subsystem.install that provides an implementation of org.apache.felix.fileinstall.ArtifactInstaller.
So I just needed to setup fileinstall properly.
regards,
Cristiano

2013/8/18 Cristiano Gavião <cv...@gmail.com>>
Hello,
I've been playing with Aries Subsystem for some time. In all my experiments I install the .esa artifacts using console commands that delegate to the subsystem service.

Now I would like to experiment with a deliverable product that embeds some .esa files.
So, how would be the best strategy to deal with such case?

thanks for any tip.
Cristiano




--
"Tudo vale a pena se a alma não é pequena..."

Re: [Aries Subsystem] initial provisioning with subsystems ?

[Cristiano Gavião <cv...@gmail.com>]

Well, I could find the solution...  :)

aries subsystem provides the bundle org.apache.aries.subsystem.install that
provides an implementation of
org.apache.felix.fileinstall.ArtifactInstaller.

So I just needed to setup fileinstall properly.

regards,

Cristiano


2013/8/18 Cristiano Gavião <cv...@gmail.com>

> Hello,
>
> I've been playing with Aries Subsystem for some time. In all my
> experiments I install the .esa artifacts using console commands that
> delegate to the subsystem service.
>
> Now I would like to experiment with a deliverable product that embeds some
> .esa files.
>
> So, how would be the best strategy to deal with such case?
>
> thanks for any tip.
>
> Cristiano
>
>
>


-- 
"Tudo vale a pena se a alma não é pequena..."