| *** amoralej|off is now known as amoralej | 06:37 | |
| holtgrewe | jingvar, oh I think I found my mistake. I tried to allocate in kayobe outside of the kayobe range as I thought that this was the dnsmasq range | 06:40 |
|---|---|---|
| jingvar | there are a lot of unclear things :) | 06:51 |
| jingvar | https://github.com/jingvar/a-universe-from-nothing/tree/test may be you can find an answers in my commits | 06:54 |
| holtgrewe | Actually, what is the process when deploying? My machines PXE boot with an inspection IP and then boot into the IPA image. | 06:54 |
| jingvar | rigth question what do ironic | 06:55 |
| jingvar | ironic has several ways to do things | 06:56 |
| jingvar | it creates pxe-mac record with an options for IPA | 06:56 |
| holtgrewe | I am puzzled a bit because what I see is that kayobe writes host variable `ipv4_address` into `/etc/bifrost/inventory/host_vars/stack-1`. However, the bifrost documentation says that it will only provide static ips (I assume write to etc/dnsmasq.d/bifrost.dhcp-hosts.d) if inventory_dhcp is set to true for bifrost. But grep -R "inventory_dhcp" /bifrost yields nothing in the bifrost container. | 06:57 |
| holtgrewe | If you deploy your machines via ironic, do they get assigned the proper IPs? | 06:58 |
| holtgrewe | Maybe I need to assign IPs in all networks separately. | 06:58 |
| jingvar | ironic unpack qcow and write cloudinit wich consist network settings - config drive was genereate by kayobe | 07:00 |
| jingvar | in my case, after deploy machine has in deffrent network - not pxe | 07:01 |
| holtgrewe | what does `find /etc/dnsmasq.d` give you in the bifrost docker container? | 07:04 |
| jingvar | empy folder | 07:05 |
| holtgrewe | jingvar, where are you deploying to? bare metal? | 07:12 |
| jingvar | vm and baremetal | 07:18 |
| holtgrewe | I really wonder what's going wrong in my case. I'm getting leases from the inspection range for dnsmasq. | 07:18 |
| holtgrewe | Do kayobe/kolla/bifrost write them before booting the machines on your side? | 07:19 |
| holtgrewe | What kind of hardware are you deploying to? | 07:20 |
| holtgrewe | Ah, but you have separate physical networks, right? | 07:21 |
| jingvar | networks depends on test env | 08:07 |
| jingvar | hardware - Supermicro X9QR7-TF+ | 08:11 |
| jingvar | cisco ucs | 08:11 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: docs: Improve info about neutron external interface https://review.opendev.org/c/openstack/kolla-ansible/+/813965 | 08:54 |
| holtgrewe | jingvar, how does your /httboot look like? Do you have an entry in pxelinux.cfg besides default? | 09:39 |
| jingvar | ls /httpboot/pxelinux.cfg/ 0-e2-ba-5c-bb-48 90-e2-ba-5c-c1-9c default | 10:01 |
| mgoddard | holtgrewe: I replied on the ML | 10:02 |
| -opendevstatus- NOTICE: zuul was stuck processing jobs and has been restarted. pending jobs will be re-enqueued | 10:02 | |
| jingvar | initaly there is only default, other files after inspect or provision | 10:02 |
| holtgrewe | @mgoddard, thanks. I will go through the universe from nothing tutorial, all VM, again and this time keep around the results so I can compare resulting files and logs | 10:03 |
| mgoddard | holtgrewe: sounds like a good plan | 10:05 |
| holtgrewe | I really hate bare metal deployment but despite the complexity of kayobe/kolla/etc., it feels more tractable than xCAT... | 10:06 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: Add api_workers for each service to defaults https://review.opendev.org/c/openstack/kolla-ansible/+/813193 | 10:50 |
| mnasiadka | yoctozepto: I guess we can, write down that in the etherpad so I don't forget :) | 11:41 |
| *** amoralej is now known as amoralej|lunch | 11:59 | |
| opendevreview | OpenStack Release Bot proposed openstack/kolla-ansible stable/xena: Update .gitreview for stable/xena https://review.opendev.org/c/openstack/kolla-ansible/+/813991 | 12:20 |
| opendevreview | OpenStack Release Bot proposed openstack/kolla-ansible stable/xena: Update TOX_CONSTRAINTS_FILE for stable/xena https://review.opendev.org/c/openstack/kolla-ansible/+/813992 | 12:20 |
| opendevreview | OpenStack Release Bot proposed openstack/kolla-ansible master: Update master for stable/xena https://review.opendev.org/c/openstack/kolla-ansible/+/813993 | 12:21 |
| opendevreview | OpenStack Release Bot proposed openstack/kolla-ansible master: Add Python3 yoga unit tests https://review.opendev.org/c/openstack/kolla-ansible/+/813994 | 12:21 |
| opendevreview | OpenStack Release Bot proposed openstack/kolla stable/xena: Update .gitreview for stable/xena https://review.opendev.org/c/openstack/kolla/+/813995 | 12:22 |
| opendevreview | OpenStack Release Bot proposed openstack/kolla stable/xena: Update TOX_CONSTRAINTS_FILE for stable/xena https://review.opendev.org/c/openstack/kolla/+/813996 | 12:22 |
| opendevreview | OpenStack Release Bot proposed openstack/kolla master: Update master for stable/xena https://review.opendev.org/c/openstack/kolla/+/813997 | 12:22 |
| opendevreview | OpenStack Release Bot proposed openstack/kolla master: Add Python3 yoga unit tests https://review.opendev.org/c/openstack/kolla/+/813998 | 12:22 |
| frickler | looks like we have reached rc1 \o/ | 12:24 |
| mnasiadka | yup | 12:27 |
| yoctozepto | mnasiadka: thanks, I did :-) | 12:27 |
| yoctozepto | yay, rc1 | 12:28 |
| eugenmayer | For a local dev setup, prefered multi-compute node setup, using https://github.com/openstack/kolla-ansible/tree/master/contrib/dev/vagrant would be a good option, right? | 12:45 |
| mnasiadka | I don't know if anybody is using those Vagrant files... | 12:46 |
| yoctozepto | I think they are broken atm | 12:47 |
| yoctozepto | contrib/ is not maintained by definition | 12:47 |
| eugenmayer | so how do you guys bootstrap a test lab right now? full local? | 12:49 |
| *** amoralej|lunch is now known as amoralej | 12:49 | |
| eugenmayer | i mean, considering that i learnding that this is full lxc, i guess that is not a bad idea. I just do not want to install 1k deps on my local dev machine, but if it is lxc only and all i need is ansible on my dev mchine, that might be a good option too. (while i still do not understand how the network-lab will work out f | 12:50 |
| hrw | can we just drop that contrib/ dir? | 12:53 |
| eugenmayer | Is kolla openstack on LXC only (and why does it have an OS / distribution requirement then, containerd would be just fine?) | 12:54 |
| yoctozepto | the kolla ansible deploys in docker | 13:01 |
| mgoddard | eugenmayer: I think you may be confusing with openstack-ansible | 13:01 |
| yoctozepto | the kolla builds images using docker | 13:01 |
| yoctozepto | we don't touch LXC :-) like mgoddard said | 13:01 |
| eugenmayer | yoctozepto, not sure i understand. I understand that openstack services are packaged/build into docker images,right? | 13:04 |
| yoctozepto | eugenmayer: yes, that's what kolla does | 13:08 |
| yoctozepto | and then kolla-ansible utilises ansible to deploy those images on docker hosts | 13:09 |
| opendevreview | Merged openstack/kolla-ansible stable/xena: Update .gitreview for stable/xena https://review.opendev.org/c/openstack/kolla-ansible/+/813991 | 13:12 |
| eugenmayer | so the docker-compose orchestration is also handled by kolla @yoctozepto . So building/packagin and the deploying the stack, right? | 13:14 |
| opendevreview | Merged openstack/kolla-ansible master: Update master for stable/xena https://review.opendev.org/c/openstack/kolla-ansible/+/813993 | 13:16 |
| hrw | eugenmayer: kolla builds. kolla-ansible deploys. | 13:19 |
| hrw | eugenmayer: you may use one and skip second (when you build images for someone else). you may use second one only (when you use ready images). | 13:20 |
| opendevreview | Merged openstack/kolla-ansible stable/xena: Update TOX_CONSTRAINTS_FILE for stable/xena https://review.opendev.org/c/openstack/kolla-ansible/+/813992 | 13:21 |
| yoctozepto | eugenmayer: docker-compose is not used here | 13:29 |
| yoctozepto | ansible deploys to docker | 13:29 |
| eugenmayer | could you please explain, because in my worlf there is no 'deploy to docker' | 13:35 |
| eugenmayer | When you mean 'deploy to docker', are you refering it starts list of docker-containers in a containerd/docker-ce engine? Or are you refering to it deploys something in a single running docker container? | 13:36 |
| hrw | eugenmayer: you have hosts. hosts run docker daemon. kolla-ansible deploys to hosts using kolla built container images to run them in docker | 13:37 |
| hrw | eugenmayer: at the end you have hosts with several containers running. one-or-few containers per service as some openstack components have multiple containers for their services | 13:38 |
| eugenmayer | ok got it, so running a list of docker images on a container engine. Kolla is resposible to build those docker images (part 1) and also start them on a host (orchestration) | 13:39 |
| yoctozepto | eugenmayer: when you "run a container using docker" it means you "deploy a container on/to docker"; and there are multiple images, for different services | 13:39 |
| yoctozepto | kolla-ansible to start though, yes | 13:40 |
| yoctozepto | nowadays, we are looking to replace docker with podman | 13:40 |
| * hrw off | 13:41 | |
| eugenmayer | i see, most move to podman (more and more) | 13:41 |
| eugenmayer | Are those build images here also used for openstack-helm for the k8s deployment | 13:42 |
| eugenmayer | ? | 13:42 |
| yoctozepto | afaik they are using loci by default, not sure if they can use kolla images | 13:44 |
| eugenmayer | ok thanks you mean https://github.com/openstack/loci - make sense too, got it | 13:51 |
| *** bsanjeewa[m] is now known as bsanjeewa | 14:25 | |
| *** amoralej is now known as amoralej|off | 15:09 | |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: Add weight of haproxy backend also for custom members https://review.opendev.org/c/openstack/kolla-ansible/+/814027 | 15:18 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: Add weight of haproxy backend also for custom members https://review.opendev.org/c/openstack/kolla-ansible/+/814027 | 15:19 |
| opendevreview | Pierre Riteau proposed openstack/kayobe master: Add missing apt playbook for infrastructure VMs https://review.opendev.org/c/openstack/kayobe/+/814028 | 15:33 |
| frickler | yoctozepto: oh, is the plan really to replace docker? so far I assumed podman would just be added as a second option | 15:36 |
| yoctozepto | frickler: long term? likely; definitely not in Yoga, unlikely in Z; we will discuss it | 15:38 |
| yoctozepto | during the PTG | 15:38 |
| yoctozepto | :-) | 15:38 |
| yoctozepto | you like docker more? | 15:39 |
| opendevreview | Pierre Riteau proposed openstack/kayobe stable/victoria: Remove CentOS 7 image resolv.conf workaround https://review.opendev.org/c/openstack/kayobe/+/813934 | 16:04 |
| opendevreview | Pierre Riteau proposed openstack/kayobe stable/ussuri: Remove CentOS 7 image resolv.conf workaround https://review.opendev.org/c/openstack/kayobe/+/813935 | 16:04 |
| opendevreview | Merged openstack/kayobe master: Use merge_configs and merge_yaml to generate Kolla configs https://review.opendev.org/c/openstack/kayobe/+/804068 | 16:47 |
| frickler | actually I don't like either of them too much, but at least for docker there seem to be useable distro pkgs in ubuntu, which wasn't the case for podman last time I checked | 17:42 |
| opendevreview | Pierre Riteau proposed openstack/kayobe master: Add missing apt playbook for infrastructure VMs https://review.opendev.org/c/openstack/kayobe/+/814028 | 18:21 |
| opendevreview | Pierre Riteau proposed openstack/kayobe master: Add support for configuring proxy settings https://review.opendev.org/c/openstack/kayobe/+/814046 | 18:44 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!