dfad1b551d
When accessing libvirtd over a SSH tunnel, the remote driver needs a way to proxy the SSH input/output stream to a suitable libvirt daemon. This is currently done by spawning netcat, pointing it to the libvirtd socket path. This is problematic for a number of reasons: - The socket path varies according to the --prefix chosen at build time. The remote client is seeing the local prefix, but what we need is the remote prefix - The socket path varies according to remote env variables, such as the XDG_RUNTIME_DIR location. Again we see the local XDG_RUNTIME_DIR value, but what we need is the remote value (if any) - The remote driver doesn't know whether it must connect to the legacy libvirtd or the modular daemons, so must always assume legacy libvirtd for back-compat. This means we'll always end up using the virtproxyd daemon adding an extra hop in the RPC layer. - We can not able to autospawn the libvirtd daemon for session mode access To address these problems this patch introduces the 'virtd-ssh-helper' program which takes the URI for the remote driver as a CLI parameter. It then figures out which daemon to connect to and its socket path, using the same code that the remote driver client would on the remote host's build of libvirt. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> |
||
|---|---|---|
| .. | ||
| as.po | ||
| bg.po | ||
| bn_IN.po | ||
| bs.po | ||
| ca.po | ||
| cs.po | ||
| da.po | ||
| de.po | ||
| el.po | ||
| en_GB.po | ||
| es.po | ||
| fi.po | ||
| fr.po | ||
| gu.po | ||
| hi.po | ||
| hu.po | ||
| id.po | ||
| it.po | ||
| ja.po | ||
| kn.po | ||
| ko.po | ||
| libvirt.pot | ||
| LINGUAS | ||
| meson.build | ||
| mk.po | ||
| ml.po | ||
| mr.po | ||
| ms.po | ||
| nb.po | ||
| nl.po | ||
| or.po | ||
| pa.po | ||
| pl.po | ||
| POTFILES.in | ||
| pt_BR.po | ||
| pt.po | ||
| README.rst | ||
| ru.po | ||
| sr.po | ||
| sr@latin.po | ||
| sv.po | ||
| ta.po | ||
| te.po | ||
| uk.po | ||
| vi.po | ||
| zh_CN.po | ||
| zh_TW.po | ||
Libvirt Message Translation
Libvirt translatable messages are maintained using the GNU Gettext tools and file formats, in combination with the Fedora Weblate web service.
https://translate.fedoraproject.org/projects/libvirt/libvirt/
Source repository
The libvirt GIT repository stores the master "libvirt.pot" file, which is to be refreshed at time of feature freeze.
The "po" files stored in GIT have source locations removed in order to cut down on storage size, by eliminating information already present in the "pot" file. All files are stored with strings sorted in alphabetical order rather than source location order, to minimize movement of strings when source locations change.
The "po" files are to be EXCLUSIVELY UPDATED by merge requests sent from the Fedora Weblate service. Other contributors MUST NEVER send changes which touch the "po" file content, as that will create merge conflicts for Weblate. IOW any bug fixes to translations should be made via the Weblate application UI.
After the "pot" file in libvirt GIT, Weblate will automatically run "msgmerge" to update the "po" files itself and send back a merge request with the changes.
Translation updates made in the Weblate Web UI will be committed to its fork of the GIT repo once a day. These commits will be submitted back to the master GIT repo via merge requests. If a merge request from Weblate is already open, commits will be added to this existing merge request. Weblate will take care of rebasing whenever changes happen in Git master. In order to avoid having to do translations merges 30 times a month, merge requests from Weblate will usually be left open until feature freeze arrives. During the freeze period, they will be accepted more promptly to ensure they make it into the new release.