Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel-dev, 2015-08-27

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

All times shown according to UTC.

Time Nick Message
00:00 sylwesterB joined #fuel-dev
00:03 dkusidlo joined #fuel-dev
00:41 asd112z joined #fuel-dev
00:47 xarses joined #fuel-dev
01:08 xarses_ joined #fuel-dev
01:45 dims joined #fuel-dev
01:49 sylwesterB joined #fuel-dev
03:22 tzn joined #fuel-dev
03:23 _tzn joined #fuel-dev
03:38 sylwesterB joined #fuel-dev
04:25 agordeev joined #fuel-dev
04:44 sylwesterB joined #fuel-dev
04:45 tzn joined #fuel-dev
05:08 xarses_ joined #fuel-dev
05:12 xarses joined #fuel-dev
05:28 zerda joined #fuel-dev
05:37 stamak joined #fuel-dev
05:46 dims joined #fuel-dev
05:49 enikanorov joined #fuel-dev
06:03 salmon_ joined #fuel-dev
06:16 pradip joined #fuel-dev
06:20 pradip hi all, i want to run my plugins in sequence , what the changes i need to do..??
06:26 samuelBartel joined #fuel-dev
06:31 alex_bh joined #fuel-dev
06:39 mkwiek joined #fuel-dev
06:39 xarses_ joined #fuel-dev
06:46 tzn joined #fuel-dev
07:08 hyperbaba joined #fuel-dev
07:17 e0ne joined #fuel-dev
07:18 amnk joined #fuel-dev
07:29 evgenyl pradip: what do you mean by "in sequence"?
07:35 dims joined #fuel-dev
07:53 stamak joined #fuel-dev
07:53 MPBNKA joined #fuel-dev
08:00 ekosareva joined #fuel-dev
08:08 salmon_ joined #fuel-dev
08:09 adanin joined #fuel-dev
08:20 akislitsky_ joined #fuel-dev
08:20 akislitsky__ joined #fuel-dev
08:26 JoeStack joined #fuel-dev
08:47 HeOS joined #fuel-dev
08:48 tzn joined #fuel-dev
08:59 e0ne joined #fuel-dev
09:10 stamak joined #fuel-dev
09:18 tzn joined #fuel-dev
09:23 dkusidlo joined #fuel-dev
09:24 tzn joined #fuel-dev
09:50 dims joined #fuel-dev
10:13 dstepanenko left #fuel-dev
10:25 tzn joined #fuel-dev
10:34 salmon_ joined #fuel-dev
10:35 monester joined #fuel-dev
10:36 dkusidlo joined #fuel-dev
10:53 adanin joined #fuel-dev
11:03 romcheg vkramskikh: Hi
11:03 romcheg around?
11:26 tzn joined #fuel-dev
11:27 agordeev joined #fuel-dev
11:27 IvanKliuk_ joined #fuel-dev
11:31 dkusidlo joined #fuel-dev
11:38 warpc__ joined #fuel-dev
11:51 kozhukalov_ joined #fuel-dev
11:51 evgenyl joined #fuel-dev
12:04 ekosareva joined #fuel-dev
12:05 zigo vkramskikh: Hey, do you know how to fix this one? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795032
12:26 pradip_ joined #fuel-dev
12:27 tzn joined #fuel-dev
12:28 amnk joined #fuel-dev
12:29 dims joined #fuel-dev
12:43 amnk joined #fuel-dev
12:44 e0ne joined #fuel-dev
14:27 pradip joined #fuel-dev
14:28 tzn joined #fuel-dev
14:30 angdraug joined #fuel-dev
14:50 pradip joined #fuel-dev
14:51 dims joined #fuel-dev
14:55 jaypipes joined #fuel-dev
15:09 vitaly1 joined #fuel-dev
15:10 vkramskikh romcheg: hi, yep
15:11 vkramskikh zigo: hi, nope, and don't even have idea why you're asking me :)
15:11 romcheg vkramskikh: I found a strange behavior of the UI
15:11 romcheg lemme find the screenshot pls
15:12 romcheg vkramskikh: http://cl.ly/image/381o21050I2p
15:13 romcheg Notice that two lines are red but one is green
15:13 vkramskikh so that's the only strange thing? :)
15:14 vkramskikh well, it's representation of network error from the very beginning - it means that some part of network config is wrong
15:14 vkramskikh you mean it should be totally red?
15:29 tzn joined #fuel-dev
15:33 rmoe joined #fuel-dev
15:48 romcheg1 joined #fuel-dev
15:59 IBerezovskiy joined #fuel-dev
16:09 sylwesterB joined #fuel-dev
16:20 tzn joined #fuel-dev
16:50 teran joined #fuel-dev
16:54 xarses_ joined #fuel-dev
17:00 romcheg1 joined #fuel-dev
17:27 rgowrishankar Hello, I see existing code in the fuel library l23network module that supports linux bonding as well as OVS Bonding.. Just want to confirm that the linux bonding model will continued to be supported..
17:28 tzn joined #fuel-dev
17:30 tzn joined #fuel-dev
17:31 angdraug rgowrishankar: yes
17:31 rgowrishankar angdraug: thanks
17:32 rgowrishankar Another question, Is there a 7.0 example plugin that makes use of the role as a plugin feature?
17:37 barthalion rgowrishankar: I guess it's https://github.com/stackforge/fuel-plugin-detach-keystone + detach-rabbitmq + detach-database
17:42 amnk joined #fuel-dev
17:44 bdudko joined #fuel-dev
17:45 e0ne joined #fuel-dev
17:47 amnk joined #fuel-dev
17:53 rgowrishankar barthalion: Ok, thanks will take a look..
17:57 sylwesterB joined #fuel-dev
18:00 kozhukalov Guys, could I suggest a feature for 8.0? As a user I'd like to have mature image management functionality in nailgun (thus in UI/CLI). The feature is to list available images, make it possible to look at images metadata (including the list of installed packages), assign available images for clusters and as a bootstrap ramdisk, maybe upload custom images, definitely build images (setting the list of necessary packages).
18:00 kozhukalov what do you think?
18:05 xarses joined #fuel-dev
18:05 mwhahaha sounds really complex, are there people asking for this?  what exactly would having this feature solve?
18:10 ogelbukh sounds like glance to me :)
18:10 ogelbukh or maybe even murano
18:11 ogelbukh as a 'global catalog'
18:29 Samos123 joined #fuel-dev
18:35 kozhukalov mwhahaha, sure it does. first we build new image every time we deploy new cluster, and we don't have functionality to find out if it is really necessary, if we just can re-use one of available images. second, currently we use the default  list of packages that are to be installed into an image. nailgun just does not care of this. third, what if a user needs per node/per role images? if we have such a feature (image management) it is
18:35 kozhukalov easy to implement per node assignment. forth, per role/per node partitioning. currently we have per node partitions (but only those which are not os related). anyway you can not make /usr a separate file system on one node in a cluster and make it a part of root file system on another node. fifth, it could be just another step forward in making fuel even more flexible and attractive for potential users.
18:38 mwhahaha Yea i can see the advantages for some of this things, specifically file system layouts.
18:38 kozhukalov ogelbukh, yes, you are right, and we only could easily adopt openstack services to do things for fuel, It would be great. But in my experience even adopting ironic as a provisioning tool is not so easy
18:38 mwhahaha I don't see the point of custom software package installation as that should be handled post install of the image
18:38 mwhahaha unless it's something like custom kernel/driver
18:38 kozhukalov s/we only could/if we only could/
18:40 kozhukalov mwhahaha, yes, it could be custom kernel, custom set of modules, custom puppet, custom mcollective, custom bootloader. see for example https://github.com/stackforge/fuel-agent/blob/master/fuel_agent/drivers/nailgun.py#L602-L644
18:40 ogelbukh well, glance is relatively simple service
18:41 ogelbukh much simplier then ironic
18:41 mwhahaha Glance would just be one piece of what he's proposing as you still need to build the images and ship them to glance
18:42 ogelbukh right
18:42 mwhahaha but rather than building our own service to host the images, leveraging glance similar to our keystone usage on the fuel master might save some time
18:42 * ogelbukh looks at the document named 'image builder as a service' in his google drive
18:44 ogelbukh https://blueprints.launchpad.net/tripleo/+spec/tripleo-image-building-api
18:44 mwhahaha Honestly i think 8.0 would be a bit aggressive unless there's already most of this work done somewhere.  Personally, i'd rather see more time devoted to splitting up the roles we have to do to allow more finer control over placement on hosts and allow for easier creation of new roles to solve the software install part
18:45 mwhahaha and perhaps opening up the custom kernel/driver part of our existing image building to make deployer's lives easier on different types of hardware
18:49 angdraug joined #fuel-dev
18:50 kozhukalov yet another thing is building bootstrap image, currently we build centos based bootstrap together with ISO and experimental ubuntu bootstrap during master node deployment. Apparently, user might want to rebuild bootstrap image from time to time  for example to include necessary modules there to make it possible to discover some new hardware
18:51 tzn joined #fuel-dev
18:55 mwhahaha i would also like to point out the issues people currently have with being able to create just one image (and deploy) with the existing system when they don't have direct internet access. i'm not sure people would really want to do this multiple times or try and do it with custom packages/dependencies
19:31 HeOS joined #fuel-dev
19:32 neophy joined #fuel-dev
19:37 bdudko joined #fuel-dev
19:37 e0ne joined #fuel-dev
19:38 nurla joined #fuel-dev
19:46 sylwesterB joined #fuel-dev
19:52 akasatkin joined #fuel-dev
21:04 angdraug xarses: https://review.openstack.org/217790
21:05 angdraug I don't know enough about granular to answer mwhahaha's question, can you have a look?
21:24 xarses angdraug: reviewed and annotated
21:25 angdraug thanks!
21:27 romcheg1 left #fuel-dev
21:35 sylwesterB joined #fuel-dev
22:09 tzn joined #fuel-dev
22:10 adanin joined #fuel-dev
23:18 dims_ joined #fuel-dev
23:24 sylwesterB joined #fuel-dev
23:29 nurla joined #fuel-dev
23:41 xarses_ joined #fuel-dev
23:56 tzn joined #fuel-dev

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