January 2024 - openstack-discuss - lists.openstack.org

Re:
by Rohit Sansiya 08 Jan '24

08 Jan '24

Please answer On Sat, 6 Jan, 2024, 13:47 Rohit Sansiya, <rsansiya(a)gmail.com> wrote: > i hvnt heard about ...how the openstack is getting the dhcp ip without > registration of mac address ? > > > Your message is ready to be sent with the following file or link > attachments: > Rohit Sansiya > https://sites.google.com/view/rpgcloud/research-india > > Note: To protect against computer viruses, e-mail programs may prevent > sending or receiving certain types of file attachments. Check your e-mail > security settings to determine how attachments are handled. >

1 0

[nova] patch delete dangling bdms lead to VM Error
by Sang Tran Quoc 08 Jan '24

08 Jan '24

Hi community, I've got the error with this patch while rebooting VM with volume source from the image, the result VM state is Error with the message "VolumeDeviceNotFound" (Tested with Netapp & PowerStrore iSCSI SAN driver) Please take a look at this! https://review.opendev.org/c/openstack/nova/+/882284

2 2

[kolla] help installing skyline UI
by garcetto 07 Jan '24

07 Jan '24

good evening, i dont find where i can enable the skyline ui frontend could have an help? thank you

3 3

Re: New OpenStack machine on new node not responding
by 韩光宇 07 Jan '24

07 Jan '24

Hi Do you configure security group? The default security group provided by OpenStack denies any incoming traffic. ----------Reply to Message---------- On Tue, Jan 2, 2024 21:54 PM kjme001<kjme001(a)gmail.com> wrote: hello, I added a new node to OpeStack. I can create a new instance on it. The instance creates itself without error, its IP address is assigned. But however, the connection over ssh to this new machine does not work for me, nor does ping. I have the network traffic passed, what else can I check why the new machine is not responding to me network-wise regards

2 1

[ironic][glance] tradeoffs between ceph and swift glance backends for ironic+kvm?
by Michael Sherman 06 Jan '24

06 Jan '24

Hey! We’re looking into deploying a cloud with a mix of VM and baremetal hosts (nova-compute vs ironic), and discovered some tension between the recommendations for glance for each case. At scale, ironic seems to recommend usage of the swift backend to remove the conductor as a bottleneck when streaming disk images, but for KVM usage, the RBD backend allows for faster launches by cloning the source image. Any thoughts on these or any other tradeoffs, or some recommended configurations? Thanks! -Mike -- Michael Sherman Infrastructure Lead – Chameleon Computer Science, University of Chicago MCS, Argonne National Lab

3 2

reset-state instances with Api in openstack
by Parsa Aminian 06 Jan '24

06 Jan '24

hello Is there any Api for reset-state instance status to active or error on openstack api ?

5 5

[release] Release countdown for week R-12
by Thierry Carrez 05 Jan '24

05 Jan '24

Development Focus ----------------- The Caracal-2 milestone is next week, on January 11th, 2024! 2024.1 Caracal-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/caracal/schedule.html for details. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library that has not been otherwise released since milestone 1. PTL's and release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well. A +1 would be appreciated, but if we do not hear anything at all by the end of the week, we will assume things are OK to proceed. Remember that non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. Next week is also the deadline to freeze the contents of the final release. All new 2024.1 Caracal deliverables need to have a deliverable file in https://opendev.org/openstack/releases/src/branch/master/deliverables and need to have done a release by milestone-2. Changes proposing those deliverables for inclusion in 2024.1 Caracal have been posted, please update them with an actual release request before the milestone-2 deadline if you plan on including that deliverable in 2024.1 Caracal, or -1 if you need one more cycle to be ready. Upcoming Deadlines & Dates -------------------------- Caracal-2 Milestone: January 11th, 2024 -- Thierry Carrez (ttx)

1 0

[neutron] Neutron drivers meeting
by Rodolfo Alonso Hernandez 05 Jan '24

05 Jan '24

