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. 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. --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. 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. 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. 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

OpenStack Swift (ep0) - 進化的儲存系統與需求

存儲方案的演進

OpenStack Object Storage, 代號 Swift 的計劃在2011年 OpenStack Cloud Computing 計劃中正式啟動.

起初的目標要能夠支撐史無前例快速增長的資料量, 它也證明了Open Source的儲存系統確實能處理極大規模的資料.

就在大量線上資料被產出的年代, 對於 Object Storage 而言, 無疑是出現在世界上最佳的時間點. Software Defined Storage(SDS) 正是演化中的新一代儲存選擇.


今日的資料儲存需求

在連接裝置(行動裝置, 終端設備) 爆炸的年代, 對於儲存系統的需求正以指數型成長. 使用者正以前所未有的速度產生資料與消耗存儲資源. 包含社交媒體, 線上影音, 用戶資料, 遊戲資訊還有玲琅滿目的 Software-as-a-Service 應用. 對於儲存系統有了新的需求, 廣泛的應用方法, 方便的存取, 不能有臨界點的增長能力. 廣大的企業與機構正面臨越來越多的儲存需求. 在科學界, 分析出來的數據如果能更有效被儲存與取得也更具價值. 動態影像正無止盡的追求高畫質產品. 企業累積越來越大量的資料, 員工需要更即時的存取資料來提升協同工作的效率.

這些都是什麼資料？ 大多數都是 "Unstructured data". 這意味著資料並沒有預先定義的形態而且基本上都是儲存為個別的檔案, 相對於資料庫中的某筆資料(structured data). 包含靜態影像, 動態影像, 電子郵件, 文件以及各種格式的檔案. 這些資料來自每一年消費者與各行業數十億的終端裝置藉由網路存取.


儲存Unstructured Data的條件

通常需要確保資料的耐久力, 可存取性, 可管理性還有相對低成本.

耐久力 - 資料可以說是最重要的東西而且有無法取代的特性. 許多形態的資料必須被永久保存. 在資料中心, 大部分Unstructured Data需要能被保存非常久的時間以符合客戶的期望或是一些法律上面的條件.

可存取性 - 讓許多終端裝置無論在何時何處都能立即的取得. 使用者期望在行動裝置, 筆電或是在家裡的桌上電腦都能夠順利獲取需要的資料.

可管理性 - 大型儲存系統的管理也是一個重要的課題. 如何讓幾個管理者輕鬆管理大量的儲存設備.

低成本 - 只要資金足…
Read more