Hello Seth,
And just to offer an open source alternative to Pavlin’s suggestion, you can
also take a look at the Apache ACE project, which provides a provisioning
solution that provides a server and a management agent based on the Deployment
Admin specification.
http://ace.apache.org/
Greetings, Marcel
On 9 December 2015 at 06:56:01, Dr. Pavlin Dobrev (p.dob...@prosyst.com) wrote:
Hi Seth,
You can find more information:
http://mprm.cloud.prosyst.com/docs/osgidm/conceptual/initial_provisioning_conceptual.html
Regarding the back-end part - Here is info our implementation of Software
Repository:
http://mprm.cloud.prosyst.com/docs/softwarerepository/conceptual/softwarerepositoryprinciples.html
p.s. Initial Provisioning bundle in eclipse is a subset of ProSyst
implementation. I delivered it to equinox few years ago:
https://www.eclipse.org/equinox/bundles/ (Initial Provisioning
(org.eclipse.equinox.ip)
An implementation of the OSGi R4 Initial Provisioning. This service Defines how
the Management Agent can make its way to the Service Platform, and gives a
structured view of the problems and their corresponding resolution methods.)
Mit freundlichen Grüßen / Best regards
Dr. Pavlin Dobrev
ProSyst Software GmbH
Research and Development Manager
Aachener Str. 222
50931 Cologne
Germany
www.prosyst.com
Tel. (+359 2) 954 91 62
Fax. (+359 2) 953 26 17
p.dob...@prosyst.com
Registered office: Köln, Register court: Amtsgericht Köln HRB 54586
Executives: Dr. Rainer Kallenbach, Thomas Hott, Daniel Schellhoss, Dr. Dimitar
Valtchev
On 12/9/2015 1:46 AM, Seth Lana wrote:
Hello,
I'm researching about the best ways to provide automatic remote provisioning
for small devices and also for the servers that will provide content for such
devices.
Reading the OSGi compendium, some specs caught my attention: Initial
Provisioning, Deployment Admin, Subsystems and Repository Services.
If I got it right, we can have an device with only the OSGi container(with a
minimal deps) and the IP Agent bundle jars assembled at factory.
At first use, the IP agent will contact the remote provisioning service (using
Http or another protocol) and will download one or more IP zip files containing
one or more bundles and configuration files defined by the remote provisioning
operator for that device.
All bundles inside the IP zips will be installed by the IP agent. So, this
process follows until all necessary bundles are installed, ending with the
Management Agent bundle being started. Am I right?
What I found strange was the fact that only one bundle can be started at each
time (each zip can have only one start entry pointing to only one bundle). Why
this restriction?
Should the Management Agent uninstall the IP agent after it is fully
operational? or the IP must run every time the device starts up ?
But the biggest doubt is about that Management Agent itself. It seems that one
needs to be developed, right?.
Should the Management Agent to use a Deployment Admin service provided by
another bundle or should it be itself the provider of such service?
And about the Repository Service, should it be used by the Management Agent or
Deployment Admin or both?
Can a Subsystem (.esa) be package inside a Deployment Package?
Can the Deployment Packages (*.dp) or Subsystems (*.esa) also be provided by an
OSGi repository ?
thanks for any opinion.
regards, Seth.
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
