| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-05-05 | |||
| 17:52:52 | dansmith | yeah | |
| 17:56:04 | mriedem | dansmith: armax: didn't this already come up awhile back https://blueprints.launchpad.net/nova/+spec/sriov-bond? | |
| 17:56:07 | mriedem | for trunk ports? | |
| 17:56:38 | armax | I think so | |
| 17:56:42 | armax | that doesn’t sound new | |
| 17:59:05 | knikolla | hey guys. why does the 'deleted' column in block_device_mapping have a number which is not zero or one. which i would expect from a column showing state? we're having to do some database surgery and not sure what value to manually set it to. | |
| 18:01:03 | mriedem | knikolla: that's a legacy bdm v1 thing | |
| 18:01:06 | mriedem | just take the default | |
| 18:01:42 | knikolla | mriedem: so any nonzero number means deleted? | |
| 18:02:33 | knikolla | mriedem: anywhere else we need to clean up for a stuck volume in the nova side of things? | |
| 18:03:03 | mriedem | knikolla: actually sorry i was confusing that with the no_device field | |
| 18:03:15 | mriedem | knikolla: 'deleted' is whether or not it's "soft" deleted in the database, | |
| 18:03:18 | cfriesen | I'm hitting gate-tempest-dsvm failures in https://review.openstack.org/#/c/434514/. Is this a known thing at the moment? | |
| 18:03:20 | mriedem | so deleted=0 means it's not deleted | |
| 18:03:28 | mriedem | knikolla: if it's 'deleted', then deleted=id | |
| 18:03:40 | mriedem | where id is the block_device_mappings.id primary key | |
| 18:05:40 | knikolla | mriedem: i see, thanks a lot! | |
| 18:09:56 | openstackgerrit | Sandeep Pawar proposed openstack/nova master: Libvirt volume driver for Veritas HyperScale https://review.openstack.org/443951 | |
| 18:10:25 | mriedem | armax: yeah this is what i was thinking of https://review.openstack.org/#/c/213644/ | |
| 18:10:46 | armax | mriedem: no I have a diffeent one in mind | |
| 18:10:47 | armax | hang on | |
| 18:11:31 | armax | https://review.openstack.org/#/c/182242/ | |
| 18:11:52 | mriedem | yeah i pointed that one out in the bp | |
| 18:12:06 | armax | mriedem: you always a step ahead of me | |
| 18:51:57 | openstackgerrit | Dan Smith proposed openstack/nova master: DNM: Canary test against multi-cell devstack https://review.openstack.org/458537 | |
| 18:51:57 | openstackgerrit | Dan Smith proposed openstack/nova master: WIP: Debug race in delete-while-booting test https://review.openstack.org/461513 | |
| 18:54:04 | mriedem | hemna: you might need to clarify for these guys https://review.openstack.org/#/c/443951/10/etc/nova/rootwrap.d/compute.filters | |
| 18:56:46 | mriedem | hemna: can all of that root_helper stuff be removed from os-brick? | |
| 19:10:43 | mriedem | melwitt: i think i can say with a high level of confidence, that me starting on the counting quotas series at this time of day on a friday before travel, is not going to happen | |
| 19:13:01 | sdague | dansmith: so... I didn't fully forget about the notes on the boot path. I just did a thing, which might be useful for that (or might not, you tell me), which is annotating a log dump tracing the server build request - https://dague.net//testing/flow.html | |
| 19:13:50 | mriedem | i smell onboarding material | |
| 19:13:53 | dansmith | sdague: that's not unhelpful | |
| 19:15:13 | sdague | mriedem: you have a url pattern you've been using for etherpads for the forum? | |
| 19:15:23 | mriedem | sdague: yeah | |
| 19:15:37 | mriedem | https://wiki.openstack.org/wiki/Forum/Boston2017 | |
| 19:15:38 | sdague | dansmith: ok... well, is that enough of a bit of backing material to feel comfortable that we've got notes? | |
| 19:15:42 | mriedem | BOS-forum-... | |
| 19:15:51 | mriedem | BOS-forum-nova-project-onboarding | |
| 19:15:54 | dansmith | sdague: that's probably way too much detail to talk through, but if you cut it down to your notes, and then remove/rename some, that'd be a good skeleton | |
| 19:15:58 | mriedem | sdague: in fact https://etherpad.openstack.org/p/BOS-forum-nova-project-onboarding | |
| 19:16:24 | dansmith | sdague: if we don't have something to draw on, we could project that and handwave through it | |
| 19:16:27 | mriedem | sdague: maybe you just want to push all of that crap down to the way bottom and do your things at the top | |
| 19:16:28 | sdague | dansmith: yeh, I don't think we'd actually write that up there, it's just backing material | |
| 19:16:55 | dansmith | yeah | |
| 19:17:10 | sdague | mriedem: did you discover if we have flipboard? | |
| 19:17:57 | mriedem | i didn't get a definitive answer no | |
| 19:18:14 | sdague | you all and your friday double negatives | |
| 19:18:33 | dansmith | I don't not know what you mean | |
| 19:18:33 | mriedem | i didn't not get no answer | |
| 19:19:15 | mriedem | i believe i was told i'd get a $20 and could deal with it myself - as a joke, but maybe not totally | |
| 19:19:32 | mriedem | i'm calling the foundations' HR dept as we speak | |
| 19:19:38 | sdague | .... deep breaths.... | |
| 19:19:49 | mriedem | was just told the request was made so they should be there | |
| 19:20:00 | dansmith | I will feel less bad about squandering the time if not provided with any tools to conduct something useful | |
| 19:21:38 | sdague | mriedem: ok, my inclination is to move that existing etherpad to -ideas, make official one include a Questions section at the bottom. Encourage people to enter there questions while we are talking, and we can use that as fodder as we go. | |
| 19:22:00 | sdague | but I don't want to stomp toes here | |
| 19:22:44 | mriedem | as far as i'm concerned you're running this onboarding show | |
| 19:22:46 | mriedem | so go nuts | |
| 19:22:50 | mriedem | like i said, i don't get there until noon | |
| 19:23:23 | mriedem | looking at your flow page, we shouldn't be creating a port twice, | |
| 19:23:39 | mriedem | but we do POST a port and then PUT (update it with the host binding) later | |
| 19:24:14 | dansmith | sdague: is that rst? | |
| 19:24:24 | sdague | dansmith: I have rst | |
| 19:24:42 | dansmith | can I have rst? | |
| 19:24:43 | sdague | https://dague.net//testing/flow.rst | |
| 19:24:57 | sdague | I can also stick this in a throw away git repo if you want | |
| 19:24:59 | mriedem | sdague: i only see "POST /v2.0/ports.json" once | |
| 19:25:10 | dansmith | thanks, I'll try to trim it | |
| 19:25:10 | sdague | mriedem: yeh, my bad, I glossed over | |
| 19:25:21 | openstackgerrit | Eric Fried proposed openstack/nova master: nova.utils.get_service_url() https://review.openstack.org/458257 | |
| 19:25:28 | sdague | dansmith: how about I do an import into a git repo | |
| 19:25:50 | dansmith | sdague: that seems entirely overkill to me, but as you wish | |
| 19:25:52 | mriedem | i'm not sure what this is: May 05 14:12:54 os4 neutron-server[24158]: DEBUG neutron.api.v2.base [req-8b4ccea7-1462-43cc-9a21-f0013b797999 demo demo] Request body: {u'port': {u'network_id': u'8356212e | |
| 19:26:58 | mriedem | "neutron-server starts building that network:" isn't actually building a network | |
| 19:27:03 | mriedem | it's finding the available network for the project | |
| 19:27:06 | mriedem | on which to create the port | |
| 19:27:21 | mriedem | we'd only create a network if we use the auto-allocated-topology (get me a network) stuff | |
| 19:27:35 | dansmith | sounds like mriedem wants to trim it | |
| 19:27:43 | mriedem | i don't, | |
| 19:27:45 | mriedem | i just want to nit pick it | |
| 19:28:10 | mriedem | i'll go back to reading the thread about stable branch LTS and n-5 upgrade support | |
| 19:28:25 | sdague | dansmith: what's your github id again? | |
| 19:28:29 | dansmith | kk7ds | |
| 19:28:52 | sdague | https://github.com/sdague/nova-boot-flow | |
| 19:28:55 | sdague | you have commit | |
| 19:29:03 | sdague | mriedem: if you want so as well | |
| 19:29:40 | sdague | dansmith: I was trying to keep all the logs around, just build the summaries when appropriate, so if you go to trim, how about just getting rid of some summaries | |
| 19:33:10 | dansmith | sdague: yeah, I meant trim the summaries, not the log lines | |
| 19:33:12 | dansmith | trim and edit the summaries I mean | |
| 19:35:50 | sdague | dansmith: have at, you should have full write on that repo | |
| 19:36:43 | dansmith | sdague: okay, I'm still scrambling with other stuff but I'll try | |
| 19:36:48 | dansmith | I guess that would be easy to do on the plane | |
| 19:36:56 | sdague | dansmith: yep, being git and all | |
| 19:41:01 | cdent | mriedem: maybe you should throw some downgrade support hand grenades into that thread | |
| 19:44:51 | mriedem | jesus | |
| 19:44:58 | mriedem | the features vs stability thing drives me nuts | |
| 19:45:13 | mriedem | no one mentioned how we talked about non-feature bug fix only releases once | |
| 19:45:43 | mriedem | 'openstack doesn't / can't scale', ok we'll work on that, 'but you're working on it makes the transition hard and complex and that pisses me off' | |
| 19:46:18 | mriedem | it's just easier to not say anything at all in these threads because they pop up every 3-6 months and die on the vine anyway | |
| 19:46:53 | mriedem | i did see cells v2 and placement get run through the mud a few times though, that's fun | |