felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall" <he...@ungoverned.org>
Subject Re: Using OSGi as a provisioning and management platform for distributed components.
Date Fri, 20 Jan 2006 16:59:19 GMT
John E. Conlon wrote:
> The Provisioning spec doesn't dictate what happens with the state of the
> bundles already on the machine. Those bundle may not be effected with
> the start or stop of the provisioning service. It just offers it's
> service, loads one or more bundles, and starts one.  It's just a way to
> dynamically load and start something else: the management agent. 
>
> Now the management agent on the other hand, could like you suggested be
> totalitarian and stop and uninstall everything or it could, be a more
> mellow component like a shellTUI or a shellGUI or it could do fine
> grained tuning and orchestration of the other bundles. 
>
> I think of the Provisioning service like the foot in the door and the
> management agent as the salesperson;-)
>   

Well, if I understand correctly, then that gets back to the original 
point I made, which is there is no standard way to achieve the desired 
result, you just have to code your own custom management agent.

-> richard

> John
>
>  On Fri, 2006-01-20 at 10:05, Richard S. Hall wrote:
>   
>> I guess I was thinking that changes to a node would be more 
>> fine-grained, i.e., only some components would be added/updated/removed, 
>> and more uncoordinated. However, if the whole configuration just needs 
>> to be wiped out and reset by a central authority, then I agree it is 
>> probably possible to do so using the Initial Provisioning Service.
>>
>> -> richard
>>
>> John E. Conlon wrote:
>>     
>>> IMHO I think the Initial Provisioning Service would provide the standard
>>> infrastructure to do this.
>>>
>>>   
>>>       
>>>>> When each node starts up, it contacts to the configuration and component
>>>>> (bundle) repository and pulls its required components on the fly.  
>>>>>       
>>>>>           
>>> Alternately  if one were to use the Provisioning Service...when each
>>> node boots up it starts the Provisioning Service which then retrieves
>>> the Provisioning Zip pointed to by a preconfigured URL. This Zip
>>> contains configuration information, bundles, or references to additional
>>> Provisioning Zips. It also specifies which bundle to start. 
>>> This start up bundle is considered a management agent. A management
>>> agent could be anything a provider would like. When the management agent
>>> starts up it looks for the Provisioning Service. The Provisioning
>>> Service Interface than provides all the hooks to control and restart the
>>> process. It's a chicken and egg kind of thing. Provisioning starts the
>>> management agent and then exposes itself to its management agent child.
>>> In this case it could install bundles from repositories or bring in
>>> other management agents. It could be autonomous or be under the control
>>> of the local or remote operator. (Or a combination.) Control can also be
>>> passed off from one operator to the next.
>>>   
>>>       
>>>> If the
>>>>     
>>>>         
>>>>> node's profile changes, the repository notifies the change to it and
it will
>>>>> automatically update existing bundles, deploy new bundles, and undeploy
>>>>> unused bundles.  Of course, all configurations and states of the deployed
>>>>> components are supposed to be monitored and reconfigured by a GUI console
>>>>> which runs in an Administrator's desktop PC.
>>>>>       
>>>>>           
>>> Again I think this can be done in a standard way. As a matter of fact I
>>> am attempting this with the Provisioning Service and JMX.
>>>
>>> Trustin is this for the ApacheDS or the MINA project?
>>>
>>> cheers,
>>> John
>>>
>>>
>>>  On Fri, 2006-01-20 at 07:21, Richard S. Hall wrote:
>>>   
>>>       
>>>> Trustin,
>>>>
>>>> There is no standard way to do what you ask. Some pieces may help you, 
>>>> such as the OBR bundle repository and others. Other people have created 
>>>> management consoles too, although I am not sure what is freely 
>>>> available. I definitely think OSGi sounds up to the task for what you 
>>>> want to do.
>>>>
>>>> -> richard
>>>>
>>>> Trustin Lee wrote:
>>>>     
>>>>         
>>>>> Hi all,
>>>>>
>>>>> I'm designing a distributed application platform which provides provisioning
>>>>> and management.
>>>>>
>>>>> When each node starts up, it contacts to the configuration and component
>>>>> (bundle) repository and pulls its required components on the fly.  If
the
>>>>> node's profile changes, the repository notifies the change to it and
it will
>>>>> automatically update existing bundles, deploy new bundles, and undeploy
>>>>> unused bundles.  Of course, all configurations and states of the deployed
>>>>> components are supposed to be monitored and reconfigured by a GUI console
>>>>> which runs in an Administrator's desktop PC.
>>>>>
>>>>> I think I can do this with OSGi, but I have no idea if it is standardized,
>>>>> or the standardization is in progress.  Anyone who can provision me?
:)
>>>>>
>>>>> Thanks in advance,
>>>>> Trustin
>>>>> --
>>>>> what we call human nature is actually human habit
>>>>> --
>>>>> http://gleamynode.net/
>>>>> PGP Key ID: 0x854B996C
>>>>>
>>>>>   
>>>>>       
>>>>>           
>>>   
>>>       
>
>
>   

Mime
View raw message