Hurtle is the orchestration framework that powers all orchestration of MCN services.

Q: Why is it Called hurtle?

A: Cos we like turtles and recursion.

Q: What is your motto?

A: "Confusing name, simple orchestration".

hurtle lets you:

offer your software as a service i.e. "hurtle it!"

Hurtle lets you automate the life-cycle management of your service, from deployment of cloud resources all the way to configuration and runtime management (e.g., scaling).

**But here comes the best part: **

hurtle has been designed since its inception to support service composition, so that you can run complex services by (recursively!) composing simple ones. Welcome to truly modular cloud service composition! Microservices anyone?

hurtle enables service and infrastructure orchestration to easily compose, deploy, provision and manage distributed systems

Its functionality all revolves around this idea, so the service offered is also one that can be designed with the cloud in mind, based on the cloud-native application research of the ICCLab.

hurtle has two origins:

1. Mobile Cloud Networking, obviously, where in the telcom world and in particular Network Function Virtualisation (NFV). Here hurtle has been used to offer services that have been to date executed directly on or embedded in hardware.
2. is the ICCLab's Cloud Orchestration Initiative

And well, it's all powered upon another hurtle ;-)

This repository provides documentation for hurtle and pointers to the other repositories that make up a complete hurtle system.

hurtle consists of the following components:

• Service Manager (SM): receives requests for new tenant service instances -> Code
• Service Orchestrator (SO): manages the lifecycle of a tenant service instance -> Sample code
• CloudController (CC): manages and abstracts underlying resources and SOs -> Code

For more details, see hurtle.it

Report bugs and request features using GitHub Issues. For additional resources, you can contact the maintainers directly. Community discussion about turtle happens in one main place:

• The hurtle-discuss mailing list. Once you subscribe to the list, you can send mail to the list address: [email protected] The mailing list archives are also available on the web.

You can follow @hurtle_it on Twitter for updates and of course on the ICCLab blog

To report bugs or request features, submit issues here on GitHub.. If you're contributing code, make pull requests to the appropriate repositories (see the repo overview). If you're contributing something substantial, you should first contact developers on the hurtle-discuss mailing list (subscribe.

For urgent questions please contact the maintainers directly.

Hurtle repositories follow no written Guidelines to date.

hurtle is licensed under the Apache License version 2.0. See the file LICENSE.