Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2015-04-09

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

All times shown according to UTC.

Time Nick Message
00:56 Longgeek joined #fuel
01:07 zhangqi joined #fuel
01:16 thumpba joined #fuel
01:39 circ-user-IQ9mz joined #fuel
01:41 xarses joined #fuel
01:49 ilbot3 joined #fuel
01:49 Topic for #fuel is now Fuel 5.1.1 (Icehouse) and Fuel 6.0 (Juno) https://software.mirantis.com | Fuel for Openstack: https://wiki.openstack.org/wiki/Fuel | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel/
01:49 huddlesj joined #fuel
02:29 huddlesj Does anyone know where the dhcp and tftp log is on the fuel node?
02:33 huddlesj I found the DHCP log. It is in the dnsmasq log
02:44 Longgeek joined #fuel
02:52 rongze joined #fuel
02:53 rongze joined #fuel
03:29 Longgeek_ joined #fuel
04:33 zerda joined #fuel
04:34 LiJiansheng joined #fuel
05:22 fedexo joined #fuel
05:24 [HeOS] joined #fuel
06:12 sambork joined #fuel
06:12 dklepikov joined #fuel
06:15 alecv joined #fuel
06:38 sc-rm joined #fuel
06:39 sc-rm Hi, I tried to deploy juno via fuel 6.0 onto some servers and it will not succed, because it gives me this error every time (/Stage[main]/Openstack::Network/Exec[waiting-for-neutron-api]/returns) change from notrun to 0 failed: bash -c "source /root/openrc ; neutron net-list --http-timeout=4 " 2>&1 > /dev/null returned 1 instead of one of [0]
06:41 sc-rm I see it’s the same issue as https://bugs.launchpad.net/fuel/+bug/1384681
07:11 e0ne joined #fuel
07:26 sc-rm Seems like I ran into https://bugs.launchpad.net/fuel/+bug/1421723 Would be really nice if the fuel master checked for this. Also I noticed that the fuel master settings tab does not validate if the mail address is actually an mail address and then open stack deployment fails afterwards
07:27 hyperbaba joined #fuel
07:41 willemgf joined #fuel
07:41 devstok joined #fuel
07:41 devstok Hi all
07:41 devstok @Kaliya ci sei?
07:43 willemgf Hi, I have an active environment for which the setiing "Allow public network to all nodes" is not checked. With a running environment it is no more possible to activate this. Is there a way to force this anyway?
07:59 devstok anyone?
08:00 e0ne joined #fuel
08:01 tobiash joined #fuel
08:14 zhangqi joined #fuel
08:16 sambork joined #fuel
08:18 tobiash joined #fuel
08:20 tzn joined #fuel
08:30 zhangqi1 joined #fuel
08:30 jskarpet MCollective call failed in agent 'net_probe', method 'start_frame_listeners', failed nodes: ID: 2 - Reason: Cant stop net_probe.py execution.
08:30 jskarpet how to fix?
08:41 ddmitriev joined #fuel
08:47 samuelBartel joined #fuel
08:48 tzn joined #fuel
08:52 alecv joined #fuel
08:55 zhangqi joined #fuel
08:55 e0ne joined #fuel
09:03 sambork joined #fuel
09:31 tzn joined #fuel
09:56 teran joined #fuel
10:24 sambork joined #fuel
10:33 ibumarskov joined #fuel
10:37 [HeOS] joined #fuel
10:40 aliemieshko_ joined #fuel
10:47 zhangqi joined #fuel
10:53 homegrown joined #fuel
11:08 ibumarskov left #fuel
11:10 zhangqi joined #fuel
11:14 homegrown Does anyone have experience of running on supermicro blades? I'm seeing the nodes PXE boot, but never registering with the Fuel(6) deployment node
11:14 homegrown The blades are MBI-6128R-T2x
11:15 e0ne joined #fuel
11:15 homegrown In the same chassis the MBI-6118D-T4 blades register fine, so might be a driver issue?
11:18 ibumarskov__ joined #fuel
11:20 subscope joined #fuel
11:21 zhangqi joined #fuel
11:22 championofcyrodi homegrown: are you sure the fuel server's dhcp server is listening on the right NIC?
11:23 ibumarskov joined #fuel
11:26 ibumarskov_ joined #fuel
11:30 ibumarskov joined #fuel
11:31 ibumarskov left #fuel
11:33 homegrown championofcyrodi: Yes, the server PXE boots & gets a DHCP address, but doesn't seem to recognize the servers NIC
11:33 homegrown just installing ubuntu manually & it complains about no network card being found ...
11:34 championofcyrodi is it enabled/disabled in the bios?
11:34 championofcyrodi i guess it would be if it pxe boots...
11:35 championofcyrodi can you get to the point where you can, 'sudo lspci | grep Ether'
11:35 homegrown just going over the BIOS settings now to doublecheck
11:37 championofcyrodi when a new node boots, you should see it pxe boot via dhcp and download two files from tftp server using periods as progress... usually something like init.rd and vmlinuz (initramfs & kernel)
11:39 championofcyrodi i think after that you should see the grub screen
11:39 championofcyrodi and be able to boot ubuntu/centos
11:39 homegrown I get as far as the bootstrap logon screen
11:39 homegrown but they nodes are never discovered by the Fuel server
11:40 homegrown any idea what the password is for the bootstrap login?
11:42 championofcyrodi I'm not familiar with the Ubuntu implementation of fuel, but I do use Ubuntu for a few other things. (although I'm more and more tempted to try ubuntu+fuel everyday)
11:43 championofcyrodi in Centos the server boots mcollective and just waits there.  then it shows up as a new node on the fuel ui.
11:43 homegrown the fuel node itself is centos
11:43 homegrown that's exactly where i get to, but it never registers in the fuel UI.
11:43 championofcyrodi i don't think my servers ever had a log in on 1st boot.  is this a new fuel instance?
11:44 homegrown It also fails to sync ntp on boot, so pretty sure the network is not being recognised
11:44 championofcyrodi that is odd.
11:44 championofcyrodi how many NICs does each server have?
11:44 homegrown After PXE boot, it just sits on a Centos login screen until a role is deployed to it
11:44 homegrown 2 NICs per server
11:45 homegrown so if i can login at the bootstrap login, maybe i can do some probing of hardware
11:45 championofcyrodi if i remember correctly, there might be an issue with the order in which the NICs are used...
11:45 championofcyrodi have you tried switching NICs?
11:46 championofcyrodi i mean switching the ethernet cable from nic0 to nic1
11:46 championofcyrodi or vice versa
11:47 homegrown I will try to flip things around in the BIOS & report back
11:47 championofcyrodi is there anything in the fuel logs?
11:49 championofcyrodi i think they would be part of cobbler
11:49 vt102 joined #fuel
11:50 championofcyrodi which has the dhcp udp port open.
11:52 championofcyrodi there should be a DHCPREQUEST and DHCPOFFER ethernet frame going back and forth when the nodes pxe boot.  there are linux tools to listen on ports you can install on a workstation and connect to the switch with a mirrored port.
11:53 homegrown Will have a look at the fuel log in a minute, still think its a driver issue
11:53 homegrown NIC is a X710 (Intel)
11:57 championofcyrodi https://access.redhat.com/articles/1400943
11:57 championofcyrodi i wonder if its supported in centos 6.5
11:57 championofcyrodi which i think is what fuel is using.
11:58 championofcyrodi [root@fuel docker-logs]# cat /etc/redhat-release
11:58 championofcyrodi CentOS release 6.5 (Final)
11:59 homegrown damn
11:59 championofcyrodi http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/ethernet-x710-brief.pdf says its stable on x86-64 Linux kernel 2.6.32/3x
11:59 championofcyrodi so it should work as long as you have the drivers
11:59 evg homegrown: login/pass for bootstrap is root/r00tme
11:59 homegrown thanks :evg
12:00 evg homegrown: just see "ip li li" "dmesg" "lspci"
12:00 homegrown So now the challenge is to get the drivers added to fuel
12:00 evg homegrown: please get sure the kernel module (and firmware if need) are loaded
12:00 championofcyrodi my guess is that you need to find the image served up as the root in cobbler... and update it to include the driver
12:01 championofcyrodi evg is right, use the command "lspci -v | grep Ether"
12:01 championofcyrodi then 'lspci -v -s <slot>' to see the kernel driver in use
12:02 championofcyrodi like so: http://paste.openstack.org/show/201226/
12:04 homegrown Controller shows up as Intel Cor device 1581
12:05 championofcyrodi what does it say to the right of "Kernel driver in use: "
12:05 championofcyrodi or just paste the whole output on paste.openstack.org
12:05 homegrown i only have console access to the machine at the moment
12:07 homegrown no showing "Kernel driver in use:  anywhere
12:07 homegrown stops after Capabilities ..Access Control Services
12:07 evg homegrown: lspci -v
12:08 homegrown Comes back with a pretty long list
12:08 championofcyrodi my guess is that if there is nothing listed for kernel driver in use or for kernel modules, then perhaps there is not an appropriate one installed in the image.
12:09 championofcyrodi in the example i pasted, nx_nic was a module i downloaded from HP's website for the NIC.
12:09 championofcyrodi netxen_nic was one already installed
12:09 homegrown Ah
12:10 homegrown so i'll need to update the cobbler image then
12:10 sc-rm joined #fuel
12:10 homegrown not fun
12:10 championofcyrodi /etc/modprobe.d/blacklist was updated with the 'netxen_nic' driver so that on reboot the 'nx_nic' would be loaded.
12:11 championofcyrodi homegrown: maybe.  I'm not experienced enough to tell you if that is the correct course of action, or if there is an easier way
12:11 evg I haven't got is ethernet UP?
12:11 homegrown nope, just seeing the loopback interface
12:11 championofcyrodi 'cat /sys/class/net/eth0' ?
12:12 evg got it
12:12 championofcyrodi i mean, ls /sys/class/net/eth* ?
12:12 homegrown no such file
12:12 championofcyrodi then there is definitely not a module loaded for it.
12:12 homegrown only lo in /net/
12:13 championofcyrodi so yea, no fitting driver in the pxe image.
12:13 championofcyrodi which is weird i know... because it pxe boots :P
12:13 championofcyrodi yay computers.
12:13 evg do you know which driver sould be used?
12:13 evg should
12:13 championofcyrodi it also may be possible to install the module inside the kernel itself... but that would require a recompile/rebuild i believe, and i've really struggled w/ that.
12:14 championofcyrodi evg: it might have to pulled from intel's site.
12:14 championofcyrodi if it's a NEW nic w/o open source drivers
12:14 homegrown I recall doing this for a dell server with fuel5
12:14 homegrown it wasn't too painful
12:14 homegrown think it was a broadcom card...
12:15 championofcyrodi let me know how it goes. would be curious to know how you resolve it.
12:15 homegrown will do, need to get this resolved .. very expensive paperweight at the moment
12:15 championofcyrodi https://downloadcenter.intel.com/download/24411/Network-Adapter-Driver-for-PCI-E-40-Gigabit-Network-Connections-under-Linux-
12:15 championofcyrodi daaaamn... that is a new driver.
12:15 championofcyrodi (7 days old)
12:16 homegrown that's the badger
12:16 devstok joined #fuel
12:16 championofcyrodi ah, wrong nic
12:16 homegrown server only shipped yesterday
12:16 championofcyrodi wait... it says at the bottom of that link...
12:16 championofcyrodi This download is valid for the product(s) listed below.
12:16 championofcyrodi Intel® Ethernet Controller X710 SeriesIntel® Ethernet Controller XL710 SeriesIntel® Ethernet Converged Network Adapter X710 SeriesIntel® Ethernet Converged Network Adapter XL710 Series
12:17 championofcyrodi yup. 3rd one on this page i think: https://downloadcenter.intel.com/search?keyword=Intel%C2%AE+Ethernet+Controller+X710+Series
12:18 championofcyrodi 40-GbE? that's going to be so fast.
12:18 championofcyrodi evg: know off hand how to clean up remote logs stored on fuel server?
12:19 championofcyrodi and set the threshold back...
12:19 championofcyrodi looking through the ops guide now though..
12:19 championofcyrodi http://docs.mirantis.com/openstack/fuel/fuel-6.0/search.html?q=remote+log&amp;check_keywords=yes&amp;area=default
12:20 evg not sure I got you. cat /dev/null > blahblah.log
12:20 LiJiansheng joined #fuel
12:21 championofcyrodi ah... and set up a cron or something.  got it.
12:21 championofcyrodi thanks
12:21 championofcyrodi in libs like log4j there are config settings the end user can change to set the maximum size logs can grow.  wasnt sure if that was an option here.
12:22 championofcyrodi rotation template looks promising...
12:22 championofcyrodi http://docs.mirantis.com/openstack/fuel/fuel-6.0/operations.html?highlight=logging#fuel-master-node-log-rotation-template
12:24 championofcyrodi huh...
12:24 geta-tn joined #fuel
12:25 championofcyrodi /etc/logrotate.d/10-fuel-docker.conf indicates with the comment that logs shouldnt grow over 30MB... but it uses property 'minsize'
12:25 championofcyrodi and i have remote logs that are growing into GB sizes
12:26 evg championofcyrodi: you can tweak configs in /etc/logrotate.d/
12:26 championofcyrodi [root@fuel node-46.ccri.com]# /etc/cron.daily/logrotate
12:26 championofcyrodi error: 20-fuel-docker.conf:3 duplicate log entry for /var/log/kern.log
12:26 championofcyrodi error: error creating output file /var/log/docker-keystone.log-20150409: File exists
12:27 championofcyrodi i'll try...  but right now its set to 'default settings from installation'
12:27 championofcyrodi pwd
12:27 championofcyrodi oops
12:27 geta-tn Hi all
12:28 geta-tn related to this bug https://bugs.launchpad.net/fuel/+bug/1432656
12:29 geta-tn what if to proceed shutting the fuel interface on the controller avoiding further problems and then adding computes
12:29 geta-tn after the installation i'll modify the /etc/hosts in the controller
12:29 geta-tn could it be the right procedure ??
12:29 championofcyrodi http://www.linuxquestions.org/questions/linux-software-2/logrotate-duplicate-log-entry-problem-853602/
12:30 championofcyrodi reading^ in regard to my issue w/ logrotate
12:32 devstok same issue for us @geta-tn
12:32 devstok please mirantis specialist give an answer
12:34 evg championofcyrodi: really it's a bug
12:34 championofcyrodi apparently running 'logrotate /etc/logrotate.d/20-fuel-docker.conf' works
12:34 championofcyrodi (or is doing something...)
12:34 championofcyrodi still running
12:35 championofcyrodi my /var is @ 100% :(
12:36 evg championofcyrodi: clear it promptly or you've got problems
12:37 championofcyrodi i also seem to have 3 pages of docker images..
12:37 championofcyrodi which are in /var probably
12:37 championofcyrodi oh i've been having problems w/ my fuel server for over a week.
12:38 championofcyrodi filled up i guess, e2fsck reported disk errors, postgres container got unlinked... worked w/ mattymo and got that recovered as sql dumps...
12:38 championofcyrodi today was trying to blow away the postgres container and rebuild it, but var is full again.
12:39 championofcyrodi can i just 'docker rmi' all these fuel 5.0, 5.1 images if i'm using 6.0 images now for running containers?
12:39 championofcyrodi also can i just rm the containers that are label 5.0 and 5.1
12:39 championofcyrodi look at this: http://paste.openstack.org/show/201260/
12:44 championofcyrodi it seems like the real fuel killer is enabling debug logging, which you NEED to debug errors, while logrotation is not set up properly.
12:44 championofcyrodi will result in full disk EVERYTIME
12:46 evg championofcyrodi: yes, you're right. https://bugs.launchpad.net/fuel/6.0.x/+bug/1383741
12:50 samuelBartel joined #fuel
12:50 championofcyrodi Perhaps it would be easier to store remote logs in postgres?
12:50 championofcyrodi but would require UI re-work for logging and all that... blah
12:50 championofcyrodi elasticsearch,logstash,kibana is pretty neat (ELK)
12:51 championofcyrodi probably could generate pretty neat analytics w/ debug logs.
12:52 rkhozinov joined #fuel
12:54 mpaz84 joined #fuel
12:54 championofcyrodi yay got it down to 97%
12:54 evg championofcyrodi: logs in postgres? I don't think so.
12:58 geta-tn can anyone help us with this bug please https://bugs.launchpad.net/fuel/+bug/1432656
12:58 geta-tn we are not able to add compute nodes
13:05 evg geta-tn: the bug is set incomplete. Really more info is required. Was it you who reported it (in irc)?
13:06 geta-tn no i did not report it...but I have the same issue
13:07 evg geta-tn: may be you could help with the bug if you shared your diagnostic shapshot.
13:08 evg geta-tn: it's not clear what's happening
13:09 evg geta-tn: Are registered in launchpad?
13:10 geta-tn you mean the snapshots?
13:11 mattymo championofcyrodi, sorry I was at lunch
13:11 evg geta-tn: yes
13:11 geta-tn no the are not
13:12 geta-tn but i can provide you
13:12 mattymo championofcyrodi, you should rm the containers for fuel-core-5.0-*, then you can delete the images fuel/*_5.0
13:12 championofcyrodi evg: looks like the log rotate script is pointing at /var/log/remote instead of /var/log/docker-logs/remote
13:12 championofcyrodi hey mattymo! just did that a few minutes ago, but only got me 3% disk back...
13:12 evg geta-tn: yes, please. I'll attach it to the bug
13:12 championofcyrodi i just ran: logrotate -d /etc/logrotate.conf
13:13 championofcyrodi and realized that my 1GB + remote log files are not getting rotated out.
13:13 championofcyrodi which is very bad since i'm running debug logging
13:13 mattymo that's a problem..
13:14 geta-tn evg: we cutomized the disk configuration when deployed
13:14 championofcyrodi i believe it is because the path in /etc/logrotate.d/*0-fuel-docker.conf for remote logs is wrong.
13:15 championofcyrodi "/var/log/remote/[1-9]*/*.log" should be "/var/log/docker-logs/remote/[1-9]*/*.log"
13:15 championofcyrodi /var/log/remote is a folder, but it is empty.
13:15 championofcyrodi maybe should be a symlink?
13:15 geta-tn nnow we are adding new compute nodes and fuel recognizes that the configuration of disk - done on install - is different
13:16 geta-tn and if we want to deploy changes - asks for deploying also changes in the controller disks
13:16 mattymo championofcyrodi, yes there should be a symlink from /var/log/remote to /var/log/docker-logs/remote
13:16 mattymo ln -s /var/log/docker-logs/remote /var/log/remote
13:16 mattymo and then try again
13:16 geta-tn maybe it is more clear now to you  :) :)
13:16 championofcyrodi i did... its working... reviewing the output
13:21 championofcyrodi it's a lot of output going to stdout and grep doesnt seem to be working properly... just re-ran the logrotate /etc/logrotate.d/20-fuel-docker.conf
13:21 championofcyrodi and now i'm waiting.
13:30 championofcyrodi heh... still waiting.
13:32 championofcyrodi but it's working... i'm seeing .1 files showing up in the remote log folders..
13:33 rkhozinov joined #fuel
13:36 evg geta-tn: sorry, nope.
13:37 evg geta-tn: you've cutomized the disks, then you deployed.
13:37 geta-tn exactly
13:37 evg geta-tn: all was ok.
13:37 geta-tn all was fine
13:37 geta-tn but now when we want to add one compute for example
13:37 evg geta-tn: then you added additional compute
13:38 geta-tn nope
13:38 geta-tn just the initial ones...
13:38 geta-tn now we eant to add new computes
13:38 evg geta-tn: and?
13:39 geta-tn we want to add new computes...but fuel finds out that the config of the disks are not the default ones some way
13:39 evg geta-tn: yes
13:40 geta-tn and is not asking only to deploy the new nodes but also to deploy the disk changes
13:41 geta-tn tahts why i was asking if by shutting the fuel interface on the controller we can avoid further problems and then adding computes
13:41 geta-tn and then change the /etc/hosts/
13:41 geta-tn in the controller
13:42 sc-rm evg: After deployment of juno using ubuntu I’m not able to boot the instances with getting network access, the healt check fails because the instances does not get any network up
13:42 geta-tn can it be a possible pocedure ??
13:42 sc-rm evg: And Hi by the way :-)
13:44 evg sc-rm: Hi, sorry let me 7 min...
13:45 sc-rm evg: If you have time tomorrow, we could look at it there. I’ll try to redeploy the stack.
13:45 evg geta-tn: I think I should try to reproduce it my myself
13:46 geta-tn i see
13:46 geta-tn yeah  it can be great and very helpful for us
13:47 evg geta-tn: what do you mean "shutting the fuel interface on the controller"?
13:48 geta-tn the interface of the fuel network...so cannot deploy any change
13:49 evg geta-tn: NIC in pxe network? How it can help?
13:50 geta-tn so fuel cannot deploy any disk change on the controllers
13:54 geta-tn evg: thanks a lot for your help
13:55 evg geta-tn: aaa, fuel tries to redeploy controllers?
13:55 geta-tn exactly
13:56 championofcyrodi glad i've identified what is taking up space and probably killing my containers.
13:56 championofcyrodi YAY for more cloud stability
13:56 evg geta-tn: thanks. I've got you. I'll try to reproduce.
13:57 championofcyrodi meanwhile... it looks like one of our AWS instances has been compromised and performing DDoS attacks using QUIC (http://en.wikipedia.org/wiki/QUIC)
13:58 geta-tn evg: thank you a lot
14:02 vt102 joined #fuel
14:03 evg geta-tn: you can try to provision/deploy this compute via cli. Not sure this workaroud works, but may be...
14:03 evg geta-tn: fuel --node-id XX --env XXX --provision; fuel --node-id XX --env XXX --deploy
14:04 geta-tn okkk...will try
14:04 evg geta-tn: no, sorry. unlikely it works...
14:05 geta-tn you think no ??
14:06 evg geta-tn: unlikely :( Let me reproduce
14:06 geta-tn okkk thnx
14:06 evg geta-tn: do you use 5.1.1 too?
14:07 geta-tn yess
14:11 evg sc-rm: "Check network connectivity from instance via floating IP" failed? Have you got other errors? Have you ran "network veryfication"?
14:12 vt102 joined #fuel
14:18 vt102 joined #fuel
14:20 rongze joined #fuel
14:46 julien_ZTE joined #fuel
14:55 emagana joined #fuel
15:20 kozhukalov joined #fuel
15:28 daniel3_ joined #fuel
15:29 daniel3_ joined #fuel
15:34 julien_ZTE joined #fuel
15:56 MiroslavAnashkin geta-tn: The message in the UI is confusing. Fuel only wants to add your new node to /etc/hosts on the already existing nodes. However, for additional safety, you may run `chmod -x /usr/bin/puppet` on the already deployed nodes, you want to preserve from any changes.
15:58 tzn joined #fuel
16:00 daniel3_ joined #fuel
16:01 mpaz84 joined #fuel
16:09 rongze joined #fuel
17:38 emagana joined #fuel
17:44 Guest58 joined #fuel
17:53 e0ne joined #fuel
17:56 rongze joined #fuel
19:00 dmitryme left #fuel
19:10 e0ne joined #fuel
19:23 [HeOS] joined #fuel
19:42 tzn joined #fuel
19:44 championofcyrodi am i just starting the container wrong???
19:44 championofcyrodi http://paste.openstack.org/show/201491/
19:45 championofcyrodi it doesnt seem to ever get past verifying the connection is up.
19:45 championofcyrodi bbf4d1f72f2e        fuel/postgres_6.0:latest        /usr/local/bin/start   41 minutes ago      Up 41 minutes               10.20.0.2:5432->5432/tcp, 127.0.0.1:5432->5432/tcp
19:46 championofcyrodi that is the output from docker ps -a...
19:46 championofcyrodi so its mapped correctly.
19:46 championofcyrodi my guess is postgres isnt actually listening properly
19:46 championofcyrodi or on the proper interface, or something.
19:48 championofcyrodi seeing this in the log...
19:48 championofcyrodi < 2015-04-09 20:06:14.755 BST >FATAL:  password authentication failed for user "nailgun"
19:48 championofcyrodi < 2015-04-09 20:06:14.755 BST >DETAIL:  Connection matched pg_hba.conf line 26: "host   all     all     0.0.0.0/0       md5     "
19:48 championofcyrodi then after a while: < 2015-04-09 20:06:15.457 BST >LOG:  received SIGHUP, reloading configuration files
19:49 championofcyrodi followed by the same password authentication failed for user "nailgun" message...
19:49 championofcyrodi so it seems that the password being used is not the same...
19:51 championofcyrodi /etc/nailgun/version.yaml showing version=5.0 :\
19:52 championofcyrodi even though i think it should be 6.0
19:53 kybe Hey guys. Is Fuel 6.1 going to offer OpenStack Kilo on Ubuntu 14.04?
19:55 championofcyrodi homegrown/evg: https://bugs.launchpad.net/fuel/+bug/1411289
19:55 championofcyrodi kybe: i think kilo is going to be openstack 7.0, thus fuel 7.0
19:55 kybe championofcyrodi: thanks!
19:58 thumpba joined #fuel
19:58 rongze joined #fuel
19:59 thumpba_ joined #fuel
20:08 kybe Is there a fuel command that displays the nodes and their 10.20.0.* ip?
20:10 kybe ah, found it. :)
20:23 homegrown joined #fuel
20:29 championofcyrodi HOLY MACKRAL!!!
20:29 championofcyrodi mattymo! I got my postgres instance restored!!!
20:29 championofcyrodi so even though the dockerctl start postgres kept reporting timeout...
20:42 e0ne joined #fuel
20:51 mattgriffin joined #fuel
20:51 MiroslavAnashkin kybe: No, 7.0 offers Kilo. 6.1 offers the latest Icehouse, with Ubuntu 14.04, if I remember correct
20:58 kybe MiroslavAnashkin: I think 6.0 has Juno already, so 6.1 will probably have that too?
20:59 rongze joined #fuel
21:06 emagana joined #fuel
21:38 LiJiansheng joined #fuel
22:33 emagana joined #fuel
22:35 emagana_ joined #fuel
22:45 emagana joined #fuel
23:01 rongze joined #fuel
23:06 thumpba joined #fuel
23:34 tzn joined #fuel
23:34 thumpba_ joined #fuel
23:54 julien_ZTE joined #fuel

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