registry team mailing list archive

[Joshua McKenty <jmckenty@xxxxxxxxx>]

As long as we keep in mind that we want to support multiple image
stores, and fall back to a more pathetic transfer method if needed.

Also that we'll be transferring OVF files (which could be bittorrent
packed).

I'm still inclined to favor multicast over bittorrent, at least when the
image store is on the LAN.

Sent from my iPhone

On 2010-07-22, at 7:53 PM, justinsb <608988@xxxxxxxxxxxxxxxxxx> wrote:

> I'm thinking a good way to do this might be by defining a better image
> format and transfer process.  For example, if we used the BitTorrent
> format (though not necessarily the protocol) then we need only check
> each block as it is transferred / written.  We can then cache images and
> image fragments efficiently on the compute machines if we want to, we
> get de-dup across images (though in practice this is unlikely to work
> very well unless the images are derived from each other), and empty
> areas should auto-compress to zero quickly.  S3 supports BitTorrent, so
> maybe Swift will one day also, but even without this the file format (or
> the concept of splitting the file into hashed chunks) is still useful...
> 
> This could also be very interesting for backup purposes...
> 
> -- 
> checksum images before booting
> https://bugs.launchpad.net/bugs/608988
> You received this bug notification because you are a member of Nova
> Bugs, which is subscribed to OpenStack Compute (nova).
> 
> Status in OpenStack Compute (Nova): New
> 
> Bug description:
> Make sure images are transfered cleanly before booting them.
> 
>

-- 
checksum images before booting
https://bugs.launchpad.net/bugs/608988
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack.