[libvirt] Website contains outdated information about remote limitations

[Matthias Bolte]

2010/1/20 Daniel Veillard <veillard at redhat.com>:
> On Tue, Jan 19, 2010 at 09:43:32PM +0100, Matthias Bolte wrote:
>> 2010/1/19 Daniel P. Berrange <berrange at redhat.com>:
>> > On Tue, Jan 19, 2010 at 08:27:55PM +0100, Matthias Bolte wrote:
>> >> http://www.libvirt.org/remote.html#Remote_limitations says:
>> >>
>> >> Limitations
>> >>     * Remote storage: To be fully useful, particularly for creating
>> >> new domains, it should be possible to enumerate and provision storage
>> >> on the remote machine. This is currently in the design phase.
>> >>     * Migration: We expect libvirt will support migration, and
>> >> obviously remote support is what makes migration worthwhile. This is
>> >> also in the design phase. Issues to discuss include which path the
>> >> migration data should follow (eg. client to client direct, or client
>> >> to server to client) and security.
>> >>
>> >> IMHO this is outdated information, because libvirt supports both
>> >> features now. So both should be removed from the website as they could
>> >> misinform newbies.
>> >
>> > Agreed, that needs to be removed.
>> >
>> >
>> > Daniel
>> >
>>
>> Here's a patch for it.
>>
>> Matthias
>
>> From 4205ae5a790c7e4022dcf6250b500a10f4d6b5a3 Mon Sep 17 00:00:00 2001
>> From: Matthias Bolte <matthias.bolte at googlemail.com>
>> Date: Tue, 19 Jan 2010 21:39:20 +0100
>> Subject: [PATCH] docs: Remove outdated information about remote limitations
>>
>> ---
>>  docs/remote.html.in |   10 ----------
>>  1 files changed, 0 insertions(+), 10 deletions(-)
>>
>> diff --git a/docs/remote.html.in b/docs/remote.html.in
>> index 2716ebe..b8b8f2b 100644
>> --- a/docs/remote.html.in
>> +++ b/docs/remote.html.in
>> @@ -811,16 +811,6 @@ should just 'do the right thing(tm)'.
>>        <a name="Remote_limitations" id="Remote_limitations">Limitations</a>
>>      </h3>
>>      <ul>
>> -      <li> Remote storage: To be fully useful, particularly for
>> -creating new domains, it should be possible to enumerate
>> -and provision storage on the remote machine.  This is currently
>> -in the design phase. </li>
>> -      <li> Migration: We expect libvirt will support migration,
>> -and obviously remote support is what makes migration worthwhile.
>> -This is also in the design phase.  Issues <a href="https://www.redhat.com/mailman/listinfo/libvir-list" title="libvir-list mailing list">to discuss</a> include
>> -which path the migration data should follow (eg. client to
>> -client direct, or client to server to client) and security.
>> -</li>
>>        <li> Fine-grained authentication: libvirt in general,
>>  but in particular the remote case should support more
>>  fine-grained authentication for operations, rather than
>
>  ACK, thanks for spotting this !
>
> Daniel
>

Well, I didn't spot it, jcox on IRC did by asking about the migration
support of libvirt and referencing this section of the website.
Pushed.

Matthias