Some companies may deploy OpenStack clouds but without the Horizon Dashboard interface, and therefore you may wish to deploy your own horizon instance, either on a hosted VM of the OpenStack infrastructure, or why not on your own computer? Well this is possible.
However, your concern is that http might be insecure… especially if hosted on a VM or machine accessible from the Internet. So you want an SSL connection.
The issue is that SSL certificates can cost some money, but for personal usage, self-signed certificates will do the Job for no costs, and
easy-rsa will make their management easy :-)
Note: even though you will run your own Horizon instance, you will not have extra privileges, it will just add your favorite “life easy-making GUI” on top of OpenStack :-)
In this article, we will show you how to store your backups in the Cloudwatt object store. For this, we’ll be using Duplicity as a backup tool:
OpenStack allows its users to manage VMs, volumes, and any other OpenStack resources through the Horizon web interface or by using OpenStack’s numerous APIs. However, when a user wants to discard his whole project, including all of its resources, he has to delete each resource individually. There is no equivalent (to my knowledge) of Linux’s
rm -rf * command for an OpenStack project. Worse, if an administrator deletes a project without deleting its resources, they will still be running, while not being usable by anyone. And it is very difficult for an administrator to find these orphan resources in order to free them.
The devstack project is an interesting tool to deploy a complete OpenStack development environment from source code. I’ve been using it from one year in my development activities on Neutron. For that, I set up an isolated VM (libvirt or VirtalBox through Vagrant), but I found that environment isn’t very efficient (too slow and uses lot of memory). Furthermore, when you developing network stack, you need to set up more than one node (three is a good number to test network virtualization). This is why I try to set up that environment into containers (LXC).
The main goal of this howto is to help Cloudwatt users to migrate their OpenStack resources from one OpenStack platform to another.
The first step to do that, is to list all the resources that are deployed/available in the project. This can be done through the use of provided script described in section “How to list all my OpenStack resources”.
The second step is to snapshot the instances whose base image were customized, download these snapshots in order to re-upload them to the new environment. Detailed description concerning these operations, is presented in section “How to migrate my instances”.
The third step is to migrate OpenStack Block Storage resources (volumes) that is described in section “How to migrate my volumes”
And the last thing to do, is to re-create, via Dashboard, CLI or bash scripting, the same infrastructure/resources on the new platform. This step will not be described in this howto, nevertheless the results of the script listing tenant resources (from step one) will be very useful as they help users to remember all resource details.
Here, you will find information about our APIs and infrastructure, OpenStack and related events organised by us. You can also find user guides, tutorials and documentation.
All articles are written by members of our tech team (developers, engineers and DevOPS). Examples of their scripts are available on GitHub.
If you would like more information on an article, or you would like further clarification, please leave a comment with your question and we will reply ASAP.