Obsolete:XenServer/NovaFlags - Revision history

Fifieldt: Fifieldt moved page XenServer/NovaFlags to Obsolete:XenServer/NovaFlags: blank page

2013-07-25T18:42:50Z

Fifieldt moved page XenServer/NovaFlags to Obsolete:XenServer/NovaFlags: blank page

Fifieldt: blanking - page was very out of date

2013-07-15T05:36:20Z

blanking - page was very out of date

Fifieldt: /* Nova flags for XenServer */

2013-07-15T05:03:47Z

‎Nova flags for XenServer

Ryan Lane: Text replace - "NOTOC" to ""

2013-02-17T23:30:12Z

Text replace - "__NOTOC__" to ""

Clark Boylan at 23:02, 16 February 2013

2013-02-16T23:02:57Z

JohnGarbutt at 15:15, 23 April 2012

2012-04-23T15:15:06Z

JohnGarbutt at 15:14, 23 April 2012

2012-04-23T15:14:47Z

JohnGarbutt at 15:14, 23 April 2012

2012-04-23T15:14:32Z

JohnGarbutt at 15:11, 23 April 2012

2012-04-23T15:11:02Z

JohnGarbutt: Update the notes on the connection URL

2012-03-22T15:39:19Z

Update the notes on the connection URL

← Older revision		Revision as of 05:36, 15 July 2013
Line 1:		Line 1:

−	~~<!-- ## page was renamed from [[XenServer/ComputeFlags]] -->~~
−	~~= Nova flags for [[XenServer]] =~~
−
−	~~When configuring Nova and [[XenServer]], please take care with the following settings in nova.conf.~~
−
−	~~== Networking ==~~
−
−	~~For more information on networking, see:~~
−	* [[XenServer/NetworkingFlags]]
−
−	~~== Storage ==~~
−
−	~~You can specify which Storage Repository to use with nova by looking at the following flag. The default is to use the local-storage setup by the default installer:~~
−
−	~~<pre><nowiki>~~
−	~~sr_matching_filter="other-config:i18n-key=local-storage"~~
−	~~</nowiki></pre>~~
−
−	~~Another good alternative is to use the "default" storage (for example if you have attached NFS or any other shared storage):~~
−
−	~~<pre><nowiki>~~
−	~~sr_matching_filter="default-sr:true"~~
−	~~</nowiki></pre>~~
−
−	~~Please note: if you want to use a [[XenServer]] pool, you must create the pool using the Host Aggregates feature.~~
−
−	~~== Flat Injection ==~~
−
−	~~Unless you know what guests you are having and test this works, it is best to use FlatDHCP, and so turn off the network injection (uses DHCP instead)~~
−
−	~~<pre><nowiki>~~
−	~~flat_injected=False~~
−	~~</nowiki></pre>~~
−
−	~~== Connection ==~~
−
−	~~It is common to use the "Host Internal Management Network" to contact XenAPI, and so you can use the following IP for [[XenServer]]: 169.254.0.1 (This is the default DevStack uses)~~
−
−	Please note, using the above address will only work when you have a single hypervisor. If you are trying to migrate VMs across machines, or work with host aggregates you will need to use management network IP address of the [[XenServer]].
−
−	~~The three flags you will need to set, so nova can talk to XenAPI, are:~~
−
−	~~<pre><nowiki>~~
−	~~xenapi_connection_url=http://111.111.111.111~~
−	~~xenapi_connection_username=root~~
−	~~xenapi_connection_password=your_password_goes_here~~
−	~~</nowiki></pre>~~
−
−	~~== VNC Proxy Address ==~~
−
−	~~Assuming you are talking to XenAPI through the host local managmenet network, and [[XenServer]] is on the address: 169.254.0.1, you can use the following:~~
−
−	~~<pre><nowiki>~~
−	~~vncserver_proxyclient_address=169.254.0.1~~
−	~~</nowiki></pre>~~
−
−	~~TODO: double check what config is needed here?~~
−
−	~~== Firewall ==~~
−
−	~~The default firewall may be specific to libvirt. There are two options.~~
−
−	* Using IP Tables in mova network:
−
−	~~<pre><nowiki>~~
−	~~firewall_driver=nova.virt.firewall.IptablesFirewallDriver~~
−	~~</nowiki></pre>~~
−
−	* Doing the isolation in Dom0:
−
−	~~<pre><nowiki>~~
−	~~firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver~~
−	~~</nowiki></pre>~~
−
−	~~== Guest Agent ==~~
−
−	~~If you don't have the guest agent on your VMs, it will take a long time for nova to decide the VM has successfully started.~~
−
−	~~While the large timeout is required for Windows instances, you may want to tweak the following flag:~~
−
−	~~<pre><nowiki>~~
−	~~agent_version_timeout=300 # number of seconds to wait, 300 is the default~~
−	~~</nowiki></pre>~~

