From 3449c602632c3dceb0d66c8e2ae31ea92f774ed8 Mon Sep 17 00:00:00 2001 From: Adam Merka <405417@muni.cz> Date: Thu, 13 Dec 2018 14:39:41 +0100 Subject: [PATCH] Updates 7-heat/README.md Auto commit by GitBook Editor --- 6-cli/README.md | 29 ++++++++++++++++++++++++++--- 7-heat/README.md | 31 +++++++++++++++++++++++++++++-- 2 files changed, 55 insertions(+), 5 deletions(-) diff --git a/6-cli/README.md b/6-cli/README.md index d29c9d3..9a63c13 100644 --- a/6-cli/README.md +++ b/6-cli/README.md @@ -1,10 +1,33 @@ # Command line interface +You can interact with OpenStack using your command line. This is the preferred option by advanced users but it is available even for beginner users. The complete functionality is accessible throug OpenStack API \([**http://developer.openstack.org/api-guide/quick-start/index.html**](http://developer.openstack.org/api-guide/quick-start/index.html)\). Remeber that OpenStack API is accessible only through the University network \(range 147.521.0.0/16\) You can also use [**VPN**](https://it.muni.cz/sluzby/vpn). Some examples of how to interact with the CLI can be found here \([**http://docs.openstack.org/user-guide/cli-cheat-sheet.html**](http://docs.openstack.org/user-guide/cli-cheat-sheet.html)\). An SDKs exists for the usual programming languages \([**http://developer.openstack.org/**](http://developer.openstack.org/)\). You can also use OpenStack Client for simple scripts written directly into the command line. Install it via: + + +`pip install python-openstackclient` + + + +1. You can forward the login credentials to the client through parameters or through variable environment. You can generate a script for the environment variables through the Horizon dashboard. Navigate to  **Project** > **Compute** > **API Acess **and hit the **"Download OpenStack RC File"** and select the **"OpenStack RC File \(Identity API v3\)"** option. + + \(insert screenshot\) + +2. And continue by setting the environment variables by running the script. \(Replace the MyProject by the actual project that you created the script in.\) + +``` +. pMyProject-openrc.sh +``` + ## Installation ->**TODO** manual install + some docker shizz? + +> **TODO** manual install + some docker shizz? ## Access to Metacloud via CLI ->**TODO** add token access info + +> **TODO** add token access info ## Usage examples ->**TODO** how to create vm, network from CLI + +> **TODO** how to create vm, network from CLI + + + diff --git a/7-heat/README.md b/7-heat/README.md index 973e67e..3383434 100644 --- a/7-heat/README.md +++ b/7-heat/README.md @@ -1,4 +1,31 @@ -# Orchestration with Heat +# Orchestration + +Apart from the native web GUI and CLI you can also operate your instances and apllications running on OpenStack using an array of orchestration tools. Some of them are listed below: + +## [**Heat**](https://wiki.openstack.org/wiki/Heat) + +Heat is one of the OpenStack projects that enables cloud resource orchestration. A Heat template describes the infrastructure for a cloud application in a text file that is readable and writable by humans, and can be checked into version control, diffed, &c. + +* Infrastructure resources that can be described include: servers, floating ips, volumes, security groups, users, etc. + +* Heat also provides an autoscaling service that integrates with [Telemetry](https://wiki.openstack.org/wiki/Telemetry), so you can include a scaling group as a resource in a template. +* Templates can also specify the relationships between resources \(e.g. this volume is connected to this server\). This enables Heat to call out to the OpenStack APIs to create all of your infrastructure in the correct order to completely launch your application. +* Heat manages the whole lifecycle of the application - when you need to change your infrastructure, simply modify the template and use it to update your existing stack. Heat knows how to make the necessary changes. It will delete all of the resources when you are finished with the application, too. +* Heat primarily manages infrastructure, but the templates integrate well with software configuration management tools such as [Puppet](https://s3.amazonaws.com/cloudformation-examples/IntegratingAWSCloudFormationWithPuppet.pdf) and [Chef](http://www.full360.com/2011/02/27/integrating-aws-cloudformation-and-chef.html). The Heat team is working on providing even better integration between infrastructure and software.Its GUI is available under + +To work with Heat, we recomment the following set of tutorials: [**1**](https://developer.rackspace.com/blog/openstack-orchestration-in-depth-part-1-introduction-to-heat/),[**2**](https://developer.rackspace.com/blog/openstack-orchestration-in-depth-part-2-single-instance-deployments/),[**3**](https://developer.rackspace.com/blog/openstack-orchestration-in-depth-part-3-multi-instance-deployments/),[**4**](https://developer.rackspace.com/blog/openstack-orchestration-in-depth-part-4-scaling/). Additional templates can be found here + +## [**Vagrant**](https://www.vagrantup.com/) + +See the [**vagrant-openstack-example**](https://gitlab.ics.muni.cz/172673/vagrant-openstack-example) for a reference including the Vagrantfile + +## [**Ansible**](https://www.ansible.com/) + +You can use this guide [**Using Ansible 2.0 to launch a server on OpenStack**](http://superuser.openstack.org/articles/using-ansible-2-0-to-launch-a-server-on-openstack/). This way was used for testing the MUNI OpenStack. [**Scipion Web Tools clusteru**](https://github.com/RadimPesa/scipion_on_ostack) # How to start ->**TODO** ad some examples + +> **TODO** ad some examples + + + -- GitLab