www.collazo.ws » Code

Uploading to Rackspace Cloud Files with PHP

robert — Tue, 30 Aug 2011 20:50:25 +0000

Someone recently asked me if I knew of a web based uploader that returned the Akamai CDN URL of the file. I looked around and found this site but it wasn’t quite what was wanted. I decided to edit the code in the example from that site and came up with this.

First, you’ll need the PHP bindings for Rackspace Cloud Files. They can be found here. You’ll need to put the files cloudfiles.php, cloudfiles_http.php, and cloudfiles_exceptions.php in directory on your web server.

Next, save the following code as “index.html”:

“index.html”

xmlns="http://www.w3.org/1999/xhtml">
</span></span>Upload to Rackspace Cloud Files<span class="sc2"><span class="kw2">
http-equiv="Content-type" content="text/html;charset=UTF-8" />
action="upload.php" enctype="multipart/form-data" method="POST">
Username: name="username" type="text" /> />
Key: name="key" type="password" /> />
Container: name="container" type="text" /> />
File: name="upload" type="file" /> />
name="submit" type="submit" value="Upload To Rackspace!" />

After that is saved, create a new file called “upload.php” and save the following:

“upload.php”

// Turn on error reporting so we can see if there are any problems
error_reporting(E_ALL);
ini_set('display_errors', 1);
// include the API
require('cloudfiles.php');
// cloud info
$username = $_POST['username']; // username
$key = $_POST['key']; // api key
$container = $_POST['container']; // container name
ob_start();
// Print some information regarding who and where
echo "Username: $username
";
echo "Container: $container
";
$localfile = $_FILES['upload']['tmp_name'];
$filename = $_FILES['upload']['name'];
// Print some information about the file
echo "Local: $localfile
";
echo "File : $filename
";
ob_flush();
// Connect to Rackspace
$auth = new CF_Authentication($username, $key);
$auth->authenticate();
$conn = new CF_Connection($auth);
// Get the container we want to use
$container = $conn->create_container($container);
// store file information
ob_flush();
// upload file to Rackspace
$object = $container->create_object($filename);
$object->load_from_filename($localfile);
$uri = $container->make_public();
print "Your URL is: " . $object->public_uri();
ob_end_flush();
?>

The important part is on line 46 that contains “$object->public_uri();”. That is function in the API binding that returns the objects URL.

Using Rackspace DNSaaS with curl (part 1)

robert — Fri, 08 Jul 2011 20:35:02 +0000

With the release of Rackspace DNSaaS (blog post here), I thought I would put together some examples of using curl with the service. With this release, you now have programmatic access to DNS via the API where you can set TTLs, create and delete various record types, and create and delete domains.

Authentication

First, you’ll have to authenticate. To do this, you will need your API key and username.

$ curl -D – -H "X-Auth-Key: yourAPIKey" -H "X-Auth-User: yourUsername" https://auth.api.rackspacecloud.com/v1.0

You should receive the following response:

HTTP/1.1 204 No Content
Server: Apache/2.2.3 (Mosso Engineering)
X-Storage-Url: https://storage101.dfw1.clouddrive.com/v1/yourAccountHash
Content-Type: application/octet-stream
Date: Date and Time
X-Auth-Token: yourAuthToken
X-Storage-Token: yourStorageToken
X-Server-Management-Url: https://servers.api.rackspacecloud.com/v1.0/yourAccountNumber
Connection: Keep-Alive
X-CDN-Management-Url: https://cdn1.clouddrive.com/v1/yourAccountHash
Content-Length: 0

Listing Domain Information

To see a list of your current domains, run the following command. Don’t forget to replace your auth token and account number.

$ curl -X GET -H "X-Auth-Token: yourAuthToken" -H "Accept: application/xml" https://dns.api.rackspacecloud.com/v1.0/yourAccountNumber/domains

Your output will be XML formatted and look like:

To see the same thing formatted as JSON output, run the following:

$ curl -X GET -H "X-Auth-Token: yourAuthToken" -H "Accept: application/json" https://dns.api.rackspacecloud.com/v1.0/yourAccountNumber/domains

{
   "domains":[
      {
         "name":"collazo.ws",
         "id":1697941,
         "accountId":yourAccountNumber,
         "updated":"2011-06-28T04:18:17.000+0000",
         "created":"2009-12-11T01:01:26.000+0000"
      },
      {
         "name":"deployitron.com",
         "id":4062964,
         "accountId":yourAccountNumber,
         "updated":"2011-03-19T08:10:31.000+0000",
         "created":"2011-01-21T23:24:44.000+0000"
      }
   ],
   "totalEntries":2
}

To get details about a particular domain, you’ll enter the following:

