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

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

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?


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?


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



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]