----- Original Message ----- > From: "Sander Grendelman" <[email protected]> > To: "Eli Mesika" <[email protected]> > Cc: [email protected] > Sent: Monday, November 18, 2013 4:25:16 PM > Subject: Re: [Users] Fence-virt support > > On Mon, Nov 18, 2013 at 3:08 PM, Eli Mesika <[email protected]> wrote: > >> - fence-virtd uses a keyfile, no username and password. > > > > This is a real problem , we are not supporting currently other > > authentication methods > Yes, It's probably going to take a bit of a hack to make this > work with the current mechanism/gui because the key file > has to be an actual _file_. > > I just made a local config + keyfile for my testnodes. > > > > >> - fence-virtd uses port=vmname to identify a VM > >> > >> The gui has mandatory username and password fields and > >> the standard port/sshport field only takes numeric values. > > > > For that we have the options field , you could omit the port from the fence > > mapping and then add in the options "port=<value>" > > Yes that's what I did. One of the problems with that is that > port= maps to the sshport field in the apc part of the gui > which brings us back to BZ 1014513.
You should add a new agent type to VdsFenceType config values then add the relevant info to (without port) for this agent to VdsFenceOptionMapping Then , when you are selecting it from the UI , the ssh port should not be shown and you can use it in the options field > > >> Some of the problems I ran into are probably related to > >> https://bugzilla.redhat.com/show_bug.cgi?id=1020344 > > > > This is actually related to another BZ > > https://bugzilla.redhat.com/show_bug.cgi?id=1014513 > > > Yes, that's actually the one I meant but I couldn't find it. > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
