Shulou(Shulou.com)06/01 Report--

This article introduces the knowledge of "the use of the integration of openstack and cloudify". Many people will encounter such a dilemma in the operation of actual cases, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1. Generate keypairs in the dashboard of openstack, save the keypairs file (xxx.pem), and put the pem file in the / clouds/openstack/upload folder

two。 Modify the openstack-cloud.groovy and openstack-cloud.properties files under / clouds/openstack/.

3. Modify the wget JDK and cloudify.zip file commands in the / clouds/openstack/upload/bootstrap-management.sh script to download on the local server, http://my.oschina.net/chape/blog/121621

3. Since cloudify's openstack cloud driver has not been updated, I downloaded a foreigner's cloud driver jar package (cloudify-openstack-driver-1.2.jar) for openstack on github and put it on / lib/platform/esm

4. Run bootstarp-cloud openstack under cloudify shell

Openstack-cloud.groovy

Cloud {name = "openstack" configuration {className "org.cloudifysource.esc.driver.provisioning.jclouds.DefaultProvisioningDriver" managementMachineTemplate "SMALL_LINUX" connectToPrivateIp truebootstrapManagementOnPublicIp falsepersistentStoragePath persistencePath} provider {Context provider name.provider "openstack-nova" cloudifyUrl "http://repository.cloudifysource.org/org/cloudifysource/2.5.0-RC/gigaspaces-cloudify-2.5.0-rc-b3993"machineNamePrefix" cloudify-agent- "managementOnlyFiles ([]) sshLoggingLevel" WARNING "managementGroup" cloudify-manager "numberOfManagementMachines 1reservedMemoryCapacityPerMachineInMB 1024} user {user" ${tenant} : ${user} "apiKey apiKey} cloudCompute {templates ([SMALL_LINUX: computeTemplate {imageId linuxImageIdremoteDirectory" / home/root/gs-files "machineMemoryMB 1600hardwareId hardwareIdlocalDirectory" upload "keyFile keyFileusername" root "password" 123456 "options ([" securityGroupNames ": [securityGroup] as String []) "keyPairName": keyPair, "generateKeyPair": false, "autoAssignFloatingIp": true]) overrides (["jclouds.endpoint": openstackUrl]) / / enable sudo.privileged true}])} custom ([:])}

Openstack-cloud.properties

User= "admin" / / password= "keystoneadmin" tenant= "openstackDemo" keyFile= "paas.pem" keyPair= "paas" securityGroup= "default" / / For instance: "https://:5000/v2.0/"openstackUrl="http://10.10.4.47:5000/v2.0/"apiKey="keystoneadmin"hardwareId="RegionOne/2"//linuxImageId="RegionOne/dd9171e4-0941-412a-8067-5d2528ed303c"linuxImageId="RegionOne/283693e1-b288-4f3f-bca4-d6513f942e99"persistencePath=null

Bootstrap-management.sh

