- openstack-discuss - lists.openstack.org

Virtual hardware Watchdog for Windows VMs
by pi3.14＠tuta.io 19 Sep '23

19 Sep '23

Hello, Is it possible to use virtual hardware watchdog in Windows VMs? I am emulating the "i6300esb" with QEMU in Linux instances and everything works as expected. But when creating Windows instances, this device does not show up in the device manager. - Has anyone tried/tested this before? - Is this supported? - Are additional drivers needed? - I found the following old bug. Has anything changed since then or are there still no suitable drivers? https://bugzilla.redhat.com/show_bug.cgi?id=610063

2 1

Advice on Openstack installer
by Felipe Mogollon 19 Sep '23

19 Sep '23

Hello to everyone, I have some experience in installing Openstack but I am having some weird problems lately. I have installed Openstack Victoria previously using packstack and everything was working fine. Some days ago I tried to deploy a more updated version of Openstack and previous configuration that I was using with packstack is not working. I have tried to deploy a new Openstack with packstack and devstack and none of them were working. I would like to ask you if you kown a running installer because I have run out of ideas about what to do. Regards Felipe -- [image: Vicomtech] <https://www.vicomtech.org> Industry Division Juan Felipe Mogollón Rodríguez Researcher Digital Media fmogollon(a)vicomtech.org +(34) 943 30 92 30 The information contained in this electronic message is intended only for the personal and confidential use of the recipients. If you have received this e-mail by mistake, please, notify us and delete it. Avoid printing this message if it is not strictly necessary.

5 4

[barbican] PTO - Canceling meetings
by Grzegorz Grasza 19 Sep '23

19 Sep '23

Hi all, I'm canceling today's barbican meeting, since I'm still on unscheduled PTO. I also won't be able to attend next week's meeting (September 26). So see y'all next month. In the meantime, if something needs urgent attention, please contact dmendiza or alee. / Greg

1 0

[openstack][skyline]Menu route problem.
by Nguyễn Hữu Khôi 19 Sep '23

19 Sep '23

Hello guys. I am working on Skyline and I followed https://github.com/openstack/skyline-console/blob/master/docs/en/develop/3-… https://github.com/openstack/skyline-console/blob/master/docs/en/develop/3-… I add layouts/menu.jsx ##### { path: '/konitor', name: t('Konitor'), key: /konitor', icon: <DatabaseOutlined />, children: [ { path: '/konitor/konitork', name: t('Konitork'), key: 'konitork', level: 1, } ], } I put my component in pages/konitor/containers/Konitork/index.jsx ####### import React, { Component } from 'react'; import { inject, observer } from 'mobx-react'; export class Konitork extends Component { render() { return ( <div>nhk oi</div> ); } } export default observer(Konitork); Here is my routes/index.js ##### import BaseLayout from '../../../layouts/Basic'; import Konitork from '../containers/Konitork'; import Instance from '../containers/Instance'; const PATH = '/konitor'; export default [ { path: PATH, component: BaseLayout, routes: [ { path: `${PATH}/konitork`, component: Konitork, exact: true }, ], }, ]; When click on Menu. Konitor>>Konitork. It return 404. although I have x.x.x.x:9999/konitor/konitork. Pls correct me. Thank you much. Nguyen Huu Khoi

2 4

[Ceilometer] neither gnocchi nor file publisher receive any data or metric
by Mostafa Salari 19 Sep '23

19 Sep '23

