[virt-tools-list] Best practice for shared-storage and network configuration via CLI for Virt-Manager?

[Decker, Schorschi]

Thanks for the insight.  I had not thought about the firewall
specifically as yet, but you reminded me, that we have to take that into
account as well.  :)  I would like to avoid if possible tweaking the
XML, only for the sake of not having to touch our scripts if the XML
structure/format changes significantly, but that may be the best way,
all things considered.


Schorschi



-----Original Message-----
From: Richard W.M. Jones [mailto:rjones at redhat.com] 
Sent: Wednesday, 20 April, 2011 10:20
To: Decker, Schorschi
Cc: virt-tools-list at redhat.com
Subject: Re: [virt-tools-list] Best practice for shared-storage and
network configuration via CLI for Virt-Manager?

On Wed, Apr 20, 2011 at 06:48:18AM -0700, Decker, Schorschi wrote:
> As we continue to automate (current) version of virt-manager, what 
> would be the best method to establish volumes and network
connectivity?
> 
> Obviously we can automate the creation of a physical NIC bridge, which

> is our desired method for VM connectivity outside of the KVM host, and

> we can reference said bridge interface as we build VMs.  However, are 
> there any side-effects to this method we should know about?

The only immediate thing I can think of is the firewall rules the
libvirtd adds.  You'd want to check that libvirtd is (or is not?)
creating the right rules for you.

Also note that if you restart the firewall, all the libvirtd rules get
thrown out and your guests can't talk to each other (RHBZ#227011).

> Same basic question for mount points to shared storage between KVM 
> hosts.  We plan to use NAS/NFS initially, some day we might use SAN 
> infrastructure.  Creating the mount points is straight forward from an

> automation perspective, but to get virt-manager to see these volumes, 
> any issues we  should be aware of?  Take into consideration?

I can't think of any issues.

> Anyone that has done this before?  Figure we can benefit from lessons 
> learned?  As always thanks for the assistance.

If you want precise control over how guests are created, use
virt-install or even create/edit libvirt XML directly from your scripts.

Rich.

--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones virt-top is 'top' for virtual machines.
Tiny program with many powerful monitoring features, net stats, disk
stats, logging, etc.
http://et.redhat.com/~rjones/virt-top

----------------------------------------------------------------------
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.