13:02:05 #startmeeting hyper-v 13:02:06 Meeting started Wed Aug 17 13:02:05 2016 UTC and is due to finish in 60 minutes. The chair is claudiub|2. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:10 The meeting name has been set to 'hyper_v' 13:03:47 Hi 13:04:47 Hi 13:04:56 hello 13:05:16 hello 13:05:32 hm, there's a storm here in romania 13:05:40 keep getting disconnected 13:06:27 and I won't be able to change topics now. :( 13:06:38 since the chair was registered as claudiub|2 13:06:48 no problem 13:06:55 we can start 13:07:20 hm, this should work I think 13:07:43 so, first of all, there aren't many updates, since most of our team is on vacation 13:07:49 #topic monasca status 13:07:55 yeay, it works 13:08:03 so, i've rebased the patches again 13:08:24 Roland knows about them, he mentioned them in last week's meeting too 13:08:25 claudiub: i saw your mail to monasca team 13:08:43 i think Roland is on vacation for some days 13:08:58 and he said that he's going to take a look at them, and push the other cores towards reviewing them as well 13:09:14 yeah, I guess it is to be expected, as it is summer. :) 13:09:28 anyways, I am actually wondering 13:09:42 based on your mail which you send today to monasca core reviewers.. i expect the reviews to start soon 13:09:43 from what I can see, at least on devstack, monasca uses a virtual env 13:09:56 maybe you can still use newton monasca in mitaka 13:10:05 sagar_nikam: can you folks give it a try? 13:10:39 claudiub: we can try... but i think in last IRC you mentioned it may not be possible 13:10:52 too many code changes 13:10:56 as far as I know, it pretty much depends only on keystone 13:10:59 is what you mentioned last week 13:11:30 sagar_nikam: yeah, cherry-picking it might be impossible, but I meant to just take the whole newton branch of monasca 13:11:30 hey guys 13:11:33 and just monasca 13:11:53 you mean copy paste the code ? 13:12:03 which code.. only hyperv ? 13:12:11 or all monasca ? 13:12:33 just clone monasca-agent and install it on windows / hyper-v nodes 13:12:44 ok 13:12:49 sagar_nikam: I assume you already have monasca runnng in your env, right? 13:13:03 claudiub: yes we have 13:13:07 monasca in our ev 13:13:09 env 13:13:22 so this is what needs to be done... correct it some steps are incorrect 13:13:39 create a mitaka controller where monasca is also available 13:13:49 yeah. I think it's worth a try, to clone the monasca-agent on a windows node, get the patches that are on review, and give it a try 13:13:54 then add hyperv host with nova and neutron 13:14:17 sagar_nikam: yep 13:14:24 on the same host, git clone monasca-agent and run setup.py 13:14:31 it will install monasca-agent 13:14:37 and now start the agent 13:14:43 are these steps correct ? 13:14:46 yeah, don't forget the patches that I've sent. 13:14:52 otherwise the agent won't start 13:14:53 ok 13:15:00 and what about the conf file 13:15:12 do you have any conf file for monasca on hyperv 13:15:13 ? 13:15:27 just a sec 13:16:39 this is the conf i'm currently using: 13:16:49 #link monasca-agent.conf http://paste.openstack.org/show/559024/ 13:17:52 ok let me try 13:18:00 also, regarding on how monasca-agent works: you will have to have a check.d folder, in the same folder as your monasca-agent.conf file 13:18:12 in it, you'll have the conf files for each checker you want to run 13:18:30 i was told earlier by somebody who had worked on monasca,, that the monasca-agent will not start on windows... i think your patches fix it... am i right ? 13:18:57 sagar_nikam: yep. it isn't starting because monasca-agent tries to hook an event listener for a linux specific signal 13:19:31 and your code fixed it by .... making it windows specific if running on windows ? 13:19:45 anyways, I think it would be better to take a look at the monasca conf files you have in your monasca controller in your env 13:20:01 it should also have the checker.d files you'll need 13:20:20 ok 13:20:23 let me try 13:20:43 sagar_nikam: one of the patches i've submitted just skips setting that event listener on windows 13:21:03 that patch has 2x +2s 13:21:24 what about package compilation in windows... running setup.py.. does it work cleanly... all dependent packaes get compiled in windows ? 13:22:30 actually not sure about that. but at least most of the packages you should have already, if you have nova / neutron running on that node 13:22:43 ok ... good... then we are fine 13:22:53 let me know if there's an issue regarding setup 13:23:01 since we are able to get nova and neutron compiled in windows 13:23:09 one more question 13:23:27 2 +2s is on only 1 patch or more patches ? 13:23:48 only on 1 patch 13:24:49 k, moving on 13:25:00 #topic neutron port migration 13:25:11 sagar_nikam: soo, any news about this? 13:25:32 did you folks get to test if this works? 13:29:59 so, i take it as no news 13:30:16 anyways, if it doesn't work, I think it would be worth a try cold migration too 13:32:07 well, I don't have any other comments for now 13:32:15 #topic open discussion 13:32:46 will close the meeting if there's nothing else to be discussed 13:35:14 hi 13:36:10 hello 13:36:18 you got disconnected. :) 13:36:40 #undo 13:36:41 Removing item from minutes: 13:37:29 so, before you got disconnected, I asked this: neutron port migration: sagar_nikam: soo, any news about this? did you folks get to test if this works? 13:37:31 no problem 13:37:57 claudiub|2 just sent a mail to sonu and vinod 13:38:07 asking them about it 13:38:14 you are in the mail 13:38:20 oh, cool. :) 13:38:31 and if it doesn't work, I think it would be worth a try cold migration too. maybe at least that works 13:39:03 ok 13:39:13 can we try this in mitaka ? 13:39:20 we dont have newton yet 13:39:32 yeah, I think it's worth a try 13:40:05 ok 13:40:50 #topic open discussions 13:41:45 so, anything to add here? 13:42:08 no ... nothing as of now 13:42:39 well, i think we can end it here for now 13:42:53 if there are no more topics 13:44:02 yes .. sure 13:44:07 we can close early 13:44:09 well then, thanks for joining, see you next week! :) 13:44:14 thanks 13:44:17 #endmeeting