Re: [Openstack] What is the correct config for vnc or novnc tosuccessfully enable VNC CONSOLE in a browser?

See below: > > but I get some thing strange for: > if I set > --vnc_enabled=true > --novncproxy_base_url=http://localhost:6080/vnc_auto.html > --vncserver_proxyclient_address=localhost > --vncserver_listen=0.0.0.0 > in nova.conf that it return > Oops! Goog

Re: [Openstack] make instances not communicate each other

Use the flag --allow_same_net_traffic : "This flag will allow all traffic from other vms (and host machines) in the same network. It defaults to true. If you would prefer to block all vm-vm traffic and use security groups to manage vm-vm traffic, set this flag to false." On Wed, Apr 4, 2012 at 6

Re: [Openstack] Dashboard VNC Console failed to connect to server

Lucian - Could you also paste your iptables nat rules to the question? Usually, when I get into a funky network state like you are in, I bust out tcpdump and map out exactly how packets are getting moved from interface to interface. That usually gets to the problem quickly. A On Wed, Apr 4, 20

Re: [Openstack] Dashboard VNC Console failed to connect to server

> > > I have just a question, the novnc works on wich browsers? I've tried on > firefox 10.0.2 and didn't worked. > Here is an approximate supported version list: https://github.com/kanaka/noVNC/wiki/Browser-support. I'm not sure about that exact version of FF, though I know that certain version

Re: [Openstack] Dashboard VNC Console failed to connect to server

On Fri, Mar 30, 2012 at 11:29 AM, Guilherme Birk wrote: > I installed the nova-consoleauth service and that resolved the problem of > 404 not found. Now I'm getting a cannot connect to the server > 127.0.0.1:6080. The IP 127.0.0.1 is strange, because on my nova.conf file > I have the following f

Re: [Openstack] Dashboard VNC Console failed to connect to server

I've proposed doc changes that add a FAQ and also remove references to vnc_redux (thanks for bringing that to my attention). https://review.openstack.org/6002 In the FAQ I also mention the python-numpy noVNC dependency, which appears to be biting you. A On Fri, Mar 30, 2012 at 7:56 AM, David Kr

Re: [Openstack] Dashboard VNC Console failed to connect to server

Lucian, I added a response to your question. There are several issues at play there. A On Fri, Mar 30, 2012 at 9:30 AM, Lucian Thomaz wrote: > Anthony, I tried to add this flags there and do some more things but I > didn't have sucess yet. > > I made a question in launchpad with all my networ

Re: [Openstack] Dashboard VNC Console failed to connect to server

On Fri, Mar 30, 2012 at 9:12 AM, Michaël Van de Borne < michael.vandebo...@cetic.be> wrote: > Thank you. > > I installed the package. > > Now I've got this error when I paste the vnc url (which I got with nova > get-vnc-console) in firefox: > > Traceback (most recent call last): > File "/usr/li

Re: [Openstack] Dashboard VNC Console failed to connect to server

On Fri, Mar 30, 2012 at 7:56 AM, David Kranz wrote: > I am also having problems with vnc console but not using dashboard and of > a different kind. First, the documentation says to use the vnc_redux branch > but that is evidently diablo-compatible code. So I used master and did the > same thing a

Re: [Openstack] Dashboard VNC Console failed to connect to server

It does not look like you are running nova-consoleauth. The vnc proxies use that service to verify incoming tokens. Try running that and see if that fixes things. A On Fri, Mar 30, 2012 at 6:50 AM, Guilherme Birk wrote: > Thanks for the reply. > > I've added the flags that you mentioned on m

Re: [Openstack] Dashboard VNC Console failed to connect to server

; thank you - morons-r-us is trying that suggestion right now... > > -joe > > On Mar 29, 2012, at 3:01 PM, Anthony Young wrote: > > Joe - looks like it could just be a typo: > > 1 > 2 > 3 > > --vncserver_list=172.18.1.1--vncserver_proxyclient_address=172.18.1.1--n

Re: [Openstack] Dashboard VNC Console failed to connect to server

org/3694439 > > The compute host is 172.18.1.1 with my instance (TTY, named "zerglet") > The nova vncproxy code is running at 172.17.1.50 - both have direct access > to each other - pingable, etc. 172.17.1.50 is the nova-api host for this > setup as well > > -joe > > On

Re: [Openstack] Dashboard VNC Console failed to connect to server

ailed', > was 'ProtocolVersion'. Msg: Failed to connect to server > util.js:71 <http://172.17.1.50:6080/include/util.js>New state 'failed', > was 'failed'. > > > Any ideas? > > -joe > > > On Mar 29, 2012, at 1:06 PM, An

Re: [Openstack] Dashboard VNC Console failed to connect to server

How are you generating this link: http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d349e8ee/None ? It looks like if horizon is behaving nicely the link would look like http://192.168.100.142/nova/instances_and_volumes/instances/5307a5c5-249b-4eda-b6e4-5b17d3

Re: [Openstack] Dashboard VNC Console failed to connect to server

Here are several flags that you must set on your compute host for a multi host deploy: - :option:`--vncserver_listen` - defaults to 127.0.0.1 This is the address that vncservers will bind, and should be overridden in production deployments as a pri

Re: [Openstack] regarding this Message #09165 (VNC error with latest version of Firefox)

In diablo, nova shipped its own websocket proxy, which had some browser compatibility issues due to eventlet's out-dated websocket implementation. For this reason, in essex we replaced nova-vncproxy with one more directly based on noVNC's websocket proxy. Docs for the current proxy may be found h

Re: [Openstack] BUG on dashboard (Horizon)

On Mon, Mar 26, 2012 at 11:58 AM, Guilherme Souza < souza.guilherm...@gmail.com> wrote: > All configurations are correct and the service is running, if i try to run > the status command on shell i prints running, and in fact it was, because i > need keystone to access the horizon, in a test i stop

Re: [Openstack] Horizon

I made a very simple horizon example plugin, maybe you will find this useful: https://github.com/cloudbuilders/simple_horizon_plugin On Thu, Mar 22, 2012 at 5:16 AM, Hallvard Westman < hallvard.west...@gmail.com> wrote: > I would like an answer to this question : > http://osdir.com/ml/openstack-

Re: [Openstack] Configuring Nova VNC Proxy_Essex_rc1

an access > URL back, but it is using the host 127.0.0.1 which obviously poses an issue > when I access my dashboard from a different host. Any idea where else I > might be able to change this? > > Thanks, > > * > * > > Andrew > > From: Anthony Young > Date:

Re: [Openstack] Configuring Nova VNC Proxy_Essex_rc1

> > When I try to execute "nova get-vnc-console " I > don't get a response... > > This sounds like you are not running nova-console-auth. There are references to that in the docs, and you can see a working configuration using that process in devstack. A > * > * > > *Andrew Weiss* > > wei...@pu

Re: [Openstack] Configuring Nova VNC Proxy_Essex_rc1

Hey Andrew, You can see out the main vnc doc in the nova source tree: https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst Let me know if have any additional questions, or if anything is unclear (so I can help you out and update the docs accordingly :) Anthony On Mon

Re: [Openstack] question of novncproxy

DeadSun, I just made a pass at trying to improve the vnc proxy docs a bit. Could you join me in reviewing this patch until the docs answer all your questions? https://review.openstack.org/#change,5086 Thanks, Anthony 2012/3/8 DeadSun > Essex4 > In mutil hosts, does any nova-compute need to

Re: [Openstack] devstack and stable/diablo

Anthony Those bugs are all fixed in the master branch a while ago. > Thanks, > > Yun > > On Tue, Feb 21, 2012 at 2:51 PM, Anthony Young > wrote: > > > > On Tue, Feb 21, 2012 at 11:23 AM, Yun Mao wrote: > >> > >> What's the recomme

Re: [Openstack] devstack and stable/diablo

On Tue, Feb 21, 2012 at 11:23 AM, Yun Mao wrote: > What's the recommended way to play with stable/diablo with devstack? > Ideally: > git checkout stable/diablo > ./stack.sh Which you are probably doing. > We've been using the stable/diablo branch of devstack but stack.sh in > that branch is

Re: [Openstack] Creating boot-from-volume capable image and volume

"while ! ping -c1 -w1 >>> $FLOATING_IP; do sleep 1; done"; then >>> +# echo "Couldn't ping volume-backed server with floating ip" >>> +#exit 1 >>> +#fi >>> >>> # Make sure our volume-backed instance launched >>> -ssh -o

Re: [Openstack] XCP toolstack support for devstack

Todd, Mike - This looks great! From the looks of things, the main difference seem to be slight changes due to the fact that dom0 is ubuntu, rather than redhat. Is that accurate? If so, it seems like it should be straightforward to support both with roughly the same code, and just if-else the u

Re: [Openstack] Creating boot-from-volume capable image and volume

$KEY_FILE cirros@$FLOATING_IP << EOF > +ssh -o StrictHostKeyChecking=no -i $KEY_FILE cirros@$IP << EOF > echo "success!" > EOF > > @@ -206,7 +209,7 @@ > nova delete $INSTANCE_NAME > > # De-allocate the floating ip > -nova floating-ip-de

Re: [Openstack] Flavor change in Essex?

It sounds like we need to update the cli to reflect this disk-configuration-parity change. It is also likely that some nova-api work will need to be done to get this humming. https://bugs.launchpad.net/nova/+bug/932423 On Tue, Feb 14, 2012 at 1:57 PM, Jesse Andrews wrote: > Deliberate change. >

Re: [Openstack] Creating boot-from-volume capable image and volume

On Fri, Feb 10, 2012 at 8:51 PM, Tomoe Sugihara wrote: > Hi folks, > > Could someone tell me what is the right way to do boot-from-volume? > Especially, how to create boot-from-volume capable image and volume? > My understanding is that, since openstack API requires imageRef, we > need to pass in

Re: [Openstack] flags.DEFINE helpers in nova-novncproxy

Hey Ken, A bug was opened against devstack for this issue: https://bugs.launchpad.net/devstack/+bug/924058 I just pushed a fix, which updates nova-novncproxy to use the new style of flags. Thanks for reporting this. Anthony On Mon, Jan 30, 2012 at 4:14 PM, Ken Thomas wrote: > Greetings all,

Re: [Openstack] Error while installing devstack

I'm not sure of the exact reason why this is failing - it could be an issue with how pip deals with git connections when a proxy is specified. It could also be a transient git network issue. If the latter is the issue, you may try running stack.sh again. Regardless, openstack.compute is no longe

Re: [Openstack] libvirt issues

hua Harlow ---01/18/2012 03:59:19 > PM---I've also had to run the following before. Might be useful]Joshua > Harlow ---01/18/2012 03:59:19 PM---I've also had to run the following > before. Might be useful for others. Might be a bug somewhere that > > From: Joshua Harl

Re: [Openstack] libvirt issues

It is likely that one of devstack, nova, openstackx, or dashboard are out-of-date. You should update those directories, and then re-run stack.sh A On Wed, Jan 18, 2012 at 8:42 AM, Mohammad Banikazemi wrote: > I resolved the 2nd problem by using "virsh undefine instance-0002". > Still have

Re: [Openstack] has anyone tried devstack this morning

< > gabriel.hur...@nebula.com> > > wrote: > > > > Confirmed that as of about 5 PM PST today, devstack is no longer broken. > I > > used it to install quantum yesterday, and as far as I can tell, Quantum > is > > in a semi-working state in relation to

Re: [Openstack] how to verify nova uses openstackx extensions?

In your nova-api log, you should see lines like the following if openstackx is loading: 2012-01-18 09:32:01,329 DEBUG nova.api.openstack.extensions [-] Loading extension extensions.admin.Admin from (pid=3731) debug /opt/stack/nova/nova/log.py:1752012-01-18 09:32:01,620 DEBUG nova.api.openstack.ext

Re: [Openstack] has anyone tried devstack this morning

stackx. That doesn’t fix the overall problem at all, > sadly. > > ** ** > > **- **Gabriel > > ** ** > > *From:* Anthony Young [mailto:sleepsonthefl...@gmail.com] > *Sent:* Tuesday, January 17, 2012 5:09 PM > *To:* Debo Dutta (dedutta) > *Cc:*

Re: [Openstack] has anyone tried devstack this morning

Hey Debo - A fix has been merged for https://bugs.launchpad.net/devstack/+bug/917457 - hopefully that resolves your issue! Anthony On Tue, Jan 17, 2012 at 4:00 PM, Debo Dutta (dedutta) wrote: > Thanks …. I tried installing devstack with Quantum and ignoring the > horizon error messages (for now

Re: [Openstack] Multinode installation (with devstack on the master)

