Jump to: navigation, search

Difference between revisions of "Heat/Blueprints/Multi Region Support for Heat"

(→‎Nested Stack)
(→‎Nested Stack)
Line 98: Line 98:
  
 
==== Nested Stack ====
 
==== Nested Stack ====
−
 
−
TemplateURL
 
−
TimeoutInMinutes
 
−
Parameters
 
  
 
{| class="wikitable"
 
{| class="wikitable"

Revision as of 10:49, 31 July 2013

--bartosz-gorski (talk) 23:51, 15 July 2013 (UTC)

Overview

Introduction

Most of enterprises are focusing on Multi-cloud (using both private and public clouds) as enterprise cloud strategy. They will not completely migrate to Service Provider's cloud (public cloud). They will still keep their mission critical information assets to their premise or collocation space (private cloud).

Our goal is to create Hybrid-cloud (combination of public and private cloud). Creating Hybrid-cloud requires:

  • Seamless operation among heterogeneous environment
  • End-to-end automatic provisioning based on system template (VM, network, topology)
  • Unified control and monitoring
    • Multi-Hypervisor including bare-metal
    • Multi-Region control
    • Secure network access via Internet (VPN connection)
Hybrid-cloud

Requirements & Challenges

Requirements for Heat:

  • Mapping between Regions and API endpoints
  • Mapping between Regions and Images
  • Specifying Region for each resource
  • Support for VPN as resource
  • Horizon interface for Heat with multi regions


Challenges:

  • dealing with dependencies between resources in different regions
  • minimizing number of single region templates for which multi region template will be split
  • figure out efficient way to update multi region stack

Goal

First Use Case Scenario (no dependencies)

Multi region first use case

We have two regions (East and West) with separate OpenStack installations. We want to use Heat with multi region support to create in both regions:

  • Quantum Network
  • Quantum Subnet
    • 10.1.0.0/24 in East
    • 10.2.0.0/24 in West
  • Router
    • Router Interface for created subnet
    • Router Gateway for external network
  • VPN Service for created router
    • IKE Policy
    • IPsec Policy
    • VPN Connection
  • Server connected to created subnet


Template file example in appendix (Multiregion.template).

Second Use Case Scenario (with dependencies)

TBD

Architecture

Overview

Description:

  • More than one region (for example two: East and West)
  • Separate OpenStack installation (Nova, Glance, Swift, Neutron and Cinder) in each region
  • One Keystone service for all regions
  • One Horizon with multi region support
  • One Heat for multi region orchestration - to be clear right now it does not exist

Context as Resource

Property Description Default Value
Tenant/Project
Region/Endpoint
User credentails 
...
"Resources" : {
    ...
    "NetworkEast": {
        "Type": "OS::Quantum::Net",
        "RegionName" : { "Ref" : "RegionEast" },
        "Properties": {
            "name": "East Region Network"
        }
    },
    ...
}
...


Nested Stack

Property Description Implementation
Context Context which will be used to create nested stack Not started
TemplateURL Url address to nested stack tempalte file Done
TimeoutInMinutes Creation timeout in minutes Done
Parameters Values for nested stack parameters Done 
...
"Resources" : {
    ...
    "NewStackTemplate": {
        "Type": "AWS::CloudFormation::Stack",
        "Properties": {
            "TemplateURL": "https://raw.github.com/openstack/heat-templates/master/cfn/NestedStack.template",
            "Parameters": {
                "ParameterName1" : "Value1",
                "ParameterName2" : "Value2",
                "ParameterName3" : "Value3",
                ...
            }
        }
    },
    ...
}
...

Master Template

TBD

Stack Launch Flow

Challenges & Solutions

Challenge First step Future work
Dependencies between resources from different regions.

What needs to be done

Heat

Engine

Blueprint for VPaaS support

API/CLI

Probably we do not need to add any new command.

UI

Existing UI views:

Horizon support for multi regions

Dropbox will appear only if more than one region is available in keystone catalog.

Dependencies & References

Appendix

Templates

  • Multiregion.template


  
NTTI3






          

                

                
        

        Retrieved from "https://wiki.openstack.org/w/index.php?title=Heat/Blueprints/Multi_Region_Support_for_Heat&oldid=27280"