Ask Your Question

Damia's profile - activity

2016-09-16 06:44:28 -0500 received badge  Enthusiast
2016-09-08 20:35:32 -0500 answered a question How to disable Private Open Stack CSRF token validation.

In your openstack_dashboard directory you should find the settings.py file. On it, there are several options related to session cookies, one being the django cookie middleware.

Find the next line and change it to False:

SESSION_COOKIE_SECURE = False

Remember to restart your website frontend process (apache2,httpd,nginx..)

2016-09-08 19:20:16 -0500 answered a question How to backup and restore keystone db ?

Hi Tamil,

The ops-guide covers the backups on all items, one of them being the mysql databases:

http://docs.openstack.org/ops-guide/ops-backup-recovery.html (http://docs.openstack.org/ops-guide/o...)

The standard approach is using mysqldump in this fashion:

# mysqldump --opt keystone > keystone.sql

To recover, simply stop all the process related to keystone and use this command to replace the database:

# mysql keystone < keystone.sql

In addition, there is a project called Freezer that can be used to schedule backups for all items that require it on OpenStack:

https://wiki.openstack.org/wiki/Freezer

2016-09-08 10:01:31 -0500 answered a question how to reserve floating ip

Hi Sudarshan,

I see two cases:

  • Want to reserve the IP for later.
  • Don't want the IP in the floating IP pool.

If you want to later use those IP within OpenStack as floating-ip, then my recommendation is that you add them to a project that doesn't have users (e.g. admin, services).

Using the neutron CLI, you can create a specific floating ip for that tenant:

neutron floatingip-create --tenant-id xxxyyy --floating-ip-address x.x.x.x FLOATING_NETWORK

Once you have need of them, you can release them and associate them with the preferred servers.

If instead those IP are already in use or should be reserved for external devices, you should create the subnet in the next fashion:

E.g.: I want to allow users to consume the next IPs 192.168.1.11 to 192.168.1.29, and 192.168.1.45 to 192.168.1.150

When I create the subnet I will use the next command:

neutron subnet-create --allocation-pool start=192.168.11,end=192.168.1.29 --allocation pool start=192.168.1.45,end=192.168.1.150 --enable-dhcp --gateway 192.168.1.1 --tenant-id ADMIN EXT_NET 192.168.1.0/24

I can also simply modify an existing subnet using the neutron subnet-update in a similar fashion.

Reference: http://docs.openstack.org/cli-reference/neutron.html (http://docs.openstack.org/cli-referen...)

In Mitaka subnet pools are also available, check them here: http://docs.openstack.org/developer/neutron/devref/address_scopes.html (http://docs.openstack.org/developer/n...)

2016-09-08 05:13:29 -0500 received badge  Supporter (source)