14:00:19 #startmeeting watcher 14:00:20 Meeting started Wed Mar 22 14:00:19 2017 UTC and is due to finish in 60 minutes. The chair is alexchadin. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:23 The meeting name has been set to 'watcher' 14:00:38 Hi Watcher folks! 14:00:40 o/ 14:00:44 o/ 14:00:48 hi 14:00:50 o/ 14:01:17 #info Today we have the following agenda https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#02.2F15.2F2016 14:01:34 #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#03.2F22.2F2017 14:01:49 #topic Announcements 14:01:55 Due to time changes the next meeting will be one hour later than usually. 14:02:10 Yayy :) 14:02:14 so be prepared next time ;) 14:02:26 ok 14:02:27 alexchadin: depends on the country though :p 14:02:47 alexchadin: not for people in the US though 14:02:54 vincentfrancoise: yeah, it is applicable only for time-change countries :) 14:03:15 :) just wanted to pshedimb to not be late 14:03:17 alexchadin: even worse not all country change time on the same day... 14:03:34 sballe_, haha :) 14:03:48 we have a lot of discussions today so I'd like to start with them 14:03:57 #topic Open discussions 14:04:04 Python 3.5 Support – it is one of the main goals for Pike cycle and we need to meet completion criteria. 14:04:09 #link https://governance.openstack.org/tc/goals/pike/python35.html 14:04:50 we have unit test gates for both 2.7 and 3.5 - it is great! 14:04:57 alexchadin: so after a quick read it means we need to have both unit tests **and** tempest test to pass with py35 14:05:15 but our functional tests works only with 2.7 14:05:28 so yes, vincentfrancoise +1, we need functional gate for 3.5 14:05:56 alexchadin: I reckon they work with py34 (I checked once like 3-4 months ago) 14:06:30 vincentfrancoise: if so, I believe they will work great with 3.5 14:06:40 alexchadin: regarding tempest tests, they are really flaky these days so before getting them onto py35, we also need to spend time stabilizing them 14:07:31 vincentfrancoise: we need to define what we want from functional tests and set boundaries 14:07:52 vincentfrancoise: the situation with "one more blueprint" ;) 14:08:10 hi sorry to be late 14:08:14 hi acabot 14:08:15 alexchadin: all api tests + the dummy strategy end2end execution 14:08:29 vincentfrancoise: +1 14:08:37 who would like to take it? 14:08:53 I suppose we need some sort of spec here 14:10:01 which would define what tests we actually need 14:11:30 well, I will add it to my TODO's and assign it later 14:11:37 move on 14:11:45 WSGI Support. Does our API work with WSGI? #link https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html#watcher 14:12:42 alexchadin: our API stack is the same as magnum and ironic so if it works for them then we should be OK 14:13:21 alexchadin: I will go through as many of the spec as i can review. based ont hese minutes 14:13:43 vincentfrancoise: there are status of projects: https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html#current-state-anticipated-impact 14:13:52 sballe_: thank you! 14:14:25 alexchadin: yes but the remaining steps can be copied from ironic then 14:14:57 alexchadin: https://github.com/openstack/ironic/blob/master/ironic/api/app.wsgi seems like one of the main difference we don't have 14:15:11 as it is one of the main goals for Pike cycle, it would be great to take it now 14:16:06 alexchadin: I can take it 14:16:59 adisky_: thanks! 14:17:14 :) 14:17:18 #action adisky_ update WSGI status of Watcher 14:17:36 Watcher is not presented in Debian-based systems due to issue. It would be great to build package by ourselves. #link http://lists.openstack.org/pipermail/openstack-dev/2017-February/112220.html 14:18:32 the main problem here is that zigo lost his contract with Mirantis, so there is no one who can hold it 14:19:26 adisky_ said that we are not presented in Debian repos for Ocata release 14:19:59 There's no Ocata release in Debian *at all*. 14:20:15 Hopefully, this may change though ... 14:20:16 Here is page https://openstack.alioth.debian.org that explains packaging process 14:20:29 hi, zigo! 14:20:41 No, this is old, and doesn't take into account the fact we're now packaging on OpenStack infra. 14:21:37 zigo: could you please give us some information about building and releasing Watcher for Debian? 14:22:19 alexchadin: We need to first get a Stretch image into OpenStack infra, which I have been working on, then all of the rest of OpenStack needs to get packaged (oslo, etc.). 14:22:49 All is done through Gerrit these days. 14:22:57 zigo: is there some docs with first steps? 14:22:58 So just openstack/deb-watcher... 14:23:34 alexchadin: Basically, it's fix the issues with openstack-infra/project-config stuff. ie: ./tools/build-image.sh 14:23:41 Currently, it fails. 14:23:47 I'm not sure why yet... 14:23:51 Help would be appreciated. 14:24:01 It's been 1 week I'm on that already, and can't find what's going on. 14:24:11 Probably something with Puppet 4 instead of 3. 14:24:44 Running ./tools/build-image.sh with these variables: 14:24:54 export DIB_RELEASE="stretch" 14:24:54 export DIB_DEBOOTSTRAP_EXTRA_ARGS=--include=systemd-sysv 14:24:54 export DISTRO=debian-minimal 14:24:54 export DISTRO_NAME=debian 14:24:54 export CONFIG_REF=refs/changes/13/445813/4 14:25:02 then fix the problems. 14:25:19 zigo: thank you. can we discuss it in our main channel, openstack-watcher? 14:25:43 Sure ! Feel free to discuss that Stretch issue on #openstack-infra or even #openstack-pkg if you like too. 14:25:50 zigo: great! 14:26:08 Once that's done, I believe I can release Ocata quite fast. 14:26:20 #action continue discussion with zigo about building Watcher for Ocata 14:26:27 move on 14:26:30 adisky reported that python-watcherclient is not included in rdo repo of python-openstackclient. 14:27:12 alexchadin: correction there is no rpm package of python-watcherclient 14:27:50 we have rpm packages available for watcher, but not for watcher-client 14:28:46 number80 is the nick behind all RDO stuff. 14:28:47 so i am unable to complete installation guide for rdo 14:28:49 Chat with him ... 14:29:06 adisky_: can you resolve this issue? 14:29:08 zigo: thanks :) 14:29:48 alexchadin: yes i will 14:30:42 #action adisky_ contact number80 to resolve rpm-issue 14:31:16 #topic Review Action Items 14:31:20 Watcher 14:31:29 Versioned Notifications for service object needs reviews #link https://review.openstack.org/#/c/437333/ 14:32:36 who would like to review it? 14:32:38 +1 14:32:55 +1 14:32:56 it isn't big patch 14:33:08 thanks chrisspencer_ vincentfrancoise 14:33:21 #action chrisspencer_ vincentfrancoise review https://review.openstack.org/#/c/437333/ 14:33:31 Add Gnocchi datasource needs final core reviews #link https://review.openstack.org/#/c/438530/ 14:34:00 hello 14:34:09 hi sanfern 14:34:20 hi 14:34:52 I can't just +2 on my patch :) 14:35:06 vincentfrancoise: will you take a look? 14:35:08 +1 14:35:38 pshedimb: thanks 14:35:40 alexchadin: on this one there were comments you didn't answer 14:35:59 vincentfrancoise: ah sure 14:36:00 alexchadin: so I remember I was waiting for you to answer before putting a +2 14:36:39 alexchadin: once you do, I'll review it once more 14:36:41 #action vincentfrancoise pshedimb review https://review.openstack.org/#/c/438530/ when alexchadin update it 14:36:57 Added suspended audit state needs reviews #link https://review.openstack.org/#/c/438800/ 14:37:29 alexchadin, also gnocchi is moving out of openstack. will it affect the patch? 14:38:21 pshedimb: I've seen this thread and they promise that there won't be any changes for projects which use it 14:38:33 alexchadin, okay :) 14:38:56 pshedimb: alexchadin what about gnocchi moving out? can I have a link about this? 14:39:21 pshedimb: they will have changes with CI, but should remain OpenStack support 14:39:25 vincentfrancoise: let me find 14:39:34 vincentfrancoise, https://review.openstack.org/#/c/447438/ 14:39:46 vincentfrancoise, Gnocchi guys submitted request to OpenStack congress to move out of openstack 14:39:47 vincentfrancoise: http://lists.openstack.org/pipermail/openstack-dev/2017-March/114300.html 14:40:51 Maybe we should do the same down the line if we want to support other eco-system than openstack... Not now but just food for thoughts 14:40:52 pshedimb: although there were some opinions that they are more OpenStack-related than they thought 14:40:53 they just want to leave the big tent 14:41:22 it doesn't mean it will not work with openstack anymore 14:41:32 alexchadin: pshedimb: so that means there is won't be any openstack-tagged telemetry project anymore 14:41:33 acabot: I agree 14:41:42 vincentfrancoise: yeap 14:41:58 how about Monasca they claim to do it all 14:42:05 vincentfrancoise, alexchadin Ceilometer is still there 14:42:15 The main component of telemetry 14:42:20 pshedimb: ceilometer doesn't have API 14:42:21 pshedimb: but witth no supported APIS 14:42:27 alexchadin: lol 14:42:39 pshedimb: high five!:D 14:42:44 alexchadin sballe_ , yeah we gotta use backend like mongodb 14:42:55 haha :D 14:43:17 indfluxDb is better for the stuff we are lookign at doing anywau 14:43:22 Gnocchi is just a backend. So any other backend like Mongo or HBase will work just fine. 14:43:22 s/anyway 14:43:24 which is why Watcher should definitely be datasource agnostic as much as possible 14:43:25 pshedimb: gnocchi works perfectly as API for Ceilometer 14:43:43 alexchadin, Yeah I agree. 14:44:47 let's leave this discussion for main channel 14:44:53 +1 14:44:55 +1 14:44:56 we have only 15 minutes left 14:44:57 +1 14:44:59 move on 14:45:00 Prevent the migration of VM with 'optimize' False in VM metadata needs new PS 14:45:08 #link https://review.openstack.org/#/c/443070/ 14:45:29 pksingh is not here 14:45:39 alexchadin: I discussed this with him 14:45:43 vincentfrancoise: +1 14:45:47 vincentfrancoise: I've seen it 14:46:13 vincentfrancoise: Have you got some conclusion? 14:46:17 alexchadin: basically, the code made me realise there was another issue with the nova metadata representation 14:46:45 alexchadin: we have an XML reprenstation to declare scenarios 14:47:15 alexchadin: this is a declarative/human readable system to make it easy in tests 14:47:52 vincentfrancoise: is it applicable only for basic_consolidation strategy? 14:47:57 alexchadin: but the metadata breaks it (or at least the test do not pass because dicts are unordered so we cannot dafely bootstrap) 14:48:10 safely* 14:48:52 Hello 14:48:53 alexchadin: so we need to ensure that we can test the model which contains json 14:49:01 pksingh: hi 14:49:18 vincentfrancoise: Hi 14:49:28 alexchadin: before we can carry on with what pksingh was actually trying to do in the first place 14:49:48 #action vincentfrancoise and pksingh work together on https://review.openstack.org/#/c/443070/ 14:49:52 alexchadin: does that make sense? 14:50:03 vincentfrancoise: yeah 14:50:13 alexchadin: good :) 14:50:19 Adding tempest test that executes outlet_temp_control strategy. needs reviews #link https://review.openstack.org/#/c/439184/ 14:50:50 +1 14:51:11 #action pshedimb review https://review.openstack.org/#/c/439184/ 14:51:37 Reduced the code complexity needs new PS #link https://review.openstack.org/#/c/441873/ 14:52:31 stale the action plan needs final core reviews #link https://review.openstack.org/#/c/440927/ 14:52:58 I will review it, who else? 14:53:39 #action alexchadin review https://review.openstack.org/#/c/440927/ 14:53:51 Add gnocchi support in basic_consolidation strategy needs reviews #link https://review.openstack.org/#/c/440293/ 14:54:25 +1 14:54:30 sanfern provided new PS yesterday, let's review it 14:54:58 #action chrisspencer_ alexchadin review https://review.openstack.org/#/c/440293/ 14:55:18 exception when running 'watcher service list' needs reviews #link https://review.openstack.org/#/c/447354/ 14:55:40 +1 14:55:46 I have a question here: is it good pattern to have one named hosts? 14:56:27 same named* 14:57:23 alexchadin: I guess no, but sometimes legcy bites... 14:58:04 vincentfrancoise: well, let's ask licanwei about it 14:58:24 #action alexchadin put some comments on https://review.openstack.org/#/c/447354/ 14:58:33 we have only 2 minutes left 14:59:00 no time left for specs :-D 14:59:01 Don't forget there are 5 specs which are waiting for your reviews 14:59:25 acabot: unfortunately... 14:59:41 well, thank you for your attention 14:59:53 bye everyone 15:00:05 bye 15:00:09 bye 15:00:14 bye 15:00:19 bye 15:00:19 bye 15:00:21 bye 15:00:24 bye 15:00:28 #endmeeting