@@ -25,8 +25,8 @@ To create and gain acces to virtual machine you need to:
To create a first instance accessible from the network you typically need to go through a few one-time steps that are not required later on. The first step is to create/import SSH keys.
1. To create a new SSH key, go to **Project > Compute > Key Pairs **and clock the button "Create Key Pair"
{% reveal %}
1. To create a new SSH key, go to **Project > Compute > Key Pairs **and click the button "Create Key Pair"
{% reveal %}
{% endreveal %}
...
...
@@ -46,7 +46,9 @@ All network traffic is blocked in OpenStack by default. You need to explicitly g
3. Add another rule. This time choose "SSH" and leave the remaining fields unchanged.
Instances in OpenStack make use of user-defined internal networks, through which they can communicate. To access your instances from an external network, you need to connect the internal and the external network via a virtual router and allocate a public \(floating\) IP address to your virtual machine.
By logging in, you are automatically provided with a default internal network **"internal-net"** and a default virtual router that connects to the public network **"public-float-21" **with a subnet of **192.168.0.0/24. **In order to make your instance publicly accessible, you only need to assign a public IP to it.
1. In the left menu navigate to **Project > Network > Networks** and hit **"Create network".**
2. Give your network a name and set a subnet. Both are optional.
2. Give your network a name and set a subnet.
3. In details add also DNS server addresses. They need to be set explicitly to **147.251.4.33** and **147.251.6.10**.
## 2. Security groups
## 2. Security groups{#Security Groups}
All network traffic is blocked in OpenStack by default. You need to explicitly grant access to individual services by utilising Security Groups. This is similar to setting up firewall rules on your router or server. If setup correctly, you can access your virtual machine via SSH connection from your terminal.
## 3. Floating IPs {#nastaveni_routeru}
## 3. Floating IPs {#Floating IPs}
## 4. Router settings {#nastaveni_site}
## 4. Router settings {#Router settings}
1. You can connetct the previously created internal network to the external net by creating a virtual router. To do so, navigate to **Project**>**Network**>**Routers** and hit **"Create router"**.
2. Here you can give your router a name and choose the "public-float-21" network and add it.
3. Click on your router and a settings window will expand. Hit **"Add Interface"**.
4. After expanding the router interface settings window, hit **"Add Interface"**.
5. Select the network you want to connect to the public network.
@@ -11,7 +11,7 @@ Heat is one of the OpenStack projects that enables cloud resource orchestration.
* 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
* 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
...
...
@@ -21,11 +21,8 @@ See the [**vagrant-openstack-example**](https://gitlab.ics.muni.cz/172673/vagra
## [**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)
You can use this guide [**Create Compute Instances from OpenStack**](https://docs.ansible.com/ansible/latest/modules/os_server_module.html). This way was used for testing the MUNI OpenStack. [**Scipion Web Tools clusteru**](https://github.com/RadimPesa/scipion_on_ostack)
