subject:"\[openstack\-dev\] \[nova\]\[serial\-console\-proxy\]"

Re: [openstack-dev] [nova][serial-console-proxy]

2015-12-14 Thread Prathyusha Guduri

Hi Markus,

Thanks a lot for a detailed document. I had a problem with installing
websocket but using the git repo u shared, I could install successfully and
got a console.

Regards,
Prathyusha

On Mon, Dec 14, 2015 at 11:34 PM, Markus Zoeller 
wrote:

> Prathyusha Guduri  wrote on 12/11/2015
> 06:37:02 AM:
>
> > From: Prathyusha Guduri 
> > To: "OpenStack Development Mailing List (not for usage questions)"
> > 
> > Date: 12/11/2015 06:39 AM
> > Subject: [openstack-dev] [nova][serial-console-proxy]
> >
> > Hi All,
>
> > I have set up open stack on an Arm64 machine and all the open stack
> > related services are running fine. Also am able to launch an instance
> > successfully. Now that I need to get a console for my instance. The
> > noVNC console is not supported in the machine am using. So I have to
> > use a serial-proxy console or spice-proxy console.
>
> > After rejoining the stack, I have stopped the noVNC service and
> > started the serial proxy service in  /usr/local/bin  as
> >
> > ubuntu@ubuntu:~/devstack$ /usr/local/bin/nova-serialproxy --config-
> > file /etc/nova/nova.conf
> > 2015-12-10 19:07:13.786 21979 INFO nova.console.websocketproxy [-]
> > WebSocket server settings:
> > 2015-12-10 19:07:13.786 21979 INFO nova.console.websocketproxy [-]
> -Listen on
> > 0.0.0.0:6083
> > 2015-12-10 19:07:13.787 21979 INFO nova.console.websocketproxy [-]   -
> > Flash security policy server
> > 2015-12-10 19:07:13.787 21979 INFO nova.console.websocketproxy [-]   -
> > No SSL/TLS support (no cert file)
> > 2015-12-10 19:07:13.790 21979 INFO nova.console.websocketproxy [-]   -
> > proxying from 0.0.0.0:6083 to None:None
>
> > But
> > ubuntu@ubuntu:~/devstack$ nova get-serial-console vm20
> > ERROR (ClientException): The server has either erred or is incapable
> > of performing the requested operation. (HTTP 500) (Request-ID: req-
> > cfe7d69d-3653-4d62-ad0b-50c68f1ebd5e)
>
> >
> > the problem seems to be that the nova-compute is not able to
> > communicate with nova-serial-proxy. The IP and port for serial proxy
> > that I have given in nova.conf is correct.
>
> > I really dont understand where am going wrong. Some help would be very
> > grateful.
> >
>
> > My nova.conf -
> >
> >
> > [DEFAULT]
> > vif_plugging_timeout = 300
> > vif_plugging_is_fatal = True
> > linuxnet_interface_driver =
> > security_group_api = neutron
> > network_api_class = nova.network.neutronv2.api.API
> > firewall_driver = nova.virt.firewall.NoopFirewallDriver
> > compute_driver = libvirt.LibvirtDriver
> > default_ephemeral_format = ext4
> > metadata_workers = 24
> > ec2_workers = 24
> > osapi_compute_workers = 24
> > rpc_backend = rabbit
> > keystone_ec2_url = http://10.167.103.101:5000/v2.0/ec2tokens
> > ec2_dmz_host = 10.167.103.101
> > vncserver_proxyclient_address = 127.0.0.1
> > vncserver_listen = 127.0.0.1
> > vnc_enabled = false
> > xvpvncproxy_base_url = http://10.167.103.101:6081/console
> > novncproxy_base_url = http://10.167.103.101:6080/vnc_auto.html
> > logging_context_format_string = %(asctime)s.%(msecs)03d %(levelname)s
> > %(name)s [%(request_id)s %(user_name)s %(project_name)s]
> %(instance)s%(message)s
> > force_config_drive = True
> > instances_path = /opt/stack/data/nova/instances
> > state_path = /opt/stack/data/nova
> > enabled_apis = ec2,osapi_compute,metadata
> > instance_name_template = instance-%08x
> > my_ip = 10.167.103.101
> > s3_port = 
> > s3_host = 10.167.103.101
> > default_floating_pool = public
> > force_dhcp_release = True
> > dhcpbridge_flagfile = /etc/nova/nova.conf
> > scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler
> > rootwrap_config = /etc/nova/rootwrap.conf
> > api_paste_config = /etc/nova/api-paste.ini
> > allow_migrate_to_same_host = True
> > allow_resize_to_same_host = True
> > debug = True
> > verbose = True
> >
> > [database]
> > connection = mysql://root:open@127.0.0.1/nova?charset=utf8
> >
> > [osapi_v3]
> > enabled = True
> >
> > [keystone_authtoken]
> > signing_dir = /var/cache/nova
> > cafile = /opt/stack/data/ca-bundle.pem
> > auth_uri = http://10.167.103.101:5000
> > project_domain_id = default
> > project_name = service
> > user_domain_id = default
> > password = open
> > username = nova
> > auth_url = http://10.167.103.101:35357
> > auth_plugin = password
> >
> > [oslo_concurrency]
> > lock_path = /opt/st