#! / bin/bash#### This script starts a Gigaspaces agent for use with the Gigaspaces# Cloudify. The agent will function as management depending on the value of $GSA_MODE## Parameters the should be exported beforehand:# $LUS_IP_ADDRESS-Ip of the head node that runs a LUS and ESM. May be my IP. (Required) # $GSA_MODE-'agent' if this node should join an already running node. Otherwise, any value.# $NO_WEB_SERVICES-'true' if web-services (rest, webui) should not be deployed (only if GSA_MODE! =' agent') # $MACHINE_IP_ADDRESS-The IP of this server (Useful if multiple NICs exist) # $WORKING_HOME_DIRECTORY-This is where the files were copied to (cloudify installation, etc..) # $GIGASPACES_LINK-If this url is found, it will be downloaded to $WORKING_HOME_DIRECTORY/gigaspaces.zip# $GIGASPACES_OVERRIDES_LINK-If this url is found It will be downloaded and unzipped into the same location as cloudify# $CLOUD_FILE-Location of the cloud configuration file. Only available in bootstrap of management machines.# $NO_WEB_SERVICES-If set to 'true', indicates that the rest and web-ui services should not be deployed in this machine.# $GIGASPACES_CLOUD_IMAGE_ID-If set, indicates the image ID for this machine.# $GIGASPACES_CLOUD_HARDWARE_ID-If set, indicates the hardware ID for this machine.# $PASSWORD-the machine password# $STORAGE_VOLUME_ATTACHED-if set to' true', storage volume will be mouted. Else all storage params will be null.# $STORAGE_FORMAT_TYPE-if set, indicates the file system type for formatting the volume before mount.# $STORAGE_MOUNT_PATH-if set, points to the path where the storage driver will be mounted.# $STORAGE_DEVICE_NAME-if set Indicated the storage device name.#### args:# $1 the error code of the last command (should be explicitly passed) # $2 the message to print in case of an error# # an error message is printed And the script exists with the provided error codefunction error_exit {echo "$2: error code: $1" exit ${1}} # args:# $1 the error code of the last command (should be explicitly passed) # $2 the message to print in case of an error # $3 the threshold to exit on## if (last_error_code [$1]) > = (threshold [$3]) the provided message [$2] is printed and the script# exists with the provided error code ($1) function error_exit_on_ Level {if [${1}-ge ${3}] Then error_exit ${1} ${2} fi} echo Checking script pathSCRIPT= `readlink-f $0`SCRIPTPATH = `dirname $script `echo script path is $SCRIPTPATHif [- f ${SCRIPTPATH} / cloudify_env.sh]; then ENV_FILE_PATH=$ {SCRIPTPATH} / cloudify_env.shelse if [- f ${SCRIPTPATH} /. / cloudify_env.sh] Then ENV_FILE_PATH=$ {SCRIPTPATH} /.. / cloudify_env.sh else echo Cloudify environment file not found! Bootstrapping cannot proceed! Exit 105fifisource ${ENV_FILE_PATH} if ["$STORAGE_VOLUME_ATTACHED" = "true"]; then echo Formatting storage volume with fs type ${STORAGE_FORMAT_TYPE} and device name ${STORAGE_DEVICE_NAME} sudo mkfs-t $STORAGE_FORMAT_TYPE $STORAGE_DEVICE_NAME | | error_exit $? "Failed formatting storage volume" echo Mounting storage volume on path ${STORAGE_MOUNT_PATH} mkdir-p / $STORAGE_MOUNT_PATH sudo mount $STORAGE_DEVICE_NAME ~ / $STORAGE_MOUNT_PATH | | error_exit $? "Failed mounting storage volume" USERNAME= `whoami` sudo chown $USERNAME storage/ fiJAVA_32_URL= "http://repository.cloudifysource.org/com/oracle/java/1.6.0_32/jdk-6u32-linux-i586.bin"#JAVA_32_URL="http://10.10.4.12:8080/GG/jdk-6u43-linux-i586.bin"JAVA_64_URL="http://repository.cloudifysource.org/com/oracle/java/1.6.0_ 32/jdk-6u32-linux-x64.bin "# If not JDK specified Determine which JDK to install based on hardware architectureif [- z "$GIGASPACES_AGENT_ENV_JAVA_URL"] Then ARCH= `uname-m`echo Machine Architecture-- $ARCH if ["$ARCH" = "i686"]; then export GIGASPACES_AGENT_ENV_JAVA_URL=$JAVA_32_URL elif ["$ARCH" = "x86y64"] Then export GIGASPACES_AGENT_ENV_JAVA_URL=$JAVA_64_URL else echo Unknown architecture-- $ARCH-- defaulting to 32 bit JDK export GIGASPACES_AGENT_ENV_JAVA_URL=$JAVA_32_URL fi fi if ["$GIGASPACES_AGENT_ENV_JAVA_URL" = "NO_INSTALL"] Then echo "JDK will not be installed" else echo Previous JAVA_HOME value-$JAVA_HOME export GIGASPACES_ORIGINAL_JAVA_HOME=$JAVA_HOME yum install wget-y echo Downloading JDK from $GIGASPACES_AGENT_ENV_JAVA_URL wget-4-Q-O $WORKING_HOME_DIRECTORY/java.bin $GIGASPACES_AGENT_ENV_JAVA_URL | | error_exit $? "Failed downloading Java installation from $GIGASPACES_AGENT_ENV_JAVA_URL" # scp $GIGASPACES_AGENT_ENV_JAVA_URL root@192.168.100.4:$WORKING_HOME_DIRECTORY/java.bin | | error_exit $? "Failed downloading Java installation from $GIGASPACES_AGENT_ENV_JAVA_URL" chmod + x $WORKING_HOME_DIRECTORY/java.bin echo-e "\ n" > $WORKING_HOME_DIRECTORY/input.txt rm-rf ~ / java | | error_exit $? "Failed removing old java installation directory" mkdir ~ / java cd ~ / java echo Installing JDK $WORKING_HOME_DIRECTORY/java.bin

