Earlier  
Posted Nick Remark
#openstack-nova - 2018-03-05
14:36:00 Spazmotic Welcome home PTG
14:36:03 Spazmotic Been lonely in here :D
14:45:48 Spazmotic I'm an amateur photographer, if you're interested in seeing my 6 favorite photos while I was in Korea. Feel free to take a look :) https://500px.com/brookskaminski/galleries/korea -- Time for me to hit the shops.
15:02:18 openstackgerrit Matt Riedemann proposed openstack/nova master: Migrate tempest-dsvm-cells job to an in-tree job definition https://review.openstack.org/549780
15:13:50 hrw http://marcin.juszkiewicz.com.pl/2018/03/05/snowstack-in-dublin/
15:14:02 stephenfin sean-k-m1: Afternoon. You about? Fancy looking at https://review.openstack.org/#/c/546588/ again?
15:18:37 mriedem hrw: "Some time later hotel staff created a separate wireless network for our use." i didn't know about that
15:18:52 mriedem i had just given up
15:18:55 hrw mriedem: info was on #openstack-ptg
15:19:03 hrw mriedem: did not changed much anyway imho
15:21:42 mriedem Spazmotic: nice pictures; would like to vacation there some day
15:37:53 openstackgerrit Matt Riedemann proposed openstack/nova master: Make nova-cells-v1 run with neutron https://review.openstack.org/549789
15:39:49 roedie Hi all, I have an issue where an instance seems to be missing some network info. When running 'openstack server list' I don't see any network info for this instance. But when looking in Horizon I do see the network. I thought heal_instance_info_cache would fix this, but it does not. Anyone got an idea?
15:40:08 stephenfin mriedem: Dumb question time: I thought cells v1 wasn't compatible with nova-network and that that was the main reason for keeping nova-network around?
15:40:15 stephenfin *wasn't compatible with neutron
15:40:46 mriedem stephenfin: depends on what you mean by compatible
15:40:53 stephenfin There was something about...Ebay (?) having custom patches to fix that but they wasn't upstream
15:41:10 mriedem there are certain things in the upstream nova code with cells v1 that don't work with neutron, the main one being the cells v1 api doesn't plumb through vif plug events from neutron
15:41:30 mriedem all cells v1 deployments are running with patches
15:41:38 mriedem godaddy and nectar run with neutron+ovs,
15:41:44 mriedem cern runs with nova-net but they are moving over to neutron
15:41:57 mriedem i think tssurya said cern is now 1/3 nova-net still
15:42:17 mriedem i have no idea about ebay or paypal or walmart since they don't work upstream
15:42:39 stephenfin It may have been GoDaddy actually.
15:42:47 stephenfin "Acme large user of OpenStack"
15:43:01 mriedem anyway, as discussed at the ptg, we can make the cells v1 job run on neutron (probably handicapped a bit) but we can't start nova-net w/o cells v1
15:43:07 mriedem so the order of removal is nova-net and then cells v1
15:43:42 stephenfin Yup, that all makes sense. It was that bit of info (what didn't work with neutron) that I was after
15:44:24 mriedem i expect i'll have to blacklist a bunch of tests, and/or make the job non-voting before we can merge that patch
15:46:32 stephenfin Makes sense
15:46:33 stephenfin I never caught up with mordred to talk about the zuulv3 native rework of those either :( Hopefully he's free some time next week once I've POCd some of the NUMA-aware vSwitch stuff
15:46:47 jgriffith mriedem: hey.. well that's up to you. I was going to try and finish it up this morning, but I'm certainly always open to help if it's something you want to work on.
15:46:58 mriedem stephenfin: i would put zuulv3 native rework of nova CI jobs way way down on the priority list
15:47:07 jgriffith mriedem: if you're just giving me a vote of "no confidence" well.. then.. uuummm..
15:47:10 jgriffith ok
15:47:13 jgriffith :)
15:47:15 mriedem stephenfin: since 98% of nova people don't know how to maintain CI jobs, less zuulv3 native
15:47:32 mriedem jgriffith: heh, no, just didn't know how busy you were
15:47:43 mriedem jgriffith: figured this might be pro bono work for you
15:47:47 jgriffith mriedem: crazy busy, but I do plan to work it today
15:48:01 jgriffith mriedem: I could use your help on the policy piece though
15:48:10 stephenfin mriedem: I'd figured they should be easier to write and maintain. Also, it scratches a personal itch (I want to know how this stuff works). Much lower priority than the NUMA vSwitch stuff though, yes
15:48:21 stephenfin *should* :)
15:48:25 mriedem jgriffith: ok i rambled a lot in the comments, but i think you just need to use the volume api to get the volume details and then use the attachments to get the servers to count things
15:48:35 mriedem jgriffith: don't think we need to worry about any policy stuff
15:48:47 mriedem jgriffith: we should be able to figure this out w/o relying on config changes
15:48:53 jgriffith I saw this morning, need to go through your latest notes.
15:49:13 mriedem stephenfin: the legacy d-g job defs are very easy to write and maintain IMO
15:49:26 mriedem especially for people that have known how the CI framework has worked for the last 8 years
15:49:34 jgriffith mriedem: ok, let me have a look at what you added and go from there. If it ends up I can't figure out a solution I'm happy for you to hack on it or just get your help on enlightening me :)
15:49:48 mriedem jgriffith: ack
15:50:29 stephenfin mriedem: Good to note. I was starting from scratch there so it was all new
15:51:35 jgriffith mriedem: oh! You added the user-context addition! That's perfect
15:52:00 mriedem jgriffith: yup so we should be able to hit the volume API from the virt driver
15:52:01 jgriffith Tjat
15:52:12 jgriffith That's what I meant when I said policy changes by the way
15:52:17 mriedem ok i figured
15:52:24 jgriffith perfect.. I'll roll on it and get somethign up before lunch
15:52:25 jgriffith thanks!
15:52:29 mriedem yw
16:10:15 openstackgerrit Merged openstack/nova master: Updated from global requirements https://review.openstack.org/549694
16:29:53 stephenfin yes
16:29:59 stephenfin whoops
16:42:21 openstackgerrit Balazs Gibizer proposed openstack/nova master: Fix the notification devref location in exception https://review.openstack.org/549816
16:46:43 hrw hm. patches...
16:47:19 hrw https://review.openstack.org/#/c/545034/ awaits for someone brave to give +w+2 to my pcie ports patch
16:56:21 gibi mriedem, Kevin_Zheng: fyi, I proposed the bp to add request_id to the instance action notification: https://blueprints.launchpad.net/nova/+spec/add-request-id-to-instance-action-notifications
16:57:25 mriedem gibi: cool, thanks - do you plan on getting 'formal' approval in the nova team meeting this week?
16:57:32 mriedem mel is on vacation this week btw
16:57:49 mriedem although we already discussed it in person,
16:57:49 gibi mriedem: sure, I will bring it up on the meeting
16:57:54 mriedem so likely not really needed
16:58:12 gibi it doesn't hurt
16:59:02 mriedem i've approved it
16:59:43 gibi mriedem: thanks
17:00:08 gibi mriedem: if you are interested in a bit heavier read then I also reworked the minimum bandwidth support spec during the weekend based on the PTG discussion https://review.openstack.org/#/c/502306/
17:00:35 mriedem omg
17:00:41 mriedem i don't think i can handle that kind of weight right now
17:01:37 gibi mriedem: no problem. I agree that this is not good read for the first day after PTG
17:02:41 openstackgerrit Matt Riedemann proposed openstack/nova master: DNM: Test nova-api eventlet deprecation https://review.openstack.org/549770
17:03:01 mriedem gibi: thanks for taking that on though, i'm glad you're owning it
17:03:31 gibi mriedem: yeah, my employer is pushing me to take it seriously
17:04:10 mriedem my employer also cares about it, but i haven't been physically kicked yet
17:04:36 mriedem it will be easier to kick Kevin_Zheng
17:04:40 gibi mriedem: mlavalle seems interested too and If I know correctly you two have the same employer
17:04:45 mriedem yup
17:05:44 mlavalle gibi: yes, I am interested. Will push it from the Neutron side
17:05:47 stephenfin mriedem: What needs to happen to move this forward now? https://review.openstack.org/#/c/483994
17:06:55 gibi mlavalle: thanks! I think when you read the nova spec you will find couple of thing that needs to be discussed on the neutron side
17:06:59 mriedem stephenfin: um
17:07:16 stephenfin I'm currently deploying DevStack to see if I can reproduce that issue from Tushar Patil. However, the deprecation doesn't really depend on that
17:07:24 mriedem stephenfin: would be nice to know if tpatil can confirm novnc 1.0.0 works for him
17:07:29 mlavalle gibi: ack. will look for them
17:08:05 gibi mlavalle: I have Bence Romsics (rubasov) who can help with the neutron discussion / implementation work
17:08:21 mriedem stephenfin: ovh was saying they have the novnc fix deployed in their cloud though and it works
17:09:00 stephenfin Right. I can't verify as I can't read Japanese :)
17:09:03 mlavalle gibi: fantastic!
17:09:07 mriedem stephenfin: so i think the thing i was looking for in the deprecation was we need wording in the config option help text that you need novnc >= 1.0.0
17:09:15 mriedem stephenfin: maybe takashin can help
17:09:21 mriedem he was also pushing a related spec for NTT related to this

Earlier   Later