My PDC10 session is available online (it was pre-recorded). I talk about the new ‘Labs’ release that we released into the datacenter this week and about a range of future capabilities that we’re planning for Service Bus. Some of those future capabilities that are a bit further out are about bringing back some popular capabilities from back in the .NET Services incubation days (like Push and Service Orchestration), some are entirely new.

One important note about the new release at http://portal.appfabriclabs.com – for Service Bus, this is a focused release that provides mostly only new features and doesn’t provide the full capability scope of the production system and SDK. The goal here is to provide insight into an ongoing development process and opportunity for feedback as we’re continuing to evolve AppFabric. So don’t derive any implications from this release on what we’re going to do with the capabilities already in production.

Click here to go to the talk.

Categories: AppFabric | Azure | Technology | Web Services

We know that there’s a number of you out there who have outbound firewall rules in place on your corporate infrastructures that are based on IP address whitelisting. So if you want to make Service Bus or Access Control work, you need to know where our services reside. Below is the current list of where the services are deployed as of today, but be aware that it’s in the nature of cloud infrastructures that things can and will move over time.IP address whitelisting strategy isn’t really the right thing to do when the other side is a massively multi-tenant infrastructure such as Windows Azure (or any other public cloud platform, for that matter)

  • Asia (SouthEast): 207.46.48.0/20, 111.221.16.0/21, 111.221.80.0/20
  • Asia (East): 111.221.64.0/22, 65.52.160.0/19
  • Europe (West): 94.245.97.0/24, 65.52.128.0/19
  • Europe (North): 213.199.128.0/20, 213.199.160.0/20, 213.199.184.0/21, 94.245.112.0/20, 94.245.88.0/21, 94.245.104.0/21, 65.52.64.0/20, 65.52.224.0/19
  • US (North/Central): 207.46.192.0/20, 65.52.0.0/19, 65.52.48.0/20, 65.52.192.0/19, 209.240.220.0/23
  • US (South/Central): 65.55.80.0/20, 65.54.48.0/21, 65.55.64.0/20, 70.37.48.0/20, 70.37.64.0/18, 65.52.32.0/21, 70.37.160.0/21
Categories: AppFabric | Azure

There must be dozens of these things, but I didn’t find one online last week and I needed a tool like this to prep a part of my keynote demo in Poland last week – and thus I wrote one. It’s a simple file management utility that works with the Windows Azure Blob store. No whistles, no bells, 344 lines of code if you care to look, both exe and source downloads below, MS-PL license.

Examples:
   List all files from the 'images' container:
        Blobber.exe -o list -c images -a MyAcct -k <key>
    List all files matching *.jpg from the 'images' container:
        Blobber.exe -o list -c images -a MyAcct -k <key> *.jpg
    List all files matching *.jpg from the 'images' container (case-insensitive):
        Blobber.exe -o list -l -c images -a MyAcct -k <key> *.jpg
    Delete all files matching *.jpg from the 'images' container:
        Blobber.exe -o deletefile -l -c images -a MyAcct -k <key> *.jpg
    Delete 'images' container:
        Blobber.exe -o deletectr -c images -a MyAcct -k <key>
    Upload all files from the c:\pictures directory into 'images' container:
        Blobber.exe -o upload -c images -a MyAcct -k <key> c:\pictures\*.jpg
    Upload like above and include all subdirectories:
        Blobber.exe -o upload -s -c images -a MyAcct -k <key> c:\pictures\*.*
    Upload like above and convert all file names to lower case:
        Blobber.exe -o upload -l -s -c images -a MyAcct -k <key> c:\pictures\*.*
    Upload all files from the c:\pictures directory into 'images' container on dev storage:
        Blobber.exe -o upload -l -s -c images -d c:\pictures\*.*
Arguments:
    -o <operation> upload, deletectr, deletefile, list (optional, default:'list')
        -o list [options] -c <container>  <relative-uri-suffix-pattern> (* and ? wildcards)
        -o upload [options] [-s] -c <container> <local-path-file-pattern>
        -o deletefile [options] -c <container> <relative-uri-suffix-pattern> (* and ? wildcards)
        -o deletectr [options] -c <container>
    -c <container> Container (optional, default:'files')
    -s Include local file subdirectories (optional, upload only)
    -p Make container public (optional)
    -l Convert all paths and file names to lower case (optional)
    -d Use the local Windows Azure SDK Developer Storage (optional)
    -b <baseUri> Base URI (optional override)
    -a <accountName> Account Name (optional if specified in config)
    -k <key> Account Key  (optional if specified in config)

You can also specify your account infomation in blobber.exe.config and omit the -a/-k arguments.

Executable: Blobber-exe.zip (133.4 KB)
Source: Blobber-src.zip (5.41 KB)

[Update: I just find that I unintentionally used the same name as a similar utility from Codeplex: http://blobber.codeplex.com/. Sorry.]

Categories: