[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] [prov] Thoughts on the engine

I was not really clear in my description. The engine takes an operation
(which is only a list of phases). When the engine performs this operation,
it runs through all the phases of the operation (currently breadth first).
Therefore if you wanted to "fetch" everything without doing any
installation and configuration, you would create a FetchOperation (only
made of the fetch phase) and give it to the engine to download everything.

<tangent>
That said I must admit that I'm not super happy with this solution since to
make such a "fetch only" operation usable, either the director would have
to expose a "fetch" operation (but it would also have to expose a "install"
operation to solve the other pb mentioned by James), or one would have to
either author its own director (or at least extend the current one) which
is something we want to avoid. In the light of recent discussions with Tim
and others, I wonder if the director should not become just a planner that
returns a bunch on operations that needs to be performed. The results of
this planner would then be passed on to the engine and a "target" phase
could be specified. For example:
      EngineOperation[] op = director.install(ius, profile1)
      engine(op, "fetch");  //This means do the operations but stop at
fetch.
</tangent>



>>This likely also has implications for touchpoints since there are
touchpoint operations that should be done during install (like global
things) and operations that need to be performed on a user basis.


Do you mean that some operations must be done with the actual user being
identified?
Also you seem to be concerned with how many time each phase is being run,
why is that? Note that we are hoping that if you asked the engine to
"fetch" an IU that has already been fetched, then it would be a no-op (or
close).


HTH


PaScaL





                                                                           
             James D Miles                                                 
             <jdmiles@xxxxxxxx                                             
             om>                                                        To 
             Sent by:                  Equinox development mailing list    
             equinox-dev-bounc         <equinox-dev@xxxxxxxxxxx>           
             es@xxxxxxxxxxx                                             cc 
                                                                           
                                                                   Subject 
             08/16/2007 11:58          Re: [equinox-dev] [prov] Thoughts   
             AM                        on the engine                       
                                                                           
                                                                           
             Please respond to                                             
                  Equinox                                                  
                development                                                
               mailing list                                                
             <equinox-dev@ecli                                             
                 pse.org>                                                  
                                                                           
                                                                           




Thanks Pascal,
>From wiki
                  Currently the processing is done breadth first, in that
                  first all the IUs are being fetched, then they are all
                  installed and finally configured. Is that too strict?



Yes I think that is too strict. For the general case (multiuser) it is too
restrictive to always get a configure with install, etc. The use case that
requires install only is a native service. It can install artifacts but it
can't configure for all users. The configure should occur when the user
starts the program. This likely also has implications for touchpoints since
there are touchpoint operations that should be done during install (like
global things) and operations that need to be performed on a user basis.

(Embedded image moved to file: pic14284.gif)Inactive hide details for
Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>Pascal Rapicault
<Pascal_Rapicault@xxxxxxxxxx>

                                                                           
                         Pascal                                            
                         Rapicault                                         
                         <Pascal_Rapicau                                   
                         lt@xxxxxxxxxx>  (Embedded image moved to file:    
                         Sent by:        pic09093.gif)                     
                         equinox-dev-bou                                To 
                         nces@xxxxxxxxxx             (Embedded image moved 
                         g                           to file:              
                                                     pic06642.gif)         
                                                     Equinox development   
                         08/16/2007                  mailing list          
                         09:36 AM                    <equinox-dev@eclipse. 
                                                     org>                  
                                         (Embedded image moved to file:    
            Please respond to            pic09731.gif)                     
    Equinox development mailing list                                    cc 
        <equinox-dev@xxxxxxxxxxx>                    (Embedded image moved 
                                                     to file:              
                                                     pic26191.gif)         
                                         (Embedded image moved to file:    
                                         pic26095.gif)                     
                                                                   Subject 
                                                     (Embedded image moved 
                                                     to file:              
                                                     pic19405.gif)         
                                                     [equinox-dev] [prov]  
                                                     Thoughts on the       
                                                     engine                
                                                                           
                                                                           
                                         (Embedded image moved to file:    
                                         pic31894.gif)                     
                                                (Embedded image moved to   
                                                file: pic25498.gif)        
                                                                           
                                                                           




I have created an wiki page describing thoughts / questions about the
Engine. http://wiki.eclipse.org/Equinox_Provisioning_Engine

PaScaL

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
(See attached file: pic21410.gif)
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Attachment: pic14284.gif
Description: GIF image

Attachment: pic09093.gif
Description: GIF image

Attachment: pic06642.gif
Description: GIF image

Attachment: pic09731.gif
Description: GIF image

Attachment: pic26191.gif
Description: GIF image

Attachment: pic26095.gif
Description: GIF image

Attachment: pic19405.gif
Description: GIF image

Attachment: pic31894.gif
Description: GIF image

Attachment: pic25498.gif
Description: GIF image

Attachment: pic21410.gif
Description: GIF image