From: git-harry Date: Fri, 14 Nov 2014 17:10:58 +0000 (+0000) Subject: Remove cinder/compute/aggregate_states.py X-Git-Url: https://review.fuel-infra.org/gitweb?a=commitdiff_plain;h=72a3092bc66657f7677c55a47fd9c396a1b8810d;p=openstack-build%2Fcinder-build.git Remove cinder/compute/aggregate_states.py This file is from the initial fork from nova. It defines the states a host aggregate can take. It is not used anywhere in the cinder code and is therefore unnecessary. The commit removes the file from the codebase. Change-Id: I9ba12aabc5009020950b746f312372fa4bfa156d --- diff --git a/cinder/compute/aggregate_states.py b/cinder/compute/aggregate_states.py deleted file mode 100644 index 149f403f7..000000000 --- a/cinder/compute/aggregate_states.py +++ /dev/null @@ -1,42 +0,0 @@ -# Copyright 2010 OpenStack Foundation -# All Rights Reserved. -# -# Licensed under the Apache License, Version 2.0 (the "License"); you may -# not use this file except in compliance with the License. You may obtain -# a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT -# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the -# License for the specific language governing permissions and limitations -# under the License. - -"""Possible states for host aggregates. - -An aggregate may be 'created', in which case the admin has triggered its -creation, but the underlying hypervisor pool has not actually being set up -yet. An aggregate may be 'changing', meaning that the underlying hypervisor -pool is being setup. An aggregate may be 'active', in which case the underlying -hypervisor pool is up and running. An aggregate may be 'dismissed' when it has -no hosts and it has been deleted. An aggregate may be in 'error' in all other -cases. -A 'created' aggregate becomes 'changing' during the first request of -adding a host. During a 'changing' status no other requests will be accepted; -this is to allow the hypervisor layer to instantiate the underlying pool -without any potential race condition that may incur in master/slave-based -configurations. The aggregate goes into the 'active' state when the underlying -pool has been correctly instantiated. -All other operations (e.g. add/remove hosts) that succeed will keep the -aggregate in the 'active' state. If a number of continuous requests fail, -an 'active' aggregate goes into an 'error' state. To recover from such a state, -admin intervention is required. Currently an error state is irreversible, -that is, in order to recover from it an aggregate must be deleted. -""" - -CREATED = 'created' -CHANGING = 'changing' -ACTIVE = 'active' -ERROR = 'error' -DISMISSED = 'dismissed'