Nice job, Mikal. I've added some review comments along with Eoghan.
Best,
-jay
On 05/20/2012 10:43 PM, Michael Still wrote:
On 09/05/12 09:01, Gabe Westmaas wrote:
This actually sounds like it covers most of the first run needs in this
etherpad:
BTW that patch is up for review as:
https://review.openstack.org/7302
Cheers,
eoghan
I'm working on a patch to at least make the glance UUID - S3 image
ID
not totally depend on an on-demand insertion order as it does now.
Agreed, collisions are inevitable given the relative domain and
On 04/05/12 20:31, Eoghan Glynn wrote:
Sorry for the slow reply, I've been trapped in meetings.
[snip]
So the way things currently stand, the EC2 image ID isn't really capable of
migration.
I was thinking however that we should change the EC2 image generation logic,
so that there is a
Alternatively, we could just consider the ec2 mapping layer to be global data
that must be replicated somehow across the system. I don't think we can really
ensure no collisions mapping from uuid - ec2_id deterministically, and I don't
see a clear path forward when we do get a collision.
Vish
I'm working on a patch to at least make the glance UUID - S3 image ID
not totally depend on an on-demand insertion order as it does now.
Agreed, collisions are inevitable given the relative domain and range
sizes (122 unique bit UUID versus 32-bit hex string) - in testing,
the first colliding
This actually sounds like it covers most of the first run needs in this
etherpad:
http://etherpad.openstack.org/FolsomGlanceImageReplication
Definitely excited to see the tool, and then I wonder if we can just add a
few things to it to get metadata and filtering support. Sounds like ec2
stuff
On 05/02/2012 11:24 PM, Michael Still wrote:
Hi.
I'd be interested in hearing from people who have implemented some form
of replication with glance. I'm especially interested in how you went
about it. I attended the session at the dev summit, but that was forward
looking, and I am pretty sure
On 04/05/12 04:07, Brian Waldon wrote:
I think the path forward is first to gather information on what
people are already doing w.r.t. replication, which you have helped
trigger with this email. I'm definitely interested in seeing your
solution. Once we get this information out in the open, we
Current warts:
...
- maintaining amazon ec2 ids across regions requires twiddling the
nova database where this mapping is stored
Hi Mikal,
We discussed that nova s3_images table earlier in the week on IRC.
Now at the time, I wasn't fully clear on the mechanics of the glance
UUID -
Current warts:
...
- maintaining amazon ec2 ids across regions requires twiddling the
nova database where this mapping is stored
Hi Mikal,
We discussed that nova s3_images table earlier in the week on IRC.
Now at the time, I wasn't fully clear on the mechanics of the glance
I think the path forward is first to gather information on what people are
already doing w.r.t. replication, which you have helped trigger with this
email. I'm definitely interested in seeing your solution. Once we get this
information out in the open, we need to explore these existing
Hi.
I'd be interested in hearing from people who have implemented some form
of replication with glance. I'm especially interested in how you went
about it. I attended the session at the dev summit, but that was forward
looking, and I am pretty sure that there wasn't any mention of current
12 matches
Mail list logo
