Thursday, 2022-07-21

*** dviroel|afk is now known as dviroel|out00:37
*** rlandy is now known as rlandy|out01:09
*** undefined is now known as Guest559803:35
*** ysandeep|out is now known as ysandeep05:00
opendevreviewJakob Meng proposed openstack/ansible-collections-openstack master: Remove deprecated stuff from baremetal_node  https://review.opendev.org/c/openstack/ansible-collections-openstack/+/84966806:47
opendevreviewJakob Meng proposed openstack/ansible-collections-openstack master: Add a wait argument to baremetal_node  https://review.opendev.org/c/openstack/ansible-collections-openstack/+/84965306:47
*** ysandeep is now known as ysandeep|lunch07:35
opendevreviewMerged openstack/ansible-collections-openstack master: Add a wait argument to baremetal_node  https://review.opendev.org/c/openstack/ansible-collections-openstack/+/84965309:08
*** ysandeep|lunch is now known as ysandeep09:59
opendevreviewJakob Meng proposed openstack/ansible-collections-openstack master: Refactored port and port_info modules  https://review.opendev.org/c/openstack/ansible-collections-openstack/+/85062710:22
opendevreviewJakob Meng proposed openstack/ansible-collections-openstack master: Refactored server and server_info modules  https://review.opendev.org/c/openstack/ansible-collections-openstack/+/84942310:24
*** rlandy|out is now known as rlandy10:32
*** ysandeep is now known as ysandeep|afk10:53
*** dviroel|out is now known as dviroel11:24
opendevreviewAnanya proposed openstack/ansible-collections-openstack master: Moves stack module from cloud to proxy  https://review.opendev.org/c/openstack/ansible-collections-openstack/+/84826611:28
noonedeadpunkHey there! We were trying to re-use your publish job for config_template collection (to publish it on galaxy under same openstack namespace) but obviously that failed, as secret, that's used under project, can be used only withing that project12:55
noonedeadpunkAt the same time I see that pypi access secrets and jobs are stored in project-config, ie https://opendev.org/openstack/project-config/src/branch/master/zuul.d/secrets.yaml#L296-L30912:56
noonedeadpunkSo I was wondering, what you think about moving that https://opendev.org/openstack/ansible-collections-openstack/src/branch/master/.zuul.yaml#L355-L376 to project-config so it can be re-sued? 12:57
*** Guest5598 is now known as rcastillo13:05
*** ysandeep|afk is now known as ysandeep13:20
jm1sshnaidm: ^13:24
noonedeadpunkBut basically for that secret must be re-encrypted 13:25
jm1noonedeadpunk: what do you want to publish under openstack namespace on galaxy?13:30
noonedeadpunkjm1: https://opendev.org/openstack/ansible-config_template13:30
noonedeadpunkWe have another candidate https://opendev.org/openstack/openstack-ansible-plugins but it needs more love and as of today it's out of scope13:38
jm1noonedeadpunk: We have to be careful here.. openstack.cloud (aka Ansible OpenStack collection aka OpenStack Ansible modules (OSA)) and other openstack.? (aka OpenStack Ansible (plugins)) could be quite confusing 😅13:46
noonedeadpunkwell, yes. but openstack.config_template or openstack.osa-common should be quite okeyish?13:47
noonedeadpunkas long as it's self-explanatory?13:47
noonedeadpunkas we were quite close of creating repo `openstack-ansible-collection` but quickly realized that would be super confusing :D13:49
noonedeadpunkbut if you have some suggestions for naming - it's not too late ;)13:51
jm1noonedeadpunk: osa.config_template, osa.common, osa.plugins would also work since osa namespace is still free. but i am open for discussion to add more to openstack namespace. waiting for sshnaidm's opinion on that ^^13:54
noonedeadpunkwell, config_template is used outside osa. So not sure how proper to place it there13:55
noonedeadpunkand out of https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_in_groups.html#naming-conventions `It is convenient if the organization and repository names on GitHub (or elsewhere) match your namespace and collection names on Ansible Galaxy, but it is not required.`13:57
noonedeadpunkso yeah, while we can create own namespace, but it would be convenient not to :D13:58
sshnaidmnoonedeadpunk, I think we can use the same namespace, I don't see a problem, like we discussed before14:10
noonedeadpunksshnaidm: yeah, well, except I today realized that for that secret should be stored in project-config for that....14:11
sshnaidmnoonedeadpunk, I didn't know that too, is it any doc..?14:11
noonedeadpunkas when we releazed today there was jsut error that it's not allowed to run the job14:11
sshnaidmnoonedeadpunk, I suppose you can just encrypt it by yourself for your repos?14:12
noonedeadpunkwell, yes, I can do that. But then I would need also to dublicate playbook and stuff14:12
noonedeadpunkwhich is doable, but well...14:12
noonedeadpunkdoc is mostly about https://zuul-ci.org/docs/zuul/latest/config/secret.html14:13
noonedeadpunkwell, maybe we can parent your job... but I dunno how that's gonna work (and if it will)14:14
noonedeadpunk(instead of just trying re-using it). and with child job we can define own secret...14:14
noonedeadpunkbut it feels way easier to just use the one that would be stored in project-config, like it's done for pypi14:14
sshnaidmnoonedeadpunk, ok, let's stick to one channel :D14:15
*** dviroel_ is now known as dviroel15:26
*** rlandy is now known as rlandy|afk15:28
*** ysandeep is now known as ysandeep|out15:30
opendevreviewRafael Castillo proposed openstack/ansible-collections-openstack master: Update router for 2.0.0  https://review.opendev.org/c/openstack/ansible-collections-openstack/+/84644620:46
*** dviroel is now known as dviroel|out21:07
opendevreviewRafael Castillo proposed openstack/ansible-collections-openstack master: Update router for 2.0.0  https://review.opendev.org/c/openstack/ansible-collections-openstack/+/84644621:18

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!