openstack team mailing list archive

[Srikanth Kumar Lingala <srikanthkumar.lingala@xxxxxxxxx>]

@janis: How can I check that metadata service is working?

@Salvatore:
DHCP Agent is working fine and I am not seeing any ERROR logs.
I am able to see dnsmasq services. I am able to see those MAC entries in
the hosts file.
tap interface is creating on Host Node, which is attached to br-int.

Regards,
Srikanth.

On Wed, Oct 24, 2012 at 7:24 PM, Salvatore Orlando <sorlando@xxxxxxxxxx>wrote:

> Srikanth,
>
> from your analysis it seems that L2 connectivity between the compute and
> the controller node is working as expected.
> Before looking further, it is maybe worth ruling out the obvious problems.
> Hence:
> 1) is the dhcp-agent service running (or is it stuck in some error state?)
> 2) Can you see dnsmasq instances running on the controller node? If yes,
> do you see your VM's MAC in the hosts file for the dnsmasq instance?
> 3) If dnsmasq instances are running, can you confirm the relevant tap
> ports are inserted on Open vSwitch instance br-int?
>
> Salvatore
>
>
> On 24 October 2012 14:14, Jānis Ģeņģeris <janis.gengeris@xxxxxxxxx> wrote:
>
>> Hi Srikanth,
>>
>> Can you confirm that metadata service is working and the VMs are able to
>> access it? Usually if VM's can't get network settings is because of
>> inaccessible metadata service.
>>
>> --janis
>>
>> On Wed, Oct 24, 2012 at 4:00 PM, Srikanth Kumar Lingala <
>> srikanthkumar.lingala@xxxxxxxxx> wrote:
>>
>>> Here is the *nova.conf* file contents:
>>>
>>> *[DEFAULT]*
>>> *# MySQL Connection #*
>>> *sql_connection=mysql://nova:password@10.232.91.33/nova*
>>> *
>>> *
>>> *# nova-scheduler #*
>>> *rabbit_host=10.232.91.33*
>>> *rabbit_userid=guest*
>>> *rabbit_password=password*
>>> *#scheduler_driver=nova.scheduler.simple.SimpleScheduler*
>>> *#scheduler_default_filters=ImagePropertiesFilter*
>>> *
>>> *
>>> *
>>> *
>>> *scheduler_driver=nova.scheduler.multi.MultiScheduler*
>>> *
>>> compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
>>> *
>>> *scheduler_available_filters=nova.scheduler.filters.standard_filters*
>>> *scheduler_default_filters=ImagePropertiesFilter*
>>> *
>>> *
>>> *
>>> *
>>> *# nova-api #*
>>> *cc_host=10.232.91.33*
>>> *auth_strategy=keystone*
>>> *s3_host=10.232.91.33*
>>> *ec2_host=10.232.91.33*
>>> *nova_url=http://10.232.91.33:8774/v1.1/*
>>> *ec2_url=http://10.232.91.33:8773/services/Cloud*
>>> *keystone_ec2_url=http://10.232.91.33:5000/v2.0/ec2tokens*
>>> *api_paste_config=/etc/nova/api-paste.ini*
>>> *allow_admin_api=true*
>>> *use_deprecated_auth=false*
>>> *ec2_private_dns_show_ip=True*
>>> *dmz_cidr=169.254.169.254/32*
>>> *ec2_dmz_host=169.254.169.254*
>>> *metadata_host=169.254.169.254*
>>> *enabled_apis=ec2,osapi_compute,metadata*
>>> *
>>> *
>>> *
>>> *
>>> *# Networking #*
>>> *network_api_class=nova.network.quantumv2.api.API*
>>> *quantum_url=http://10.232.91.33:9696*
>>> *libvirt_vif_type=ethernet*
>>> *linuxnet_vif_driver=nova.network.linux_net.LinuxOVSInterfaceDriver*
>>> *firewall_driver=nova.virt.firewall.NoopFirewallDriver*
>>> *libvirt_use_virtio_for_bridges=True*
>>> *
>>> *
>>> *# Cinder #*
>>> *#volume_api_class=cinder.volume.api.API*
>>> *
>>> *
>>> *# Glance #*
>>> *glance_api_servers=10.232.91.33:9292*
>>> *image_service=nova.image.glance.GlanceImageService*
>>> *
>>> *
>>> *# novnc #*
>>> *novnc_enable=true*
>>> *novncproxy_base_url=http://10.232.91.33:6080/vnc_auto.html*
>>> *vncserver_proxyclient_address=127.0.0.1*
>>> *vncserver_listen=0.0.0.0*
>>> *
>>> *
>>> *# Misc #*
>>> *logdir=/var/log/nova*
>>> *state_path=/var/lib/nova*
>>> *lock_path=/var/lock/nova*
>>> *root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf*
>>> *verbose=true*
>>> *dhcpbridge_flagfile=/etc/nova/nova.conf*
>>> *dhcpbridge=/usr/bin/nova-dhcpbridge*
>>> *force_dhcp_release=True*
>>> *iscsi_helper=tgtadm*
>>> *connection_type=libvirt*
>>> *libvirt_type=kvm*
>>> *libvirt_ovs_bridge=br-int*
>>> *libvirt_vif_type=ethernet*
>>> *libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchDriver*
>>>
>>>
>>> Regards,
>>> Srikanth.
>>>
>>>
>>> On Mon, Oct 22, 2012 at 7:48 AM, gong yong sheng <
>>> gongysh@xxxxxxxxxxxxxxxxxx> wrote:
>>>
>>>>  can u send out nova.conf file?
>>>>
>>>> On 10/22/2012 07:30 PM, Srikanth Kumar Lingala wrote:
>>>>
>>>> Hi,
>>>> I am using latest devstack I am trying to create a VM with one Ethernet
>>>> interface card. I am able to create the VM successfully, but not able to
>>>> get IP for the ethernet interface.
>>>> I have Openstack Controller running the following:
>>>>
>>>>    - nova-api
>>>>    - nova-cert
>>>>    - nova-consoleauth
>>>>    - nova-scheduler
>>>>    - quantum-dhcp-agent
>>>>    - quantum-openvswitch-agent
>>>>
>>>>
>>>>  And O also have Openstack Host Node running the following:
>>>>
>>>>    - nova-api
>>>>    - nova-compute
>>>>    - quantum-openvswitch-agent
>>>>
>>>>
>>>>  I am not seeing any kind of errors in logs related nova as well as
>>>> quantum.
>>>> I observed that when I execute 'dhclient' in VM, 'br-int' interface in
>>>> 'Openstack Controller' getting DHCP requests, but not sending reply.
>>>> Please let me know, what I am doing wrong here.
>>>> Thanks in advance.
>>>>
>>>>  --
>>>> ----
>>>> Srikanth.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> ----
>>> Srikanth.
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>