$ curl -X GET -H "X-Auth-Token: yourAuthToken" -H "Accept: application/xml" https://dns.api.rackspacecloud.com/v1.0/yourAccountNumber/domains/4062964 # <- make sure you replace this with your domain ID

This will output the following in XML format:

To get the same thing JSON formatted:

$ curl -X GET -H "X-Auth-Token: yourAuthToken" -H "Accept: application/json" https://dns.api.rackspacecloud.com/v1.0/yourAccountNumber/domains/4062964

{
   "name":"deployitron.com",
   "id":4062964,
   "accountId":yourAccountNumber,
   "nameservers":[
      {
         "name":"ns.rackspace.com"
      },
      {
         "name":"ns1.rackspace.com"
      }
   ],
   "updated":"2011-03-19T08:10:31.000+0000",
   "ttl":3600,
   "recordsList":{
      "records":[
         {
            "name":"deployitron.com",
            "id":"A-1234567",
            "type":"A",
            "data":"174.143.174.233",
            "updated":"2011-01-22T11:28:10.000+0000",
            "ttl":3600,
            "created":"2011-01-22T11:28:10.000+0000"
         },
         {
            "name":"deployitron.com",
            "id":"NS-2345678",
            "type":"NS",
            "data":"dns1.stabletransit.com",
            "updated":"2011-01-21T23:24:44.000+0000",
            "ttl":3600,
            "created":"2011-01-21T23:24:44.000+0000"
         },
         {
            "name":"deployitron.com",
            "id":"NS-2345680",
            "type":"NS",
            "data":"dns2.stabletransit.com",
            "updated":"2011-01-21T23:24:44.000+0000",
            "ttl":3600,
            "created":"2011-01-21T23:24:44.000+0000"
         },
         {
            "name":"www.deployitron.com",
            "id":"CNAME-4567890",
            "type":"CNAME",
            "data":"deployitron.com",
            "updated":"2011-01-22T11:30:35.000+0000",
            "ttl":3600,
            "created":"2011-01-22T11:30:35.000+0000"
         },
         {
            "name":"www2.deployitron.com",
            "id":"CNAME-5678901",
            "type":"CNAME",
            "data":"deployitron.com",
            "updated":"2011-03-19T08:10:31.000+0000",
            "ttl":600,
            "created":"2011-03-19T08:10:31.000+0000"
         }
      ],
      "totalEntries":5
   },
   "emailAddress":"ipadmin@stabletransit.com",
   "created":"2011-01-21T23:24:44.000+0000"
}

Creating Domains

To create a domain, we issue the following JSON formatted command:

$ curl -D – -X POST -d '{ "domains":[ { "name":"aeVo8AiHeesh.ws", "emailAddress":"robert@aeVo8AiHeesh.ws", "comment":"This is the first domain created via API", "recordsList": { "records":[ { "ttl":600, "data":"127.0.0.1", "name":"aeVo8AiHeesh.ws", "type":"A" },{ "priority": 10, "ttl":86400, "data":"mail.aeVo8AiHeesh.ws", "name":"aeVo8AiHeesh.ws", "type":"MX" },{ "ttl":300, "data":"v=spf1 mx -all", "name":"aeVo8AiHeesh.ws", "type":"TXT" } ] } } ] }' -H "X-Auth-Token: yourAuthToken" -H "Content-Type: application/json" https://dns.api.rackspacecloud.com/v1.0/yourAccountNumber/domains

And the following is returned:

HTTP/1.1 202 Accepted
X-API-VERSION: 1.0.8
Content-Type: application/json
Date: Fri, 08 Jul 2011 15:18:12 GMT
Content-Length: 155
Server: Jetty(7.3.1.v20110307)

{"jobId":"yourJobID","callbackUrl":"https://dns.api.rackspacecloud.com/v1.0/yourAccountNumber/status/yourJobID"}

It’s important to note your job ID so that you can check the status of your job by issuing the following command:

$ curl -X GET -H "X-Auth-Token: yourAuthToken" -H "Accept: application/json" https://dns.api.rackspacecloud.com/v1.0/yourAccountNumber/status/yourJobID

If your job completed successfully, you should see something similar to the following:

{"domains":[{"name":"aevo8aiheesh.ws","id":2841222,"comment":"This is the first domain created via API","accountId":yourAccountNumber,"nameservers":[{"name":"ns.rackspace.com"},{"name":"ns1.rackspace.com"}],"updated":"2011-07-08T15:21:46.000+0000","ttl":3600,"recordsList":{"records":[{"name":"aevo8aiheesh.ws","id":"A-7088731","type":"A","data":"127.0.0.1","updated":"2011-07-08T15:21:47.000+0000","ttl":600,"created":"2011-07-08T15:21:47.000+0000"},{"name":"aevo8aiheesh.ws","id":"MX-3272903","priority":10,"type":"MX","data":"mail.aeVo8AiHeesh.ws","updated":"2011-07-08T15:21:48.000+0000","ttl":86400,"created":"2011-07-08T15:21:48.000+0000"},{"name":"aevo8aiheesh.ws","id":"TXT-243256","type":"TXT","data":"v=spf1 mx -all","updated":"2011-07-08T15:21:49.000+0000","ttl":300,"created":"2011-07-08T15:21:49.000+0000"}]},"emailAddress":"robert@aeVo8AiHeesh.ws","created":"2011-07-08T15:21:45.000+0000"}]}

