Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vhd-meta.py #206

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

vhd-meta.py #206

wants to merge 3 commits into from

Conversation

germanop
Copy link
Contributor

When we moved to github we dropped many utilities just because they were
not packaged in the RPM.

vhd-meta.py is one of those utilities.

The commits should be kept (IMHO) separated for historical reasons.
The first one is the original one from Andrei they we dropped.

The second one is my improved version to work with LVHD SRs (the previous one
was meant only for file based SRs). It was already reviewed and ready to be committed but
after we moved, because the original was not there the patch was dropped.

The third one is an improved version from Keith to cope with nasty situations were the footers
were corrupted. I did not spend time reviewind the patch in full so there is room for improving
the commit message.

These 3 patches are the state of the art of this script. There many versions scattered throughout
tickets from customers. An old version has been discarded because it was supersed by the first
commit from Andrei (it was a first attempt from Andrei to support a customer but then he refined
the patch).
Another version is not included because it was a hybrid: it had the second commit on top of a very
old version (see above).

So, these 3 patches together are exhaustive.

andreil and others added 3 commits August 11, 2014 19:21
This script is useful for getting problematic VHDs off of a customer site
without copying the entire VHD chain (which could be many GBs) or taking
customer's sensitive data: the script copies only the metadata and recreates
the VHD chain locally by adding zeros in place of data.

Signed-off-by: Andrei Lifchits <andrei.lifchits@citrix.com>
Signed-off-by: Germano Percossi <germano.percossi@citrix.com>
VHD BAT size on LVM is kept at its maximum on purpose, to allow
future resizes without moving data around.
The modification takes this into account

Signed-off-by: Germano Percossi <germano.percossi@citrix.com>
Reviewed-by: Vineeth Thampi Raveendran <vineeth.thampi@citrix.com>
A better description to be done..

Signed-off-by: Keith Petley <keith.petley@citrix.com>
Signed-off-by: Germano Percossi <germano.percossi@citrix.com>
@germanop
Copy link
Contributor Author

N.B: These pacthes won't be shipped in the RPM but we need a place to store them to have
a unique place to retrieve them from when giving assistance.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.0%) when pulling 87ca139 on germanop:vhd-meta into bce4501 on xapi-project:master.

@matelakat
Copy link
Contributor

I guess it's just an "import", so I don't think we need any review at this point, Let's merge it!

@germanop
Copy link
Contributor Author

It is not an import.
The third commit for sure has never been reviewed even if we know it works

@BobBall
Copy link
Contributor

BobBall commented Jul 2, 2015

Just a note for improvement... The script appears to assume that each VDI has the same BAT size. Rackspace had to modify it to extract the metadata.

@germanop
Copy link
Contributor Author

germanop commented Jul 2, 2015

In out case the BAT is always the same.

If they want to send the patch over, we can include it here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants