expressadmin

We are planning to attend Zandvoort for the race on Sunday and we are staying in Amsterdam.

We plan on staying a couple of days extra in Amsterdam and we were looking at the "3-Day Amsterdam and Region Travel Ticket" instead of the standard "one day" grand prix ticket that is offered.

Does anybody know if that "Amsterdam and Region Travel Ticket" would allow us to travel to Zandvoort on race day as well? I tried to find out more information but can't seem to find specific information. The 1-day Grand Prix ticket seems to be the same price as the 1-Day travel ticket, so it seems like it would be accepted, but just looking for confirmation.

We are currently running a Ceph cluster on Ubuntu 22.04 running Quincy (17.2.7) with 3 OSD nodes with 8 OSDs per nodes (24 total OSDs).

We are looking for feedback or reports on what others have run into when upgrading the base OS while running Ceph containers.

We have hit some other snags in the past with things like RabbitMQ not running on older versions of a base OS, and required an upgrade to the base OS before the container would run.

Is anybody running a newish version of Ceph (reef or squid) in a container on Ubuntu 24.04? Is anybody running those versions on older versions like Ubuntu 22.04? Just looking for reports from the field to see if anybody ran into any issues, or if thing

A bit of a strange question here.

We have an Openstack deployment running with Neutron with OpenVSwitch handling our SDN functions. Everything is working correctly for us.

We have an operational request to set a network interface on a VM as "down". I know that this can be done using raw virsh (virsh-domif-setlink instance-0000000 tapxxxxxxxx down).

I was curious to know if anybody is aware of a way to accomplish this with Openstack's API or general application layer/module (i.e. could I write a module for Openstack Nova/Neutron to handle this operation).

Alternatively, if this feature is available in a newer version that would help light some fires on this side to get an upgrade windo

We currently have an Openstack cluster deployed with kolla-ansible that is running Ceph installed with ceph-ansible. We have finally gotten a dedicated Ceph cluster and we have moved those nodes into production (OSD and MGR).

We would like to migrate the currently running monitors from the Openstack nodes (they were running converged) to only the Ceph nodes. I have added the new Ceph nodes to the quorum, and I would like to move forward in shutting down the converged monitor instances and removing them from the quorum.

Has anyone done this in the past? Is the process as simple as replacing the ceph.conf in the /etc/kolla/config directories for nova, glance, and cinder then just running a

I was looking at our database usage recently and discovered that we have over 88K deleted instances in our database.

All of our instances are very transient. We provision a given template via Heat, do what we need to and then tear it all down again. So we move through a lot of instances on a daily basis.

No one really uses Horizon except for myself to investigate when things go wonky.

Are there any issues with running nova-manage db archive_deleted_rows --purge on a daily basis to keep things tidy in the nova database? We never really have to go back and look at an instance as they are truly treated as ephemeral.

Alternatively, is there a configuration option in nova.conf that I am

I have been using my MK730 for several years without any issue. Love the keyboard and the switches.

Recently I had an issue where my ESC, F1, F2 and F3 keys all stopped working. I have the keyboard configured where it will blink the LED after you press a key, and all other keys do that, but the ones listed above don't.

Tested them with a keyboard tester and they also don't register. They are still backlit correctly, just don't register key presses.

Has anybody ever had this happen to them? Have you taken the keyboard apart and tried to fix it? I checked it and it is out of warranty, so out of luck there.

I have another MK730 that I am using currently, but I would like to refurb this olde

We have a medium size Openstack cluster deployed via Kolla-ansible. We need to make a patch to Nova to allow for a corner case on a few VMs running in this cluster.

Has anybody done this?

If so, do you have a guide on how to do it?

Ideally I would just like to patch the actual docker image for nova-compute, and not have to rebuild the entire kolla image collection (kolla-build).

I am wondering if someone can assist me in clearing up my understanding of what is happening here. We are running a somewhat recent version of Octopus (15.2.8) with 3 MONs, and 4 OSDs.

We recently had the following error crop up in Ceph status and I am not exactly sure what it is telling me.

[WRN] LARGE_OMAP_OBJECTS: 4 large omap objects
    4 large objects found in pool 'default.rgw.buckets.index'
    Search the cluster log for 'Large omap object found' for more details.

Clearly we have some large buckets in the buckets.index pool. However, I am pretty sure that rgw_dynamic_resharding is defaulted to True, so shouldn't these bucket indexes be resharded automatically?

Or is t

I have submitted a ticket to vmware already about this, but I was hoping maybe the gurus might have some additional insight that I might be missing here.

We are running vCenter 7.0, with VCD (Orgs show up as compute resources in vCenter). We are trying to catch HA based events for VMs for a specific customer.

We have created a simple alarm at the vcenter level, and have it watching for all vm based events. Specifically "HA is resetting a VM" and send an email. We then place a VM on a test host and reboot the host without placing it into maintenance mode.

We do get emails for the host being down (we have an alert for that already, so we know that the emails work), and I can see the HA even

It took them a few hours to get everything setup, but they now have the packages out there. So if you were using the repos, update now to patch the security exploit on the Salt Master.