cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Angus <paul.an...@shapeblue.com>
Subject RE: Any way to cause CloudStack to use non-primary NIC
Date Wed, 22 Nov 2017 17:05:24 GMT
Hi Jay,

I assume here that you are talking about the management server and the IP address that CloudStack
tells remote resources to connect to it over...?

There is a global setting called 'host' which specifies that particular IP.
It's initially set when you run cloudstack-setup-databases.  You can add ' -i 123.123.123.123'
to specify a specific address, otherwise it defaults back to the 'main' IP on that host.

You can also update the 'host' global setting and restart the management server, you may need
to check that IP tables allows 8080, 9090 and 8250 in to your alternate address, but CloudStack
listens on all local addresses.



Kind regards,

Paul Angus

paul.angus@shapeblue.comĀ 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-----Original Message-----
From: Jay Hahn-Steichen [mailto:pesher.tehelim@gmail.com] 
Sent: 20 November 2017 06:44
To: users@cloudstack.apache.org
Subject: Any way to cause CloudStack to use non-primary NIC

All:

I would like to experiment with a cloudstack configuration where the primary NIC (e.g. eth0)
is used only for logging into the server directly, and the cloudstack components use eth1.
 The two nics are on different LAN segments.

From my reading of the docs, there is a built-in assumption that cloudstack will use eth0.
 Is there a place/way to change this default behavior?

Thanks.
--jay
Mime
View raw message