[openstack-dev] [nova] about notification in nova
Hi, all： I have a question about the notification in nova, that is the actual operator is different from the operator was record in panko. Such as the delete action, we create the VM as user1, and we delete the VM as user2， but the operator is user1 who delete the VM in panko event, not the actual operator user2. Can you tell me more about this?Thank you very much. Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance] about use shared image with each other
yes, but I also have a question, Do we have the quota limit for requests to share the image to each other? For example, someone shares the image with me without stop, how do we deal with it? -- Original -- From: "Brian Rosmaita"; Date: Mon, Nov 19, 2018 10:26 PM To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [glance] about use shared image with each other On 11/19/18 7:58 AM, Rambo wrote: > Hi,all > > Recently, I want to use the shared image with each other.I find it > isn't convenient that the producer notifies the consumer via email which > the image has been shared and what its UUID is. In other words, why the > image api v2 is no provision for producer-consumer communication? The design goal for Image API v2 image sharing was to provide an infrastructure for an "image marketplace" in an OpenStack cloud by (a) making it easy for cloud end users to share images, and (b) making it easy for end users not to be spammed by other end users taking advantage of (a). When v2 image sharing was introduced in the Grizzly release, we did not want to dictate how producer-consumer communication would work (because we had no idea how it would develop), so we left it up to operators and end users to figure this out. The advantage of email communication is that client side message filtering is available for whatever client a particular cloud end-user employs, and presumably that end-user knows how to manipulate the filters without learning some new scheme (or, if the end-user doesn't know, learning how to filter messages will apply beyond just image sharing, which is a plus). Also, email communication is just one way to handle producer-consumer communication. Some operators have adjusted their web interfaces so that when an end-user looks at the list of images available, a notification pops up if the end-user has any images that have been shared with them and are still in "pending" status. There are various other creative things you can do using the normal API calls with regular user credentials. In brief, we figured that if an image marketplace evolved in a particular cloud, producers and consumers would forge their own relationships in whatever way made the most sense for their particular use cases. So we left producer-consumer communication out-of-band. > To make it is more convenient, if we can add a task to change the > member_status from "pending" to "accepted" when we share the image with > each other. It is similar to the resize_confirm in Nova, we can control > the time interval in config. You could do this, but that would defeat the entire purpose of the member statuses implementation, and hence I do not recommend it. See OSSN-0005 [1] for more about this issue. Additionally, since the Ocata release, "community" images have been available. These do not have to be accepted by an end user (but they also don't show up in the default image-list response). Who can "communitize" an image is governed by policy. See [2] for a discussion of the various types of image sharing currently available in the Image API v2. The Image Service API v2 api-ref [3] contains a brief discussion of image visibility and image sharing that may also be useful. Finally, the Glance Ocata release notes [4] have an extensive discussion of image visibility. >Can you tell me more about this?Thank you very much! The original design page on the wiki [5] has a list of 14 use cases we wanted to address; looking through those will give you a better idea of why we made the design choices we did. Hope this helps! cheers, brian [0] http://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-image-api-v2.html [1] https://wiki.openstack.org/wiki/OSSN/1226078 [2] http://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-image-api-v2.html [3] https://developer.openstack.org/api-ref/image/v2/ [4] https://docs.openstack.org/releasenotes/glance/ocata.html [5] https://wiki.openstack.org/wiki/Glance-api-v2-image-sharing > > Best Regards > Rambo > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] about filter the flavor
Hi,all I have an idea.Now we can't filter the special flavor according to the property.Can we achieve it?If we achieved this,we can filter the flavor according the property's key and value to filter the flavor. What do you think of the idea?Can you tell me more about this ?Thank you very much.__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [glance] about use shared image with each other
Hi,all Recently, I want to use the shared image with each other.I find it isn't convenient that the producer notifies the consumer via email which the image has been shared and what its UUID is. In other words, why the image api v2 is no provision for producer-consumer communication? To make it is more convenient, if we can add a task to change the member_status from "pending" to "accepted" when we share the image with each other. It is similar to the resize_confirm in Nova, we can control the time interval in config. Can you tell me more about this?Thank you very much! Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Openstack-operators] [nova] about resize the instance
When I resize the instance, the compute node report that "libvirtError: internal error: qemu unexpectedly closed the monitor: 2018-11-08T09:42:04.695681Z qemu-kvm: cannot set up guest memory 'pc.ram': Cannot allocate memory".Has anyone seen this situation?And the ram_allocation_ratio is set 3 in nova.conf.The total memory is 125G.When I use the "nova hypervisor-show server" command to show the compute node's free_ram_mb is -45G.If it is the result of excessive use of memory? Can you give me some suggestions about this?Thank you very much. -- Original ------ From: "Rambo"; Date: Thu, Nov 8, 2018 05:45 PM To: "OpenStack Developmen"; Subject: [openstack-dev] [nova] about resize the instance Hi,all When we resize/migrate instance, if error occurs on source compute node, the instance state can rollback to active currently.But if error occurs in "finish_resize" function on destination compute node, the instance state would not rollback to active. Is there a bug, or if anyone plans to change this?Can you tell me more about this ?Thank you very much. Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] about resize the instance
Hi,all When we resize/migrate instance, if error occurs on source compute node, the instance state can rollback to active currently.But if error occurs in "finish_resize" function on destination compute node, the instance state would not rollback to active. Is there a bug, or if anyone plans to change this?Can you tell me more about this ?Thank you very much. Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] about live-resize the instance
Hi,all I find it is important that live-resize the instance in production environment. We have talked it many years and we agreed this in Rocky PTG, then the author remove the spec to Stein, but there is no information about this spec, is there anyone to push the spec and achieve it? Can you tell me more about this ?Thank you very much. [1]https://review.openstack.org/#/c/141219/ Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] about use nfs driver to backup the volume snapshot
Sorry , I mean use the NFS driver as the cinder-backup_driver.I see the remotefs code achieve the create_volume_from snapshot[1],in this function the snapshot.status must be available. But before this in the api part, the snapshot.status was changed to the backing_up status[2].Is there something wrong?Can you tell me more about this?Thank you very much. [1]https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/remotefs.py#L1259 [2]https://github.com/openstack/cinder/blob/master/cinder/backup/api.py#L292 -- Original -- From: "Eric Harney"; Date: Fri, Nov 2, 2018 10:00 PM To: "jsbryant"; "OpenStack Developmen"; Subject: Re: [openstack-dev] [cinder] about use nfs driver to backup the volume snapshot On 11/1/18 4:44 PM, Jay Bryant wrote: > On Thu, Nov 1, 2018, 10:44 AM Rambo wrote: > >> Hi,all >> >> Recently, I use the nfs driver as the cinder-backup backend, when I >> use it to backup the volume snapshot, the result is return the >> NotImplementedError[1].And the nfs.py doesn't has the >> create_volume_from_snapshot function. Does the community plan to achieve >> it which is as nfs as the cinder-backup backend?Can you tell me about >> this?Thank you very much! >> >> Rambo, > > The NFS driver doesn't have full snapshot support. I am not sure if that > function missing was an oversight or not. I would reach out to Eric Harney > as he implemented that code. > > Jay > create_volume_from_snapshot is implemented in the NFS driver. It is in the remotefs code that the NFS driver inherits from. But, I'm not sure I understand what's being asked here -- how is this related to using NFS as the backup backend? >> >> >> [1] >> https://github.com/openstack/cinder/blob/master/cinder/volume/driver.py#L2142 >> >> >> >> >> >> >> >> >> Best Regards >> Rambo __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [cinder] about use nfs driver to backup the volume snapshot
Hi,all Recently, I use the nfs driver as the cinder-backup backend, when I use it to backup the volume snapshot, the result is return the NotImplementedError[1].And the nfs.py doesn't has the create_volume_from_snapshot function. Does the community plan to achieve it which is as nfs as the cinder-backup backend?Can you tell me about this?Thank you very much! [1]https://github.com/openstack/cinder/blob/master/cinder/volume/driver.py#L2142 Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [docs][cinder] about cinder volume qos
Hi,all At first,I find it is supported that we can define hard performance limits for each volume in doc.openstack.org[1].But only can define hard performance limits for each volume type in fact. Another, the note"As of the Nova 18.0.0 Rocky release, front end QoS settings are only supported when using the libvirt driver.",in fact, we have supported the front end QoS settings when using the libvirt driver previous. Is the document wrong?Can you tell me more about this ?Thank you very much. [1]https://docs.openstack.org/cinder/latest/admin/blockstorage-basic-volume-qos.html Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Openstack-operators][nova] ask deployment question
Hi,all I have some questions about deploy the large scale openstack cloud.Such as 1.Only in one region situation,How many physical machines are the biggest deployment scale in our community? Can you tell me more about these combined with own practice? Would you give me some methods to learn it?Such as the website,blog and so on. Thank you very much!Looking forward to hearing from you. Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [docs][nova] about update flavor
Sorry,I don't understand what has been removed,the docs about the update the flavor's cpu?Otherwise,why we don't consider to add the function that we can update the flavor's cpu? -- Original -- From: "Zhenyu Zheng"; Date: 2018年8月16日(星期四) 下午3:56 To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [docs][nova] about update flavor We only allow update flavor descriptions(added in microversion 2.55) in Nova and what the horizon did was just delete the old one and create a new one, and I think it has been removed in last year. On Thu, Aug 16, 2018 at 3:19 PM Rambo wrote: Hi,all I find it is supported that we can update the flavor name, VCPUs, RAM, root disk, ephemeral disk and so on in doc.openstack.org[1].But only can change the flavor propertity in fact.Is the document wrong?Can you tell me more about this ?Thank you very much. [1]https://docs.openstack.org/horizon/latest/admin/manage-flavors.html Best Regards Rambo __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [docs][nova] about update flavor
Hi,all I find it is supported that we can update the flavor name, VCPUs, RAM, root disk, ephemeral disk and so on in doc.openstack.org[1].But only can change the flavor propertity in fact.Is the document wrong?Can you tell me more about this ?Thank you very much. [1]https://docs.openstack.org/horizon/latest/admin/manage-flavors.html Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Openstack-operators][nova] deployment question consultation
Hi,all I have some questions about deploy the large scale openstack cloud.Such as 1.Only in one region situation,what will happen in the cloud as expansion of cluster size?Then how solve it?If have the limit physical node number under the one region situation?How many nodes would be the best in one regione? 2.When to use cellV2 is most suitable in cloud? 3.How to shorten the time of batch creation of instance? Can you tell me more about these combined with own practice? Would you give me some methods to learn it?Such as the website,blog and so on. Thank you very much!Looking forward to hearing from you. Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Openstack-operators][nova]about live-resize down the instance
Hi,all I find it is important that live-resize the instance in production environment,especially live downsize the disk.And we have talked it many years.But I don't know why the bp[1] didn't approved.Can you tell me more about this ?Thank you very much. [1]https://review.openstack.org/#/c/141219/ Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] about live-resize down the instance
Hi,all I find it is important that live-resize the instance in production environment,especially live downsize the disk.And we have talked it many years.But I don't know why the bp[1] didn't approved.Can you tell me more about this ?Thank you very much. [1]https://review.openstack.org/#/c/141219/ Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [cinder] about block device driver
Hi,all In the Cinder repository, I noticed that the BlockDeviceDriver driver is being deprecated, and was eventually be removed with the Queens release. https://github.com/openstack/cinder/blob/stable/ocata/cinder/volume/drivers/block_device.py However,I want to use it out of tree,but I don't know how to use it out of tree,Can you share me a doc? Thank you very much! Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] about block device driver
yes -- Original -- From: "Ivan Kolodyazhny"; Date: Tue, Jul 17, 2018 05:00 PM To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [cinder] about block device driver Do you use the volumes on the same nodes where instances are located? Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Jul 17, 2018 at 11:52 AM, Rambo wrote: yes,My cinder driver is LVM+LIO.I have upload the test result in appendix.Can you show me your test results?Thank you! -- Original -- From: "Ivan Kolodyazhny"; Date: Tue, Jul 17, 2018 04:09 PM To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [cinder] about block device driver Rambo, Did you try to use LVM+LIO target driver? It shows pretty good performance comparing to BlockDeviceDriver, Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Jul 17, 2018 at 10:24 AM, Rambo wrote: Oh,the instances using Cinder perform intense I/O, thus iSCSI or LVM is not a viable option - benchmarked them several times, unsatisfactory results.Sometimes it's IOPS is twice as bad,could you show me your test data?Thank you! Cheers, Rambo -- Original -- From: "Sean McGinnis"; Date: 2018年7月16日(星期一) 晚上9:32 To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [cinder] about block device driver On Mon, Jul 16, 2018 at 01:32:26PM +0200, Gorka Eguileor wrote: > On 16/07, Rambo wrote: > > Well,in my opinion,the BlockDeviceDriver is more suitable than any other > > solution for data processing scenarios.Does the community will agree to > > merge the BlockDeviceDriver to the Cinder repository again if our company > > hold the maintainer and CI? > > > > Hi, > > I'm sure the community will be happy to merge the driver back into the > repository. > The other reason for its removal was its inability to meet the minimum feature set required for Cinder drivers along with benchmarks showing the LVM and iSCSI driver could be tweaked to have similar or better performance. The other option would be to not use Cinder volumes so you just use local storage on your compute nodes. Readding the block device driver is not likely an option. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev D7C81B68@5B350B78.B0B54D5B Description: Binary data __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] about block device driver
yes,My cinder driver is LVM+LIO.I have upload the test result in appendix.Can you show me your test results?Thank you! -- Original -- From: "Ivan Kolodyazhny"; Date: Tue, Jul 17, 2018 04:09 PM To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [cinder] about block device driver Rambo, Did you try to use LVM+LIO target driver? It shows pretty good performance comparing to BlockDeviceDriver, Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Jul 17, 2018 at 10:24 AM, Rambo wrote: Oh,the instances using Cinder perform intense I/O, thus iSCSI or LVM is not a viable option - benchmarked them several times, unsatisfactory results.Sometimes it's IOPS is twice as bad,could you show me your test data?Thank you! Cheers, Rambo -- Original -- From: "Sean McGinnis"; Date: 2018年7月16日(星期一) 晚上9:32 To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [cinder] about block device driver On Mon, Jul 16, 2018 at 01:32:26PM +0200, Gorka Eguileor wrote: > On 16/07, Rambo wrote: > > Well,in my opinion,the BlockDeviceDriver is more suitable than any other > > solution for data processing scenarios.Does the community will agree to > > merge the BlockDeviceDriver to the Cinder repository again if our company > > hold the maintainer and CI? > > > > Hi, > > I'm sure the community will be happy to merge the driver back into the > repository. > The other reason for its removal was its inability to meet the minimum feature set required for Cinder drivers along with benchmarks showing the LVM and iSCSI driver could be tweaked to have similar or better performance. The other option would be to not use Cinder volumes so you just use local storage on your compute nodes. Readding the block device driver is not likely an option. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 99BB7964@8738C509.52AE4D5B.png Description: Binary data test2639.png Description: Binary data __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] about block device driver
Oh,the instances using Cinder perform intense I/O, thus iSCSI or LVM is not a viable option - benchmarked them several times, unsatisfactory results.Sometimes it's IOPS is twice as bad,could you show me your test data?Thank you! Cheers, Rambo -- Original -- From: "Sean McGinnis"; Date: 2018年7月16日(星期一) 晚上9:32 To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [cinder] about block device driver On Mon, Jul 16, 2018 at 01:32:26PM +0200, Gorka Eguileor wrote: > On 16/07, Rambo wrote: > > Well,in my opinion,the BlockDeviceDriver is more suitable than any other > > solution for data processing scenarios.Does the community will agree to > > merge the BlockDeviceDriver to the Cinder repository again if our company > > hold the maintainer and CI? > > > > Hi, > > I'm sure the community will be happy to merge the driver back into the > repository. > The other reason for its removal was its inability to meet the minimum feature set required for Cinder drivers along with benchmarks showing the LVM and iSCSI driver could be tweaked to have similar or better performance. The other option would be to not use Cinder volumes so you just use local storage on your compute nodes. Readding the block device driver is not likely an option. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] about block device driver
But I want to create a volume backed server for data processing scenarios,maybe the BlockDeviceDriver is more suitable. -- Original -- From: "Sean McGinnis"; Date: 2018年7月16日(星期一) 晚上9:32 To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [cinder] about block device driver On Mon, Jul 16, 2018 at 01:32:26PM +0200, Gorka Eguileor wrote: > On 16/07, Rambo wrote: > > Well,in my opinion,the BlockDeviceDriver is more suitable than any other > > solution for data processing scenarios.Does the community will agree to > > merge the BlockDeviceDriver to the Cinder repository again if our company > > hold the maintainer and CI? > > > > Hi, > > I'm sure the community will be happy to merge the driver back into the > repository. > The other reason for its removal was its inability to meet the minimum feature set required for Cinder drivers along with benchmarks showing the LVM and iSCSI driver could be tweaked to have similar or better performance. The other option would be to not use Cinder volumes so you just use local storage on your compute nodes. Readding the block device driver is not likely an option. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 回复:Re: [cinder] about block device driver
ok,thank you --原始邮件-- 发件人："Gorka Eguileor "; 发送时间：2018年7月16日(星期一) 晚上7:32 收件人："OpenStack Developmen" ; 主题：Re: [openstack-dev] [cinder] about block device driver --- On 16/07, Rambo wrote: > Well,in my opinion,the BlockDeviceDriver is more suitable than any other > solution for data processing scenarios.Does the community will agree to merge > the BlockDeviceDriver to the Cinder repository again if our company hold the > maintainer and CI? > Hi, I'm sure the community will be happy to merge the driver back into the repository. Still, I would recommend you looking at the "How To Contribute a driver to Cinder" guide [1] and the "Third Party CI Requirement Policy" documentation [2], and then adding this topic to Wednesday's meeting [3] and go to the meeting to ensure that everybody is on board with it. Best regards, Gorka. [1]: https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver [2]: https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers [3]: https://etherpad.openstack.org/p/cinder-rocky-meeting-agendas > > -- Original -- > From: "Gorka Eguileor"; > Date: 2018年7月16日(星期一) 下午5:20 > To: "OpenStack Developmen"; > Subject: Re: [openstack-dev] [cinder] about block device driver > > > On 16/07, Rambo wrote: > > Hi,all > > > > > > In the Cinder repository, I noticed that the BlockDeviceDriver driver > > is being deprecated, and was eventually be removed with the Queens release. > > > > > > https://github.com/openstack/cinder/blob/stable/ocata/cinder/volume/drivers/block_device.py > > > > > > In my use case, the instances using Cinder perform intense I/O, thus iSCSI > > or LVM is not a viable option - benchmarked them several times, since Juno, > > unsatisfactory results.For data processing scenarios is always better to > > use local storage than any SAN/NAS solution. > > > > > > So I felt a great need to know why we deprecated it.If there has any better > > one to replace it? What do you suggest to use once BlockDeviceDriver is > > removed?Can you tell me about this?Thank you very much! > > > > Best Regards > > Rambo > > Hi, > > If I remember correctly the driver was deprecated because it had no > maintainer or CI. In Cinder we require our drivers to have both, > otherwise we can't guarantee that they actually work or that anyone will > fix it if it gets broken. > > Cheers, > Gorka. > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder] about block device driver
Well,in my opinion,the BlockDeviceDriver is more suitable than any other solution for data processing scenarios.Does the community will agree to merge the BlockDeviceDriver to the Cinder repository again if our company hold the maintainer and CI? -- Original -- From: "Gorka Eguileor"; Date: 2018年7月16日(星期一) 下午5:20 To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [cinder] about block device driver On 16/07, Rambo wrote: > Hi,all > > > In the Cinder repository, I noticed that the BlockDeviceDriver driver is > being deprecated, and was eventually be removed with the Queens release. > > > https://github.com/openstack/cinder/blob/stable/ocata/cinder/volume/drivers/block_device.py > > > In my use case, the instances using Cinder perform intense I/O, thus iSCSI or > LVM is not a viable option - benchmarked them several times, since Juno, > unsatisfactory results.For data processing scenarios is always better to use > local storage than any SAN/NAS solution. > > > So I felt a great need to know why we deprecated it.If there has any better > one to replace it? What do you suggest to use once BlockDeviceDriver is > removed?Can you tell me about this?Thank you very much! > > Best Regards > Rambo Hi, If I remember correctly the driver was deprecated because it had no maintainer or CI. In Cinder we require our drivers to have both, otherwise we can't guarantee that they actually work or that anyone will fix it if it gets broken. Cheers, Gorka. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [cinder] about block device driver
Hi,all In the Cinder repository, I noticed that the BlockDeviceDriver driver is being deprecated, and was eventually be removed with the Queens release. https://github.com/openstack/cinder/blob/stable/ocata/cinder/volume/drivers/block_device.py In my use case, the instances using Cinder perform intense I/O, thus iSCSI or LVM is not a viable option - benchmarked them several times, since Juno, unsatisfactory results.For data processing scenarios is always better to use local storage than any SAN/NAS solution. So I felt a great need to know why we deprecated it.If there has any better one to replace it? What do you suggest to use once BlockDeviceDriver is removed?Can you tell me about this?Thank you very much! Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] about filter the flavor
Does the "OSC“ meas the osc placement? -- Original -- From: "Matt Riedemann"; Date: Mon, Jul 2, 2018 10:36 PM To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [nova] about filter the flavor On 7/2/2018 2:43 AM, 李杰 wrote: > Oh,sorry,not this means,in my opinion,we could filter the flavor in > flavor list.such as the cli:openstack flavor list --property key:value. There is no support for natively filtering flavors by extra specs in the compute REST API so that would have to be added with a microversion (if we wanted to add that support). So it would require a nova spec, which would be reviewed for consideration at the earliest in the Stein release. OSC could do client-side filtering if it wanted. -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] about filter the flavor
Hi,all I have an idea.Now we can't filter the special flavor according to the property.Can we achieve it?If we achieved this,we can filter the flavor according the property's key and value to filter the flavor. What do you think of the idea?Can you tell me more about this ?Thank you very much. Best Regards Rambo__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
