Skip to content. | Skip to navigation

Personal tools

Navigation

You are here: Home / Wiki / Kb162

Kb162

Emulab FAQ: Testbed Operations: What are the primary issues that students should be aware of?

Emulab FAQ: Testbed Operations: What are the primary issues that students should be aware of?

  • That they should be extremely careful of leaving idle experiment swapped in. Trying to fool the idle detection mechanism is a big no-no and bound to get student accounts frozen.
  • Students should read through the tutorial first, and start with a simple two node experiment to get the hang of things. Obviously, they are encouraged to read the FAQ as well.
  • Questions should first be directed to you, and then questions you cannot answer should be directed to us. Use the project and group email lists as well (e.g. SE17-654-users@emulab.net, subgroup-name@emulab.net, ...).
> I will be creating group areas for each student team (5 of them) to put
> their work under the project, is that the best way to control their
> projects?

Yep, although read the groups document; if you want to isolate them from each other, they should have "user" permission in the project and local root in the subgroup.

> What tools are available for development by the students and how would
> they most easily activate their applications?

That is entirely up to you and the students. The tutorial explains how to create custom disk images, so that might be useful if you want to create a baseline image that includes software for students to use in their experiments.

> If they plan to use CORBA, or J2EE type developments, again what should
> they be aware of in the Emulab environment?

The main issue for students is understanding the control network. Your experiments and software needs to be careful of accidentally sending traffic over the control network instead of your internal networks. See this tutorial entry. Hope this helps; good luck!