14:00:50 <tellesnobrega> #startmeeting sahara
14:00:50 <openstack> Meeting started Thu Jun 29 14:00:50 2017 UTC and is due to finish in 60 minutes.  The chair is tellesnobrega. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:55 <openstack> The meeting name has been set to 'sahara'
14:00:58 <tosky> o/
14:01:00 <jeremyfreudberg> o/
14:01:11 <jeremyfreudberg> ::q
14:01:29 <jeremyfreudberg> oops, wrong window
14:02:12 <tellesnobrega> I guess it will be just the three of us
14:02:26 <tellesnobrega> this should be quick
14:02:28 <tosky> at least we have some updates to record
14:02:35 <tellesnobrega> yes
14:02:43 <tellesnobrega> #topic News/Updates
14:03:28 <jeremyfreudberg> not much for me this week
14:04:03 <tellesnobrega> I'm still working on images, it was a little on hold due to internal stuff but I'm back to it
14:04:20 <tosky> working on deploying Pike with containers with TripleO (and testing a bit Pike on the way)
14:04:36 <tellesnobrega> requested tagging on stable/ocata on sahara repos, that is still ongoing
14:05:04 <tellesnobrega> our intern on the outreachy program wrote the spec and a patch already so lets get reviewing those
14:05:57 <tellesnobrega> anything else tosky?
14:06:29 <tosky> I asked around about the documentation
14:06:43 <tosky> (maybe another point?)
14:06:53 <tellesnobrega> #topic Doc Migration
14:07:00 <tellesnobrega> i had the topic already set up here
14:07:06 <tosky> eheh
14:07:08 <tellesnobrega> go ahead
14:07:33 <tosky> I switched from oslosphinx to openstackdocstheme, which is the step 0 for the doc migration (it's really a different spec)
14:08:02 <tosky> I discovered afterwards that the changes can be simplified, but we can move forward for now
14:09:33 <tellesnobrega> tosky, I think you have a little summary of what we will need to do to accomplish doc migration goal, can you share it?
14:10:56 <tosky> yep, sorry;
14:11:06 <tosky> about the doc itself, the only unified document/manual that contains some sahara stuff is the configuration manual
14:11:17 <tosky> with the configuration keys/values in sahara.conf
14:11:20 <tosky> that should be imported
14:11:44 <tosky> also, our existing documentation can be adapted to the new structure
14:12:01 <tosky> the first part about installation etc could go into the installation section according the new structure
14:12:22 <tosky> I will (slowly) follow this, it's not too complicated (unless someone beats me with the reviews of course :)
14:12:24 <tosky> and that's it
14:13:03 <tellesnobrega> cool, when you say you will follow this, is to do the work or review the work?
14:14:51 <tellesnobrega> #topic Denver PTG
14:15:38 <tellesnobrega> Some projects are already working on a little schedule for the PTG, I will start to work on something for us, gathering discussion topics, and maybe do a doc fix day or bug fix
14:15:47 <tosky> (the answer to the previous question was: do the work)
14:16:06 <tellesnobrega> tosky, perfect
14:16:14 <jeremyfreudberg> tellesnobrega, +1 to doc fixing day
14:16:44 <tellesnobrega> I will start an etherpad and send it on the ML so we can all start contributing to it
14:16:52 <jeremyfreudberg> +1 to that also
14:17:39 <tellesnobrega> that sums up PTG I guess
14:18:05 <tosky> I guess than the doc restructuring is the step 0 for the doc fixing day(s), or be part of it, if we don't want too many conflicting patches
14:18:37 <tellesnobrega> of course
14:19:26 <tellesnobrega> once we decide whether or not to do it, we can try to create a priority list of todo's
14:19:57 <tellesnobrega> #topic Open Discussion
14:20:54 <tosky> about the "use infra resources for some non-fake scenario jobs" I didn't follow up yet; I wanted to join the infra meeting, but I forgot on Tuesday
14:20:59 <tosky> but it's still on my TODO
14:21:23 <jeremyfreudberg> a quick reminder (mostly for my own benefit), following all that nova-network / heat changes, there are few cleanup tasks 1) remove use_neutron code paths, 2) doc fixes, 3) verifying ironic works, 4) removing the last bits of direct-engine code
14:21:38 <jeremyfreudberg> those todos aren't in any exact order
14:21:51 <tosky> I would say that the priority is 3) 2) 1) 4)
14:22:04 <tellesnobrega> +1 to tosky order
14:22:06 <tellesnobrega> just as a heads up, I would like to bring API v2 to focus again, we lost some people on that and we were doing great, lets try to not get that into limbo again
14:22:25 <jeremyfreudberg> +1 to tosky order also
14:23:03 <jeremyfreudberg> +1 to apiv2 also
14:23:07 <tosky> yep
14:24:11 <tellesnobrega> I don't have anything else for today, do any of you have any other topics to discuss?
14:24:28 <jeremyfreudberg> one clarification
14:25:10 <tellesnobrega> yes
14:26:32 <jeremyfreudberg> regarding feature freeze, what is the extent of the meaning of "No featureful patch" (This is my first time sticking around during a release)
14:28:12 <tellesnobrega> what is the context of that?
14:28:17 <tosky> well, that's up to the community (which is small) and the risk of breakages (which, for a small community, is more relevant)
14:28:26 <tosky> and yes, do you have any specific example in mind?
14:28:30 <tosky> it's really a case-by-case
14:29:39 <jeremyfreudberg> not much of a specific example, I guess I was thinking of moving those cleanup tasks as late as possible and trying to land some interesting patches I have on my personal backlog sooner
14:29:42 <tellesnobrega> if it is for a FFE, just as tosky said, it is really case by case, depending on the complexity of the change, and the amount of people available to check it out
14:31:38 <tellesnobrega> jeremyfreudberg, does the answer help at all?
14:31:49 <jeremyfreudberg> yes, it does
14:33:08 <jeremyfreudberg> I do have one other thing to mention, actually
14:34:05 <jeremyfreudberg> I just spent a few minutes investigating some sahara-dashboard integration tests failure (which has been happening a long time), poking around in project-config a few other small projects' UIs have the same issue.
14:34:24 <jeremyfreudberg> I was going to send mail about it, just a heads up
14:34:46 <tellesnobrega> jeremyfreudberg, please do
14:35:12 <jeremyfreudberg> great, that's it for me for now
14:35:15 <tellesnobrega> can you paste the link to the logs here?
14:35:19 <jeremyfreudberg> yes
14:35:29 <tellesnobrega> just so we can look as well and be curious together
14:36:35 <tosky> jeremyfreudberg: so it's something for horizon too (and other projects), not just sahara? interesting
14:37:03 <jeremyfreudberg> tellesnobrega, one more second, just looking around for a specific one
14:37:10 <tellesnobrega> no worries
14:37:17 <jeremyfreudberg> tosky: not horizon itself, just a few horizon plugins like ours
14:37:34 <tosky> jeremyfreudberg: but if it's the same, maybe it was a change in horizon
14:37:56 <tosky> the point was about which tags should be put in the email, and I think that [horizon] fits too
14:38:03 <jeremyfreudberg> yes, definitely
14:38:24 <jeremyfreudberg> http://logs.openstack.org/30/472330/1/check/gate-sahara-dashboard-dsvm-integration-ubuntu-xenial/803b498/console.html.gz#_2017-06-08_17_02_46_788254 is example i was thinking of
14:38:42 <tellesnobrega> cool
14:38:44 <tellesnobrega> i will take a look
14:38:53 <jeremyfreudberg> sometimes it doesn't get that far  though, http://logs.openstack.org/03/478103/1/check/gate-sahara-dashboard-dsvm-integration-ubuntu-xenial/c645c97/console.html#_2017-06-27_12_59_53_906576
14:39:40 <tellesnobrega> jeremyfreudberg, seems like a straight forward problem/solution
14:39:49 <tosky> uh, "Message: 'geckodriver' executable needs to be in PATH." ?
14:39:56 <tosky> environment issue maybe
14:40:07 <tellesnobrega> that is what I'm thinking too
14:40:10 <tosky> but better ask around, yeah, probably someone else hit and fixed it too
14:40:29 <tellesnobrega> please send out the email, people will reply with good info on that
14:40:33 <jeremyfreudberg> yep
14:41:44 <tellesnobrega> if we don't have any further discussion, I will end the meeting
14:42:02 <tellesnobrega> thanks for hard work :)
14:43:18 <tellesnobrega> #endmeeting