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 KuoMay 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 KuoMay 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. UnknownApril 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
  6. gunardiJune 6, 2019 at 6:58 AM

    Hello It’s really a nice and helpful piece of info. I am happy that you shared this helpful info with us. Please stay us informed like this. Thank you for sharing. bye
    Tangki Panel
    Tangki Fiberglass
    Jual Septic Tank

    ReplyDelete
  7. Aditi RayJuly 28, 2019 at 8:25 PM

    TreasureBox is operated by a group of young, passionate, and ambitious people that are working diligently towards the same goal - make your every dollar count, as we believe you deserve something better
    rabbit hutch nz
    bed frames nz
    cheap outdoor furniture nz

    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

OpenStack Swift - Container Sync (New & Old ways)

Image
OpenStack Swift Container-Sync  Swift 內建功能利用背景工作, 讓 Container to Container 如同鏡像一樣同步所有資料. 不僅僅是自己的Container, 還可以跟其他人Account內的Container相互同步資料. 這個功能也被部分企業用來將資料從舊的Swift Cluster轉移到新的環境上. 提示 如果User request是對object做POST的操作, 操作內容不一定會被同步, 除非object_post_as_copy = true 在 Proxy server 的設定, 目前這個值預設為開啟 true. 同步的設定可以有幾種模式 : One-way sync : 單向同步 containerA --> containerB Two-way sync : 雙向同步 containerA <--> containerB Chain : 鏈狀同步 containerA --> containerB --> containerC --> containerA 首先你必須要知道目前有兩種方法(新/舊)來設定 Container Sync First of all, you need to know there are two styles for setting container-sync currently.  OLD-style(舊): Supported since Swift's initial release. 任何版本,包含新版本 NEW-style(新): Implemented in Swift 1.12  or later. 在1.12版本後才釋出 不論新舊styles, 都有一個重要的前提, 原資料所在的Container Server, 必須要能跟遠端目標Container 的 Proxy Server 透過網路連結的到. NEW-Style - 多了realm(域)的觀念. 新的做法需要先建立一個設定檔 ( /etc/swift/container-sync-realms.conf )在兩個叢集的"所有"節點. 具體一點來說, 只要會涉及到這個同步過程的所有Pro
Read more