Re: [openstack-dev] [nova][serial-console-proxy]

2015-12-14 Thread Markus Zoeller

Prathyusha Guduri  wrote on 12/11/2015 
06:37:02 AM:

> From: Prathyusha Guduri 
> To: "OpenStack Development Mailing List (not for usage questions)" 
> 
> Date: 12/11/2015 06:39 AM
> Subject: [openstack-dev] [nova][serial-console-proxy]
> 
> Hi All,

> I have set up open stack on an Arm64 machine and all the open stack 
> related services are running fine. Also am able to launch an instance 
> successfully. Now that I need to get a console for my instance. The 
> noVNC console is not supported in the machine am using. So I have to 
> use a serial-proxy console or spice-proxy console. 

> After rejoining the stack, I have stopped the noVNC service and 
> started the serial proxy service in  /usr/local/bin  as
> 
> ubuntu@ubuntu:~/devstack$ /usr/local/bin/nova-serialproxy --config-
> file /etc/nova/nova.conf
> 2015-12-10 19:07:13.786 21979 INFO nova.console.websocketproxy [-] 
> WebSocket server settings:
> 2015-12-10 19:07:13.786 21979 INFO nova.console.websocketproxy [-]   
-Listen on 
> 0.0.0.0:6083
> 2015-12-10 19:07:13.787 21979 INFO nova.console.websocketproxy [-]   -
> Flash security policy server
> 2015-12-10 19:07:13.787 21979 INFO nova.console.websocketproxy [-]   -
> No SSL/TLS support (no cert file)
> 2015-12-10 19:07:13.790 21979 INFO nova.console.websocketproxy [-]   -
> proxying from 0.0.0.0:6083 to None:None

> But 
> ubuntu@ubuntu:~/devstack$ nova get-serial-console vm20
> ERROR (ClientException): The server has either erred or is incapable 
> of performing the requested operation. (HTTP 500) (Request-ID: req-
> cfe7d69d-3653-4d62-ad0b-50c68f1ebd5e)

> 
> the problem seems to be that the nova-compute is not able to 
> communicate with nova-serial-proxy. The IP and port for serial proxy 
> that I have given in nova.conf is correct.

> I really dont understand where am going wrong. Some help would be very
> grateful.  
> 

