1 / 21

OpenAFS ’ Road to IPv6

OpenAFS ’ Road to IPv6. Andrew Deason Sine Nomine Associates European AFS & Kerberos Conference 2014. It’s not as hard as it sounds!. Trimming down tasks. Varying levels of “need to do” Debug interfaces, optional features, … Varying levels of difficulty

diep
Download Presentation

OpenAFS ’ Road to IPv6

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OpenAFS’ Road to IPv6 Andrew Deason Sine Nomine AssociatesEuropean AFS & Kerberos Conference 2014

  2. It’s not as hard as it sounds!

  3. Trimming down tasks • Varying levels of “need to do” • Debug interfaces, optional features, … • Varying levels of difficulty • Design vs “just replace v4 addr with v6” • Varying levels of stability • Standards vs internal

  4. General plan • First, just focus on basic client and server, assume v4/v6 • Then, all of the “we can test” sites can test • Now we have momentum for everything else

  5. IPv6 Tasks ICMP errors Debug interfaces RXAFS_FlushCPS RXAFSCB_TMAY AFSVol_ admin RPCs Local configs UbikGetSyncSite VL_ admin RPCs Host ACLs VL_RegisterAddrs fs commands VL_GetAddrsU VLDB format Internal ubik RPCs XDR addr type sockaddr

  6. “Less necessary” Tasks • Only do what we need for a client to access files in AFS • Some obviously optional • AFSCB_TMAY, just get rid of addresses • Some helpful, but not required

  7. IPv6 Tasks (less necessary) ICMP errors Debug interfaces RXAFS_FlushCPS RXAFSCB_TMAY AFSVol_ admin RPCs Local configs UbikGetSyncSite VL_ admin RPCs Host ACLs VL_RegisterAddrs fs commands VL_GetAddrsU VLDB format Internal ubik RPCs XDR addr type sockaddr

  8. “v4/v6 servers” • Assume all servers have at least one ipv4 address • Simplifies many administrative RPCs • “okay” for existing sites, maybe not for new sites

  9. IPv6 Tasks (v4/v6 servers) ICMP errors Debug interfaces RXAFS_FlushCPS RXAFSCB_TMAY AFSVol_ admin RPCs Local configs UbikGetSyncSite VL_ admin RPCs Host ACLs VL_RegisterAddrs fs commands VL_GetAddrsU VLDB format Internal ubik RPCs XDR addr type sockaddr

  10. IPv6 Tasks (easy/consensus) ICMP errors Debug interfaces RXAFS_FlushCPS RXAFSCB_TMAY AFSVol_ admin RPCs Local configs UbikGetSyncSite VL_ admin RPCs Host ACLs VL_RegisterAddrs fs commands VL_GetAddrsU VLDB format Internal ubik RPCs XDR sockaddr sockaddr

  11. IPv6 Tasks (no standards) ICMP errors Debug interfaces RXAFS_FlushCPS RXAFSCB_TMAY AFSVol_ admin RPCs Local configs UbikGetSyncSite VL_ admin RPCs Host ACLs VL_RegisterAddrs fs commands VL_GetAddrsU VLDB format Internal ubik RPCs XDR sockaddr sockaddr

  12. IPv6 Tasks • “Easy” doesn’t mean “trivial” • Many tasks have at least 3 solutions: • The “wrong” way (kluges) • The “right” way • The practical way (middle ground)

  13. RPCs • Prereq: ext-union • draft-keiser-afs3-xdr-union-06 • General agreement, but needs implementation

  14. RPCs • XDR sockaddr • Wrong: opaque[16] • Right: nested ext-union • Practical: ext-union • RPCs • Wrong: opaque[16] • Right: special vector types • Practical: arrays of the XDR sockaddr

  15. sockaddr • Wrong: 128-bit storage • Right/Practical: sockaddr or new struct • Usually “easy” but tedious • Tedious • Tedious

  16. VLDB • Wrong: stuff v6 addrs in existing v4 • Right: completely new db • Practical: new address records in extent blocks

  17. Extent blocks vlentry vlentry extent block MH MH MH vlentry

  18. Extent blocks • Currently for MH (multi-homed) records • Unreferenced data is ignored • …as long as we VLCONTBLOCK • Anything at all can go in here

  19. Extent blocks • Add any new arbitrary data, and existing vlservers don’t break • Entire new db, broken up by 8k blocks • Speed not critical

  20. Extent blocks • What to put in them? XDR addrs • Or opaque[16]s if you want to be “wrong” • Maybe more extensible/arbitrary server data • One block per server

  21. Beyond • With that done, move on to v6-only • Debugging, may be useful during dev • rxdebug, maybe temporary solution • Optional features as needed

More Related