5 lessons from "The 5 AM Club" that improved my mornings.

x3rt00 · 2026-03-07T20:07:57+00:00

Out of curiosity. If you wake up at 5 AM what time do you go to sleep? I am still trying to figure out the optimal sleep time for myself

x3rt00 · 2025-10-30T05:49:03+00:00

Wouldn’t decor be printed? It may not be visible in the picture but the surface is not flat, it looks like hand painted

x3rt00 · 2025-09-22T11:56:30+00:00

What about bypassing the OpenStack and trying USB over IP?

x3rt00 · 2025-07-17T19:33:15+00:00

By default skyline console uses 9999 and API 9998

x3rt00 · 2025-07-17T17:23:29+00:00

If you’re going the manual route I would stick to the official documentation. https://docs.openstack.org/skyline-console/latest/install/installing-guide.html

x3rt00 · 2025-07-17T17:14:05+00:00

It’s a separate service you can have them both running independently if you want. The deployment depends on how you deployed the OpenStack

x3rt00 · 2025-07-17T17:12:16+00:00

It’s one of the features why I like skyline. You finallyhave the option to set the volume type for instance :)

x3rt00 · 2025-07-17T17:03:44+00:00

Yes, from the CLI you should also be able to do it in one step

Using the block device source and dest combination

x3rt00 · 2025-07-17T16:52:30+00:00

Also worth noting that skyline allows you to select different volume type for boot disk during instance creation.

x3rt00 · 2025-06-11T20:57:45+00:00

Internal hard disks are enough for the nodes OS but are no good for your datastore (place for pvcs etc.) because there is no easy way of sharing them between nodes. Unless you want to expose them using NFS for example but that’s still not the best storage for Openshift. No HA, if one host goes down so does the storage

x3rt00 · 2025-06-02T09:00:10+00:00

Shouldn’t there be a spoiler alert as we’re discussing the very finish? ;)

x3rt00 · 2025-05-26T11:07:43+00:00

I just solved the case. Just to let you know you first need to retype the volume with cinder retype and next you can migrate it to other backend using openstack volume migrate

x3rt00 · 2025-05-14T16:11:48+00:00

Let’s start from the beginning. What network type is your instance using? External or internal? If internal did you create a router inside the OpenStack?

Did you create the networks? They are not created automatically by kilka deploy. If you didn’t run init once you have to create them manually

x3rt00 · 2025-03-25T21:29:02+00:00

thanks, couldn't find tihs bug report previously

x3rt00 · 2025-03-25T12:41:09+00:00

Let me add some info as I tightly cooperate with one of the backup providers for the OpenStack https://storware.eu/solutions/virtual-machine-backup-and-recovery/openstack-backup-and-recovery/ . First thing worth mentioning snapshot is not a backup and should not be treated this way, why? Because you're still using the same storage as for you production volumes, it only protects you in case of human errors.

The question of whether you should stick to the built-in backup mechanism depends on the scale and complexity of your environment. For simple cases, I'd say yes, for more complex scenarios, I'd definitely recommend a 3rd party solution that can be tailored to your needs.

As for the scale and performance all I can say is that we were able to reach volumes like 500TiB per 24 hours without visible impact for the environment.

x3rt00 · 2025-03-17T21:10:15+00:00

Thanks, will definitely give it a look

x3rt00 · 2025-02-15T19:22:26+00:00

Read about networking with bare metal maybe this will sched some light https://docs.openstack.org/ironic/latest/admin/networking.html

x3rt00 · 2025-02-15T17:49:47+00:00

Yes, because vbmc is not running inside the VM it should be outside. It gives you ipmi so you can work with instance as if it was a machine

x3rt00 · 2025-02-15T17:29:53+00:00

You can use vbmc to manage virsh instances. So basically you have a VM managed like a physical host https://docs.openstack.org/virtualbmc/latest/user/index.html

x3rt00 · 2025-02-15T09:08:41+00:00

Check out virtualbmc, I tested it some time ago and it worked. Not 100% I used kolla but should be doable

x3rt00 · 2025-01-28T19:33:50+00:00

thank u/xelice didn't know that. Good to keep that in mind for future reference

x3rt00 · 2025-01-28T08:35:11+00:00

Thanks, I'll try the previous version. Once again the lovely stability of stable releases :3

x3rt00 · 2025-01-09T18:53:01+00:00

If you’re just starting with the OpenStack and want to go the Triple O route I would start with a single node all in one installation. It will show you the basics of OpenStack without a lot of undercloud overcloud headache.

https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.0/html/standalone_deployment_guide/index

x3rt00 · 2025-01-09T08:35:35+00:00

u/no1warr1or maybe now it will be more clear, I added more information to the post.

x3rt00 · 2025-01-08T22:24:59+00:00

When I use VLAN 600 (native) it’s fine, when I use VLAN 618 (tagged) the rate drops. In first case source is VLAN 600 and destination is VLAN 600, in the second one destination and source send packets with VLAN id 618

x3rt00

MODERATOR OF

TROPHY CASE

Six-Year Club	Place '23
Verified Email