- openstack-discuss - lists.openstack.org

[Neutron] Future of TripleO OVN migration in-tree code
by Jakub Libosvar 17 Apr '23

17 Apr '23

Hello Neutrinos and others, as this has been brought up several times through some conversation channels with no consensus, I wanted to start a discussion and possibly find a consensus about the code for migrating an OpenStack from OVS mechanism driver to OVN [1]. The code leverages TripleO to install and to configure OVN services, however the TripleO project is no longer maintained after Zed release [2]. This brings up the question what to do with the migration tooling that relies on TripleO. Shall we remove the code completely or is there anybody who would be interested in maintaining that code and implement support for other installers? Thanks Kuba [1] https://opendev.org/openstack/neutron/src/branch/master/tools/ovn_migration… [2] https://review.opendev.org/c/openstack/governance/+/878799

2 2

[kolla] Reducing ceilometer, gnocchi, aodh time interval
by Modyngs 17 Apr '23

17 Apr '23

Dear lists, Hi I have recently noticed of this link to customize configurations to be overridden [Thanks to michal nasiadka]: https://docs.openstack.org/kolla-ansible/latest/admin/advanced-configuratio… but i have some doubts in regards! The docs says /etc/kolla/ config/<< service name >>/<< config file >> (Ex. /etc/kolla/config/nova/nova-scheduler.conf) let's say i want to change interval to 30sec (* 'interval: 30'*) in *'/etc/kolla/ceilometer-central/polling.yaml'* file: as i understood, i need to create a file in *'/etc/kolla/config/ceilometer-central/polling.yaml'* and copy all the contents of * '/etc/kolla/ceilometer-central/polling.yaml'* into it ( *or just the change?*) and then change just the *interval from 300 to 30 .* Am I doing Right? ( because there was no [DEFAULT] section available in the polling.yaml file ....) After doing the same for all the desired files, then i need to do prechecks and deploy? kolla-ansible -i /etc/kolla/all-in-one prechecks kolla-ansible -i /etc/kolla/all-in-one deploy Thanks

1 0

[largescale-sig] Next meeting: April 19, 15utc
by Thierry Carrez 17 Apr '23

17 Apr '23

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC, our EU+US-friendly time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230322T14 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[tc] Technical Committee next weekly meeting on 2023 April 18 at 1800 UTC
by Nikolla, Kristi 16 Apr '23

16 Apr '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday (April 18) at 1800 UTC on #openstack-tc on OFTC IRC Items can be proposed by editing the wiki page at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Unless there are last minute additions (for which I will send a follow-up email) the agenda will be: • Roll call • Follow up on past action items • gmann respond to Sahara PTL volunteer to propose a patch to governance, and explain the outcome of today's discussion • jamespage to write email about Winstackers removal • Gate health check • 2023.2 cycle Leaderless projects • https://etherpad.opendev.org/p/2023.2-leaderless • Broken docs due to inconsistent release naming • Recurring tasks check • Bare 'recheck' state • https://etherpad.opendev.org/p/recheck-weekly-summary • Open Reviews • https://review.opendev.org/q/projects:openstack/governance+is:open Thank you, Kristi Nikolla

1 0

Installation
by BEDDA Fadhel 14 Apr '23

14 Apr '23

Bonjour, Ou je peux trouver pour tester openstack sur Ubuntu 22.04 Cordialement

3 2

[tc][all] What's happening in the Technical Committee - 2023 April 14
by Nikolla, Kristi 14 Apr '23

14 Apr '23