Hi. how can i find a simple, correct, ceilometer configuration for "yoga" version of openstack? 1) I followed this instruction guide <https://docs.openstack.org/ceilometer/latest/install/> step by step! 2) I installed devstack with enabled ceilometer (and gnocchi as backend) but after both tries mentioned above, i did not see any metric. I also changed the publisher from gnocchi:// into file:// but the result did not change. cat /etc/ceilometer/ceilometer.conf: [DEFAULT] transport_url = rabbit://stackrabbit:bsvbr5pzLpN0szN84v3m@127.0.0.1:5672/ use_syslog = True [oslo_messaging_notifications] topics = notifications driver = messagingv2 [coordination] backend_url = redis://localhost:6379 [notification] workers = 4 [cache] backend_argument = url:redis://localhost:6379 backend_argument = distributed_lock:True backend_argument = db:0 backend_argument = redis_expiration_time:600 backend = dogpile.cache.redis enabled = True [service_credentials] auth_url = http://127.0.0.1/identity region_name = RegionOne password = bsvbr5pzLpN0szN84v3m username = ceilometer project_name = service project_domain_id = default user_domain_id = default auth_type = password [keystone_authtoken] memcached_servers = localhost:11211 cafile = /opt/stack/data/ca-bundle.pem project_domain_name = Default project_name = service user_domain_name = Default password = bsvbr5pzLpN0szN84v3m username = ceilometer auth_url = http://127.0.0.1/identity interface = public auth_type = password _________________________________________ cat /etc/ceilometer/pipeline.yaml: --- sources: - name: meter_source meters: - "*" sinks: - meter_sink sinks: - name: meter_sink publishers: - file:///tmp/ceilofile?json # - gnocchi://?archive_policy=low&filter_project=service ____________________________ cat /etc/ceilometer/polling.yaml --- sources: - name: all_pollsters interval: 300 meters: - "*" _____________________________ root@os-aio:/# cat /etc/gnocchi/gnocchi.conf [DEFAULT] debug = True coordination_url = redis://localhost:6379 [indexer] url = mysql+pymysql:// root:bsvbr5pzLpN0szN84v3m@127.0.0.1/gnocchi?charset=utf8 [storage] redis_url = redis://localhost:6379 driver = redis [metricd] metric_processing_delay = 5 [api] auth_mode = keystone [keystone_authtoken] memcached_servers = localhost:11211 cafile = /opt/stack/data/ca-bundle.pem project_domain_name = Default project_name = service user_domain_name = Default password = bsvbr5pzLpN0szN84v3m username = gnocchi auth_url = http://127.0.0.1/identity interface = public auth_type = password

2 1

[manila] - Enforcing CephFS pool data placement via backend config. options deprecated?
by Paul Browne 18 Sep '23

18 Sep '23

Hello to the list, In OpenStack releases prior to Wallaby, in CephFS native driver Manila backend config there existed a configuration directive cephfs_volume_path_prefix <https://docs.openstack.org/manila/wallaby/configuration/shared-file-systems…> ; # DEPRECATED: The prefix of the cephfs volume path. (string value) > # This option is deprecated for removal since Wallaby. > # Its value may be silently ignored in the future. > # Reason: This option is not used starting with the Nautilus release > # of Ceph. > #cephfs_volume_path_prefix = /volumes This volume path prefix was usable (and very useful) to set different prefixes in different backends, pointing to different pools in the same backend Ceph cluster e.g. pools backed by storage devices of different characteristics/technology or Ceph CRUSH rule, etc The pool selection would be done in CephFS via the use of file layout fattributes <https://docs.ceph.com/en/quincy/cephfs/file-layouts/>, file layout inheritance ensuring that data created in sub-directories ends up in the correct Ceph pool. e.g. two backends using the same Ceph cluster but two different path prefixes hitting different Ceph pools [cephfsnative1] > driver_handles_share_servers = False > share_backend_name = CEPHFS1 > share_driver = manila.share.drivers.cephfs.driver.CephFSDriver > cephfs_conf_path = /etc/ceph/ceph.conf > cephfs_auth_id = manila > cephfs_cluster_name = ceph > cephfs_volume_path_prefix = /volumes-staging > cephfs_volume_mode = 777 > cephfs_enable_snapshots = False > [cephfsnative1_ec] > driver_handles_share_servers = False > share_backend_name = CEPHFS1_EC > share_driver = manila.share.drivers.cephfs.driver.CephFSDriver > cephfs_conf_path = /etc/ceph/ceph.conf > cephfs_auth_id = manila > cephfs_cluster_name = ceph > cephfs_volume_path_prefix = /volumes-ec-staging > cephfs_volume_mode = 777 > cephfs_enable_snapshots = False However, since Wallaby this config directive looks to have been deprecated and the default of using a path prefix of only /volumes is possible.Trying to use any other prefix in backend configs is ignored. Would anyone on the list know why this option was deprecated in Manila code, or was this forced on Manila by upstream Ceph as of Nautilus? Is there a way to get back to an equivalent functionality? Currently using only a default path of /volumes means we have lost all flexibility in defining Manila CephFS share data placement using the native CephFS driver. Possibly using share group types+share groups and some pre-created paths in the root CephFS could get to something like equivalency? But these paths would need to correspond to the share group UUID, which will only be known after the share group has been created. So not all that flexible a path, since it requires an interaction between users to communicate the share group ID and Ceph admins to set the correct file layout policy. Putting the path prefix in the backend type removed all of that in a nicely transparent way. Having just prototyped this, it will work for setting a desired file layout on a pre-defined share group UUID path in the root CephFS, though it's not really ideal or sustainable to be able to do this for dynamically created share groups by users or automation... Thanks in advance for any advice, Paul Browne