I see that it was created and I can verify via dig by running:

$ dig aevo8aiheesh.ws @ns.rackspace.com any

Which returns:

; <<>> DiG 9.6.0-APPLE-P2 <<>> aevo8aiheesh.ws @ns.rackspace.com any
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40475
;; flags: qr aa rd; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;aevo8aiheesh.ws.               IN      ANY

;; ANSWER SECTION:
aevo8aiheesh.ws.        3600    IN      SOA     ns1.rackspace.com. robert.aevo8aiheesh.ws. 1310138509 3600 3600 3600 3600
aevo8aiheesh.ws.        86400   IN      MX      10 mail.aevo8aiheesh.ws.
aevo8aiheesh.ws.        3600    IN      NS      dns1.stabletransit.com.
aevo8aiheesh.ws.        3600    IN      NS      dns2.stabletransit.com.
aevo8aiheesh.ws.        300     IN      TXT     "v=spf1 mx -all"
aevo8aiheesh.ws.        600     IN      A       127.0.0.1

;; ADDITIONAL SECTION:
dns1.stabletransit.com. 86400   IN      A       69.20.95.4
dns2.stabletransit.com. 86400   IN      A       65.61.188.4

;; Query time: 35 msec
;; SERVER: 69.20.95.4#53(69.20.95.4)
;; WHEN: Fri Jul  8 10:45:38 2011
;; MSG SIZE  rcvd: 241

We can accomplish the same thing via XML by running the following:

$ curl -D - -X POST -d '' -H "X-Auth-Token: yourAuthToken" -H "Content-Type: application/xml" https://dns.api.rackspacecloud.com/v1.0/yourAccountID/domains

Which outputs:

HTTP/1.1 202 Accepted
X-API-VERSION: 1.0.8
Content-Type: application/json
Date: Fri, 08 Jul 2011 19:35:22 GMT
Content-Length: 155
Server: Jetty(7.3.1.v20110307)

{"jobId":"yourJobID","callbackUrl":"https://dns.api.rackspacecloud.com/v1.0/yourAccountNumber/status/yourJobID"}

Checking the status:

$ curl -X GET -H "X-Auth-Token: yourAuthToken" -H "Accept: application/xml" https://dns.api.rackspacecloud.com/v1.0/yourAccountID/status/yourJobID

Which returns:

To verify the domain exists via dig:

$ dig paingeez7uec.com @ns.rackspace.com any

Which outputs:

; <<>> DiG 9.6.0-APPLE-P2 <<>> paingeez7uec.com @ns.rackspace.com any
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45478
;; flags: qr aa rd; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;paingeez7uec.com.              IN      ANY

;; ANSWER SECTION:
paingeez7uec.com.       5600    IN      SOA     ns1.rackspace.com. robert.paingeez7uec.com. 1310153726 5600 5600 5600 5600
paingeez7uec.com.       5000    IN      MX      10 mail.paingeez7uec.com.
paingeez7uec.com.       5600    IN      NS      dns1.stabletransit.com.
paingeez7uec.com.       5600    IN      NS      dns2.stabletransit.com.
paingeez7uec.com.       600     IN      TXT     "v=spf1 mx -all"
paingeez7uec.com.       5600    IN      A       127.0.0.1

;; ADDITIONAL SECTION:
dns1.stabletransit.com. 86400   IN      A       69.20.95.4
dns2.stabletransit.com. 86400   IN      A       65.61.188.4

;; Query time: 42 msec
;; SERVER: 69.20.95.4#53(69.20.95.4)
;; WHEN: Fri Jul  8 14:49:55 2011
;; MSG SIZE  rcvd: 239

Now you can create domains in using both JSON and XML formatted responses.

Deleting Domains

To delete a domain using curl follow these simple steps. You will need your account ID (yourAccountID in previous examples) and the domain ID from a domain list.

JSON:

$ curl -X DELETE -H "X-Auth-Token: yourAuthToken" -H "Accept: application/json" https://dns.api.rackspacecloud.com/v1.0/yourAccountID/domains/2841222

{"jobId":"yourJobID","callbackUrl":"https://dns.api.rackspacecloud.com/v1.0/yourAccountID/status/yourJobID"}

XML:

