Routers can also be used to route traffic between internal networks. This is an advanced topic not covered in this guide.
</div>
## Orchestration
## Orchestration
...
@@ -101,9 +43,46 @@ os_distro=ubuntu # example
...
@@ -101,9 +43,46 @@ os_distro=ubuntu # example
5. OpenStack will resize instance after start. Image shouldn't contain any empty partitions or free space
5. OpenStack will resize instance after start. Image shouldn't contain any empty partitions or free space
For mor detailed explanation about CLI work with images, please refer to [https://docs.openstack.org/python-openstackclient/pike/cli/command-objects/image.html](https://docs.openstack.org/python-openstackclient/pike/cli/command-objects/image.html).
## Image visibility
In OpenStack there are 4 possible visibilities of particular image: **public, private, shared, community**.
### 1. Public image
**Public image** is an image visible to everyone and everyone can access it.
### 2. Private image
**Private image** is an image visible to only to owner of that image. This is default setting for all newly created images.
### 3. Shared image
**Shared image** is an image visible to only to owner and possibly certain groups that owner specified. How to share an image between project, please read following [tutorial](/gui/#image-sharing-between-projects) below.
### 4. Community image
**Community image** is an image that is accesible to everyone, however it is not visible in dashboard. These images can be listed in CLI via command:
```openstack image list --community```.
This is especially beneficial in case of great number of users who should get access to this image or if you own image that is old but some users might still require that image. In that case you can make set old image and **Community image** and set new one as default.
For more detailed explanation about these properties, go to the following link: [https://wiki.openstack.org/wiki/Glance-v2-community-image-visibility-design](https://wiki.openstack.org/wiki/Glance-v2-community-image-visibility-design).
## Image sharing between projects
## Image sharing between projects
Image sharing allows you to share your image between different projects and then it is possible to launch instances from that image in those projects with other collaborators etc. As mentioned in section about CLI, you will need to use your OpenStack credentials from ```openrc``` or ```cloud.yaml``` file.
Image sharing allows you to share your image between different projects and then it is possible to launch instances from that image in those projects with other collaborators etc. As mentioned in section about CLI, you will need to use your OpenStack credentials from ```openrc``` or ```cloud.yaml``` file.
Then to share an image you need to know it's ID, which you can find with command:
Then to share an image you need to know it's ID, which you can find with command:
```
```
...
@@ -154,7 +133,7 @@ openstack image member list <image_ID>
...
@@ -154,7 +133,7 @@ openstack image member list <image_ID>
When you find ```<ID_project_to_unshare>``` of project, you can cancel access of that project to shared image by command:
When you find ```<ID_project_to_unshare>``` of project, you can cancel access of that project to shared image by command: