ph0tek's profile - activity

2016-12-30 12:21:41 -0600 received badge  Great Answer (source)
2016-11-06 11:50:54 -0600 received badge  Good Answer (source)
2016-11-05 11:50:45 -0600 received badge  Nice Answer (source)
2016-09-18 07:06:55 -0600 received badge  Teacher (source)
2016-09-18 04:17:53 -0600 received badge  Editor (source)
2016-09-18 03:00:42 -0600 answered a question [Devstack] Instance console keyboard error

I had the same problem, it seems to be a bug in noVNC, I also saw it at: https://bugs.launchpad.net/horizon/+bug/1622684 (https://bugs.launchpad.net/horizon/+b...)

I was able to work around it by using an older version of noVNC. go to /opt/stack/noVNC and do a git checkout v0.6.0. Then reload the the console for the instance.

Alternatively you can add NOVNC_BRANCH=v0.6.0 to your local.conf file, and restack.

2016-02-01 04:57:52 -0600 received badge  Enthusiast
2016-01-28 05:57:07 -0600 answered a question neutron l2-gateway installation for packstack

After some googling I found:

neutron-l2gw-db-manage --config-file /etc/neutron/neutron.conf upgrade head

This creates the tables, and works for me.

I found some useful info at: http://kimizhang.com/neutron-l2-gateway-hp-5930-switch-ovsdb-integration/ (http://kimizhang.com/neutron-l2-gatew...)

Hope this helps.

2016-01-28 05:17:31 -0600 commented question neutron l2-gateway installation for packstack

I have the same issue using openstack Kilo on Ubuntu. It seems that the tables were not created using the pip install. It would be nice if they could be added manually, or using another pip command.

2015-03-01 01:24:19 -0600 received badge  Famous Question (source)
2015-02-09 03:14:01 -0600 commented answer nova get-serial-console produces HTTP 400 error

Thanks! Indeed the issue was that I didn't update the nova.conf of the compute nodes. Now it seems to work.

2015-02-09 03:12:52 -0600 received badge  Notable Question (source)
2015-02-06 11:20:31 -0600 received badge  Popular Question (source)
2015-02-06 03:55:41 -0600 asked a question nova get-serial-console produces HTTP 400 error

Hi,

I am testing Openstack Juno, using a dedicated controller and two compute nodes. For this test, would like to access the serial console port of my VM's as currently is possible using nova-get-serial-console.

I am using Cirros as a test VM.

As documented elsewhere, I started the serial proxy:

2015-02-06 09:41:02.038 15179 INFO nova.console.websocketproxy [-] WebSocket server settings:
2015-02-06 09:41:02.039 15179 INFO nova.console.websocketproxy [-]   - Listen on 0.0.0.0:6083
2015-02-06 09:41:02.039 15179 INFO nova.console.websocketproxy [-]   - Flash security policy server
2015-02-06 09:41:02.039 15179 INFO nova.console.websocketproxy [-]   - No SSL/TLS support (no cert file)
2015-02-06 09:41:02.040 15179 INFO nova.console.websocketproxy [-]   - proxying from 0.0.0.0:6083 to None:None

When I issue a telnet to it on port 6083, I get a connection, so it is running.

But when I request a serial console, I get the following:

[node-4 ~]# nova get-serial-console test6
ERROR (BadRequest): Unavailable console type serial. (HTTP 400) (Request-ID: req-bbec8a4e-58ff-40f2-ac0e-503c0be9777b)

Does anyone have any insight what might be the problem?

Thanks in advance for your support.

2014-12-09 03:27:05 -0600 received badge  Famous Question (source)
2014-10-09 10:33:48 -0600 received badge  Notable Question (source)
2014-10-03 09:47:53 -0600 received badge  Scholar (source)
2014-10-02 21:11:23 -0600 received badge  Popular Question (source)
2014-10-02 15:08:49 -0600 commented answer Accessing serial port of running instance

Thanks for your feedback, I will keep an eye out, and for now try to do it using KVM.

2014-10-02 04:04:08 -0600 asked a question Accessing serial port of running instance

Hi,

Is it possible to remotely access a serial port of an instance (eg /dev/ttyS1), just like you can access the console through Horizon?

This is possible under Virtualbox by creating a 'host pipe' so that the hypervisor creates a file for the serial port of your VM which you can read from and write to.

Are there options like this to configure this in Nova? Or should I look in the direction of the hypervisor that we are using? (KVM)

If anyone has experience in this, I would help a lot.

Thanks in advance.