Implement instance VNC console on Google Chrome

HowTO







1. bzr merge this branch to django-dashboard (thanks for Joe)
https://code.launchpad.net/~sleepsonthefloor/openstack-dashboard/vnc_console


2. get Cactus source code
https://answers.launchpad.net/+branch/nova/cactus

3. copy two binaries to /usr/bin
nova-vncproxy
nova-direct-api

4. config nova.conf
--vnc_console_proxy_url=http://192.168.1.1:6080 
--vnc_enabled=True
--vncproxy_host=192.168.1.1
--vncproxy_url=http://172.16.4.75:6080 #the ip depends on which network you want to use VNC console

5.Add noVNC
Download noVNC , noVNC must be in the location specified by –vncproxy_wwwroot, which defaults to /var/lib/nova/noVNC. nova-vncproxy will fail to launch until this code is properly installed.

6. iptable rule on nova-network host (depends on different situation, customize)
-A PREROUTING -d 172.16.4.75/32 -p tcp -m tcp --dport 8000 -j DNAT --to-destination 192.168.1.1:8000
-A PREROUTING -d 172.16.4.75/32 -p tcp -m tcp --dport 6080 -j DNAT --to-destination 192.168.1.1:6080

7. run up service
/usr/bin/nova-direct-api --flagfile=/etc/nova/nova.conf
/usr/bin/nova-vncproxy --flagfile=/etc/nova/nova.conf --logfile=/var/log/nova/nova-vncproxy.log


=Limitation=
Must use Google Chrome
Must enable ssh PassworkAuth , and have an exist account/passwd
Maybe it will be better later....


