CBR's profile - activity

2020-04-28 16:06:38 -0600 received badge  Notable Question (source)
2020-04-28 16:06:38 -0600 received badge  Famous Question (source)
2016-10-27 19:43:50 -0600 received badge  Famous Question (source)
2016-10-27 19:43:50 -0600 received badge  Notable Question (source)
2016-10-27 19:43:50 -0600 received badge  Popular Question (source)
2015-10-14 18:26:14 -0600 received badge  Famous Question (source)
2015-10-09 01:24:40 -0600 received badge  Popular Question (source)
2015-07-24 00:06:55 -0600 received badge  Notable Question (source)
2015-07-21 01:52:28 -0600 received badge  Notable Question (source)
2015-07-19 16:21:10 -0600 received badge  Popular Question (source)
2015-07-19 05:29:00 -0600 received badge  Student (source)
2015-07-18 12:07:10 -0600 asked a question Compute-node communicate/ping vms run on it

Hi all.

In Ceilometer, when pollsters collect meter from VMs, it used hypervisor on compute-node. Now, I want to write new plugin for ceilometer and not use hypervisor to collect meter, I want to collect meter by a service that is installed on VMs (mean ceilometer get data from service), so I need compute-node must communicate with VMs by IP (private IP). Is there any solution to do this?

Thanks all.

2015-07-01 00:06:08 -0600 received badge  Popular Question (source)
2015-06-22 03:08:49 -0600 received badge  Editor (source)
2015-06-22 03:05:21 -0600 asked a question [Docker] Cannot create docker container

I have problem about setup nova-docker (docker hypervisor) on multi-node OpenStack (version Juno), my OS is Ubuntu 14.04 I followed: https://wiki.openstack.org/wiki/Docker, when I create a container vm by dashboard or nova boot, I received error in nova-compute.log

2015-06-22 14:41:40.059 2550 ERROR nova.compute.manager [-] [instance: 62d7a3d3-7008-44d7-b17f-129b4c10c105] Instance failed to spawn
2015-06-22 14:41:40.059 2550 TRACE nova.compute.manager [instance: 62d7a3d3-7008-44d7-b17f-129b4c10c105] Traceback (most recent call last):
2015-06-22 14:41:40.059 2550 TRACE nova.compute.manager [instance: 62d7a3d3-7008-44d7-b17f-129b4c10c105]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2267, in _build_resources
2015-06-22 14:41:40.059 2550 TRACE nova.compute.manager [instance: 62d7a3d3-7008-44d7-b17f-129b4c10c105]     yield resources
2015-06-22 14:41:40.059 2550 TRACE nova.compute.manager [instance: 62d7a3d3-7008-44d7-b17f-129b4c10c105]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2137, in _build_and_run_instance
2015-06-22 14:41:40.059 2550 TRACE nova.compute.manager [instance: 62d7a3d3-7008-44d7-b17f-129b4c10c105]     block_device_info=block_device_info)
2015-06-22 14:41:40.059 2550 TRACE nova.compute.manager [instance: 62d7a3d3-7008-44d7-b17f-129b4c10c105]   File "/usr/local/lib/python2.7/dist-packages/novadocker/virt/docker/driver.py", line 301, in spawn
2015-06-22 14:41:40.059 2550 TRACE nova.compute.manager [instance: 62d7a3d3-7008-44d7-b17f-129b4c10c105]     instance_id=instance['name'])
2015-06-22 14:41:40.059 2550 TRACE nova.compute.manager [instance: 62d7a3d3-7008-44d7-b17f-129b4c10c105] InstanceDeployFailure: Cannot create container
2015-06-22 14:41:40.059 2550 TRACE nova.compute.manager [instance: 62d7a3d3-7008-44d7-b17f-129b4c10c105]

*UPDATE* Error in docker debug: docker -d -D

INFO[0000] Docker daemon                                 commit=0baf609 execdriver=native-0.2 graphdriver=aufs version=1.7.0