2 1

[neutron] Bug Deputy Report September 11 - 17
by Miro Tomaska 18 Sep '23

18 Sep '23

Hello All, I was the neutron bug deputy last week (Sept 11-17). Here is what is new: High: -https://bugs.launchpad.net/neutron/+bug/2035325 FDB entries grows indefinitely Assigned: Luis Tomas - https://bugs.launchpad.net/neutron/+bug/2035382 "TestMonitorDaemon._run_monitor" failing radomly, initial message not written Assigned: Miro Tomaska - https://bugs.launchpad.net/neutron/+bug/2035578 [stable branches] devstack-tobiko-neutron job Fails with InvocationError('could not find executable python', None) Unassigned - https://bugs.launchpad.net/neutron/+bug/2036118 VM fails to contact metadata during live-migration Assigned: Jakub Libosvar Medium: - https://bugs.launchpad.net/neutron/+bug/2035168 Remaining db migrations for unmaintained Nuage plugin Unassigned - https://bugs.launchpad.net/neutron/+bug/2035281 [ML2/OVN] DGP/Floating IP issue - no flows for chassis gateway port Assigned: Roberto Bartzen Acosta Undecided: - https://bugs.launchpad.net/neutron/+bug/2035230 Port on creation is returned without the fixed_ips field populated - https://bugs.launchpad.net/neutron/+bug/2035573 Insertion of a duplicated ProviderResourceAssociation entry while creating a HA router Asked for more info - https://bugs.launchpad.net/neutron/+bug/2035332 [OVN] VLAN networks for North / South Traffic Broken Best Regards, -- Miro Tomaska Senior Software Engineer

1 0

[ironic] Mass retirement of old branches due to config errs
by Jay Faulkner 18 Sep '23

18 Sep '23

Hi all, Ironic is one of the major offenders remaining in the work to cleanup Zuul config errors. To resolve these issues, it's my plan to retire any impacted branches unless a contributor volunteers to clean them up. I will give folks until at least September 1, 2023, to object before I begin to take action. These branches have been broken for at least one year, and have gotten no patches or releases in that time. It's clear they have little need to continue existing. Please look at https://zuul.opendev.org/t/openstack/config-errors for the full list of potentially impacted branches; I will list here as best I can: openstack/ironic-prometheus-exporter - bugfix/2.1 - stable/train openstack/networking-generic-switch - stable/pike - stable/train - stable/ussuri - stable/victoria - stable/wallaby - stable/xena openstack/python-ironicclient - stable/train - stable/ussuri - stable/victoria - stable/wallaby - stable/xena - Note: stable/yoga is also in the config errors list, but is considered maintained and cannot be retired at this time. I will work to remove failing jobs and get this zuul config fixed manuallt. As an additional note, the following branches were retired months ago, but due to a bug were recreated. They have been fully deleted (again): openstack/ironic-python-agent - bugfix/8.0 openstack/ironic - bugfix/18.0

3 4

[manila] Manila Bugsquash Sep 19th - Sep 21st
by Carlos Silva 18 Sep '23

18 Sep '23

