Fujitsu K5 Example Heat Stacks

Finally, I get to publish some heat stacks for the Fujitsu K5 OpenStack Public cloud platform. Things have been manic over the last few weeks with very little time to blog.

Heat is OpenStack’s orchestration project and is generally what should be used when you have a requirement to be able to build an infrastructure pattern (template) quickly and consistently in your OpenStack K5 IaaS cloud, or any other OpenStack cloud for that matter . The advantage of this is that, as you can see below, the template is coded in a YAML file which I have stored in Github. Now I have the ability to version control my infrastructure as well as my application code which should result in less surprises during deployments of tested IaC (Infrastructure as Code) versions. This is a requirement if you are hoping to move to a Continuous Integration and Continuous Deployment operational model.

The first example below, and also available here, builds the following infrastructure  ‘automagically’:

  • 2 x L2 networks
  • 2 x Subnets
    • Note: Additional routes have been added tot he subnets – these are not required for this post
  • 1 x Windows server
    • with an additional block drive
    • init script to  configure and mount new drive as ‘D:\’
    • DHCP assigned ip address
    • admin user set to k5user
    • attached to management network
  • 1 x Linux Server
    • with an additional block drive
    • init script to configure and mount new drive at deployment time
    • fixed ip address assignment
    • admin user set to K5user
    • attached to shared services network
  • 2 x Security Groups (SGs)
    • Warning: These SGs are WIDE OPEN – Please ensure to configure these SGs appropriately for your environment.

Example – Project 1 Stack

Upload the heat template through the Stack option in the K5 IaaS gui as follows:


Heat stacks can also be deployed using the API – blog to follow.

Example – Project 2 Stack

Happy Stacking!







2 thoughts on “Fujitsu K5 Example Heat Stacks

  1. Hi,

    have you made any stack where you allocate puplic ip to windows machine and after creation you can actually connect it with RDP?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s