Jump to: navigation, search

Difference between revisions of "Blazar/Installation without Devstack"

m (Sergey Lukjanov moved page Climate/Installation without Devstack to Blazar/Installation without Devstack: Climate project has been renamed to the Blazar project due to the possible trademark issues.)
Line 1: Line 1:
 
== Installation guide ==
 
== Installation guide ==
  
This page includes instructions for Climate installation.
+
This page includes instructions for Blazar installation.
  
Download all Climate related repos:
+
Download all Blazar related repos:
  
     git clone https://github.com/stackforge/climate.git
+
     git clone https://github.com/stackforge/blazar.git
     git clone https://github.com/stackforge/climate-nova.git
+
     git clone https://github.com/stackforge/blazar-nova.git
     git clone https://github.com/stackforge/python-climateclient.git
+
     git clone https://github.com/stackforge/python-blazarclient.git
  
 
Install all these projects to your working environment via:
 
Install all these projects to your working environment via:
Line 17: Line 17:
 
     python setup.py develop
 
     python setup.py develop
  
Next you need to configure Climate and Nova. Define /etc/climate/climate.conf file using the following example:
+
Next you need to configure Blazar and Nova. Define /etc/climate/climate.conf file using the following example:
  
 
  [DEFAULT]
 
  [DEFAULT]
 
   
 
   
  host=<climate_host>
+
  host=<blazar_host>
 
   
 
   
 
  os_auth_host=<auth_host>
 
  os_auth_host=<auth_host>
Line 45: Line 45:
 
   
 
   
 
  [database]
 
  [database]
  connection=<path_to_climate.sqlite>
+
  connection=<path_to_blazar.sqlite>
  
Here os_admin_* flags refer to Climate service user. climate_* ones - to admin user created specially to work with physical reservations. If you have no these users, create them via Keystone:
+
Here os_admin_* flags refer to Blazar service user. climate_* ones - to admin user created specially to work with physical reservations. If you have no these users, create them via Keystone:
  
 
  keystone user-create --name=climate --pass=<service_password> --tenant_id=<service_tenant_id> --email=climate@example.com
 
  keystone user-create --name=climate --pass=<service_password> --tenant_id=<service_tenant_id> --email=climate@example.com
Line 68: Line 68:
 
Restart nova-api to use new configuration file.
 
Restart nova-api to use new configuration file.
  
Climate uses Keystone trusts to commit actions on behalf of user created lease. That’s why we need to create identityv3 service with appropriate endpoints:
+
Blazar uses Keystone trusts to commit actions on behalf of user created lease. That’s why we need to create identityv3 service with appropriate endpoints:
  
 
  keystone service-create --name keystonev3 --type identityv3 --description "Keystone Identity Service v3"
 
  keystone service-create --name keystonev3 --type identityv3 --description "Keystone Identity Service v3"
Line 78: Line 78:
 
  keystone endpoint-create --region <region> --service climate --publicurl "<auth_protocol>://<climate_host>:1234/v1" --adminurl "<auth_protocol>://<climate_host>:1234/v1"
 
  keystone endpoint-create --region <region> --service climate --publicurl "<auth_protocol>://<climate_host>:1234/v1" --adminurl "<auth_protocol>://<climate_host>:1234/v1"
  
To start Climate services use:
+
To start Blazar services use:
  
 
  climate-api
 
  climate-api
 
  climate-manager
 
  climate-manager
  
Now you can use python-climateclient to communicate with Climate.
+
Now you can use python-blazarclient to communicate with Blazar.

Revision as of 20:51, 5 June 2014

Installation guide

This page includes instructions for Blazar installation.

Download all Blazar related repos:

   git clone https://github.com/stackforge/blazar.git
   git clone https://github.com/stackforge/blazar-nova.git
   git clone https://github.com/stackforge/python-blazarclient.git

Install all these projects to your working environment via:

   python setup.py install

or

   python setup.py develop

Next you need to configure Blazar and Nova. Define /etc/climate/climate.conf file using the following example:

[DEFAULT]

host=<blazar_host>

os_auth_host=<auth_host>
os_auth_port=<auth_port>
os_auth_protocol=<http, for example>
os_admin_username=<username>
os_admin_password=<password>
os_admin_tenant_name=<tenant_name>

[manager]
plugins=basic.vm.plugin,physical.host.plugin

[virtual:instance]
on_start=on_start
on_end = create_image, delete

[physical:host]
on_start=on_start
on_end = on_end
climate_username=<username>
climate_password=<password>
climate_tenant_name=<tenant_name>

[database]
connection=<path_to_blazar.sqlite>

Here os_admin_* flags refer to Blazar service user. climate_* ones - to admin user created specially to work with physical reservations. If you have no these users, create them via Keystone:

keystone user-create --name=climate --pass=<service_password> --tenant_id=<service_tenant_id> --email=climate@example.com
keystone user-role-add --tenant-id <service_tenant_id> --user-id <climate_user> --role-id <admin_role>

And the same procedure for special admin user to work with physical reservations.

Next you need to configure Nova. If you want to use virtual reservations, please add the following lines to nova.conf file:

osapi_compute_extension = nova.api.openstack.compute.contrib.standard_extensions
osapi_compute_extension = climatenova.api.extensions.default_reservation.Default_reservation
osapi_compute_extension = climatenova.api.extensions.reservation.Reservation

If you want to use physical reservations add these ones:

scheduler_available_filters = nova.scheduler.filters.all_filters
scheduler_available_filters = climatenova.scheduler.filters.climate_filter.ClimateFilter
scheduler_default_filters=RetryFilter,AvailabilityZoneFilter,RamFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,ClimateFilter

Restart nova-api to use new configuration file.

Blazar uses Keystone trusts to commit actions on behalf of user created lease. That’s why we need to create identityv3 service with appropriate endpoints:

keystone service-create --name keystonev3 --type identityv3 --description "Keystone Identity Service v3"
keystone endpoint-create --region <region> --service keystonev3 --publicurl "<auth_protocol>://<auth_host>:5000/v3" --adminurl "<auth_protocol>://<auth_host>:35357/v3" --internalurl "<auth_protocol>://<auth_host>:5000/v3"

And, finally, we need to create reservation service in Keystone with its endpoints:

keystone service-create --name climate --type reservation --description “OpenStack reservation service.”
keystone endpoint-create --region <region> --service climate --publicurl "<auth_protocol>://<climate_host>:1234/v1" --adminurl "<auth_protocol>://<climate_host>:1234/v1"

To start Blazar services use:

climate-api
climate-manager

Now you can use python-blazarclient to communicate with Blazar.