Hello, Zorillas! As agreed in the previous weekly meeting, our bugsquash will run from September 19th to September 21st. The kick off call will be held on Tuesday, Sep 19th at 14:30 UTC using meetpad [1]. We will use the Manila weekly meeting on Thursday at 15 UTC as a checkpoint. If you plan to work on a bug that is not on the list [2], feel free to add it. Looking forward to seeing you there! [1] https://meetpad.opendev.org/manilabobcatbugsquash [2] https://etherpad.opendev.org/p/6VZ5-sbYiSy0hygRZZ6c Regards, carloss

1 0

[cinder] Map Availability Zone to Volume Type
by Jahns, Jay 18 Sep '23

18 Sep '23

Hi, We have a multi-AZ environment where we launch instances with bootable volumes. When we specify AZ, we need to have a specific volume type in that AZ selected to launch to. Right now, the __DEFAULT__ volume type is used. Normally, that would work, since there is 1 backend in each AZ; however, we need to be able to use the key/value RESKEY:availability_zones to pin a volume type to an AZ, so we can use specific key/values in creating the volume. It is 2 separate backends in the environment. I see this bug: https://bugs.launchpad.net/cinder/+bug/1999706 And this change: https://review.opendev.org/c/openstack/cinder/+/868539 Is there anything we can do to help expedite adding this functionality? It seems that it was supposed to already be in. Thanks, Jay

2 1

[neutron] CI meeting on 18.09.2023 cancelled
by Yatin Karel 18 Sep '23

18 Sep '23

Hello Neutron Team !! I will be out tomorrow for a public holiday, so cancelling the CI meeting. Sorry for the short notice. See You at the next meeting on 25th of September. Thanks and Regards Yatin Karel

1 1

[kolla] [ptg] Kolla 2024.1 (Caracal) PTG planning
by Michał Nasiadka 18 Sep '23

18 Sep '23

Hello All, The 2024.1 (Caracal) virtual PTG is approaching and will be held between 23-27 October, 2023. I’ve created a usual etherpad [1] where you can post your topic proposals and we’ll discuss them For dates - we have been usually meeting on two/three days: There were requests on the Bobcat PTG to make these time slots more Europe friendly (e.g. earlier in the day and not finish at 8pm) and host a slot that is Americas/Asia friendly (if needed) - so I associated each day with a Doodle Poll - let’s try to work out best times for most of us. 1. Kolla/Kolla-Ansible topics day 1 - 4 hours Doodle: https://doodle.com/meeting/participate/id/dyXZN9nb 2. Kolla/Kolla-Ansible topics day 2 - 4 hours (including Kolla Operator Hour) Doodle: https://doodle.com/meeting/participate/id/aO8WxqLb 3. Kayobe topics day - 2 hours Doodle: https://doodle.com/meeting/participate/id/e5LmZExd NOTE: If there are participants interested from other timezones that proposed times in the Doodle poll would not fit - please reply to this email and we’ll work out a dedicated slot. Please add your topics timely so they can be arranged as per your preferences, see you at the PTG! [1] https://etherpad.opendev.org/p/kolla-caracal-ptg Thanks, Michal

1 0

[nova] Live migration of a RAM intensive instance failed
by Rafa 18 Sep '23

18 Sep '23