DEBU[0018] Calling GET /images/{name:.*}/json           
INFO[0018] GET /v1.13/images/tutum/mysql/json           
DEBU[0018] Calling POST /containers/create              
INFO[0018] POST /v1.13/containers/create?name=nova-0e24a2ef-57f3-421e-b357-6cbc71dbe15b 
ERRO[0018] Handler for POST /containers/create returned error: json: cannot unmarshal string into Go value of type []string 
ERRO[0018] HTTP Error                                    err=json: cannot unmarshal string into Go value of type []string statusCode=500
DEBU[0018] Calling GET /containers/ps                   
INFO[0018] GET /v1.13/containers/ps?all=1               
DEBU[0018] Calling GET /containers/{name:.*}/json       
INFO[0018] GET /v1.13/containers/86bbca94cb7cf4a8dc81c4eaba55a46ca92c9e6bb8b79b63dfdb1466bee15233/json 
DEBU[0018] Calling GET /containers/ps                   
INFO[0018] GET /v1.13/containers/ps?all=1               
DEBU[0018] Calling GET /containers/{name:.*}/json       
INFO[0018] GET /v1.13/containers/86bbca94cb7cf4a8dc81c4eaba55a46ca92c9e6bb8b79b63dfdb1466bee15233/json
  • My configuration:

/etc/nova/nova.conf

  [DEFAULT]
    compute_driver = novadocker.virt.docker.DockerDriver
    network_api_class = nova.network.neutronv2.api.API
    security_group_api = neutron
    linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
    firewall_driver = nova.virt.firewall.NoopFirewallDriver
    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
    force_dhcp_release=True
    libvirt_use_virtio_for_bridges=True
    verbose=True
    ec2_private_dns_show_ip=True
    api_paste_config=/etc/nova/api-paste.ini
    enabled_apis=ec2,osapi_compute,metadata

    rpc_backend = rabbit
    rabbit_host = controller
    rabbit_password = openstack 


    rbd_user=volumes
    rbd_secret_uuid=f514c965-78b3-46ed-b986-838b3cb91655


    instance_usage_audit = True
    instance_usage_audit_period = hour
    notify_on_state_change = vm_and_task_state
    notification_driver = messagingv2

    my_ip = 10.0.0.33
    vnc_enabled = True
    vncserver_listen = 0.0.0.0
    vncserver_proxyclient_address = 10.0.0.33
    novncproxy_base_url = http://controller:6080/vnc_auto.html
    auth_strategy = keystone
    [keystone_authtoken]
    auth_uri = http://controller:5000/v2.0
    identity_uri = http://controller:35357 ...
(more)
2015-06-11 02:05:37 -0600 received badge  Enthusiast
2015-06-08 23:15:10 -0600 answered a question [Openstack] Problem about suspend/resume vm

Please help me!, I'm confusing :'(

2015-06-07 23:30:23 -0600 asked a question [OpenStack] Problem about suspend/resume vm

Hi all. I'm having a problem about suspend/resume instance. Theoretically, as I suspend a vm, it will save the vm's state at that time, and upon resumption, vm is exactly as it was before entering suspending. However, in OpenStack (Juno verrsion), when I resume, it does not return to previous state, which looks like the vm boot from start and requires login username/password. So it make me confused and I don't know why!.

Thanks all!

2015-06-07 23:28:45 -0600 asked a question [Openstack] Problem about suspend/resume vm

Hi all.

I'm having a problem about suspend/resume instance. Theoretically, as I suspend a vm, it will save the vm's state at that time, and upon resumption, vm is exactly as it was before entering suspending. However, in OpenStack (Juno verrsion), when I resume, it does not return to previous state, which looks like the vm boot from start and requires login username/password. So it make me confused and I don't know why!.

I'm using OpenStack (Juno version), hypervisor is KVM/QEMU.

Thanks all!