August 2020 - openstack-discuss - lists.openstack.org

[Diversity] Diversity & Inclusion WG Meeting 8/31 - Removing Divisive Language
by Amy Marrich 26 Aug '20

26 Aug '20

The Diversity & Inclusion WG has taken on the task from this week's Board meeting to assist with the development of the OSF's stance on the removal of Divisive Language within the OSF projects. The WG invites members of all OSF projects to participate in this effort and to join us at our next meeting Monday, August 31, at 17:00 UTC which will be held at https://meetpad.opendev.org/osf-diversity-and-inclusion. <https://meetpad.opendev.org/osf-diversity-and-inclusion> The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. If you have any questions please let me and the team know here, on #openstack-diversity on IRC, or you can email me directly. Thanks, Amy Marrich (spotz)

1 0

openstack-discuss
by ARUNKUMAR PALANISAMY 26 Aug '20

26 Aug '20

Hello Team, My name is ARUNKUMAR PALANISAMY, As part of our project requirement, we are evaluating trove components and need your support for experimental datastore Image for testing cluster. (Redis, Cassandra, MongoDB, Couchbase) 1.) We are running devstack enviorment with Victoria Openstack release and with this image (trove-master-guest-ubuntu-bionic-dev.qcow2<https://tarballs.opendev.org/openstack/trove/images/trove-master-guest-ubun…>), we are able to deploy mysql instance and and getting below error while creating mongoDB instances. "ModuleNotFoundError: No module named 'trove.guestagent.datastore.experimental' " 2.) While tried creating mongoDB image with diskimage-builder<https://opendev.org/openstack/diskimage-builder> tool, but we are getting "Block device " element error. Regards, Arunkumar Palanisamy =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

1 0

Re: [tc][masakari] Project aliveness (was: [masakari] Meetings)
by Jegor van Opdorp 26 Aug '20

26 Aug '20

We're also using masakari and willing to help maintain it! ________________________________ From: Mark Goddard <mark(a)stackhpc.com> Sent: Monday, August 17, 2020 12:12 PM To: Jegor van Opdorp <jegor(a)greenedge.cloud> Subject: Fwd: [tc][masakari] Project aliveness (was: [masakari] Meetings) ---------- Forwarded message --------- From: Radosław Piliszek <radoslaw.piliszek(a)gmail.com> Date: Fri, 14 Aug 2020 at 08:53 Subject: [tc][masakari] Project aliveness (was: [masakari] Meetings) To: openstack-discuss <openstack-discuss(a)lists.openstack.org> Cc: Sampath Priyankara (samP) <sam47priya(a)gmail.com>, Tushar Patil (tpatil) <tushar.vitthal.patil(a)gmail.com> Hi, it's been a month since I wrote the original (quoted) email, so I retry it with CC to the PTL and a recently (this year) active core. I see there have been no meetings and neither Masakari IRC channel nor review queues have been getting much attention during that time period. I am, therefore, offering my help to maintain the project. Regarding the original topic, I would opt for running Masakari meetings during the time I proposed so that interested parties could join and I know there is at least some interest based on recent IRC activity (i.e. there exist people who want to use and discuss Masakari - apart from me that is :-) ). -yoctozepto On Mon, Jul 13, 2020 at 9:53 PM Radosław Piliszek <radoslaw.piliszek(a)gmail.com> wrote: > > Hello Fellow cloud-HA-seekers, > > I wanted to attend Masakari meetings but I found the current schedule unfit. > Is there a chance to change the schedule? The day is fine but a shift > by +3 hours would be nice. > > Anyhow, I wanted to discuss [1]. I've already proposed a change > implementing it and looking forward to positive reviews. :-) That > said, please reply on the change directly, or mail me or catch me on > IRC, whichever option sounds best to you. > > [1] https://blueprints.launchpad.net/masakari/+spec/customisable-ha-enabled-ins… > > -yoctozepto

6 13

[kolla] Kayobe config walkthrough docs call
by Mark Goddard 26 Aug '20

26 Aug '20

Hi, In today's kolla IRC meeting we proposed to have a meeting to discuss the long awaited Kayobe configuration walkthrough documentation. We'll try to agree on an approach, and get people signed up for writing parts or all of it. The proposed meeting time is tomorrow (27th August) at 15:00 - 16:00 UTC, the same slot as the Kolla Klub (which is still on summer break). Please reply if you would like to attend but cannot make this slot. Google meet link: https://meet.google.com/xfg-ieza-qrz Regards, Mark

1 0

[monasca] Retire monasca-analytics repository
by Witek Bedyk 26 Aug '20

26 Aug '20

Hello, this message is to announce the retirement of openstack/monasca-analytics repository. The project will not accept any new patches. It will follow the process described in Project Team Guide [1]. Please reply to this message until Sept. 7 if you would like to take over the development and maintenance of this repository. Thanks Witek [1] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-re…

1 0

[releases] Dropping my releases core/release-manager hat
by Jean-Philippe Evrard 26 Aug '20

26 Aug '20

Hello folks, I am sad to announce that, while super motivated to keep helping the team, I cannot reliably and consistantly do my duties of core in the releases team, due to my current duties at work. It's been a while I haven't significantly helped the release team, and the team deserve all the transparency and clarity it can get about its contributors. It's time for me to step down. It's been a pleasure to help the team while it lasted. If you are looking for a team to get involved in OpenStack, make no mistake, the release team is awesome. Thank you everyone in the team, you were all amazing and so welcoming :) Regards, Jean-Philippe Evrard (evrardjp)

