Iron Foundry Support for Stackato 1.2 Released

By On · Add Comment · In Release

With the latest changes from the Cloud Foundry team (re: anniversary of Cloud Foundry) comes a new and improved Stackato & Iron Foundry Micro VM combo. We’ve checked and tweaked things to run even better in your Stackato + Iron Foundry environment with the latest downloads. So check out the latest available micro image downloads for Stackato. The ActiveState Stackato team provides images available in:

Some of the changes and additions include…

  • Introduction of group management to Stackato managed applications
    • Support for separate per-user and per-group limits
    • Users can be in zero or many groups
  • Heroku buildpack framework support, with built-in buildpacks for
    Clojure, Go, Java, JRuby, Play! and Python
  • Updated Stackato App Store
    • Multiple App Store sources supported
    • Stackato admins can control App Store sources from the console

For Iron Foundry one of the key changes is the way DEA droplets spec handles things. So get the latest to be sure you have the best compatibility between these two Cloud Foundry Micro Environments. Find out about even more of the Stackato features here: http://community.activestate.com/node/8626

We’ve been testing this release and have added to the Iron Foundry VMs to include the following formats:

We’ve posted release notes on our latest VM images here:  http://help.ironfoundry.org/entries/20950078-micro-cloud-release-notes

For information on setting up these images follow the previously posted instructions “Iron Foundry, Stackato, a New Micro Image Pair“.

More news is coming here at the Iron Foundry Project so stay tuned. We’ll be back with more soon.

Pizza, Beer, PaaS and Lots of Frameworks

By On · Add Comment · In Community

This past Wednesday the Iron Foundry Team held a Pizza and PaaS Meetup at Tier 3 (@Tier3) headquarters in Bellevue, Washington. It was a great event with individuals coming to check out what the Iron Foundry Project enables and also to talk about PaaS Technologies in general.

One Part of the Room of Coders

One Part of the Room of Coders

The meeting kicked off with an introduction from Jared Wray, CTO of Tier 3. After he wrapped up the Iron Foundry Team; Eric Lee (@saintgimp), Shantu Roy (@shanturoy), Luke Bakken (@lukebakken) and I (@Adron) walked through several demoes involving ASP.NET MVC, SQL Server, Node.js, Express.js + NPM Additions, Java, Rabbit MQ, and Ruby with Sinatra.

During the course of the event we were able to show off a lot of the key pieces of the Iron Foundry Project including the Visual Studio Extension, the Cloud Explorer and discussed how the Windows DEA operates within the Cloud Foundry PaaS environment.

The Future, PaaS

PaaS is the future and with that we’ll be aiming to build and expand on our Pizza and PaaS meetups. They’re a lot of fun, informative and we get to push forward the PaaS technologies! So keep an eye out and we’ll post future meet ups here on the blog. We’re looking forward to meeting you!

PDX Cloud Foundry Hackathon

By On · Add Comment · In Community

Members of the Iron Foundry Contributors Team will be attending the PDX Cloud Foundry Hackathon this coming April 14th at Puppet Labs in Portland, Oregon. If you’re in Portland or want to come to Portland for a great day of Pizza, Beer, and DevOping come and check out the event. Ok, so I got your attention with the beer and pizza, but what’s the hacking really about?

The event is going to be multi-track with a focus on hacking the Cloud Foundry (and Iron Foundry) Code base. This track will dive into what is in the code base and how it is put together. The other track will focus on working to deploy and build applications specifically for the Cloud Foundry + Iron Foundry based platforms.

