External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-22 04:25:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Remove outdated information about remote limitations

Browse Source
This commit is contained in:
Matthias Bolte 2010-01-19 21:39:20 +01:00
parent eb895e7407
commit d392f4db9d
1 changed files with 0 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/remote.html.in
View File

@ -811,16 +811,6 @@ should just 'do the right thing(tm)'.
<a name="Remote_limitations" id="Remote_limitations">Limitations</a> <a name="Remote_limitations" id="Remote_limitations">Limitations</a>
</h3> </h3>
<ul> <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, <li> Fine-grained authentication: libvirt in general,
but in particular the remote case should support more but in particular the remote case should support more
fine-grained authentication for operations, rather than fine-grained authentication for operations, rather than