[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Virgo & p2 use cases
- From: Pascal Rapicault <pascal@xxxxxxxxxxxx>
- Date: Tue, 15 Feb 2011 23:23:29 -0500
- Delivered-to: firstname.lastname@example.org
In this description, what is "Virgo"? The container and the application, or just the container?
Where does the use case of "the user downloads virgo, starts it and install an application using p2" fit?
How much flexibility is there in terms of changing the layout of the actual runtime to maybe make it more "manageable" from a p2 standpoint and still accommodate the two scenarios?
On 2011-02-15, at 10:33 AM, Glyn Normington wrote:
> Following last week's discussion of p2, I would like to ensure that the following use cases work when we eventually integrate Virgo and p2:
> 1. Unzip and go - the user downloads and unzips Virgo, edits config files, and runs a startup script, much like in 2.1.0. No need to invoke p2, although it is acceptable for p2 to run under the covers.
> 2. Provision Virgo via p2 - the user uses p2 to provision and start Virgo.
> 3. "Hybrid" - the user uses p2 to provision Virgo, edits config files, and runs a startup script, the latter two steps much like in 2.1.0.