| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-08-01 | |||
| 16:40:55 | jaypipes | ok with me | |
| 16:40:57 | mriedem | but if you're ready like now then i can wait | |
| 16:41:18 | jaypipes | mriedem: please proceed. | |
| 16:41:57 | mriedem | done | |
| 16:43:00 | cdent | jaypipes: has a plan (for migrations) distilled out of today’s conversations yet, or is that still pending? | |
| 16:43:32 | jaypipes | cdent: 1707071 is the primary bug I'm tracking right now. | |
| 16:44:29 | cdent | jaypipes: yes, but I thought any potential solutions to that impinge on the wider migration picture? | |
| 16:45:06 | jaypipes | cdent: not quite following you on that... | |
| 16:47:30 | cdent | jaypipes: maybe I misunderstood your answer to my question. Are you saying “yes, that’s what 1707071 is about” or “no, I’m focused on the details of making sure that we create the right allocations”? Looks like the former? | |
| 16:48:05 | jaypipes | cdent: I'm focused on trying to not have Pike compute node RTs fight each other writing and overwriting allocation records. | |
| 16:48:06 | cdent | Earlier today you said that overnight you fought with the code enough to think that you had to rejigger everything again. | |
| 16:48:42 | jaypipes | cdent: what I said earlier we mostly referring to needing to essentially put a bunch of conditionals in to keep being broken for Ocata compute hosts migrating to Pike compute hosts. | |
| 16:49:43 | cdent | So sounds like you have some kind of plan. That’s great. As before, if there’s something I can do, let me know. | |
| 16:50:14 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Accept any scheduler driver entrypoint https://review.openstack.org/484828 | |
| 16:50:17 | openstackgerrit | Eric Fried proposed openstack/nova master: DNM: Refactor get_endpoint_data to accept service_type https://review.openstack.org/489666 | |
| 16:50:28 | jaypipes | cdent: will do. | |
| 16:56:16 | bks | Hi all, i wanted to run a clou-init script in centos 6.6 os to change the root password, can someone please pass me the cloud-init to do it. Thanks | |
| 16:56:34 | cfriesen_ | in Newton would we expect a deleted instance (which is in the "instances" table) to always have an entry in instance_extra? | |
| 16:56:59 | bks | and is used_data option is used in the nova create server api to pass the cloud-init? | |
| 16:57:18 | bks | can someone please help me here | |
| 16:58:04 | cfriesen_ | bks: your question should probably be asked on #openstack | |
| 17:00:19 | bks | @cfriesen_ i asked there too, no response | |
| 17:00:54 | openstackgerrit | Rodolfo Alonso Hernandez proposed openstack/os-vif master: Add ``HostPortProfileInfo`` class https://review.openstack.org/441590 | |
| 17:02:08 | mriedem | yes user_data is passed through to cloud-init | |
| 17:02:12 | cfriesen | bks: many of the nova folks are busy with release-critical stuff. have you looked at: http://blog.scottlowe.org/2015/11/09/changing-passwords-cloud-init/ | |
| 17:05:03 | bks | @cfriesen ohh sorry, iam trying the same script but couldnot get it worked | |
| 17:05:37 | bks | @cfriesen the userdata option in createserver is used to pass the cloud-init? | |
| 17:06:06 | bks | as mentioned in the https://developer.openstack.org/api-ref/compute/#create-server | |
| 17:06:54 | mriedem | https://github.com/openstack/openstack-manuals/blob/stable/ocata/doc/user-guide/source/cli-config-drive.rst | |
| 17:08:53 | cburgess | Because.....? | |
| 17:10:29 | openstackgerrit | Eric Fried proposed openstack/nova master: Adopt new pypowervm power_off APIs https://review.openstack.org/476945 | |
| 17:20:21 | openstackgerrit | Jackie Truong proposed openstack/nova master: Add trusted_certs to instance_extra https://review.openstack.org/457711 | |
| 17:42:44 | openstackgerrit | Matt Riedemann proposed openstack/nova master: WIP: See if we can squash ComputeHostNotFound_Remote on startup https://review.openstack.org/489683 | |
| 17:42:50 | mriedem | dansmith: ^ destroys unit tests for the objects b/c of the fake indirection api, but is that something that's even possible? ^ | |
| 17:43:26 | mriedem | i want to get rid of these http://logs.openstack.org/54/487954/5/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/4412f5d/logs/screen-n-cpu.txt.gz?level=TRACE#_Jul_28_19_41_38_466972 | |
| 17:43:37 | dansmith | mriedem: no because those aren't actually the rpc calls | |
| 17:43:45 | cdent | Is stephenfin around this week, I sense his absence | |
| 17:43:46 | dansmith | well, I'm guessing that won't work because ^ | |
| 17:43:57 | mriedem | cdent: i'm told he's back tomorrow | |
| 17:44:04 | cdent | thanks mriedem | |
| 17:45:48 | dansmith | mriedem: that line you quote is intentional log.warning in the libvirt driver | |
| 17:46:02 | dansmith | mriedem: and it looks like we're getting a stack trace automagically from the logging layer (?) | |
| 17:46:05 | mriedem | i know, but the trace is coming from oslo.messaging isn't it? | |
| 17:46:11 | dansmith | no I don't think so | |
| 17:47:06 | dansmith | mriedem: see the line below.. you need exc_info=False maybe ? | |
| 17:47:09 | dansmith | maybe a default changed somehow? | |
| 17:47:12 | dansmith | oh | |
| 17:47:14 | dansmith | ooooh | |
| 17:47:17 | dansmith | you're hitting the lower one | |
| 17:47:19 | dansmith | with exc_info=True | |
| 17:47:25 | dansmith | because it is _Remote | |
| 17:47:52 | mriedem | dansmith: yeah there is that, | |
| 17:47:54 | dansmith | so maybe in that handler, check the exception name and if it looks remoteish then you can not pass the exc_info flag? | |
| 17:47:57 | mriedem | but that doesn't explain this one http://logs.openstack.org/54/487954/5/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/4412f5d/logs/screen-n-cpu.txt.gz?level=TRACE#_Jul_28_19_41_40_927881 | |
| 17:47:59 | dansmith | it's a little icky | |
| 17:48:33 | mriedem | https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L6624 | |
| 17:48:40 | mriedem | oh well, | |
| 17:48:51 | mriedem | maybe we don't hit that code b/c of the same thing? | |
| 17:49:45 | dansmith | well, you log that message, so it seems like you are | |
| 17:49:50 | dansmith | not sure why you get a trace there then | |
| 17:49:53 | mriedem | but where does the traceback come from? | |
| 17:49:54 | mriedem | right | |
| 17:50:28 | dansmith | unless a default has changed and oslo now logs a trace if you're in exception context | |
| 17:51:22 | dansmith | boy that sure is ugly | |
| 17:51:51 | mriedem | been this way since ocata | |
| 17:52:13 | trinaths | hi, I'm hitting this error, when i start nova-compute, http://paste.openstack.org/show/617156/ | |
| 17:52:16 | openstackgerrit | Sumedh Degaonkar proposed openstack/nova master: Adds 'sata' as a valid disk bus for qemu and kvm hypervisors https://review.openstack.org/459794 | |
| 17:52:22 | trinaths | please help me resolve the same. | |
| 17:58:39 | sdague | mriedem: actually, looking at sfinucan's split up of docs, I'm really not convinced that https://review.openstack.org/#/c/478485/ is a good move | |
| 18:00:17 | mriedem | http://docs-draft.openstack.org/85/478485/16/check/gate-nova-docs-ubuntu-xenial/481415d//doc/build/html/ | |
| 18:00:17 | mriedem | sdague: ... i said it was a massive change | |
| 18:00:36 | mriedem | compared to how things used to be https://docs.openstack.org/nova/ocata/ | |
| 18:00:37 | sdague | mriedem: yeh | |
| 18:00:39 | mriedem | i can't even really review it | |
| 18:00:53 | mriedem | asettle is also working on that patch | |
| 18:00:59 | sdague | honestly, I mostly want to light docs like that on fire | |
| 18:01:17 | sdague | because you have to know what you are looking for before you can find what you are looking for | |
| 18:01:44 | mriedem | wait which thing do you want to light on fire? | |
| 18:02:29 | sdague | spliting up the process doc into 6 process docs | |
| 18:02:52 | sdague | http://docs-draft.openstack.org/85/478485/16/check/gate-nova-docs-ubuntu-xenial/481415d//doc/build/html/contributor/process.html | |
| 18:03:14 | mriedem | compared to https://docs.openstack.org/nova/ocata/process.html ? | |
| 18:03:24 | sdague | yes | |
| 18:06:23 | mriedem | idk if this is meant to be consistent with other projects, but it's not consistent with cinder's home page now | |
| 18:06:31 | mriedem | https://docs.openstack.org/cinder/latest/ | |
| 18:06:41 | mriedem | or glance https://docs.openstack.org/glance/latest/ | |
| 18:13:16 | sdague | it would be nice to figure out how we get in page toc into the sidebar instead of top of page | |
| 18:13:34 | mriedem | yes that's also been annoying me | |
| 18:14:28 | sdague | dhellman might know | |
| 18:14:34 | sdague | looks like glance does it | |
| 18:16:56 | mriedem | sdague: any idea how we figure out which log formatter/handler we're using in a devstack run? | |
| 18:17:05 | mriedem | like, are those configurable somewhere? | |
| 18:18:10 | sdague | mriedem: ?? | |
| 18:18:24 | mriedem | well there is a json formatter, and a context formatter | |
| 18:18:33 | sdague | yes, we're using the context formatter | |
| 18:18:38 | mriedem | and a color handler, and journal and syslog handler | |
| 18:18:43 | mriedem | but how would someone know? | |
| 18:18:47 | mriedem | config? | |
| 18:19:27 | sdague | it's config, but I think those are the defaults | |
| 18:20:55 | sdague | oh, you know what it is, it's actually python logging config | |
| 18:20:59 | sdague | outside of our config | |