Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] [prov] Shared install

From wiki reference

>>The reconciler would check for differences and update the user's profile as needed.

Did you mean the user's bundles.txt? As I understand it the profile would be explicit. It should specify the variability that is allowed and we should stay within those limits. I am not exactly clear on what we mean by profile so maybe it is just a definition difference.

Nice document.


Inactive hide details for "Tim Webb" <tim@xxxxxxxxxx>"Tim Webb" <tim@xxxxxxxxxx>


          "Tim Webb" <tim@xxxxxxxxxx>
          Sent by: equinox-dev-bounces@xxxxxxxxxxx

          08/21/2007 02:14 PM

          Please respond to
          Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To

"Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>

cc


Subject

Re: [equinox-dev] [prov] Shared install

All,

I've written up a few notes on the Shared Install and a quick summary of what Andrew and I will be doing to start an implementation. Online at:

http://wiki.eclipse.org/Equinox_Provisioning_Shared_Install

Cheers,
Tim

On 8/21/07, Tim Webb < tim@xxxxxxxxxx> wrote:
    Pascal,

    In the case of a shared linux installation, there is the potential that what you could describe would work though for other situations such as with Maya where the "shared" profile comes from a location other than the local file system, this would be a bit simplistic. For a first pass Andrew and I are going to do an implementation that would run the reconciler on each launch. Once we determine the performance impacts of doing so, we will then determine if it is worth optimizing the algorithm further. This will allow us to get our feet wet with the provisioning code and have something running in hopefully short order.

    I'll go ahead and write up some of the discussions on a Wiki page.

    Tim



    On 8/21/07, Pascal Rapicault < Pascal_Rapicault@xxxxxxxxxx> wrote:

    Tim, Andrew,

    For records, could you guys write a short wiki describing the various
    approaches we talked about to implement shared installs? In a few months
    this will help us remember why/or not we've done what we've done :-)

    Also , following the call, Simon and I had further discussions and believe
    a good approach would be:
    - simple configurator reads the user bundles.txt
    - simple configurator reads the shared bundles txt
    - if the shared bundles.txt has changed, only run with its content (ignore
    bundles from the user), since it should be a consistent whole (composed of
    the agent / reconciler)
    - then run the reconciler on the running profile (we may need another
    operation on the director or something like that). Note here I'm not saying
    when it is actually run and this should just be configurable.

    Something like that offers the advantage that
    - we don't need to have another configurator as we had touched on
    previously
    - we should always be able to start something
    - gives flexibility as to when the reconciliation should be done

    HTH,

    PaScaL

    _______________________________________________
    equinox-dev mailing list

    equinox-dev@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

GIF image

GIF image

GIF image


Back to the top