March 11, 2015 bpotter

In my first two blog posts in this series, Part 1 and Part 2, I covered many general aspects of how to use the SoftLayer API effectively. In this post, we'll dive into how to order SoftLayer resources using the SoftLayer API.

February 13, 2015 bpotter

In my previous blog post, I covered how to navigate the SoftLayer Services website, and how to query the SoftLayer API efficiently. In this post, I'll cover additional aspects of using the SoftLayer API with the python client.

February 6, 2015 bpotter

So you want to code to the SoftLayer API, your language of choice is python (well done), and you’ve read the SoftLayer API Overview on the SLDN site. You've even read the article using the SoftLayer API from python, but it just felt like a tease.

January 2, 2015 cgallo

We added a new feature, a simple bind importer, to the python CLI client that allows users to easily import bind style DNS zones into the SoftLayer DNS system. Before diving into the caveats that come with dealing with a file format that seems to be more human readable than machine readable, let’s discuss how to use it.

~$ sl dns import 
usage: sl dns import <file> [—dryRun]
~$ sl dns import realtest.test 
October 30, 2014 amfred

One often overlooked but powerful feature of SoftLayer is the ability to run a provision script on any server you deploy. You can use the SoftLayer REST API or the Web-based order form:

Make your script available via HTTPS, and SoftLayer will automatically download it onto the new server and execute it for you. If a script fails, you will receive a notification email.

September 5, 2014 matt.eldridge

In part seven of this series we explored using fog-softlayer for managing your SoftLayer Global IP addresses.

In this installment, we'll look at using tags to bring order to the compute and network assets that we provisioned on SoftLayer.

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

:softlayer_username: example-username
:softlayer_api_key: 1a1a1a1a1a1a1a1a1a11a1a1a1a1a1a1a1a1a1 
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 as the script. If you place the URL on the browser, the result should be:

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.