Hello, I have a volume-backed instance with 16 vCPU and 64GB RAM. The instance uses 60GB RAM out of 64GB (used: 22GB; buff/cache 38GB). When I do a live migration of this instance, it fails without any timeouts. It copies almost all the RAM (within 150 - 250 seconds) to the target compute host without any problems according to the logs. Then the instance is paused to copy the rest of the RAM. Everything seems to be working correctly up to this point, but then the instance resumes and the following error message appears: Live Migration failure: operation failed: migration out job: unexpectedly failed: libvirt.libvirtError: operation failed: migration out job: unexpectedly failed Unfortunately, this error message does not say much. It doesn't look like it's due to any timeouts or short downtimes, but I still tested different (higher) values for the following configurations. Unfortunately without success. - live_migration_completion_timeout - live_migration_timeout_action: abort / force_complete (pause) - live_migration_downtime - live_migration_downtime_steps - live_migration_downtime_delay - live_migration_permit_auto_converge: True / False All other instances on the same source and destination hosts can be live migrated without any issues. This instance can also be successfully live migrated after a restart, as it is probably not yet heavily loaded. After a few hours, however, the live migration no longer works. Any ideas what the problem could be? Logs: - nova-compute.log from source compute host: https://paste.openstack.org/show/bJMFxnPKQBEVaPakud61/ - i found this Traceback using journalctrl: https://paste.openstack.org/show/bIS4GFAd2RJ5fHVN9I8d/ - there was also an error in /var/log/libvirt/qemu/: https://paste.openstack.org/show/bImT89IelDcXXBPSgTCO/ Enviroment: - Libvirt: 8.0.0 - QEMU: 4.2.1 - Nova: 25.1.1 - OpenStack: Yoga - Compute operating system: Ubuntu 20.04

4 7

[release] Release countdown for week R-2, Sep 18-22
by Elõd Illés 15 Sep '23

15 Sep '23

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the 2023.2 Bobcat deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Warning ------- This is a special note to teams about issues regarding oslo.db and castellan deliverables. Please be aware that new releases are about to be sent out. For details, see the mail thread: https://lists.openstack.org/pipermail/openstack-discuss/2023-September/0351… Actions ------- Early in the week, the release team will be proposing stable/2023.2 branch creation for all deliverables that have not branched yet, using the latest available 2023.2 Bobcat release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/2023.2 branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/2023.2 branch before releasing out of the stable/2023.2 branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for 2024.1 Caracal development, though the focus should still be on finishing up 2023.2 Bobcat until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final 2023.2 Bobcat release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the 2023.2 Bobcat version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: September 28th, 2023 (R-1 week) Final 2023.2 Bobcat release: October 4th, 2023 2024.1 Caracal Virtual PTG - October 23-27, 2023

1 0

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 15 Sep '23

15 Sep '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[manila] - Enforcing CephFS pool data placement via backend config. options deprecated?
by Paul Browne 15 Sep '23

15 Sep '23

Hello to the list, In OpenStack releases prior to Wallaby, in CephFS native driver Manila backend config there existed a configuration directive cephfs_volume_path_prefix<https://docs.openstack.org/manila/wallaby/configuration/shared-file-systems…> ; # DEPRECATED: The prefix of the cephfs volume path. (string value) # This option is deprecated for removal since Wallaby. # Its value may be silently ignored in the future. # Reason: This option is not used starting with the Nautilus release # of Ceph. #cephfs_volume_path_prefix = /volumes This volume path prefix was usable (and very useful) to set different prefixes in different backends, pointing to different pools in the same backend Ceph cluster e.g. pools backed by storage devices of different characteristics/technology or Ceph CRUSH rule, etc The pool selection would be done in CephFS via the use of file layout fattributes<https://docs.ceph.com/en/quincy/cephfs/file-layouts/>, file layout inheritance ensuring that data created in prefix child sub-directories ends up in the correct Ceph pool. e.g. two backends using the same Ceph cluster but two different path prefixes hitting different Ceph pools [cephfsnative1] driver_handles_share_servers = False share_backend_name = CEPHFS1 share_driver = manila.share.drivers.cephfs.driver.CephFSDriver cephfs_conf_path = /etc/ceph/ceph.conf cephfs_auth_id = manila cephfs_cluster_name = ceph cephfs_volume_path_prefix = /volumes-staging cephfs_volume_mode = 777 cephfs_enable_snapshots = False [cephfsnative1_ec] driver_handles_share_servers = False share_backend_name = CEPHFS1_EC share_driver = manila.share.drivers.cephfs.driver.CephFSDriver cephfs_conf_path = /etc/ceph/ceph.conf cephfs_auth_id = manila cephfs_cluster_name = ceph cephfs_volume_path_prefix = /volumes-ec-staging cephfs_volume_mode = 777 cephfs_enable_snapshots = False However, since Wallaby this config directive looks to have been deprecated and the default of using a path prefix of only /volumes is possible. Trying to use any other prefix in backend configs is ignored. Would anyone on the list know why this option was deprecated in Manila code, or was this forced on Manila by upstream Ceph as of Nautilus? Is there a way to get back to an equivalent functionality? Currently using only a default path of /volumes means we have lost all flexibility in defining Manila CephFS share data placement using the native CephFS driver. Possibly using share group types+share groups and some pre-created paths in the root CephFS could get to something like equivalency? But these paths would need to correspond to the share group UUID, which will only be known after the share group has been created. So not all that flexible a path, since it requires an interaction between users/tenant to communicate the share group ID and Ceph admins to set the correct file layout policy. Putting the path prefix in the backend+share-type removed all of that in a nicely transparent way. Having just prototyped this, it will work for setting a desired file layout on a pre-defined share group UUID path in the root CephFS, though it's not really ideal or sustainable to be able to do this for dynamically created share groups by users or automation, which could exist in large numbers... Thanks in advance for any advice, Paul Browne ******************* Paul Browne Research Computing Platforms University Information Services Roger Needham Building JJ Thompson Avenue University of Cambridge Cambridge United Kingdom E-Mail: pfb29(a)cam.ac.uk<mailto:pfb29@cam.ac.uk> Tel: 0044-1223-746548 *******************

