Opened 12 years ago
Closed 12 years ago
#19 closed (fixed)
Creating slivers with Free BSD and Ubuntu images results in Fedora hosts being allocated
Reported by: | lnevers@bbn.com | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | IG-EXP-1 |
Component: | Experiment | Version: | SPIRAL4 |
Keywords: | image support | Cc: | |
Dependencies: |
Description
Created the following:
- 1 sliver named "ln0515" requesting 2 emulab-openvz nodes with FBSD82-STD images
- 1 sliver named "ln0515a" requesting 2 emulab-openvz nodes with UBUNTU11-64-STD images
Both slivers were created without problems, logged into each of the 4 hosts and found that all 4 hosts are actually running FEDORA15-STD hosts.
Attaching the rspec for each of the sliver, and the sliverstatus for each of the sliver which shows the requested OS where allocated.
Attachments (4)
Change History (8)
Changed 12 years ago by
Attachment: | insta-2vm-bsd82.rspec added |
---|
Changed 12 years ago by
Attachment: | insta-2vm-ubuntu11.rspec added |
---|
Changed 12 years ago by
Changed 12 years ago by
comment:1 Changed 12 years ago by
comment:2 follow-up: 3 Changed 12 years ago by
Using advertised Ubuntu or FreeBSD images is not supported for sliver_type emulab-openvz. This does not allow the execution of step 4 in the IG-EXP-2 InstaGENI Single Site test case, found at http://groups.geni.net/geni/wiki/GENIRacksHome/AcceptanceTests/InstageniAcceptanceTestsPlan#IG-EXP-2:InstaGENISingleSiteAcceptanceTest.
Two options available:
(a) Modify step 4 to assume default image is used (Fedora15).
(b) Modify step 4 to assume a raw-pc is used to load the custom image, which duplicates later step 12 in the procedure.
Choosing option (a) for the execution of step 4.
comment:3 Changed 12 years ago by
Replying to lnevers@bbn.com:
Using advertised Ubuntu or FreeBSD images is not supported for sliver_type emulab-openvz. This does not allow the execution of step 4 in the IG-EXP-2 InstaGENI Single Site test case, found at http://groups.geni.net/geni/wiki/GENIRacksHome/AcceptanceTests/InstageniAcceptanceTestsPlan#IG-EXP-2:InstaGENISingleSiteAcceptanceTest.
Two options available:
(a) Modify step 4 to assume default image is used (Fedora15).
(b) Modify step 4 to assume a raw-pc is used to load the custom image, which duplicates later step 12 in the procedure.
Choosing option (a) for the execution of step 4.
I'd say this is a good path of least resistance for your testing. We do expect that for now, a single shared IG node will only support one single OS/userspace, and in this case, AFAIK, the only openvz image that is supported in the IG racks is F15. We can imagine someone creating another image that is openvz based on another OS (i.e. an Ubuntu openvz image), in which case we would think of the containers on a node running that image as being Ubuntu containers, but I'd say that we don't want to get hung up on that for now.
comment:4 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Test case IG-EXP-2 step 4 is being modified to use Fedora 15 VM. Closing ticket.
On 5/16/12 10:27 AM, Leigh Stoller wrote:
If this is not a supported path, there is no indication of it. I was able to request the sliver without error. The sliver was created without error, and the sliverstatus shows the requested OS.
Should there be some indication of non-support in any of these steps?
Also, this combination is allowed within flack, so I assumed it was supported.