3 2

nova config vCenter and creating instance failed
by Ankele zhang 26 Aug '20

26 Aug '20

Hi all I have config vCenter in my nova.conf, cinder.conf and glance-api.conf. First of all, I can create VM inner vSphere successfully and I can create VM inner OpenStack without vCenter configuration successfully. Now I config vCenter driver in nova, cinder and glance. Creating images and volumes successfully, but when I create VM instance, I got the error message "Build of instance e3e8e049-98fc-486e-95c7-e17ec0e22e59 aborted: 主机配置过程中出错。" , in english is "Build of instance e3e8e049-98fc-486e-95c7-e17ec0e22e59 aborted: an error occurred during host configuration". And error in vCSA client is just "主机配置过程中出错" while creating vm. Environment: OpenStack(Rocky), vSphere(6.7), storage(iSCSI),network(OVS vlan),vCenter is VMware-VIM-all-6.7.0-16046470.iso installed in windows2012 server. I don't know where did my configuration error in OpenStack or something error in my vSphere. nova.conf: [default] ... compute_driver = vmwareapi.VMwareVCDriver [vmware] host_ip = 192.168.3.115 host_username = administrator(a)vsphere.local host_password = Zl@123456 cluster_name = mycluster datastore_regex = Datastore_iscsi insecure = True vlan_interface = vmnic0 integration_bridge = br-int api_retry_count = 10 cinder.conf: [DEFAULT] enabled_backends = vmware default_volume_type = vmware [vmware] volume_driver = cinder.volume.drivers.vmware.vmdk.VMwareVcVmdkDriver vmware_host_ip=192.168.3.115 vmware_host_password=Zl@123456 vmware_host_username=administrator(a)vsphere.local vmware_wsdl_location=https://192.168.3.115/sdk/vimService.wsdl vmware_volume_folder= openstack_volume vmware_datastore_regex = Datastore_iscsi vmware_insecure = True vmware_host_version = 6.7 glance-api.conf: [default] ... known_stores = vmware default_store = vmware [glance_store] filesystem_store_datadir = /tri_fs/images/ stores = files,http,vmware default_store = vsphere vmware_server_host = 192.168.3.115 vmware_server_username = administrator(a)vsphere.local vmware_server_password = Zl@123456 vmware_datastore_name = Datastore_iscsi vmware_datacenter_path = Datacenter vmware_datastores = Datacenter:Datastore_iscsi vmware_task_poll_interval = 5 vmware_store_image_dir = /openstack_glance vmware_api_insecure = True I hope you can help me. Thank you very much!

1 0

[largescale-sig] Next meeting: August 26, 8utc
by Thierry Carrez 26 Aug '20

26 Aug '20

Hi everyone, Our next meeting will be a EU-APAC-friendly meeting, on Wednesday, August 26 at 8 UTC[1] in the #openstack-meeting-3 channel on IRC: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200826T08 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting A reminder of the TODOs we had from last meeting, in case you have time to make progress on them: - amorin to add some meat to the wiki page before we push the Nova doc patch further - all to describe briefly how you solved metrics/billing in your deployment in https://etherpad.openstack.org/p/large-scale-sig-documentation Talk to you all on Wednesday, -- Thierry Carrez

1 1

[horizon] default create_volume setting can't be changed
by Eugen Block 26 Aug '20

26 Aug '20

Hi *, we recently upgraded from Ocata to Train and I'm struggling with a specific setting: I believe since Pike version the default for "create_volume" changed to "true" when launching instances from Horizon dashboard. I would like to change that to "false" and set it in our custom /srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.d/_100_local_settings.py: LAUNCH_INSTANCE_DEFAULTS = { 'config_drive': False, 'create_volume': False, 'hide_create_volume': False, 'disable_image': False, 'disable_instance_snapshot': False, 'disable_volume': False, 'disable_volume_snapshot': False, 'enable_scheduler_hints': True, } Other configs from this file work as expected, so that custom file can't be the reason. After apache and memcached restart nothing changes, the default is still "true". Can anyone shed some light, please? I haven't tried other configs yet so I can't tell if more options are affected. Thanks! Eugen

2 3

[nova] Add 'accel_uuids' parameter to rebuild() function of the virt driver
by Brin Zhang(张百林) 26 Aug '20

26 Aug '20

Hi all. In Ussuri release we were completed the nova-cyborg-interaction feature, but there are some operations of instance were blocked [1], we will support evacuate/rebuild [2] and/or shelve/unshelve [2] instance with accelerator in Victoria release. In [2] we will add 'accel_uuids' parameter to the rebuild() method of virt driver and Ironic driver, in virt/driver [4] we are not implemented the rebuild() method, and the 'accel_uuids' will be ignored in virt/ironic/driver. [1] https://docs.openstack.org/api-guide/compute/accelerator-support.html [2] Cyborg evacuate/rebuild support https://review.opendev.org/#/c/715326 [3] Cyborg shelve/unshelve support https://review.opendev.org/#/c/729563 [4] https://github.com/openstack/nova/blob/master/nova/virt/driver.py#L285 [5] https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L1… brinzhang

1 0