GoogleCloudPlatform / PerfKitBenchmarker

PerfKit Benchmarker (PKB) contains a set of benchmarks to measure and compare cloud offerings. The benchmarks use default settings to reflect what most users will see. PerfKit Benchmarker is licensed under the Apache 2 license terms. Please make sure to read, understand and agree to the terms of the LICENSE and CONTRIBUTING files before proceeding.
https://googlecloudplatform.github.io/PerfKitBenchmarker/
Apache License 2.0
1.9k stars 510 forks source link

OpenStack zones for volume #773

Open kivio opened 8 years ago

kivio commented 8 years ago

Current OpenStack driver where i use boot_from_volume option use VM zone name for volume - this not work because volume zones is other thing that VM zones if you want to use specified zones.

boot_from_vol = [{'boot_index': 0,
                              'uuid': image.id,
                              'volume_size': FLAGS.openstack_volume_size,
                              'source_type': 'image',
                              'destination_type': 'volume',
                              'delete_on_termination': True}]

We wan't to change it to create volume in disk zone and give this volume for booting there VM. We need to add zone in disk_spec.

meteorfox commented 8 years ago

@kivio Clarifying question: Currently the --zones flag is associated to an availability zone in the OpenStack provider implementatoin. This zone is specified for all uses VMs, networks, volumes, etc.

Recently, I pushed the PR https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/pull/734 which is is still in review, that allows you to override the availability zone just for VMs, so that we can use the <availability_zone>:<host> format to build VMs in specific hosts.

It seems the intention in PKB for the --zones flag is to represent regions. So, when you speak about differentiaing the volumes zone from the VM zones, are we talking about region or availability zone?

kivio commented 8 years ago

@meteorfox in Cinder we have another availability zones - currently hard to define - one storage node can have one zone defined in config. But if you use zones for VM, nova client try to use this same zone name for cinder and this is my problem. It's not connected with regions i think. Notation : partially solves it because nova send just root zone to cinder without host.