Earlier  
Posted Nick Remark
#openstack-nova - 2017-03-09
10:14:57 bauzas owalsh is one of our top-notch engineers responsible for integrating Nova features into TripleO
10:15:04 johnthetubaguy I don't see any logs about what is going wrong, I guess
10:15:21 bauzas the problem I have is that I'm blind of the left problems
10:15:38 johnthetubaguy yeah, same
10:15:44 asettle bauzas: awesome :)
10:15:48 bauzas I would love to see what's missing or still having problems so we could discuss on what's wrong
10:15:51 johnthetubaguy there is no info to help debug the issues, apart from go reproduce it I guess
10:16:06 johnthetubaguy and hope you see the same problem
10:16:09 asettle johnthetubaguy: pretty much. I'm still going to reach out to the ML to get some reviews and help outside of the nova team.
10:16:11 asettle What else can I do?
10:16:24 johnthetubaguy if we could get logs from bmoss, that would really help us
10:16:29 asettle Brian has gone to bed, and Amy (spotz) who is the other person experiencing the issue won't be up for a bit (Austin)
10:16:30 bauzas upstream documentation is one thing, deployment procedures for a specific tool is another
10:16:38 asettle johnthetubaguy: let me try and contact him. I know in theory he's awake.
10:17:02 johnthetubaguy OK, I don't want to get him out of bed, just saying we don't really have anything to work on here
10:17:08 asettle bauzas: very much so. andymccr offered to help too as he got it working in OSA. But I'm not too sure how mcuh it would help or not (I mean, I ain't knocking hte offer back)
10:17:09 bauzas so, here, we could try to see what are the discrepancies between upstream docs and how TripleO gates nova
10:17:11 asettle Nah, it's only 8pm there
10:17:13 asettle Uno momenot
10:17:29 bauzas asettle: you're EU based ?
10:17:35 asettle bauzas: yes, London :)
10:17:37 bauzas okay
10:17:44 bauzas owalsh is Irish and I'm French
10:17:54 asettle Excellent :D
10:17:54 bauzas so we can somehow sort that out
10:17:58 andymccr yeah if we compare it to OSA or TripleO we should be able to get it going
10:18:11 bauzas not sure it's excellent to be French, but meh :p
10:18:19 johnthetubaguy well, can compare it to the in tree docs too
10:18:19 asettle I am happy to spin up an instance and start replicating if I can't get bmoss to give me his error logs rn
10:18:23 asettle bauzas: it's pretty great right now :P
10:19:11 bauzas so, the question I have is
10:19:22 johnthetubaguy andymccr: did we get that ordering issue sorted?
10:19:27 bauzas without using a deployment tool, are we able to spin up an instance by following the upstream documentation ?
10:19:36 bauzas and if not, what is the error ?
10:19:44 asettle bauzas: that's basically the problem. No, we cannot.
10:19:51 asettle spotz experienced this, and so did bmoss
10:20:00 johnthetubaguy using the install guide, it doesn't work right now, right?
10:20:02 bauzas asettle: do you have ways to reproduce that so you could throw me the exception ?
10:20:04 asettle I've just text Brian now to see if he can shoot me his logs (I'm sure his wife will be hatin')
10:20:06 andymccr johnthetubaguy: yes sir - we now do a "api_db version" before attempting the sync - if it's 0 --> sync, if it's not --> don't sync just create cell.
10:20:21 andymccr (and sync later)
10:20:30 asettle bauzas: not at the moment, no. Will work on getting you more information. I don't have the instance up, Brian does. Let me get back to you :)
10:20:47 asettle (I hope?)
10:20:51 bauzas Brian is ET-based ?
10:20:55 asettle bauzas: Australia
10:21:01 bauzas meh okay
10:21:07 asettle So, complete opposite timezone.
10:21:12 bauzas not sure we could get him
10:21:26 johnthetubaguy andymccr: I wonder if the docs have that issue, they seem to not do api_db sync
10:21:37 asettle It's after 8pm - not too late.
10:21:42 andymccr johnthetubaguy: hmm maybe
10:21:53 andymccr johnthetubaguy: on a new build you need it first
10:23:28 asettle bauzas: he's awake ;) he's just turning on his computer to send me the logs for you
10:23:54 asettle "I updated the patch (with the comments from mriedem_away) but haven't tested the revision yet. I'll send you my nova logs."
10:24:00 asettle So, hopefully we can see what the original problem was, and move from there.
10:24:09 bauzas \o/
10:24:16 bauzas I'll have to bail out for a couple of hours
10:24:34 bauzas but I'll be back around 1pm UTC
10:24:55 asettle bauzas: no problem :) thank you for offering ot help. I've sent out to the ML too. Hopefully we can get some people looking at it too.
10:26:08 asettle Sorry andymccr and johnthetubaguy - not ignoring you both :P
10:26:15 asettle Getting the error logs from bmoss rn
10:28:43 asettle Ugh *head desk*
10:28:48 asettle And it was such a nice day too
10:29:57 bauzas alex_xu: around ?
10:30:20 bauzas alex_xu: not understood your point in https://review.openstack.org/#/c/440580/3/specs/pike/approved/scheduler-hints-in-server-details.rst@34
10:30:52 johnthetubaguy asettle: do we tell people to always install the controller first, and then the compute node?
10:31:47 bauzas "controller" is a pure non-nova thing :)
10:31:50 asettle johnthetubaguy: good question, lemme just check historically.
10:31:53 asettle Yes, we do.
10:32:01 johnthetubaguy OK, thats good
10:32:06 bauzas but yeah I remember the old docs, and it's the case
10:32:18 asettle Yep
10:32:22 asettle Controller -> Compute
10:32:27 bauzas asettle: is the problem due to an upgrade or a greenfields install ?
10:32:36 asettle bauzas: greenfields, I believe.
10:32:50 bauzas because instructions are fairly different
10:32:52 asettle We just test the install instructions, we don't test upgrades.
10:32:53 bauzas for cells
10:33:04 asettle bauzas: that documentation for upgrades should belong in the upgrade docs, no?
10:33:11 bauzas asettle: yup
10:33:20 asettle Yes, okay, I'm not going crazy then.
10:33:31 bauzas just wanted to verify that bmoss is following the fresh install procedure, that's it
10:33:59 bauzas because he's pointing to some internal BZ that mentions upgrades and TripleO hence my confusion
10:34:13 bauzas both are totally separate things
10:34:40 asettle bauzas: yes he should be. The whole idea behind doing the install guide testing ist hat you have to do a full manual install (which is also why we don't have people racing to do it)
10:36:19 bauzas yeah, I followed it in 2012 :p
10:36:32 bauzas using .deb packages :blushes:
10:37:11 bauzas glad to see it continuing even if not a lot of people are crazy pants enough to install OpenStack by hand :)
10:37:26 bauzas oh
10:37:35 lyarwood https://review.openstack.org/#/c/391597/ - pretty simple ~1k LOC removal change in favor of os-brick code if anyone has time this morning
10:37:36 bauzas asettle: my reply to your email was bounced
10:37:52 bauzas asettle: because openstack-docs@ is moderated
10:37:57 asettle bauzas: by me!
10:38:00 asettle Let me add you in
10:38:10 bauzas strange, why are you moderating it ?
10:38:14 johnthetubaguy oh, did not know there was a docs ML
10:38:16 asettle bauzas: cause i'm the PTL :p
10:38:31 bauzas well, in general, our lists are open
10:38:32 asettle johnthetubaguy: yeah we're weird like that. I dunno why we have it.
10:38:50 asettle Hence why I added the dev list into it, and the docs for others. I don't know the historical reason we have a separate ML

Earlier   Later