Opened 8 years ago

Closed 8 years ago

#27 closed task (fixed)

Common post-boot script

Reported by: johren@bbn.com Owned by: somebody
Priority: major Milestone: GEC18
Component: OMF Version: Sprint2
Keywords: Cc:
Dependencies:

Description

There are some differences in the GIMI post-boot scripts for ExoGENI and InstaGENI. Currently, we have two different post-boot scripts. This ticket is for investigating having one post-boot script that will work for both ExoGENI and InstaGENI. Perhaps this includes using some of Josh Smift's Dingbot functionality.

There currently is not an appropriate component for this item. I have assigned it to OMF for now.

Change History (3)

comment:1 Changed 8 years ago by johren@bbn.com

Milestone: GEC18

comment:2 Changed 8 years ago by johren@bbn.com

Version: BacklogSprint2

Divya has written a common postboot script and sent the information out to the GIMI list for feedback.

I have written and tested a common postboot script that runs GIMI on both InstaGENI and ExoGENI. It is based on Josh Smift's dingbot bash script. It is available here:

http://emmy9.casa.umass.edu/GEC-17/install_script_gimibot.tar.gz

I also attached the InstaGENI and ExoGENI 5 node topology RSpecs (the same which we used for GEC 17) here. They are also available on the GENI Portal as

1. GIMI_exogeni_common
2. GIMI_instageni_common

There are 3 shell scripts in install_script_gimibot.tar.gz
1. gimibot.sh - This checks if the node is InstaGENI or ExoGENI by checking for neuca services
2. postboot_script_exo.sh - This script is executed if the node is an ExoGENI node
3. postboot_script.sh - This scripts is executed if the node is an InstaGENI node

I would be happy to receive any questions/comments about the scripts.

comment:3 Changed 8 years ago by divyashri.bhat@gmail.com

Resolution: fixed
Status: newclosed

I tested the RSpec on the latest ExoGENI and it works fine.

Note: See TracTickets for help on using tickets.