14:00:33 <rafaelweingartner> #startmeeting cloudkitty
14:00:33 <opendevmeet> Meeting started Mon Jul 26 14:00:33 2021 UTC and is due to finish in 60 minutes.  The chair is rafaelweingartner. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:33 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:33 <opendevmeet> The meeting name has been set to 'cloudkitty'
14:00:41 <rafaelweingartner> Roll count
14:00:54 <mkarpiarz> Hi!
14:01:13 <priteau> o/
14:01:49 <adam_aqb> o/
14:06:56 <mkarpiarz> Hi!
14:07:01 <mkarpiarz> :)
14:07:20 <priteau> Have we lost rafaelweingartner?
14:08:07 <rafaelweingartner> #topic Target review of the meeting
14:08:14 <rafaelweingartner> #link https://review.opendev.org/c/openstack/cloudkitty/+/786651
14:08:23 <rafaelweingartner> Have you guys had the opportunity to review the PR?
14:09:07 <rafaelweingartner> I noticed Pierre already provided some feeedback there
14:09:42 <priteau> I did. I only had cosmetic feedback on wording in commit message, docs, comments, so I made changes directly to the patch
14:09:56 <priteau> Unfortunately CI is broken because of unrelated Sphinx issues
14:11:24 <rafaelweingartner> I see
14:11:54 <rafaelweingartner> Do you want my help to fix it?
14:12:30 <priteau> Not sure how much we can do ourselves, it's a wsme issue
14:12:36 <priteau> I've reported it to the mailing list
14:12:56 <priteau> One option might be to drop this extension, do you know what we use it for?
14:15:07 <rafaelweingartner> I see
14:15:20 <rafaelweingartner> I have no idea, but I can try to check it today
14:15:25 <rafaelweingartner> maybe, we do nto even use it
14:16:00 <priteau> We use it for `autotype`
14:16:17 <priteau> This is in the API reference
14:16:20 <rafaelweingartner> about the review, I really appreciate it
14:16:37 <rafaelweingartner> if others also have something else to contribute there, just ping me in the patch
14:18:09 <adam_aqb> I woul like to a topic for discussion
14:18:13 <adam_aqb> to add*
14:18:25 <adam_aqb> I have been working on CK's documentation for a while now
14:18:34 <rafaelweingartner> We will have time when we open for open discussions
14:18:40 <rafaelweingartner> So, moving on
14:18:41 <rafaelweingartner> #topic next virtual PTG
14:18:55 <adam_aqb> alright
14:19:11 <rafaelweingartner> We defined  date and time for the next CloudKitty virtual PTG, which will take place October 18, at 14:00-17:00 UTC.
14:19:27 <rafaelweingartner> do not forget to register at: https://openinfra-ptg.eventbrite.com/
14:20:11 <rafaelweingartner> #topic Broken CI
14:20:18 <rafaelweingartner> Pierre: do we need to discuss anything further about the CI?
14:21:19 <priteau> Not really, let's see what the wsme dev reply
14:21:28 <priteau> Follow this thread: http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023837.html
14:21:35 <rafaelweingartner> ok, thanks
14:21:37 <rafaelweingartner> I will do so
14:21:45 <priteau> The same extension broken for Sphinx 2 and 3
14:22:03 <priteau> So it's not the first time we see this :)
14:22:12 <rafaelweingartner> no
14:22:21 <rafaelweingartner> these dependency management is a nightmare sometimes
14:23:00 <rafaelweingartner> #topic AOB
14:23:07 <rafaelweingartner> Now, I open for general questions and topics that people might have.
14:23:18 <rafaelweingartner> adam_aqb: do you have something?
14:23:46 <adam_aqb> Yes, CK's documentation
14:24:26 <adam_aqb> The current version of it is a bit out of date, and is not in compliance with Openstack's latest directory scheme
14:24:42 <adam_aqb> see the project guide setup https://docs.openstack.org/doc-contrib-guide/project-guides.html
14:25:17 <adam_aqb> I have been working on a new version of the documentation, that repeats some of the old parts and adds a bit more explanations. It would also have a quick guides section
14:25:30 <adam_aqb> here is a **draft** https://cloudkitty-documentation-project.readthedocs.io/en/latest/index.html
14:26:14 <adam_aqb> I have a few questions : First, how can we go about changing the documentation, what would be the best approach ?
14:26:35 <priteau> When moving content around, we should redirect existing pages
14:26:43 <priteau> There is a module for this
14:26:48 <adam_aqb> second : Can someone help with CLI guide ? There isn't enough info on it in the current documentation
14:26:57 <rafaelweingartner> Hmm, I would say that opening a patch would be the first step
14:27:06 <adam_aqb> priteau : alright
14:27:14 <rafaelweingartner> what kind of help do you need with the CLI?
14:27:22 <adam_aqb> rafaelweingartner : Yes I will, I wanted your opinions first
14:27:48 <priteau> I don't remember the name, I will look it up
14:28:04 <adam_aqb> For the CLI : I haven't gotten the time yet to see how it works, and I've already noticed a bug. So, I'm not the best person suited to write documentation about it
14:28:15 <adam_aqb> priteau : Thanks, that would be great
14:29:30 <priteau> https://docs.openstack.org/whereto/latest/
14:29:40 <priteau> It's actually just for testing the redirects
14:29:48 <adam_aqb> okay I see
14:29:52 <priteau> redirects are done via .htaccess files
14:30:17 <priteau> See https://review.opendev.org/c/openstack/kayobe/+/748523 for an example
14:30:19 <adam_aqb> a .htaccess file put inside build/ N
14:30:21 <adam_aqb> ?
14:30:58 <adam_aqb> alright thanks for the example
14:32:56 <priteau> But this is the last step, we need to agree on layout and content first
14:33:06 <priteau> No need to write redirect rules that might change later
14:33:28 <adam_aqb> The layout is similar to the one described in the project guide setup (https://docs.openstack.org/doc-contrib-guide/project-guides.html)
14:33:52 <adam_aqb> for the content, you can already see a first draft by following the link above
14:33:59 <adam_aqb> I will also create a story
14:34:24 <rafaelweingartner> I liked the layout, but to validate the content, at least to me, it would be easier to review in a patch
14:34:26 <priteau> At first glance it looks ok. Not sure we will have much info in user, as cloudkitty is mostly an admin-level service
14:34:47 <priteau> Also I don't think the architecture should be under a "quick guide"
14:35:05 <adam_aqb> what do you mean ?
14:35:37 <priteau> I think it should be part of the admin doc
14:35:44 <priteau> Not under Miscellaneaous
14:36:00 <adam_aqb> alright, noted
14:37:49 <rafaelweingartner> the installation part, I am not sure how you guys see it, but it has more or less to different processes
14:38:15 <rafaelweingartner> one for the processor, and another one for the API, which is not just "apt install"/"python setup.py install" thing
14:38:29 <rafaelweingartner> maybe, a section to describe these details would be interesting
14:39:00 <priteau> There is more complexity in many other services. We can look at what they do
14:39:10 <adam_aqb> which section in the installation are refering to ?
14:39:22 <rafaelweingartner> "Installing the API behind WSGI"
14:39:25 <priteau> But I find there is limited interest in these install guides. People should really be using OSA, Kolla Ansible, etc.
14:39:35 <rafaelweingartner> it is in the same level as "Install on CentOS 7"
14:40:08 <priteau> Also why these references to CentOS 7 / Train?
14:40:12 <rafaelweingartner> priteai, I agree, but there are people that insist in using these manual installation processes ... I have no idea why
14:40:37 <mkarpiarz> The project looks good to me but what's the long-term plan? Will these new docs replace the official ones?
14:41:04 <adam_aqb> For the installation, I have tried to transcribe what was already in the current documentation. I do agree that some of it is not relevant
14:43:45 <rafaelweingartner> Overall, I liked it, and I guess that these details of sections and content could be discussed in the patch
14:43:56 <adam_aqb> yes
14:43:59 <rafaelweingartner> I only wonder the best why to introduce this, one page/section at a time
14:44:15 <rafaelweingartner> or one single big patch that introduces everything
14:44:16 <adam_aqb> The first step would be to reorganize the directories
14:44:46 <adam_aqb> Then one small change at a time
14:46:36 <rafaelweingartner> That sounds good to me
14:48:02 <adam_aqb> alright, if everyone agrees I'll start working on the patch
14:50:28 <rafaelweingartner> +1
14:51:32 <priteau> +1
14:53:48 <mkarpiarz> Sure, go for it.
14:55:29 <rafaelweingartner> we will have to close now
14:55:32 <rafaelweingartner> Thank you guys for participating. Have a nice week.
14:55:35 <rafaelweingartner> #endmeeting