Just to follow-up, I got all of this working yesterday evening. Result of my own far fingering, can't remember what root cause was...
//adam *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1 302-387-4660 Direct: +1 916-246-2072 On Thu, Oct 22, 2015 at 10:40 PM, Adam Lawson <[email protected]> wrote: > Looks like I may have hosed the VNC settings in tryng to fixz a bad DNS > issue with fuel inserting an unknown string "i.e. public.fuel.blah" into > the DNS access path. > . > What are the correct IP settings so I can connect to VNC within Horizon? > > Currently, Horizon appears to be listening on 172.16.149.4 > The controller currently has novncproxy_host=172.16.149.5 (if I set this > to 172.16.149.4 I get a 503 error) > > The compute node has > novncproxy_base_url=https://172.16.149.5:6080/vnc_auto.html (If I set > this .4 I also get a 503 error in Horizon) > vncserver_listen=0.0.0.0 > vncserver_proxyclient_address=192.168.1.7 (I changed this manually; I know > it should be IP of compute node -- can't remember which IP to use) > > > > *Adam Lawson* > > AQORN, Inc. > 427 North Tatnall Street > Ste. 58461 > Wilmington, Delaware 19801-2230 > Toll-free: (844) 4-AQORN-NOW ext. 101 > International: +1 302-387-4660 > Direct: +1 916-246-2072 > >
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
