Add new content to Murano introduction article
Change-Id: I84ec4a5483a6be8be959bab77488c0949fb5f1a0
This commit is contained in:
parent
561eb2040d
commit
3a03effd9e
@ -40,7 +40,6 @@ Introduction to Murano
|
||||
intro/target_users
|
||||
intro/architecture
|
||||
intro/use_cases
|
||||
intro/user_stories
|
||||
|
||||
Using Murano
|
||||
~~~~~~~~~~~~
|
||||
|
BIN
doc/source/draft/intro/architecture.png
Normal file
BIN
doc/source/draft/intro/architecture.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 42 KiB |
@ -3,3 +3,20 @@
|
||||
============
|
||||
Architecture
|
||||
============
|
||||
|
||||
Murano uses other OpenStack services in order to prevent reimplementing of
|
||||
existing functionality. Murano interacts with these services using their REST
|
||||
API (via their python clients). The most used external services are keystone
|
||||
and heat.
|
||||
|
||||
* Heat is used to orchestrate the infrastructural resources such as servers,
|
||||
volumes, and networks. Murano dynamically creates the heat templates based on
|
||||
the application definition.
|
||||
|
||||
* All remote operations to the user’s servers are done via an AMQP queue to the
|
||||
murano-agent. Examples of this are installing and configuring software on the
|
||||
server. Note that this communication can easily be configured on a separate
|
||||
instance of AMQP to ensure that the infrastructure and servers are isolated.
|
||||
|
||||
.. image:: architecture.png
|
||||
:width: 700 px
|
||||
|
@ -6,3 +6,28 @@
|
||||
=========
|
||||
Use cases
|
||||
=========
|
||||
|
||||
* *IT as a Service*
|
||||
|
||||
An IT organization wants to control applications, available to cloud users.
|
||||
Application management should be simple and not time-consuming. Users should be
|
||||
able to easily find and create the desired applications.
|
||||
|
||||
* *Self-service portal*
|
||||
|
||||
You may want to create compound combinations of applications dynamically from
|
||||
simple app blocks. And you can create an environment that satisfies your
|
||||
requirements in a matter of minutes. Examples of such an environment may be
|
||||
“Jenkins+Java+Tomcat” or “Jenkins+Gerrit+Java+JBoss”. So testing application in
|
||||
different environment combinations becomes easier.
|
||||
|
||||
* *Glue layer use case*
|
||||
|
||||
Any external service or technology may be linked to the application in the
|
||||
cloud. It can be done using the powerful Murano architecture. For example,
|
||||
Murano supports Docker and OracleDB applications, and to enable this support
|
||||
no single change was made to Murano itself. So, users can integrate with new
|
||||
external services with a minimum cost. Currently, murano applications have been
|
||||
integrated with the following technologies: Docker, Legacy apps VMs or bare
|
||||
metal, apps outside of OpenStack, and the following ones are planned for the
|
||||
future: cloudify and TOSCA, apache brooklin, APS.
|
||||
|
@ -1,8 +0,0 @@
|
||||
.. _user-stories:
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
============
|
||||
User stories
|
||||
============
|
Loading…
Reference in New Issue
Block a user