Hello Neutrinos: Due to the lack of quorum, I've cancelled the meeting 5 minutes after starting it. We'll retake the pending issues next week. Regards.

1 0

tox -e pep8 error
by Alex Song (宋文平) 05 Jan '24

05 Jan '24

Folks, my env run 'tox -e pep8' error with the info below, any body can help? Thanks. /opt/stack/nova/.tox/pep8/lib/python3.8/site-packages/setuptools/__init__.py :80: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! **************************************************************************** **** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. **************************************************************************** **** !! dist.fetch_build_eggs(dist.setup_requires) /opt/stack/nova/.tox/pep8/lib/python3.8/site-packages/setuptools/command/dev elop.py:39: EasyInstallDeprecationWarning: easy_install command is deprecated. !! **************************************************************************** **** Please avoid running ``setup.py`` and ``easy_install``. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://github.com/pypa/setuptools/issues/917 for details. **************************************************************************** **** !! easy_install.initialize_options(self) /opt/stack/nova/.tox/pep8/lib/python3.8/site-packages/setuptools/_distutils/ cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! **************************************************************************** **** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. **************************************************************************** **** !! self.initialize_options() pep8 develop-inst-nodeps: /opt/stack/nova pep8 installed: alembic==1.9.4,amqp==5.1.1,async-timeout==4.0.3,attrs==23.1. 0,autopage==0.5.1,backports.zoneinfo==0.2.1,bcrypt==4.0.1,cachetools==5.3.1, castellan==4.3.0,certifi==2023.11.17,cffi==1.15.1,cfgv==3.4.0,charset-normal izer==3.2.0,cliff==4.4.0,cmd2==2.4.3,cryptography==41.0.4,cursive==0.2.3,deb tcollector==2.5.0,decorator==5.1.1,Deprecated==1.2.14,distlib==0.3.7,dnspyth on==2.4.2,dogpile.cache==1.2.2,eventlet==0.33.3,fasteners==0.19,filelock==3. 12.4,fixtures==4.1.0,futurist==2.4.1,greenlet==2.0.2,identify==2.5.33,idna== 3.4,importlib-metadata==6.0.1,importlib-resources==6.1.1,iso8601==2.0.0,Jinj a2==3.1.2,jmespath==1.0.1,jsonpatch==1.33,jsonpointer==2.4,jsonschema==4.19. 1,jsonschema-specifications==2023.7.1,jwcrypto==1.5.1,keystoneauth1==5.4.0,k eystonemiddleware==10.5.0,kombu==5.3.2,lxml==4.9.3,Mako==1.2.4,MarkupSafe==2 .1.3,microversion-parse==1.0.1,msgpack==1.0.6,netaddr==0.9.0,netifaces==0.11 .0,nodeenv==1.8.0,-e git+ssh://songwenping@review.opendev.org:29418/openstack/nova@39f560d6730f2b 212506b7d754645c288d13f1cd#egg=nova,numpy==1.24.2,openstacksdk==2.0.0,os-bri ck==6.5.0,os-client-config==2.1.0,os-resource-classes==1.1.0,os-service-type s==1.7.0,os-traits==3.0.0,os-vif==3.3.0,os-win==5.9.0,osc-lib==2.8.1,oslo.ca che==3.5.0,oslo.concurrency==5.2.0,oslo.config==9.2.0,oslo.context==5.3.0,os lo.db==14.1.0,oslo.i18n==6.2.0,oslo.limit==2.2.0,oslo.log==5.4.0,oslo.messag ing==14.5.0,oslo.metrics==0.7.0,oslo.middleware==5.2.0,oslo.policy==4.2.1,os lo.privsep==3.2.0,oslo.reports==3.1.0,oslo.rootwrap==7.1.0,oslo.serializatio n==5.2.0,oslo.service==3.2.0,oslo.upgradecheck==2.2.0,oslo.utils==6.3.0,oslo .versionedobjects==3.2.0,ovs==3.1.2,ovsdbapp==2.5.0,packaging==23.1,paramiko ==3.3.1,Paste==3.5.3,PasteDeploy==3.0.1,pbr==6.0.0,pkgutil_resolve_name==1.3 .10,platformdirs==3.10.0,pre-commit==3.5.0,prettytable==3.9.0,prometheus-cli ent==0.17.1,psutil==5.9.5,pycadf==3.1.1,pycparser==2.21,pyinotify==0.9.6,PyJ WT==2.8.0,PyNaCl==1.5.0,pyOpenSSL==23.2.0,pyparsing==3.1.1,pyperclip==1.8.2, pyroute2==0.7.9,python-barbicanclient==5.6.1,python-cinderclient==9.4.0,pyth on-dateutil==2.8.2,python-glanceclient==4.4.0,python-keystoneclient==5.2.0,p ython-neutronclient==11.1.0,pytz==2023.3.post1,PyYAML==6.0.1,redis==5.0.0,re ferencing==0.30.2,repoze.lru==0.7,requests==2.31.0,requestsexceptions==1.4.0 ,retrying==1.3.4,rfc3986==2.0.0,Routes==2.5.1,rpds-py==0.10.3,simplejson==3. 19.1,six==1.16.0,sortedcontainers==2.4.0,SQLAlchemy==1.4.41,statsd==4.0.1,st evedore==5.1.0,tenacity==6.3.1,testresources==2.0.1,testscenarios==0.5.0,tes ttools==2.7.0,tooz==4.2.0,typing_extensions==4.8.0,tzdata==2023.3,urllib3==1 .26.16,vine==5.0.0,virtualenv==20.24.5,voluptuous==0.13.1,warlock==2.0.1,wcw idth==0.2.6,WebOb==1.8.7,websockify==0.11.0,wrapt==1.15.0,yappi==1.4.0,zipp= =3.17.0 pep8 run-test-pre: PYTHONHASHSEED='2048831401' pep8 run-test: commands[0] | pre-commit run --all-files --show-diff-on-failure [INFO] Locking pre-commit directory [INFO] Initializing environment for https://github.com/pre-commit/pre-commit-hooks. An unexpected error has occurred: CalledProcessError: command: ('/usr/bin/git', 'fetch', 'origin', '--tags') return code: 128 stdout: (none) stderr: (none) Check the log at /root/.cache/pre-commit/pre-commit.log ERROR: InvocationError for command /opt/stack/nova/.tox/pep8/bin/pre-commit run --all-files --show-diff-on-failure (exited with code 3) ____________________________________________________________________________ _______________________________________________________________ summary ____________________________________________________________________________ _______________________________________________________________ ERROR: pep8: commands failed

2 2

Issue when connecting to openstack object storage with openstacksdk
by sadir＠free.fr 05 Jan '24

05 Jan '24

Hello, I am currently developing a software application to access the OpenStack object store service on an IBM Spectrum Scale server. I first created a Python application which is manipulating objects and containers thru the OpenStack's object storage REST API (https://docs.openstack.org/api-ref/object-store) It works fine and I had no issue to access the server object store service by this way. But I also need to access the OpenStack object store service thru the openstacksdk (https://docs.openstack.org/openstacksdk/latest) Unfortunately, the connection does not seem to work properly in this case, even when using the same identifiers than in the working Python/REST application. The connection stalls and goes into some sort of timeout. I also made some tests by putting wrong identifiers, and then it fails immediately with a different error message. It makes me think that something goes wrong after the authentication process. The error message I have is this one: Failed to contact the endpoint at http://yeti.ds.eurecom.fr:8080/v1/AUTH_da0d8589692741d1b2a82956568227e6 for discovery. Fallback to using that endpoint as the base url. I am wondering if there is some additional configuration to perform on the server or the network to make it work as expected. Could you please provide me with some support so that I can sort out what's going on? I could of course share the Python piece of code I am using for my testing. Thank you for your help.

5 4