In addition to the main tracks there are a few other workshops we’ll be putting on. These include:

  • On Premise, Off Premise Cloud Foundry – As quoted on the description “You have internal infrastructure and external infrastructure in this “cloud” thing and would like to utilize both… we’ll dive into that.“
  • Cloud Foundry + Iron Foundry and Bridging the Gaps – “Now we’re talking FULL stack across every major stack. Iron Foundry, the missing linq in Cloud Foundry. Adding .NET & having it play nicely with Node.js, Ruby on Rails, and more. We’ll also dive into SQL Server, Mongo, and how to make the best use of RDBMS + NoSQL bits. Making the most of the abilities with PaaS.“
  • The Interoperable Cloud App Gallery – “Ingy döt Net would like to see a huge collection of apps that have been made to work on any PaaS solution. Think of it as the http://rosettacode.org/ of PaaS. Ingy started a GitHub organization called Cloud-Apps that is meant to curate forks of popular apps that have been made to work with one or more PaaS solutions like:  Cloud Foundry, Stackato, AppFog, PaaS.io, Iron Foundry, OpenShift, Heroku, DotCloud, etc. He is giving out commit to whomever wants it!“

 

Caldecott with MS SQL Server!

By On · 1 Comment · In Community, How To Guide, Release, VMC

Yesterday we launched our new testing environment that you can read about. With that announcement we added support for Caldecott which allows you to tunnel from your environment to services in the Cloud Foundry environment. Today we have enabled MS SQL support with Caldecott into our .ME environment and also our own version of the Cloud Foundry VMC that has all of the Iron Foundry support built in.

Install VMC Iron Foundry

Install Ruby for Windows from Ruby Installer. This is tested using version 1.9.3. During installation you can either add ruby to your PATH or add it manually later.

Run the following commands from a command prompt. You should ensure that ruby and sqlcmd are in your PATH as well.

Checking ruby version:

C:\>ruby --version
ruby 1.9.3p125 (2012-02-16) [i386-mingw32]
C:\>gem install vmc-ironfoundry --pre

Caldecott and MS SQL

To use Caldecott on Iron Foundry from a Windows machine to connect to a provisioned MS SQL database, follow these steps.

Install Ruby for Windows from Ruby Installer. This is tested using version 1.9.3. During installation you can either add ruby to your PATH or add it manually later.

Run the following commands from a command prompt. You should ensure that ruby and sqlcmd are in your PATH as well.

Checking ruby version:

C:\>ruby --version
ruby 1.9.3p125 (2012-02-16) [i386-mingw32]

Ensuring that sqlcmd.exe is in your PATH. If not, it is located by default at

C:\Program Files\Microsoft SQL Server\100\Tools\Binn\sqlcmd.exe

C:\>sqlcmd /?
Microsoft (R) SQL Server Command Line Tool
Version 10.50.2500.0 NT x64
Copyright (c) Microsoft Corporation. All rights reserved.

Install the vmc-IronFoundry gem

C:\>gem install vmc-IronFoundry --pre
Fetching: vmc-IronFoundry-0.3.16.IF.1.gem (100%)
Successfully installed vmc-IronFoundry-0.3.16.IF.1
1 gem installed
Installing ri documentation for vmc-IronFoundry-0.3.16.IF.1...
Installing RDoc documentation for vmc-IronFoundry-0.3.16.IF.1...

Target api.ironfoundry.me and log in to your account

