Re: [Xen-devel] xl remus - Invoking scripts from xl

[George Dunlap <George.Dunlap@xxxxxxxxxxxxx>]

On Wed, Jul 17, 2013 at 5:39 PM, Shriram Rajagopalan <rshriram@xxxxxxxxx> wrote:
> On Wed, Jul 17, 2013 at 9:57 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
> wrote:
>>
>> On Sun, 2013-07-14 at 10:13 -0500, Shriram Rajagopalan wrote:
>>
>> > I can use xenstore too but I don't want to pollute xenstore entries
>> > unless absolutely necessary.
>>
>> Ultimately it may be that the script is running in a different domain
>> (e.g. a driver domain) so xenstore may be the best way.
>>
>> Can you enumerate what would be going in there? It may be
>> that /libxl/<domid> or even /tools/remus/<domid> might be an appropriate
>> home for it.
>>
>
> driver domains is something that I didnt think about. interesting idea
> though.
>
> basically, if I were to use xenstore as a communication medium between
> the script & xl-remus, things that xl would need as return values from the
> script
> (via xenstore) are the ifb devices that map to each of the vifs belonging to
> the guest,
> so that plug qdiscs can be installed on all of them.

Just to check, are you making a distinction here between xl and libxl?
 Ideally the important functionality to do Remus would be in libxl, so
that any toolstack could impliment it.  xl is meant to represent an
example toolstack one might build; it in theory one should be able to
implement Remus using libvirt or xapi without significant effort.

 -G

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel