Friday, 2021-11-12

*** gouthamr_ is now known as gouthamr06:19
holtgreweI want to use Ceph for block/object storage. It looks like kayobe does not provide any support for this (any more). The train release apparently had a ceph.conf. Could anyone give me pointers where to start looking to set this up?07:04
opendevreviewlikui proposed openstack/kolla-ansible master: Use Docker healthchecks for ironic-neutron-agent services  https://review.opendev.org/c/openstack/kolla-ansible/+/81770607:07
bsanjeewaholtgrewe: https://docs.openstack.org/kolla-ansible/latest/reference/storage/external-ceph-guide.html07:20
holtgrewebsanjeewa, thanks!07:20
bsanjeewaPaths should change from /etc/kolla to /etc/kayobe/kolla as I remember07:20
holtgreweIs it possible with kayobe to attach bonds directly into networks? I would like such a setup for my ceph backend/cluster traffic. When I attach my bond directly via controller_extra_network_interfaces then the netmask is set to /32. When I attach the network without a bridge then my bond1 is configured with TYPE=Ethernet.07:37
DK4does kolla works with xena yet?07:56
jingvarholtgrewe: could yuo please rephrase07:58
*** amoralej|off is now known as amoralej07:59
holtgrewejingvar, I would like to connect my controller to a second network with a second bond (called bond1).08:00
holtgreweCan I configure kayobe such that it creates bond1 with 192.168.2.14/24, for example.08:00
holtgreweWithout a bridge.08:00
jingvarcreate network with the subnet into networks.yaml, add the network to entaernal network for controllers, add bond1 with the network into inventory/group_vars/controllers/network-interfaces08:06
jingvari think it shold just configure interface into /etc/sysconfig/networkscrips08:07
opendevreviewPierre Riteau proposed openstack/kayobe-config-dev stable/xena: Define infra VMs for testing  https://review.opendev.org/c/openstack/kayobe-config-dev/+/81767208:33
opendevreviewPierre Riteau proposed openstack/kayobe stable/xena: CI: add Infra VM jobs  https://review.opendev.org/c/openstack/kayobe/+/81767308:37
opendevreviewPierre Riteau proposed openstack/kayobe-config-dev stable/xena: Synchronise job config with kayobe  https://review.opendev.org/c/openstack/kayobe-config-dev/+/81767408:39
opendevreviewMark Goddard proposed openstack/kayobe-config-dev stable/xena: Define infra VMs for testing  https://review.opendev.org/c/openstack/kayobe-config-dev/+/81767208:57
opendevreviewMark Goddard proposed openstack/kayobe stable/xena: CI: add Infra VM jobs  https://review.opendev.org/c/openstack/kayobe/+/81767308:58
opendevreviewMerged openstack/kolla-ansible stable/victoria: docs: Fix python-openstackclient package name and init-runonce path  https://review.opendev.org/c/openstack/kolla-ansible/+/81726609:17
kevkohrw: could you check my review for cron image ? - trivial and usefull :P 09:19
opendevreviewlikui proposed openstack/kolla-ansible master: The ironic-ipxe service should be False when the enable_ironic_ipxe is no  https://review.opendev.org/c/openstack/kolla-ansible/+/81772209:26
holtgrewejingvar, which changes did you need for installing rocky as controller OS? Just apply the patch to the kayobe source and specify os_distribution:rocky and os_release:8 in etc/kayobe/globals.yml?09:49
hrwkevko: it helps when you give url next to request09:50
hrwmorning09:50
kevkomorninng :) 09:50
kevkohttps://review.opendev.org/c/openstack/kolla/+/81300809:51
jingvarholtgrewe: I did'nt use the patch09:51
holtgrewejingvar, oh, you did not deploy rocky for controller OS? I guess I misunderstood09:51
jingvarit may depend on ansible version09:51
jingvarI have my patch09:52
jingvarhttps://github.com/jingvar/a-universe-from-nothing/commit/a45a643ab6db2bf9d3b20bea7a684dfb12ff3e9809:56
jingvarit about kayobe-config09:56
jingvarand patch for ansible 09:57
holtgreweneat!09:57
jingvarhttps://paste.opendev.org/show/810964/10:06
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Make cron logfile minsize,maxsize configurable  https://review.opendev.org/c/openstack/kolla-ansible/+/81086110:08
hrwholtgrewe: could you use 'rockylinux' (with or without space) when you mention rocky? There was Openstack release called rocky10:37
opendevreviewMerged openstack/kolla-ansible master: Stop creating unused cron/logrotate directory  https://review.opendev.org/c/openstack/kolla-ansible/+/81319910:59
opendevreviewMerged openstack/kolla-ansible master: docs: stop installing kolla in quickstart  https://review.opendev.org/c/openstack/kolla-ansible/+/81752310:59
opendevreviewMerged openstack/kolla-ansible master: docs: Install openstack-client with upper constraints  https://review.opendev.org/c/openstack/kolla-ansible/+/81607610:59
frickleryoctozepto: kevko: regarding ^^, in osism we use a docker image for osc, do you think it might make sense to adopt that approach into kolla, too? https://github.com/osism/container-image-openstackclient11:09
kevkofrickler: do you mean constraints ? Because I can see that you are already using it no ? 11:11
kevkohmm, maybe I don't understand the question 11:14
kevko:/11:14
holtgrewehrw, of course, thanks for the pointer11:26
hrwholtgrewe: thanks11:26
hrwnot that anyone sane would use rocky still11:27
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Make cron logfile minsize,maxsize configurable  https://review.opendev.org/c/openstack/kolla-ansible/+/81086111:28
fricklerkevko: no, the idea would be to create a osc image within kolla instead of osism and then reference that in the quickstart guide and possibly elsewhere11:29
* frickler should've been more explicit11:30
kevkohmm, what is osism ? 11:30
kevkofrickler: ah, If i understand correctly - You are saying, don't install openstack-client etc in your Operating System or venv, just use this osc client image - so replace quickstart guide to use image ? right ? 11:32
kevkoIf yes, it could be an optional, but don't think it should be default as machine where kolla-ansible is installed can be tiny small instance or your notebook ..and no everyone wants to have docker installed ...11:34
kevkoFor example I'm using kolla-ansible with osc clients inside container  + patching ansible to avoid this long-term bug in kolla -> https://bugs.launchpad.net/kolla-ansible/+bug/186351011:36
kevkofrickler: btw, i've already fixed your review notes here -> https://review.opendev.org/c/openstack/kolla-ansible/+/81086111:42
kevkofrickler: maybe you can review also 2 more patches about cron from me :) ? -> https://review.opendev.org/c/openstack/kolla/+/813008 and https://review.opendev.org/c/openstack/kolla-ansible/+/81303911:43
opendevreviewPierre Riteau proposed openstack/kolla-ansible stable/xena: Stop creating unused cron/logrotate directory  https://review.opendev.org/c/openstack/kolla-ansible/+/81767812:10
opendevreviewPierre Riteau proposed openstack/kolla-ansible stable/wallaby: Stop creating unused cron/logrotate directory  https://review.opendev.org/c/openstack/kolla-ansible/+/81767912:10
opendevreviewPierre Riteau proposed openstack/kolla-ansible stable/victoria: Stop creating unused cron/logrotate directory  https://review.opendev.org/c/openstack/kolla-ansible/+/81768012:11
opendevreviewPierre Riteau proposed openstack/kolla-ansible stable/ussuri: Stop creating unused cron/logrotate directory  https://review.opendev.org/c/openstack/kolla-ansible/+/81768112:11
fricklerkevko: interesting bug. I was waiting for your updates on the other patches, but left some comments now12:17
kevkofrickler: do you mean that bug with looped notifiers ? 12:17
kevko*handlers ? 12:18
holtgrewe*tada* I now have openstack and horizon setup. What's the next appropriate step to setup a provider network? "openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider" gives me "BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for flat provider network."12:18
kevkoyeah, on big openstack cluster it's problem especially with l3 agents restarts ..even if they are not need to be restarted ... :(12:18
kevkoholtgrewe: check your flat_networks in /etc/kolla/neutron-server/ml2_conf.ini 12:19
kevkoholtgrewe: --provider-physical-network is name (one of - in case you've defined several physnets) of your physnet for flat network 12:20
holtgrewekevko, thanks! oh, interesting, there are only [ml2] and [ml2_type_vlan] headers defined but no entries... I guess I'm missing some kayobe config12:21
kevkoholtgrewe: kolla globals -> neutron_external_interface: your interface for interface providing your physnet12:23
kevkoholtgrewe: https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutron.html12:25
kevkoholtgrewe: and this one -> https://docs.openstack.org/kolla-ansible/latest/admin/production-architecture-guide.html12:25
holtgrewejingvar, how does your "etc/kolla/config/neutron/ml2_conf.ini" look like?12:39
holtgrewekevko, thanks but as I am using kolla via kayobe, I have some trouble figuring out how the ini file should look like...12:41
jingvarholtgrewe: :) 12:44
jingvarlet me second12:44
kevkowell, I'm not using kayobe ..but it's using kolla-ansible somehow, isn't it ? 12:45
jingvarholtgrewe: https://paste.opendev.org/show/810971/12:46
holtgrewekevko, yes, but some aspects of kayobe are a bit ... involved ... and I don't know yet how the ini file should look like for me. I can go backwards from the ini file and see how I can make kayobe generate it. kayobe is using networks and interfaces and I have network / bridge / bond / interface and I still throuble to see how it should look like12:47
holtgrewejingvar, thanks12:47
holtgreweoh, interesting, kayobe xena writes out to neutron/ rather than neutron-server ;-)12:48
jingvarI think you need kolla/globals.yaml 12:48
jingvarneutron_plugin_agent: "ovn"12:48
jingvarneutron_ovn_distributed_fip: "yes"12:48
holtgrewejingvar, ah, interesting... that's not in your universe-from-nothing files diskless branch, right?12:49
holtgrewe"grep neutron etc/kolla/globals.yml" returns "enable_neutron_provider_networks: false"12:50
*** amoralej is now known as amoralej|lunch13:03
holtgreweoooh, OK, you were referring to /etc/kolla/neutron-server/ml2_conf.ini on the controller/compute servers... I have that setup correctly as welll. So probably my network is called physnet113:03
holtgrewe"openstack network create --share --external --provider-physical-network physnet1 --provider-network-type flat provider" works now ...13:04
holtgrewesorry for all the questions and noise... I'm learning13:04
jingvarit is ok13:29
opendevreviewMichal Arbet proposed openstack/kolla master: Make cron's logrotate schedule configurable  https://review.opendev.org/c/openstack/kolla/+/81300813:47
*** amoralej|lunch is now known as amoralej13:50
kevkofrickler: cron review updated :P 13:51
jingvarholtgrewe: diskless is splited into 2 parts - pxe boot image creation with installed openstack services from a compute node and a magic around kayobe ironic15:21
EugenMayerholtgrewe i have done the same setup very recently, Xena/OVN but without DVR - i created a vagrant lab for that https://github.com/EugenMayer/openstack-lab15:31
EugenMayerif you need the post installation part for typical provider/lan, see https://github.com/EugenMayer/openstack-lab/blob/master/config/bin/setup_defaults.sh#L1115:31
EugenMayerphysnet1 is always the first one you name in https://github.com/EugenMayer/openstack-lab/blob/master/config/inventory/group_vars/control/control.yml#L3 - the second will be physnet2 . You can define severat comma seperated and give them more meaningfull names using15:33
EugenMayerhttps://github.com/EugenMayer/openstack-lab/blob/master/config/inventory/group_vars/control/control.yml#L4 - just keep the order15:33
opendevreviewMichal Arbet proposed openstack/kolla master: Make cron's logrotate schedule configurable  https://review.opendev.org/c/openstack/kolla/+/81300816:30
kevkofrickler: still here ? :) 16:34
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Add way to change logrotate scheduling  https://review.opendev.org/c/openstack/kolla-ansible/+/81303916:50
*** amoralej is now known as amoralej|off17:14

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