[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [virt-tools-list] [PATCH V2] virt-manager: enable direct interface selection



Hi Schorschi,

First, why did you restart this discussion by responding to Gerhard's
unrelated patch? If you want to start a new discussion, please do not reply to
unrelated emails on the list, but send a new email directly to
virt-tools-list redhat com  If you want to continue an existing discussion,
please respond to one of the emails already pertaining to that discussion.

On 04/08/2011 12:32 PM, Decker, Schorschi wrote:
> Yes, let me restate the original question in more detail...
> 
> Need...
> 
> What we need... is a way to add a 'host' connection to Virt-Manager that is not interactive at all.  Virsh -c or connect still invokes GUI or some interactive response from Virt-Manager.
> 
> This does not work for full automation of Virt-Manager configuration.  We want to add KVM hosts to Virt-manager 100% from automated script process.
> 
> Issue...
> 
> As I understand it, this add host connection, can only be done via raw API use?  Today?  You can configure storage (volumes), create networks and even VMs via CLI with no interactive effort, but not add KVM host connections?  This is seems to be an obvious gap in the design of the CLI for Virt-Manager.
> 
> Use Case...
> 
> We want to pre-configure Virt-Manager, so that our operations team does not need to know any id/password or any SSL information because the host connections are already in place when Virt-Manager is started.  They never have to add or remove a host connection, they just open Virt-Manager and all the host connections are already there, and all the VMs visible per host.
> 
> Work-Around...?
> 
> Using Gconf is one scenario that seems to work, but Virt-Manager sometimes gets confused, and does not always remove a host connection in a clean manner for the Gconf method of adding a connection fails.  We are looking for a better method to add a host connection to Virt-Manager if possible, or get this feature into the roadmap for the Virt-Manager CLI, so in the future it is an official, supported method/feature.
> 

Setting this value in GConf is the supported method for doing this. If you are
having issues, please describe exactly the steps you are taking, what errors
you are encountering including explicit error messages, and the output of
virt-manager --debug when reproducing the problem.

Thanks,
Cole

> Schorschi
> 
> -----Original Message-----
> From: Gerhard Stenzel [mailto:gstenzel linux vnet ibm com] 
> Sent: Friday, 08 April, 2011 06:37
> To: Decker, Schorschi
> Cc: crobinso redhat com; virt-tools-list redhat com
> Subject: RE: [virt-tools-list] [PATCH V2] virt-manager: enable direct interfaceselection
> 
> On Fri, 2011-04-08 at 06:16 -0700, Decker, Schorschi wrote:
>> Defining a virtual machine or host?  We need a way to add a 
>> 'connection'
>> i.e. host to virt-manager with 100% CLI for automation.  Virsh -c 
>> invokes the GUI.  There should be away to add a KVM host to 
>> virt-manager that does not require any interactive effort.  If not, 
>> that is a feature that is missing that should be added.
>>
>> VMware vCenter has CLI support to add host via their API, so does 
>> Hyper-V, etc.  The way to drive KVM adoption is via automation.  No?
>>
>> Schorschi
> 
> I am not sure I understand your comment.
> 
> Defining a virtual machine via "virsh define" will it also make visible in virt-manager. That works. No problem.
> 
> The patch is specifically for the case when a virtual machine is defined interactively with virt-manager.
> 
> --
> Best regards, 
> 
> Gerhard Stenzel,
> -----------------------------------------------------------------------------------------------------------------------------------
> IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter
> Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen
> Registergericht: Amtsgericht Stuttgart, HRB 243294
> 
> 
> ----------------------------------------------------------------------
> This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. 
> Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. 
> The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. 
> 
> References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: 
> http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]