[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC PATCH] xen/arm: Rebranding dom0less feature



>>> 
>>> Instead, the use case configurations should themselves be describable.
>> 
>> Thanks Christopher, Daniel and all!
>> 
>> So if I understand correctly, you are in favor if renaming Dom0less to
>> Hyperlaunch throughout the Xen codebase? And we need a clarification of
>> the docs/, especially docs/features/dom0less.pandoc?
> 
> Christopher wrote:
>>> = Community resourcing
> 
> Note the pre-requisite work items for upstream Xen, listed under "Community 
> Resourcing", to merge code for Hyperlaunch common interfaces and test cases, 
> with docs on configuration of Hyperlaunch to deliver functionality for 
> dom0less use cases.

Are you saying that before renaming the “dom0less” feature, we should wait for 
it to be ported to the common code?

> 
> Thanks,
> Rich



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.