← Back to team overview

openstack team mailing list archive

Re: xen server agent code in nova?


Agree with the directory structure. I'm hoping we can get some
conversation on where to pull the configuration that we use xentore for
now. I've heard some ideas around zookeeper from more than one person, but
have not fully investigated yet.


On 2/9/11 5:08 PM, "Chris Behrens" <chris.behrens@xxxxxxxxxxxxx> wrote:

>Thanks.  I was going to pose the same question:  where should this go? :)
>I'm currently working on the 'xs-guest-agent' blueprint which involves
>clean up with the current Rackspace linux agent.  While this agent
>currently only supports Linux on XenServer (because of some Linux
>specific calls and communication via XenStore), some of the work I'm
>doing will make it more portable (so that it'll work on *BSD, too) and
>will modularize the communication mechanism.  This will allow the
>XenStore communication to be swapped out in favor of something else not
>Xen specific.
>That said, I'm not sure the main code base should live in a 'xen_server'
>subdirectory as suggested below.  Modifying the below, I'd perhaps
>/tools/guest_agent/unix for the main unix agent code base.
>Subdirectories could exist under there for different communication
>Windows might be different, as it is definitely XenServer specific...
>maybe, /tools/guest_agent/windows/xen_server
>(As a side note, I wonder if we want move to sharing some common code
>between Windows and Unix agents which would further impact the directory
>structure :)
>- Chris
>On Feb 9, 2011, at 2:16 PM, Paul Voccio wrote:
>> All,
>> After discussing this among some small groups that are working with
>>XenServer, we've decided we probably should pull in our guest agent code
>>so others can look at it and start using it and building on it. Today,
>>this code is XenServer specific, but long term I think we need to figure
>>out where to put the code in the Nova codebase. I might suggest
>>/tools/guest_agent/xen_server/ but am open. We have Windows 2003/2008
>>code and Linux code so we'll need to include build instructions for both
>>in the directories.
>> So the question I want to pose to the community is if they are
>>interested in the code, where should it go and how should we move
>>forward on extending it?
>> Thanks,
>> Paul
>> Confidentiality Notice: This e-mail message (including any attached or
>> embedded documents) is intended for the exclusive and confidential use
>>of the
>> individual or entity to which this message is addressed, and unless
>> expressly indicated, is confidential and privileged information of
>> Any dissemination, distribution or copying of the enclosed material is
>> If you receive this transmission in error, please notify us immediately
>>by e-mail
>> at abuse@xxxxxxxxxxxxx, and delete the original message.
>> Your cooperation is appreciated.
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp