Earlier  
Posted Nick Remark
#openstack-nova - 2017-05-18
16:29:46 zzzeek https://en.wikipedia.org/wiki/UTF-8#Description
16:29:47 zzzeek OK
16:30:07 sean-k-mooney sfinucan: i thinkg its 1-4 bytes if i remember correctly
16:30:11 zzzeek sdague: thougth that was weird, b.c. why not refer to "6 byte support" :)
16:30:18 sdague I guess I had misunderstood that unicode consortium had crossed that line
16:30:40 sfinucan sean-k-mooney: Are you saying Google lied to me? :O
16:30:41 mdbooth IIRC UTF-8 characters can be arbitrarily many bytes, because they may combine arbitrarily many codepoints
16:31:23 zzzeek mdbooth: the hypotthetical max is 6 bytes
16:31:29 sfinucan And this is the point where I go chuck a ball about in the sunshine :)
16:31:30 sean-k-mooney sfinucan: yes hehe ill double check but when i was working with it in the past i rember it being 4 bytes max for some reason
16:31:35 openstackgerrit Dan Smith proposed openstack/nova master: WIP: De-complicate some of the instance delete path https://review.openstack.org/458636
16:31:36 openstackgerrit Dan Smith proposed openstack/nova master: Move to proper target_cell calling convention https://review.openstack.org/458634
16:31:37 openstackgerrit Dan Smith proposed openstack/nova master: Make target_cell() yield a new context https://review.openstack.org/458635
16:31:38 openstackgerrit Dan Smith proposed openstack/nova master: WIP: Debug race in delete-while-booting test https://review.openstack.org/461513
16:31:39 mdbooth zzzeek: I think that's for a single codepoint?
16:31:40 openstackgerrit Dan Smith proposed openstack/nova master: DNM: Canary test against multi-cell devstack https://review.openstack.org/458537
16:31:40 openstackgerrit Dan Smith proposed openstack/nova master: Target cell on local delete https://review.openstack.org/464059
16:31:56 mdbooth A character may be multiple codepoints
16:32:08 zzzeek mdbooth: now that you have to show me
16:32:09 zzzeek :)
16:32:21 zzzeek mdbooth: im pretty sure no such voodoo is used in practice
16:32:35 mdbooth zzzeek: Like a-umlaut, for eg
16:32:41 mdbooth IIRC that's 2 code points, but 1 char
16:32:47 zzzeek mdbooth: i mean, in databases
16:33:14 mdbooth Well it's all strings ultimately.
16:33:27 mdbooth It boils down to the definition of a character.
16:34:03 dansmith please don't let my snoring interrupt this riveting conversation
16:34:09 zzzeek mdbooth: OK! well. writing an email here, specifics, things that affect us right now :)
16:35:03 sdague zzzeek: I'll update the pg spec with that, it's good info
16:39:14 mdbooth dansmith zzzeek: Heh, yeah, its unlikely to be of interest to us :) It's of interest when you need to display text and, for eg, select characters with a mouse. I read a fantastic article about it recently but I can't find it right now.
16:39:15 sean-k-mooney sfinucan: looking at https://tools.ietf.org/html/rfc3629 section 10 "Security Considerations" we are both right.... the utf-8 encounding would support up to 6 bytes but such encounding produce illegal and only up to 4 bytes are vailid
16:40:05 mdbooth Questions like: what should pressing backspace do in a text editor are actually really hard to answer.
16:47:22 sean-k-mooney sdague: zzzeek mdbooth if ye just define the field as an NVARCHAR in sqlalchemy and set the coalation type for the table to utf8_bin or utf8_general_ci/utf8_unicode_ci the db should handel it its self
16:50:47 openstackgerrit Jianghua Wang proposed openstack/nova master: Skip policy rules on attach_network for none network allocation https://review.openstack.org/465903
16:55:31 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/nova master: Read Neutron port 'binding_profile' during boot https://review.openstack.org/449257
16:55:31 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/nova master: Add Neutron port capabilities to devspec in request https://review.openstack.org/451777
16:55:32 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/nova master: Format NIC features using os-traits definitions https://review.openstack.org/466051
16:57:27 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/nova master: Read Neutron port 'binding_profile' during boot https://review.openstack.org/449257
18:17:20 openstackgerrit melanie witt proposed openstack/nova master: Cache database and message queue connection objects https://review.openstack.org/465042
18:18:27 ZZelle_ sfinucan, hi
18:34:09 marst edleafe: are you around?
18:36:45 openstackgerrit christopher.uhler proposed openstack/nova master: Libvirt volume driver for Veritas HyperScale https://review.openstack.org/443951
18:37:09 openstackgerrit Dan Smith proposed openstack/nova master: DNM: Canary test against multi-cell devstack https://review.openstack.org/458537
18:53:44 cdent marst: edleafe is probably on a plane on his way to pycon
18:59:08 marst cdent: thanks! I've just read his blog post
19:15:18 openstackgerrit Sean Dague proposed openstack/nova master: see if we can use pg wheels with no bindep https://review.openstack.org/466081
19:26:09 mriedem dansmith: did you figure out http://logs.openstack.org/37/458537/20/check/gate-tempest-dsvm-multinode-live-migration-ubuntu-xenial/ab364da/logs/testr_results.html.gz ?
19:47:47 openstackgerrit Cedric Brandily proposed openstack/nova master: Correct _ensure_console_log_for_instance implementation https://review.openstack.org/466088
19:48:56 mriedem this seems wrong http://logs.openstack.org/42/465042/6/check/gate-nova-tox-functional-py35-ubuntu-xenial/9829a45/console.html#_2017-05-18_18_43_03_020297
19:49:00 mriedem b"KeyError: 'allocations'"
19:49:56 dansmith mriedem: I found the hook yeah, still working on a fix
19:50:07 mriedem ok,
19:50:21 mriedem i'm working on disabling the grenade live migration job from running on pike until we fix it, or queens
19:50:28 mriedem since right now it's just burning nodes
19:51:53 mriedem this is very weird - http://logs.openstack.org/42/465042/6/check/gate-nova-tox-functional-py35-ubuntu-xenial/9829a45/console.html#_2017-05-18_18_43_03_020297 it's like in the middle of a functional test, we got a different response from placement
19:52:07 mriedem like it's a GET / response
19:52:21 mriedem but was expecting GET /resource_providers/d41180aa-047e-4bc3-b0f3-11532683400d/allocations
19:54:44 openstackgerrit Cedric Brandily proposed openstack/nova master: Correct _ensure_console_log_for_instance implementation https://review.openstack.org/466088
19:58:31 melwitt mriedem: yeah, I didn't know what to make of that
20:03:21 mriedem could have something to do with running those services under eventlet in our functional tests?
20:20:29 efried Where does the hashy thing at the end of a release note .yaml's basename come from?
20:21:36 openstackgerrit Dan Smith proposed openstack/nova master: DNM: Canary test against multi-cell devstack https://review.openstack.org/458537
20:21:54 artom efried, the 'reno' command does it
20:23:04 efried artom Is there a doc somewhere that describes the release note process?
20:23:12 efried (Cause your answer just raised bigger questions ;-)
20:23:35 artom efried, not that I know of, but if you have a devstack env somewhere reno should be in there
20:23:35 openstackgerrit Matt Riedemann proposed openstack/nova master: Skip ceph in grenade live migration job due to restart failures https://review.openstack.org/466097
20:23:36 mriedem sdague: i think i've found a poor man's compromise ^
20:23:44 artom efried, in which case reno --help will help :)
20:24:01 mriedem efried: artom: https://docs.openstack.org/developer/nova/releasenotes.html
20:24:06 efried artom Yeah, found reno --help; it kinda assumes you know what youre doing already.
20:24:10 efried Okay, thank you artom
20:24:16 mriedem the hash is auto-generated
20:24:26 mriedem tox -e venv -- reno new <your reno name>
20:25:01 mriedem dhellmann said he's found that sometimes people copy renos and re-use the same hash which messes things up
20:25:26 efried I guessed that would be a no-no
20:25:33 efried Thanks mriedem & artom
20:25:42 mriedem yeah, plus reviewers wouldn't be able to eyeball that
20:25:58 mriedem seems the reno docs build itself should fail if that happens
21:25:13 openstackgerrit Alex Szarka proposed openstack/nova master: Add method for verify multiple notifications https://review.openstack.org/465526
21:25:33 openstackgerrit Alex Szarka proposed openstack/nova master: [WIP] Transform instance.exists notification https://review.openstack.org/403660
21:33:10 openstackgerrit Monty Taylor proposed openstack/nova master: WIP Show results of nested parameters in api-ref https://review.openstack.org/464277
21:33:10 openstackgerrit Monty Taylor proposed openstack/nova master: WIP Add description of server addresses objects https://review.openstack.org/464331
21:39:32 cfriesen mriedem: you around?
21:40:03 mriedem sort of
21:40:50 cfriesen mriedem: got a weird scenario...upgrades are in progress, one compute node hasn't been upgraded. It gets rebooted without being upgraded and hits exception.ServiceTooOld
21:41:16 cfriesen mriedem: are we just expecting people to upgrade in that case?
21:41:35 openstackgerrit Alex Szarka proposed openstack/nova master: Add method for verify multiple notifications https://review.openstack.org/465526
21:42:34 cfriesen mriedem: actually, thinking about it a bit I'm not clear why the version of that compute node isn't being seen in the DB
21:42:44 openstackgerrit Alex Szarka proposed openstack/nova master: [WIP] Transform instance.exists notification https://review.openstack.org/403660
21:44:01 cfriesen mriedem: maybe the service is still being forced down by our management software, causing its version to be ignored by service_get_minimum_version()
21:45:53 mriedem that's a dansmith question
21:46:50 mriedem cfriesen: it's blowing up here right? https://github.com/openstack/nova/blob/master/nova/objects/service.py#L307
21:47:14 cfriesen mriedem: yep.
21:47:39 cfriesen down in the sql code we ignore the version of "forced-down" services, so maybe that's it
21:49:12 mriedem right this query https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L490
21:50:46 mriedem so all of your other computes are newton, and you've got a mitaka forced-down compute, and you're restarting it and it's blowing up because that mitaka compute is older than the minimum for all of the other computes, which is newton
21:51:38 mriedem so upgrade that compute to newton
21:51:57 cfriesen mriedem: yeah, I'm not certain it's forced down but it's the only thing that makes sense
21:52:06 mriedem do you have the service record from the db?

Earlier   Later