[Openstack] Cannot reboot instance: Unable to add bridge
Hi, i've got strange situation, in my case here, 3 nodes are get power cut from source when i turn it on, instance can't boot, and have this as the nova-compute.log * Cannot reboot instance: Unable to add bridge qbrbe24b178-79 port tapbe24b178-79: Invalid argument* i have restart quantum-server and it's component, also with openvswith . hoping some clue thanks ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Host NIC configuration example needed Pretty PLEASE!
Hi, here's my controller node NIC setting (running quantum server) /auto eth1// //iface eth1 inet static// //address 192.168.7.85// //netmask 255.255.255.0// //network 192.168.7.0// //broadcast 192.168.7.255// //gateway 192.168.7.1// //# dns-* options are implemented by the resolvconf package, if installed// //dns-nameservers 192.168.7.106// // //auto eth0// //iface eth0 inet static// //address 10.10.10.10// //netmask 255.255.255.0// //gateway 10.10.10.1// //dns-nameservers 192.168.7.106// /and this for network node (running quantum l3, dhcp, openvswitch) /auto eth1// //iface eth1 inet manual// //#iface eth1 inet static// //up ifconfig $IFACE 0.0.0.0 up// //down ifconfig $IFACE down// //# address 192.168.7.86// //# netmask 255.255.255.0// //# network 192.168.7.0// //# broadcast 192.168.7.255// //# gateway 192.168.7.1// //# # dns-* options are implemented by the resolvconf package, if installed// //# dns-nameservers 192.168.7.106// // //auto eth0// //iface eth0 inet static// //address 10.10.10.20// //netmask 255.255.255.0// // //auto eth2// //iface eth2 inet static// //address 10.10.20.10// //netmask 255.255.255.0// // //auto br-ex// //iface br-ex inet static// //address 192.168.7.86// //netmask 255.255.255.0// //gateway 192.168.7.1// //dns-nameservers 192.168.7.106// /On controller node (running quantum server) my nova.conf on network(quantum) part /network_api_class = nova.network.quantumv2.api.API// //quantum_url = http://10.10.10.10:9696// //quantum_auth_strategy = keystone// //quantum_admin_tenant_name = service// //quantum_admin_username = quantum// //quantum_admin_password = password// //quantum_admin_auth_url = http://10.10.10.10:35357/v2.0// //libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver// //linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver// //firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver/ Hope that helps --- Mahardhika Gilang // On 7/26/2013 12:41 PM, Jake G. wrote: Hi everyone, Really screaming right now trying to get Quantum networking configured correctly. Wondering if someone can share there host NIC configuration with me? Basically, I have two NICs but not sure how they should be configured. Any IPs are ok. Do I need to create a bridge? Should I assign an IP to both NICs. Do I need to add/change anything to the nova.conf file? Mostly stuff that is missing from the documentation. Please please please! Thank you Jake ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Volume Success Create But No Volume in its Path
Oh i see, no i run manual configuration following this guide https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst now my problem is, on compute node log (when i attached volume to instance) it said that : *iscsiadm: No session found*, i used iscsitarget on controller (run cinder volume). On 7/16/2013 1:01 PM, John Griffith wrote: On Mon, Jul 15, 2013 at 10:01 PM, Mahardhika mahardika.gil...@andalabs.com mailto:mahardika.gil...@andalabs.com wrote: Hi all, i have investigate this issue, since i am successful in create volume with cinder, but volume is not create on it's own volumes_dir that's in /var/lib/cinder/volumes and in cinder-volumes.log it said success when creating no error or warn appear. lvm (with /dev/loop) is show that lvm is used for volume . please help thanks -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com mailto:mahardika.gil...@andalabs.com ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp Hi Mahardhika, The cinder volumes directory is actually used just for specifying the location of the iscsi target persistence files. Your volume is actually an LVM/Volume that you should see by running sudo lvs. As far as the persistence file, are you runing devstack? If so it will be in /opt/stack/data/cinder/volumes... If not perhaps you could provide your cinder.conf file and we could get a better idea of what you're setup is and where things might be. Thanks, John ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] libvirtError: unsupported configuration: disk bus 'ide' cannot be hotplugged.
Hi, i've got this when try to attach on running instance that running centos 6.3 *libvirtError: unsupported configuration: disk bus 'ide' cannot be hotplugged.* volume can attach when instance is on suspend state, but when i resume and reboot, no volume device is appear it work when i used cirros, but not with other os (bare-metal) or .iso image please help thanks ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] libvirtError: unsupported configuration: disk bus 'ide' cannot be hotplugged.
Hi, i used KVM. On 7/16/2013 4:16 PM, Wangpan wrote: what hypervisor you are using? 2013-07-16 Wangpan *发件人：*Mahardhika mahardika.gil...@andalabs.com *发送时间：*2013-07-16 17:09 *主题：*[Openstack] libvirtError: unsupported configuration: disk bus 'ide' cannot be hotplugged. *收件人：*openstack@lists.launchpad.netopenstack@lists.launchpad.net *抄送：* Hi, i've got this when try to attach on running instance that running centos 6.3 *libvirtError: unsupported configuration: disk bus 'ide' cannot be hotplugged.* volume can attach when instance is on suspend state, but when i resume and reboot, no volume device is appear it work when i used cirros, but not with other os (bare-metal) or .iso image please help thanks -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Volume Success Create But No Volume in its Path
Hi all, i have investigate this issue, since i am successful in create volume with cinder, but volume is not create on it's own volumes_dir that's in /var/lib/cinder/volumes and in cinder-volumes.log it said success when creating no error or warn appear. lvm (with /dev/loop) is show that lvm is used for volume . please help thanks -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Path Cinder Volume
Hello, in my configuration at cinder.conf volumes_dir is on***/var/lib/cinder/volumes*. but when i create new volume it isn't there, on cinder-volume.log not said much, it's just successful kindly help thanks ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Exception during message handling on Cinder
Hi, i have check that . my current topology is like this : controller(run cinder, ip : 10.10.10.10) - switch - compute node (ip : 10.10.10.30) i used iscsitarget (ietadm), here my cinder.config /[DEFAULT]/ /# LOG/STATE/ /verbose = True/ /debug = False/ /iet_conf = /etc/iet/ietd.conf/ /iscsi_helper = ietadm/ /iscsi_ip_address = 10.10.10.10/ /iscsi_target = 10.10.10.10/ /auth_strategy = keystone/ /volume_name_template = volume-%s/ /volume_group = cinder-volumes/ /#volume_name_template = cinder-volumes/ /state_path = /var/lib/cinder/ /volumes_dir = /var/lib/cinder/volumes/ /rootwrap_config = /etc/cinder/rootwrap.conf/ /api_paste_config = /etc/cinder/api-paste.ini/ /# RPC/ /rabbit_host = 10.10.10.10/ /rabbit_password = guest/ /rpc_backend = cinder.openstack.common.rpc.impl_kombu/ /# DATABASE/ /sql_connection = mysql://cinder:cinder@10.10.10.10/cinder/ /# API/ /osapi_volume_extension = cinder.api.contrib.standard_extensions/ On 7/11/2013 12:43 PM, Hameedullah Khan wrote: Please check your iscsi_ip_address. If that is not the issue can you please share more information? What iscsi implementation are you using? Are you using tgt or iscsitarget? Can you show your cinder.conf On Thu, Jul 11, 2013 at 8:57 AM, Mahardhika mahardika.gil...@andalabs.com mailto:mahardika.gil...@andalabs.com wrote: Hi, i've got it work when creating volume, but i can't attach to instance. error log from nova-compute : /Stderr: 'iscsiadm: No session found.\n'/ i have run : iscsiadm -m node -o show and it show it's values On 7/10/2013 6:08 PM, claudio marques wrote: Hi I also found a problem a while a go with creating or managing volumes. After some research I could solve it by doing the following: /vim /usr/lib/python2.7/dist-packages/cinder/volume/drivers/lvm.py/ remove line 388 385 self.tgtadm.create_iscsi_target(iscsi_name, iscsi_target, 386 0, volume_path, chap_auth, 387 check_exit_code=False*) -- close here the method* 388 * old_name=old_name) -- (remove this line)* restart all cinder services / / /cd /etc/init.d/; for i in $( ls cinder-* ); do sudo service $i restart; done/ If that doesn't help, try to see your iscsitarget is up and running. See the logs. Hope it help's Cheer's Claudio Marques clau...@onesource.pt mailto:clau...@onesource.pt http://www.onesource.pt/ Date: Wed, 10 Jul 2013 16:36:49 +0700 From: mahardika.gil...@andalabs.com mailto:mahardika.gil...@andalabs.com To: openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Subject: [Openstack] Exception during message handling on Cinder Hi, i've got this Error message in cinder-volume.log ERROR [cinder.volume.iscsi] Failed to create iscsi target for volume id:volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd. ERROR [cinder.volume.manager] volume volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd: create failed ERROR [cinder.openstack.common.rpc.amqp] Exception during message handling i have check on cinder.conf, api-paste.ini files, let me know if you guys need my config file please help me out of this thanks -- Regards, Mahardhika Gilang ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp -- Regards, Mahardhika Gilang ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Exception during message handling on Cinder
Hi, i've got this Error message in cinder-volume.log ERROR [cinder.volume.iscsi] Failed to create iscsi target for volume id:volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd. ERROR [cinder.volume.manager] volume volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd: create failed ERROR [cinder.openstack.common.rpc.amqp] Exception during message handling i have check on cinder.conf, api-paste.ini files, let me know if you guys need my config file please help me out of this thanks -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Exception during message handling on Cinder
Hi, i've got it work when creating volume, but i can't attach to instance. error log from nova-compute : /Stderr: 'iscsiadm: No session found.\n'/ i have run : iscsiadm -m node -o show and it show it's values On 7/10/2013 6:08 PM, claudio marques wrote: Hi I also found a problem a while a go with creating or managing volumes. After some research I could solve it by doing the following: /vim /usr/lib/python2.7/dist-packages/cinder/volume/drivers/lvm.py/ remove line 388 385 self.tgtadm.create_iscsi_target(iscsi_name, iscsi_target, 386 0, volume_path, chap_auth, 387 check_exit_code=False*) -- close here the method* 388 * old_name=old_name) -- (remove this line)* restart all cinder services / / /cd /etc/init.d/; for i in $( ls cinder-* ); do sudo service $i restart; done/ If that doesn't help, try to see your iscsitarget is up and running. See the logs. Hope it help's Cheer's Claudio Marques clau...@onesource.pt mailto:clau...@onesource.pt http://www.onesource.pt/ Date: Wed, 10 Jul 2013 16:36:49 +0700 From: mahardika.gil...@andalabs.com To: openstack@lists.launchpad.net Subject: [Openstack] Exception during message handling on Cinder Hi, i've got this Error message in cinder-volume.log ERROR [cinder.volume.iscsi] Failed to create iscsi target for volume id:volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd. ERROR [cinder.volume.manager] volume volume-7b84fb74-7278-4a5d-8f1e-735eae060bcd: create failed ERROR [cinder.openstack.common.rpc.amqp] Exception during message handling i have check on cinder.conf, api-paste.ini files, let me know if you guys need my config file please help me out of this thanks -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com mailto:mahardika.gil...@andalabs.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Cinder as Volume Implementation
Hi, now i am using grizzly on 13.04 Ubuntu with cinder volume as the module, and used multinode topology : - compute node - controller node - network node and cinder is on controller node, as far i know cinder used iscsi to hit the target, does it possible to used cinder on controller node? i have tried but have no luck, still get some error on the log said that failed to make iscsi target, and if it better to used cinder as volume on separate physical machine? (that will be connected to openstack management network) let me know if you all need my cinder.conf and other config file. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] why the time got from date is different from that from nova-manage?
Hi, if i'm not mistaken, time in service list is time when it's start On 6/27/2013 2:48 PM, mophis wrote: HI, I run nova-manage service list on n1 which is the contoller node, and the output is below nova-conductor n1 internal enabled:-) 2013-06-27 07:13:12 nova-certn1 internal enabled:-) 2013-06-27 07:13:12 nova-compute n1 nova enabled:-) 2013-06-27 07:13:10 nova-scheduler n1 internal enabled:-) 2013-06-27 07:13:12 nova-consoleauth n1 internal enabled:-) 2013-06-27 07:13:11 nova-compute n2 xzoneenabled:-) 2013-06-27 07:13:17 nova-compute n3 nova enabled:-) 2013-06-27 07:13:17 however, the n1's time is date Thu Jun 27 15:13:25 CST 2013 why the time got from date is different from that from nova-manage? BTW, the mysql time zone related setting is system_time_zone | CST time_zone | SYSTEM Thanks. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] why the time got from date is different from thatfrom nova-manage?
Then it's ntp things perhaps , it will update to ntp.ubuntu.com (i config this on ntp.conf) On 6/27/2013 2:58 PM, mophis wrote: No, it it the time stamp of the heartbeat sent from compute node, I dont know the frequency, but it seems to be very frenquent. please see below. Binary Host Zone Status State Updated_At nova-conductor n1 internal enabled:-) 2013-06-27 07:55:12 nova-certn1 internal enabled:-) 2013-06-27 07:55:14 nova-compute n1 nova enabled:-) 2013-06-27 07:55:13 nova-scheduler n1 internal enabled:-) 2013-06-27 07:55:12 nova-consoleauth n1 internal enabled:-) 2013-06-27 07:55:13 nova-compute n2 xzoneenabled:-) 2013-06-27 07:55:13 nova-compute n3 nova enabled:-) 2013-06-27 07:55:13 root@n1:/etc/mysql mailto:root@n1:/etc/mysql# date Thu Jun 27 15:55:32 CST 2013 -- Original -- *From: * Mahardhikamahardika.gil...@andalabs.com; *Date: * Thu, Jun 27, 2013 03:52 PM *To: * mophishongxing@qq.com; openstackopenstack@lists.launchpad.net; *Subject: * Re: [Openstack] why the time got from date is different from thatfrom nova-manage? Hi, if i'm not mistaken, time in service list is time when it's start On 6/27/2013 2:48 PM, mophis wrote: HI, I run nova-manage service list on n1 which is the contoller node, and the output is below nova-conductor n1 internal enabled:-) 2013-06-27 07:13:12 nova-certn1 internal enabled:-) 2013-06-27 07:13:12 nova-compute n1 nova enabled:-) 2013-06-27 07:13:10 nova-scheduler n1 internal enabled:-) 2013-06-27 07:13:12 nova-consoleauth n1 internal enabled:-) 2013-06-27 07:13:11 nova-compute n2 xzoneenabled:-) 2013-06-27 07:13:17 nova-compute n3 nova enabled:-) 2013-06-27 07:13:17 however, the n1's time is date Thu Jun 27 15:13:25 CST 2013 why the time got from date is different from that from nova-manage? BTW, the mysql time zone related setting is system_time_zone | CST time_zone | SYSTEM Thanks. ___ Mailing list:https://launchpad.net/~openstack Post to :openstack@lists.launchpad.net Unsubscribe :https://launchpad.net/~openstack More help :https://help.launchpad.net/ListHelp -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Vlan or Gre on Switch
Hello, i'm new in here - Does vlan tagging that connected between network node and compute node need a manageable switch? - Can i used GRE tunnel on unmanaged switch? is that possible? or vlan configuration on unmanage switch? so i can add more compute node. Thanks! -- Regards, Mahardhika Gilang ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Vlan or Gre on Switch
Could you help me? i have configure like this on ovs_quantum_plugin.ini [DATABASE] sql_connection = mysql://quantum:quantum@172.16.0.51/quantum reconnect_interval = 2 [OVS] enable_tunneling = True tenant_network_type = gre tunnel_id_ranges = 1:1000 local_ip = 10.10.10.53 integration_bridge = br-int tunnel_bridge = br-tun [AGENT] polling_interval = 2 [SECURITYGROUP] = and not work if attached to switch networknode=switch=computenode when i direct connected both of node it's working (can assign ip to instance etc) networknode===computenode Thanks! On 6/26/2013 2:55 PM, Sergey Skripnick wrote: Sure you can use GRE tunnel on unmanaged switch. Hello, i'm new in here - Does vlan tagging that connected between network node and compute node need a manageable switch? - Can i used GRE tunnel on unmanaged switch? is that possible? or vlan configuration on unmanage switch? so i can add more compute node. -- Regards, Mahardhika Gilang ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Vlan or Gre on Switch
Sure it is, but it's on vlan configuration, i am working on tunnel now. On 6/26/2013 3:51 PM, Darragh O'Reilly wrote: can the nodes ping each other via the switch? You will need to get that working first. From: Mahardhika mahardika.gil...@andalabs.com To: Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 9:04 Subject: Re: [Openstack] Vlan or Gre on Switch Could you help me? i have configure like this on ovs_quantum_plugin.ini [DATABASE] sql_connection = mysql://quantum:quantum@172.16.0.51/quantum reconnect_interval = 2 [OVS] enable_tunneling = True tenant_network_type = gre tunnel_id_ranges = 1:1000 local_ip = 10.10.10.53 integration_bridge = br-int tunnel_bridge = br-tun [AGENT] polling_interval = 2 [SECURITYGROUP] = and not work if attached to switch networknode=switch=computenode when i direct connected both of node it's working (can assign ip to instance etc) networknode===computenode Thanks! On 6/26/2013 2:55 PM, Sergey Skripnick wrote: Sure you can use GRE tunnel on unmanaged switch. Hello, i'm new in here - Does vlan tagging that connected between network node and compute node need a manageable switch? - Can i used GRE tunnel on unmanaged switch? is that possible? or vlan configuration on unmanage switch? so i can add more compute node. -- Regards, Mahardhika Gilang ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Vlan or Gre on Switch
Yes it is, it's gre-2 and connect each other, then i restart interface on VM, but it still can't get IP from network node. checking dnsmasq on network node is working $ps faux | grep dnsmasq dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces --interface=tap1a8f1ea3-54 --except-interface=lo --pid-file=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/pid --dhcp-hostsfile=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/host --dhcp-optsfile=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/opts --dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update --leasefile-ro --dhcp-range=set:tag0,10.10.30.0,static,120s --conf-file= --domain=openstacklocal On 6/26/2013 5:02 PM, Darragh O'Reilly wrote: ok good, run 'ovs-vsctl show' on both nodes. There should be gre-X port on each with remote_ip that points to the other node. If not, check local_ip on both is correct and restart the OVS plugin agent - that should rebuild the tunnel endpoints. From: Mahardhika mahardika.gil...@andalabs.com To: Darragh O'Reilly dara2002-openst...@yahoo.com; Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 10:44 Subject: Re: [Openstack] Vlan or Gre on Switch Sure it is, but it's on vlan configuration, i am working on tunnel now. On 6/26/2013 3:51 PM, Darragh O'Reilly wrote: can the nodes ping each other via the switch? You will need to get that working first. From: Mahardhika mahardika.gil...@andalabs.com To: Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 9:04 Subject: Re: [Openstack] Vlan or Gre on Switch Could you help me? i have configure like this on ovs_quantum_plugin.ini [DATABASE] sql_connection = mysql://quantum:quantum@172.16.0.51/quantum reconnect_interval = 2 [OVS] enable_tunneling = True tenant_network_type = gre tunnel_id_ranges = 1:1000 local_ip = 10.10.10.53 integration_bridge = br-int tunnel_bridge = br-tun [AGENT] polling_interval = 2 [SECURITYGROUP] = and not work if attached to switch networknode=switch=computenode when i direct connected both of node it's working (can assign ip to instance etc) networknode===computenode Thanks! On 6/26/2013 2:55 PM, Sergey Skripnick wrote: Sure you can use GRE tunnel on unmanaged switch. Hello, i'm new in here - Does vlan tagging that connected between network node and compute node need a manageable switch? - Can i used GRE tunnel on unmanaged switch? is that possible? or vlan configuration on unmanage switch? so i can add more compute node. -- Regards, Mahardhika Gilang ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Regards, Mahardhika Gilang PT. Andalabs Technology Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Vlan or Gre on Switch
Nothing at all on tcpdump, do you mean crossover cable? damn i used straight ! as nowdays switch recognize it. On 6/26/2013 7:00 PM, Darragh O'Reilly wrote: ok time to see what is actually going on. Start tcpdump on the physical interfaces on both nodes: sudo tcpdump -n -i ethX proto GRE if the switch is blocking GRE, then you should see the DHCP request packets leave the compute node but not appear on the network node. If you see nothing at all - take off the 'proto GRE' from tcpdump. Or try again with the crossover to see how that worked. From: Mahardhika mahardika.gil...@andalabs.com To: Darragh O'Reilly dara2002-openst...@yahoo.com; Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 12:39 Subject: Re: [Openstack] Vlan or Gre on Switch Yes it is, it's gre-2 and connect each other, then i restart interface on VM, but it still can't get IP from network node. checking dnsmasq on network node is working $ps faux | grep dnsmasq dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces --interface=tap1a8f1ea3-54 --except-interface=lo --pid-file=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/pid --dhcp-hostsfile=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/host --dhcp-optsfile=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/opts --dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update --leasefile-ro --dhcp-range=set:tag0,10.10.30.0,static,120s --conf-file= --domain=openstacklocal On 6/26/2013 5:02 PM, Darragh O'Reilly wrote: ok good, run 'ovs-vsctl show' on both nodes. There should be gre-X port on each with remote_ip that points to the other node. If not, check local_ip on both is correct and restart the OVS plugin agent - that should rebuild the tunnel endpoints. From: Mahardhika mahardika.gil...@andalabs.com To: Darragh O'Reilly dara2002-openst...@yahoo.com; Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 10:44 Subject: Re: [Openstack] Vlan or Gre on Switch Sure it is, but it's on vlan configuration, i am working on tunnel now. On 6/26/2013 3:51 PM, Darragh O'Reilly wrote: can the nodes ping each other via the switch? You will need to get that working first. From: Mahardhika mahardika.gil...@andalabs.com To: Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 9:04 Subject: Re: [Openstack] Vlan or Gre on Switch Could you help me? i have configure like this on ovs_quantum_plugin.ini [DATABASE] sql_connection = mysql://quantum:quantum@172.16.0.51/quantum reconnect_interval = 2 [OVS] enable_tunneling = True tenant_network_type = gre tunnel_id_ranges = 1:1000 local_ip = 10.10.10.53 integration_bridge = br-int tunnel_bridge = br-tun [AGENT] polling_interval = 2 [SECURITYGROUP] = and not work if attached to switch networknode=switch=computenode when i direct connected both of node it's working (can assign ip to instance etc) networknode===computenode Thanks! On 6/26/2013 2:55 PM, Sergey Skripnick wrote: Sure you can use GRE tunnel on unmanaged switch. Hello, i'm new in here - Does vlan tagging that connected between network node and compute node need a manageable switch? - Can i used GRE tunnel on unmanaged switch? is that possible? or vlan configuration on unmanage switch? so i can add more compute node. -- Regards, Mahardhika Gilang ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Regards, Mahardhika Gilang PT. Andalabs Technology Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com -- Regards, Mahardhika Gilang PT. Andalabs Technology Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com -- Regards, Mahardhika Gilang *PT. Andalabs Technology * Gedung Gravira Jl. Cideng Barat no. 54 Jakarta Pusat 10150 HP : 0852 139 55861 Email : mahardika.gil...@andalabs.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Vlan or Gre on Switch
br-tun and br-int is down on both node #br-tun: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN mode DEFAULT #br-int: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN mode DEFAULT how can they down, i have restart openvswitch agent and restart both machine still same. On 6/26/2013 8:02 PM, Darragh O'Reilly wrote: are you sure the instance is sending DHCP requests? Because if you are seeing nothing leave the compute-node, then neither direct nor via switch will work. But you say GRE worked with a direct cable. So I can't explain that, unless your new config is wrong or the switch is blocking GRE for some reason. Are you using the same IP addresses for the switch connection as you used for the direct connection? If you could post 'ovs-vsctl show' and 'ip link' from both nodes. From: Mahardhika mahardika.gil...@andalabs.com To: Darragh O'Reilly dara2002-openst...@yahoo.com; openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 13:14 Subject: Re: [Openstack] Vlan or Gre on Switch Nothing at all on tcpdump, do you mean crossover cable? damn i used straight ! as nowdays switch recognize it. On 6/26/2013 7:00 PM, Darragh O'Reilly wrote: ok time to see what is actually going on. Start tcpdump on the physical interfaces on both nodes: sudo tcpdump -n -i ethX proto GRE if the switch is blocking GRE, then you should see the DHCP request packets leave the compute node but not appear on the network node. If you see nothing at all - take off the 'proto GRE' from tcpdump. Or try again with the crossover to see how that worked. From: Mahardhika mahardika.gil...@andalabs.com To: Darragh O'Reilly dara2002-openst...@yahoo.com; Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 12:39 Subject: Re: [Openstack] Vlan or Gre on Switch Yes it is, it's gre-2 and connect each other, then i restart interface on VM, but it still can't get IP from network node. checking dnsmasq on network node is working $ps faux | grep dnsmasq dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces --interface=tap1a8f1ea3-54 --except-interface=lo --pid-file=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/pid --dhcp-hostsfile=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/host --dhcp-optsfile=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/opts --dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update --leasefile-ro --dhcp-range=set:tag0,10.10.30.0,static,120s --conf-file= --domain=openstacklocal On 6/26/2013 5:02 PM, Darragh O'Reilly wrote: ok good, run 'ovs-vsctl show' on both nodes. There should be gre-X port on each with remote_ip that points to the other node. If not, check local_ip on both is correct and restart the OVS plugin agent - that should rebuild the tunnel endpoints. From: Mahardhika mahardika.gil...@andalabs.com To: Darragh O'Reilly dara2002-openst...@yahoo.com; Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 10:44 Subject: Re: [Openstack] Vlan or Gre on Switch Sure it is, but it's on vlan configuration, i am working on tunnel now. On 6/26/2013 3:51 PM, Darragh O'Reilly wrote: can the nodes ping each other via the switch? You will need to get that working first. From: Mahardhika mahardika.gil...@andalabs.com To: Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 9:04 Subject: Re: [Openstack] Vlan or Gre on Switch Could you help me? i have configure like this on ovs_quantum_plugin.ini [DATABASE] sql_connection = mysql://quantum:quantum@172.16.0.51/quantum reconnect_interval = 2 [OVS] enable_tunneling = True tenant_network_type = gre tunnel_id_ranges = 1:1000 local_ip = 10.10.10.53 integration_bridge = br-int tunnel_bridge = br-tun [AGENT] polling_interval = 2 [SECURITYGROUP] = and not work if attached to switch networknode=switch=computenode when i direct connected both of node it's working (can assign ip to instance etc) networknode===computenode Thanks! On 6/26/2013 2:55 PM, Sergey Skripnick wrote: Sure you can use GRE tunnel on unmanaged switch. Hello, i'm new in here - Does vlan tagging that connected between network node and compute node need a manageable switch? - Can i used GRE tunnel on unmanaged switch? is that possible? or vlan configuration on unmanage switch? so i can add more compute node. -- Regards, Mahardhika Gilang ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net
Re: [Openstack] Vlan or Gre on Switch
Hi, i've got it work! i just missing # in ovs_quantum_plugin.ini in vlan configuration, but in #ip link, br-int and br-tun still state down but it just work on unmanaged switch. Thanks for helping me out Darragh O'Reilly and all, now i can move to next level. On 6/26/2013 8:02 PM, Darragh O'Reilly wrote: are you sure the instance is sending DHCP requests? Because if you are seeing nothing leave the compute-node, then neither direct nor via switch will work. But you say GRE worked with a direct cable. So I can't explain that, unless your new config is wrong or the switch is blocking GRE for some reason. Are you using the same IP addresses for the switch connection as you used for the direct connection? If you could post 'ovs-vsctl show' and 'ip link' from both nodes. From: Mahardhika mahardika.gil...@andalabs.com To: Darragh O'Reilly dara2002-openst...@yahoo.com; openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 13:14 Subject: Re: [Openstack] Vlan or Gre on Switch Nothing at all on tcpdump, do you mean crossover cable? damn i used straight ! as nowdays switch recognize it. On 6/26/2013 7:00 PM, Darragh O'Reilly wrote: ok time to see what is actually going on. Start tcpdump on the physical interfaces on both nodes: sudo tcpdump -n -i ethX proto GRE if the switch is blocking GRE, then you should see the DHCP request packets leave the compute node but not appear on the network node. If you see nothing at all - take off the 'proto GRE' from tcpdump. Or try again with the crossover to see how that worked. From: Mahardhika mahardika.gil...@andalabs.com To: Darragh O'Reilly dara2002-openst...@yahoo.com; Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 12:39 Subject: Re: [Openstack] Vlan or Gre on Switch Yes it is, it's gre-2 and connect each other, then i restart interface on VM, but it still can't get IP from network node. checking dnsmasq on network node is working $ps faux | grep dnsmasq dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces --interface=tap1a8f1ea3-54 --except-interface=lo --pid-file=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/pid --dhcp-hostsfile=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/host --dhcp-optsfile=/var/lib/quantum/dhcp/5b4619d2-198b-453a-8ab6-b1c5545edb1f/opts --dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update --leasefile-ro --dhcp-range=set:tag0,10.10.30.0,static,120s --conf-file= --domain=openstacklocal On 6/26/2013 5:02 PM, Darragh O'Reilly wrote: ok good, run 'ovs-vsctl show' on both nodes. There should be gre-X port on each with remote_ip that points to the other node. If not, check local_ip on both is correct and restart the OVS plugin agent - that should rebuild the tunnel endpoints. From: Mahardhika mahardika.gil...@andalabs.com To: Darragh O'Reilly dara2002-openst...@yahoo.com; Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 10:44 Subject: Re: [Openstack] Vlan or Gre on Switch Sure it is, but it's on vlan configuration, i am working on tunnel now. On 6/26/2013 3:51 PM, Darragh O'Reilly wrote: can the nodes ping each other via the switch? You will need to get that working first. From: Mahardhika mahardika.gil...@andalabs.com To: Sergey Skripnick sskripn...@mirantis.com; openstack@lists.launchpad.net Sent: Wednesday, 26 June 2013, 9:04 Subject: Re: [Openstack] Vlan or Gre on Switch Could you help me? i have configure like this on ovs_quantum_plugin.ini [DATABASE] sql_connection = mysql://quantum:quantum@172.16.0.51/quantum reconnect_interval = 2 [OVS] enable_tunneling = True tenant_network_type = gre tunnel_id_ranges = 1:1000 local_ip = 10.10.10.53 integration_bridge = br-int tunnel_bridge = br-tun [AGENT] polling_interval = 2 [SECURITYGROUP] = and not work if attached to switch networknode=switch=computenode when i direct connected both of node it's working (can assign ip to instance etc) networknode===computenode Thanks! On 6/26/2013 2:55 PM, Sergey Skripnick wrote: Sure you can use GRE tunnel on unmanaged switch. Hello, i'm new in here - Does vlan tagging that connected between network node and compute node need a manageable switch? - Can i used GRE tunnel on unmanaged switch? is that possible? or vlan configuration on unmanage switch? so i can add more compute node. -- Regards, Mahardhika Gilang ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help
