Custom Query (138 matches)

Getting a listresources via the RENCI SM reports a failures:

$ omni.py -a eg-renci listresources -o
INFO:omni:Loading config file /home/lnevers/.gcf/omni_config
INFO:omni:Using control framework pg
INFO:omni:Substituting AM nickname eg-renci with URL https://rci-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Saving output to a file.
INFO:omni:Substituting AM nickname eg-renci with URL https://rci-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
WARNING:omni:No resource listing returned!
INFO:omni:Listed advertised resources at 0 out of 1 possible aggregates.
INFO:omni:Substituting AM nickname eg-renci with URL https://rci-hn.exogeni.net:11443/orca/xmlrpc, URN unspecified_AM_URN
WARNING:omni:No RSpec returned from rci-hn-exogeni-net-11443-orca
INFO:omni:Writing to 'rspec-rci-hn-exogeni-net-11443-orca.xml'
INFO:omni:<!-- Resources at AM:
	URN: unspecified_AM_URN
	URL: https://rci-hn.exogeni.net:11443/orca/xmlrpc
 -->
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed listresources:

  Options as run:
		aggregate: ['eg-renci']
		framework: pg
		output: True

  Args: listresources

  Result Summary: Queried resources from 0 of 1 aggregate(s).
Wrote rspecs from 1 aggregate(s) to 1 file(s)
Saved listresources RSpec at 'unspecified_AM_URN' (url 'https://rci-hn.exogeni.net:11443/orca/xmlrpc') to file rspec-rci-hn-exogeni-net-11443-orca.xml; No resources from AM https://rci-hn.exogeni.net:11443/orca/xmlrpc:  (Error from Aggregate: code 2: Error encountered converting NDL ads to RSpec via converter service: Unable to contact/use any of specified NDL-RSPEC converters at http://geni.renci.org:12080/ndl-conversion/,http://bbn-hn.exogeni.net:14080/ndl-conversion/.) 
INFO:omni: ============================================================

The switch hostnames "bbn-8052.bbn.xo" and "bbn-8264.bbn.xo" no longer resolve on the BBN head node:

[lnevers@bbn-hn opt]$ ssh bbn-8064.bbn.xo
ssh: Could not resolve hostname bbn-8064.bbn.xo: Name or service not known
[lnevers@bbn-hn opt]$ ssh bbn-8052.bbn.xo
ssh: Could not resolve hostname bbn-8052.bbn.xo: Name or service not known

While looking for instruction for Site Administrators, I was able to find some information at ​https://wiki.exogeni.net/doku.php?id=public:operators:start that lets the reader know the following:

Administrator accounts on racks are managed through a hierarchical LDAP deployment rooted at RENCI. Site administrators have rights to their rack, while ExoGENI Ops team has admin rights on all racks.

But there are no instruction for Site Admins for:

• What to do to get an administrative account
• Who to contact to request am account
• Administrative accounts policies.
• System access granted to Site Admins (head node, worker node, bare metal, switches)
• Type of access granted (public key ssh, https).