Re: [openstack-dev] [Neutron] FWaaS: Support for explicit commit

Hi Sumit, So all the other Network Services like LBaaS, VPNaaS as well also has to support implicit and explicit 'Commit' modes for configuration. It is certainly a good idea to support implicit and explicit modes. It is good if all the other network services also follows the same. regards, ba

Re: [openstack-dev] Usage of mox through out the Openstack project.

Based on an intial run of the Hyper-V Nova tests with pymox (https://github.com/emonty/pymox), only 2 of the tests required some minor adjustements while the rest was running perfectly fine by just replacing the mox import line. If we plan to support pymox in Havana, I'd be happy to send a patc

Re: [openstack-dev] the performance degradation of swift PUT

For those playing along from home, this question has been discussed at https://answers.launchpad.net/swift/+question/233444 --John On Aug 3, 2013, at 10:34 AM, kalrey wrote: > hi openstackers， > I'm a learner of swift. I took some benchmark about swift last week and the > result is not pleas

Re: [openstack-dev] [Ceilometer] Event API Access Controls

On 08/02/2013 06:26 PM, Herndon, John Luke (HPCS - Ft. Collins) wrote: Hello, I'm currently implementing the event api blueprint[0], and am wondering what access controls we should impose on the event api. The purpose of the blueprint is to provide a StackTach equivalent in the ceilometer api. I

[openstack-dev] [Nova] Monitoring plugin file names

Hi, As part of the BP blueprint utilization-aware-scheduling a plugin has been added. I have an issue with the placement of the drivers (the code is looking good:)) and would like to know what the community thin

[openstack-dev] the performance degradation of swift PUT

hi openstackers， I'm a learner of swift. I took some benchmark about swift last week and the result is not pleasant. When I put a large number of small files(4KB) under high concurrency, the performance degradation of PUT appeared. The speed of PUT even can reach to 2000/s at beginning. But it d

Re: [openstack-dev] [Cinder] Snapshot List support

The only snapshot functions in the volume driver are create_snapshot, delete_shapshot and create_volume_from_snapshot. That row should probably be deleted from the wiki since listing snapshots occurs entirely via the db/api. I've added the current set of supported features for the Solaris ISCSI dri

Re: [openstack-dev] [openstack][neutron] Reserved fixed IPs

Mark, Ian, than you for your answers. > Have you considered altering the allocation range of a subnet? You can still > create ports with IPs that are within the subnet, but> outside of the > allocation range. You can then control which instances get the "reserved" > IPs from the block that is

Re: [openstack-dev] [Cinder] Snapshot List support

On 08/03/2013 10:49 AM, Mikhail Khodos wrote: The Cinder Support Matrix https://wiki.openstack.org/wiki/CinderSupportMatrix, states that snapshot listing is implemented in drivers by: LVM, EMC, NetApp, IBM, etc. However, I could not find any methods or interfaces in the cinder volume api that imp

[openstack-dev] [Cinder] Snapshot List support

The Cinder Support Matrix https://wiki.openstack.org/wiki/CinderSupportMatrix, states that snapshot listing is implemented in drivers by: LVM, EMC, NetApp, IBM, etc. However, I could not find any methods or interfaces in the cinder volume api that implement snapshot listing. Could anyone clarify if

Re: [openstack-dev] [Neutron] FWaaS: Support for explicit commit

On 03/08/13 02:43, Sumit Naiksatam wrote: Hi All, In Neutron Firewall as a Service (FWaaS), we currently support an implicit commit mode, wherein a change made to a firewall_rule is propagated immediately to all the firewalls that use this rule (via the firewall_policy association), and the rule