- openstack-discuss - lists.openstack.org

[tc][releases][ptl][all] 'Unmaintained' branch update
by Brian Rosmaita 15 Nov '23

15 Nov '23

Hello Stackers, I'm sure you saw Elod's email eariler this week [0] calling for final releases from stable/yoga in preparation for its transition to 'Unmaintained' status. In addition to stable/yoga, the TC resolution [1] specified that the three most recent Extended Maintenance branches would also transition to 'Unmaintained', and branches older than that can be deleted. The TC and the release team have had some discussions over the past two weeks [2,3,4,5], and we are closing in on a consensus on how the proposal described in the 2023-07024 resolution should work. This is how it's looking: (1) branches ineligible for Unmaintained status These are stable/ussuri and stable/train. The release team will use the current tooling to generate the patches proposing the ussuri-eol and train-eol tags; teams will have a grace period to get any final changes merged; after the -eol tags are made, the branches will be deleted. (2) transitioning a branch out of Maintained status This is stable/yoga. Elod has already sent the reminder email [0] for project teams to propose a release patch if there's a reason to do a final release. The release team is working on tooling that will mark the HEAD of stable/yoga with yoga-eom (for "end of maintenance"), delete the stable/yoga branch, and then cut the unmaintained/yoga branch based on the yoga-eom tag. There will be a grace period for the community to decide whether the branch should be kept in Unmaintained status or deleted, as described in [1]. Eventually (either when the grace period expires, or later, when there is no longer interest in keeping unmaintained/yoga around), the HEAD will be tagged yoga-eol and the branch deleted. (3) transitioning current eligible Extended Maintenance branches to Unmaintained status These are stable/xena, stable/wallaby, and stable/victoria. Ericsson has expressed interest in keeping victoria in Unmaintained status. Subject to the guidelines in [1], wallaby, xena, and yoga will therefore be kept in Unmaintained status as well. Eventually, consistent with [1], these branches will be tagged $series-eol and deleted. For more details about (1)-(3) above, see the discussion in [6]. The current patch to the Project Team Guide [7] will be updated shortly to reflect the discussion in [6]. (4) amendment to the Unmaintained branch resolution The original plan in [1] was for there to be a $project-unmaintained-core Gerrit group for each OpenStack project that would have +2/+W powers on the unmaintained/$series branches. This would entail changes in the Gerrit ACL config files for all projects plus populating all the Gerrit groups. I've put up an amendment [8] to the resolution that would instead establish a single openstack-unmaintained-core Gerrit group that would have +2/+W powers over all the unmaintained/* branches in the openstack namespace. Projects that would prefer to stick with the original proposal and have tighter control over their unmaintained/* branches can still do so; they'll have to patch the appropriate Gerrit ACL config file(s) for their project and populate the $project-unmaintained-core group. Note that except for the Amendment mentioned in (4), this email only provides details about how [1] is to be implemented; it does not change the nature of the Unmaintained branch proposal that was adopted by the TC back in July 2023. If you have questions or comments, please reply to the openstack-discuss mailing list, or leave comments on [7] and [8]. [0] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branc… [2] https://meetings.opendev.org/meetings/tc/2023/tc.2023-10-31-18.00.log.html#… [3] https://meetings.opendev.org/meetings/tc/2023/tc.2023-11-07-18.00.log.html#… video meeting recording: https://www.youtube.com/watch?v=qv6nSRhfV_M [4] https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-11-… [5] https://meetings.opendev.org/meetings/tc/2023/tc.2023-11-14-18.00.log.html#… [6] https://etherpad.opendev.org/p/early-caracal-unmaintained-transition [7] https://review.opendev.org/c/openstack/project-team-guide/+/897505 [8] https://review.opendev.org/c/openstack/governance/+/900940

1 0

Discuss i18n IRC Meeting date
by Seongsoo Cho 15 Nov '23

15 Nov '23

Hi i18n Team. It's time to update our regular meeting date. This is the current meeting date in the doc, but actually, there are no meeting. [1] Every odd week: 16:00 UTC, Thursday Every even week: 07:00 UTC, Thursday So I want to set a new meeting date. For now, I'd like to have a monthly IRC meeting. Please let me know what days and times work best for you. Survey form: https://forms.gle/SZUFmwJS6QTs4akNA Best Regards Seongsoo [1] https://docs.openstack.org/i18n/latest/i18n_team_meeting.html -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

1 0

[ptls][PTG] OpenInfra Live: PTG Recap
by Kristin Barrientos 15 Nov '23

15 Nov '23

Hi Everyone, I wanted to reach out to see if any PTLs were interested in providing their highlights from last month’s PTG in an OpenInfra Live[1] episode on Thursday, December 7 at 1500 UTC. Ideally, we would like to have 4-6 projects represented (OpenStack, Kata, and/or StarlingX). A previous example of a PTG recap episode can be found here[2]. Please let me know if you’re interested and I can provide the next steps. If you would like to provide an update but that time doesn’t work for you, please share a recording with me and I can get it added. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation [1] openinfra.dev/live [2] https://www.youtube.com/watch?v=yIt4dJvTQVg&t=231s

7 11

[swift]: Swiftstack Zone/DC decommission
by Muralikrishna Gutha 15 Nov '23

15 Nov '23

Hello Team, We currently utilize SwiftStack Object Storage to meet our object storage requirements, and our cluster has a Primary Zone/Secondary Zone topology. Recently, we attempted to remove/disable the Secondary Zone. However, upon doing so, we observed a concerning trend: the storage utilization in the Primary Zone rapidly increased, reaching approximately 90%. This surge was particularly notable due to the use of the 'tworeplicaperregion' policy. In an attempt to address this, we brought the Secondary Zone nodes back online, expecting Swift to redistribute the data back to these nodes and alleviate the storage strain on the Primary Zone. Despite reintegrating the Secondary Zone nodes into the cluster, we continue to witness a persistent rise in storage utilization within the Primary Zone. Interestingly, two out of the three nodes in the Primary Zone seem to bear the brunt of the data and tokens, while the third node is not receiving a proportional distribution of data. At this juncture, we are seeking guidance on potential configurations or adjustments, such as specific knobs, that could expedite the rebalance process. Our objective is to efficiently distribute the data across nodes, particularly in the Primary Zone, and optimize the overall storage utilization in our SwiftStack Object Storage cluster. Any insights or recommendations on tuning parameters for a swifter rebalance would be highly appreciated. Thanks, Murali -- This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this on behalf of the addressee you must not use, copy, disclose or take action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply email and delete this message. Thank you.

3 7

[tc] Next TC Meeting will be Nov 28 (2023-11-21 meeting cancelled)
by Jay Faulkner 14 Nov '23

14 Nov '23

Hi all, The Technical Committee will not be meeting next week. The meeting was cancelled due to American Thanksgiving. Our next meeting will be November 28, 2023. Thanks, Jay Faulkner OpenStack TC Chair

1 0

Implementation review day will be Nov 15
by Sylvain Bauza 14 Nov '23

14 Nov '23

Hey folks, We just agreed during today's meeting on having our first implementation review day this week. In order to make this day efficient, I proposed an etherpad for tracking our efforts https://etherpad.opendev.org/p/nova-caracal-status Shall you want the nova community to look at your changes, you should please add them into the etherpad in the very last section ('proposed bugfixes') and then me and a few other cores will curate that list. Tomorrow, we'll scrub the list of approved blueprints's patches and the bugfixes' ones that got approved as a review priority and we'll iterate over them. Please try to look at your Gerrit emails, you could get comments ;-) Thanks, -Sylvain

1 1

the volume cannot be deleted, it is in deleting state
by kjme001＠gmail.com 14 Nov '23

14 Nov '23

hello, I'm having trouble deleting volumes in OpenStackl from a machine that no longer exists. How to execute cinder command reset-state --attach-status detached volume_name then I execute the command: # cinder delete volume_name Delete for volume cifar-10-copy failed: Invalid volume: Volume status must be available or error or error_restoring or error_extending or error_managing and must not be migrating, attached, belong to a group, have snapshots or be disassociated from snapshots after volume transfer. (HTTP 400) (Request-ID: req-b2d3f2e4-7855-4831-a68d-f6710cc97e94) ERROR: Unable to delete any of the specified volumes. then executes the command: cinder reset-state --state available volume_name and cinder delete volume_name Request to delete volume volume_name has been accepted. when I check: openstack volume show volume_name is: | status | deleting The volume is not being deleted, it is in the deleting state. This is a volume from a non-existent node, but the volume is still visible in OpenStack and cannot be deleted because it is in the deleting state. Maybe someone can tell me how to remove such a volume? Regards

1 0

cinder-manage service remove cinder-volume xxxx@lvm-ssd - error
by kjme001＠gmail.com 14 Nov '23

14 Nov '23

cinder-manage service remove cinder-volume xxxx@lvm-ssd /usr/lib/python3/dist-packages/cinder/db/sqlalchemy/models.py:152: SAWarning: implicitly coercing SELECT object to scalar subquery; please use the .scalar_subquery() method to produce a scalar subquery. last_heartbeat = column_property( /usr/lib/python3/dist-packages/cinder/db/sqlalchemy/models.py:160: SAWarning: implicitly coercing SELECT object to scalar subquery; please use the .scalar_subquery() method to produce a scalar subquery. num_hosts = column_property( /usr/lib/python3/dist-packages/cinder/db/sqlalchemy/models.py:169: SAWarning: implicitly coercing SELECT object to scalar subquery; please use the .scalar_subquery() method to produce a scalar subquery. num_down_hosts = column_property( 2023-11-11 14:34:00.928 898920 CRITICAL cinder [req-525973bb-e026-4999-95af-d852aa137066 - - - - -] Unhandled error: oslo_db.exception.DBNonExistentDatabase: (sqlite3.OperationalError) unable to open database file (Background on this error at: https://sqlalche.me/e/14/e3q8) 2023-11-11 14:34:00.928 898920 ERROR cinder Traceback (most recent call last): 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 3250, in _wrap_pool_connect 2023-11-11 14:34:00.928 898920 ERROR cinder return fn() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 310, in connect 2023-11-11 14:34:00.928 898920 ERROR cinder return _ConnectionFairy._checkout(self) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 868, in _checkout 2023-11-11 14:34:00.928 898920 ERROR cinder fairy = _ConnectionRecord.checkout(pool) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 476, in checkout 2023-11-11 14:34:00.928 898920 ERROR cinder rec = pool._do_get() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/impl.py", line 256, in _do_get 2023-11-11 14:34:00.928 898920 ERROR cinder return self._create_connection() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 256, in _create_connection 2023-11-11 14:34:00.928 898920 ERROR cinder return _ConnectionRecord(self) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 371, in __init__ 2023-11-11 14:34:00.928 898920 ERROR cinder self.__connect() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 665, in __connect 2023-11-11 14:34:00.928 898920 ERROR cinder with util.safe_reraise(): 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ 2023-11-11 14:34:00.928 898920 ERROR cinder compat.raise_( 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 207, in raise_ 2023-11-11 14:34:00.928 898920 ERROR cinder raise exception 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 661, in __connect 2023-11-11 14:34:00.928 898920 ERROR cinder self.dbapi_connection = connection = pool._invoke_creator(self) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/engine/create.py", line 590, in connect 2023-11-11 14:34:00.928 898920 ERROR cinder return dialect.connect(*cargs, **cparams) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 597, in connect 2023-11-11 14:34:00.928 898920 ERROR cinder return self.dbapi.connect(*cargs, **cparams) 2023-11-11 14:34:00.928 898920 ERROR cinder sqlite3.OperationalError: unable to open database file 2023-11-11 14:34:00.928 898920 ERROR cinder 2023-11-11 14:34:00.928 898920 ERROR cinder The above exception was the direct cause of the following exception: 2023-11-11 14:34:00.928 898920 ERROR cinder 2023-11-11 14:34:00.928 898920 ERROR cinder Traceback (most recent call last): 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/bin/cinder-manage", line 10, in <module> 2023-11-11 14:34:00.928 898920 ERROR cinder sys.exit(main()) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/cinder/cmd/manage.py", line 1069, in main 2023-11-11 14:34:00.928 898920 ERROR cinder fn(**fn_kwargs) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/cinder/cmd/manage.py", line 711, in remove 2023-11-11 14:34:00.928 898920 ERROR cinder svc = objects.Service.get_by_args(ctxt, host_name, binary) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/cinder/objects/service.py", line 133, in get_by_args 2023-11-11 14:34:00.928 898920 ERROR cinder db_service = db.service_get(context, host=host, binary=binary_key) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/cinder/db/api.py", line 270, in service_get 2023-11-11 14:34:00.928 898920 ERROR cinder return IMPL.service_get(context, service_id, backend_match_level, 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/cinder/db/sqlalchemy/api.py", line 168, in wrapper 2023-11-11 14:34:00.928 898920 ERROR cinder return f(*args, **kwargs) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/cinder/db/sqlalchemy/api.py", line 745, in service_get 2023-11-11 14:34:00.928 898920 ERROR cinder query = _service_query(context, backend_match_level=backend_match_level, 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/cinder/db/sqlalchemy/api.py", line 686, in _service_query 2023-11-11 14:34:00.928 898920 ERROR cinder query = model_query(context, models.Service, session=session, 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/cinder/db/sqlalchemy/api.py", line 259, in model_query 2023-11-11 14:34:00.928 898920 ERROR cinder session = kwargs.get('session') or get_session() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/cinder/db/sqlalchemy/api.py", line 95, in get_session 2023-11-11 14:34:00.928 898920 ERROR cinder return main_context_manager._factory.get_legacy_facade().get_session( 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 357, in get_legacy_facade 2023-11-11 14:34:00.928 898920 ERROR cinder self._start() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 504, in _start 2023-11-11 14:34:00.928 898920 ERROR cinder self._setup_for_connection( 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 529, in _setup_for_connection 2023-11-11 14:34:00.928 898920 ERROR cinder engine = engines.create_engine( 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/debtcollector/renames.py", line 43, in decorator 2023-11-11 14:34:00.928 898920 ERROR cinder return wrapped(*args, **kwargs) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/oslo_db/sqlalchemy/engines.py", line 211, in create_engine 2023-11-11 14:34:00.928 898920 ERROR cinder test_conn = _test_connection(engine, max_retries, retry_interval) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/oslo_db/sqlalchemy/engines.py", line 386, in _test_connection 2023-11-11 14:34:00.928 898920 ERROR cinder return engine.connect() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 3204, in connect 2023-11-11 14:34:00.928 898920 ERROR cinder return self._connection_cls(self, close_with_result=close_with_result) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 96, in __init__ 2023-11-11 14:34:00.928 898920 ERROR cinder else engine.raw_connection() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 3283, in raw_connection 2023-11-11 14:34:00.928 898920 ERROR cinder return self._wrap_pool_connect(self.pool.connect, _connection) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 3253, in _wrap_pool_connect 2023-11-11 14:34:00.928 898920 ERROR cinder Connection._handle_dbapi_exception_noconnection( 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 2098, in _handle_dbapi_exception_noconnection 2023-11-11 14:34:00.928 898920 ERROR cinder util.raise_(newraise, with_traceback=exc_info[2], from_=e) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 207, in raise_ 2023-11-11 14:34:00.928 898920 ERROR cinder raise exception 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 3250, in _wrap_pool_connect 2023-11-11 14:34:00.928 898920 ERROR cinder return fn() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 310, in connect 2023-11-11 14:34:00.928 898920 ERROR cinder return _ConnectionFairy._checkout(self) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 868, in _checkout 2023-11-11 14:34:00.928 898920 ERROR cinder fairy = _ConnectionRecord.checkout(pool) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 476, in checkout 2023-11-11 14:34:00.928 898920 ERROR cinder rec = pool._do_get() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/impl.py", line 256, in _do_get 2023-11-11 14:34:00.928 898920 ERROR cinder return self._create_connection() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 256, in _create_connection 2023-11-11 14:34:00.928 898920 ERROR cinder return _ConnectionRecord(self) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 371, in __init__ 2023-11-11 14:34:00.928 898920 ERROR cinder self.__connect() 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 665, in __connect 2023-11-11 14:34:00.928 898920 ERROR cinder with util.safe_reraise(): 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ 2023-11-11 14:34:00.928 898920 ERROR cinder compat.raise_( 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 207, in raise_ 2023-11-11 14:34:00.928 898920 ERROR cinder raise exception 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 661, in __connect 2023-11-11 14:34:00.928 898920 ERROR cinder self.dbapi_connection = connection = pool._invoke_creator(self) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/engine/create.py", line 590, in connect 2023-11-11 14:34:00.928 898920 ERROR cinder return dialect.connect(*cargs, **cparams) 2023-11-11 14:34:00.928 898920 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 597, in connect 2023-11-11 14:34:00.928 898920 ERROR cinder return self.dbapi.connect(*cargs, **cparams) 2023-11-11 14:34:00.928 898920 ERROR cinder oslo_db.exception.DBNonExistentDatabase: (sqlite3.OperationalError) unable to open database file 2023-11-11 14:34:00.928 898920 ERROR cinder (Background on this error at: https://sqlalche.me/e/14/e3q8) 2023-11-11 14:34:00.928 898920 ERROR cinder

3 4

(no subject)
by mgutha＠liveperson.com 14 Nov '23

14 Nov '23

I have observed an imbalance in the cluster based on the object.builder output. Is this possibly due to an ongoing rebalance process? Additionally, I'd like to confirm my understanding of 'min_part_hours.' Is it accurate to say that this parameter represents the number of hours an object needs to reside on a disk before it's considered for movement to another device during a rebalance? According to the Swift documentation, the default value is 24 hours. I'm curious if this value is applied to data written specifically by the rebalance process or if it also includes data written by other Swift services. object.builder, build version 775, id 61b2166cb8684b2b80d6fc370cef37a6 65536 partitions, 2.000000 replicas, 2 regions, 2 zones, 95 devices, 38.89 balance, 0.00 dispersion The minimum number of hours before a partition can be reassigned is 0 (0:00:00 remaining) The overload factor is 10.00% (0.100000) Ring file object.ring.gz not found, probably it hasn't been written yet Devices: id region zone ip address:port replication ip:port name weight partitions balance flags meta 129 1 1 182.16.128.36:6000 182.16.128.36:6003 d129 1.00 2 38.89 130 1 1 182.16.128.36:6006 182.16.128.36:6003 d130 1.00 2 38.89 131 1 1 182.16.128.36:6007 182.16.128.36:6003 d131 1.00 2 38.89 132 1 1 182.16.128.36:6008 182.16.128.36:6003 d132 1.00 2 38.89 133 1 1 182.16.128.36:6009 182.16.128.36:6003 d133 1.00 2 38.89 134 1 1 182.16.128.36:6010 182.16.128.36:6003 d134 1.00 1 -30.56 135 1 1 182.16.128.36:6011 182.16.128.36:6003 d135 1.00 1 -30.56 136 1 1 182.16.128.36:6012 182.16.128.36:6003 d136 1.00 1 -30.56 137 1 1 182.16.128.36:6013 182.16.128.36:6003 d137 1.00 1 -30.56 138 1 1 182.16.128.36:6014 182.16.128.36:6003 d138 1.00 1 -30.56 139 1 1 182.16.128.36:6015 182.16.128.36:6003 d139 1.00 1 -30.56 140 1 1 182.16.128.38:6000 182.16.128.38:6003 d140 1.00 2 38.89 141 1 1 182.16.128.38:6006 182.16.128.38:6003 d141 1.00 2 38.89 142 1 1 182.16.128.38:6007 182.16.128.38:6003 d142 1.00 2 38.89 143 1 1 182.16.128.38:6008 182.16.128.38:6003 d143 1.00 2 38.89 144 1 1 182.16.128.38:6009 182.16.128.38:6003 d144 1.00 2 38.89 145 1 1 182.16.128.38:6010 182.16.128.38:6003 d145 1.00 1 -30.56 146 1 1 182.16.128.38:6011 182.16.128.38:6003 d146 1.00 1 -30.56 147 1 1 182.16.128.38:6012 182.16.128.38:6003 d147 1.00 1 -30.56 148 1 1 182.16.128.38:6013 182.16.128.38:6003 d148 1.00 1 -30.56 149 1 1 182.16.128.38:6014 182.16.128.38:6003 d149 1.00 1 -30.56 150 1 1 182.16.128.38:6015 182.16.128.38:6003 d150 1.00 1 -30.56 151 1 1 182.16.128.39:6000 182.16.128.39:6003 d151 1.00 2 38.89 152 1 1 182.16.128.39:6006 182.16.128.39:6003 d152 1.00 2 38.89 153 1 1 182.16.128.39:6007 182.16.128.39:6003 d153 1.00 2 38.89 154 1 1 182.16.128.39:6008 182.16.128.39:6003 d154 1.00 2 38.89 155 1 1 182.16.128.39:6009 182.16.128.39:6003 d155 1.00 2 38.89 156 1 1 182.16.128.39:6010 182.16.128.39:6003 d156 1.00 1 -30.56 157 1 1 182.16.128.39:6011 182.16.128.39:6003 d157 1.00 1 -30.56 158 1 1 182.16.128.39:6012 182.16.128.39:6003 d158 1.00 1 -30.56 159 1 1 182.16.128.39:6013 182.16.128.39:6003 d159 1.00 1 -30.56 160 1 1 182.16.128.39:6014 182.16.128.39:6003 d160 1.00 1 -30.56 161 1 1 182.16.128.39:6015 182.16.128.39:6003 d161 1.00 1 -30.56 55 1 1 182.16.128.5:6000 182.16.128.5:6003 d55 2000.40 2789 -3.18 56 1 1 182.16.128.5:6006 182.16.128.5:6003 d56 2000.40 2789 -3.18 57 1 1 182.16.128.5:6007 182.16.128.5:6003 d57 2000.40 2789 -3.18 58 1 1 182.16.128.5:6008 182.16.128.5:6003 d58 2000.40 2789 -3.18 59 1 1 182.16.128.5:6009 182.16.128.5:6003 d59 2000.40 2789 -3.18 60 1 1 182.16.128.5:6010 182.16.128.5:6003 d60 2000.40 2789 -3.18 61 1 1 182.16.128.5:6011 182.16.128.5:6003 d61 2000.40 2789 -3.18 62 1 1 182.16.128.5:6012 182.16.128.5:6003 d62 2000.40 2789 -3.18 63 1 1 182.16.128.5:6013 182.16.128.5:6003 d63 2000.40 2789 -3.18 64 1 1 182.16.128.5:6014 182.16.128.5:6003 d64 2000.40 2789 -3.18 65 1 1 182.16.128.5:6015 182.16.128.5:6003 d65 2000.40 2788 -3.21 44 1 1 182.16.128.6:6000 182.16.128.6:6003 d44 269.43 376 -3.09 45 1 1 182.16.128.6:6006 182.16.128.6:6003 d45 269.43 376 -3.09 46 1 1 182.16.128.6:6007 182.16.128.6:6003 d46 269.43 376 -3.09 47 1 1 182.16.128.6:6008 182.16.128.6:6003 d47 269.43 376 -3.09 48 1 1 182.16.128.6:6009 182.16.128.6:6003 d48 269.43 376 -3.09 49 1 1 182.16.128.6:6010 182.16.128.6:6003 d49 269.43 376 -3.09 50 1 1 182.16.128.6:6011 182.16.128.6:6003 d50 269.43 376 -3.09 51 1 1 182.16.128.6:6012 182.16.128.6:6003 d51 269.43 375 -3.35 52 1 1 182.16.128.6:6013 182.16.128.6:6003 d52 269.43 375 -3.35 53 1 1 182.16.128.6:6014 182.16.128.6:6003 d53 269.43 375 -3.35 54 1 1 182.16.128.6:6015 182.16.128.6:6003 d54 269.43 375 -3.35 0 1 1 182.16.128.7:6000 182.16.128.7:6003 d0 2000.40 2789 -3.18 1 1 1 182.16.128.7:6006 182.16.128.7:6003 d1 2000.40 2789 -3.18 10 1 1 182.16.128.7:6015 182.16.128.7:6003 d10 2000.40 2788 -3.21 2 1 1 182.16.128.7:6007 182.16.128.7:6003 d2 2000.40 2789 -3.18 3 1 1 182.16.128.7:6008 182.16.128.7:6003 d3 2000.40 2789 -3.18 4 1 1 182.16.128.7:6009 182.16.128.7:6003 d4 2000.40 2789 -3.18 5 1 1 182.16.128.7:6010 182.16.128.7:6003 d5 2000.40 2789 -3.18 6 1 1 182.16.128.7:6011 182.16.128.7:6003 d6 2000.40 2789 -3.18 7 1 1 182.16.128.7:6012 182.16.128.7:6003 d7 2000.40 2789 -3.18 8 1 1 182.16.128.7:6013 182.16.128.7:6003 d8 2000.40 2789 -3.18 9 1 1 182.16.128.7:6014 182.16.128.7:6003 d9 2000.40 2789 -3.18 11 2 2 11.17.128.5:6000 11.17.128.5:6003 d11 2000.40 2979 3.42 12 2 2 11.17.128.5:6006 11.17.128.5:6003 d12 2000.40 2979 3.42 13 2 2 11.17.128.5:6007 11.17.128.5:6003 d13 2000.40 2979 3.42 15 2 2 11.17.128.5:6008 11.17.128.5:6003 d15 2000.40 2979 3.42 16 2 2 11.17.128.5:6009 11.17.128.5:6003 d16 2000.40 2979 3.42 17 2 2 11.17.128.5:6010 11.17.128.5:6003 d17 2000.40 2978 3.38 18 2 2 11.17.128.5:6011 11.17.128.5:6003 d18 2000.40 2978 3.38 19 2 2 11.17.128.5:6012 11.17.128.5:6003 d19 2000.40 2978 3.38 20 2 2 11.17.128.5:6013 11.17.128.5:6003 d20 2000.40 2978 3.38 21 2 2 11.17.128.5:6014 11.17.128.5:6003 d21 2000.40 2978 3.38 77 2 2 11.17.128.5:6015 11.17.128.5:6003 d77 2000.40 2978 3.38 33 2 2 11.17.128.6:6000 11.17.128.6:6003 d33 2000.40 2979 3.42 34 2 2 11.17.128.6:6006 11.17.128.6:6003 d34 2000.40 2979 3.42 35 2 2 11.17.128.6:6007 11.17.128.6:6003 d35 2000.40 2979 3.42 36 2 2 11.17.128.6:6008 11.17.128.6:6003 d36 2000.40 2979 3.42 37 2 2 11.17.128.6:6009 11.17.128.6:6003 d37 2000.40 2978 3.38 38 2 2 11.17.128.6:6010 11.17.128.6:6003 d38 2000.40 2978 3.38 39 2 2 11.17.128.6:6011 11.17.128.6:6003 d39 2000.40 2978 3.38 40 2 2 11.17.128.6:6012 11.17.128.6:6003 d40 2000.40 2978 3.38 41 2 2 11.17.128.6:6013 11.17.128.6:6003 d41 2000.40 2978 3.38 42 2 2 11.17.128.6:6014 11.17.128.6:6003 d42 2000.40 2978 3.38 43 2 2 11.17.128.6:6015 11.17.128.6:6003 d43 2000.40 2978 3.38 162 2 2 11.17.128.71:6000 11.17.128.71:6003 d162 1.00 2 38.89 163 2 2 11.17.128.71:6006 11.17.128.71:6003 d163 1.00 2 38.89 164 2 2 11.17.128.71:6007 11.17.128.71:6003 d164 1.00 2 38.89 165 2 2 11.17.128.71:6008 11.17.128.71:6003 d165 1.00 2 38.89 166 2 2 11.17.128.71:6009 11.17.128.71:6003 d166 1.00 1 -30.56 167 2 2 11.17.128.71:6010 11.17.128.71:6003 d167 1.00 1 -30.56 168 2 2 11.17.128.71:6011 11.17.128.71:6003 d168 1.00 1 -30.56

3 2

Re: [swift]: Swiftstack Zone/DC decommission
by Muralikrishna Gutha 13 Nov '23

13 Nov '23

Clary, Thanks for the update I was unable to locate the object.builder file in the instance where we are running swiftstack. We are currently on Swift Package Version: 2.24.0.3-1.el7 [root@hostname swift]# /opt/ss/bin/swift-ring-builder object.builder | head Ring Builder file does not exist: object.builder [root@hostname swift]# locate object.builder [root@hostname swift]#pwd /etc/swift Thanks, Murali -- This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this on behalf of the addressee you must not use, copy, disclose or take action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply email and delete this message. Thank you.

2 1