Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev/stephand/bareos 18.2/vmware fixes utf8 #140

Closed

Conversation

sduehr
Copy link
Member

@sduehr sduehr commented Jan 22, 2019

Fixed VMWare plugin and documentation related to use of non-ascii characters.

sduehr and others added 3 commits January 16, 2019 16:05
Fixed UnicodeEncodeError in the Bareos VMWare Plugin when the VM name
and/or VMDK file name or folder name contained non-ascii characters.
It is also possible now to configure backups of VMs contained in vApps
by handling the vApp name like a folder name.

The script vmware_cbt_tool.py was also adapted to handle non-ascii
characters and vApps properly. The --listall flag was added to output a
list of all VMs in the given datacenter including the instanceUUID,
folder name and VM name. Also it's possible now to specify the VM by
using --vm-uuid <instanceUUID> instead of folder and VM Name.

Additionally small changes to comply with flake8 --max-line-length=100.
The VMware plugin documentation was not converted before.
As we still do auto conversion of the *.tex files, we can only
include it inside of the "Plugins" chapter,but not in the
"File Daemon Plugins" section.
Updated documentation for the VMWare plugin related to the fixed
errors and changes regarding use of non-ascii characters.
@pstorz
Copy link
Member

pstorz commented Jan 22, 2019

branch was merged into bareos-18.2

@pstorz pstorz closed this Jan 22, 2019
@pstorz pstorz deleted the dev/stephand/bareos-18.2/vmware-fixes-utf8 branch July 10, 2019 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants