Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-07-28
04:18:43 dansmith mriedem: dims said he'd get it in the morning if ttx didn't first
04:18:56 mriedem yeah doug said they'd do it by the 10am CT release meeting
04:19:04 dansmith aye
04:20:15 mriedem alright, well f yeah, i'm going to watch some much deserved garbage tv and then go to bed
04:20:31 dansmith enjoy
04:20:42 mriedem thanks for shepharding
04:20:46 mriedem *shepherding?
04:20:48 dansmith np, g'nite
04:25:45 openstackgerrit OpenStack Proposal Bot proposed openstack/python-novaclient master: Updated from global requirements https://review.openstack.org/488283
06:00:24 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove unnecesary code https://review.openstack.org/488299
06:01:27 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove unnecessary code https://review.openstack.org/488299
07:33:47 openstackgerrit Takashi NATSUME proposed openstack/nova master: Amend uuid4 hacking rule https://review.openstack.org/488315
08:07:28 openstackgerrit longxingmiao proposed openstack/nova master: test review https://review.openstack.org/488328
08:24:09 openstackgerrit Balazs Gibizer proposed openstack/nova master: Test resize with placement api https://review.openstack.org/487958
08:31:56 openstackgerrit jichenjc proposed openstack/nova master: refactory some code on get_password https://review.openstack.org/449458
08:35:25 openstackgerrit jichenjc proposed openstack/nova master: add cert when send keystone request https://review.openstack.org/485121
08:37:43 openstackgerrit jichenjc proposed openstack/nova master: Add quiesce and unquiesce in support matrix https://review.openstack.org/482390
09:04:07 bhagyashris gibi: Hi, I have resolved my yesterday's issue there was some problem to restart the nfs server and for locking thing through nfs required statd service to enable.
09:09:44 gibi bhagyashris: good to hear that
09:11:02 bhagyashris gibi: Now everything is working fine to test the shared resource provider thing. I have just tested one scenario simply created instance as as mentioned in http://paste.openstack.org/show/616724/ but in my observation the root gb of created flavor has been considered in the allocations table against the compute resource provider and CUSTOM_DISK resource against "shared_resource" resource provider.
09:12:46 bhagyashris gibi: IMO, As i am creating the nfc backed instance so it should take the RAM and VCPU from the computes resource provider and DISK from the "shared_resource" provider
09:13:06 bhagyashris s/nfc/nfs
09:22:41 gibi bhagyashris: I don't know how can you tell nova that you want to consume DISK_GB not from the compute provider but from the shared one
09:23:07 gibi bhagyashris: this is why I suggested to use CUSTOM_DISK in the shared and then add CUSTOM_DISK to the flavor
09:23:20 gibi bhagyashris: that way I sure that the instance will consume from your shared provider
09:23:42 gibi bhagyashris: I hope others can help with this specific issue
09:29:56 bhagyashris gibi: ohk. thank you.
09:39:11 SteveRUKC hey all, quick question to which im struggling to find an answer. Is disk_allocation_ratio taken into account on live/cold migrations. As we have an allocation ratio of 6 set, but are having issues with migrations failing with a disk instance too large for target message.
09:39:34 SteveRUKC also, hypervisor_stats is showing a negative number for least_free
09:39:44 SteveRUKC if anyone has any ideas it would be most appreciated
09:48:14 openstackgerrit Balazs Gibizer proposed openstack/nova master: DNM: trying to turn on periodic tasks https://review.openstack.org/488352
09:53:39 openstackgerrit Chris Dent proposed openstack/nova master: Optional separate database for placement API https://review.openstack.org/362766
10:09:26 dims dansmith : looks like ttx took care of it 3 hours ago. w00t
10:14:46 cdent gibi: I did some similar periodic job fiddling last night and ran into the same confusion with the computes getting weird
10:15:15 cdent I’m guessing the fixture (or the the service) is not happy being in the same process with another version of itself?
10:29:49 bhagyashris cdent: Hi, Hi, I have resolved my yesterday's issue there was some problem to restart the nfs server and for locking thing through nfs required statd service to enable.
10:29:51 openstackgerrit Chris Dent proposed openstack/nova master: [placement] quash unicode warning with shared provider https://review.openstack.org/488363
10:30:12 cdent bhagyashris: ah, cool, glad you were able to make it work
10:30:51 bhagyashris cdent: Now everything is working fine to test the shared resource provider thing. I have just tested one scenario simply created instance as as mentioned in http://paste.openstack.org/show/616724/ but in my observation the root gb of created flavor has been considered in the allocations table against the compute resource provider and CUSTOM_DISK resource against "shared_resource" resource provider.
10:31:09 bhagyashris cdent: IMO, As i am creating the nfs backed instance so it should take the RAM and VCPU from the computes resource provider and DISK from the "shared_resource" provider.
10:31:12 kashyap mdbooth: Thanks for the review!
10:31:56 kashyap And also to dansmith (About: https://review.openstack.org/#/c/485752/, but not for the "summary" remark :P)
10:32:16 cdent bhagyashris: you can address that (at least in part) by using DISK_GB instead of CUSTOM_DISK for the nfs shared resource provider
10:32:17 kashyap johnthetubaguy: Maybe when you have a minute to ACK this straightforward change: https://review.openstack.org/#/c/485752/
10:33:07 cdent the thing that will be missing is that there’s nothing currently in place to manage the allocation of disk on the shared resource provider, but that’s in progress with the claim in the scheduler stuff that is being worked on this week
10:36:25 bhagyashris cdent: ohk Means instead of creating the "CUSTOM_DISK" resource class and then creating the inventory for that I need to update the inventory against "DISK_GB" resource class right.
10:37:41 cdent bhagyashris: well basically the general rule is that if you can use a standard resource class (because it maps to the unit of resource a provider is providing) you may as well
10:39:43 bhagyashris cdent: ohk. checking...
10:48:08 s-dean Hello, could someone point me in the right direction to debug this nova.exception.NeutronAdminCredentialConfigurationInvalid' ?
10:50:10 s-dean nevermind
10:53:47 bhagyashris cdent: I have updated the inventory using DISK_GB resource class against the nfs shared resource provider but in that case after booting the instance it's not using shared_storage provider.
10:54:36 bhagyashris cdent: It address the disk used against compute node resource provider.
10:58:23 vdrok good morning everyone!
10:58:38 vdrok sdague: small request, if you have some time :) https://review.openstack.org/480624
11:00:47 vdrok thanks!
11:01:01 cdent bhagyashris: ah, right, because the compue is reporting it’s own disk too, so is considered a valid target for all the resources. /me thinks
11:01:30 cdent bhagyashris: are you working from today’s master or something earlier?
11:02:29 bhagyashris cdent: yeah. I am working from todays master commit-id: 23c4eb34380bdf3eece11abbe0f6ccb68c060f47 "claim resources in placement API during schedule()"
11:07:10 cdent bhagyashris: do you have the log of it making the PUT /allocations requests? It might be that the scheduler is claimng one set of allocations, but later (in the periodic update) the resource tracker is changing things. if you’re going to be using the CUSTOM_DISK resource class you need to make sure your flavor doesn’t indicate any requests for disk_gb
11:07:53 cdent I think over the next few days things are likely to be quite unstable with claims, and there will be a few more changes coming
11:09:48 bhagyashris cdent: ohk.
11:10:28 cdent bhagyashris: it’s great that you’re doing this investigating, but right now is going to be a chaotic time
11:13:15 cdent bauzas: if this still alive? https://review.openstack.org/#/c/427200/
11:13:24 bauzas cdent: looking
11:13:47 bauzas cdent: well, maybe we should discuss with matt
11:13:58 bauzas I can rebase it
11:14:05 bauzas meanwhile
11:14:26 cdent k, thanks
11:16:26 bhagyashris cdent: ohk. Just to inform you I have checked the allocations table entries and in that I saw the disk_gb reported against the compute node resource provider and not the shared resource provider.
11:16:59 bhagyashris cdent: Thank you for your time :)
11:17:19 cdent yeah, in the case where you have two different provider of DISK_GB it is likely that the non-shared provider will be picked when there are multiple options.
11:24:56 bhagyashris cdent: ohk.
11:25:58 openstackgerrit Sean Dague proposed openstack/nova master: always show urls in list_cells https://review.openstack.org/487860
11:36:10 gibi cdent: yes, I have the same feeling about the host name confusion
11:36:27 gibi cdent: but I cannot spend more time on it today. I will continue looking into it on Monday
11:36:42 cdent gibi: I also left a comment on your test about another thing worth looking into
11:36:56 cdent if I have time today I may experiment some more, but not sure I’ll have time
11:37:06 cdent thanks for messing with it
11:37:38 gibi thanks for thelping
11:38:21 gibi if you make some progress still today then do not hesistate to update any of my reviews
11:43:58 openstackgerrit Sylvain Bauza proposed openstack/nova master: Add a status check for enabled filters https://review.openstack.org/427200
11:44:24 bauzas cdent: ^
11:44:34 cdent ✔
11:44:40 bauzas after reviewing it, I think it's important to merge it
11:44:43 bauzas for Pike
11:46:28 openstackgerrit Chris Dent proposed openstack/nova master: Add functional test for two-cell scheduler behaviors https://review.openstack.org/452006
11:49:01 openstackgerrit Chris Dent proposed openstack/nova master: [placement] gabbi tests for shared custom resource class https://review.openstack.org/485209
11:50:46 cdent bauzas: there’s quite a lot of small things that either fix minor bugs, cover areas not previously covered, or document things. all of which would be nice for pike. update 30 will be ready in a few minutes. If you and others can get to some of the things in the “other” section that would be very useful.
11:51:21 bauzas cdent: sorry, I don't understand you
11:51:30 bauzas cdent: you want me to do what ? review ?
11:52:20 cdent bauzas: a) I’m agree with hou on the import to merge 427200 and b) saying there’s lots of similar things, which will be listed in the # Other section rp update 30 coming out soon, which will need review and ought to be merged
11:52:40 bauzas ah, yes, agreed on that
11:53:05 bauzas we need to make sure we use those two weeks correctly, ie. not for features but rather bugs and/or docs
11:53:19 bauzas tbc, I'll mostly do bug triage next week
11:53:28 bauzas and the rest of my time will be for reviewing
12:03:47 sdague cdent / bauzas / jay - just an FYI of something I closed as won't fix - https://bugs.launchpad.net/nova/+bug/1707085 - in case you have other opinions
12:03:48 openstack Launchpad bug 1707085 in OpenStack Compute (nova) "Max_unit should account for allocation_ratio" [Undecided,Won't fix]
12:09:35 cdent sdague: your response makes sense to me, and max_unit is being set as it for the reasons you describe
12:23:26 cdent edleafe: left a comment on https://review.openstack.org/#/c/487954/ Just trying to make your life harder (as usual)
12:24:27 edleafe cdent: saw it. I'm not sure that any instance on an ironic node would ever have any other custom resource class. I mean, that's the point, right?

Earlier   Later