← Older revision		Revision as of 05:03, 15 July 2013
Line 4:		Line 4:

	When configuring Nova and [[XenServer]], please take care with the following settings in nova.conf.		When configuring Nova and [[XenServer]], please take care with the following settings in nova.conf.
−
−	~~You can find more details on the flags in the following wiki page:~~
−	* [[NovaConfigOptions]]

	== Networking ==		== Networking ==

@@ Line 1: / Line 1: @@
-__NOTOC__
 <!-- ## page was renamed from [[XenServer/ComputeFlags]] -->
 = Nova flags for [[XenServer]] =

@@ Line 20: / Line 20: @@
 sr_matching_filter="other-config:i18n-key=local-storage"
 </nowiki></pre>
 Another good alternative is to use the "default" storage (for example if you have attached NFS or any other shared storage):
@@ Line 27: / Line 26: @@
 sr_matching_filter="default-sr:true"
 </nowiki></pre>
 Please note: if you want to use a [[XenServer]] pool, you must create the pool using the Host Aggregates feature.
@@ Line 34: / Line 32: @@
 Unless you know what guests you are having and test this works, it is best to use FlatDHCP, and so turn off the network injection (uses DHCP instead)
 <pre><nowiki>
 flat_injected=False
 </nowiki></pre>
 == Connection ==
-It is common to use the "Host Internal Management Network" to contact XenAPI, and so you can use the following IP for [[XenServer]]: 169.254.0.1 (This is the default [[DevStack]] uses)
+It is common to use the "Host Internal Management Network" to contact XenAPI, and so you can use the following IP for [[XenServer]]: 169.254.0.1 (This is the default DevStack uses)
 Please note, using the above address will only work when you have a single hypervisor. If you are trying to migrate VMs across machines, or work with host aggregates you will need to use management network IP address of the [[XenServer]].
@@ Line 54: / Line 50: @@
 xenapi_connection_password=your_password_goes_here
 </nowiki></pre>
 == VNC Proxy Address ==
 Assuming you are talking to XenAPI through the host local managmenet network, and [[XenServer]] is on the address: 169.254.0.1, you can use the following:
 <pre><nowiki>
 vncserver_proxyclient_address=169.254.0.1
 </nowiki></pre>
 TODO: double check what config is needed here?
@@ Line 83: / Line 76: @@
 firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver
 </nowiki></pre>
 == Guest Agent ==
@@ Line 90: / Line 82: @@
 While the large timeout is required for Windows instances, you may want to tweak the following flag:
 <pre><nowiki>
 agent_version_timeout=300 # number of seconds to wait, 300 is the default
 </nowiki></pre>

@@ Line 5: / Line 5: @@
 When configuring Nova and [[XenServer]], please take care with the following settings in nova.conf.
-You can find more details on the flags in the following wiki page: [[NovaConfigOptions]]
+You can find more details on the flags in the following wiki page:
 == Networking ==

← Older revision	Revision as of 18:42, 25 July 2013
(No difference)

@@ Line 9: / Line 9: @@
 For more information on networking, see:
 * [[XenServer/NetworkingFlags]]
 == Flat Injection ==

Obsolete:XenServer/NovaFlags - Revision history

Fifieldt: Fifieldt moved page XenServer/NovaFlags to Obsolete:XenServer/NovaFlags: blank page

Fifieldt: blanking - page was very out of date

Fifieldt: /* Nova flags for XenServer */

Ryan Lane: Text replace - "__NOTOC__" to ""

Clark Boylan at 23:02, 16 February 2013

JohnGarbutt at 15:15, 23 April 2012

JohnGarbutt at 15:14, 23 April 2012

JohnGarbutt at 15:14, 23 April 2012

JohnGarbutt at 15:11, 23 April 2012

JohnGarbutt: Update the notes on the connection URL

Ryan Lane: Text replace - "NOTOC" to ""