Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2013-12-05

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

All times shown according to UTC.

Time Nick Message
23:02 rmoe joined #fuel
23:14 Vidalinux joined #fuel
23:56 rongze joined #fuel
00:04 dhblaz joined #fuel
00:04 xarses joined #fuel
00:51 jouston joined #fuel
01:16 tsduncan__ joined #fuel
01:28 rongze joined #fuel
01:40 fandikurnia01 joined #fuel
01:48 jouston joined #fuel
02:14 jouston I have completed iso build: https://bugs.launchpad.net/fuel/+bug/1255088/comments/12
02:15 jouston However the repo.mk code isn't merged yet. Should I commit the code? I have no idea about the check for yumdownloader.log so I'm probably won't be the right person to checkin code.
02:48 fandikurnia01 joined #fuel
02:50 dhblaz joined #fuel
02:53 rongze joined #fuel
02:55 vkozhukalov joined #fuel
02:55 rongze_ joined #fuel
03:00 IlyaE joined #fuel
03:26 ArminderS- joined #fuel
03:43 IlyaE joined #fuel
03:58 dhblaz joined #fuel
04:22 rvyalov joined #fuel
04:38 IlyaE joined #fuel
05:22 xarses joined #fuel
05:52 IlyaE joined #fuel
06:01 e0ne joined #fuel
06:36 e0ne joined #fuel
06:44 jkyle joined #fuel
06:54 rongze joined #fuel
07:00 IlyaE joined #fuel
07:07 mihgen joined #fuel
07:21 ArminderS- why does the node wait for determining IPs for NICs 2, 3 & 4 post centos install while deployment
07:21 ArminderS- shouldn't those nics be down on first boot post os install
07:21 ArminderS- it just delays the booting process
07:21 ArminderS- puppet can anyways up the nics while running
07:49 IlyaE joined #fuel
07:52 Fecn joined #fuel
07:56 ArminderS- why do we need this -> node-1 puppet-agent[23158]: (/Stage[main]/Galera/File[/etc/init.d/mysql]/mode) mode changed '0755' to '0644'
07:58 e0ne joined #fuel
08:02 fandikurnia01 joined #fuel
08:07 ArminderS- <29>Dec  5 07:59:24 node-1 puppet-agent[23158]: (Puppet::Type::Neutron_net::ProviderNeutron) Neutron API not avalaible. Wait up to 116 sec.
08:07 ArminderS- <29>Dec  5 07:59:29 node-1 puppet-agent[23158]: (Puppet::Type::Neutron_net::ProviderNeutron) Neutron API not avalaible. Wait up to 111 sec.
08:07 ArminderS- <29>Dec  5 07:59:35 node-1 puppet-agent[23158]: (Puppet::Type::Neutron_net::ProviderNeutron) Neutron API not avalaible. Wait up to 105 sec.
08:08 e0ne_ joined #fuel
08:08 ArminderS- any ideas as to why it can't find neutron api
08:08 ArminderS- its fuel 4 from fuel-4.0-91-2013-12-02_06-01-30.iso
08:09 ArminderS- puppet started deploying openstack and its still on first controller
08:09 ArminderS- trying to setup ha with neutron gre, 3 controllers, 2 ceph & 2 compute nodes
08:10 ArminderS- all on vmware esxi with all 4 networks having promisc enabled
08:11 mihgen ArminderS-: hi
08:12 ArminderS- the above is immediately after -> (/Stage[main]/Neutron::Agents::Metadata/Service[p_neutron-metadata-agent]/enable) enable changed 'true' to 'true'
08:12 mihgen I think all of this is worth to be filed as bugs =)
08:12 ArminderS- and can see that mysql dies by that time
08:13 mihgen 4.0 is very unstable now...
08:13 ArminderS- aye, i understand
08:13 ArminderS- but still thought of taking my chances with it
08:16 mihgen ArminderS-: it's all just needs a sit and step by step fixing ..
08:17 ArminderS- i reckon
08:21 ArminderS- mihgen: you got code freeze yet on 3.2.1?
08:23 tatyana joined #fuel
08:32 SteAle joined #fuel
08:32 vkozhukalov joined #fuel
08:42 mihgen ArminderS-: yes, we did, yesterday morning MSK
08:42 mihgen subscribe to fuel-dev mailing list for updates here: https://launchpad.net/~fuel-dev
08:45 ArminderS- aye, found that email
08:45 ArminderS- i'm already subscribed
08:46 ArminderS- just need to put proper filters for mail client
08:46 ArminderS- all my openstack mailing lists is going into same folder
08:46 ArminderS- just wondering where can one put some feature request
08:46 meow-nofer joined #fuel
08:47 ArminderS- i liked the additions to settings in fuel
08:48 ArminderS- and network (spl. public start and end instead of cidr)
08:49 ArminderS- just wished you would have added 1 additional parameter to input the KA IP
08:49 ArminderS- so that one can choose which IP to set as VIP for controller cluster
08:50 ArminderS- seems like the first IP in public is being used for the purpose now
09:01 e0ne joined #fuel
09:13 amartellone joined #fuel
09:18 jouston joined #fuel
09:22 xdeller joined #fuel
09:36 e0ne_ joined #fuel
09:54 teran joined #fuel
10:14 manashkin_ joined #fuel
10:33 teran joined #fuel
10:55 jkirnosova joined #fuel
11:29 mihgen joined #fuel
11:29 teran joined #fuel
11:38 jouston joined #fuel
11:57 rongze joined #fuel
12:17 teran joined #fuel
12:17 zwj joined #fuel
12:35 rongze joined #fuel
12:41 rongze_ joined #fuel
12:49 xdeller joined #fuel
13:05 vk is netmask 255.255.255.255 valid for our l2 networks? and 255.255.255.254?
13:15 e0ne joined #fuel
13:20 mattymo technically they're legal but unusual
13:20 mattymo 1st only can include 1 host, 2nd only 2
13:20 mattymo vk, ^
13:21 mihgen mattymo: it's about network, btw L3
13:21 mihgen vk: is it for network, or netmask for host IP ?
14:03 e0ne joined #fuel
14:05 e0ne joined #fuel
14:11 ruhe joined #fuel
14:12 zwj_ joined #fuel
14:43 vk joined #fuel
15:04 e0ne joined #fuel
15:27 e0ne joined #fuel
15:34 IlyaE joined #fuel
15:40 ArminderS- joined #fuel
15:44 oleksii_klymenok left #fuel
16:04 ArminderS- joined #fuel
16:15 ArminderS- joined #fuel
16:17 e0ne_ joined #fuel
17:11 angdraug joined #fuel
17:24 dhblaz joined #fuel
17:31 e0ne_ joined #fuel
17:33 dhblaz xarses, the img I made yesterday didn't include my patch for ks.cfg to work with cciss hardware (HP RAID)
17:41 Fecn joined #fuel
17:59 rmoe joined #fuel
18:00 xarses joined #fuel
18:00 teran joined #fuel
18:08 vkozhukalov joined #fuel
18:17 IlyaE joined #fuel
18:35 e0ne joined #fuel
18:37 e0ne joined #fuel
18:38 e0ne__ joined #fuel
19:00 e0ne joined #fuel
19:13 manashkin__ joined #fuel
19:14 manashkin__ <dhblaz>: Oops, yes. We have not included this patch to master node kickstart, only to slave nodes ones.
20:01 e0ne joined #fuel
20:24 tatyana joined #fuel
20:33 xdeller joined #fuel
20:36 e0ne_ joined #fuel
20:49 manashkin_ joined #fuel
20:58 mihgen joined #fuel
21:28 IlyaE joined #fuel
21:39 e0ne joined #fuel
21:40 e0ne joined #fuel
21:56 Fecn Hi Folks - if I mark a disk as unassigned in the installer, does that mean it won't be used, or that it will be assigned some purpose by default? ( I ask this because all of my servers have a dumb 4GB USB stick embedded on the motherboard and I think fuel is building it into all of the md raid sets)
21:58 Fecn filesystem performance is around 80MB/sec for dd'ing from /dev/zero
21:59 Fecn which is pretty lame
22:04 Fecn I'm also have a weird problem where 90% of the way through the the install, fuel reconfigures two of the controller nodes so that they have clashing IP addresses... at which point one or the other of them becomes 'disconnected' (of course)
22:19 dhblaz joined #fuel
22:22 dhblaz I forgot what controls the initial puppet bootstrap on the fuel master node
22:22 dhblaz Would someone remind me please
22:33 dhblaz Found it, /usr/local/sbin/bootstrap_admin_node.sh
22:58 xarses Fecn: It will be included in the md that is used for the boot volume
22:59 xarses Fecn: The clash should only occur if 1) there is a partially deployed node on the network that didn't go back into the bootloader 2) there is a DHCP server on one of the networks assigning a conflicting ip. I've yet to see that occur in any other way. If neither 1,2 are correct then its very much a bug we haven't seen

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