[openstack-dev] [Neutron] Bulk network operations

Mohammad Banikazemi mb at us.ibm.com
Tue Jan 27 16:08:08 UTC 2015

Saksham, The Neutron bulk operations are by definition atomic [1]: "Bulk
operations are always performed atomically, meaning that either all or none
of the objects in the request body are created."



[1] https://wiki.openstack.org/wiki/Neutron/APIv2-specification

From:	"Saksham Varma (sakvarma)" <sakvarma at cisco.com>
To:	"OpenStack Development Mailing List (not for usage questions)"
            <openstack-dev at lists.openstack.org>
Date:	01/26/2015 08:01 PM
Subject:	Re: [openstack-dev] [Neutron] Bulk network operations

Modifying the subject line.

From: Saksham Varma <sakvarma at cisco.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
openstack-dev at lists.openstack.org>
Date: Tuesday, January 27, 2015 at 5:21 AM
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] Bulk network operations


I was working on bulk network operations for one of Cisco’s plugins. I was
wondering how do other plugins handle failures in bulk requests. Are all
the requests in the bulk payload rolled back, if any fails (like an atomic
strategy)? Or is it like a best effort, which is not necassarily atomic?

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150127/872c5163/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150127/872c5163/attachment.gif>

More information about the OpenStack-dev mailing list