Custom Query (138 matches)

The ability is needed for individual admins to choose whether or not they want to receive e-mailed alerts from rack nagios installations to which they have access.

This doesn't need to be self-service ("ask RENCI to turn on the notification bit" is an acceptable implementation), but different users need to be able to choose different settings.

Created a sliver via ExoSM to request one VM from BBN rack and one VM from RENCI rack, which resulted in the following error:

$ ./src/omni.py -a exosm createsliver experiment1 ./exorspec/EG-EXP-4_exp1.rspec 
INFO:omni:Loading config file omni_config
INFO:omni:Using control framework pgeni
WARNING:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+experiment1 expires in <= 3 hours
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+experiment1 expires on 2012-05-23 20:28:37 UTC
INFO:omni:Substituting AM nickname exosm with URL https://geni.renci.org:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Substituting AM nickname exosm with URL https://geni.renci.org:11443/orca/xmlrpc, URN unspecified_AM_URN
INFO:omni:Creating sliver(s) from rspec file ./exorspec/EG-EXP-4_exp1.rspec for slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+experiment1
INFO:omni:Asked https://geni.renci.org:11443/orca/xmlrpc to reserve resources. Result:
INFO:omni:<!-- Reserved resources for:
	Slice: experiment1
	At AM:
	URL: https://geni.renci.org:11443/orca/xmlrpc
 -->
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed createsliver:

  Options as run:
		aggregate: exosm
		framework: pgeni
		native: True

  Args: createsliver experiment1 ./exorspec/EG-EXP-4_exp1.rspec

  Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+experiment1 expires in <= 3 hours on 2012-05-23 20:28:37 UTC
Asked https://geni.renci.org:11443/orca/xmlrpc to reserve resources. No manifest Rspec returned. ERROR: Exception encountered: java.lang.NullPointerException 
INFO:omni: ============================================================

Attaching the RSpec used, which has been succesfully used in earlier testing.

From a login on bbn-hn, i see:

bbn-hn,[~],13:39(0)$ nslookup
> server
Default server: 152.54.1.66
Address: 152.54.1.66#53
Default server: 192.1.249.10
Address: 192.1.249.10#53
> 8052.bbn.xo
Server:         152.54.1.66
Address:        152.54.1.66#53

** server can't find 8052.bbn.xo: NXDOMAIN
> 8064.bbn.xo
Server:         152.54.1.66
Address:        152.54.1.66#53

** server can't find 8064.bbn.xo: NXDOMAIN
> 192.168.103.2
Server:         152.54.1.66
Address:        152.54.1.66#53

** server can't find 2.103.168.192.in-addr.arpa.: NXDOMAIN
> 192.168.103.4
Server:         152.54.1.66
Address:        152.54.1.66#53

** server can't find 4.103.168.192.in-addr.arpa.: NXDOMAIN
> 

Based on Wednesday's call, i believe the DNS server at 152.54.1.66 should be serving records for things in bbn.xo (vlan 1006), so i think this is a bug.