<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-09-05 16:04 GMT+02:00 Andrew J. Hobbs <span dir="ltr"><<a href="mailto:ajhobbs@desu.edu" target="_blank">ajhobbs@desu.edu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Are you referring to unique tags within a vdi name, or over the entire cluster? </blockquote><div><br></div><div>vdi name<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I've never attempted to use repeated tags inside a vdi, but I do use date derived tags across the cluster. Requiring unique tags within a single vdi name would make sense to me, but I'd hate to lose the ability to use dated tags.<br></blockquote><div><br></div><div>I also use dated for tag in the format year,month,day,hour,minute,second so there's no possibility to duplicate a tag.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
While we're on the subject, requiring the tag not to start with a number seems a bit restrictive. I'd be happier if I could tag it with '201409051004' for example..<br></blockquote><div><br></div><div>I think it's very important to distinguish a tag from an id (number).<br></div><div>Just add a single letter.<br></div><div>It's easy to strip it away in scripts.<br></div><div>E.g. s201409060801<br><br></div><div>Valerio.<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
On 09/04/2014 08:34 AM, Valerio Pachera wrote:<br>
<br>
<br>
<br>
2014-09-04 12:42 GMT+02:00 Ruoyu <<a href="mailto:liangry@ucweb.com">liangry@ucweb.com</a><mailto:<a href="mailto:liangry@ucweb.com">liangry@ucweb.com</a>>>:<br>
<div class="HOEnZb"><div class="h5"><br>
In your opinion, duplicated tag name should be forbidden once user tries to create a snapshot for the vdi?<br>
If yes, it is not difficult. I will take care of it.<br>
<br>
<br>
Because we can refer to a snapshot by id and by tag, I think tag has to be unique as the id.<br>
I guess sheepdog in its internal operation uses only the snapshot id but, situations like the one below, make me wonder what's going to happen till I tried it first.<br>
<br>
dog vdi list<br>
Name Id Size Used Shared Creation time VDI id Copies Tag<br>
s test 1 1.0 GB 1.0 GB 0.0 MB 2014-09-04 14:19 7c2b25 2 xxx<br>
s test 2 1.0 GB 0.0 MB 1.0 GB 2014-09-04 14:19 7c2b26 2 xxx<br>
s test 3 1.0 GB 0.0 MB 1.0 GB 2014-09-04 14:19 7c2b27 2 xxx<br>
s test 4 1.0 GB 0.0 MB 1.0 GB 2014-09-04 14:19 7c2b28 2 xxx<br>
s test 5 1.0 GB 0.0 MB 1.0 GB 2014-09-04 14:19 7c2b29 2 xxx<br>
test 0 1.0 GB 0.0 MB 1.0 GB 2014-09-04 14:19 7c2b2a 2<br>
<br>
dog vdi delete -s xxx test<br>
<br>
dog vdi list<br>
Name Id Size Used Shared Creation time VDI id Copies Tag<br>
s test 1 1.0 GB 1.0 GB 0.0 MB 2014-09-04 14:19 7c2b25 2 xxx<br>
s test 2 1.0 GB 0.0 MB 1.0 GB 2014-09-04 14:19 7c2b26 2 xxx<br>
s test 3 1.0 GB 0.0 MB 1.0 GB 2014-09-04 14:19 7c2b27 2 xxx<br>
s test 4 1.0 GB 0.0 MB 1.0 GB 2014-09-04 14:19 7c2b28 2 xxx<br>
test 0 1.0 GB 0.0 MB 1.0 GB 2014-09-04 14:19 7c2b2a 2<br>
<br>
Before patching, evaluate if there may be any impact in the cluster snapshot save:<br>
dog vdi snapshot -s xxx test<br>
dog cluster snapshot save tag1 path<br>
dog vdi delete -s 1 test<br>
# later on<br>
dog vdi snapshot -s xxx test<br>
dog cluster snapshot save tag2 path<br>
<br>
I this example, both cluster snapshots are storing the vdi with the same tag.<br>
<br>
<br>
<br>
<br>
<br>
</div></div><br>--<br>
sheepdog-users mailing lists<br>
<a href="mailto:sheepdog-users@lists.wpkg.org">sheepdog-users@lists.wpkg.org</a><br>
<a href="http://lists.wpkg.org/mailman/listinfo/sheepdog-users" target="_blank">http://lists.wpkg.org/mailman/listinfo/sheepdog-users</a><br>
<br></blockquote></div><br></div></div>