> My nova.conf - 
> 
> 
> [DEFAULT]
> vif_plugging_timeout = 300
> vif_plugging_is_fatal = True
> linuxnet_interface_driver =
> security_group_api = neutron
> network_api_class = nova.network.neutronv2.api.API
> firewall_driver = nova.virt.firewall.NoopFirewallDriver
> compute_driver = libvirt.LibvirtDriver
> default_ephemeral_format = ext4
> metadata_workers = 24
> ec2_workers = 24
> osapi_compute_workers = 24
> rpc_backend = rabbit
> keystone_ec2_url = http://10.167.103.101:5000/v2.0/ec2tokens
> ec2_dmz_host = 10.167.103.101
> vncserver_proxyclient_address = 127.0.0.1
> vncserver_listen = 127.0.0.1
> vnc_enabled = false
> xvpvncproxy_base_url = http://10.167.103.101:6081/console
> novncproxy_base_url = http://10.167.103.101:6080/vnc_auto.html
> logging_context_format_string = %(asctime)s.%(msecs)03d %(levelname)s 
> %(name)s [%(request_id)s %(user_name)s %(project_name)s] 
%(instance)s%(message)s
> force_config_drive = True
> instances_path = /opt/stack/data/nova/instances
> state_path = /opt/stack/data/nova
> enabled_apis = ec2,osapi_compute,metadata
> instance_name_template = instance-%08x
> my_ip = 10.167.103.101
> s3_port = 
> s3_host = 10.167.103.101
> default_floating_pool = public
> force_dhcp_release = True
> dhcpbridge_flagfile = /etc/nova/nova.conf
> scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler
> rootwrap_config = /etc/nova/rootwrap.conf
> api_paste_config = /etc/nova/api-paste.ini
> allow_migrate_to_same_host = True
> allow_resize_to_same_host = True
> debug = True
> verbose = True
> 
> [database]
> connection = mysql://root:open@127.0.0.1/nova?charset=utf8
> 
> [osapi_v3]
> enabled = True
> 
> [keystone_authtoken]
> signing_dir = /var/cache/nova
> cafile = /opt/stack/data/ca-bundle.pem
> auth_uri = http://10.167.103.101:5000
> project_domain_id = default
> project_name = service
> user_domain_id = default
> password = open
> username = nova
> auth_url = http://10.167.103.101:35357
> auth_plugin = password
> 
> [oslo_concurrency]
> lock_path = /opt/stack/data/nova
> 
> [spice]
> #agent_enabled = True
> enabled = false
> html5proxy_base_url = http://10.167.103.101:6082/spice_auto.html
> #server_listen = 127.0.0.1
> #server_proxyclient_address = 127.0.0.1
> 
> [oslo_messaging_rabbit]
> rabbit_userid = stackrabbit
> rabbit_password = open
> rabbit_hosts = 10.167.103.101
> 
> [glance]
> api_servers = http://10.167.103.101:9292
> 
> [cinder]
> os_region_name = RegionOne
> 
> [libvirt]
> vif_driver = nova.virt.libvirt.vif.LibvirtGenericVIFDriver
> inject_partition = -2
> live_migration_uri = qemu+ssh://ubuntu@%s/system
> use_usb_tablet = False
> cpu_mode = host-model
> virt_type = kvm
> 
> [neutron]
> service_metadata_proxy = True
&g

Re: [openstack-dev] [nova][serial-console-proxy]

2015-12-14 Thread Prathyusha Guduri

Hi Tony,

Your reply gave me a hint that nova-consoleauth service must be running. I
did not start that service before so no token authentication was done. Now
after starting the service,
$nova get-serial-console vm-check-6
++-+
| Type   | Url |
++-+
| serial | ws://127.0.0.1:6083/?token=c2fb4073-79a0-44b9-a977-cc7a1fa074f6 |

Following
http://docs.openstack.org/developer/nova/testing/serial-console.html

$ python client.py ws://
127.0.0.1:6083/?token=c2fb4073-79a0-44b9-a977-cc7a1fa074f6

..hangs

Log at consoleauth shows that the token authentication is done.