$ curl -X DELETE -H "X-Auth-Token: yourAuthToken" -H "Accept: application/xml" https://dns.api.rackspacecloud.com/v1.0/yourAccountID/domains/2841642

yourJobIDhttps://dns.api.rackspacecloud.com/v1.0/yourAccountID/status/yourJobID

Stay tuned for part 2 where I will show how to modify domains, and add/delete/modify records.

Edge Purge Content from Rackspace Cloud Files via curl

robert — Wed, 29 Jun 2011 21:10:16 +0000

When the Rackspace Cloud Files product received Edge Purge functionality via the API, I didn’t give it much thought as I didn’t use the CDN functionality for any of my personal projects. That changed recently and I started doing some work with the CDN (powered by Akamai). All was fine until I realized I had set the TTL for the objects too high for my testing and wasn’t receiving the right content. Below you’ll find the appropriate methods for doing an edge purge of an object and container via curl using the API.

First, you’ll need to authenticate using your API key and username.

$ curl -D – -H "X-Auth-Key: yourAPIkey" -H "X-Auth-User: yourUsername" https://auth.api.rackspacecloud.com/v1.0

You should receive the following:

HTTP/1.1 204 No Content
Server: Apache/2.2.13 (Red Hat)
X-Storage-Url: https://storage.clouddrive.com/v1/yourAccountHash
Content-Type: application/octet-stream
Date: Date & Time
X-Auth-Token: yourAuthToken
X-Storage-Token: yourStorageToken
X-Server-Management-Url: https://servers.api.rackspacecloud.com/v1.0/yourAccountNumber
Connection: Keep-Alive
X-CDN-Management-Url: https://cdn1.clouddrive.com/v1/yourAccountHash
Content-Length: 0

You now have the information you need to do the Edge Purge from the Akamai fronted CDN. To delete an object, you’ll need the “X-Auth-Token” and “X-CDN-Management-Url”.

To do an Edge Purge of the given object “foo.txt” in the container “bar”, send the following via curl:

$ curl -D – -X DELETE -H "X-Auth-Token: yourAuthToken" -H "X-Purge-Email: your@email.address" https://cdn1.clouddrive.com/v1/yourAccountHash/bar/foo.txt

You’ll receive the following in response as well as an email to your@email.address.

HTTP/1.1 204 No Content
Date: Date & Time
Server: Apache
X-Akam-Est-Time: 420
X-Akam-Result-Code: 100
Content-Length: 0
Connection: close
Content-Type: text/plain; charset=UTF-8

To do an Edge Purge of the container “bar”, send the following via curl:

curl -D – -H "X-Auth-Token: yourAuthToken" -H "X-Purge-Email: your@email.address" -X DELETE https://cdn1.clouddrive.com/v1/yourAccountHash/bar/

You should receive a response identical to the one you did for object Edge Purge.

That’s it!

Putting subject & from in mail from command line

robert — Fri, 13 Jul 2007 19:56:04 +0000

I couldn’t figure out how to send an email with both the subject and from set from the command line.

mail -s "my subject" example@foo.bar

worked with mail but would only set the subject.

sendmail -f "sender@foo.bar" receiver@foo.bar

worked with sendmail but would only set the “from”. With a little help from Google I put this together:

#!/bin/bash
HOST=`hostname | awk 'BEGIN { FS="." } ; {print $1}'`
DOMAIN=`hostname`
PASSWORD='mypassword'
BODY=`tail -n 40 /var/log/maillog`
FROM="$HOST@$DOMAIN"
TO='receiver@foo.bar'
SUBJECT="Last 40 lines of maillog"
(
echo "From: $FROM"
echo "Subject: $SUBJECT"
echo "To: $TO"
echo "$BODY"
) | sendmail -f $FROM $TO

Postfix mailq search

robert — Thu, 12 Jul 2007 14:21:02 +0000

I couldn’t find a script to search the Postfix mail queue so I wrote one. It’s a bash script and can be downloaded here (or just copy and paste it to file of your choice). I call it ssubject.sh. It ends up just spitting out the queue id’s of messages that match. Usage: “ssubject.sh “some words to look for”

#!/bin/bash
SUBJECT=$1
/usr/sbin/postqueue -p | awk {'print $1'} | grep -v (host | \\
grep -v @ | grep -v (delivery | grep -v (Host | grep -v (connect | \\
grep -v (lost | grep -v (conversation | grep -v -Queue | \\
sed 's/*//g' | sed '/^$/d' > /tmp/queue_ids.txt
cat /tmp/queue_ids.txt | while read line; do
sudo /usr/sbin/postcat -q ${line}|> | grep "$SUBJECT" > /dev/null 2>&1
if [ "$?" -eq "0" ]; then
echo ${line}|> ;
fi
done