*** mazzy509881 is now known as mazzy50988 | 00:10 | |
*** mazzy509889 is now known as mazzy50988 | 00:34 | |
opendevreview | wushiming proposed openstack/kolla-ansible master: Replace deprecated assertRaisesRegexp https://review.opendev.org/c/openstack/kolla-ansible/+/816938 | 01:03 |
---|---|---|
*** r3ap3r_ is now known as r3ap3r | 02:46 | |
osmanlicilegi | morning | 10:22 |
jingvar | afternoon is for me :) | 10:39 |
kevko | morning :) | 10:46 |
opendevreview | Ibrahim DERRAZ proposed openstack/kolla-ansible master: rabbitmq: add node parameter in rabbitmq_user call https://review.opendev.org/c/openstack/kolla-ansible/+/817190 | 11:09 |
DK4 | is kolla fully functionable with xenia release yet? | 11:24 |
opendevreview | Merged openstack/kolla stable/xena: Debian: we want Openvswitch and ovn from backports https://review.opendev.org/c/openstack/kolla/+/816657 | 11:49 |
shyamb | Hi | 12:23 |
shyamb | With template-override option, If I want to add a file to container using 'ADD' command, where should I keep that file | 12:24 |
shyamb | ? | 12:24 |
shyamb | On build server? | 12:24 |
shyamb | --working-dir ? | 12:24 |
shyamb | or --docker-dir? | 12:25 |
shyamb | If I keep that file in current dir from where I am running kolla-build command, it's throwing error: https://paste.openstack.org/show/810870/ | 12:27 |
shyamb | hrw: ^^ | 12:27 |
hrw | shyamb: same dir as Dockerfile.j2 is | 12:28 |
hrw | easiest way | 12:29 |
shyamb | okay | 12:29 |
opendevreview | Verification of a change to openstack/kayobe-config-dev master failed: Fix configuration sync for infra-vms https://review.opendev.org/c/openstack/kayobe-config-dev/+/816848 | 12:33 |
shyamb | hrw: I cloned this repo: "https://github.com/openstack/kolla" | 12:34 |
shyamb | If I want to tell kolla-build command to use this repo, do I need to specify --working-dir? | 12:35 |
shyamb | or config-dir? | 12:35 |
hrw | shyamb: cd kolla;pip install .; kolla-build | 12:36 |
hrw | or even ./tools/build.py instead of kolla-build | 12:36 |
shyamb | hrw: okay, then just running kolla-build command from koll/ dir will take care of it? | 12:37 |
hrw | yes | 12:37 |
shyamb | hrw: okay, thanks | 12:38 |
hrw | my way is "initialize kolla virtualenv", "cd ~/devel/linaro/kolla/" and then use kolla-build-images.sh from https://github.com/hrw/docker-utils/blob/master/kolla-build-images.sh | 12:38 |
opendevreview | Adrian Andreias proposed openstack/kolla-ansible master: docs: Get release name dynamically https://review.opendev.org/c/openstack/kolla-ansible/+/816582 | 13:11 |
opendevreview | Adrian Andreias proposed openstack/kolla-ansible master: docs: Install openstack-client with upper constraints https://review.opendev.org/c/openstack/kolla-ansible/+/816076 | 13:23 |
opendevreview | Martin Hiner proposed openstack/kolla-ansible master: Systemd container control PoC https://review.opendev.org/c/openstack/kolla-ansible/+/816724 | 13:25 |
holtgrewe | I have a conceptual question. I have four servers "stack-1" ... "stack-4" that I want to have as controllers but also non-baremetal compute. These would go into etc/kayobe/inventory/host - but would they also be discovered by the ironic driver? | 15:45 |
jingvar | holtgrewe: it is about bifrost/ironic? | 16:00 |
JohnB | In which vlan should we place our switches and pdu's in combination with kayobe? I would guess everything needs to be connected to the "overcloud admin" vlan, but can't find any proof. | 16:44 |
mgoddard | holtgrewe: are you referring to 'kayobe overcloud inventory discover' ? | 16:44 |
mgoddard | holtgrewe: that command will discover hosts via bifrost's ironic node list, and add them to etc/kayobe/inventory/overcloud | 16:45 |
mgoddard | JohnB: are you referring to the management port of switches and pdus? | 16:45 |
JohnB | Yes. This is about de management port of switches and PDU's. | 16:46 |
mgoddard | JohnB: there is no strict requirement there. you need L3 connectivity from the ansible control host to switch management ports if you want to manage them via kayobe | 16:48 |
mgoddard | JohnB: by pdus, do you mean BMCs or PDUs? | 16:49 |
JohnB | Well, actually. I would mean both. BMC's for the overcloud/workload nodes. And PDU's to kill the power if needed. | 16:50 |
opendevreview | Merged openstack/kayobe-config-dev master: Fix configuration sync for infra-vms https://review.opendev.org/c/openstack/kayobe-config-dev/+/816848 | 16:54 |
kevko | hmm, where is kolla downloading tarballs ? | 17:01 |
kevko | i have kolla templates generated ..but can see only ADD keystone-base-archive /keystone-base-source < for keystone for example | 17:02 |
mgoddard | JohnB: for BMCs you need L3 connectivity from the seed and from the controllers if using baremetal compute | 17:02 |
mgoddard | JohnB: PDUs can go where you like - kayobe won't touch them | 17:02 |
mgoddard | JohnB: https://docs.openstack.org/kayobe/latest/configuration/reference/network.html#network-to-host-mapping | 17:03 |
mgoddard | https://docs.openstack.org/kayobe/latest/configuration/reference/network.html#network-role-configuration | 17:04 |
mgoddard | typically we might use a separate network for BMCs, defined via oob_oc_net_name | 17:04 |
mgoddard | or oob_wl_net_name if using baremetal compute (these may be the same network) | 17:05 |
JohnB | We won't combine oob_oc_net_name and oob_wl_net_name as this gave us much headache during our POC. The controller nodes got mixed up with the baremetal compute nodes. | 17:08 |
JohnB | mgoddard: For the BMC it's sorted out. We will split them. But if separating the network for OC and WL would that give problems on 'kayobe physical network configure'? | 17:11 |
opendevreview | Mark Goddard proposed openstack/kayobe master: Remove chrony cleanup from overcloud host configure https://review.opendev.org/c/openstack/kayobe/+/817279 | 17:11 |
mgoddard | JohnB: it's up to you where you put the switch management ports. It could be one of those OOB networks, or a separate one | 17:12 |
mgoddard | JohnB: out of interest, where are you from? | 17:13 |
JohnB | mgoddard: Thanks for the information. | 17:21 |
JohnB | mgoddard: We're from The Netherlands. | 17:21 |
mgoddard | JohnB: nice - which org? | 17:22 |
JohnB | mgoddard: I can't fully disclose that atm. | 17:23 |
mgoddard | JohnB: np | 17:23 |
opendevreview | Mark Goddard proposed openstack/kayobe master: Revert "Use OpenStack Xena release" https://review.opendev.org/c/openstack/kayobe/+/817281 | 17:32 |
opendevreview | Mark Goddard proposed openstack/kayobe master: [release] Set previous_release to xena https://review.opendev.org/c/openstack/kayobe/+/817282 | 17:32 |
opendevreview | Mark Goddard proposed openstack/kolla-ansible master: [release] Set previous_release to xena https://review.opendev.org/c/openstack/kolla-ansible/+/817284 | 17:37 |
opendevreview | Mark Goddard proposed openstack/kolla master: docs: add master branch preparation to release management https://review.opendev.org/c/openstack/kolla/+/817285 | 17:46 |
opendevreview | James Kirsch proposed openstack/kolla master: Add LetsEncrypt images for cert request/renewal https://review.opendev.org/c/openstack/kolla/+/741339 | 19:40 |
opendevreview | Merged openstack/kolla-ansible master: Fix octavia doesn't set subnet gateway_ip https://review.opendev.org/c/openstack/kolla-ansible/+/817034 | 21:07 |
opendevreview | Merged openstack/kolla-ansible master: Replace deprecated assertRaisesRegexp https://review.opendev.org/c/openstack/kolla-ansible/+/816938 | 21:07 |
opendevreview | Merged openstack/kolla-ansible master: docs: Fix python-openstackclient package name and init-runonce path https://review.opendev.org/c/openstack/kolla-ansible/+/816074 | 21:07 |
opendevreview | Adrian Andreias proposed openstack/kolla-ansible master: docs: Install openstack-client with upper constraints https://review.opendev.org/c/openstack/kolla-ansible/+/816076 | 22:43 |
opendevreview | Adrian Andreias proposed openstack/kolla-ansible master: docs: Install openstack-client with upper constraints https://review.opendev.org/c/openstack/kolla-ansible/+/816076 | 23:18 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!