Received Token: c2fb4073-79a0-44b9-a977-cc7a1fa074f6, {'instance_uuid':
u'5a725707-440e-4cf1-b262-fdb6492ac4d7', 'access_url': u'ws://
127.0.0.1:6083/?token=c2fb4073-79a0-44b9-a977-cc7a1fa074f6', 'token':
u'c2fb4073-79a0-44b9-a977-cc7a1fa074f6', 'last_activity_at':
1450111951.325766, 'internal_access_path': None, 'console_type': u'serial',
'host': u'127.0.0.1', 'port': 10005}
2015-12-14 16:53:23.083 INFO nova.consoleauth.manager
[req-2996a251-7fea-4b72-8fd4-30c8505224a3 None None] Checking Token:
c2fb4073-79a0-44b9-a977-cc7a1fa074f6, True

Log at serial-proxy shows that it waits forever connecting to 127.0.0.1

127.0.0.1 - - [14/Dec/2015 16:53:22] "GET
/?token=c2fb4073-79a0-44b9-a977-cc7a1fa074f6 HTTP/1.1" 101 -
127.0.0.1 - - [14/Dec/2015 16:53:22] 127.0.0.1: Plain non-SSL (ws://)
WebSocket connection
127.0.0.1 - - [14/Dec/2015 16:53:22] 127.0.0.1: Version hybi-13, base64:
'False'
127.0.0.1 - - [14/Dec/2015 16:53:22] 127.0.0.1: Path:
'/?token=c2fb4073-79a0-44b9-a977-cc7a1fa074f6'
2015-12-14 16:53:23.011 INFO oslo_messaging._drivers.impl_rabbit
[req-2996a251-7fea-4b72-8fd4-30c8505224a3 None None] Connecting to AMQP
server on 10.167.103.101:5672
2015-12-14 16:53:23.040 INFO oslo_messaging._drivers.impl_rabbit
[req-2996a251-7fea-4b72-8fd4-30c8505224a3 None None] Connected to AMQP
server on 10.167.103.101:5672
2015-12-14 16:53:23.048 INFO oslo_messaging._drivers.impl_rabbit
[req-2996a251-7fea-4b72-8fd4-30c8505224a3 None None] Connecting to AMQP
server on 10.167.103.101:5672
2015-12-14 16:53:23.076 INFO oslo_messaging._drivers.impl_rabbit
[req-2996a251-7fea-4b72-8fd4-30c8505224a3 None None] Connected to AMQP
server on 10.167.103.101:5672
2015-12-14 16:53:23.220 INFO nova.console.websocketproxy
[req-2996a251-7fea-4b72-8fd4-30c8505224a3 None None]   2: connect info:
{u'instance_uuid': u'5a725707-440e-4cf1-b262-fdb6492ac4d7',
u'internal_access_path': None, u'last_activity_at': 1450111951.325766,
u'console_type': u'serial', u'host': u'127.0.0.1', u'token':
u'c2fb4073-79a0-44b9-a977-cc7a1fa074f6', u'access_url': u'ws://
127.0.0.1:6083/?token=c2fb4073-79a0-44b9-a977-cc7a1fa074f6', u'port': 10005}
2015-12-14 16:53:23.221 INFO nova.console.websocketproxy
[req-2996a251-7fea-4b72-8fd4-30c8505224a3 None None]   2: connecting to:
127.0.0.1:10005


In nova.conf I have only made enabled=true under [serial-proxy] section.
Other values are not specified so that letting the nova take default
values. I have read that with default values single node set up will not
have any issues.

I thought the issue might be because of websocket, so I was not able to
install websocket module of python in my system.

system-specifications :

uname -m = aarch64
uname -r = 4.2.0-03373-gdded870-dirty
uname -s = Linux
uname -v = #4 SMP Tue Dec 8 14:47:17 IST 2015

Error while installing :
libev/ev.c:45:22: fatal error: config.h: No such file or directory
 #  include "config.h"
  ^
compilation terminated.
error: command 'aarch64-linux-gnu-gcc' failed with exit status 1


Please help me how to proceed further.

Thanks,
Prathyusha







On Mon, Dec 14, 2015 at 12:41 PM, Prathyusha Guduri <
prathyushaconne...@gmail.com> wrote:

> Hi Tony,
>
>
> Thanks a lot for your response.
> I actually did a rejoin-stack.sh which will also restart n-api and all
> other services. But still the same issue.
>
> Anyway now that I've to run all over again, will change my local.conf
> according to the guide and run stack.
>
> Will keep you updated.
>
> Thanks,
> Prathyusha
>
>
>
> On Mon, Dec 14, 2015 at 4:09 AM, Tony Breeds 
> wrote:
>
>> On Fri, Dec 11, 2015 at 11:07:02AM +0530, Prathyusha Guduri wrote:
>> > Hi All,
>> >
>> > I have set up open stack on an Arm64 machine and all the open stack
>> related
>> > services are running fine. Also am able to launch an instance
>> successfully.
>> > Now that I need to get a console for my instance. The noVNC console is
>> not
>> > supported in the machine am using. So I have to use a serial-proxy
>> console
>> > or spice-proxy console.
>> >
>> > After rejoining the stack, I have stopped the noVNC service and started
>> the
>> > serial proxy service in  /usr/local/bin  as
>> >
>> > ubuntu@ubuntu:~/devstac

Re: [openstack-dev] [nova][serial-console-proxy]

2015-12-13 Thread Prathyusha Guduri

Hi Tony,


Thanks a lot for your response.
I actually did a rejoin-stack.sh which will also restart n-api and all
other services. But still the same issue.

Anyway now that I've to run all over again, will change my local.conf
according to the guide and run stack.

Will keep you updated.

Thanks,
Prathyusha



On Mon, Dec 14, 2015 at 4:09 AM, Tony Breeds 
wrote:

> On Fri, Dec 11, 2015 at 11:07:02AM +0530, Prathyusha Guduri wrote:
> > Hi All,
> >
> > I have set up open stack on an Arm64 machine and all the open stack
> related
> > services are running fine. Also am able to launch an instance
> successfully.
> > Now that I need to get a console for my instance. The noVNC console is
> not
> > supported in the machine am using. So I have to use a serial-proxy
> console
> > or spice-proxy console.
> >
> > After rejoining the stack, I have stopped the noVNC service and started
> the
> > serial proxy service in  /usr/local/bin  as
> >
> > ubuntu@ubuntu:~/devstack$ /usr/local/bin/nova-serialproxy --config-file
> > /etc/nova/nova.conf
> > 2015-12-10 19:07:13.786 21979 INFO nova.console.websocketproxy [-]
> > WebSocket server settings:
> > 2015-12-10 19:07:13.786 21979 INFO nova.console.websocketproxy [-]   -
> > Listen on 0.0.0.0:6083
> > 2015-12-10 19:07:13.787 21979 INFO nova.console.websocketproxy [-]   -
> > Flash security policy server
> > 2015-12-10 19:07:13.787 21979 INFO nova.console.websocketproxy [-]   - No
> > SSL/TLS support (no cert file)
> > 2015-12-10 19:07:13.790 21979 INFO nova.console.websocketproxy [-]   -
> > proxying from 0.0.0.0:6083 to None:None
> >
> > But
> > ubuntu@ubuntu:~/devstack$ nova get-serial-console vm20
> > ERROR (ClientException): The server has either erred or is incapable of
> > performing the requested operation. (HTTP 500) (Request-ID:
> > req-cfe7d69d-3653-4d62-ad0b-50c68f1ebd5e)
>
> So you probably need to restart you nova-api, cauth and compute servcies.
>
> As you're using devstack I'd recommend you start again and follow the
> following
> guides:
>  1.
> http://docs.openstack.org/developer/devstack/guides/nova.html#nova-serialproxy
>  2. http://docs.openstack.org/developer/nova/testing/serial-console.html
>
> Also your nova.conf looked strange I hope that's just manually formatting.
>
> Tony.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][serial-console-proxy]

2015-12-13 Thread Tony Breeds

On Fri, Dec 11, 2015 at 11:07:02AM +0530, Prathyusha Guduri wrote:
> Hi All,
> 
> I have set up open stack on an Arm64 machine and all the open stack related
> services are running fine. Also am able to launch an instance successfully.
> Now that I need to get a console for my instance. The noVNC console is not
> supported in the machine am using. So I have to use a serial-proxy console
> or spice-proxy console.
> 
> After rejoining the stack, I have stopped the noVNC service and started the
> serial proxy service in  /usr/local/bin  as
> 
> ubuntu@ubuntu:~/devstack$ /usr/local/bin/nova-serialproxy --config-file
> /etc/nova/nova.conf
> 2015-12-10 19:07:13.786 21979 INFO nova.console.websocketproxy [-]
> WebSocket server settings:
> 2015-12-10 19:07:13.786 21979 INFO nova.console.websocketproxy [-]   -
> Listen on 0.0.0.0:6083
> 2015-12-10 19:07:13.787 21979 INFO nova.console.websocketproxy [-]   -
> Flash security policy server
> 2015-12-10 19:07:13.787 21979 INFO nova.console.websocketproxy [-]   - No
> SSL/TLS support (no cert file)
> 2015-12-10 19:07:13.790 21979 INFO nova.console.websocketproxy [-]   -
> proxying from 0.0.0.0:6083 to None:None
> 
> But
> ubuntu@ubuntu:~/devstack$ nova get-serial-console vm20
> ERROR (ClientException): The server has either erred or is incapable of
> performing the requested operation. (HTTP 500) (Request-ID:
> req-cfe7d69d-3653-4d62-ad0b-50c68f1ebd5e)

So you probably need to restart you nova-api, cauth and compute servcies.

As you're using devstack I'd recommend you start again and follow the following
guides:
 1. 
http://docs.openstack.org/developer/devstack/guides/nova.html#nova-serialproxy
 2. http://docs.openstack.org/developer/nova/testing/serial-console.html

Also your nova.conf looked strange I hope that's just manually formatting.

Tony.


pgp5mGZBgVbi2.pgp
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova][serial-console-proxy]

