Re: [Xen-API] Status report for Xapi sprint wk28 planning

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

It's just a client at the moment, but a server is pretty easy from that base.  
I'll let the list know when that code is usable separately.

-anil


On 26 Jun 2013, at 16:09, Rob Hoes <Rob.Hoes@xxxxxxxxxx> wrote:

> HI Anil,
> 
> That issue was to not rely on changes to dhclient-script to notify xapi when 
> DHCP has finished configuring a NIC (for xapi to update its DB). That's 
> already fixed by making the network daemon watch for IP address changes and 
> do those callbacks.
> 
> However, we still depend on a particular DHCP client to be present on the 
> system. Is the migrate code a DHCP client or server (or both)? I think it 
> would be interesting in any case.
> 
> Cheers,
> Rob
> 
>> -----Original Message-----
>> From: xen-api-bounces@xxxxxxxxxxxxx [mailto:xen-api-
>> bounces@xxxxxxxxxxxxx] On Behalf Of Anil Madhavapeddy
>> Sent: 26 June 2013 3:47 PM
>> To: Mike McClurg
>> Cc: xen-api@xxxxxxxxxxxxx
>> Subject: Re: [Xen-API] Status report for Xapi sprint wk28 planning
>> 
>> It's definitely useful.  Incidentally:
>> 
>>> CP-5153: Make DHCP work in distros other than Citrix XenServer
>> 
>> There's been some interest in extracting the Mirage-net DHCP code and
>> making it work properly under UNIX to use it as a general-purpose DHCP
>> library.  I can put this on the queue if that's useful for this particular 
>> thing
>> above.
>> 
>> -anil
>> 
>> On 26 Jun 2013, at 15:39, Mike McClurg <mike.mcclurg@xxxxxxxxxx> wrote:
>> 
>>> Hi all,
>>> 
>>> I'm going to start sending bi-monthly (every two weeks) status reports for
>> our Xapi team sprint planning. In these status reports I'll link to status 
>> report
>> pages on our wiki. These reports will reference ticket numbers on our
>> internal ticket tracker. We aren't going to be able to create an externally
>> visible ticket system any time soon (this is something we want to do, but we
>> don't have a plan for it yet).
>>> 
>>> I think it will still be useful to mention these numbers on the status
>> reports since we already reference these numbers in our commit messages
>> and pull requests. This will at least make it easier for people to refer to
>> specific bugs or work items in emails on the list.
>>> 
>>> Here is the current Xapi roadmap:
>>> 
>>> http://wiki.xenproject.org/wiki/Xapi_Project_Roadmap
>>> 
>>> And here are the reports for the recently closed sprint, and the sprint we
>> just started today:
>>> 
>>> http://wiki.xenproject.org/wiki/Sprint_wk26
>>> http://wiki.xenproject.org/wiki/Sprint_wk28
>>> 
>>> Please let me know if you have any comments about these reports. I hope
>> that it will be useful to people (or at least moderately interesting) to see
>> what we will be working on. I'm worried, though, that the short titles of the
>> tickets won't be enough information to be useful enough. So comments on
>> this will definitely be welcome!
>>> 
>>> Mike
>>> 
>>> _______________________________________________
>>> Xen-api mailing list
>>> Xen-api@xxxxxxxxxxxxx
>>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
>>> 
>> 
>> 
>> _______________________________________________
>> Xen-api mailing list
>> Xen-api@xxxxxxxxxxxxx
>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
> 


_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api