There is no need to tweak configuration to get "nova hypervisor-list" output. As I just replied in another thread, it works by default. Please try it on Vbox to confirm.
According to your email, you have issues with networking. Did you check your networking connectivity, especially over management network? Thanks, On Thu, Jun 19, 2014 at 11:03 AM, Gandhirajan Mariappan (CW) < [email protected]> wrote: > Hi Sergii/Miroslav, > > > > I have shared the “Diagnostic Snapshot” at > https://www.dropbox.com/s/79op6pi1vxe9w9l/fuel-snapshot-2014-06-19_04-40-10.tgz > > > > *Topology:* > > Our topology is like below – > > [image: cid:[email protected]] > > *Query:* nova hypervisor-list is empty in compute node > > > > *Steps we tried for ‘neutron agent-list’:* > > Neutron agent-list was also not listing host-node5 (highlighted below) by > default. After we changed the IP address from 192.26.0.3(management > network) to 10.24.41.3(public network) in Compute node -> neutron.conf file > and restarting neutron service, node-5 agent got listed successfully. > > > > *Line modified from 192.26.0.3 to 10.24.41.3 in Compute Node-Neutron.conf > file:* > > connection = mysql:// > neutron:[email protected]:3306/neutron?read_timeout=60 > > > > *Compute Node – neutron agent-list:* > > *root@node-6:/etc/neutron# neutron agent-list* > > > *+--------------------------------------+--------------------+--------+-------+----------------+* > > *| id | agent_type | host | > alive | admin_state_up |* > > > *+--------------------------------------+--------------------+--------+-------+----------------+* > > *| 3078a077-101e-49a4-861f-6e79ced41fc6 | Metadata agent | node-6 | > :-) | True |* > > *| 8d00c407-648f-46a2-9a17-ee575c4daf7b | DHCP agent | node-6 | > :-) | True |* > > *| b28cfc33-a8ba-4c4c-b1f0-dbb65b6b1e2c | L3 agent | node-6 | > :-) | True |* > > *| e44d7841-3ab8-46e2-b46e-e1bcf39785e9 | Open vSwitch agent | node-5 | > :-) | True |* > > *| eb79f92e-6fd2-4d11-9e2c-024f55353e81 | Open vSwitch agent | node-6 | > :-) | True |* > > > *+--------------------------------------+--------------------+--------+-------+----------------+* > > > > *Steps we tried to display compute node in ‘nova hypervisor-list’:* > > We have replaced all the references of 192.168.0.3 to 10.24.41.3 in > Compute node -> /etc/nova/nova.conf file. > > Also modified Compute node -> /etc/nova/nova-compute.conf with the below > lines - > > > > *[DEFAULT]* > > *compute_driver=libvirt.LibvirtDriver* > > *#sql_connection=mysql://nova:[email protected]/nova?charset=utf8 > <http://nova:[email protected]/nova?charset=utf8>* > > *#sql_connection=mysql://nova:[email protected]/nova?read_timeout=60 > <http://nova:[email protected]/nova?read_timeout=60>* > > *sql_connection=mysql://nova:[email protected]/nova?read_timeout=60 > <http://nova:[email protected]/nova?read_timeout=60>* > > *#neutron_url=http://10.24.41.3:9696 <http://10.24.41.3:9696>* > > *neutron_url=http://10.24.41.3:9696 <http://10.24.41.3:9696>* > > *neutron_admin_username=neutron* > > *#neutron_admin_password=password* > > *neutron_admin_password=TdvGnCTq* > > *neutron_admin_tenant_name=services* > > *neutron_region_name=RegionOne* > > *#neutron_admin_auth_url=http://10.24.41.3:35357/v2.0 > <http://10.24.41.3:35357/v2.0>* > > *neutron_admin_auth_url=http://10.24.41.3:35357/v2.0 > <http://10.24.41.3:35357/v2.0>* > > *neutron_auth_strategy=keystone* > > *security_group_api=neutron* > > *debug=True* > > *verbose=True* > > *connection_type=libvirt* > > *network_api_class=nova.network.neutronv2.api.API* > > *libvirt_use_virtio_for_bridges=True* > > *neutron_default_tenant_id=default* > > *rabbit_userid=nova* > > *rabbit_password=WENFYGnk* > > > > *[libvirt]* > > *virt_type=kvm* > > *compute_driver=libvirt.LibvirtDriver* > > *libvirt_ovs_bridge=br-int* > > *libvirt_vif_type=ethernet* > > *libvirt_vif_driver=nova.virt.libvirt.vif.NeutronLinuxBridgeVIFDriver* > > > > Thanks and Regards, > > Gandhi Rajan > > > > *From:* Sergii Golovatiuk [mailto:[email protected]] > *Sent:* Wednesday, June 18, 2014 8:18 PM > *To:* Gandhirajan Mariappan (CW) > *Cc:* [email protected]; Miroslav Anashkin; > DL-GRP-ENG-SQA-Open Stack; Prakash Kaligotla > *Subject:* Re: [Fuel-dev] Controller node ip is not pinging from Compute > node > > > > Hi Gandhirajan, > > From your email it's not clear a topology your have. I am kindly asking to > create "Diagnostic snapshot" so we'll be able to analyze it. The link below > will help you with the process > > https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Test_and_report_bugs > > Thank you. > > -- > Mailing list: https://launchpad.net/~fuel-dev > Post to : [email protected] > Unsubscribe : https://launchpad.net/~fuel-dev > More help : https://help.launchpad.net/ListHelp > > -- Mike Scherbakov #mihgen
-- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
