| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-09-05 | |||
| 17:39:33 | sean-k-mooney | dansmith: yes so when we systesize traiths i was suggesting uses a prefix other then custom to do that | |
| 17:39:44 | dansmith | sean-k-mooney: yeah but that does't work | |
| 17:39:53 | dansmith | sean-k-mooney: because anything but a CUSTOM_ is a hard enum in a library | |
| 17:40:02 | dansmith | sean-k-mooney: anything synthesized by the operator or somecode has to be CUSTOM_ | |
| 17:40:40 | sean-k-mooney | dansmith: correct so im suggesting that we extend os tratis to have other prefixes that are not enums. if that is not desirabel then CUSTOM_ works too | |
| 17:41:04 | sean-k-mooney | i just can tell if its created by a person of synthesize by openstack | |
| 17:44:16 | sean-k-mooney | may main concern is that as an enduse i have no way of knowing is CUSTOM_PHYSNET_<XYZ> is special custom trait that casuse a change in the behaior of openstack vs CUSTOM_MY_TRAIT_<XYZ> that does not. | |
| 17:48:13 | sean-k-mooney | anyway got to run. food is calling | |
| 17:55:49 | gvrangan | https://docs.openstack.org/nova/pike Folloed the latest install in centOs7 | |
| 17:55:56 | gvrangan | the hypervisot list is not listing | |
| 17:56:03 | gvrangan | the computes are not added to cells | |
| 17:56:09 | gvrangan | Should the doc be updated? | |
| 18:04:12 | gvrangan | when I execure the discover, the computes are not getting listed | |
| 18:04:29 | gvrangan | should the nova compute be configure differntly in pike? | |
| 18:07:09 | melwitt | gvrangan: which instructions did you follow? this? https://docs.openstack.org/nova/latest/user/cells.html#fresh-install | |
| 18:07:11 | jaypipes | gvrangan: pls see /topic. Best to ask your question on the @openstack mailing list. | |
| 18:08:31 | gvrangan | melwitt, I followed only the nhttps://docs.openstack.org/nova/pike/install/controller-install-rdo.html and https://docs.openstack.org/nova/pike/install/compute-install-rdo.html | |
| 18:11:53 | openstackgerrit | Jackie Truong proposed openstack/python-novaclient master: Microversion 2.54 - Add trusted_certificates param https://review.openstack.org/500396 | |
| 18:13:34 | melwitt | gvrangan: okay. I see all of the commands you need are in those docs. so you have to make sure you see cell0 and cell1 when you do 'nova-manage cell_v2 list_cells' and then make sure you did 'nova-manage cell_v2 discover_hosts --verbose' after you have brought up the compute node | |
| 18:20:28 | rybridges1 | Hello all | |
| 18:20:35 | rybridges1 | I had a quick question about nova cells | |
| 18:21:24 | rybridges1 | We are currently attempting to deploy a fresh ocata cluster. I was wondering if [cells] section of nova.conf is required for cells v2 at all? I read in the comments that the stuff under that section is only for cells v1, but just wanted to make sure | |
| 18:23:19 | melwitt | rybridges1: that's correct. see 4. on the FAQ, [cells] section is not to be used https://docs.openstack.org/nova/latest/user/cells.html#faqs | |
| 18:24:53 | efried | jaypipes We were talking last week about how to model e.g. minimum egreess bandwidth support on SR-IOV VFs. | |
| 18:24:56 | rybridges1 | Okay great! Thanks melwitt | |
| 18:25:08 | jaypipes | efried: who is we? :) | |
| 18:25:25 | efried | dansmith suggested we would model the PF as a RP with e.g. SRIOV_VFS=48,EGRESS_BW_PCT=100 | |
| 18:26:15 | efried | So that basically you would grab some number of VFs and some percentage of the bandwidth, and whichever you exhausted first would take that PF out of the running for subsequent requests, kind of thing. | |
| 18:26:28 | efried | First of all, is this along the lines of what you've been thinking? | |
| 18:27:05 | efried | Doesn't have to be percentage; could be bps or whatever; point is the number of VFs and the total bandwidth are separate but parallel resource classes in the RP. | |
| 18:27:33 | cdent | “parallel”? | |
| 18:27:59 | efried | just meaning that they're RC inventories on the same RP | |
| 18:28:37 | cdent | isn’t that what we do around here? | |
| 18:28:45 | efried | Some of us shouldn't. | |
| 18:29:25 | jaypipes | efried: yep. that's pretty close. I don't like the pct versus using bytes_per_sec but yeah. | |
| 18:29:39 | jaypipes | efried: in fact, that's pretty close to what I had written on the ML, no? | |
| 18:29:47 | efried | jaypipes okay, so help me fill in the gaps here. | |
| 18:30:16 | efried | IRL I'll have multiple PF-y RPs, and let's say they each have both of those RC inventories defined. | |
| 18:30:30 | jaypipes | k | |
| 18:31:14 | efried | When I make a request for, say, SRIOV_VFS=1,EGRESS_BW_PCT=20 -- what's to stop placement from allocating the VF inventory from one RP and the egress bandwidth inventory from another?? | |
| 18:32:47 | openstackgerrit | Mateusz Kowalski proposed openstack/nova stable/pike: Handle keypair not found from metadata server using cells https://review.openstack.org/500953 | |
| 18:32:59 | openstackgerrit | Mateusz Kowalski proposed openstack/nova stable/ocata: Handle keypair not found from metadata server using cells https://review.openstack.org/500954 | |
| 18:36:59 | jaypipes | efried: actually currently stressing out trying to figure out how to deal with this hurricane that is going to hit us. | |
| 18:37:13 | efried | jaypipes Been there, done that. Where you at? | |
| 18:37:26 | jaypipes | efried: and getting my girls to safety and my wife to her plane flight to Italy on Sunday :( | |
| 18:37:33 | jaypipes | efried: Sarasota | |
| 18:38:29 | efried | Totally counts as (b) | |
| 18:40:28 | jaypipes | efried: the answer to your question is: nothing would stop placement from doing so. | |
| 18:40:52 | efried | jaypipes Then... "eek". | |
| 18:40:59 | jaypipes | efried: yeah | |
| 18:41:37 | efried | The followup, of course, is what about SRIOV_VFS=4,EGRESS_BW_PCT=20 ? | |
| 18:42:11 | jaypipes | efried: we would need to add some mechanism to the request that says "make sure the thing providing EGRESS_BW_PCT and SRIOV_VF is the same provider. | |
| 18:42:44 | efried | jaypipes Rojah dat. Any thoughts been assayed in that regard to this point? | |
| 18:43:39 | melwitt | mriedem: I'm gonna sign up for that nova project update redhat interview thing at the PTG | |
| 18:44:05 | jaypipes | efried: resource_constraints=same_provider:SRIOV_NET_VF,NET_EGRESS_BYTES_SEC&resources=SRIOV_NET_VF:1&NET_EGRESS_BYTES_SEC:20000 | |
| 18:44:06 | mriedem | melwitt: awesome | |
| 18:44:53 | openstackgerrit | Merged openstack/nova master: Replace dd with shred for zeroing lvm volumes. https://review.openstack.org/495532 | |
| 18:46:35 | efried | jaypipes What stage is that semantic in? Just popped out of your head, in a spec somewhere, implemented, released? | |
| 18:48:20 | jaypipes | efried: popped off the top of my thick, oh so thick, head of hair. | |
| 18:48:30 | melwitt | mriedem: let me know if there's anything else you'd like me to highlight other than cells and placement. I was gonna go through the rel notes and dev ML announcements to see what else to mention | |
| 18:49:10 | efried | jaypipes Cool, will add it to discussion points. | |
| 18:49:10 | melwitt | and then I'll use the nova PTG etherpad to summarize what's coming up in queens | |
| 18:49:46 | efried | I still need to complete my reading, but presumably there's a syntax for requesting multiple different resources of the same class with different traits? | |
| 18:51:26 | efried | jaypipes So like, pursuant to the anti-affinity grouping conversation avolkov and I were having earlier, I want to be able to say gimme (SRIOV_NET_VF:1&NET_EGRESS_BYTES_SET:2000&traits=CUSTOM_PF_HA_GROUP_1; SRIOV_NET_VF:1&NET_EGRESS_BYTES_SET:2000&traits=CUSTOM_PF_HA_GROUP_2) | |
| 18:51:36 | mriedem | melwitt: i can send you my list that i sent internally | |
| 18:52:15 | melwitt | mriedem: cool, I think that would be helpful. thanks | |
| 18:54:41 | jaypipes | efried: lemme pastebin something for that | |
| 18:54:43 | prometheanfire | this look like an error with the os-xenapi bump? http://logs.openstack.org/70/500770/3/check/gate-cross-nova-python27-ubuntu-xenial/1305547/testr_results.html.gz | |
| 18:54:50 | prometheanfire | from https://review.openstack.org/500770 | |
| 18:55:44 | mriedem | prometheanfire: looking | |
| 18:56:20 | openstackgerrit | Michael Still proposed openstack/nova master: Move nbd commands to privsep. https://review.openstack.org/500351 | |
| 18:56:21 | openstackgerrit | Michael Still proposed openstack/nova master: Move xend existence probes to privsep. https://review.openstack.org/495538 | |
| 18:56:21 | openstackgerrit | Michael Still proposed openstack/nova master: Move lvm handling to privsep. https://review.openstack.org/495516 | |
| 18:56:22 | openstackgerrit | Michael Still proposed openstack/nova master: Cleanup mount / umount and associated rmdir calls https://review.openstack.org/494423 | |
| 18:56:22 | openstackgerrit | Michael Still proposed openstack/nova master: Move shred to privsep. https://review.openstack.org/495537 | |
| 18:56:23 | openstackgerrit | Michael Still proposed openstack/nova master: Move loopback setup and removal to privsep. https://review.openstack.org/495664 | |
| 18:56:23 | openstackgerrit | Michael Still proposed openstack/nova master: WIP / Aspirational: we don't need rootwrap any more. https://review.openstack.org/495542 | |
| 18:56:26 | openstackgerrit | Michael Still proposed openstack/nova master: Move libvirt usages of chown to privsep. https://review.openstack.org/471972 | |
| 18:56:27 | openstackgerrit | Michael Still proposed openstack/nova master: Don't shell out to mkdir, use ensure_tree() https://review.openstack.org/492326 | |
| 18:56:28 | openstackgerrit | Michael Still proposed openstack/nova master: Move ploop commands to privsep. https://review.openstack.org/492325 | |
| 18:56:28 | openstackgerrit | Michael Still proposed openstack/nova master: Move the idmapshift binary into privsep. https://review.openstack.org/495541 | |
| 18:56:30 | openstackgerrit | Michael Still proposed openstack/nova master: Read from console ptys using privsep. https://review.openstack.org/489486 | |
| 18:56:31 | openstackgerrit | Michael Still proposed openstack/nova master: Move kpartx calls to privsep. https://review.openstack.org/500354 | |
| 18:56:35 | openstackgerrit | Michael Still proposed openstack/nova master: Avoid chowning console logs in libvirt https://review.openstack.org/472229 | |
| 18:56:36 | openstackgerrit | Michael Still proposed openstack/nova master: First attempt at adding a privsep user to nova itself. https://review.openstack.org/459166 | |
| 18:56:38 | prometheanfire | mriedem: that's a quick git-review you have there (or rebase maybe) | |
| 18:56:38 | openstackgerrit | Michael Still proposed openstack/nova master: Move execs of touch to privsep. https://review.openstack.org/489190 | |
| 18:56:39 | openstackgerrit | Michael Still proposed openstack/nova master: Move blkid calls to privsep. https://review.openstack.org/500398 | |
| 18:56:39 | openstackgerrit | Michael Still proposed openstack/nova master: Move libvirts dmcrypt support to privsep. https://review.openstack.org/490737 | |
| 18:56:41 | openstackgerrit | Michael Still proposed openstack/nova master: Move execs of tee to privsep. https://review.openstack.org/489438 | |
| 18:56:53 | prometheanfire | bah, meant that for michael | |
| 18:57:41 | openstackgerrit | Merged openstack/nova master: Updated from global requirements https://review.openstack.org/500011 | |
| 18:57:46 | efried | prometheanfire git restack, yo. | |
| 18:58:09 | prometheanfire | what that come from? | |
| 18:58:22 | efried | It's a thing, hold on... | |
| 18:59:19 | efried | prometheanfire I think you install it with `pip install git-restack` | |
| 18:59:44 | efried | It's a git plugin maintained by stackers | |
| 19:00:49 | mriedem | prometheanfire: looks like this is the regression https://github.com/openstack/os-xenapi/commit/755876c19f7c47eaa773f835a68dcf93c3d6b50d | |
| 19:01:14 | efried | prometheanfire You say `git restack <commit-before-the-bottom-of-the-pile>`. Then you can choose to edit whichever ones in the chain via an edit file that looks kinda like when you rebase -i. It auto rebases everything in the pile. Then when you're done, you can `git review` and it pushes the whole pile (anything that has been changed, including rebases) | |
| 19:01:55 | prometheanfire | mriedem: k, so nova needs to update it's tests? | |