Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2013-12-07

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
23:01 e0ne joined #fuel
23:09 Vidalinux can I use RDO openstack packages with fuel ?
23:11 xarses Vidalinux: If you have a subscription with RedHat, we support installing RHOS
23:11 Vidalinux xarses, I don't have it
23:15 xarses Vidalinux: thats the only way we can provide RHOS support, as we can't ship the redhat packages due to licensing restrictions
23:15 Vidalinux RDO packages have restrictions ?
23:16 xarses Most of RedHat's packages do
23:17 xarses of course the sources usually available, but they would have all be built (Like CentOS does)
23:19 Vidalinux yeah but I think their RDO are community packages and doesn't have any redhat logo or propietary code or something
23:21 xarses Sorry, I'm confusing RDO and RHOS. We cant distribute RHOS, I'm not sure about the RDO packages
23:22 xarses but we have our own builds of openstack packages so we would not use the RDO ones anyway
23:26 Vidalinux ok
23:57 tsduncan__ I am having trouble with Neutron with GRE after deployment in 3.2.1.
23:57 tsduncan__ fuellib_sha: f916de800c2e40e351feba49f47b63b975749a82
23:57 tsduncan__ nailgun_sha: 91630e8158a0edd555175392af704b28a678507d
23:57 tsduncan__ astute_sha: cb4868f0481d6c7d2d213ceb065ae3c40ab699ce
23:57 tsduncan__ ostf_sha: f1db8d45af5f5aad391af1b353c3de5d0471b99c
23:57 tsduncan__ fuelmain_sha: 3dedb1b78d3c2394b6d8a9a82a4e492d3d62c1bd
23:57 tsduncan__ I am using VLAN 101 tagged for Public, 102 for management and 103 for storage.
23:57 tsduncan__ The network test runs successfully before deployment. After deployment, the nodes can ping each other on the 101 Public network (using 172.16.0) but the other two networks have no connectivity. Any suggestions?
00:01 xarses tsduncan__: most usually, the network port on the switch is misconfigured and not passing the vlan tag. Next most common is that the switch ports and server ports are not plumbed to the proper interface
00:01 xarses tsduncan__: I haven't heard of any kernel driver issues like this with GRE, has been and issue with Neutron VLANs on Centos though
00:02 xarses tsduncan__: I have heard that there are sometimes performance issues with GRE, but that should only effect the guests.
00:03 tsduncan__ xarses: I am 99% positive the networks are configured and wired correctly. Checked, double checked and are all set up the same as vlan 101.  What is the most commonly used network deployment model?
00:05 xarses tsduncan__: I think Neutron VLAN is up there, but I'm a dev so i only hear about the ones with problems
00:06 tsduncan__ xarses: I will go back to 3.2 and see if I get the same issue. If so, I will assume it is some issue with my config. Otherwise could this be a regression?
00:08 xarses tsduncan__: everything is possible, I think there is a CI test for this already so it should have been tested. Did you use the "validate networks" button on the network page after setting the options and configuring the nodes//node interfaces?
00:08 tsduncan__ xarses: yes, the verify networks test passed before deployment
00:08 xarses hmm, that should have caught this if there was a upstream issue
00:10 xarses tsduncan__: Please file a bug if you see it happen on 3.2 as well https://bugs.launchpad.net/fuel/+bugs
00:11 tsduncan__ xarses: I also have used vconfig and created interfaces on these vlans to verify that the vlans are passing traffic between the nodes. Sometimes, after using vconfig, the openvswitch networks will start to work
00:11 xarses are you using centos?
00:12 tsduncan__ yes
00:12 xarses what is the interface driver "ethtool -i <ethX>" for the working interface and non-working?
00:12 xarses and can you http://paste.openstack.com ovs-vsctl show
00:15 tsduncan__ this is the one that works... [root@node-2 ~]# ethtool -i br-ex
00:15 tsduncan__ driver: openvswitch
00:15 tsduncan__ version:
00:15 tsduncan__ firmware-version:
00:15 tsduncan__ bus-info:
00:15 tsduncan__ supports-statistics: no
00:15 tsduncan__ supports-test: no
00:15 tsduncan__ supports-eeprom-access: no
00:15 tsduncan__ supports-register-dump: no
00:16 tsduncan__ supports-priv-flags: no
00:16 tsduncan__ Here is the one that doesn't ...[root@node-2 ~]# ethtool -i br-storage
00:16 tsduncan__ driver: openvswitch
00:16 tsduncan__ version:
00:16 tsduncan__ firmware-version:
00:16 tsduncan__ bus-info:
00:16 tsduncan__ supports-statistics: no
00:16 tsduncan__ supports-test: no
00:16 tsduncan__ supports-eeprom-access: no
00:16 tsduncan__ supports-register-dump: no
00:16 tsduncan__ supports-priv-flags: no
00:16 xarses tsduncan__: the physical eth0 or em0 or which ever
00:17 xarses I only need the driver
00:17 xarses line
00:17 tsduncan__ xarses: ok, both virtual nets are on the same physical interface
00:17 tsduncan__ [root@node-2 ~]# ethtool -i eth1
00:17 tsduncan__ driver: igb
00:17 tsduncan__ version: 4.0.1-k
00:17 tsduncan__ firmware-version: 2.00, 0x0000bb22
00:17 tsduncan__ bus-info: 0000:01:00.1
00:17 tsduncan__ supports-statistics: yes
00:17 tsduncan__ supports-test: yes
00:17 tsduncan__ supports-eeprom-access: yes
00:18 tsduncan__ supports-register-dump: yes
00:18 tsduncan__ supports-priv-flags: no
00:18 xarses thats the working and the non-working are on the same physical?
00:18 tsduncan__ xarses: correct
00:19 xarses hmm, that makes it odd, I was hoping this was an variation of the vlan-splinters issue
00:20 rmoe joined #fuel
00:21 xarses hmm go ahead and try this
00:21 xarses ovs-vsctl set interface eth1 other-config:enable-vlan-splinters=true
00:22 xarses on each physical interface that ovs uses for the vlan tagged interfaces
00:22 xarses worse case, it doesn't fix anything
00:23 tsduncan__ xarses: previously requested show is here http://paste.openstack.org/show/54634/
00:26 xarses odd that with all three on the interface that only public works
00:26 tsduncan__ xarses: that command did it
00:27 tsduncan__ I can now ping on all three
00:30 xarses ok, on the settings page should be a checkbox to enable vlan-splinters
00:30 tsduncan__ xarses: does this mean the igb driver has issues?
00:31 xarses tsduncan__: I need to check if its still in the splinters list
00:31 xarses tsduncan__: we thought the newer kernel fixed it, which it aparenntly does but for only one network tag
00:33 xarses ok, its still in the list still of drivers that might have problems, if you check that box, fuel will deploy with that param set
00:33 xarses it does increase load as more vlans are in use but since you are in GRE you will only have these three to deal with
00:34 xarses in Neutron VLAN it can cripple the box if there are enough vlans to iterate
00:34 xarses https://github.com/Mirantis/fuel/blob/3.2-fixes/deployment/puppet/l23network/lib/facter/ovs_vlan_splinters.rb#L10-15
00:34 xarses tsduncan__: ^ Drivers that are known to have buggy support (depending on kernel version)
00:34 xarses tsduncan__: also, if you use Ubuntu, this should not be an issue
00:37 tsduncan__ xarses: I wanted to use Ubuntu but the storage driver in the latest kernel does not support my hardware. It worked fine in 12.04-1 but in 12.04-3 and all of the 13.X Ubuntu releases it no longer recognizes it.
00:38 tsduncan__ LSI 1064e - it is an older part that unfortunately was used on this series of machines
00:44 xarses back in a bit
01:25 IlyaE joined #fuel
01:38 xarses joined #fuel
02:21 mihgen joined #fuel
02:26 rmoe joined #fuel
02:29 teran joined #fuel
03:13 rongze joined #fuel
03:41 ArminderS- joined #fuel
03:59 teran joined #fuel
04:10 Vidalinux joined #fuel
04:12 Vidalinux /msg NickServ identify mierda@2011
04:12 Vidalinux clear
04:13 Vidalinux lol
04:17 Vidalinux joined #fuel
04:18 Vidalinux joined #fuel
04:19 Vidalinux joined #fuel
04:21 Vidalinux joined #fuel
04:35 teran joined #fuel
05:22 rongze joined #fuel
05:39 vkozhukalov joined #fuel
06:05 teran joined #fuel
06:36 rongze joined #fuel
06:47 rongze joined #fuel
07:06 teran joined #fuel
07:59 teran joined #fuel
10:10 mihgen joined #fuel
11:20 rongze joined #fuel
11:22 e0ne joined #fuel
11:32 rongze joined #fuel
12:01 Vidalinux joined #fuel
12:04 e0ne joined #fuel
12:13 e0ne_ joined #fuel
12:16 e0ne joined #fuel
12:20 e0ne joined #fuel
12:28 teran joined #fuel
12:54 e0ne joined #fuel
13:16 e0ne joined #fuel
13:18 e0ne joined #fuel
13:41 vkozhukalov joined #fuel
14:08 ruhe joined #fuel
14:18 e0ne joined #fuel
14:48 mihgen joined #fuel
14:48 e0ne joined #fuel
14:50 e0ne joined #fuel
14:57 b-zone joined #fuel
16:08 jkyle joined #fuel
16:08 Vidalinux joined #fuel
18:14 e0ne joined #fuel
19:20 Vidalinux joined #fuel
19:33 rmoe joined #fuel
20:11 e0ne joined #fuel
21:03 mihgen joined #fuel
22:34 Vidalinux joined #fuel
22:50 teran joined #fuel

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary