Hey,
I’ve been playing with Grizzly -> Havana upgrade paths with cells.
Having Havana at the api cell with Grizzly compute cells won’t work (don’t
think it’s supposed too?)
Having Grizzly at api level with Havana compute cell almost works, it seems the
only major issue is the block_device_mappings.
When havana child gets a parent grizzly build request the block_device_mapping
is an empty list, when it come from Havana it has something like:
block_device_mapping = [{'boot_index': 0,
'connection_info': None,
'delete_on_termination': True,
'destination_type': 'local',
'device_name': None,
'device_type': 'disk',
'disk_bus': None,
'guest_format': None,
'image_id': ‘XXX-XXX-XXX-XXX',
'instance_uuid': XXX-XXX-XXX-XXX,
'no_device': None,
'snapshot_id': None,
'source_type': 'image',
'volume_id': None,
'volume_size': None}]
I don’t know much about the new BDM stuff but it looks like not too much code
needed to get this working?
Was wondering if anyone else is looking into this kind of stuff or is willing
to help?
Cheers,
Sam
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
