Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2015-06-24

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

All times shown according to UTC.

Time Nick Message
00:03 dhblaz joined #fuel
00:50 n3m8tz joined #fuel
00:57 dhblaz joined #fuel
01:10 xarses joined #fuel
01:28 LiJiansheng joined #fuel
01:40 dhblaz joined #fuel
02:52 Longgeek_ joined #fuel
02:53 Longgeek joined #fuel
02:55 Longgeek joined #fuel
02:59 Longgeek_ joined #fuel
03:04 Longgeek joined #fuel
03:23 Longgeek joined #fuel
03:34 claflico joined #fuel
03:37 Longgeek joined #fuel
03:42 Longgeek_ joined #fuel
03:43 Longgee__ joined #fuel
03:48 Longgeek joined #fuel
04:12 Longgeek joined #fuel
05:27 LiJiansheng joined #fuel
05:38 drifterza joined #fuel
06:03 ub joined #fuel
06:07 e0ne joined #fuel
06:17 fedexo joined #fuel
06:19 drifterza1 joined #fuel
06:24 e0ne joined #fuel
06:36 moquist joined #fuel
06:45 e0ne joined #fuel
07:04 Satya joined #fuel
07:07 Satya left #fuel
07:16 saibarspeis joined #fuel
07:19 samuelBartel joined #fuel
07:21 dancn joined #fuel
07:53 hyperbaba joined #fuel
07:54 baloney joined #fuel
08:25 e0ne joined #fuel
08:31 monester_laptop joined #fuel
08:31 drifterza joined #fuel
08:40 e0ne joined #fuel
08:40 saibarspeis joined #fuel
09:20 baloney joined #fuel
09:22 hyperbaba Hi there, I have a question. Let's presume that i have initial hardware for cloud deployment (using fuel 5.1.1), and fuel does the discovery of the machine resources. The system is put into production. Because we use ceph we had to add additional disks into servers and add them to ceph manually using ceph-deploy. The fuel is totally agnostic on the resource changes for that nodes. If i have to redeploy the node those additional resources are still not g
09:22 hyperbaba oing to be detected.
09:41 drifterza1 joined #fuel
09:41 drifterza1 left #fuel
09:43 obcecado joined #fuel
09:46 e0ne joined #fuel
09:47 pbrooko joined #fuel
10:18 ddmitriev joined #fuel
11:57 xdeller joined #fuel
12:19 baloney joined #fuel
12:50 championofcyrodi joined #fuel
12:51 pbrooko joined #fuel
12:53 dhblaz joined #fuel
13:42 kaliya joined #fuel
14:16 rmoe joined #fuel
14:45 baloney joined #fuel
14:50 claflico joined #fuel
15:21 Samos123 is there a torrent link for MOS 6.1? getting corrupted files the whole time, gotta love China's firewall
15:21 Samos123 official release
15:24 MiroslavAnashkin It is possible to download only community 6.1 builds via torrent.
15:43 baloney joined #fuel
16:03 baloney joined #fuel
16:15 xarses joined #fuel
16:33 v1k0d3n joined #fuel
16:34 v1k0d3n hey everyone, have a question for installing fuel. during the install it always says the static ip address i am using is taken. am i doing something wrong?
16:37 v1k0d3n it also complains about PXE every time...
16:52 dontalton joined #fuel
16:57 magicrobotmonkey left #fuel
17:25 v1k0d3n is anyone even in this chan?
17:29 MiroslavAnashkin What is Fuel version? And are you install it to bare-metal or to virtual machine?
18:01 e0ne joined #fuel
19:31 ub joined #fuel
19:33 e0ne joined #fuel
19:59 n3m8tz joined #fuel
20:06 v1k0d3n man, so sorry i missed this. i have tried 6 and 7 newest builds (7 nightly). trying to get kilo support because of docker capabilities.
20:06 v1k0d3n and vm.
20:07 v1k0d3n MiroslavAnashkin: sorry for the late response...have been working and client was in teh background
20:29 xarses v1k0d3n: Kilo is not in the 7x builds yet
20:30 xarses eta is end of june , so next week
20:33 DrSlump Is there a way to ensure Admin (PXE) is not eth0 for MOS 6.1? In fuelmenu, it's set to eth2 but on the web UI, all nodes have Admin on eth0.
20:39 v1k0d3n xarses: ah...ok. was reading through docs and said that it was supposed to be in 7, right? i assumed that the work was being build into the nightly's for 7...so this is my error.
20:40 v1k0d3n thank you for that update! this makes sense now.
20:40 xarses v1k0d3n: it will be in 7, its not in the nightly yet because it's failing CI still
20:42 v1k0d3n yeah, that makes much better sense now. thank you for clearing that up...i missed it while reading up on fuel.
20:43 xarses DrSlump: the Admin (PXE) network selection on the nodes you are deploying is done 1) the lowest interface with an DHCP address that matches the same network as the fuel-master nodes PXE settings (from fuel-menu) or 2) the interface with the default gateway if 1 is not met
20:44 xarses DrSlump: this means that on the nodes you want to provision eth0 can reach the fuel node, or it was the only interface that received an IP address. if this is the only interface that has this access, the logical interface name (eth0) ordered differently than another OS (which happens)
20:44 xarses v1k0d3n: we likely didn't make it very obvious that the kilo packages aren't in yet
20:46 v1k0d3n xarses: i wasn't going to be the one to say it :) hey, there's a lot of work in fuel...i'm glad i came to the chan to ask though. i would still be scratching my head over it.
20:46 v1k0d3n is fuel typically a version or two back?
20:48 monester_laptop joined #fuel
20:49 xarses v1k0d3n: the major version releases will match the next version of OpenStack. We try to release a couple of months after the OpenStack release. This is the first one that is this far out. It might indicate a change in that behavior. It's unknown yet
20:50 DrSlump and kilo just came out last month so i wasn't expecting it
21:09 Longgeek joined #fuel
21:12 championofcyrodi i'm still learning the issues w/ ceph+block device cinder volume issues.  https://ask.openstack.org/en/question/68838/cinder-multi-backend-ceph-with-block-device-support/
21:13 championofcyrodi looks like i'll need to start a cinder-volume service on the actual compute node in which the device volumes reside.
22:11 Longgeek joined #fuel
22:38 ub joined #fuel
22:57 n3m8tz joined #fuel
23:00 n3m8tz joined #fuel
23:31 rmoe joined #fuel
23:33 claflico joined #fuel
23:35 xarses joined #fuel
23:52 claflico joined #fuel

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