Earlier  
Posted Nick Remark
#openstack-nova - 2017-07-18
14:25:39 bauzas dansmith: isn't the intent ? :)
14:26:04 dansmith bauzas: I dunno, I just saw that notification pop up and noticed not all those words belong together
14:26:11 bauzas everyone wants their blackbox for deciding which kid they have is the best
14:26:16 dansmith if that was the intent, then.. bravo :)
14:26:37 bauzas the real problem is that the list of kids is depending on the blackbox
14:26:52 sean-k-mooney bauzas: mriedem basically for the ONAP case when a host is selected and resouce allocated they need to relay that up into there own invetory system also. i think today they do that via connectin directly to the nova db.
14:27:24 bauzas sean-k-mooney: sure, but my point is that the input you should get should only hosts that placement agrees with
14:27:37 sean-k-mooney bauzas: yes i agree with that too
14:27:49 bauzas sean-k-mooney: like, you should never choose between hosts that don't have resources for the asked flavor
14:28:00 sean-k-mooney bauzas: yes
14:28:09 bauzas sean-k-mooney: that's how we guarantee interop
14:28:13 bauzas a flavor is an interop thing
14:28:49 bauzas so whatever the decision system is doing, you as a user will be sure that your instance will be on a host that can support X CPUs, Y RAM and Z disk
14:29:06 bauzas the rest is left to you
14:29:26 sean-k-mooney bauzas: so as i said there are way to supprot them if they need it without a costom driver. i just dont know how many people have already used the plugable interface that would be effect by the bug.
14:29:48 bauzas you could decide to pick host A against B and C because you're Saggitarian if you wish
14:30:07 dims mriedem : i had a cleanup from looking at castellan, do we want to do that now or when queens opens up? https://review.openstack.org/#/c/484036/
14:30:10 bauzas that's why I turned my choice
14:31:09 mriedem alex_xu: i replied in https://review.openstack.org/#/c/469800/
14:31:19 mriedem dims: that conflicts with a change that kfarr did
14:31:25 mriedem did you see that?
14:31:35 dims oops checking
14:31:42 mriedem dims https://review.openstack.org/#/c/439855/9
14:32:10 dims mriedem : kfarr's works! looking deeper
14:32:43 sean-k-mooney jaypipes: hehe i need to figure out how to integreate weechat with spell also a git hook for same
14:33:04 jaypipes sean-k-mooney: :)
14:34:23 dims mriedem : yep +1 on that review, we should get that in for Pike if possible
14:34:38 openstackgerrit Merged openstack/python-novaclient master: Updated from global requirements https://review.openstack.org/484582
14:34:55 jaypipes sean-k-mooney: re: ONAP, if they have chosen to architect their system by subverting the public interfaces of Nova, it is not our job to cater to those architectural fauxpas. The best advice I would have to ONAP folks is what mriedem said and have their global inventory system work with the placement service via Placement's public REST APIs and let the filter scheduler do its job (with custom weighers as you mentioned)
14:35:52 openstackgerrit Alex Xu proposed openstack/nova master: Use plain routes list for os-volume-attachments instead of stevedore https://review.openstack.org/484824
14:35:53 openstackgerrit Alex Xu proposed openstack/nova master: Use plain routes list for extension_info instead of stevedore https://review.openstack.org/484826
14:35:53 openstackgerrit Alex Xu proposed openstack/nova master: Use plain routes list for os-snapshots instead of stevedore https://review.openstack.org/484825
14:36:12 sean-k-mooney jaypipes: yep i agree and that is the direction i would be pushing them towords but i do not spend much time on ONAP to be honest so not sure how much they will listen.
14:36:33 jaypipes sean-k-mooney: who are the driving forces in ONAP?
14:37:36 jangutter jaypipes: Telcos, I believe.
14:38:06 sean-k-mooney jaypipes: AT&T from the ecomp side and several asian telcos form the OpenO community. ONAP is a fusion of both comunitys under the linux foundation. intel is a member but we have not been invole in the achitecher of this part whic come mainly form ecomp i belive
14:38:14 jaypipes jangutter: well, yeah :)
14:38:53 openstackgerrit Sylvain Bauza proposed openstack/nova master: Add a scheduler custom driver possibility https://review.openstack.org/484828
14:38:54 sean-k-mooney jaypipes: there is little european representation in ONAP current with most European telcos look more to OSM instead
14:39:13 jaypipes sean-k-mooney: wow, that was impressive :) comunitys, invole, achitecher, whic and belive. all new words in one sentence!
14:39:19 bauzas sean-k-mooney: mriedem: jaypipes: I need to disappear from a certain amount of time because I need to pick my daughter and do some stuff, but I'll respond to the ML thread
14:39:23 jaypipes sean-k-mooney: ok, I'm going to stop poking fun now :)
14:39:34 bauzas sean-k-mooney: mriedem: jaypipes: reviews welcome on https://review.openstack.org/484828
14:40:08 jangutter jaypipes: there was _lots_ of representation from Chinese telcos on ONAP at OPNFV.
14:40:09 sean-k-mooney jaypipes: :)
14:41:29 jaypipes jangutter: k. good to know. I'm more looking for specific people, though. any names or emails would be good to get so I can reach out and have a chat.
14:41:48 jaypipes I suppose I can hit up alanmeadows from AT&T for that info
14:42:51 jangutter jaypipes: I'll see if there's a nice mini-summit link for the presentations with contact details.
14:42:55 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Populate the 'configuration' section https://review.openstack.org/478473
14:42:55 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Populate the 'user' section https://review.openstack.org/478475
14:42:56 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Switch to openstackdocstheme https://review.openstack.org/477751
14:42:56 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Populate the 'contributor' section https://review.openstack.org/478474
14:42:57 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Start using oslo_config.sphinxext https://review.openstack.org/482961
14:42:57 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Rework README to reflect new doc URLs https://review.openstack.org/480074
14:42:58 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Start using oslo_policy.sphinxext https://review.openstack.org/479358
14:42:58 openstackgerrit Stephen Finucane proposed openstack/nova master: policies: Fix Sphinx issues https://review.openstack.org/480516
14:42:59 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Populate the 'reference' section https://review.openstack.org/478484
14:42:59 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Rework index page per new sections https://review.openstack.org/478485
14:43:00 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Remove dead files https://review.openstack.org/478470
14:43:29 jaypipes just kiddin, stephenfin :)
14:43:45 jangutter jaypipes: http://events.linuxfoundation.org/events/opnfv-summit/extend-the-experience/onap
14:44:16 jangutter jaypipes: just names though, you should be able to hit the presentations from the 2017 summary site.
14:44:20 mriedem i'm sure i can ask around within huawei and someone might know
14:44:25 stephenfin jaypipes: Sorry - merge conflicts, yet again 🙈
14:47:02 mriedem stephenfin: reviewing https://review.openstack.org/#/c/463987/ would be good
14:47:20 sean-k-mooney bauzas: maybe add a release note but i think that review looks fine otherwise
14:47:22 mriedem it's passed https://review.openstack.org/#/c/481290/
14:47:37 mriedem sean-k-mooney: bauzas: i don't, but review comments incoming
14:49:01 stephenfin mriedem: eek. ildikov has been imploring me to look at that, but I don't feel I know that code enough to really sign-off on it
14:49:20 stephenfin I'll try, but don't blame me if everything explodes afterwards, heh
14:50:05 mriedem it's ok to ask questions and not +2
14:50:15 mriedem i've been through it a couple of times
14:51:00 sean-k-mooney mriedem: https://review.openstack.org/#/c/463987 is basically using the same workflow as the neutron portbinding then? eg createing a new binding/attachemt in this case on the destination and only removing the old one on succesfull migration?
14:51:20 mriedem sean-k-mooney: similar yes
14:51:59 sean-k-mooney mriedem: ok cool i have no ideay how the cinder integration works so proably wont review but that workflow makes sense to me. good to know
14:52:43 mriedem dims: i'd like to get this in first https://review.openstack.org/#/c/484501/ so we can backport that to stable
14:52:49 mriedem because of the associated bug
14:54:41 dims mriedem : +1, though we should probably add an upgrade note to ask operators to make sure that option is set in everyone's nova.conf
14:57:24 mriedem dims: hmm, if we have to add an upgrade release note then i worry about backporting it
14:57:48 mriedem dims: honestly i'm not really sure why the set_default there is overriding what the operator puts in the config,
14:57:52 mriedem but that was reported yesterday
14:58:00 mriedem dims: if you could figure that out it would be helpful
14:59:31 dims mriedem : it should not be overriding what's in nova.conf, it just sets the default value if there's nothing in nova.conf
14:59:59 dims mriedem : http://git.openstack.org/cgit/openstack/oslo.config/tree/oslo_config/cfg.py#n2736
15:01:18 gibi jaypipes: with cdent fix I still get the same KeyError as before, logs are here http://paste.openstack.org/show/615743/
15:01:23 keerthi scheduling always happen only 10 at a time in the nova ?
15:01:38 keerthi shall we change this value ?
15:03:15 keerthi mriedem ?
15:04:11 jaypipes gibi: k, thanks for that log output, that's helpful. I'm wondering if alex_xu's patch here might help: https://review.openstack.org/#/c/480379/
15:04:25 gibi jaypipes: I can test that as well
15:04:25 jaypipes gibi: sorry to bother you on this, but do you think you can apply that patch too?
15:04:34 jaypipes gibi: ty sir, much appreciated!
15:04:51 jaypipes gibi: in the meantime, I am working on adding functional test scenarios for your specific case.
15:05:12 gibi jaypipes: put me in the review if any I will check that out
15:05:19 jaypipes gibi: cheers
15:05:21 alex_xu mriedem: replied https://review.openstack.org/#/c/469800/, if we really think it is time to merge this patch first, I can change to +w
15:05:48 jaypipes gibi: köszönöm!
15:06:02 mriedem dims: yeah that's what i thought, but he was saying he had a value set in nova.conf and it would still use the default from code, and removing that line fixed it
15:06:18 gibi jaypipes: szivesen
15:06:24 mriedem dims: i don't have a devstack handy to recreate

Earlier   Later