| *** dviroel|rover|afk is now known as dviroel|out | 00:16 | |
| *** rlandy|bbl is now known as rlandy | 00:34 | |
| *** rlandy is now known as rlandy|out | 00:55 | |
| *** ysandeep|out is now known as ysandeep | 02:12 | |
| *** ysandeep is now known as ysandeep|afk | 04:18 | |
| *** ysandeep|afk is now known as ysandeep | 06:13 | |
| *** jpena|off is now known as jpena | 07:13 | |
| *** ysandeep is now known as ysandeep|brb | 07:25 | |
| *** ysandeep|brb is now known as ysandeep | 07:30 | |
| opendevreview | Merged openstack/project-config master: Start bulding ubuntu-jammy images https://review.opendev.org/c/openstack/project-config/+/839057 | 08:15 |
|---|---|---|
| *** benj_1 is now known as benj_ | 08:18 | |
| *** rlandy|out is now known as rlandy | 10:24 | |
| *** ysandeep is now known as ysandeep|coffee | 10:37 | |
| *** dviroel|out is now known as dviroel|rover | 11:09 | |
| *** ysandeep|coffee is now known as ysandeep | 11:28 | |
| opendevreview | Dr. Jens Harbott proposed openstack/project-config master: Start launching Jammy images https://review.opendev.org/c/openstack/project-config/+/839366 | 11:54 |
| *** rlandy is now known as rlandy|mtg | 11:58 | |
| *** dasm|off is now known as dasm | 12:04 | |
| sean-k-mooney | clarkb: fungi quick question is the an offical process for creating a new code hosting org in open infra. e.g. like that vexhost top level ones | 13:52 |
| sean-k-mooney | *opendev | 13:52 |
| fungi | sean-k-mooney: no process whatsoever, just create a project in your desired namespace | 14:24 |
| fungi | though if you want the projects in that namespace to aslo have a separate zuul tenant, then there's some additional zuul configuration required, and you'll need a dedicated config project for that tenant | 14:24 |
| fungi | if you're adding the projects to an existing tenant, then just create your projects like normal | 14:25 |
| sean-k-mooney | i was talking internally regarding if we wanted to create a toplevel redhat namespace on opendev to host some of the project we currently have on github or other code hosting sites | 14:26 |
| sean-k-mooney | so im not really sure how i would go about create a redhat/whaterver project on gerrit with the assocaited project-config repo to manage zuul | 14:27 |
| sean-k-mooney | fungi: we didnt actully have that disucssion yet of if we want to do that or not | 14:28 |
| sean-k-mooney | i was just trying to find any background read on the topic | 14:28 |
| sean-k-mooney | i have followed the project creators guid to create repos in the past in the x namespace but i didnt reacally anything about creating new namespaces | 14:28 |
| sean-k-mooney | fungi: https://docs.opendev.org/opendev/infra-manual/latest/creators.html#decide-status-and-namespace-of-your-project just say if your project does not fit in anexsitng namespace you may create a new one but not how | 14:31 |
| fungi | yeah, the "x" namespace was really just a dumping ground for all the projects we moved out of the "openstack" namespace who didn't request a dedicated namespace for themselves. we didn't generally intend people to create new projects in "x" but they have anyway | 14:31 |
| clarkb | sean-k-mooney: ya because it just happens when you do the other steps taht are already documented | 14:31 |
| fungi | namespaces aren't really an explicit thing, they're implicitly created by creating a project which is prefixed with them | 14:31 |
| clarkb | maybe we need to make that more clear but the process isn't any different | 14:31 |
| clarkb | foo/bar is the same as openstack/bar creation wise | 14:31 |
| sean-k-mooney | i need to re read this but dose that guid actully tell you how to create the repo | 14:33 |
| sean-k-mooney | i seams to have skip the step of creating the repo in gerrit entirly | 14:34 |
| sean-k-mooney | i tought we jsuted to creat them by updating openstack/project-config | 14:35 |
| sean-k-mooney | and then automation created the repo | 14:35 |
| *** ysandeep is now known as ysandeep|afk | 14:36 | |
| fungi | right, that's what creates it | 14:36 |
| sean-k-mooney | right that is not really explained | 14:36 |
| sean-k-mooney | also is it openstack/project-config for opendev porject in other namespaces | 14:36 |
| fungi | you push a change to add it to the gerrit/projects.yaml file and the project will be created via automation once that change merges | 14:36 |
| sean-k-mooney | ya so thats what https://docs.opendev.org/opendev/infra-manual/latest/creators.html#adding-the-project-to-the-ci-system is covering | 14:37 |
| sean-k-mooney | well https://docs.opendev.org/opendev/infra-manual/latest/creators.html#add-the-project-to-the-master-projects-list | 14:37 |
| fungi | yes, for legacy reasons the gerrit project list is still in openstack/project-config for now, we want to move it to our opendev/project-config repo eventually | 14:37 |
| sean-k-mooney | oh ok | 14:37 |
| fungi | we've moved some stuff from openstack/project-config to opendev/project-config but there's still a lot more to do | 14:38 |
| sean-k-mooney | i was aware that opendev/project-config was a thing which was confusing me | 14:38 |
| sean-k-mooney | i was assuming this was out of date and that had likely moved | 14:38 |
| fungi | the two repos are gated by different zuul tenants, and project interrelationships make moving things hard | 14:38 |
| sean-k-mooney | if i can assume the docs is still correct | 14:39 |
| sean-k-mooney | then that is enough to have the discussion internally if we want to move the code hosting, are there any considerations we should be aware of in general | 14:39 |
| fungi | mainly it's that our opendev/system-config repo is also still in the openstack zuul tenant, and we'll probably have to move it to the opendev zuul tenant the same time we move most of the contents of openstack/project-config to opendev/project-config | 14:39 |
| clarkb | the puppet cleanups we've been doing reduce the problem space significantly | 14:40 |
| clarkb | I'm hoping we can get to a fairly minimal state with config management then switch it over | 14:40 |
| fungi | sean-k-mooney: probably i'd mainly worry about whether anyone in red hat has concerns with there being a "redhat" namespace in opendev, but from our perspective it's fine whatever you want to call it | 14:42 |
| fungi | i mean, within reason of course ;) | 14:42 |
| sean-k-mooney | yep so that is one of the thigns we want to disucss internally | 14:43 |
| sean-k-mooney | i have two differnt uscases in mind one is a porject i started on my own github which i was orginally plannign to convert to be pti complient and ask to put under offical nova governacne and or move to x namespace if the tc perfered | 14:44 |
| sean-k-mooney | the other usecase is we have some pocs ectra that are currently on different github orgs that we might want to make into real project and if we do i raised a question of moving the hosting to opendev so we can use the same tooling ectra as the rest of openstack | 14:46 |
| fungi | yeah, all of those are good reasons | 14:48 |
| sean-k-mooney | https://github.com/SeanMooney/arbiterd is the first usecase. right now its still to early to warrent movign to opendev but if i lay the ground work for integrating it with nova this cycle i would like to actully move it next cycle but not sure to which namespace | 14:50 |
| fungi | you could also just make it https://opendev.org/arbiter/arbiterd or something if you wanted | 14:51 |
| sean-k-mooney | ya that might make sense for this repo but im not sure if it makes sense to always do that for other repos that we convert from pocs to real prject so i was thinking either openstac, x or redhat namespace | 14:53 |
| sean-k-mooney | i need to do some work in oslo and nova first so really its not a pressing desion to make now anyway | 14:54 |
| sean-k-mooney | for now im the only one working on arbiterd and its kind of part time in that i have 3 feature to work on in zed and this is just one of the 3 | 14:55 |
| sean-k-mooney | fungi: anyway thanks for clarifying :) | 14:56 |
| fungi | yw! | 14:57 |
| *** ysandeep|afk is now known as ysandeep | 14:59 | |
| *** xek_ is now known as xek | 15:23 | |
| opendevreview | Merged openstack/project-config master: Start launching Jammy images https://review.opendev.org/c/openstack/project-config/+/839366 | 15:32 |
| *** dviroel|rover is now known as dviroel|rover|lunch | 16:11 | |
| *** rlandy|mtg is now known as rlandy | 16:14 | |
| *** ysandeep is now known as ysandeep|out | 16:17 | |
| *** jpena is now known as jpena|off | 16:17 | |
| *** blarnath is now known as d34dh0r53 | 16:23 | |
| *** dviroel|rover|lunch is now known as dviroel|rover | 17:02 | |
| opendevreview | Gage Hugo proposed openstack/project-config master: End project gating for openstack-helm-docs https://review.opendev.org/c/openstack/project-config/+/839103 | 19:01 |
| opendevreview | Gage Hugo proposed openstack/project-config master: Retire openstack-helm-docs repo, step 3.3 https://review.opendev.org/c/openstack/project-config/+/839427 | 19:01 |
| opendevreview | Gage Hugo proposed openstack/project-config master: Retire openstack-helm-docs repo, step 3.3 https://review.opendev.org/c/openstack/project-config/+/839427 | 19:14 |
| *** dasm is now known as dasm|off | 21:40 | |
| *** rlandy is now known as rlandy|out | 22:53 | |
| *** dviroel|rover is now known as dviroel|rover|out | 22:56 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!