Instead of implementing availability zones in the service table, availability zones are implemented using general aggregate metadata. This patch does not remove availability zones from the service table, a latter patch will do that. * In theory supports a single compute node in multiple availability zones * Drop availability_zone column from Aggregate table (is now a property) * map aggregate metadata 'availability_zone' so API does not change Implements blueprint aggregate-based-availability-zones Change-Id: I2a2ac5bfaa526d639dff5efa392c051347dbd9bb
		
			
				
	
	
		
			15 lines
		
	
	
		
			374 B
		
	
	
	
		
			XML
		
	
	
	
	
	
			
		
		
	
	
			15 lines
		
	
	
		
			374 B
		
	
	
	
		
			XML
		
	
	
	
	
	
<?xml version='1.0' encoding='UTF-8'?>
 | 
						|
<aggregate>
 | 
						|
  <name>name</name>
 | 
						|
  <availability_zone>nova</availability_zone>
 | 
						|
  <deleted>False</deleted>
 | 
						|
  <created_at>2012-11-16 06:22:25.587739</created_at>
 | 
						|
  <updated_at>None</updated_at>
 | 
						|
  <hosts/>
 | 
						|
  <deleted_at>None</deleted_at>
 | 
						|
  <id>1</id>
 | 
						|
  <metadata>
 | 
						|
    <availability_zone>nova</availability_zone>
 | 
						|
  </metadata>
 | 
						|
</aggregate>
 |