| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-11-21 | |||
| 20:40:20 | mriedem | not breakable at all! | |
| 20:40:28 | dansmith | so a new incompatible syntax for ... something you can already do but shouldn't | |
| 20:40:29 | dansmith | hah right | |
| 20:40:31 | mriedem | i also didn't know that % pre-dated format() | |
| 20:40:34 | mriedem | i prefer % | |
| 20:40:51 | dansmith | me too, because I'm old school | |
| 20:41:07 | dansmith | I've been doing python since before .format and since before you saw the non-java light, whippersnapper | |
| 20:41:44 | mriedem | hey, now we're both losers because there is go: java for python people | |
| 20:41:55 | dansmith | heh | |
| 20:41:56 | dansmith | indeed | |
| 20:41:59 | mriedem | umm, + pointers | |
| 20:44:05 | mriedem | f strings also looks like you can run functions from within strings, which .... | |
| 20:44:08 | mriedem | seems like erlang? | |
| 20:44:27 | dansmith | you can definitely hit dictionaries, which seems borderline evil | |
| 20:44:34 | dansmith | running functions and you're nearly bash | |
| 20:45:19 | dansmith | I also don't like the single-char prefix to a quoted string syntax python seems to love | |
| 20:45:29 | dansmith | u"foo", r"bar", etc | |
| 20:46:01 | dansmith | and all these new kids with their hoverboards and roller skates...*fist* | |
| 20:46:51 | melwitt | mriedem: replied. no strong opinion here | |
| 20:47:02 | melwitt | I'm cool with whatever you think is best | |
| 20:47:03 | mriedem | melwitt: but what's your take on f-strings?! | |
| 20:47:08 | melwitt | lol | |
| 20:47:14 | mriedem | f'em right?! | |
| 20:47:23 | melwitt | I didn't know what f-strings is yet so I'm way ahead of the game | |
| 20:47:36 | mriedem | i learned <1 hour ago | |
| 20:47:40 | melwitt | I read a few of the posts and had no idea what was going on | |
| 20:47:56 | melwitt | and of course, I didn't read the first one, cause BORING | |
| 20:48:04 | melwitt | jk | |
| 20:48:42 | melwitt | I mean, I really didn't read it but not because it was boring. once I saw replies piling up I read a few | |
| 20:52:41 | artom | Hates, even | |
| 20:54:42 | melwitt | I think we all do. I've been thinking about how nice it would be to refactor those things in a non-boil the ocean way. somehow. | |
| 20:54:57 | dansmith | I don't | |
| 20:54:59 | dansmith | I love it | |
| 20:55:00 | dansmith | LOVE | |
| 20:55:07 | melwitt | :) | |
| 20:56:32 | artom | Microversion 2.whatever "support for resize, cold migration, and rebuild is dropped" | |
| 20:56:39 | artom | Rewrite everything from scratch | |
| 20:56:57 | artom | Microversion 2.whatever+1 "Nova now supports resize, cold migration, and rebuild" | |
| 20:57:15 | melwitt | lol, nah just leave em out | |
| 20:57:28 | artom | Hah, yeah, just conveniently forget step 3 | |
| 20:57:35 | artom | Or step 2, even | |
| 20:58:09 | mriedem | artom: how are rebuild and resize/cold migrate intertwined? | |
| 20:58:14 | efried | Nova meeting in 2 minutes in #openstack-meeting | |
| 20:58:24 | artom | mriedem, through sheer willpower and anger | |
| 20:58:25 | efried | mriedem: they're not, rebuild and evacuate are the same thing though. | |
| 20:58:37 | mriedem | don't make me link the doc i wrote again | |
| 20:58:41 | artom | OK, resize and cold migrate then | |
| 20:58:45 | artom | Mea culpa | |
| 20:59:14 | mriedem | ok so write a resize vs cold migrate doc like this https://docs.openstack.org/nova/latest/contributor/evacuate-vs-rebuild.html | |
| 20:59:15 | mriedem | easy | |
| 20:59:24 | mriedem | 1. resize has a new flavor, cold migrate doesn't, | |
| 20:59:31 | gregwork | does nova in queens understand how to boot instances on a particular host aggregate? ive tried tagging the host aggregate "compute = 1" and then passing scheduler_hints: compute: 1 when deploying a stack with OS::Nova::Server .. however that doesnt appear to do anything and the instances ends up on whatever compute node | |
| 20:59:36 | mriedem | 2. resize can sometimes go on the same host, cold migrate does not except if you're using vcenter | |
| 21:00:05 | mriedem | artom: what other differences are there besides those 2 things? | |
| 21:00:16 | melwitt | gregwork: has to be availability zone. host agg is a admin only hidden thing | |
| 21:00:36 | artom | mriedem, I think that's about it? | |
| 21:00:47 | artom | And resize to same host is user-configurable | |
| 21:00:52 | gregwork | melwitt: oh .. so even if the admin has defined the host agg, regular users cant reference it ? | |
| 21:00:53 | mriedem | JESUS THEY ARE SO INTERTWINED!!! | |
| 21:00:54 | artom | Cold migrate is... always to a new host? | |
| 21:01:02 | mriedem | artom: you mean operator configurable... | |
| 21:01:03 | artom | mriedem, just... let me be angry | |
| 21:01:07 | artom | mriedem, sorry, yeah | |
| 21:01:19 | artom | I meant in the code, anyways | |
| 21:01:22 | mriedem | artom: remember https://review.opendev.org/#/c/676022/ | |
| 21:01:26 | melwitt | gregwork: they can but only by way of a AZ. you have to make one and map it to the aggregate(s) you want (as admin) | |
| 21:01:36 | artom | Like, you hit a method called "_cold_migrate" in the resize flow | |
| 21:01:52 | mriedem | yeah, so docstrings ftw | |
| 21:01:52 | artom | mriedem, I do | |
| 21:02:05 | mriedem | -1 people that don't write code comments | |
| 21:02:13 | gregwork | melwit: from reading up on AZ's in openstack, these seem like a very heavy abstraction compared to a simple host aggregate to configure | |
| 21:02:19 | mriedem | be the change you want to see in the world... | |
| 21:02:48 | artom | But how do I become free limitless beer? | |
| 21:02:58 | artom | (Point taken, though) | |
| 21:03:13 | melwitt | gregwork: they're really just a tag on host aggregates. shouldn't be heavy. you put tag my_az on the host aggs you want to be part of it and then the user can say my_az | |
| 21:03:46 | mriedem | artom: so if you want to see some things in a contributor doc about resize vs cold migrate, throw those into a doc bug and maybe i can crank something out | |
| 21:16:49 | melwitt | gregwork: sorry that link was for admin user to be able to bypass the scheduler. this is the normal end user instructions for how to specify AZ https://docs.openstack.org/nova/latest/user/availability-zones.html | |
| 21:20:20 | artom | mriedem, I think that I'd really at this point is a sequence diagram for resize (to start with), like we have for live migration | |
| 21:21:02 | artom | Btw, stephenfin, who gave me https://review.opendev.org/#/c/662522/, I will forever remember that | |
| 21:21:27 | artom | My fault for opening my mouth and saying I have extra bandwidth, I suppose | |
| 21:21:50 | mriedem | i had an old todo somewhere to do a resize diagram like the live migrate one i put on a post-it and efried turned into that diagram | |
| 21:21:54 | mriedem | and then got the nickel 3 years later | |
| 21:22:24 | mriedem | artom: fwiw i do have a simple resize diagram in my last cells v2 summit presentation, you could lift the slides from that and turn it into what seqdiag stuff in sphinx | |
| 21:23:00 | mriedem | https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c087f27a43eea/www-assets-prod/summits/26/presentations/23287/slides/Whats-new-in-Nova-CellsV2-Denver-Summit-2019.pdf | |
| 21:23:21 | mriedem | slide 26 | |
| 21:25:22 | artom | mriedem, much thanks | |
| 21:26:06 | gregwork | hmmn "Cannot update metadata of aggregate 11: Reason: One or more hosts already in availability zones [u'nova'] | |
| 21:29:56 | mriedem | i've noticed that artom has the same disappearing pattern as bauzas | |
| 21:30:03 | mriedem | t0: complain! | |
| 21:30:06 | mriedem | t1: here you can do this | |
| 21:30:12 | mriedem | t2: thanks! but i've got to run | |
| 21:31:54 | gregwork | alright nm i think i got it .. | |
| 21:32:17 | mriedem | gregwork: hosts can be in M aggregates but 1 AZ | |
| 21:32:43 | gregwork | yeah i had created an aggregate and already tagged it as nova | |
| 21:32:47 | gregwork | for the az | |
| 21:32:59 | gregwork | so adding an additional az was failing | |
| 21:33:32 | gregwork | now to figure out what the scheduler_hint is to specify the az in OS::Nova::Server | |
| 21:33:40 | gregwork | i dont think its group: | |
| 21:34:19 | mriedem | there is a big fat warning in the docs to not ever create an az literally called "nova" | |
| 21:34:33 | mriedem | b/c that's the default schedule zone for services, | |