Hey Sagar, Are you able to produce logs from n-cpu? If you are in the screen session, you should be able to switch to the window (ctrl-a + [number]) of that name and use ctrl-a + [ to enable interactive scrollback (uses vim keybindings). I think there is a chance that some data from a previous ru

Re: [Openstack] Multinode installation (with devstack on the master)

Hey Sagar, I'll take a quick guess here that maybe your servers have host names that don't resolve. So for example, if host1 is 'server1' and host2 is 'server2' the vnc proxy may try connect using those hostnames (connecting to the latter host would probably fail). A quick fix could be to add an

Re: [Openstack] Multinode installation (with devstack on the master)

Hey Sagar, It does sound like you need to use eth1 for FLAT_INTERFACE - but note this parameter is used when your network is first created with nova-manage, so if you change this you will need to re-run stack.sh (it isn't enough to update your nova.conf), which is probably best to do after a reboo

Re: [Openstack] Multinode installation (with devstack on the master)

> > > > In this case, how should i tweak my localrc file to get network access > for my VMs? I have setup SNAT on the master node to provide external > network access to machines in the network 192.168.2.0/24. All my VMs are > given ips in the fixed range 192.168.3.0/24. > Is each machine conf

[Openstack] VNC Console Cleanup Specification

Hey All, I've been working on a spec to cleanup VNC consoles for consistency and xs/libvirt parity: http://wiki.openstack.org/VNCConsoleCleanup (related to blueprint https://blueprints.launchpad.net/nova/+spec/vnc-console-cleanup ) The proposal aims to create a consistent (ie hypervisor independe

Re: [Openstack] how to list all account and get disk usage info?

Take a look at this extension: https://github.com/openstack/nova/blob/master/nova/api/openstack/v2/contrib/simple_tenant_usage.py I don't believe a client has yet been added to python-novaclient to access this endpoint, though it should be simple enough to implement. A On Wed, Nov 30, 2011 at 2

Re: [Openstack] Whats the process for devstack suggestions and bug reports

Hey Michael, There is a launchpad project here: https://launchpad.net/devstack >From there you can submit blueprints and bug reports. We are in the process of moving the main repo from https://github.com/cloudbuilders/devstack to https://github.com/openstack-dev/devstack and gerrit, and that mo

Re: [Openstack] Problems with dashboard and keystone

Could this be related? https://lists.launchpad.net/openstack/msg04657.html A On Thu, Oct 13, 2011 at 7:39 PM, 李沐洋 wrote: > Hi all! > > I installed OpenStack using the script from devstack. > > It seemed all right until I logged in Dashboard. > > It showed > > Unable to get usage info: 401 Unau

Re: [Openstack] Several keystone questions ...

Looks cool! When do you think you'll be ready to propose these changes back into trunk? A On Mon, Oct 10, 2011 at 7:32 AM, Dmitry Maslennikov < dmaslenni...@griddynamics.com> wrote: > On Thu, Oct 6, 2011 at 3:49 PM, Kuo Hugo wrote: > > 3. We can using cloud with Dashbord smoothly for basic usa

Re: [Openstack] Several keystone questions ...

> > > 1. What's the difference of python-novaclient between > devstack > and rackspace , as I > know devstack's version forked from rackspace.. but while I install each of > them... only devstack'

Re: [Openstack] keystone + dash + diablo user flows

Hey Luis, I ran into the same issue last week when I was implementing this for dashboard. I filed a bug on launchpad here: https://bugs.launchpad.net/keystone/+bug/857671 The issue is that for admin users, all tenants get returned on GET /tenants, including tenants for which the admin is not a m

Re: [Openstack] Diablo 4 dashboard error Unable to get usage info: (OperationalError) no such column: vm_state

vm_state was added to the instance model in d4 - if you are upgrading, you will need to migrate: nova-manage db sync A On Tue, Sep 13, 2011 at 9:21 AM, atkisc wrote: > ** > hi > when i run the diablo-4 dashboard,Has the following error : > > > Unable to get usage info: (OperationalError) no

Re: [Openstack] Diablo 4 dashboard error missing openstackx extensions in nova.

Another thing to check - the os1.1 keystone endpoints have been modified in d4 to include a tenant prefix. If you are upgrading an existing install, you may need to update your keystone service catalog accordingly: keystone-manage $* endpointTemplates add RegionOne nova http://<%= api_vip %>:8774

Re: [Openstack] Diablo 4 dashboard error missing openstackx extensions in nova.

Make sure that the openstackx/extensions contents are accessible via the flag FLAGS.osapi_extensions_path. nova-api uses that flag to dynamically load external extensions. Anthony On Mon, Sep 12, 2011 at 7:52 AM, shake chen wrote: > Hi > > I run Diablo 3 and dashboard, all the component is wor

Re: [Openstack] Can't create an instance with openstack-dashboard

Thanks, Jae - I pushed a change like you mention below to openstackx. At this point, most of the features we need for dashboard support of servers.create have been pushed to nova core, so we should be able to get rid of the openstackx dep for this call. A 2011/9/8 Jae Sang Lee > self answer :)

Re: [Openstack] VNC and dashboard

Hey Carlo, Not sure what the exact issue is in that question as I'm having trouble reproducing, but I left a comment with a guess. It is worth noting that the protocol that is used to set up the proxy is different for html5 browsers like safari/chrome versus Firefox(and I suppose IE?). In Chrome

Re: [Openstack] VNC consoles for all

The main issue was that maintaining ec2 extensions was becoming too hairy, which is why the original doc talks about using the direct api client to get a console url. Dashboard support for vnc was subsequently added through the community using dashboard's ec2 extensions. Proper support for vnc co