1 0

[kolla-ansible]change prometheus data volume path
by Satish Patel 15 Sep '23

15 Sep '23

Folks, I have deployed prometheus with koll-ansible and now I want to change the path of prometheus volume to store matrices on bigger partitions. How do I change the volume path of prometheus to store matrix data on separate filesystem? This is what I did in globals.yml but it doesn't work. Is the following variable correct? prometheus_server_default_volumes: "/mnt/prometheus"

3 2

[cinder][kolla-ansible] cinder-volume active/active usage
by 韩光宇 15 Sep '23

15 Sep '23

Hello, I saw that kolla-ansible had allow cinder coordination backend to be configured. And it can be set to "redis" or "etcd" in /etc/kolla/gloabls.yml [1]. Based on my current understanding, this option enables cinder-volume active/active. 1. I would like to ask, between Redis and Etcd, which one is more recommended or what are their pros and cons? 2. And I have saw the spec of cinder-volume a/a[2]. Is it sufficient to configure [coordination]backend_url and [DEFAULT]cluster to use Cinder volume active/active, or are there any other considerations? Could any reference for Cinder volume active/active configuration and usage documentation be recommended ? I would appreciate for any help. Best wishes. Han Guangyu [1] https://github.com/openstack/kolla-ansible/blob/master/etc/kolla/globals.ym… [2] https://specs.openstack.org/openstack/cinder-specs/specs/ocata/ha-aa-job-di…

3 2

[adjutant][barbican][blazar][ec2-api][freezer][masakari][mistral][monasca][murano][sahara][solum][telemetry][vitrage][zun] broken gate on master branch
by Elõd Illés 14 Sep '23

14 Sep '23

Hi $teams_in_subject, I've generated test patches to see gate health (this time for cycle-with-rc deliverables, that have not merged any patches recently) and the patches show [1] that you have broken CI jobs on your gate. Could the teams please check what the issue is / issues are and fix as soon as possible? Thanks in advance! [1] https://review.opendev.org/q/topic:release-health-check-cwr-bobcat+is:open Thanks, Előd Illés irc: elodilles @ #openstack-release

2 1

Octavia - open source scalable load balancer for use in large OpenStack deployments.
by Ajay Kushal 14 Sep '23

14 Sep '23

Hello this is Ajay, final year engineering student from karnataka,India. I have come across this project and feels really interesting and very important for part my course project. Can you please help me in executing this complete project successfully or sharing a demo video of project could be more clear. Please help me in this regards..

2 1

[puppet] Transitioning train, ussuri and victoria to EOL
by Takashi Kajinami 14 Sep '23

14 Sep '23

Hello, As we agreed in the PTG discussions at Vancouver, we'll EOL the old stable branches of Puppet OpenStack projects. As the first step I'll start transitioning stable/train, ussuri and victoria to EOL early next week. Please let me know in case anyone has any concerns about it. Thank you, Takashi

