September 2023 - openstack-discuss

[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 韩光宇 14 Sep '23

14 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