/ dev/null mv ~ / java/*/* ~ / java | | error_exit $? "Failed moving JDK installation" rm-f $WORKING_HOME_DIRECTORY/input.txt export JAVA_HOME=~/javafi export EXT_JAVA_OPTIONS= "- Dcom.gs.multicast.enabled=false" if [!-z "$GIGASPACES_LINK"]; then echo Downloading cloudify installation from $GIGASPACES_LINK.tar.gz wget-Q $GIGASPACES_LINK.tar.gz-O $WORKING_HOME_DIRECTORY/gigaspaces.tar.gz | | error_exit $? "Failed downloading cloudify installation" fiif [!-z "$GIGASPACES_OVERRIDES_LINK"]; then echo Downloading cloudify overrides from $GIGASPACES_OVERRIDES_LINK.tar.gz wget-Q $GIGASPACES_OVERRIDES_LINK.tar.gz-O $WORKING_HOME_DIRECTORY/gigaspaces_overrides.tar.gz | | error_exit $? "Failed downloading cloudify overrides" fi# Todo: Check this conditionif [!-d "~ / gigaspaces"-o $WORKING_HOME_DIRECTORY/gigaspaces.tar.gz-nt ~ / gigaspaces]; then rm-rf ~ / gigaspaces | | error_exit $? "Failed removing old gigaspaces directory" mkdir ~ / gigaspaces | | error_exit $? "Failed creating gigaspaces directory" # 2 is the error level threshold. 1 means only warnings # this is needed for testing purposes on zip files created on the windows platform tar xfz $WORKING_HOME_DIRECTORY/gigaspaces.tar.gz-C ~ / gigaspaces | | error_exit_on_level $? "Failed extracting cloudify installation" 2 # Todo: consider removing this line chmod-R 777 ~ / gigaspaces | | error_exit $? "Failed changing permissions in cloudify installion" mv ~ / gigaspaces/*/* ~ / gigaspaces | | error_exit $? "Failed moving cloudify installation" if [!-z "$GIGASPACES_OVERRIDES_LINK"]; then echo Copying overrides into cloudify distribution tar xfz $WORKING_HOME_DIRECTORY/gigaspaces_overrides.tar.gz-C ~ / gigaspaces | | error_exit_on_level $? "Failed extracting cloudify overrides" 2 fifi# if an overrides directory exists, copy it into the cloudify distributionif [- d $WORKING_HOME_DIRECTORY/cloudify-overrides]; then cp-rf $WORKING_HOME_DIRECTORY/cloudify-overrides/* ~ / gigaspacesfi# UPDATE SETENV SCRIPT...echo Updating environment scriptcd ~ / gigaspaces/bin | | error_exit $? "Failed changing directory to bin directory" sed-I "1i source ${ENV_FILE_PATH}" setenv.sh | | error_exit $? "Failed updating setenv.sh" sed-I "1i export NIC_ADDR=$MACHINE_IP_ADDRESS" setenv.sh | | error_exit $? "Failed updating setenv.sh" sed-I "1i export LOOKUPLOCATORS=$LUS_IP_ADDRESS" setenv.sh | | error_exit $? "Failed updating setenv.sh" sed-I "1i export PATH=$JAVA_HOME/bin:$PATH" setenv.sh | | error_exit $? "Failed updating setenv.sh" sed-I "1i export JAVA_HOME=$JAVA_HOME" setenv.sh | | error_exit $? "Failed updating setenv.sh" # START AGENT ALONE OR WITH MANAGEMENTif [- f nohup.out]; then rm nohup.outfiif [- f nohup.out]; then error_exit 1 "Failed to remove nohup.out Probably used by another process" fi# Privileged mode handlingif ["$GIGASPACES_AGENT_ENV_PRIVILEGED" = "true"]; then # First check if sudo is allowed for current session export GIGASPACES_USER= `whoami`if ["$GIGASPACES_USER" = "root"] Then # root is privileged by definition echo Running as root else sudo-n ls > / dev/null | | error_exit_on_level $? "Current user is not a sudoer, or requires a password for sudo" 1 fi # now modify sudoers configuration to allow execution without tty grep-I ubuntu / proc/version > / dev/null if ["$?"-eq "0"] Then # ubuntu echo Running on Ubuntu if sudo grep-Q-E'[^!] requiretty' / etc/sudoers Then echo creating sudoers user file echo "Defaults: `whoami`! requiretty" | sudo tee / etc/sudoers.d/ `whoami` > / dev/null sudo chmod 0440 / etc/sudoers.d/ `whoami`else echo No requiretty directive found Nothing to do fi else # other-modify sudoers file if [!-f "/ etc/sudoers"] Then error_exit 101" Could not find sudoers file at expected location (/ etc/sudoers) "fi echo Setting privileged mode sudo sed-I's / ^ defaults. * requiretty/#&/g' / etc/sudoers | | error_exit_on_level $? "Failed to edit sudoers file to disable requiretty directive" 1 fifi# Execute per-template commandif [!-z "$GIGASPACES_AGENT_ENV_INIT_COMMAND"]; then echo Executing initialization command cd $WORKING_HOME_DIRECTORY $GIGASPACES_AGENT_ENV_INIT_COMMANDficd ~ / gigaspaces/tools/cli | | error_exit $? "Failed changing directory to cli directory" START_COMMAND_ARGS= "- timeout 30-- verbose-auto-shutdown" if ["$GSA_MODE" = "agent"] Then ERRMSG= "Failed starting agent" START_COMMAND= "start-agent" else ERRMSG= "Failed starting management services" START_COMMAND= "start-management" START_COMMAND_ARGS= "${START_COMMAND_ARGS}-cloud-file ${CLOUD_FILE}" if ["$NO_WEB_SERVICES" = "true"] That's all for then START_COMMAND_ARGS= "${START_COMMAND_ARGS}-no-web-services-no-management-space" fifi nohup. / cloudify.sh $START_COMMAND $START_COMMAND_ARGS RETVAL=$?echo cat nohup.outcat nohup.outif [$RETVAL-ne 0]; then error_exit $RETVAL $ERRMSGfiexit 0 "the use of openstack and cloudify Integration". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.