08:00:18 #startmeeting daisycloud 08:00:19 Meeting started Fri Aug 12 08:00:18 2016 UTC and is due to finish in 60 minutes. The chair is huzhj. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:23 The meeting name has been set to 'daisycloud' 08:00:37 #topic Roll Call 08:00:51 #info kongwei 08:01:05 #info Zhijiang 08:02:32 aha, only a few people 08:03:06 @kongwei , please take the chair for a while for me, I will BRB in minutes. 08:03:15 ok 08:06:06 #info luyao 08:06:18 hi 08:07:18 hi 08:08:37 #info sunjing 08:09:58 #topic the first release 08:10:31 I am back 08:10:37 #topic Daisy Demo and doc 08:10:42 ok 08:11:39 Seems I should fire a spcific command something like chair... to give chair to other, otherwise, only I can issue command like topic... 08:11:50 we will get a demo version 08:12:02 yes 08:12:17 i can not change topic 08:13:17 #info we have athe demo version online for donload 08:13:22 #undo 08:13:24 Removing item from minutes: 08:13:42 #info we have athe demo version online for public download 08:14:34 welcome zhuzeyu 08:14:45 thank you 08:14:55 #link http://www.daisycloud.org/static/files/installdaisy_el7_noarch.bin 08:15:35 great 08:15:47 good 08:16:24 #this is only a demo version which do not support barematel discovery currently , user must install OS on all to-be-deplyed hosts before hand 08:16:34 #info this is only a demo version which do not support barematel discovery currently , user must install OS on all to-be-deplyed hosts before hand 08:17:16 #info The corresponding document will avaliable next week 08:18:11 great 08:19:42 #info Zhijiang will send email to OpenStack and OPNFV to announce the release event 08:20:19 #topic Ironic status update 08:20:53 @luyao anything intresting about ironic from your side? 08:22:07 I am studying how deploy os with ironic。 08:22:24 #info Daisy uses ironic as the baremetal discovery and OS ochestrating tool 08:23:14 Good! 08:23:24 maybe we should add ironic interface to fullfill the fuction of deploy centos 08:23:35 #info Yao will work on ironic related things 08:24:55 Hope the latest version of the ironic meets our requirements 08:25:21 yes 08:27:01 I do not know if there is any website which publish the detail changelog of ironic from K to Mitaka. We need do some research on the changelog to find out which new things can benifit us 08:27:27 only a hope :0 08:27:30 : 08:27:33 :) 08:27:46 yes 08:28:01 We can check ironic no of new version. 08:28:18 ironic bp 08:29:05 As we know there are some other projects like what we are doing. They are trying to use ironic to deploy OS. 08:30:14 OK, if no further progress to report about ironic , we's better go to the next topic 08:30:26 #topic Get backend type by calling host_get_all function 08:30:31 you mean we can learn from them? 08:30:41 Yes @zhouya 08:30:56 If M can not fullfill our need,we can add new interface to do it 08:31:10 Yes, agree @luyao 08:31:11 OK 08:31:49 #info Julien 08:32:05 OK, @zhouya so you are working one the host_get_all() function rectifing? 08:32:13 yes 08:32:16 we 08:32:41 What do you think about the idea of providing bakcend info through that API? 08:32:53 I add a interface in host-detail 08:32:53 welcome julien 08:32:58 Is it a correct way we should go ? 08:33:15 welcome Julien-zte 08:33:31 Hi @ChrisPriceAB_ and Hi @Julien-zte 08:33:31 welcome julien 08:33:32 I think it's the right thing we should do 08:33:35 huzhj you can use chair command to let other has the priority 08:33:52 welcome 08:34:02 welcome 08:34:04 Yes Julien, thanks 08:34:11 thanks everyone 08:34:44 what's current topic 08:35:00 Get backend type by calling host_get_all function? 08:35:12 About How to identify backend in our code. 08:35:14 yes 08:35:21 what's the backend? 08:35:47 the backend of kolla,tecs and zenic 08:35:55 As you know, we will suport alot of disctrbuted system to deploy, we call each of them as a specific backend 08:36:15 distribution is more fit :) 08:36:25 yep :) 08:36:31 and I will still work on the code of multi backend type 08:36:49 great 08:37:11 whtat distribution does we expect to support? centos , ubuntu? and other? 08:37:27 we expect all of them :) 08:37:44 in the next release, I do think centos + ubuntu is enough 08:37:48 and now is CentOS 08:37:50 we have just released the demo for centos7 08:37:52 even we can choose only one 08:38:12 where can I check / download the demo? 08:38:36 http://www.daisycloud.org/static/files/installdaisy_el7_noarch.bin 08:38:43 www.daisycloud.org 08:38:45 That is the previrous topic 08:39:01 It will ben meaningful in OPNFV, for we can support multiple release version. currently in OPNFV, one installer choose only distribution 08:39:07 The related document will be avaliable next week. 08:39:11 Ubuntu is mostly used. 08:39:22 Acctually I can send the doc offline to you 08:39:43 Yes. 08:39:46 fantastic 08:39:53 thanks huzhj 08:40:06 at your service:) 08:40:27 So can we move to next topic now? 08:40:38 ok 08:40:40 OK 08:40:43 #info Ya will work on the host_get_all rectify things 08:40:56 @topic Related status update 08:41:01 sorry 08:41:10 #topic Daisy4nfv Related status update 08:42:30 I discussed with @kongwei about the relationship between escalator and installer 08:43:13 We also realized that Escalator may need to be located at the north bond of VNFM 08:43:27 such as tacker or something 08:44:42 Because when you do upgrading , there may a sequencial activities among escalator , VNFM and the installer 08:45:51 First, escalator call into VNFM to let it to do VM change over, then, escalator call installer to do upgrading 08:46:20 So we can treate escalator as the very top level scheduler 08:46:23 includes the installer itself? 08:46:33 may be @zhouya 08:47:04 fantastic 08:47:06 At the summit, I declared a so called DaaS modle 08:47:26 maybe we will have some integration with tacker 08:48:11 in this release, we can mainly focus on implementation of Daisy and documents/or basic support of escalator 08:48:20 can we support them both in Release D? 08:48:28 Agree, But now I did not dive so deep into VNFM 08:48:37 I'm think of over workload 08:48:55 team in Shanghai can give some assistance 08:49:13 we are formiliar with MANO including VNFM 08:49:30 Greate, that will be so great:) 08:49:41 not familiar with Tacker 08:49:59 but mayny a new team member is good at tacker 08:50:11 mayny -> maybe 08:50:57 let's push forward these items. 08:51:21 #info huzhj, I think we'd better use jira.opnfv.org to manage our requirements 08:51:33 I hope we need more concentration on the relationship between escalator and installer , thus, do not think of vm change over things, that may be more easily for us to finish in release D 08:51:41 then anyone can check our working items 08:51:57 @julien-zte will do that 08:52:23 can not get it for " do not think of vm change over things" 08:52:23 #info Zhijiang will update work items for opnfv in jira 08:52:37 change info to action 08:52:46 #undo 08:52:47 Removing item from minutes: 08:52:54 #action Zhijiang will update work items for opnfv in jira 08:53:58 I mean as the frist phase , let just simply do not care about vm change over, os that there is no need for escalator to talk to VNFM 08:54:47 and I think , if we do not upgrade some critical service such as libvert. then there is also no need to do VM change over 08:55:18 sorry, what is "VM change over" ? 08:55:20 migration? 08:55:27 but taht is really a small , non common upgrade use case :) 08:55:47 Not migration exactly 08:55:58 I mean the HA change over 08:56:02 no background information 08:56:11 Let discuss it offline 08:56:14 OK? 08:56:14 can I check these states in some docs? 08:56:20 good 08:56:40 I think @kongwei are working on a document on that 08:57:13 no questions for this 08:57:34 #info Wei is working on a document about more detail upgrading requirements for escalator 08:57:47 yes 08:57:50 great 08:58:23 anything for daisy4nfv? 08:58:55 Oh , just FYI , the meeting log and minutes link can be found at https://wiki.opnfv.org/display/meetings/Meetings 08:59:43 #info the meeting log and minutes link can be found at https://wiki.opnfv.org/display/meetings/Meetings 09:00:01 ok,thank s~ 09:00:52 Get it 09:01:16 seems we have finished with all topics. anything intresting before call it a meeting :) 09:02:20 do we have some docs about opnfv? 09:02:22 intresting -> interesting 09:02:57 some docs for on boarding? 09:03:38 learn about esclastor 09:04:01 escalator 09:04:01 basically they are all located at http://artifacts.opnfv.org/opnfvdocs 09:04:37 OK,it will be a great help 09:04:38 but the url redirect to google storage ... 09:04:52 not easy to get 09:04:59 :( 09:05:14 OK,I see 09:05:15 you can also check out the wiki.opnfv.org 09:05:26 thank you 09:05:54 there are quiet a lot description about projects on their man page. 09:06:17 got it 09:06:44 for escalator https://wiki.opnfv.org/display/escalator 09:07:21 wow we are running out of time 09:07:33 :) 09:07:39 let's call it a meeting 09:07:44 yes 09:07:47 bye 09:07:48 ok 09:07:52 bye 09:07:54 bye 09:07:56 bye 09:08:01 have a good weekend 09:08:07 #endmeeting