2015-12-10 Thread Prathyusha Guduri

Hi All,

I have set up open stack on an Arm64 machine and all the open stack related
services are running fine. Also am able to launch an instance successfully.
Now that I need to get a console for my instance. The noVNC console is not
supported in the machine am using. So I have to use a serial-proxy console
or spice-proxy console.

After rejoining the stack, I have stopped the noVNC service and started the
serial proxy service in  /usr/local/bin  as

ubuntu@ubuntu:~/devstack$ /usr/local/bin/nova-serialproxy --config-file
/etc/nova/nova.conf
2015-12-10 19:07:13.786 21979 INFO nova.console.websocketproxy [-]
WebSocket server settings:
2015-12-10 19:07:13.786 21979 INFO nova.console.websocketproxy [-]   -
Listen on 0.0.0.0:6083
2015-12-10 19:07:13.787 21979 INFO nova.console.websocketproxy [-]   -
Flash security policy server
2015-12-10 19:07:13.787 21979 INFO nova.console.websocketproxy [-]   - No
SSL/TLS support (no cert file)
2015-12-10 19:07:13.790 21979 INFO nova.console.websocketproxy [-]   -
proxying from 0.0.0.0:6083 to None:None

But
ubuntu@ubuntu:~/devstack$ nova get-serial-console vm20
ERROR (ClientException): The server has either erred or is incapable of
performing the requested operation. (HTTP 500) (Request-ID:
req-cfe7d69d-3653-4d62-ad0b-50c68f1ebd5e)