Comments

  1. JesseMay 17, 2011 at 7:39 AM

    Hi Hugo,

    I have a two nodes cloud running. Below is the nova.conf file.

    --dhcpbridge_flagfile=/etc/nova/nova.conf
    --dhcpbridge=/usr/bin/nova-dhcpbridge
    --logdir=/var/log/nova
    --state_path=/var/lib/nova
    --lock_path=/var/lock/nova
    --verbose
    --sql_connection=mysql://root:nova@10.1.1.1/nova
    --s3_host=192.168.0.2
    --cc_host=10.1.1.1
    --rabbit_host=10.1.1.1
    --ec2_host=192.168.0.2
    --ec2_url=http://192.168.0.2:8773/services/Cloud
    --network_manager=nova.network.manager.FlatDHCPManager
    --fixed_range=10.1.1.0/24
    --network_size=253
    --flat_network_dhcp_start=10.1.1.2
    --public_interface=eth0
    --flat_interface=eth1
    --flat_injected=False
    --iscsi_ip_prefix=10.1.1
    --glance_host=10.1.1.1
    --image_service=nova.image.glance.GlanceImageService

    In this case, how should I configure the vnc in the nova.conf?

    Thank you.

    Jesse

    ReplyDelete
  2. Hugo K.May 17, 2011 at 10:34 AM

    --vnc_console_proxy_url=http://192.168.1.1:6080
    --vnc_enabled=True
    --vncproxy_host=192.168.1.1
    --vncproxy_url=http://172.16.4.75:6080

    ReplyDelete
  3. JesseMay 18, 2011 at 12:54 AM

    Hi Hugo,

    Thanks for responding. I'm still confused with the ip addresses, 192.168.1.1, 172.16.4.75 and 192.168.2.4(ip of server 30) in your case. In my case, the public ip of the cloud controller is 192.168.0.2 and the private ip is 10.1.1.1, the ip of instance is 10.1.1.2. How should I configure the vnc?

    Thank you very much.

    Jesse

    ReplyDelete
  4. Hugo K.May 18, 2011 at 11:06 AM

    OK, I know the reason why that you feel confusing.
    Bcz the environment is a little bit different from regular one.

    In your case
    --vnc_console_proxy_url=http://192.168.0.2:6080
    --vnc_enabled=True
    --vncproxy_host=192.168.0.2
    --vncproxy_url=http://192.168.0.2:6080

    btw , you can try to drop
    --vnc_console_proxy_url=http://192.168.0.2:6080
    I think it's wrong flag in VNC instruction from OPENSTACK. I found that VNCproxy try to use "--vncproxy_url" instead of the first one for setting VNC porxy address....

    ReplyDelete
  5. kopiluwak nyaApril 11, 2015 at 4:02 PM

    https://www.facebook.com/bantalsilikongrosir
    http://bantalsilikon01.blogspot.com/2014/12/a.html
    http://jualsangkarpleci.blogspot.com/2014/12/a.html
    http://kopiluwakliar01.blogspot.com/2014/12/a.html
    http://vvty.in/uncategorized/marinir-seo/

    http://marinirseo.blogspot.com/2014/12/a.html
    http://marinir-seo.blogspot.com/2014/12/a.html
    http://bumbu-pecel-malang.blogspot.com/2014/12/a.html
    http://distro-seo.blogspot.com/2014/12/a.html
    http://restoran-seo.blogspot.com/2014/12/a.html
    http://bantalmalangmurah.blogspot.com/2014/12/a.html
    http://distrobantal.blogspot.com/2014/12/a.html
    http://kesethandukmalang.blogspot.com/2014/12/a.html

    http://tasya.marinirseo.web.id/?p=4http://caca.marinirseo.web.id/?p=4http://anne.marinirseo.web.id/?p=4http://jeannet.marinirseo.web.id/?p=4http://jelita.marinirseo.web.id/?p=4http://brenda.marinirseo.web.id/?p=1http://ruth.marinirseo.web.id/?p=4http://tasya1.marinirseo.web.id/?p=4http://caca1.marinirseo.web.id/?p=4http://anne1.marinirseo.web.id/?p=4http://jeannet1.marinirseo.web.id/?p=4http://jelita1.marinirseo.web.id/?p=4http://brenda1.marinirseo.web.id/?p=1http://ruth1.marinirseo.web.id/?p=4http://tasya2.marinirseo.web.id/?p=4http://caca2.marinirseo.web.id/?p=5http://anne2.marinirseo.web.id/?p=4http://jeannet2.marinirseo.web.id/?p=4http://jelita2.marinirseo.web.id/?p=4http://brenda2.marinirseo.web.id/?p=1http://ruth2.marinirseo.web.id/?p=4http://ruth3.marinirseo.web.id/?p=3http://jelita3.marinirseo.web.id/?p=3http://brenda3.marinirseo.web.id/?p=3http://jeannet3.marinirseo.web.id/?p=3http://anne3.marinirseo.web.id/?p=3http://caca3.marinirseo.web.id/?p=3http://tasya3.marinirseo.web.id/?p=3http://tasya4.marinirseo.web.id/?p=4http://caca4.marinirseo.web.id/?p=4http://anne4.marinirseo.web.id/?p=4http://jeannet4.marinirseo.web.id/?p=4http://jelita4.marinirseo.web.id/?p=4http://brenda4.marinirseo.web.id/?p=6http://ruth4.marinirseo.web.id/?p=4http://tasya5.marinirseo.web.id/?p=4http://caca5.marinirseo.web.id/?p=4http://anne5.marinirseo.web.id/?p=4http://jelita5.marinirseo.web.id/?p=4http://ruth5.marinirseo.web.id/?p=4
    http://tasya.marinirseo.web.id/?p=4http://caca.marinirseo.web.id/?p=4http://anne.marinirseo.web.id/?p=4http://jeannet.marinirseo.web.id/?p=4http://jelita.marinirseo.web.id/?p=4http://brenda.marinirseo.web.id/?p=1http://ruth.marinirseo.web.id/?p=4http://tasya1.marinirseo.web.id/?p=4http://caca1.marinirseo.web.id/?p=4http://anne1.marinirseo.web.id/?p=4http://jeannet1.marinirseo.web.id/?p=4http://jelita1.marinirseo.web.id/?p=4http://brenda1.marinirseo.web.id/?p=1http://ruth1.marinirseo.web.id/?p=4http://tasya2.marinirseo.web.id/?p=4http://caca2.marinirseo.web.id/?p=5http://anne2.marinirseo.web.id/?p=4http://jeannet2.marinirseo.web.id/?p=4http://jelita2.marinirseo.web.id/?p=4http://brenda2.marinirseo.web.id/?p=1http://ruth2.marinirseo.web.id/?p=4http://ruth3.marinirseo.web.id/?p=3http://jelita3.marinirseo.web.id/?p=3http://brenda3.marinirseo.web.id/?p=3http://jeannet3.marinirseo.web.id/?p=3http://anne3.marinirseo.web.id/?p=3http://caca3.marinirseo.web.id/?p=3http://tasya3.marinirseo.web.id/?p=3http://tasya4.marinirseo.web.id/?p=4http://caca4.marinirseo.web.id/?p=4http://anne4.marinirseo.web.id/?p=4http://jeannet4.marinirseo.web.id/?p=4http://jelita4.marinirseo.web.id/?p=4http://brenda4.marinirseo.web.id/?p=6http://ruth4.marinirseo.web.id/?p=4http://tasya5.marinirseo.web.id/?p=4http://caca5.marinirseo.web.id/?p=4http://anne5.marinirseo.web.id/?p=4http://jelita5.marinirseo.web.id/?p=4http://ruth5.marinirseo.web.id/?p=4

    ReplyDelete

Post a Comment

Popular posts from this blog

The method of Web Service HA+LB in OPENSTACK NOVA for private cloud only

Image
Cloud Server HA+LB  in NOVA


Our purpose is to provide uninterrupted   web services  with low cost in OPENSTACK. Due to all instances traffic through Nova-Network host in a basic deployment of NOVA . And it's hard to do HA+LB for Nova-Network. As I know it will be very hard to implement. 
After read "Bootstrapping OpenStack Clouds" doc writed by DELL....The fault zone concept it much easier and cheaper. 



There're three diagrams ....
I.Two zones topology , share nothing between each zones. But combine two instance network in same network segment. Zone1 using 192.168.1.0/25,   Zone2 using 192.168.1.128/25 . We do  not using floating ip. Let instance route from Core Network  Switch directly.




Read more