pyjuju

cobbler system names can change

Bug #817735 reported by William Reade
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyjuju
Fix Released
Undecided
William Reade
pyjuju dublin

Bug Description

We really want to be able to identify systems uniquely and persistently, and mutable names aren't good enough for that. Cobbler objects do have internal uids, which appear to be immutable, and we should use those to identify them instead.

Related branches

lp://staging/~fwereade/pyjuju/cobbler-instance-ids
Kapil Thangavelu (community): Approve
Gustavo Niemeyer: Approve
Diff: 113 lines (+23/-15)
3 files modified
ensemble/providers/orchestra/cobbler.py (+11/-9)
ensemble/providers/orchestra/launch.py (+4/-4)
ensemble/providers/orchestra/tests/test_bootstrap.py (+8/-2)
William Reade (fwereade)
Changed in ensemble:
status: New → In Progress
assignee: nobody → William Reade (fwereade)
milestone: none → dublin
Revision history for this message
Scott Moser (smoser) wrote :

"Cobbler objects do have internal uids, which appear to be immutable, and we should use those to identify them instead."

That does not sound right to me. Generalize it:
 - <thing> has internal uid
 - <external thing> should use <thing>'s internal uids

Revision history for this message
William Reade (fwereade) wrote :

Well, it's a bit more like:

- <thing> has internal uid, and no other persistent identifier
- <external thing> needs to reliably identfy <thing>s
- <external thing> should use <thing>'s internal uids

...and I probably shouldn't have used the word "internal". This is actually the intended use of a cobbler UID; see:

http://<email address hidden>/msg01577.html

William Reade (fwereade)
Changed in ensemble:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.