| *** rlandy|bbl is now known as rlandy|out | 01:09 | |
| lecris[m]1 | Besides the abisimal documentation, are there issues? I want a solution to deploy multiple Openstack stacks, e.g. to deploy a testing overcloud before trying to do upgrades | 04:01 |
|---|---|---|
| lecris[m]1 | TripleO seems to be built to do exactly that, but are there other deployments with similar functionality? | 04:02 |
| lecris[m]1 | Aren't all of ansible recipes common among all of these? | 04:08 |
| *** soniya is now known as soniya|ruck | 05:04 | |
| jrosser | lecris[m]1: there is almost certainly an IRC channel specific to tripleo, see https://www.rdoproject.org/tripleo/ | 06:32 |
| lecris[m]1 | Thanks I got some help there. So this channel is more on the general openstack help? I.e. after any of the deployments? | 06:34 |
| jrosser | basically yes | 06:36 |
| jrosser | imho you should look also at the other deployment tools aside from tripleo, unless you have a big need to use that specifically | 06:36 |
| lecris[m]1 | 👍️ | 06:36 |
| jrosser | you have reasonable amount of choices which make different decisions about how they work | 06:37 |
| jrosser | some will be better / worse fit for your needs | 06:37 |
| lecris[m]1 | Well I want something that can be daisy-chained, which TripleO in theory is the supported way to do that | 06:38 |
| jrosser | you mean there is an upgrade path? | 06:39 |
| lecris[m]1 | And I am at the very last step of getting it working | 06:40 |
| lecris[m]1 | Like `undercloud` -> `overcloud` -> `overcloud-test`/`overcloud-next`/`undercloud...`, and basically just switch them around at next stable etc. | 06:41 |
| *** tweining|off is now known as tweining | 08:12 | |
| Jan[m]1 | Hi all! I am looking into contributing to the openstack documentation.... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/WpaYUxxxtXZQrLWNZVgzPXfa) | 10:05 |
| frickler | Jan[m]1: using a bridge from matrix makes it pretty difficult for most participants here to read your message. maybe only write one line at a time. | 10:20 |
| *** rlandy|out is now known as rlandy | 10:20 | |
| Jan[m]1 | ok, thanks for the hint | 10:20 |
| Jan[m]1 | I am looking into contributing to the openstack documentation. | 10:20 |
| Jan[m]1 | I found the following guide for first timers: | 10:20 |
| Jan[m]1 | https://docs.openstack.org/doc-contrib-guide/quickstart/first-timers.html | 10:21 |
| Jan[m]1 | The section on "Finding a bug" sends me to a launchpad (https://bugs.launchpad.net/openstack-manuals/+bugs) | 10:21 |
| Jan[m]1 | The launchpad however returns only the following message: | 10:21 |
| Jan[m]1 | openstack-manuals must be configured in order for Launchpad to forward bugs to the project's developers. | 10:21 |
| Jan[m]1 | What am I doing wrong? | 10:21 |
| Jan[m]1 | How can I find things to contribute? | 10:21 |
| Jan[m]1 | Is this the right place to ask questions regarding documentation contributions? | 10:21 |
| Jan[m]1 | (Sorry for the flood :) | 10:21 |
| frickler | I'm not sure about the issue with launchpad, but then, most projects publish their documentation from their own repo nowadays, so documentation bugs will be tracked in their specific bug tracker | 10:21 |
| frickler | also this is the right channel, but it isn't pretty active. you might also want to visit #openstack-doc , which however is even less active | 10:22 |
| Jan[m]1 | Thanks | 10:23 |
| frickler | Jan[m]1: if you do not want to look at specific projects, testing the installation guide and seeing if everything still works as described might be a good start https://docs.openstack.org/install-guide/ | 10:24 |
| Jan[m]1 | ok, the thing is that the guide mentions that you have to have a story or a bug to contribute | 10:25 |
| Jan[m]1 | contributions without any of these is ok too, but having an issue is prefered | 10:26 |
| Jan[m]1 | That is why I asked, as I cannot see anyting in the launchpad, it is hard to come up with an issue (and to search for existing issue, etc.) | 10:27 |
| frickler | Jan[m]1: submitting patches without a bug reference is valid, too. worst case some reviewer will ask for a bug to be created. | 10:41 |
| frickler | Jan[m]1: you can also check doc bugs for individual projects. like nova has them tagged https://bugs.launchpad.net/nova/+bugs?field.tag=doc | 10:41 |
| Jan[m]1 | Ah, this launchpad works as expected. Ok I think I get it now, some projects track their bugs some place else (e.g. a story board) and some are still on launch pad. Thanks that helped! | 10:49 |
| *** soniya29 is now known as soniya29|ruck | 11:08 | |
| *** soniya29|ruck is now known as soniya29|ruck|brb | 11:10 | |
| lecris[m]1 | Jan: what documentation part are you targeting? I am starting some work on TripleO deployment. | 12:02 |
| Jan[m]1 | Currently I am looking for the issue tracker of openstack-manuals. | 12:06 |
| Jan[m]1 | Also I am looking into Ironic, but I found a matching StoryBoard already. | 12:07 |
| *** soniya is now known as soniya|ruck | 12:21 | |
| lecris[m]1 | Why are there both launchpad and storyboard? It's confusing to find where/how to contribute. At least the repositories on github point to the relevant infrastructures | 12:41 |
| Jan[m]1 | That is not always true. In case of the openstack-manuals: github points to opendev, opendev points to a not configured launchpad. | 12:42 |
| Jan[m]1 | Good question, btw. I find it confusing as well. | 12:43 |
| lecris[m]1 | Sorry i meant gitea | 12:45 |
| lecris[m]1 | The one on opendev | 12:45 |
| lecris[m]1 | If it points to unconfigured launchpad it's likely because it should point to the parent project | 12:47 |
| Jan[m]1 | Ok, that makes sense, so documentation bugs should be in the overall openstack launchpad. | 13:10 |
| jamesbenson | I find doc bugs in the project that I'm interested in/working on typically | 13:11 |
| *** soniya|ruck is now known as soniya|out | 16:11 | |
| *** prometheanfire is now known as Guest0 | 22:26 | |
| *** rlandy is now known as rlandy|bbl | 23:02 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!