1 1

[cinder] festival of feature reviews on 15th September
by Rajat Dhasmana 14 Sep '23

14 Sep '23

Hello Argonauts, We will be having our monthly festival of reviews tomorrow i.e. 15th September (Friday) from 1400-1600 UTC. Following are some additional details: Date: 15th September, 2023 Time: 1400-1600 UTC Meeting link: https://meet.google.com/jqg-eigw-rku etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews We are planning to prioritize patches for RC2[1]. [1] https://etherpad.opendev.org/p/cinder-bobcat-rc-patches Thanks Rajat Dhasmana

1 0

Re: [openstack][skyline] Some works with skyline
by Nguyễn Hữu Khôi 14 Sep '23

14 Sep '23

Hello. The case is here, https://github.com/openstack/skyline-console/blob/master/src/pages/compute/… but you need to understand how skyline construct page. This project uses nodejs, I use the chart.js library to code. it will need some knowledge about api and javascript. Let's read first. Nguyen Huu Khoi On Wed, Sep 13, 2023 at 7:29 PM Satish Patel <satish.txt(a)gmail.com> wrote: > Sure that is ok. Can you give me a small hit about what you actually > did? I can see you created a new tab 'monitor' but behind that did you > create a new css theme etc to pull metrics from prometheus? > > All I want to do is just to see if it's worth it because we don't have > prometheus but we have different data sources which I can integrate. Thanks > for the work. very appreciated. > > On Wed, Sep 13, 2023 at 7:27 AM Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> > wrote: > >> Hello. Bc i am just working. And I am not dev so I still learn. If it is >> ok then i will do. >> >> On Wed, Sep 13, 2023, 6:17 PM Satish Patel <satish.txt(a)gmail.com> wrote: >> >>> That is great!! >>> >>> I’m not a developer but will try to read the code but it would be good >>> if you just give me file name or clue about where to look. >>> >>> If you have patch or diff would be great. Why don’t you contribute this >>> feature and submit a patch >>> >>> Sent from my iPhone >>> >>> On Sep 12, 2023, at 8:08 PM, Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> >>> wrote: >>> >>> >>> >>> Nguyen Huu Khoi >>> Hello. I just read skyline source code and followed it about data >>> source. This is >>> https://github.com/zhangjianweibj/prometheus-libvirt-exporter. >>> >>>

2 4

[cinder][PTG] Cinder 2024.1 (Caracal) PTG Planning
by Rajat Dhasmana 14 Sep '23

14 Sep '23

Hello All, The 2024.1 (Caracal) virtual PTG is approaching and will be held between 23-27 October, 2023. I've created a planning etherpad[1] and a PTG etherpad[2] to gather topics for the PTG. Note that you only need to add topics in the planning etherpad[1] and those will be arranged in the PTG etherpad[2] later. Date: Tuesday (24th October) to Friday (27th October) 2023 Time: 1300-1700 UTC Etherpad: https://etherpad.opendev.org/p/caracal-ptg-cinder-planning Please add your topics timely so they can be arranged as per your preferences, see you at the PTG! [1] https://etherpad.opendev.org/p/caracal-ptg-cinder-planning [2] https://etherpad.opendev.org/p/caracal-ptg-cinder Thanks Rajat Dhasmana

1 0

[kolla-ansible][ovn] availability zone for OVN
by Satish Patel 13 Sep '23

13 Sep '23

Folks, I am trying to set an availability zone for OVN because skyline UI has a mandatory requirement to have an availability zone otherwise you are not allowed to create a network from skyline GUI. for OVN based deployment only option to set AZ is in ovn-cms-options # ovs-vsctl set open_vswitch . external_ids:ovn-cms-options="enable-chassis-as-gw,availability-zones=az-0" Question: 1. How do I configure in kolla-ansible to override or set ovn-cms-options on only gateway chassis? 2. How does AZ work in OVN because OVN is anyway distributed as per documents, What if I just give foobar AZ name to meet Skyline requirement? Is it going to break anything?

3 3