PI at a site wasn't able to view/update node info at their site because some nodes had a whitelist. Had to modify the whitelisting policy so that site members, and slice mememebrs on the whitelist can see whitelisted nodes.
A user downloaded and installed a myplc with a broken schema. User was advised to download another version.
Adding Nodes To A Site
When the guardog myplc was recently updated we lost functionality that allowed pi/tech's with multiple sites to choose which site to add a node to. This functionality was added again and checked into cvs.
Registration with PI role.
Old netflow log requests. What's in, what's out? How do we get this information for requests?
Bogus PI signups were the main problem this week, but users should not be able to sign up as a PI now. Also maybe we don't want to ask people to respond to pl_mom messages as this spawns a lot of support tickets.
Explaining the whitelisting feature of the current API was bothersome.
Mike and Andy were not aware that they were on support duty so David carried the load himself. Possibly someone should write a script to inform those on support each week that they're up.
There is clearly confusion being caused by users still thinking that they need separate BootCD and plnode.txt/floppy files, when they are using the Custom, all-in-one BootCD.
I have made some changes to the myplc/db-config that sends messages, and I will make a few other changes to the GUI to provide in-line hints about what to do or download. I think there may be other sources of information causing confusion.
Also, the bootmanager, should look on the BootCD itself first, and ignore any other node configuration files it finds... Or not?
1. Slice mailing list isn't working: The problem was due to a bug in the aliasing script. It is fixed, and in case of a future problem, take a look at /usr/bin/gen_aliases.py on golf. Reid also mentions this below.
Problem: Users not recieving emails sent to alias: email@example.com.
Solution: Bug fix in gen_aliases.py on mail server. Script was only emailing PIs of the slice. Updated script to email users as well. Discussed merging this into the API itself, no decision made. Thoughts?
Problem: Users unable to find up to date PCU suggestions for new site.
Solution: Infromed the User of a few different options. Updated PCU documentation is needed. Removal of current out of date suggestions is recomended.
Dominant issues or repeated problems and their causes, if known. Suggestions for solutions would also be nice.