Friday, 2016-01-15

*** tzn has joined #openstack-bareon00:26
*** tzn has quit IRC01:01
*** tzn has joined #openstack-bareon02:58
*** tzn has quit IRC03:03
*** tzn has joined #openstack-bareon03:59
*** tzn has quit IRC04:04
*** tzn has joined #openstack-bareon05:00
*** tzn has quit IRC05:04
*** tzn has joined #openstack-bareon06:00
*** tzn has quit IRC06:05
*** tzn has joined #openstack-bareon07:01
*** tzn has quit IRC07:06
*** tzn has joined #openstack-bareon08:02
*** tzn has quit IRC08:07
*** sylwesterB has joined #openstack-bareon08:08
*** sylwesterB has quit IRC08:10
*** sylwesterB has joined #openstack-bareon08:10
sylwesterBmorning ;)08:16
evgenylsylwesterB: morning :)08:38
*** tzn has joined #openstack-bareon09:03
*** tzn has quit IRC09:08
sylwesterBin ideal world, all direct calls to volume_manager should be removed from nailgun09:13
evgenylsylwesterB: yes :D09:13
sylwesterBit's to much work for just recording a Demo09:13
evgenylsylwesterB: what is the plan do you have on problem with get_volume_blha method which is not implemented in bareon extension?09:14
sylwesterBthere are IMO 3 ways of resolving the issue09:15
sylwesterB1. put this specific data into bareon-api, create method get_node_volumes and then volume_manager can be safely removed.09:16
sylwesterB2. make more direct calls to volume_manager instead of invoking 'node_extension_call'09:17
sylwesterB3. do not remove volume_manager from extensions for the demo (which is the worst I think)09:17
sylwesterBevgenyl: do you see any other solutions?09:17
*** tzn has joined #openstack-bareon09:18
evgenylsylwesterB: I think 1st is the best. But it somehow should implement interface, so serializer won't fail.09:19
*** tzn has quit IRC09:20
evgenylsylwesterB: I mean it should return a list of volumes.09:20
*** tzn has joined #openstack-bareon09:21
evgenylsylwesterB: But ideally I think we will have to implement this logic in a part, where (in the future) you introduce ability for extensions to change deployment/provisioning data.09:22
evgenylsylwesterB: so for now make it not to fail09:23
sylwesterBevgenyl: look https://review.openstack.org/#/c/250864/5/nailgun/nailgun/extensions/bareon/extension.py here in :37 I also use volume_manager but as a part of 'Node' model09:26
sylwesterBI can do the same with 'volumes'. Put this data to bareon-api, create new method in extension "get_node_volumes" and it will work for sure09:28
sylwesterBis that ok?09:28
evgenylRegarding to your link, we will need to implement it in node adaptor of bareon-extension, copy-paste if will be required.09:29
evgenylHm, let me think.09:29
evgenylsylwesterB: It's not going to be good even for the demo. Can you try to make a list out of data from bareon? How hard is it to make simple convertation?09:32
sylwesterBlet me check09:33
sylwesterBok09:50
sylwesterBthere are 2 ways I think:09:50
*** tzn has quit IRC09:50
sylwesterB1. https://review.openstack.org/#/c/250864/5/nailgun/nailgun/extensions/bareon/extension.py here I do "disk.pop('volumes')". Without it 'get_node_volumes' can be done easily and it should work... The only place I can have some doubts is that one: https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/orchestrator/deployment_serializers.py#L545-L552 because I don't what is that data used for later...09:55
sylwesterB2. convert the hardcoded partitioning data. For example to count number of glance number i would need to parse somehow the 'device' field "/dev/mapper/image-glance"09:57
evgenylsylwesterB: they are trying to find volume group with specific name10:01
evgenylhttps://github.com/openstack/fuel-library/blob/master/deployment/puppet/osnailyfacter/lib/puppet/parser/functions/get_disks_list_by_role.rb#L1610:01
evgenylSo lets try 1st.10:02
sylwesterBok, let's try10:03
evgenylsylwesterB: basically what you are doing now is not just "a demo", you are finding the problems which we will face to very early, so the entire thing will not look like "a simple task with no problems".10:05
sylwesterByep, you're right10:06
sylwesterBthere should be a task to remove all direct volume_manager calls in one of the specs10:07
sylwesterBwhat do you think?10:07
evgenylsylwesterB: yes, correct, basically there is going to be a spec on changing of serialized data, where we will be able to remove glance_blha calculation, similar call will be for ceph.10:11
sylwesterByou're talking about the one with so called 'data pipelines' ?10:12
evgenylsylwesterB: Yeah, with this thing, extension will be able to do additional searilization, which is specific for volumes.10:14
sylwesterBok10:15
*** tzn has joined #openstack-bareon11:19
sylwesterBevgenyl: deployment succeed11:24
sylwesterBwith the option 1.11:24
sylwesterBwith disabled volume_manager extension for cluster11:25
evgenylsylwesterB: nice11:25
sylwesterBso I will now build custom iso and finally record it ;)11:25
*** openstackgerrit has quit IRC12:50
*** openstackgerrit has joined #openstack-bareon12:50
*** sylwesterB has quit IRC15:39
*** tzn has quit IRC17:12
*** tzn has joined #openstack-bareon19:07
*** tzn has quit IRC19:13
*** tzn has joined #openstack-bareon19:28
*** tzn has quit IRC20:18

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!