Hi all, Here’s another edition of “What’s happening on the Technical Committee.” Meeting ======= The Technical Committee met on April 11 on the #openstack-tc channel on OFTC IRC. The next weekly meeting will happen on April 18th. For more information visit https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Happenings ========== Final call for Winstackers (and Windows Support) ------------------------------------------------ Cloudbase Solutions are no longer in a position to maintain support for running OpenStack on Windows and have also ceased operation of their 3rd party CI for the windows support across a number of OpenStack projects. This is the final call for any maintainers to step forward for maintaining Winstackers if this feature is important to them in OpenStack[0][1]. If there is no response by June 2023, we will discuss the retirement of this project. [0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033342.h… [1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033273.h… Final call for Vitrage maintainers ---------------------------------- This is the final call for maintainers. If anyone is using or interested in this project, this is the right time to step up. If there is no response by the end of April 2023, we will discuss the retirement of this project.[0] [0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033348.h… Patrole retirement ------------------ As notified on the mailing list yesterday[0] and by a patch proposed to the governance repo[1], the Patrole project is being retired. The project is inactive, and there was no interest from prospective maintainers. [0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033346.h… [1]. https://review.opendev.org/c/openstack/governance/+/880014 Gate status ----------- Every week we have a look at the overall status of the "gate". In the last meeting the status was reported and not super healthy[0]. * The U-C bump broke Glance's functional test and there is a desire to put Glance's functional tests behind the U-C gate so that future breakages are caught before they happen. * It was also reported that we were seeing some guest kernel crashes on volume tests. These may be related to nested virtualization. [0]. https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-11-17.59.log.html#… Changes ======= * Merged * Add ovn-bgp-agent to Neutron governed projects (project-update) | https://review.opendev.org/c/openstack/governance/+/879455 * Add xstatic-angular-fileupload as Horizon team deliverables (project-update) | https://review.opendev.org/c/openstack/governance/+/873845 * Retire puppet-tacker - Step 3: Retire Repository (project-update) | https://review.opendev.org/c/openstack/governance/+/875295 * New Open * Appoint Jerry Zhou as Sahara PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/879847 * Retire patrole (project-update) | https://review.opendev.org/c/openstack/governance/+/880014 * Correct the old deprecated policies removal timeline for SLURP release (formal-vote) | https://review.opendev.org/c/openstack/governance/+/880238 * Add missing governance-sigs repo in technical-committee-repos.yaml (project-update) | https://review.opendev.org/c/openstack/governance/+/880237 * Retire puppet-rally - Step 3: Retire Repository (project-update) | https://review.opendev.org/c/openstack/governance/+/880018 * All Open * https://review.opendev.org/q/project:openstack/governance+status:open How to contact the TC ===================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send an email with the tag [tc] on the openstack-discuss mailing list. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 16:00 UTC 3. IRC: Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC.

1 0

[glance][cinder]create volume from image too slow
by Nguyễn Hữu Khôi 14 Apr '23

14 Apr '23

Hello guys. I am using nfs for glance and SAN for cinder but when i create 1 gb volume with 100mb image(Converted 112.00 MB image at 25.4 MB/s) then it will fast. however, if I create 100gb volume with 100mb image(Converted 112.00 MB image at 8.24 MB/s) then it will very slow. Pls give me some advices. ty Nguyen Huu Khoi

1 1

[neutron] Drivers meeting agenda
by Rodolfo Alonso Hernandez 14 Apr '23

14 Apr '23

Hello Neutrinos: Remember we have the Neutron drivers meeting today at 14UTC. The agenda is here: https://wiki.openstack.org/wiki/Meetings/NeutronDrivers Regards.

1 0

[Controller/Infra node removal] [openstack-ansible] Need to remove infra/controller node from environment.
by Danish Khan 14 Apr '23

14 Apr '23

Hello Team, Is it possible to remove an infra host from environment? If yes, can you please share the exact steps that need to be followed. I am trying to remove it manually by destroying all lxc containers from infra host which needs to be removed and then running setup openstack playbook. but it is not working properly. Can someone please share the exact steps needed to be followed to remove infra host from the environment. Openstack version: Wallaby or Yoga. Regards, Danish

2 1

[kolla-ansible][yoga] is there a way to deploy or reconfigure a container to run in privileged mode?
by wodel youchi 14 Apr '23

14 Apr '23

Hi, Is there a way to deploy or reconfigure a container to run in privileged mode? I need to make glance-api run in privileged mode. Regards.

2 1

[ptl] Need PTL volunteer for OpenStack Winstackers
by Ghanshyam Mann 13 Apr '23

13 Apr '23

Hi Lukas, I am reaching out to you as you were PTL for OpenStack Winstackers project in the last cycle. There is no PTL candidate for the next cycle (2023.2), and it is on the leaderless project list. Please check if you or anyone you know would like to lead this project. - https://etherpad.opendev.org/p/2023.2-leaderless Also, if anyone else would like to help leading this project, this is time to let TC knows. -gmann

7 14

[qa][patrole] Retiring Patrole project
by Ghanshyam Mann 13 Apr '23