the problem seems to be that the nova-compute is not able to communicate
with nova-serial-proxy. The IP and port for serial proxy that I have given
in nova.conf is correct.

I really dont understand where am going wrong. Some help would be very
grateful.


My nova.conf -


[DEFAULT]
vif_plugging_timeout = 300
vif_plugging_is_fatal = True
linuxnet_interface_driver =
security_group_api = neutron
network_api_class = nova.network.neutronv2.api.API
firewall_driver = nova.virt.firewall.NoopFirewallDriver
compute_driver = libvirt.LibvirtDriver
default_ephemeral_format = ext4
metadata_workers = 24
ec2_workers = 24
osapi_compute_workers = 24
rpc_backend = rabbit
keystone_ec2_url = http://10.167.103.101:5000/v2.0/ec2tokens
ec2_dmz_host = 10.167.103.101
vncserver_proxyclient_address = 127.0.0.1
vncserver_listen = 127.0.0.1


*vnc_enabled = falsexvpvncproxy_base_url =
http://10.167.103.101:6081/console
novncproxy_base_url =
http://10.167.103.101:6080/vnc_auto.html
*
logging_context_format_string = %(asctime)s.%(msecs)03d %(levelname)s
%(name)s [%(request_id)s %(user_name)s %(project_name)s]
%(instance)s%(message)s
force_config_drive = True
instances_path = /opt/stack/data/nova/instances
state_path = /opt/stack/data/nova
enabled_apis = ec2,osapi_compute,metadata
instance_name_template = instance-%08x
my_ip = 10.167.103.101
s3_port = 
s3_host = 10.167.103.101
default_floating_pool = public
force_dhcp_release = True
dhcpbridge_flagfile = /etc/nova/nova.conf
scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler
rootwrap_config = /etc/nova/rootwrap.conf
api_paste_config = /etc/nova/api-paste.ini
allow_migrate_to_same_host = True
allow_resize_to_same_host = True
debug = True
verbose = True

