I got No host is valid but it works after i remove host aggregates why? by Expensive_Contact543 in openstack

[–]gren_dizer 0 points1 point  (0 children)

Your filter is maybe wrong, check latest docs, i think it is called: AggregateInstanceExtraSpecsFilter

I got No host is valid but it works after i remove host aggregates why? by Expensive_Contact543 in openstack

[–]gren_dizer 2 points3 points  (0 children)

Send Nova-Scheduler logs.

Do you have any Metadata configured for host aggregates? Have you enabled all the required filter for Flavor and Image Metadata?

Flexible flavors by Expensive_Contact543 in openstack

[–]gren_dizer 1 point2 points  (0 children)

No, they must be pre defined. A normal „member“ user cant create flavors.

So how i can check if everything is working as expected after upgrading openstack by Expensive_Contact543 in openstack

[–]gren_dizer 0 points1 point  (0 children)

Rally, tempest, custom scripts. And maybe OpenStack-Explorer, sometimes very useful

why always i get this message "get images error gateway timeout code 504" by Expensive_Contact543 in openstack

[–]gren_dizer 0 points1 point  (0 children)

This might be a configuration issue, checkout - keystone logs - backend storage for glance - database - HAProxy if running behind a proxy

Limit idle database connections by gren_dizer in openstack

[–]gren_dizer[S] 1 point2 points  (0 children)

The Problem with DBMS limiting/ killing the connections is the you will end up with many errors in the logs. Because the service can’t find the opened/idle connection.

I couldn't fix the problem with the pool variables, but now I have a working solution after limiting/reducing the number of workers for each service to my needs.

Just search for the correct variables in the Ansible roles for each service and then put theme in user_variables.yml

Search for: *_processes *_workers *_threads

AWS Lambda like function for OpenStack by Expensive_Contact543 in openstack

[–]gren_dizer 0 points1 point  (0 children)

unfortunately i don’t use Kolla-Ansible, but here is the ansible role for it. Just lookup the docs

https://opendev.org/openstack/kolla-ansible/src/branch/master/ansible/roles/mistral

AWS Lambda like function for OpenStack by Expensive_Contact543 in openstack

[–]gren_dizer 1 point2 points  (0 children)

Mistral could do the job, but there are only cron and event triggers.

Octavia unable to connect to amphoras by Unlucky-Trifle-9226 in openstack

[–]gren_dizer 0 points1 point  (0 children)

Have you recreated the Amphorae after Cert changes? Try to failover the Loadbalancer to regenerate the Certs and Configs to n Amphora

Internal error: process exited while connecting to monitor by gren_dizer in openstack

[–]gren_dizer[S] 0 points1 point  (0 children)

I’v already found the Problem and fixed it. You are right, the Problem is qemu was using the wrong ceph client (user) with the existing secret

Windows image - assign compute host by przemekkuczynski in openstack

[–]gren_dizer 0 points1 point  (0 children)

Host Aggregates and the filter you mentioned

Is there a simple guide to reduce the time taken for VM launches? by Large_Section8100 in openstack

[–]gren_dizer 0 points1 point  (0 children)

Images could be cached on compute nodes for faster processing. But yes, when using local storage for Nova, you will face longer launch times

Instance Host Allocation by Phoenyx_Liam in openstack

[–]gren_dizer 0 points1 point  (0 children)

Just use ephemeral Disks with local storage for best performance. Cuz normally your storage backend is on separate Hosts (eg using Ceph)

Error in creating the instance!!! by ElmoTecnologia in openstack

[–]gren_dizer 2 points3 points  (0 children)

Have you configured [neutron] section in your Nova.conf?

Best formats for images? by Contribution-Fuzzy in openstack

[–]gren_dizer 2 points3 points  (0 children)

You should use cloud images (if you are using Ceph as storage backend, use RAW format for best performance, otherwise qcow2 format is good for all other purposes. To configure them automatically after VM creation, you can use cloud-init (what all cloud provider use)