| *** gkadam has joined #openstack-kayobe | 04:28 | |
| *** egonzalez has joined #openstack-kayobe | 06:24 | |
| *** dougsz_ has joined #openstack-kayobe | 08:26 | |
| *** ktibi has joined #openstack-kayobe | 08:37 | |
| verdurin | Morning. Just saw that the seed VM requires python-setuptools. Happy to create a ticket noting that requirement if it would be useful. | 08:41 |
|---|---|---|
| ktibi | verdurin, hi | 08:52 |
| ktibi | verdurin, yes you can open a bug with the fail thx ;) | 08:52 |
| ktibi | verdurin, do you run : kayobe seed host configure ? | 08:53 |
| verdurin | ktibi: yes | 08:54 |
| ktibi | verdurin, what is the task which fail ? | 08:56 |
| verdurin | ktibi: that's too far back in my history, but I think it was ansible/kayobe-target-venv.yml | 08:57 |
| ktibi | verdurin, ok maybe it's when kayobe create the virtualenv | 08:58 |
| verdurin | ktibi: yes | 08:58 |
| ktibi | I remember maybe same issue | 08:58 |
| ktibi | what is your workarround ? | 08:59 |
| verdurin | ktibi: I just installed that RPM and then it worked. | 08:59 |
| openstackgerrit | Mark Goddard proposed openstack/kayobe stable/pike: Fix stable/pike branch https://review.openstack.org/588213 | 08:59 |
| ktibi | cat you check in your /etc/yum.repos.d | 08:59 |
| ktibi | if you have exclude=python-virtualenv python-pip python-setuptools | 08:59 |
| verdurin | ktibi: no, nothing like that. It was freshly created yesterday with no special configuration. | 09:00 |
| *** ktibi has quit IRC | 09:00 | |
| *** ktibi has joined #openstack-kayobe | 09:01 | |
| verdurin | Here's the issue I've opened: https://storyboard.openstack.org/#!/story/2003380 | 09:01 |
| ktibi | * /etc/yum.conf sorry | 09:01 |
| ktibi | verdurin, thx for open ticket | 09:02 |
| ktibi | verdurin, disk-image-builder create image for seed | 09:03 |
| ktibi | and add this conf I don't know why >< Nothing in your /etc/yum.conf ? | 09:03 |
| verdurin | ktibi: I built the seed myself; there's nothing beyond the defaults in /etc/yum.conf | 09:07 |
| ktibi | ok ;) I think it's because your build the seed yourself. We need to add this step in kayobe when the seed is already provisioned | 09:09 |
| verdurin | I now have a different problem with Docker configuration on the seed: https://storyboard.openstack.org/#!/story/2003381 | 09:11 |
| openstackgerrit | Mark Goddard proposed openstack/kayobe master: Install setuptools when using easy_install https://review.openstack.org/590197 | 09:12 |
| *** mgoddard has joined #openstack-kayobe | 09:12 | |
| mgoddard | hi verdurin, that last patch should resolve https://storyboard.openstack.org/#!/story/2003380 | 09:13 |
| mgoddard | one recommendation I have is to use a virtualenv for remote operations. This is not enabled by default, but can be done by modifying the inventory as described at http://kayobe.readthedocs.io/en/latest/configuration/kayobe.html#remote-execution-environment | 09:15 |
| ktibi | verdunrin try rm -rf /usr/lib/python2.7/site-packages/ipaddress* | 09:15 |
| verdurin | mgoddard: yes, looks like that would solve the Docker problem I have now. Thanks for the patch. | 09:15 |
| verdurin | ktibi: I'll undo the yum installations and test the patch | 09:16 |
| mgoddard | verdurin: here is an example of how to do it: https://github.com/stackhpc/eod-kayobe-config/blob/master/etc/kayobe/inventory/group_vars/seed/python-interpreter | 09:16 |
| mgoddard | and https://github.com/stackhpc/eod-kayobe-config/blob/master/etc/kayobe/inventory/group_vars/overcloud | 09:16 |
| mgoddard | I would like to put this into the default kayobe-config, but it gets a little messy due to ansible not allowing the ansible_python_interpreter to use jinja templates to reference {{ venv_path }}. Perhaps we should just take that hit and document it | 09:17 |
| openstackgerrit | Mark Goddard proposed openstack/kayobe stable/pike: Fix stable/pike branch https://review.openstack.org/588213 | 10:01 |
| *** priteau has joined #openstack-kayobe | 10:07 | |
| *** gkadam has quit IRC | 10:13 | |
| *** gkadam has joined #openstack-kayobe | 10:13 | |
| openstackgerrit | Merged openstack/kayobe master: Install setuptools when using easy_install https://review.openstack.org/590197 | 11:06 |
| verdurin | What's the Kayobe way of achieving https://www.stackhpc.com/tripleo-dib-ofed.html? | 11:28 |
| verdurin | I had that working nicely when I was using TripleO. Would like to do the same with Kayobe. | 11:29 |
| mgoddard | verdurin: which part in particular? Different images for different machines, custom DIB elements, or both? | 12:26 |
| mgoddard | both are possible, although neither is particularly well integrated currently | 12:26 |
| mgoddard | this covers the former: https://storyboard.openstack.org/#!/story/2002098 | 12:27 |
| mgoddard | the overcloud image config is defined in etc/kayobe/bifrost.yml | 12:30 |
| mgoddard | the bifrost container deployment (seed service deploy) includes building an image via DIB | 12:35 |
| mgoddard | the image ends up at /httpboot/deployment_image.qcow2 in the bifrost_deploy container | 12:35 |
| mgoddard | you can set the image to use on a per-host basis in bifrost, via the deploy_image_filename variable | 12:36 |
| mgoddard | we generate per-host variables for bifrost in ansible/kolla-bifrost-hostvars.yml, and we could add the name of the image to use here | 12:37 |
| mgoddard | that would get us different images per host | 12:37 |
| mgoddard | to build multiple images, would require a bifrost change, or to build them outside of bifrost (e.g. stackhpc.os-images) and copy them into place | 12:38 |
| verdurin | mgoddard: primarily I want to include custom DIB elements, notably the mlnx-ofed one, on all machines | 12:50 |
| mgoddard | verdurin: oh ok. The part that's missing is getting the custom image elements into the bifrost_deploy container | 12:53 |
| mgoddard | you can set kolla_bifrost_dib_elements, kolla_bifrost_dib_env_vars and kolla_bifrost_dib_packages to customise the image, including adding ELEMENTS_PATH in your environment | 12:59 |
| mgoddard | I suspect there's a bit of chicken and egg here though since the image is built during deployment of the bifrost_deploy container | 12:59 |
| mgoddard | you either need to add support for cloning an elements repo to bifrost, or skip the image build during deploy and do it afterwards | 13:03 |
| mgoddard | you could that by setting create_image_via_dib: false in etc/kayobe/kolla/config/bifrost/dib.yml | 13:04 |
| mgoddard | all untested... | 13:04 |
| *** egonzalez has quit IRC | 13:06 | |
| verdurin | mgoddard: I think I'll write a playbook to handle this post-deployment for now. Shall I open a ticket to suggest handling this properly? | 13:12 |
| mgoddard | verdurin: yes, please do | 13:13 |
| *** gkadam_ has joined #openstack-kayobe | 14:26 | |
| *** gkadam has quit IRC | 14:30 | |
| verdurin | Another question - do you support booting uEFI machines? I noticed there's no ipxe.efi, as I had with TripleO. | 14:46 |
| mgoddard | bifrost should support UEFI, although I haven't tried it | 14:48 |
| verdurin | Hmm, not sure it was ever finished: https://review.openstack.org/#/c/268808/ | 14:49 |
| *** priteau has quit IRC | 14:52 | |
| mgoddard | verdurin: as I imagine you've seen in #openstack-ironic, you are right - the work was not finished | 14:57 |
| mgoddard | we have used /etc/dnsmasq.d/ in other projects to customise the dnsmasq config, which would be one step closer | 14:59 |
| mgoddard | see ansible/roles/dell-switch-bmp in kayobe | 14:59 |
| mgoddard | that role doesn't belong in kayobe these days but that's another issue | 15:00 |
| mgoddard | I'm sure TheJulia would appreciate validation of the approach in that review | 15:04 |
| verdurin | Yes, I was going to see if I could hack it with dtantsur's suggestions | 15:06 |
| *** priteau has joined #openstack-kayobe | 15:37 | |
| *** gkadam_ has quit IRC | 16:32 | |
| *** ktibi has quit IRC | 16:37 | |
| *** dougsz_ has quit IRC | 16:50 | |
| *** mgoddard has quit IRC | 17:02 | |
| *** priteau has quit IRC | 18:15 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!