| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-04-11 | |||
| 10:16:57 | ralonsoh | sfinucan: hi! | |
| 10:18:04 | sfinucan | ralonsoh: How come we're using the 'extra_info' column in that review rather than adding a new capabilities column? | |
| 10:18:54 | sfinucan | I didn't even question it until you said that nothing else was using the column now. If it was important enough to move out the other stuff, why re-add new stufF? | |
| 10:19:33 | ralonsoh | sfinucan: that is the easy way, to add a new field | |
| 10:20:05 | ralonsoh | sfinucan: instead of this, we decided not to modify the DB schema and add this information into extra_info | |
| 10:20:36 | ralonsoh | sfinucan: extra_info is initially a bucket for "other" information, not so relevant | |
| 10:22:06 | sfinucan | ralonsoh: OK. What's the long term strategy then? Drop that entire table in favour of resource providers? | |
| 10:22:18 | openstackgerrit | Stephen Finucane proposed openstack/nova master: Add description to policies in hypervisors.py https://review.openstack.org/451294 | |
| 10:22:48 | ralonsoh | sfinucan: yes, move every item (network:capabilities, etc) to resource providers | |
| 10:23:09 | ralonsoh | sfinucan: this migration will modify a small part of this feature | |
| 10:23:29 | ralonsoh | sfinucan: and should be fast to implement | |
| 10:24:08 | openstackgerrit | Sylvain Bauza proposed openstack/nova-specs master: Proposed block accepting AZ renames https://review.openstack.org/446446 | |
| 10:24:15 | sfinucan | ralonsoh: Oh yeah - I agree with doing it this way. Just making sure I've the big picture right in my head first :) | |
| 10:24:55 | abhi89 | johnthetubaguy: at https://github.com/openstack/nova/blob/5a6d4e089dca2515c0f7e083a8b903ac7a166773/nova/volume/cinder.py#L202, after catching the OverLimit exception, we are raising OverQuota exception with overs='volumes'. But here the overs could have been volumes, gigabytes or per_volume_gigabytes. In each case there would be different error messages specific to the quota exceeded | |
| 10:24:56 | ralonsoh | sfinucan: sure! this is the last working point of the spec, but I'll do it | |
| 10:25:31 | johnthetubaguy | abhi89: I agree with you, it just the fix is in a different place to your current patch | |
| 10:25:40 | sfinucan | ralonsoh: Ok, thanks for the info. I'm going to add a few points about including context comments (so people can understand what's going on) but that looks good to me otherwise | |
| 10:25:53 | ralonsoh | sfinucan: thanks! | |
| 10:28:09 | BobBall | johnthetubaguy / artom: Found the problem - it's relating to Ia0869dc6f7f5bd347ccbd0930d1d668d37695a22 (device tag disappearing) - because nova re-added the device tag in the 2.42 version but novaclient doesn't support that version, we have no way of using device tagging currently. | |
| 10:28:15 | jsheeren | anyone know if it is possible to limit image A to be only able to use flavor X and Y, image B only flavor Z? | |
| 10:28:37 | johnthetubaguy | BobBall: oh I forgot about that being for tags | |
| 10:29:02 | BobBall | Not sure what the fix is currently -I did try hacking novaclient but it still can't cope with device tags for block devices... | |
| 10:29:24 | johnthetubaguy | jsheeren: there are various image properties that can help for specific requirements, not sure there is a blanket only flavor X thing. | |
| 10:29:50 | johnthetubaguy | BobBall: can't you raise the max supported API version up to 2.42? | |
| 10:32:09 | BobBall | works for nics but not for block devices (volume_id is not recognised) | |
| 10:35:46 | johnthetubaguy | BobBall: I am curious what the API tests are doing, I don't remember the context around that stuff | |
| 10:36:26 | BobBall | :P | |
| 11:24:00 | sfinucan | vladikr, sahid: Could you guys take a look at some point, please? https://review.openstack.org/#/q/topic:bump-min-libvirt+status:open | |
| 11:32:28 | jsheeren | johnthetubaguy: thanks | |
| 11:32:43 | openstackgerrit | Sergey Nikitin proposed openstack/nova master: Added PCI NUMA policies https://review.openstack.org/390520 | |
| 11:33:58 | vladikr | sfinucan, sure. will drop off my kids to school and then | |
| 11:43:17 | artom | BobBall, if you pin the version to 2.32 it should work for both nic and bdm tags | |
| 11:43:25 | artom | Until we merge the 2.42 novaclient change | |
| 11:48:28 | gaurangt | hi, I'm facing issue in the nova instance creation and it is failing with following error in nova-compute.log | |
| 11:48:30 | gaurangt | Failed to create resource provider record in placement API for UUID | |
| 11:48:39 | gaurangt | The requested URL /placement/resource_providers was not found on this server | |
| 11:49:11 | gaurangt | I actually added the <Directory> section in nova-placement-api.conf, but still the same issue. | |
| 11:50:03 | gaurangt | any idea what might be going wrong here? | |
| 11:50:44 | gaurangt | nova-placement-api.conf looks like this - http://paste.openstack.org/show/606143/ | |
| 11:51:41 | cdent | gaurangt: "/nova-placement-api" should be "/placement" in both places it shows up | |
| 11:51:56 | cdent | actually the Alias is wrong in other ways too, just a sec | |
| 11:53:14 | cdent | gaurangt: we're you following some docs to set this up? | |
| 11:53:58 | gaurangt | cdent, yes, I'm following the official OpenStack guide | |
| 11:53:59 | gaurangt | https://docs.openstack.org/ocata/install-guide-rdo/nova-controller-install.html | |
| 11:55:36 | cdent | gaurangt: it looks like the rdo packages may be configuring apache somewhat incorrectly | |
| 11:56:00 | gaurangt | cdent, oh | |
| 11:56:04 | cdent | changes the <Location ..> entry to be <Location /placement> and reload apache and see what happens | |
| 11:56:13 | gaurangt | cdent, what should be the workaround here? | |
| 11:56:21 | cdent | what I just said | |
| 11:56:38 | gaurangt | what about this - Alias /nova-placement-api /usr/bin/nova-placement-api? | |
| 11:56:58 | gaurangt | just above the <Location..> | |
| 11:57:46 | cdent | there too: Alias /placement /usr/bin/nova-placement-api | |
| 11:58:14 | gaurangt | cdent, hmm ok | |
| 11:59:06 | gaurangt | any nova service needs to be restarted? | |
| 11:59:13 | cdent | no just apache | |
| 11:59:30 | gaurangt | ok | |
| 11:59:52 | gaurangt | ah, now it says - You don't have permission to access /placement/resource_providers | |
| 12:02:01 | gaurangt | cdent, anything still wrong? | |
| 12:06:05 | cdent | move that <Directory> section outside of the VirtualHost | |
| 12:06:10 | cdent | gaurangt: ^ | |
| 12:06:50 | gaurangt | cdent, ok | |
| 12:10:26 | cdent | gaurangt: once you get this figured out, I'd suggest you submit a bug to the rdo packagers. It seems like there might some confusion between what's being set the apache configuration and what's being set in the service catalog. Either the packages or the docs are wrong | |
| 12:13:06 | gaurangt | cdent, thanks it worked | |
| 12:13:20 | cdent | gaurangt: ah, good, glad to hear it | |
| 12:13:23 | gaurangt | cdent, I will submit a bug now | |
| 12:13:30 | cdent | awesome! | |
| 12:13:57 | gaurangt | cdent, thanks for the help ! | |
| 12:50:06 | egonzalez | Hi, it's been a recent change in master who change the behaviour in nova service-list? in current master output is empty with no service registered | |
| 12:59:57 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers-actions (4/4) https://review.openstack.org/455573 | |
| 13:07:10 | jsheeren | hi again, i'm back with my question about pinning an image to a flavor | |
| 13:07:30 | jsheeren | we can set the min-disk and min-ram on the image, is there something similar with os_distro or os_type? | |
| 13:11:57 | BobBall | artom: Thanks but I don't think it will - nova client is rejecting the volume_id based on internal code, not checking the nova API version | |
| 13:13:59 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Example verification for servers-actions.inc https://review.openstack.org/454565 | |
| 13:15:01 | peter-hamilton | johnthetubaguy: do you have a minute to discuss cert validation? | |
| 13:23:20 | andymccr | cdent: are you about? | |
| 13:23:37 | cdent | andymccr: hi, yes | |
| 13:23:54 | andymccr | cdent: hey :) if you have a second - is there a reason why CONTENT_LENGTH has to be set to an int? https://github.com/openstack/nova/commit/6dd047a3307a1056077608fd5bc2d1c3b3285338 | |
| 13:24:16 | andymccr | im having issues in that content_length is present, but empty so its failing with a valueError: https://bugs.launchpad.net/nova/+bug/1681843 | |
| 13:24:16 | openstack | Launchpad bug 1681843 in OpenStack Compute (nova) "Nova-placement returns "ValueError: invalid literal for int() with base 10: ''"" [Undecided,New] | |
| 13:24:32 | andymccr | i figure the easiest fix is just to remove the int() (which works) but wanted to make sure im not overlooking anything | |
| 13:25:27 | cdent | andymccr: need to catch up and get my brain right, just a sec | |
| 13:25:41 | andymccr | cdent: no problem. lemme know if i can explain anything better/further | |
| 13:25:49 | peter-hamilton | jaypipes: do you have a sec to discuss cert validation? | |
| 13:26:13 | jaypipes | peter-hamilton: here on IRC? or in a hangout or something? | |
| 13:26:25 | peter-hamilton | jaypipes: here's fine, just some quick questions | |
| 13:26:35 | jaypipes | peter-hamilton: go for it. | |
| 13:27:02 | peter-hamilton | jaypipes: are you ok with adding two conf options, (1) to enable/disable cert validation, and (2) to provide a default list of trusted cert IDs | |
| 13:27:17 | peter-hamilton | jaypipes: the goal would be to smooth the migration path and user experience | |
| 13:27:25 | peter-hamilton | jaypipes: these were recommended by johnthetubaguy | |
| 13:27:39 | jaypipes | peter-hamilton: if that smooths the integration path, I'm all for it.' | |
| 13:28:32 | peter-hamilton | jaypipes: cool, i'm folding those in | |
| 13:28:37 | jaypipes | rock on brother. | |
| 13:30:53 | openstackgerrit | Andy McCrae proposed openstack/nova master: Don't force CONTENT_LENGTH to be an int() https://review.openstack.org/455710 | |
| 13:31:11 | cdent | andymccr: hmmm. that's icky behavior by nginx. what that check is trying to do is detect that there is a body with some length, without actually looking at the body, and then complain if there's no content-type header | |
| 13:31:40 | cdent | so if nginx is sending both, but with empty values, neither line is correct | |
| 13:32:33 | andymccr | cdent: agreed, although im confused as to why we need to force it to be an int? if there are no integer comparisons after that | |
| 13:33:11 | cdent | andymccr: probably because i was being overzealous: the spec says that if the header is present it's value is made up of DIGITS | |
| 13:33:20 | andymccr | ahh | |
| 13:33:54 | andymccr | cdent: any issue with removing the int? alternatively, we could get it, check it's not None and then make sure it's an int? | |
| 13:34:03 | andymccr | (or something slightly more efficient i assume) | |