Identifying ExoGENI software

[jbs@bbn.com]

I'm working on EG-MON-1 Step 1 (​http://groups.geni.net/geni/wiki/GENIRacksHome/AcceptanceTests/ExogeniAcceptandceTestsPlan#EG-MON-1:ControlNetworkSoftwareandVLANInspectionTest), and identified various files that are part of programs that are listening on the network, but aren't part of RPM packages. How would a site admin find out where those files came from, e.g. if they wanted to review the code?

[jbs@bbn.com]

So, /omd/sites/rack_bbn/var/tmp/xinetd, which appears to be a copy of /usr/sbin/xinetd -- is that as expected? As to the others, the relevant part of the acceptance test procedure says:

A site administrator enumerates processes on each of the head node and an OpenStack? worker node which listen for network connections from other nodes, identifies what version of what software package is in use for each, and verifies that we know the source of each piece of software and could get access to its source code.

So, if a site admin wanted to find out that information about those six things, how would they go about doing it?

[ibaldin@renci.org]

​https://wiki.exogeni.net/doku.php?id=private:orca:deployment

​https://wiki.exogeni.net/doku.php?id=public:software:aux_infrastructure:start

​https://wiki.exogeni.net/doku.php?id=private:openflow:start

[jbs@bbn.com]

The first and last of those three are private pages; should I be able to see those?

[ibaldin@renci.org]

Yes if you login.

[jbs@bbn.com]

Aha, ok. RENCI LDAP credentials? (Which other site admins will have too?)

(Just being cautious because I don't want to send that password to a host that shouldn't have it.)

[ibaldin@renci.org]

ExoGENI LDAP credentials, yes. All site admins will have those.

[jbs@bbn.com]

Ok. Lemme cycle back to this next week, so y'all can focus on your deployment for now.

[lnevers@bbn.com]

Replying to ibaldin@renci.org:

​https://wiki.exogeni.net/doku.php?id=private:orca:deployment

​https://wiki.exogeni.net/doku.php?id=public:software:aux_infrastructure:start

​https://wiki.exogeni.net/doku.php?id=private:openflow:start

Using LDAP credentials to reviewed both public and private pages listed above and here are some updates:

1. Both private pages do not exist:
   • ​https://wiki.exogeni.net/doku.php?id=private:orca:deployment
   • ​https://wiki.exogeni.net/doku.php?id=private:openflow:start

2. Public page ​https://wiki.exogeni.net/doku.php?id=public:software:aux_infrastructure:start provides a list of "auxiliary infrastructure elements" which includes:
   • ImageProxy
   • Orca Actor Registry
   • NDL-OWL/RSpec Conversion service

The aux_infrastructure page also points to ORCA Actors at ​https://wiki.exogeni.net/doku.php?id=public:software:start which gives insight into other software components including:

• FOAM ("version": "0.8.2")
• Shorewall DNAT Proxy
• FlowVisor (FV version=flowvisor-0.8.1::1)
• ORCA AM (not the GENI AM!)
• Local and Global Brokers
• EC2
• xCAT
• Eucalyptus
• OpenStack
• Apache Tomcat (version 7.0.22)

[vjo@duke.edu]

Has this received an adequate response, or does this ticket require further action?

[jbs@bbn.com]

I re-ran EG-MON-1 Step 1 just now, with results at ​http://groups.geni.net/geni/wiki/GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-MON-1#ResultsofStep1from2012-12-18. Search down for "here are the files that aren't from an RPM" and you'll find a list of files that aren't part of RPMs.

I can't easily tell from Luisa's recent update whether she thinks that a site admin could easily tell where each of those files came from. I couldn't at a glance, although it's possible I could track them down with more research.

Luisa, what do you think? Is the existing documentation adequate here, or is more needed?