Bug 783150 - [ovirt] [vdsm] change vm channel name suffix from com.redhat.rhevm.vdsm to org.ovirt.vdsm
Summary: [ovirt] [vdsm] change vm channel name suffix from com.redhat.rhevm.vdsm to or...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Gal Hammer
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-19 14:26 UTC by Haim
Modified: 2014-01-13 00:50 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-03 12:24:32 UTC
oVirt Team: ---


Attachments (Terms of Use)

Description Haim 2012-01-19 14:26:20 UTC
Description of problem:

- vm channel name looks as follows: 

/var/lib/libvirt/qemu/channels/myVm42.com.redhat.rhevm.vdsm

- should look as follows: 

/var/lib/libvirt/qemu/channels/myVm42.org.ovirt.vdsm



git 7884251a245ef214e442f1d4372a9ff70b2b7a78

file: vdsm/libvirtvm.py

Comment 1 Haim 2012-01-19 14:30:25 UTC
http://gerrit.ovirt.org/1146

Comment 2 Federico Simoncelli 2012-06-22 11:56:25 UTC
Patch abandoned upstream.

Comment 3 Dan Kenigsberg 2012-06-22 13:53:48 UTC
Actually, we *should* find a way to drop the rhevm trademark properly. Maybe Gal could help.

Comment 4 Federico Simoncelli 2012-06-22 15:00:58 UTC
(In reply to comment #3)
> Actually, we *should* find a way to drop the rhevm trademark properly. Maybe
> Gal could help.

Ah nice! Thanks. I didn't know what happened "behind the scene", the patch was abandoned, and I though that it was after Haim spoke with you. I'm all for fixing this.

Comment 5 Gal Hammer 2012-06-24 06:03:28 UTC
(In reply to comment #3)
> Actually, we *should* find a way to drop the rhevm trademark properly. Maybe
> Gal could help.

The channel name can be changed using the configuration file.

Comment 6 Itamar Heim 2013-02-03 12:24:32 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.


Note You need to log in before you can comment on or make changes to this bug.