Tuesday, 2021-12-28

noonedeadpunkjrosser_: hey! Am I right that for multi-regions it's good idea to use same rootCA but use different intermediates?08:32
jrosser_if you ever want the internal networks to share things, that could help08:33
noonedeadpunknah, we have nothing-shared...08:33
noonedeadpunkso then it's probably doesn't really matter08:35
noonedeadpunkand not worth complexing08:35
jrosser_or if you want to visit internal url via vpn for debug, or monitoring systems which connect to internal things?08:35
noonedeadpunkoh, well, unless this root we want to use outside of osa ofc...08:35
jrosser_yes that too08:35
noonedeadpunkyeah, monitoring is valid point08:35
noonedeadpunkthanks!08:36
jrosser_would be really interesting to test out providing an external root CA, intermediate and key, and see if the PKI role can cope with that08:36
jrosser_almost certainly some trouble to fix with that but I think it’s a very valid use case08:37
noonedeadpunkIf names would be matching I guess it should08:37
jrosser_yes08:37
jrosser_we needed to do something like this for ceph rgw08:37
jrosser_they need to talk https to keystone08:38
noonedeadpunkwell, yeah, if they want to talk through internalurl...08:39
jrosser_yep, it’s all very much depending on what architecture you have08:39
noonedeadpunkwould be great if somebody could take a look at https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/82299810:26
noonedeadpunkas with virtualenv removal from openstack_hosts we got setuptools missing10:27
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible-os_tempest master: Allow to create only specific tempest resources.  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/80347711:46
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible-os_tempest master: Do not set default value for tempest_private_net_seg_id  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/80348611:48
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible-os_tempest master: Allow to create only specific tempest resources.  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/80347711:48
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible-os_tempest master: Fix hardcoded flavor_ref and flavor_ref_alt  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/80349212:16
opendevreviewMerged openstack/openstack-ansible-os_octavia master: Use focal amphora test image by default  https://review.opendev.org/c/openstack/openstack-ansible-os_octavia/+/82283412:17
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible-os_tempest master: Fix hardcoded flavor_ref and flavor_ref_alt  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/80349212:19
damiandabrowski[m]hey folks, can I ask for some attention on my tempest changes? They were stuck for a few months and I'd love to finally merge them.12:32
damiandabrowski[m]https://review.opendev.org/q/topic:%22tempest-damian-2021-12%2212:32
opendevreviewMerged openstack/ansible-role-python_venv_build master: Replace virtualenv with exacutable for pip  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/82299812:49
noonedeadpunkdamiandabrowski[m]: commented13:03
admin1i am having a strange issue in an aio setup ..    logs here: https://gist.githubusercontent.com/a1git/caa4c3b201d156384134778eeb004959/raw/65ba7ba28263f0068d8888eaf46573cde7a0b7a6/gistfile1.txt   . it fails on systemd_service : Create TEMP run dir  .. tag = 23.2.0 14:33
admin1scenaio is aio_ceph 14:33
noonedeadpunkI bet you have ens3 interface?:)14:48
noonedeadpunkadmin1: we do assumptions here https://opendev.org/openstack/openstack-ansible/src/branch/master/tests/roles/bootstrap-host/templates/user_variables_ceph.yml.j2#L1914:51
noonedeadpunkso we expect to see eth1 interface present because that's what we have in CI...14:52
noonedeadpunknot sure how to workaround that to satisfy everybody...14:52
noonedeadpunkmaybe check all available interfaces and pick first....14:53
opendevreviewMerged openstack/openstack-ansible-os_glance master: Define _glance_available_stores in variables  https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/82289914:56
noonedeadpunkI suggest to cancel today meeting if nobody against that?15:00
noonedeadpunkAs I believe everybody having Christmas holidays :)15:00
opendevreviewMerged openstack/openstack-ansible-os_glance master: Add boto3 module for s3 backend  https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/82287015:04
opendevreviewMerged openstack/openstack-ansible master: Update ansible-core to 2.12.1  https://review.opendev.org/c/openstack/openstack-ansible/+/82206315:05
admin1noonedeadpunk i had enp1s0 15:10
admin1created via kvm 15:10
admin1thank noonedeadpunk .. i know what to check and fix now 15:11
jamesdentoni am around, but cancelling the meeting is fine by me15:13
noonedeadpunkok, thanks)15:18
noonedeadpunkI just don't have an agenda really :(15:19
jamesdentonit's all good15:19
noonedeadpunkWell, maybe I do but let's leave that after holidays ;)15:19
jamesdentoni did want to ask about roles or features in 'experimental' status. working on ironic inspector and may want to change a few things without some extended deprecation notice15:21
jamesdentoni am honestly not sure if anyone is using it15:21
noonedeadpunkI can triplo wer pushing changes to it?15:21
noonedeadpunk*can recall15:21
noonedeadpunkoh not...15:22
jamesdentonpossibly - i am mainly looking to split out inspector dnsmasq into its own service (instead of leveraging base dnsmasq) and possibly even make dnsmasq optional, since if you use 'neutron' as the network interface you can rely on neutron's dnsmasq stuff15:23
noonedeadpunkIronic is still dark magic to me...15:24
jamesdentonme too15:24
jamesdenton:D15:24
jamesdentonthere are a lot of knobs15:24
noonedeadpunkWe're trying to hire somebody who will be able to focus on it and get us a service, so had no chance to dig there yet15:24
noonedeadpunkLet me read why inspector needs dnsmasq...15:26
jamesdentonoh, to add baremetal instances to your product offering?15:26
noonedeadpunkyeah15:26
noonedeadpunkand for computes/controllers deployment I believe as well.15:26
noonedeadpunkbut it's smth that is currently being dicsussed15:26
jamesdentoninspector can work w/ a 'flat' network model or 'neutron' - the former requires its own dnsmasq service and doesn't manage any networking, the latter relies on neutron for dnsmasq and even switchport manipulation (w/ ML2 driver)15:28
noonedeadpunkUm, what is the worst case scenario if to split inspector dnsmasq to separate thing? I just thought that it should be able to access some ironic leases but maybe I';m wrong?15:29
jamesdentonfor 'flat' you would need the inspector/controller plugged into a bridge that VMs will ultimately also be connected to - it's one large flat network for provisioning, inspection, etc.15:29
jamesdentoneh, the issues i ran into was that inspector dns config was hanging off of 'dnsmasq' service that didn't want to start due to some conflict, so split it into it's own service w/ own directories, fikles, etc.15:29
jamesdentonone sec15:30
jamesdentoni think it was due to running inspector on metal vs lxc15:30
jamesdentonhttps://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/82150315:30
noonedeadpunkah, ironic-inspector is smth like "provisioning" in maas :D15:33
noonedeadpunkBut I'm not sure how valid to have separate dnsmasq...15:33
jamesdentonit's sort of like discovery, ironic is the true provisioner15:34
jamesdentonbut yeah, all related15:34
noonedeadpunkas I'd say that I'd expect node to have same IP (esp if it's "static") when booting for expection15:34
jamesdentonwell, in the case of inspector vs ironic provisioning, it won't have the same IP - it will manage its own leases outside of neutron. and it's usually a 1-time operation AFAIK15:35
jamesdentonfor provisioning, those ips are managed by neutron (with a baremetal port -> neutron port) mapping or sorts. 15:35
noonedeadpunks/provisioning/comission/15:36
jamesdentonyeah ok15:36
noonedeadpunkaha, I see. I just trying to compare to maas as it's smth I'm aware of hehe. And there IP would be consistent for real provisioning and comissioning15:37
noonedeadpunkand how it would work then without net conflicts? as basically you do both operations on the same interface in the same vlan?15:38
noonedeadpunk*ip conflicts15:38
jamesdentonwell, you might configure a different CIDR for inspection vs provisioning/tenant15:40
noonedeadpunkfor pxe boot you can't use tagged vlans anyway I believe... So dhcp for pxe boot should be kind of same?15:40
jamesdentonand i think there is some iptables magic happening15:40
noonedeadpunkhm15:40
noonedeadpunkso for me tbh sharing dnsmasq sounds more logical, dunno... 15:41
noonedeadpunkbut if it can be optional, I guess it's ok15:42
jamesdentoni'll have to see if i can track down the error i was getting. but it would be similar to how lxc-dnsmasq is its own service, and i think tripleo breaks it out, too15:42
noonedeadpunkor, well, both using neutron for that sounds fine as well15:42
jamesdentoni'll keep plugging away at it, need to compare lxc and metal deploys again. too many moving pieces right now15:43
admin1for those with ocd, will ExampleCorp in pki role be a var someday :) ? 15:52
admin1to replace it with MyAwesomeCorp .. 15:53
jrosser_admin1: it is already overridden from the PKI role defaults here https://github.com/openstack/openstack-ansible/blob/master/inventory/group_vars/all/ssl.yml#L32-L6215:55
jrosser_you would redefine openstack_pki_authorities with whatever you want instead15:56
admin1yay \o/ 15:56
admin1one question question .. does aio ceph also include object_storage via ceph  by default 15:56
jrosser_it should do15:57
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-galera_server master: Allow galera_address to be FQDN  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/82310115:57
noonedeadpunk spotted that ^ in our dev env during upgrade :(15:58
opendevreviewMerged openstack/openstack-ansible-galera_server master: Fix galera_force_bootstrap behaviour  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/82291116:03
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible-os_tempest master: Fix hardcoded flavor_ref and flavor_ref_alt  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/80349217:21
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-galera_server stable/xena: Fix galera_force_bootstrap behaviour  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/82294217:30
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-galera_server stable/wallaby: Fix galera_force_bootstrap behaviour  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/82294317:31
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_glance stable/xena: Add boto3 module for s3 backend  https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/82294417:34
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_glance stable/xena: Add boto3 module for s3 backend  https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/82294417:34
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_glance stable/wallaby: Add boto3 module for s3 backend  https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/82294517:34
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_glance stable/victoria: Add boto3 module for s3 backend  https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/82294617:34
*** dmsimard7 is now known as dmsimard17:36
opendevreviewMerged openstack/openstack-ansible master: [doc] Update infra node scaling documentation  https://review.opendev.org/c/openstack/openstack-ansible/+/82291217:52
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_horizon master: Improve defining horizon_lib_dir  https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/82092817:57
admin1i followed this in an AIO ..  https://docs.openstack.org/openstack-ansible-haproxy_server/latest/configure-haproxy.html   ..  using haproxy wtih letsencrypt .. what I notice is .. when I do cloud.domain.com, it comes 1 time, then goes to 503 .. again 503 .. again  503 and then again comes backup with the actual horizon login 19:40
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-tests stable/wallaby: Add config_template collection  https://review.opendev.org/c/openstack/openstack-ansible-tests/+/82294919:41
admin1has anyone else noticed such ? 19:41
NeilHanlonadmin1: have you checked any logs? syslogs on the host, inside the horizon container?19:55
jrosser_admin1: if it works once then fails twice you have two broken horizon backends and one working one, check the haproxy status19:59
admin1tcpdump showed no traffic between  haproxy ->   horizon container when 503 occoured20:00
jrosser_503 can come from haproxy20:00
jrosser_so check hatop or whatever you normally use20:00
admin1this one is just 1 controller .. so there were no other backends .. and the   ok, not ok, not ok, OK confused  me as well .. but i have to test somethign else on it now .. was getting stuck on haproxy ..so i removed the config .. once this test is done, i will put it back on letsencrypt and report back with logs, observations and configs i can20:02
admin1share 20:02
admin1 setting up a new 23.2.0 tag with ceph  .. i added ceph rgw as object storage .. the page loads .. but it gives me a new error:  Unable to fetch the policy details.   .. .. i don't recall this error in older builds .. so a bit confused 20:23
admin1i added the correct entries in the mon in ceph.conf for rgw and added the endpoints, re-run horizon playbook and that was pretty much it . working out of the box 20:24
admin1i hit this bug somehow: https://bugs.launchpad.net/ubuntu/+source/python-swiftclient/+bug/190294420:29
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible-os_tempest master: Allow to create only specific tempest resources.  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/80347721:06
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible-os_tempest master: Fix hardcoded flavor_ref and flavor_ref_alt  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/80349221:10

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