16:00:02 #startmeeting watcher 16:00:03 Meeting started Wed Oct 21 16:00:02 2015 UTC and is due to finish in 60 minutes. The chair is acabot. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:08 The meeting name has been set to 'watcher' 16:00:17 hi 16:00:52 Hi 16:00:58 hi 16:01:02 hello 16:01:19 o/ 16:01:36 o/ 16:01:41 o/ 16:01:47 our meeting agenda #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda 16:02:46 acabot: ready... thanks for sending the email out 16:02:49 hi 16:02:57 ok lets start with announcements 16:03:09 #topics announcements 16:03:20 #topic announcements 16:04:09 I'd like to introduce vincentfrancoise who is joining our watcher-drivers team 16:04:24 cool! 16:04:28 welcome :) 16:04:46 vincentfrancoise: are you from b-com? 16:05:10 Yeah I'm from b-com :) 16:05:11 howdy vincentfrancoise 16:05:34 welcome 16:05:41 vincentfrancoise has been working on our metering chain for 3 months now and will jump on Watcher core components now 16:05:49 acabot: do we need to add vincent into Launchpad "watcher drivers" team ? 16:06:07 dtardivel_: yes please do 16:06:26 vincentfrancoise: welcome aboard 16:06:44 #action dtardivel_ add vincentfrancoise in watcher drivers 16:07:00 any other annoucement ? 16:07:19 acabot: nothing here - ready for actions 16:07:33 jwcroppe: ok 16:07:45 #topic Review Action Items 16:08:29 mailing to the community has been sent today 16:08:36 saw that - thanks 16:08:49 yeah that was great! 16:08:49 we already have an answer from a ceilometer contributor 16:09:28 http://lists.openstack.org/pipermail/openstack-dev/2015-October/077627.html 16:09:39 yep, will be good to continue socializing Watcher 16:09:55 I think we should definitely add Watcher to https://wiki.openstack.org/wiki/Ceilometer#Ceilometer_Extensions 16:10:01 +1 16:10:04 also we need to look opnfv and the doctor project so we have an answer to the quesiton how is wathcer different from doctor 16:10:11 acabot: +1 16:10:46 #link https://wiki.opnfv.org/doctor 16:11:32 sballe: they look to be quite different - we can add this to Wiki FAQ 16:12:01 #action acabot sballe look at opnfv doctor project before the summit 16:12:07 jwcroppe: yes and no. I think we just need to have a written down answer around why they are different 16:12:17 sballe: +1 16:12:24 sballe: +1 16:13:18 "The goal of this project is to build fault management and maintenance framework for high availability of Network Services on top of virtualized infrastructure" ... I think the core missions are different. We can get pen to paper on that. 16:13:26 doctor is not part of openstack so even if its close, they can live in both openstack and opnfv 16:14:05 agree with both of you. We just need to make sure we understand the difference 16:14:07 opnfv is deeply related to NFV and I think we do not want to address this right now in Watcher 16:14:42 acabot: +1 ... we've got the action above to write that down, next topic? 16:14:47 the question is doctor going ot be a sub-set of watcher? 16:14:56 jwcroppe: +1 16:15:08 +1 16:15:10 a) Scheduled evacuation and Live migration would be considered to be actions to move VM from faulty host. If VM does not want to support this, no action. 16:16:03 jed56: This could sound like watcher as well 16:16:13 yes you can see that here https://wiki.opnfv.org/_media/doctor-opnfv-proposal.pptx 16:16:51 as stated we will have a deeper look at it before the summit 16:16:53 but that's an aspect of live migration in general 16:16:58 I propose that we do some research on this and start compiling notes and write some notes 16:17:01 seems like the difference is fault tolerance vs optimization, two kind of related but not quite the same goals 16:17:04 before summit 16:17:22 jwcroppe: yes I believe that is the action above 16:17:28 sballe: agree 16:17:30 lets move to stackforge code migration 16:17:39 tpeoples i agree 16:17:42 so did it happen? 16:17:48 the stackforge migration/ 16:18:01 watcher and python-watchercient projects have migrated to openstack namespace 16:18:07 +1 16:18:28 dtardivel_: assume we also need watcher-specs created ? 16:18:40 but there is an issue on watcher project, due to bad oslo config version used 16:18:58 tpeoples: +1, watcher would be doing fault tolerance moves as well? 16:19:08 we alreay fixed this issue internaly 16:19:36 we are waiting for a core review for watcher-specs 16:19:48 We will put a patch before the summit in order to finalize the migration 16:19:52 can you send us the review 16:20:14 jed56: sounds good - do we have our core names loaded into specs and watcher-core ? 16:20:50 yes : https://review.openstack.org/#/c/233679/ 16:20:53 thx 16:21:09 sballe: yes of course 16:21:15 the document was not always clear between openstack and stackforge 16:21:17 jed56: IIRC, for watcher-specs it was sballe, acabot and jwcroppe? For watcher-core it was jed56, dtardivel_ and tpeoples, correct? 16:21:33 wznoinsk: i don't think that is something we would try to handle with the first iteration of watcher, but it is something we can discuss and keep in mind. you could think of "faults" as just some other stat that could reach a threshold to be optimized, so the framework watcher provides should allow that in the future 16:21:59 jwcroppe: jed56 is talking about creating the watcher-specs repo 16:22:19 jwcroppe: as it is still in review, we cannot add contributors yet 16:22:30 acabot: +1 16:22:47 tpeoples: yes, optimization is one thing and fault tolerance is another, it tend to treat tehse two separate, we can take any discussion off-meeting/in open discussion part ... 16:22:53 tpeoples: we will be looking at sla and risk minization so we will be looking at risk for component failure after our initial poc around nergy comsumption 16:22:55 acabot: I think watcher-core should be ready, correct? 16:24:43 jwcroppe: today watcher-core is the watcher-drivers team 16:25:15 jwcroppe: we are still waiting for watcher-specs creation to start a dedicated launchpad with contributors 16:25:24 ok, sounds good 16:25:30 jwcroppe: if its needed 16:27:20 we also add a github repo for watcher toold 16:27:22 tools 16:27:30 helping people deploying Watcher 16:27:44 #link https://github.com/b-com/watcher-tools 16:28:05 we are internaly on review on docker part 16:28:36 we will push also ansible playbook later (before the summit I hope) 16:28:43 acabot: yeah I started doing the deploy the otehr day. Still working at it. 16:28:47 acabot: yeah and hopefully watcher can easily build on devstack as well (eventually) 16:29:06 I have devstack deployed and was tryingot get watcher to work. 16:29:22 I could use some more documentation :-) 16:29:52 sballe: code == documentation ;-) 16:29:58 just kidding - agree 16:30:07 sballe: I think we will do it together next week and will improve doc as well 16:30:22 please wait for next commit on docker part, because we updated container images (located on dicker hub), and we need to update documentation as well 16:31:19 for information we use gerrithub.io for reviews on this project 16:31:21 acabot: ok, so sounds like progress has been made on the repos 16:31:37 acabot: and we just need watcher-specs to complete review 16:32:11 jwcroppe: I think everything will be OK before Tokyo 16:32:50 sounds good - shall we move on 16:32:51 ? 16:32:58 +1 16:32:58 yes Tokyo agenda 16:33:18 sballe sent us an invit for tuesday morning 16:33:30 yes let me know if you need to be added 16:33:47 it is Tuesday at 10:45 during the coffee break 16:33:50 acabot: I started working on a doc I'd like to discuss when we get there with the team... it's not complete, but it will get the discussion going 16:33:52 #link https://docs.google.com/document/d/1xcLQY6532Ed2FS2_6d4s6CF4ijeTqr43k5GMSurFepM/edit#heading=h.vae16077waj6 16:34:26 wznoinsk: do you want to join ? 16:34:33 ok. Should we add all our session to our wiki? I am assuming we can't add them to the official list 16:35:03 sballe: yes, thanks 16:35:38 the doc I was using a 'scratch pad' of some thoughts we should explore during the PoC phase - with the goal of making things as simple as possible and start getting the framework built out 16:35:39 done 16:35:50 I think we can add them here https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads 16:36:03 ok let's do thta 16:36:27 so I will add the tuesday session but we still have a problem with rooms for next days 16:36:38 acabot: jwcroppe Do tou know who Federico Michele Facca is? 16:36:51 sballe: no 16:37:11 sballe: that's a new name t me 16:37:20 sballe: yes sorry I met Federico at a conference on Monday and he is looking at Watcher 16:37:27 ok 16:37:32 cool 16:37:59 acabot: So we have our first meeting setup by sballe, but we should carve out some other focused design slots 16:38:00 #action acabot add watcher session to https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads 16:38:02 acabot: do oyu remember the name of the oher intel person that was interested in joining? 16:38:42 sballe: isnt it wznoinsk ? 16:39:09 no but I think I can find her name 16:39:54 sballe: oh yes sorry Mrittika Ganguli 16:40:08 yes taht was it. I will invite her too 16:40:36 jwcroppe: +1 but we still have a problem with rooms, we should probably define on our tuesday meeting the next design slots 16:41:31 everyone is OK with groupme ? 16:42:08 feel free to invite people tot he GroupMe app 16:42:14 yep 16:42:17 ok 16:42:23 acabot: yeah, I'm not sure if we'll get a room this summit - we might have to take over some corners or some such :) 16:42:55 jwcroppe: so we will ;-) 16:42:56 +1 16:43:05 jwcroppe: next to the coffee machine please 16:43:24 Last year a lot of the LBaaS/FWaas discussions happened in the hallway on chairs 16:43:29 acabot: +1 16:43:30 acabot: +1 16:43:32 during breaks the booths on the corridors are usually busy but we can try to use one of them (with couches) 16:43:41 ok lets move to our last topic 16:43:43 wznoinsk: +1 16:43:51 #topic open discussions 16:44:07 Just a reminder: Can people please sign in to GroupMe? 16:44:10 if people get a chance - take a look at the google doc I started above. it's very rough admittedly, but it's a good straw man for some discussion 16:44:38 jwcroppe: ok I will do it in the plane ;-) 16:44:42 jwcroppe: i will 16:44:58 cool 16:45:24 and yes - to echo sballe - join GroupMe :) 16:46:23 OK can we close our meeting and just say see you in Tokyo ? 16:46:32 sounds good to me 16:46:37 Sounds like a plan 16:46:51 bye 16:46:52 safe travels 16:46:52 #endmeeting