13 Apr '23

Hello Everyone, You might know that Patrole project[1] which was created to test the RBAC but had some design challenges, and we never got much attention to this project to align it with the new SRBAC or efficient way to test the RBAC. Since the last couple of years (After AT&T's focus was changed from OpenStack), we hardly had any maintainer in this project. In this cycle, the QA team decided to retire this project. There is always an option to bring it back in OpenStack if anyone is interested in maintaining it. I have pushed the changes required for retirement, including governance change. If anyone using or interested in this project, feel free to reply here or in governance change[2]. [1] https://wiki.openstack.org/wiki/QA#Patrole_.28RETIRED.29 [2] https://review.opendev.org/c/openstack/governance/+/880014 -gmann

1 0

[heat] Performance scaling with number of resources
by John Bartelme 13 Apr '23

13 Apr '23

Hello, I'm wondering about heat performance when I scale to a larger number of resources. A single resource deploys quite quickly but when I deploy the below template it takes 2 minutes for this stack to deploy. This occurs on Antelope via DevStack on Ubuntu 22.04 as well as a full production cluster(yoga) deployed with OpenStack-Ansible on RHEL 8. Not only does this template take 2 minutes to deploy it also takes 2 minutes to update without any changes. Is there anything in the stack configuration or heat configuration I can do to speed up the process of updating the stack when very little changes? Or this something inherit in the design of heat? --- heat_template_version: 2021-04-16 description: test resources: test-resources: type: OS::Heat::ResourceGroup properties: count: 100 resource_def: type: OS::Heat::None --- A little more detail: Obviously I have no need to deploy this template but it is a much more simplified case of what I really want to deploy. I'm deploying resource groups that contain hundreds of custom resources(containing network/compute/storage etc.) that are conditionally enabled or disabled based on a JSON property array(in general only about 20 or so resources are deployed but depending on needs any one of the resources might be needed in the near future). The JSON properties array is complex enough that I really want to have it all defined so that changing a boolean value is all that is needed to turn on and off resources without having to fully write new complex heat templates. Additionally the nature of the workflow is that I want to add future resources to the existing stack. I don't change the number of the resources to the resource group, i.e. count=20 instead of 100 because when I conditionally add another resource it causes all the existing resources to be renumbered. Ideally I could rapidly modify one value to the json array and then update the stack and have it quickly modified. Thanks, john

1 0

[manila] Cancelling next week's weekly meeting
by Carlos Silva 13 Apr '23

13 Apr '23

Hello everyone! As we will have a significant drop in attendance in next week's IRC weekly meeting (Apr 20th), we will be cancelling it. The next IRC weekly meeting will be on Apr 27th. Thanks, carloss

1 0

[oslo.messaging][nova][neutron] quorum queues
by Arnaud Morin 13 Apr '23

13 Apr '23

Hey team, I am currently looking into using quorum queues (see patch [1] introduced in oslo_messaging) for openstack services (nova, neutron mostly). After switching the value to true and bootstraping a new cluster, all queues are quorum except the fanout and reply queues. I understand that transient queues are managed differently in openstack, but why is it so? I am asking this because when using rabbit in cluster mode, the quorum queues are replicated accross the cluster. But because the fanout and reply queues are not replicated, if one of the cluster is shutting down during an instance boot, the boot may endup in error (the reply queue may be on the faulty node). Is there any reason to not enable quorum on transient queues? [1] https://github.com/openstack/oslo.messaging/commit/7e8acbf87070354cd2438f3a…

1 0

Updating OS-TRAITS in placement stable/yoga and stable/zed
by Karl Kloppenborg 13 Apr '23

13 Apr '23

Hello Placement and OS-Traits teams. Karl from Openstack-Helm. After debugging a number of issues in Cyborg, it has become necessary to update the pinned OS-TRAITs version in stable/yoga and stable/zed. I have submitted the following two reviews for updating the pinned versions to 2.10.0 https://review.opendev.org/c/openstack/placement/+/880249 https://review.opendev.org/c/openstack/placement/+/880249 By merging these changes, it will allow us to continue to use vGPU capabilities in cyborg in the stable/yoga and stable/zed onwards branches. Kind Regards, -- Karl Kloppenborg, (BCompSc, CNCF-[KCNA, CKA, CKAD], LFCE, CompTIA Linux+ XK0-004) Managing Director, Invention Labs.

3 2

[Cloudkitty][ptg] CloudKitty 2023.2 Bobcat PTG outcome
by Rafael Weingärtner 13 Apr '23

13 Apr '23

Hello, Thanks to everyone who attended the CloudKitty PTG sessions, we covered a lot during the meeting. The Etherpad is available at [1]. [1] https://etherpad.opendev.org/p/march2023-ptg-cloudkitty -- Rafael Weingärtner

1 0

Does cinder-backup support multi-backend?
by wodel youchi 13 Apr '23

13 Apr '23

Hi, Could cinder-backup be configured with multiple-backends, ceph and nfs for example? Regards.

5 9

[kolla-ansible][mariadb] socat: Connection reset by peer
by Satish Patel 12 Apr '23

12 Apr '23

Folks, I am getting the following errors in logs constantly and continually. I have 3 node galera clusters. Everything looks good except this error making me nervous. I have deployed Zed release of kolla openstack. ==> /var/log/kolla/mariadb/mariadb-clustercheck.log <== 2023/04/12 02:42:16 socat[1574755] W read(7, 0x5653c4a4c000, 8192): Connection reset by peer 2023/04/12 02:42:16 socat[1574761] W read(7, 0x5653c4a4c000, 8192): Connection reset by peer 2023/04/12 02:42:16 socat[1574755] W read(6, 0x5653c4a4c000, 8192): Connection reset by peer 2023/04/12 02:42:16 socat[1574761] W read(6, 0x5653c4a4c000, 8192): Connection reset by peer 2023/04/12 02:42:18 socat[1574767] W read(7, 0x5653c4a4c000, 8192): Connection reset by peer 2023/04/12 02:42:18 socat[1574767] W read(6, 0x5653c4a4c000, 8192): Connection reset by peer

2 2

[kolla-ansible][yoga] how to configure cinder to connect to iscsi target?
by wodel youchi 12 Apr '23

12 Apr '23

Hi, I am trying to configure cinder to connect to an iscsi target. I am using targetcli as my target server. I have tested the connection from the node using iscsiadm and it works from the OS. Now I am trying to use the iscsid container to do the job. I added this to my globals.yml enable_iscsid: "yes" enable_cinder_backend_iscsi: "yes" enable_cinder_backend_lvm: "no" And I created the cinder.conf file like this [DEFAULT] enabled_backends = rbd1,nfs-1,*lvmtnas * # add follows to the end [lvmtnas] target_helper = lioadm target_protocol = iscsi target_ip_address = 20.1.0.32 (my target server) volume_backend_name = lvmtnas # volume group name created volume_group = *vg_volume01 * volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver use_chap_auth = false I did create the vg_volume01 on the LUN prior to the test. I did a deploy, the container has been created, but nothing happened, it's like I am missing something. docker logs iscsid fome one the compute nodes + sudo -E kolla_set_configs INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json INFO:__main__:Validating config file INFO:__main__:Kolla config strategy set to: COPY_ALWAYS INFO:__main__:Copying service configuration files INFO:__main__:Writing out command to execute ++ cat /run_command + CMD='iscsid -d 8 -f' + ARGS= + sudo kolla_copy_cacerts + [[ ! -n '' ]] + . kolla_extend_start ++ [[ ! -f /etc/iscsi/initiatorname.iscsi ]] + echo 'Running command: '\''iscsid -d 8 -f'\''' + exec iscsid -d 8 -f Running command: 'iscsid -d 8 -f' iscsid: sysfs_init: sysfs_path='/sys' iscsid: in ctldev_open iscsid: created NETLINK_ISCSI socket... iscsid: InitiatorName=iqn.1994-05.com.redhat:2a318909ad8 iscsid: InitiatorName=iqn.1994-05.com.redhat:2a318909ad8 iscsid: InitiatorAlias=computehci01 iscsid: Max file limits 1048576 1048576 iscsid: current time 258465 iscsid: nothing on pend_list, deactivating alarm Any idea? Regards.

2 4

[neutron] Deprecation of the neutronclient CLI code
by Rodolfo Alonso Hernandez 12 Apr '23

12 Apr '23

Hello all: Since this release [1], the python-neutronclient project will no longer provide CLI support. Any Neutron related CLI command should be executed using python-openstackclient (OSC). This deprecation and removal was announced in [2] and was initially planned for Zed release. We have been working during the last releases to finish the migration and provide all the commands in OSC. In case you find any missing command, argument or output, please open a bug in the Neutron site of launchpad and we'll address it. You can also install a previous (Antelope) version of neutronclient if you missed the migration window. The python-neutronclient will still be available to provide the Networking API python bindings [3]. Regards. [1]https://review.opendev.org/c/openstack/python-neutronclient/+/871711 [2] https://docs.openstack.org/python-neutronclient/latest/contributor/transiti… [3]https://docs.openstack.org/python-neutronclient/ocata/usage/library.html

1 0

CYBORG HTTP400 create trait OWNER_CYBORG
by Karl Kloppenborg 12 Apr '23

12 Apr '23

Hi Cyborg Team, Karl from the Openstack-Helm group. I’ve hit a really an issue I cannot seem to overcome, Cyborg is detecting GPU Profiles from a NVIDIA A40, and it goes to create the record but cyborg-conductor errors with ``` [cyborg-conductor-6fc477ff8b-cw5lf cyborg-conductor] 2023-04-12 06:17:37.581 1 INFO cyborg.conductor.manager [None req-600fcdcf-a620-466a-ba6c-cdfbf6bf83e2 - - - - - -] Failed to add device DriverDevice(controlpath_id=DriverControlPathID,created_at=<?>,deployable_list=[DriverDeployable],model='NVIDIA Corporation Device',std_board_info='{"product_id": "2235", "controller": "3D controller"}',stub=False,type='GPU',updated_at=<?>,vendor='10de',vendor_board_info='{"vendor_info": "gpu_vb_info"}'). Reason: Failed to create trait OWNER_CYBORG: HTTP 400: {"errors": [{"status": 400, "title": "Bad Request", "detail": "The server could not comply with the request since it is either malformed or otherwise incorrect.\n\n The trait is invalid. A valid trait must be no longer than 255 characters, start with the prefix \"CUSTOM_\" and use following characters: \"A\"-\"Z\", \"0\"-\"9\" and \"_\" ", "request_id": "req-24634fad-b312-4ad3-9482-09d6df2b26c2"}]} ``` It appears Cyborg is attempting to create the trait OWNER_CYBORG but I cannot seem to get it to stop that, can I please have some assistance from the Cyborg team to overcome this? Kind Regards, -- Karl Kloppenborg, (BCompSc, CNCF-[KCNA, CKA, CKAD], LFCE, CompTIA Linux+ XK0-004) Managing Director, Invention Labs.

1 0

In Person PTG June 2023 Teams List
by Kendall Nelson 11 Apr '23

11 Apr '23

Hello Everyone! The June 2023 Project Teams List is official! Projects + Teams - OpenInfra Foundation Teams - - Diversity & Inclusion Working Group - Environmental Sustainability Working Group - Kata Containers - StarlingX - OpenStack - - Service Teams - - Cinder - Cyborg - Designate - Heat - Ironic - Keystone - Manila - Neutron - Nova - OpenStack-Ansible - Puppet OpenStack - QA - SDK/CLI/AOC - Tacker - Telemetry - Other OpenStack Teams - - Security SIG - Technical Committee - Scientific SIG If your team was planning to meet and isn’t in this list, please contact ptg(a)openinfra.dev IMMEDIATELY. In a couple weeks, I will be contacting moderators to sign up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — prices go up May 5th! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: https://vancouver2023.openinfra.dev/

1 0

[openstack][sharing][kolla ansible]Problems when 1 of 3 controller was be down
by Nguyễn Hữu Khôi 11 Apr '23

11 Apr '23

Hello everyone. I want to summary for who meets problems with Openstack when deploy cluster with 3 controller using Kolla Ansible Scenario: 1 of 3 controller is down 1. Login horizon and use API such as nova, cinder will be very slow fix by: nano: kolla-ansible/ansible/roles/heat/templates/heat.conf.j2 kolla-ansible/ansible/roles/nova/templates/nova.conf.j2 kolla-ansible/ansible/roles/keystone/templates/keystone.conf.j2 kolla-ansible/ansible/roles/neutron/templates/neutron.conf.j2 kolla-ansible/ansible/roles/cinder/templates/cinder.conf.j2 or which service need caches add as below [cache] backend = oslo_cache.memcache_pool enabled = True memcache_servers = {{ kolla_internal_vip_address }}:{{ memcached_port }} memcache_dead_retry = 0.25 memcache_socket_timeout = 900 https://review.opendev.org/c/openstack/kolla-ansible/+/849487 but it is not the end 2. Cannot launch instance or mapping block device(stuck at this step) nano kolla-ansible/ansible/roles/rabbitmq/templates/definitions.json.j2 "policies":[ {"vhost": "/", "name": "ha-all", "pattern": "^(?!(amq\.)|(.*_fanout_)|(reply_)).*", "apply-to": "all", "definition": {"ha-mode":"all"}, "priority":0}{% if project_name == 'outward_rabbitmq' %}, {"vhost": "{{ murano_agent_rabbitmq_vhost }}", "name": "ha-all", "pattern": ".*", "apply-to": "all", "definition": {"ha-mode":"all"}, "priority":0} {% endif %} ] nano /etc/kollla/global.conf [oslo_messaging_rabbit] kombu_reconnect_delay=0.5 https://bugs.launchpad.net/oslo.messaging/+bug/1993149 https://docs.openstack.org/large-scale/journey/configure/rabbitmq.html I used Xena 13.4 and Yoga 14.8.1. Above bugs are critical, but I see that it was not fixed. I am just an operator and I want to share what I encountered for new people who come to Openstack Nguyen Huu Khoi

6 11

Re: StackOver Flow Error: 2103 ERROR oslo.messaging._drivers.impl_rabbit Connection failed: failed to resolve broker hostname
by Dmitriy Rabotyagov 11 Apr '23

11 Apr '23

If you're going to go prod I would for sure use some deployment tool rather then manual deployment, as further operations and scaling up would be way easier. What error do you get with existing hosts record? вт, 11 апр. 2023 г., 14:57 Trey Fleishman <nfleishman(a)student.ccaeagles.org >: > Hello Dmitriy, > > That is what I thought too, in my host file I define the hostname as the > correct IP address, and if I change the "controller" hostname to some > factitious IP I get a different error. I've tried putting the IP instead of > the hostname, but to no avail. I can successfully ping the hostname from > the machine. I would also rather not use a tool as I plan to go production > once I get my two node setup functional. I am not sure if this might be a > configuration issue, or maybe a bug. > Trey Fleishman > Student and IT Intern > (704) 750 - 1740 > *Calvary Chapel Fort Lauderdale* > 2401 W. Cypress Creek Rd., Ft. Lauderdale, FL 33309 > CalvaryFTL.org > > > On Tue, Apr 11, 2023 at 12:54 AM Dmitriy Rabotyagov < > noonedeadpunk(a)gmail.com> wrote: > >> Hi Trey, >> >> Have you defined a record in your /etc/hosts for "controller", as >> according to the error service simply can not resolve this hostname to an >> IP address. >> >> Also I can suggest trying out one of the following OpenStack deployment >> tools: >> https://docs.openstack.org/zed/deploy/index.html >> >> Most of them have All-In-One guides that can spawn an opestack sandbox to >> play with. >> >> вт, 11 апр. 2023 г., 00:21 Trey Fleishman < >> nfleishman(a)student.ccaeagles.org>: >> >>> Hello all, >>> Recently I tried installing Openstack via this >>> <https://docs.openstack.org/install-guide/openstack-services.html> >>> guide. Upon completion of all the steps including the dashboard step, I was >>> greeted with this error inside the nova_schedular.log file, after I tried >>> creating an instance. >>> >>> 2103 ERROR oslo.messaging._drivers.impl_rabbit Connection failed: failed >>> to resolve broker hostname: OSError: failed to resolve broker hostname >>> >>> When I try to create an instance it hangs in the "scheduling" state and >>> throws this error. I have not configured anything in the "oslo.messaging" >>> section of the Nova config file. I believe that under the [default] section >>> this is what's causing the issue, but the password and hostname are fine. >>> >>> transport_url = >>> rabbit://openstack:BnE9LLfCtjdPvpEnZUnPytSyrfUxE8th@controller >>> >>> Thanks! >>> >>

2 1