August 25, 2014 aly
What is Jumpgate?

Jumpgate, an OpenStack community project, is a library that acts as a translation layer to convert an incoming OpenStack call to a different cloud provider's API call.

Teams from IBM and SoftLayer collaborated to support more of Jumpgate's functionality, increasing coverage of the standard OpenStack API for SoftLayer’s API. Supporting Neutron (network) is one of our focus items in the latest release.

New OpenStack Functionality Added to Jumpgate
August 21, 2014 jarteche

The SoftLayer platform lets you add dynamic data and scripts when you place your order. The scripts are executed after the machine is booted.

To place a script on a virtual server, the script must be available through a URL.

Note: For HTTP URLs, the script is injected in the server and manually executed. For HTTPS URLs, the script is injected and automatically executed.

In this article, we use https://x.x.x.x/ as the URL where the scripts are available and time.sh as the script. If you place the URL on the browser, the result should be:

#!/bin/bash
August 19, 2014 Isaac Karrer

Jumpgate is an OpenStack library that acts as an adapter to help cloud providers become OpenStack compliant. We have added additional endpoints to support the creation, deletion, listing, attachment, detachment, and type listing of volumes within SoftLayer using the OpenStack Cinder and Nova commands. Previously, you were limited to using the SoftLayer CLI tool to interact with SoftLayer resources. Now you can use Cinder and Nova CLI tools to consume SoftLayer resources.

Jumpgate supports these additional OpenStack Cinder and Nova endpoints:

August 1, 2014 matt.eldridge

In part six of this series we explored using fog-softlayer for managing your SoftLayer VLANs.

In this installment, we’ll cover creating and routing global IP addresses.

You can follow this link for details on what SoftLayer global IP addresses are and how they work.

July 31, 2014 matt.eldridge

In part five of this series, we explored using fog-softlayer for managing your SoftLayer key pairs.

In this blog, we'll look at creating and assigning VLANs for use with our virtual servers.

Network Examples

Note that SoftLayer uses the term VLAN. The Fog project tries to keep things provider-independent, so we'll be referring to them as networks.

These examples all assume you have ~/.fog, which contain the following:

 

July 30, 2014 matt.eldridge

In part four of this series, we explored using fog-softlayer for managing your SoftLayer tags.

In this post, we'll look at creating and assigning SSH key pairs for use with our compute instances.

Key Pair Examples

These examples all assume you have ~/.fog, which contains the following:

default:
  softlayer_username: example-username
  softlayer_api_key: 1a1a1a1a1a1a1a1a1a11a1a1a1a1a1a1a1a1a1 
July 25, 2014 matt.eldridge

This is Part 4 of a series, so to get the most out of it you may want to start at the beginning. This post explores using fog-softlayer to manage your SoftLayer DNS.

First however, to give credit where it's due, a thank you goes out to @fernandes. He sent in the initial pull request that adds this DNS support.

Configure

These examples all assume you have ~/.fog, which contains the following.

 

July 18, 2014 matt.eldridge

In part two of this series we explored using fog-softlayer to leverage fog, the cloud services library, for managing servers.

In this installment, we will cover several examples of using fog-softlayer to manage SoftLayer Object Storage.

Configure fog-softlayer for your account.

These examples assume you have ~/.fog which contains:

July 9, 2014 matt.eldridge

Very small things can make a very large difference. I learned the hard way that one difference between MySQL 5.1.68 and 5.1.70 is that 5.1.70 would spontaneously restart if one of my applications added too many new connections quickly.

Keeping all of the packages, their dependencies, and their patches locked down can be overwhelming. This has given rise to the fairly common use of the so-called "Golden Image." The idea is that you get a VM into a state where you know it will perform in a predictable manner and you snapshot it as an image you can create new VMs from.

July 1, 2014 matt.eldridge

In part one of this series we introduced a new ruby gem, fog-softlayer, which enables SoftLayer users to leverage fog, the Ruby cloud services library.

In this installment, we will walk users through getting started with fog, covering several examples of using fog-softlayer to manage servers using both VMs and bare metal cloud instances.