C:\>vmc target api.ironfoundry.me
Successfully targeted to [http://api.ironfoundry.me]
C:\>vmc login --email foo@bar.com --passwd XXXYYYZZZ
Attempting login to [http://api.ironfoundry.me]
Successfully logged into [http://api.ironfoundry.me]

Provision an MS SQL database

C:\>vmc create-service mssql
Creating Service [mssql-c902d]: OK

Tunnel to your database

C:\>vmc tunnel mssql-c902d sqlcmd
Deploying tunnel application 'caldecott'.
Uploading Application:
 Checking for available resources: OK
 Packing application: OK
 Uploading (1K): OK
Push Status: OK
Binding Service [mssql-c902d]: OK
Staging Application 'caldecott': OK
Starting Application 'caldecott': OK
Getting tunnel connection info: OK
Service connection info:
 username : uxeBbNM0jYAFS
 password : psOmxGWibimeX
 name : d7dedaf7e01ae42568c07c44ec30bff99
Starting tunnel to mssql-c902d on port 10000.
Launching 'sqlcmd -S localhost,10000 -U uxeBbNM0jYAFS -P psOmxGWibimeX -d d7dedaf7e01ae42568c07c44ec30bff99'
1>

You can now run commands from within sqlcmd against your database!

1> select @@VERSION
2> GO
Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
 Jun 17 2011 00:54:03
 Copyright (c) Microsoft Corporation
 Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

In addition, you can use the displayed connection information to connect via SQL Management Studio. Just use localhost,10000 as the “Server name”. Be sure to start the tunnel first and keep it open during the time you’re using Management Studio. Quitting sqlcmd will close the tunnel.

connect_local.png

New Iron Foundry Test Environment .ME

By On · 2 Comments · In Community, Release, Test Environment

Today we have released a major update to the Iron Foundry test environment. Currently this environment is supporting over 350 developers constantly deploying/hosting applications using .NET and the Iron Foundry developer tool set. Here are some of the major changes and highlights:

  • Multi-Runtime Support: We have extended the offering to support polyglot applications with the support of Java, Ruby, PHP, Python, Node.js, and .NET.
  • Rabbit MQ Support: Rabbit MQ is now added as a service offering to use in the environment. For more information about Rabbit MQ visit our quick start guide.
  • Extended Database Support: Adding support for MySQL and Postgres to extend the other databases currently offered (MS SQL, Redis, and MongoDB).
  • Caldecott Support: We have enabled Caldecott support for the entire environment so that you can tunnel to backend services. Learn more about it at the Cloud Foundry Blog.
  • No more trial expiration: We have removed the 90 day trial limitation so that you can test your application longer if needed. This is a testing environment and we do not give support for it beyond what a standard test environment needs so please do not run production applications on it. The limitation is now based on resources being provisioned to 3 application instances and 2 database instances. If you need more contact us so that we can help.
  • New Friendly Url: The new friendly url is ironfoundry.me and will enable your applications with [appname].ironfoundry.me. The API to access the new environment is api.ironfoundry.me.

For the developers who already have signed up you will not have to sign up again as we have ported your user names and passwords over to the ironfoundry.me environment.

As this is a new environment with many features, we decided to keep the gofoundry.net environment running so users have time to migrate their applications to the new environment. All new accounts will have access to the new environment and you can sign up here for free.

Go here to get started!

Iron Foundry, Stackato, a New Micro Image Pair

By On · 1 Comment · In Micro Iron Instance, Release

Today we’re releasing a new update for the Iron Foundry Micro Instance. The biggest changes are two fold. One is our full support of the Stackato from ActiveState powered micro instance. We’ve taken the great work that the ActiveState Team has done with Cloud Foundry and rolled that into our Iron Foundry enabled Micro Instance! The second big addition is full support for the Cloud Foundry Micro Cloud Foundry 1.2 release.

For those of you that have dived heavily into the overall framework, some of the specifics include changes that enhance the reliability of the controller and self-healing nature of the system.

How to get it up and running? Easy…

First download and get the Stackato Micro Cloud Running.

  1. Download the Stackato Micro Cloud here: http://www.activestate.com/stackato/download_vm
  2. Unzip the image to the location you want the image to execute from.
  3. Set the network on the staccato image to bridged.
  4. Startup the Stackato Image.
  5. When it boots up get the IP and Hostname Address. Note both the host name and IP address.
  6. The Hostname will need to be added to your hosts file, either /etc/hosts in OS-X or Linux and c:WindowsSystem32Drivershosts. Add the IP & host to the file like ‘192.168.NNN.YYYY stackato-XXXX.local’ and  ’api.stackato-XXXX.local testwebapp.stackato-XXXX.local‘ (add additional entries at the end for other web apps you intend to push)
  7. Navigate to http://stackato-XXXX.local and it will redirect to the initial setup page where you enter an email address and password. These credentials are added to the Stackato Instance, so be sure to remember them.

Next step get the Micro Iron Foundry VM Running & Communicating w/ The Stackato Micro Cloud.

    1. Download the Micro Iron Foundry VM here: http://www.ironfoundry.org/download (Use 7-zip to unzip, or on the Mac use a tool like the “Unarchiver”(http://wakaba.c3.cx/s/apps/unarchiver.html or get it from the App Store)).
    2. If VMWare asks if you have moved or copied the VM, choose “I copied it”.
    3. It will show “Setup is starting services” as this is a Windows VM. After it goes through the inital setup it will continue and require your input
    4. Set the timezone. Click Next
    5. Accept the licensing terms. Click Next
    6. It will now say that the users password must be changed before logging on the first time. Click OK and set the password (make sure to remember the password!)
    7. After setting the password you will now be logged into the core terminal prompt. You can now enable Iron Foundry on your Cloud Foundry Micro Cloud. (Make sure your Cloud Foundry Micro Cloud is running at the same time)
    8. Boot up the Micro Iron Foundry instance. It will prompt you for a password for the Administrator user.
    9. At the command prompt (C:UsersAdministrator) execute these commands:
    10. C:UsersAdministrator>cd C:IronFoundrySetup
    11. C:IronFoundrySetup>RunSetup.cmd
    12. At the prompt enter your domain stackato-XXXX.local, IP address and password.
    13. It will then connect via ssh, patch the system, restart the cloud controller, and setup the local SQL provisioning services in the Iron Foundry VM.

command line results

Once the setup process is done you can use Cloud Foundry Explorer (http://www.ironfoundry.org/download) to push an ASP.NET application. I’ve attached a sample ASP.NET application. Click the gear icon to add a cloud, click the green + button to add a New Server. Rename server to something and add an api url of api.stackato-XXXX.local, email and password. Clicking ”Validate Account” should succeed. Once the cloud is added, you can use push and choose that cloud to publish to it. You should use “testwebapp” as the name since you added it to the hosts file above. Once pushed, you can visit http://testwebapp.stackato-XXXX.local to browse to your application, and http://testwebapp.stackato-XXXX.local/env to see more detailed info.

To get involved with Iron Foundry check out the project at http://www.ironfoundry.org and Cloud Foundry at http://www.cloudfoundry.org/. With the code available on github at https://github.com/IronFoundry or https://github.com/cloudfoundry.

How To Deploy Orchard CMS on Iron Foundry

By On · Add Comment · In Cloud Foundry Explorer, How To Guide, Release, Test Environment
Orchard is a free, open source, community-focused project aimed at delivering applications and reusable components on the ASP.NET platform. The Orchard project as a very active and vibrant community that is actively developing and also using it for personal and commercial offerings.

Iron Foundry is an open source project  that extends .NET to Cloud Foundry (The Open Platform as a Service). available for the Windows Server Environments with the ability to run the full spectrum of .NET Web Applications, SQL Server, and more. Iron Foundry places the Microsoft tool stack on an even footing with the Linux-based stacks. This platform is all open source and can be deployed anywhere. Today we are going to use the free trial environment provided by the Iron Foundry project.

With Iron Foundry and Cloud Foundry Orchard can scale within minutes to handle load on the system. This also gives an environment for rapid testing and staging of your application.

In four easy steps you can deploy and start configuring your Orchard CMS instance on Iron Foundry:

Step 1:  Download Orchard CMS

To download Orchard just go to the Download Page and then select the “Download as a zip” it is about 8MB in size. It will then ask you to agree to the terms.

Step 2:  Make changes to be supported on Iron Foundry

  1. Go ahead and unzip it to your temporary directory.

You can read more about the manual install here:http://docs.orchardproject.net/Documentation/Manually-installing-Orchard-zip-file

Step 3:  Sign up and Deploy to Iron Foundry

  1. Sign up for your free account on Iron Foundry so you can test your deployment. (Note: this can take up to 24 hours to get your account activated.)
  2. Once your account is activated you can also download the Cloud Foundry Explorer from Iron Foundry.
  3. After installing the Cloud Foundry explorer you will need to run the application.
  4. Upon startup, use the gear icon to add a connection to api.gofoundry.net:
    image00.png
  1. You will be presented with the “Manage Clouds” screen (new in 1.6.0). To add a well-known cloud, use the dropdown at the bottom of the left side of the screen, with the cloud-plus icon. Select “Iron Foundry” to add a connection to this cloud. The url will be pre-filled to http://api.gofoundry.net
  2. Enter the email address and password credentials that were mailed to you upon signup. Use the “Validate Account” button to double-check your entriesimage01.png 
  3. When you choose “Ok”, you will see this new cloud connection added to your explorer window.
    image03.png
  1. Double-click the new connection to see an overview that will be displayed on the right.
    image05.png 
  1. Next you will want to create an SQL instance to use. Main Iron Foundry Production tab at the bottom switch to “Applications” view.
  2. On the services click the button to create a new service. Create a name for it and then from the drop down select MS SQL.
    image04.png
  3. Use the “Push Application” button to push a new application to Iron Foundry:
    image02.png
  1. In the dialog, choose the cloud to which to push. Then, choose an application name that does not contain spaces. The url to specify will be in the form APPNAME.gofoundry.net, where APPNAME is the name you chose. Choose Browse… to pick the directory in which you unziped your orchard application. Note: this directory is the one in which a Web.config file and a bin subdirectory exists.image06.png
  2. Once push completes, browse to APPNAME.gofoundry.net to see your deployed application.

Step 4: Setup your new Orchard Instance

You should be able to browse to your new orchard install at your application url (http://APPNAME.gofoundry.net) where you will see a getting started page:
image07.png

When you get to the screen below you are going to want to select to deploy SQL server and put in the connection string. To get the connection string you need to do the following:

  1. Go back to the Cloud Foundry Explorer
  2. Once there browse to your cloud and then browse to your application
  3. Once you have expanded to see the files double click on the web.config file which will open for you. In there you will see more entries added. All you need to do is copy the SQL server configuration settings and then put it into the orchard setup screen.
    image08.png
Anybody deploying Orchard on Iron Foundry can contribute and get a free Iron Foundry shirt!

Have you brought the HAMMA?

By On · Add Comment · In Community

If you have contributed to Iron Foundry in any way, let us know. We’ll send you a free exclusive “I BRING THE HAMMA” Iron Foundry t-shirt while supplies last. Using Iron Foundry on a project, providing feedback, blogging about Iron Foundry, or source code improvements are some of the ways that you can contribute. Here are a couple of examples:

Let us know how you are contributing by going to: http://www.ironfoundry.org/hamma

Check out how to start contributing: http://help.ironfoundry.org/entries/20777076-start-contributing

Explorer and Plugin Updates!

By On · Add Comment · In Cloud Foundry Explorer, Release, Visual Studio Extension

Today we are releasing some enhancements/bug fixes to the Cloud Foundry Explorer and Visual Studio Plugin.

The most significant enhancement is how you manage your Cloud Foundry instances: We simplified it to a single screen to make it easier.

cf_explorer_manage_clouds.png

Cloud Foundry Explorer:

Release notes: http://help.ironfoundry.org/entries/20794491-cloud-foundry-explorer-current-release

Updated documentation: http://help.ironfoundry.org/entries/20794486-cloud-foundry-explorer-documentation

On the Visual Studio plugin we updated it with some bug fixes.

VS Plugin:

Release notes: http://help.ironfoundry.org/entries/20794496-visual-studio-extension-current-release

As always you can download here: http://www.ironfoundry.org/download

DEA and Micro Updates.. Oh My!

By On · Add Comment · In DEA.NET, Micro Iron Instance, Release

Today we released the updated to the DEA (Droplet Execution Agent) and our Micro Cloud download. These updates do address some of the bugs that have been reported and also a memory leak issue with the IIS Management COM object.

Download the latest DEA, Micro, and Developer tools: http://www.ironfoundry.org/download.

Get Help: http://help.ironfoundry.org

The Iron Foundry Trial environment has been updated to the latest and greatest DEA and you can sign up for FREE to try it out: http://www.ironfoundry.org/signup

Thanks

Iron Foundry Team – Bringing the Hamma!

← Previous Entries