Skip to content

Conversation

@heliosfa
Copy link
Contributor

This PR splits the AddressBook from the Nameserver that was submitted as part of #103. Comments made during that PR are addressed, a series of tests (more to be added later) in the current testing framework are added and the AddressBook sources have been moved to a sub-directory of Nameserver.

This is not currently used by the Orchestrator, but is built and tested with make tests.

Two bits of preliminary documentation included:
AddressBookDocs.pdf
AddrBook.pdf

@heliosfa heliosfa added the feature New feature label Jan 13, 2020
@heliosfa heliosfa requested a review from mvousden January 13, 2020 15:31
@heliosfa heliosfa self-assigned this Jan 13, 2020
Copy link
Contributor

@mvousden mvousden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Points:

  • I like your documentation. I would add something about the notion of integrity to your documentation, since those checks are the most complicated section of this changeset, and it took me a while to figure out what was being checked when (and by what, in the case of the multithreaded implementation).

  • Code structure is consistent, which made it easy for me to find methods and names I was looking for.

  • I would welcome docstrings (in the source) for the methods that do not have them, though I grant you it is somewhat intuitive what the methods do at points.

  • Your documentation claims that int AddressBook::TaskCount exists when it doesn't. I agree that it shouldn' existt (you've got a method that simply queries the size of AddressBook::TaskMap, which is fine), but I wonder if there are other discrepancies I have not found.

  • Typo in AddressBookDocs.pdf: "Task Data structs (TaskData_t) represent a task without and of the fast access maps and vectors."

  • Could you put your documentation on the shared drive and commit it to the orchestrator-documentation repository when done?

Happy Mark, no 🍠 for you.

unsigned long Rank; // OR Supervisor's MPI Rank.
};
DTypeIdx DeviceType; // Index of the Device's type in task.
AttrIdx Attribute; // Index of the Device's attribute in task.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand this comment - what is a "Device's attribute"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A device can supposedly have a free-form attribute that can be stored - this facilitates that

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does that mean in the wider context of POETS?

@heliosfa heliosfa merged commit 04ba1af into development Jan 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature New feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants