Opened 11 years ago
Last modified 11 years ago
#169 new
request of type "raw-pc" gives a VM
Reported by: | ahelsing@bbn.com | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | AM | Version: | SPIRAL5 |
Keywords: | Cc: | ||
Dependencies: |
Description
I requested, from the ExoSM, a node of sliver_type="raw-pc"
. I got a manifest saying the sliver type was m1.small
Change History (8)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
Now I get a manifest with a sliver type of "ExoGENI-M4". Shouldn't this remain "raw-pc" since that is what I asked for?
Additionally, should I be surprised that the disk_image I got for the raw PC is still exactly the same as it was for an m1.small VM?
... <node sliver_id="urn:publicid:IDN+exogeni.net:fiuvmsite+sliver+f2892d4f-f5e4-4858-bb32-917d83f82fde#baremetal" exclusive="true" component_name="orca-xcat-cloud" component_manager_id="urn:publicid:IDN+exogeni.net:fiuvmsite+authority+am" component_id="urn:publicid:IDN+exogeni.net:fiuvmsite+node+orca-xcat-cloud" client_id="baremetal"> <sliver_type name="ExoGENI-M4"> <disk_image version="ba15fa6f56cc00d354e505259b9cb3804e1bcb73" name="http://geni-images.renci.org/images/standard/debian/deb6-neuca-v1.0.7.xml"/> </sliver_type> <services/> <ns4:geni_sliver_info state="Ticketed" start_time="2013-04-11T08:51:54.015-04:00" expiration_time="2013-04-12T08:51:54.015-04:00" creation_time="2013-04-11T08:51:54.015-04:00" creator_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+ahelsing"/> </node> <ns3:geni_slice_info state="configuring" uuid="721e5dbb-f890-44fb-9dd5-008f097d02e6" urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+ahtest"/> ...
comment:3 Changed 11 years ago by
The actual hardware type we use is ExoGENI-m4, not raw-pc. Raw-pc is used for compatibility in the requests, but we want to be specific in the manifest, what it is you actually got.
The image thing is a bug, I will take a look.
comment:4 Changed 11 years ago by
The ExoGENI Resource Types information at the page https://wiki.exogeni.net/doku.php?id=public:experimenters:resource_types:start lists the supported compute resource types for experimenters. Up to now, this list has mapped to information that can be used in an RSpec. Should both "raw-pc" and "ExoGENI-M4" be listed to mimic the information that is available via the Advertisement RSpec?
comment:5 Changed 11 years ago by
Since there are two sliver types in the Advertisement RSpec for Dedicated Nodes:
<node component_id="urn:publicid:IDN+exogeni.net:bbnvmsite+node+orca-xcat-cloud" component_manager_id="urn:publicid:IDN+exogeni.net:b bnvmsite+authority+am" component_name="orca-xcat-cloud" exclusive="false"> <sliver_type name="raw-pc"/> <sliver_type name="ExoGENI-M4"/>
I tested an RSpec requesting 1 dedicated node and using both sliver_types. This is a valid request RSpec which passes rspeclint:
<node client_id="geni1"> <sliver_type name="ExoGENI-M4"/> <sliver_type name="raw-pc"/> </node>
Submitting the above request for one dedicated node at the ExoSM results into two VMs being allocated. Following is the sliver creation showing the manifest for the allocated sliver:
$ omni.py createsliver -a eg-sm ln1pcm4raw ./exo-1pc-raw-m4.rspec INFO:omni:Loading config file /home/lnevers/.gcf/omni_config INFO:omni:Using control framework pg INFO:omni:Substituting AM nickname eg-sm with URL https://geni.renci.org:11443/orca/xmlrpc, URN unspecified_AM_URN INFO:omni.protogeni:Detected busy result for Resolve PG slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+ln1pcm4raw at SA https://www.pgeni.gpolab.bbn.com:443/protogeni/xmlrpc/sa. Retrying in 10 seconds. INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+ln1pcm4raw expires on 2013-04-13 13:52:48 UTC INFO:omni:Substituting AM nickname eg-sm with URL https://geni.renci.org:11443/orca/xmlrpc, URN unspecified_AM_URN INFO:omni:Substituting AM nickname eg-sm with URL https://geni.renci.org:11443/orca/xmlrpc, URN unspecified_AM_URN INFO:omni:Creating sliver(s) from rspec file ./exo-1pc-raw-m4.rspec for slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+ln1pcm4raw INFO:omni:Got return from CreateSliver for slice ln1pcm4raw at https://geni.renci.org:11443/orca/xmlrpc: INFO:omni:<?xml version="1.0" encoding="UTF-8" standalone="yes"?> INFO:omni: <!-- Reserved resources for: Slice: ln1pcm4raw at AM: URN: unspecified_AM_URN URL: https://geni.renci.org:11443/orca/xmlrpc --> INFO:omni: <rspec type="manifest" xsi:schemaLocation="http://www.geni.net/resources/rspec/3 http://www.geni.net/resources/rspec/3/manifest.xsd http://hpn.east.isi.edu/rspec/ext/stitch/0.1/ http://hpn.east.isi.edu/rspec/ext/stitch/0.1/stitch-schema.xsd http://groups.geni.net/exogeni/attachment/wiki/RspecExtensions/slice-info/1 http://groups.geni.net/exogeni/attachment/wiki/RspecExtensions/slice-info/1/slice_info.xsd?format=raw http://groups.geni.net/exogeni/attachment/wiki/RspecExtensions/sliver-info/1 http://groups.geni.net/exogeni/attachment/wiki/RspecExtensions/sliver-info/1/sliver_info.xsd?format=raw" xmlns:ns2="http://hpn.east.isi.edu/rspec/ext/stitch/0.1/" xmlns="http://www.geni.net/resources/rspec/3" xmlns:ns4="http://groups.geni.net/exogeni/attachment/wiki/RspecExtensions/sliver-info/1" xmlns:ns3="http://groups.geni.net/exogeni/attachment/wiki/RspecExtensions/slice-info/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <node sliver_id="urn:publicid:IDN+exogeni.net:fiuvmsite+sliver+383a7fb2-11dc-4236-821a-a5d4f87f73d9#/dd9be3b4-f258-48ba-9a75-0eec9fc26cf4/MasterGroup" exclusive="true" component_name="orca-vm-cloud" component_manager_id="urn:publicid:IDN+exogeni.net:fiuvmsite+authority+am" component_id="urn:publicid:IDN+exogeni.net:fiuvmsite+node+orca-vm-cloud" client_id="/dd9be3b4-f258-48ba-9a75-0eec9fc26cf4/MasterGroup"> <sliver_type name="vm"/> <services/> <interface client_id="Fiu/ExoGeni/TengigabitEthernet/2/ethernet"/> <ns4:geni_sliver_info error="Reservation 53a320eb-b5a2-43bf-8976-03126901b025 (Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+ln1pcm4raw) is in state [Failed,None] Last ticket update: Insufficient resources for specified start time, Failing reservation:53a320eb-b5a2-43bf-8976-03126901b025 Ticket events Insufficient resources for specified start time, Failing reservation:53a320eb-b5a2-43bf-8976-03126901b025" destroyed="true" state="Failed" start_time="2013-04-12T12:53:10.541Z" expiration_time="2013-04-13T12:53:10.541Z" creation_time="2013-04-12T12:53:10.541Z" creator_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers"/> </node> <node sliver_id="urn:publicid:IDN+exogeni.net:bbnvmsite+sliver+383a7fb2-11dc-4236-821a-a5d4f87f73d9#/dd9be3b4-f258-48ba-9a75-0eec9fc26cf4/SlaveGroup" exclusive="true" component_name="orca-vm-cloud" component_manager_id="urn:publicid:IDN+exogeni.net:bbnvmsite+authority+am" component_id="urn:publicid:IDN+exogeni.net:bbnvmsite+node+orca-vm-cloud" client_id="/dd9be3b4-f258-48ba-9a75-0eec9fc26cf4/SlaveGroup"> <sliver_type name="vm"/> <services/> <interface client_id="Bbn/ExoGeni/TengigabitEthernet/2/ethernet"/> <ns4:geni_sliver_info state="Ticketed" start_time="2013-04-12T12:53:10.541Z" expiration_time="2013-04-13T12:53:10.541Z" creation_time="2013-04-12T12:53:10.541Z" creator_urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers"/> </node> <link vlantag="unknown" sliver_id="urn:publicid:IDN+exogeni.net+sliver+383a7fb2-11dc-4236-821a-a5d4f87f73d9#/dd9be3b4-f258-48ba-9a75-0eec9fc26cf4/Connection" client_id="/dd9be3b4-f258-48ba-9a75-0eec9fc26cf4/Connection"> <interface_ref client_id="Bbn/ExoGeni/TengigabitEthernet/2/ethernet"/> <interface_ref client_id="Fiu/ExoGeni/TengigabitEthernet/2/ethernet"/> </link> <ns2:stitching lastUpdateTime="Fri Apr 12 12:54:55 UTC 2013"> <ns2:path id="/dd9be3b4-f258-48ba-9a75-0eec9fc26cf4/Connection"> <ns2:hop type="strict" id="hop1"> <ns2:link id="bbnNet.rdf#bbnNet/Domain/vlan/3a0de601-86b2-43db-a412-aedb9cb05d57/vlan"> <ns2:remoteLinkId>unknown</ns2:remoteLinkId> <ns2:trafficEngineeringMetric>unknown</ns2:trafficEngineeringMetric> <ns2:capacity>10000000</ns2:capacity> <ns2:maximumReservableCapacity>10000000</ns2:maximumReservableCapacity> <ns2:minimumReservableCapacity>10000000</ns2:minimumReservableCapacity> <ns2:granularity>10000000</ns2:granularity> <ns2:unreservedCapacity>unknown</ns2:unreservedCapacity> <ns2:switchingCapabilityDescriptor> <ns2:switchingcapType>l2sc</ns2:switchingcapType> <ns2:encodingType>ethernet</ns2:encodingType> <ns2:switchingCapabilitySpecificInfo> <ns2:switchingCapabilitySpecificInfo_L2sc> <ns2:vlanRangeAvailability>2604</ns2:vlanRangeAvailability> </ns2:switchingCapabilitySpecificInfo_L2sc> </ns2:switchingCapabilitySpecificInfo> </ns2:switchingCapabilityDescriptor> </ns2:link> <ns2:nextHop>hop2</ns2:nextHop> </ns2:hop> <ns2:hop type="strict" id="hop2"> <ns2:link id="nlr.rdf#nlr/Domain/vlan/6cbd0607-2feb-43bd-9604-f861445fabe6/vlan"> <ns2:remoteLinkId>unknown</ns2:remoteLinkId> <ns2:trafficEngineeringMetric>unknown</ns2:trafficEngineeringMetric> <ns2:capacity>10000000</ns2:capacity> <ns2:maximumReservableCapacity>10000000</ns2:maximumReservableCapacity> <ns2:minimumReservableCapacity>10000000</ns2:minimumReservableCapacity> <ns2:granularity>10000000</ns2:granularity> <ns2:unreservedCapacity>unknown</ns2:unreservedCapacity> <ns2:switchingCapabilityDescriptor> <ns2:switchingcapType>l2sc</ns2:switchingcapType> <ns2:encodingType>ethernet</ns2:encodingType> <ns2:switchingCapabilitySpecificInfo> <ns2:switchingCapabilitySpecificInfo_L2sc> <ns2:vlanRangeAvailability>2604</ns2:vlanRangeAvailability> </ns2:switchingCapabilitySpecificInfo_L2sc> </ns2:switchingCapabilitySpecificInfo> </ns2:switchingCapabilityDescriptor> </ns2:link> <ns2:nextHop>hop3</ns2:nextHop> </ns2:hop> <ns2:hop type="strict" id="hop3"> <ns2:link id="fiuNet.rdf#fiuNet/Domain/vlan/2669704d-3ae9-4407-a2ef-ea4cc3c1622a/vlan"> <ns2:remoteLinkId>unknown</ns2:remoteLinkId> <ns2:trafficEngineeringMetric>unknown</ns2:trafficEngineeringMetric> <ns2:capacity>10000000</ns2:capacity> <ns2:maximumReservableCapacity>10000000</ns2:maximumReservableCapacity> <ns2:minimumReservableCapacity>10000000</ns2:minimumReservableCapacity> <ns2:granularity>10000000</ns2:granularity> <ns2:unreservedCapacity>unknown</ns2:unreservedCapacity> <ns2:switchingCapabilityDescriptor> <ns2:switchingcapType>l2sc</ns2:switchingcapType> <ns2:encodingType>ethernet</ns2:encodingType> <ns2:switchingCapabilitySpecificInfo> <ns2:switchingCapabilitySpecificInfo_L2sc> <ns2:vlanRangeAvailability>1764</ns2:vlanRangeAvailability> </ns2:switchingCapabilitySpecificInfo_L2sc> </ns2:switchingCapabilitySpecificInfo> </ns2:switchingCapabilityDescriptor> </ns2:link> <ns2:nextHop>null</ns2:nextHop> </ns2:hop> </ns2:path> </ns2:stitching> <ns3:geni_slice_info state="failed" uuid="3a96267b-c93c-4f5e-b80d-c7c6275510e7" urn="urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+ln1pcm4raw"/> </rspec> INFO:omni: ------------------------------------------------------------ INFO:omni: Completed createsliver: Options as run: aggregate: ['eg-sm'] framework: pg Args: createsliver ln1pcm4raw ./exo-1pc-raw-m4.rspec Result Summary: Got Reserved resources RSpec from geni-renci-org-11443-orca INFO:omni: ============================================================
comment:6 Changed 11 years ago by
This last one has nothing to do with multiple sliver types (which schema should not allow!) This is an embedding bug we saw before. It is fixed on trunk but not deployed.
comment:7 Changed 11 years ago by
This was us messing with ontology models posted on the web. ORCA imports them in order to process the requests and run inferences, and you must have caught it at just the right moment.
comment:8 Changed 11 years ago by
As far as the original purpose of the ticket - you can request raw-pc or exogeni-m4. You will get exogeni-m4. Raw-pc is used for compatibility. Its name is useless and delivers absolutely no information about what you are actually getting, so it is only useful in the request. Providing it in the manifest would be misleading.
Request RSpec:
Manifest returned: