| *** EugenMayer4401809 is now known as EugenMayer440180 | 08:23 | |
| crab | i have a small cluster which is entirely x86_64 with the exception of a single aarch64 node. | 16:17 |
|---|---|---|
| crab | at the moment if i create an instance, i select an appropriate image (either x86_64 / or aarch64 as appropriate) and then i select a flavour. i don't think (but im not 100% sure) we do anything special with the images, | 16:17 |
| crab | but with the flavours we have metadata in the properties field which selects either an x86_64 node or an aarch64 node. | 16:18 |
| crab | we do something similar if we want a node with gpus too. | 16:18 |
| crab | however, with our octavia setup we dont have any flavours - just images | 16:18 |
| crab | and ive noticed that our x86_64 images are trying to start on the arm machine and unsurprisingly its not working well. | 16:19 |
| crab | i guess the question is what is best practice in this situation? should we think about creating flavours for octavia too and using them in the same way, or is there some way we can make sure that the x86_64 lb images dont try and start on arm? and what is best practice (if there is any in this area) ? | 16:20 |
| crab | oops. git obsessed with best practice here. :( | 16:20 |
| crab | *bit even | 16:20 |
| johnsom | Yes, there is a way to mark images with metadata that will allow the automatic selection of the correct image for the compute architecture. | 17:36 |
| johnsom | See: https://docs.openstack.org/glance/latest/admin/useful-image-properties.html#image-property-keys-and-values | 17:37 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!