[database]
connection = mysql://root:open@127.0.0.1/nova?charset=utf8

[osapi_v3]
enabled = True

[keystone_authtoken]
signing_dir = /var/cache/nova
cafile = /opt/stack/data/ca-bundle.pem
auth_uri = http://10.167.103.101:5000
project_domain_id = default
project_name = service
user_domain_id = default
password = open
username = nova
auth_url = http://10.167.103.101:35357
auth_plugin = password

[oslo_concurrency]
lock_path = /opt/stack/data/nova






*[spice]#agent_enabled = Trueenabled = falsehtml5proxy_base_url =
http://10.167.103.101:6082/spice_auto.html
#server_listen =
127.0.0.1#server_proxyclient_address = 127.0.0.1*

[oslo_messaging_rabbit]
rabbit_userid = stackrabbit
rabbit_password = open
rabbit_hosts = 10.167.103.101

[glance]
api_servers = http://10.167.103.101:9292

[cinder]
os_region_name = RegionOne

[libvirt]
vif_driver = nova.virt.libvirt.vif.LibvirtGenericVIFDriver
inject_partition = -2
live_migration_uri = qemu+ssh://ubuntu@%s/system
use_usb_tablet = False
cpu_mode = host-model
virt_type = kvm

[neutron]
service_metadata_proxy = True
url = http://10.167.103.101:9696
region_name = RegionOne
admin_tenant_name = service
auth_strategy = keystone
admin_auth_url = http://10.167.103.101:35357/v2.0
admin_password = open
admin_username = neutron

[keymgr]
fixed_key = c5861a510cda58d367a44fc0aee6405e8e03a70f58c03fdc263af8405cf9a0c6













*[serial_console]enabled = true# Location of serial console proxy. (string
value)base_url = ws://127.0.0.1:6083/ # IP address
on which instance serial console should listen# (string value)listen =
127.0.0.1# The address to which proxy clients (like nova-serialproxy)#
should connect (string value)proxyclient_address = 127.0.0.1*


Thanks,
Prathyusha
__
OpenStack Development Mailing List (not for

Re: [openstack-dev] [nova][serial-console-proxy]

Re: [openstack-dev] [nova][serial-console-proxy]

Re: [openstack-dev] [nova][serial-console-proxy]

Re: [openstack-dev] [nova][serial-console-proxy]

Re: [openstack-dev] [nova][serial-console-proxy]

[openstack-dev] [nova][serial-console-proxy]

6 matches

Site Navigation

Mail list logo

Footer information