Custom Query – GENI: exogeni

Results (1 - 3 of 138)

1 2 3 4 5 6 7 8 9 10 11 →

Ticket	Resolution	Summary	Owner	Reporter
#75	fixed	Ad RSpec: Typo in an interface	yxin@renci.org	ahelsing@bbn.com
Description	In the ExoSM Ad Node `urn:publicid:IDN+exogeni.net:bbnNet+node+orca-transit-net-vlan` 3rd interface appears to have a typo in the ID: `urn:publicid:IDN+exogeni.net:bbnNet+interface+bbnNet.rdf#BbnNet/BM/G8052/TenGigabitEthernet/1/2/ethernet` BM -> IBM
#11	fixed	define full reverse and forward zones for BBN rack's public IPs	vjo@duke.edu	chaos@bbn.com
Description	All public IP addresses in use by the BBN rack (non-gateway/broadcast addresses in the `192.1.242.0/25` subnet) should resolve in DNS to something reasonable. This doesn't need to be up-to-date per-experiment, but DNS should report at a glance whether a given IP address belongs to an infrastructure device (and which one), or whether it is reserved for OpenStack or bare metal experimental use.
#33	fixed	Private IPs assigned for iSCSI array should be in /etc/hosts	vjo@duke.edu	chaos@bbn.com
Description	Per Wednesday's call, the IP addresses which are used for the iSCSI array should be in `/etc/hosts` with `.iscsi` suffixes. That file contains: ## ## iSCSI - VLAN 1009 ## 10.102.0.1 bbn-hn.iscsi 10.102.0.11 bbn-w1.iscsi 10.102.0.12 bbn-w2.iscsi 10.102.0.13 bbn-w3.iscsi 10.102.0.14 bbn-w4.iscsi but does not contain the IP(s) for the interface(s) on the iSCSI itself. I think the iSCSI protocol in fact uses IP addresses on both ends, so there is an IP address on the iSCSI itself, and it should be recorded.

1 2 3 4 5 6 7 8 9 10 11 →