Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2014-08-26

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

All times shown according to UTC.

Time Nick Message
01:00 angdraug joined #fuel
01:55 xarses joined #fuel
02:30 mattgriffin joined #fuel
04:04 ArminderS joined #fuel
04:11 mattgriffin joined #fuel
04:12 xarses joined #fuel
04:34 aepifanov joined #fuel
05:02 pasquier-s joined #fuel
05:20 nimion joined #fuel
05:21 adanin joined #fuel
05:57 Longgeek joined #fuel
06:34 e0ne joined #fuel
06:34 holser joined #fuel
06:41 e0ne joined #fuel
06:46 Longgeek joined #fuel
06:46 e0ne joined #fuel
06:55 Longgeek_ joined #fuel
06:56 monester_ joined #fuel
06:58 Longgeek joined #fuel
06:58 adanin joined #fuel
07:07 Longgeek_ joined #fuel
07:11 Longgeek joined #fuel
07:14 Longgeek_ joined #fuel
07:14 omelchek joined #fuel
07:30 ddmitriev joined #fuel
07:54 Longgeek joined #fuel
07:55 Longgeek_ joined #fuel
08:16 e0ne joined #fuel
08:44 Longgeek joined #fuel
08:45 e0ne joined #fuel
08:53 skonno joined #fuel
08:55 skonno hello
08:56 skonno just one simple question.  are there any way to initialize fuel environment by command?
09:09 kaliya skonno: you mean by starting from a minimal CentOS ISO?
09:31 geekinut1h joined #fuel
09:31 HeOS joined #fuel
09:40 skonno joined #fuel
09:44 skonno that is one way but anyway to "db sync" the fuel DB?
09:45 kaliya skonno: what's your goal?
09:46 skonno i have a fuel environment but that does not detect servers.  i want to refresh it without starting from scratch.
09:48 kaliya are you running fuel 5.0?
09:48 kaliya so, servers are not booting from fuel-master dhcp correctly?
09:49 skonno not booting, using 5.0.1 on virtualbox
09:51 Longgeek joined #fuel
09:52 kaliya skonno: you can try to destroy the containers and rebuild them all
09:52 kaliya dockerctl destroy postgres;dockerctl destroy nailgun;dockerctl destroy cobbler
09:52 kaliya and then, `dockerctl build all`
09:54 neophy joined #fuel
09:55 skonno it happens almost always when I abort the virtualbox env.
09:55 skonno ok, thanks!
09:58 neophy I used Fuel 5.0 for Openstack Icehouse deployment. when I use # ceilometer statistics --meter cpu_util
09:58 neophy I am getting : Error communicating with http://<controller_ip>:8777 [Errno 110] Connection timed out
09:58 neophy but my ceilometer-api is running
09:58 neophy # ps aux | grep ceilometer-api | grep -v grep 166      20834  0.4  0.0 324760 60440 ?        S    09:57   0:01 /usr/bin/python /usr/bin/ceilometer-api --logfile /var/log/ceilometer/api.log
09:59 neophy does any one faced similar issue? any help clue?
10:01 neophy when I restart ceilometer-api in my controller works some time and give response to # ceilometer statistics --meter cpu_util command. After few seconds getting same issue: Error communicating with http://<controller_ip>:8777 [Errno 110] Connection timed out
10:04 mattymo joined #fuel
10:05 kaliya joined #fuel
10:14 bookwar joined #fuel
10:15 bookwar_ joined #fuel
10:23 tatyana joined #fuel
11:04 kevinbenton joined #fuel
11:19 Longgeek joined #fuel
11:30 Longgeek joined #fuel
11:35 adanin joined #fuel
11:41 ganso hi guys, where can I find 5.0 --> 5.0.1 --> 5.0.2 changelog?
11:43 bookwar_ ganso: take a look at http://docs.mirantis.com/openstack/fuel/fuel-5.0/pdf/Mirantis-OpenStack-5.0.1-RelNotes.pdf
11:44 ganso bookwar: thanks a lot! :)
12:02 aepifanov joined #fuel
12:28 rmoe joined #fuel
12:39 nimissa joined #fuel
12:51 kaliya_ joined #fuel
12:52 monester_ joined #fuel
12:56 kaliya joined #fuel
12:57 kaliya joined #fuel
13:26 adanin_ joined #fuel
13:28 avicii joined #fuel
13:28 tatyana joined #fuel
13:53 Kupo24z joined #fuel
13:57 e0ne joined #fuel
14:05 Chocobo joined #fuel
14:06 Chocobo When installing the fuel master node is it normal to get the "Mounted filesystem with ordered data mode" repeatedly when doing the docker "stuff"?
14:07 kaliya Chocobo, yes
14:08 Chocobo kaliya: Ok thanks.
14:09 Chocobo I was a littler nervous because it seems to take a REALLY long time.
14:15 akupko joined #fuel
14:19 kaliya Chocobo, it takes a while. What's your hardware/VM settings?
14:19 mattymo Chocobo, that speed depends mostly on disk performance of your system
14:19 mattymo there's a tool recently released called docker-squash, which should speed this part up by 30% according to my first tests. I am still trying to integrate it in our build process, though
14:19 f13o KVM: what sort of disk images are you using for Fuel? I've tried qcow2 and raw, with and w/o cache... it's slow in every case....
14:20 f13o Any hints?
14:20 f13o VirtualBox "flies" on the same hw....
14:20 f13o So I'm guessing it's something with kvm/qemu tunning...
14:23 mattymo there's not a lot we can do to speed it up on vms. In 6.0 we should have a newer docker and smaller docker images with fewer layers
14:25 f13o one thing I haven't tried is not runing guest images on top of LVM.. Would that make any difference ?
14:28 skonno joined #fuel
14:30 skonno joined #fuel
14:34 MiroslavAnashkin we use both, qcow2 and raw. Raw is greatly recommended for Ceph backends, qcow2 for Cinder LVM backend
14:36 f13o Thanks. But here I'm mainly talking about the Fuel master itself. That one is slow to install and boot on kvm.
14:39 evg f13o: I use kvm/qemu and don't see any difference with virtualbox. Are you sure kvm is enabled?
14:40 Kupo24z Looks like the tcp iptables bug got fixed but the master/5.1 community failed tests :(
14:44 f13o Other guests run quite nicely and yes, kvm is loaded and enabled.
14:44 MiroslavAnashkin f13o: Please also check KSM (kernel same page merging) and if Nested Virtualization enabled in KVM
14:45 MiroslavAnashkin Master node uses LXC/Docker and definitely need nested virtualization enabled.
14:45 evg f13o: sorry, what do you mean "other guests"?
14:47 evg f13o: master node takes a time for instalation, btw
14:48 f13o non-fuel, non-openstack guests that i run for different purposes ... non-related to fuel (and, no, they are not up when I am installing fuel)
14:50 f13o anyway, I'll try later, and continue using Virtualbox at the moment.. Thanks for your time.
14:50 f13o Will return to this later, though...
14:54 Chocobo joined #fuel
14:54 Chocobo joined #fuel
15:02 jobewan joined #fuel
15:07 angdraug joined #fuel
15:15 blahRus joined #fuel
15:35 Chocobo How about "Not collecting exported resources without storeconfigs"  Is that a normal warning?
15:43 TVR_1 joined #fuel
15:48 xarses joined #fuel
15:52 MiroslavAnashkin Yes, it is OK
15:58 rmoe joined #fuel
15:58 ArminderS joined #fuel
16:19 ArminderS- joined #fuel
16:33 angdraug joined #fuel
16:41 pasquier-s joined #fuel
16:41 Chocobo joined #fuel
16:48 Chocobo joined #fuel
16:48 Chocobo joined #fuel
16:55 aepifanov joined #fuel
16:58 Chocobo if I was to apply this patch set: https://review.openstack.org/#/c/116261/ Where would I apply it?  I do not seem to have any directory structure on the fuel master node that looks like this.
16:59 angdraug deployment/puppet/ in fuel-library corresponds to /etc/puppet/modules/ on the master node
17:02 Chocobo well that is a bummer... the fuel master node doesn't have patch.
17:03 e0ne joined #fuel
17:03 fandi joined #fuel
17:06 angdraug what? mattymo: ^
17:06 angdraug which container did you hide patch in? :)
17:07 angdraug http://fuel-repository.mirantis.com/fwm/5.1/centos/os/x86_64/Packages/patch-2.6-6.el6.x86_64.rpm
17:07 angdraug it's there in the repo, so yum install should be able to fix that
17:08 angdraug http://docs.mirantis.com/openstack/fuel/fuel-5.0/operations.html#applying-a-patch
17:08 angdraug mattymo: looks like ^ needs to be updated to post-docker reality
17:15 kupo24z joined #fuel
17:17 Chocobo Thanks angdraug
17:18 Chocobo We just did them by hand real quickly.
17:18 Chocobo After installing the patch is there anything else I have to do before trying to deploy openstack again?
17:19 angdraug no
17:19 kupo24z Can somone verify if fuel-community-5.1-8-2014-08-26_05-19-34 has https://bugs.launchpad.net/bugs/1360298 commited?
17:19 angdraug rmoe: can you have a quick look for kupo24z?
17:19 rmoe angdraug: sure, no problem
17:19 kupo24z and if not can a new image be pushed? its a critical stopping deployments from testing
17:25 syndrift joined #fuel
17:29 bookwar kupo24z: it wasn't there, iso was built at 2 AM, while patch was merged around 1 pm
17:30 kupo24z Darn, guess will have to wait till tomorrow then
17:31 bookwar kupo24z: community builds are scheduled for 5 AM UTC
17:32 mattgriffin joined #fuel
17:33 kupo24z bookwar: community builds are normally scheduled for 5AM why did this one build at 2am?
17:33 bookwar kupo24z: maybe I was mistaken, I'll check..
17:35 blahRus bookwar: If we supply a server can we create builds ourself ;) ?
17:36 bookwar blahRus: our build instructions are open and i can share aour Jenkins job configuration with you, so it could be easy for you to organize daily builds
17:37 bookwar kupo24z: build id says Aug 26, 2014 5:19:34 AM so this is the time in UTC timezone when build was performed
17:38 bookwar kupo24z: and timestamp shows some other time, and i need to check what this timestamp means here: https://fuel-jenkins.mirantis.com/view/ISO/
17:38 bookwar i'll add the info on this page tomorrow
17:38 kupo24z any chance to spawn a new build if you have idle servers today?
17:40 bookwar kupo24z: let me check if we plan any critical mirror updates tonight, if not i'll trigger the build
17:40 kupo24z ty
17:42 bookwar kupo24z: ok, let's try it https://fuel-jenkins.mirantis.com/view/ISO/job/fuel_community_5_1_iso/9/
17:43 kupo24z That has the commit for https://bugs.launchpad.net/bugs/1360298 bookwar?
17:43 bookwar kupo24z: yes, it is built from current master
17:43 kupo24z Thanks!
17:43 kupo24z I'll test it out when its done
17:45 xarses joined #fuel
17:47 mattgriffin joined #fuel
18:06 angdraug joined #fuel
18:07 HeOS joined #fuel
18:13 angdraug joined #fuel
18:30 tatyana joined #fuel
18:37 adanin joined #fuel
19:22 aepifanov joined #fuel
19:23 monester_ joined #fuel
20:17 emagana joined #fuel
20:18 emagana Is this the right channel for Fuel questions?
20:18 emagana https://wiki.openstack.org/wiki/Fuel
20:20 xarses emagana: correct
20:20 emagana nice!
20:21 emagana xarses: I just downloaded 5.0.1 and I was comparing the puppet modules with the ones in stackforce
20:21 emagana They seem to be different...
20:21 emagana I was checking out the mysql one for instance
20:22 xarses correct, a number of our modules are behind what puppet-openstack uses
20:23 emagana mhhh, for instance how can I find the repos that Fuel uses for all puppet modules?
20:23 xarses we are in progress of making them closer to upstream, hopefully around the 6.0 release we will be able to use the tip of any of the puppet-openstack modules and therefore also run CI tests for them
20:23 emagana xarses: I got it
20:24 xarses take a look over https://blueprints.launchpad.net/fuel/+spec/merge-openstack-puppet-modules which is what we have been doing to pull the modules back up
20:24 emagana xarses: Oh, it seems you got it from here: https://github.com/Mirantis/puppetlabs-mysql
20:24 MiroslavAnashkin All our repos are publicly available. Please check http://docs.mirantis.com/fuel-dev/develop/env.html#building-the-fuel-iso , repos are listed there
20:25 tatyana joined #fuel
20:25 emagana Great docs!
20:26 xarses you should be able check the Modulefile in each puppet module to see where it came from
20:27 xarses the module files we use are kept at https://github.com/stackforge/fuel-library/tree/master/deployment/puppet
20:27 emagana that is the consugin part
20:28 emagana name 'puppetlabs-mysql'
20:28 emagana version '0.3.0'
20:28 emagana source 'git://github.com/puppetlabs/puppetlabs-mysql.git'
20:28 emagana for instance, the mysql module in my fuel master server indicates:
20:29 xarses correct, so when we added it to fuel, thats where it came from
20:29 emagana but if a visually compare the code there is not match
20:29 emagana compare with the https://github.com/puppetlabs/puppetlabs-mysql
20:30 xarses you also need to change the version to 0.3.0
20:30 xarses the closest version would be https://github.com/puppetlabs/puppetlabs-mysql/tree/0.3.0
20:30 xarses but since we are still out of sync on that module, we have likely modified it
20:31 xarses once it's been synced there will be a commit like https://github.com/stackforge/fuel-library/commit/29be2f2e4d71397fc7aaabafd57cdc2471e15011
20:31 xarses which identifies exactly which commit we took
20:32 xarses also that that point we try to stop making our own modifications.
20:32 xarses Like i said already, we are very far behind on some of the modules and diverged
20:33 xarses sometimes up to 2 years ago, and we are working had to get back to using current versions
20:48 e0ne joined #fuel
20:49 emagana xarses: I got it.. sorry I had to go offline for a bit
20:49 emagana I see that.. I checkout the 0.x version and is matching what you had in fuel..
20:49 emagana xarses: Thanks for the answers
20:56 kupo24z xarses: do you know if https://wiki.openstack.org/wiki/InstanceResourceQuota works with ceph ephemeral?
20:57 xarses kupo24z: it's a feature of libvirt so no clue
20:57 xarses I can ask
20:57 kupo24z ty
21:05 angdraug joined #fuel
21:10 kupo24z xarses: do you know offhand if there is any difference limiting the port in/out via OVS/Neutron vs libvirt?
21:11 kupo24z I imagine there is a bit of overhead of its done at libvirt
21:12 xarses no, I dont. but I'd imagine libvirt would have less of an issue with it since it can easily make it look like the mac layer is blocking vs OVS would have to cache / drop packets to get it to back off
21:46 emagana joined #fuel
22:15 angdraug joined #fuel
22:50 ilbot3 joined #fuel
22:50 Topic for #fuel is now Fuel 5.0.1 for Openstack: https://wiki.openstack.org/wiki/Fuel | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel/
22:56 ganso joined #fuel
23:08 kupo24z New zabbix bug :( made report.
23:15 xarses =(
23:15 kupo24z Also looks like glance upload error is back, but it may be caused by the zabbix freaking out
23:16 kupo24z since it looks like rabbitMQ started fine in docker this time
23:16 xarses glance tends to fail if ceph wont accept the writes
23:16 xarses although that might not be your case
23:18 kupo24z I'm trying again now
23:24 kupo24z Looks like 'host not ready' and 'init hw failure' is still around but less common now
23:48 kupo24z Looks like its working with no glance upload error when i took zabbix out of the picture
23:48 kupo24z NBD really
23:52 pasquier-s joined #fuel
23:56 xarses odd that it gave you glance image failed instead of node error
23:57 kupo24z Well it was node errors + the glance error, its in the snapshot on that bug
23:57 kupo24z https://bugs.launchpad.net/fuel/+bug/1361903
23:57 kupo24z It was just the generic astute log error
23:58 kupo24z as i recall zabbix node failed, then 3x controllers failed, then astute error

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