# Extended OpenStack and OpenNebula Functionalities

* Improved scheduling for allocation of resources by popular open source Cloud platforms, i.e. OpenStack and OpenNebula.
  * Enhancements will address both better scheduling algorithms and support for spot-instances. 
  * We will also support dynamic partitioning of resources among “traditional batch systems” and Cloud infrastructures (for some LRMS).
* Support for standards in IaaS resource orchestration engines through the use of the TOSCA standard.
  * This overcomes the portability and usability problem that ways of orchestrating resources in Cloud computing frameworks widely differ among each other.
* Improved IaaS orchestration capabilities for popular open source Cloud platforms, i.e. OpenStack and OpenNebula.
  * Enhancements will include the development of custom TOSCA templates to facilitate resource orchestration for end users, increased scalability of deployed resources and support of orchestration capabilities for OpenNebula.

Components:

* OpenStack support for INDIGO developments (AAI, preemptible instances, etc.)
  * [OpenStack preemptible instances support (OpenStack Preemptible Instances Extensions)](/indigo-datacloud-releases/chapter2/all/eoof2/opie2.md)
  * OpenStack support for INDIGO AAI
    * [OpenStack Identity Authentication Library support for INDIGO AAI developments](/indigo-datacloud-releases/chapter2/all/eoof2/keystone_library2.md)
    * [Keystone AAI support](https://github.com/indigo-dc/indigo-datacloud-releases/tree/23e3ac652361e53b94532886bd37d707e297ab05/indigo2/keystone_aai_support2.md)
* [Docker driver for OpenStack Nova](/indigo-datacloud-releases/chapter2/all/eoof2/nova-docker2.md)
* [Heat-Translator tool is aimed to translate non-heat templates to OpenStack Heat Orchestration Template (HOT)](/indigo-datacloud-releases/chapter2/all/eoof2/heat-translator2.md)
* [Docker support for OpenNebula](/indigo-datacloud-releases/chapter2/all/eoof2/onedock2.md)
* [Sync between INDIGO Docker-hub, ONEDock and nova-docker](/indigo-datacloud-releases/chapter2/all/eoof2/reposync2.md)
* [OpenStack Client](https://github.com/indigo-dc/indigo-datacloud-releases/tree/23e3ac652361e53b94532886bd37d707e297ab05/indigo2/python-osclient1.md) & [Nova Client](https://github.com/indigo-dc/indigo-datacloud-releases/tree/23e3ac652361e53b94532886bd37d707e297ab05/indigo2/python-nova2.md)

## Installation and Configuration

After setting the INDIGO-DC repositories as explained in the [Generic Installation & Configuration Guide](/indigo-datacloud-releases/chapter2/generic_installation_and_configuration_guide_2.md):

* On CentOS 7, as root or otherwise using sudo:\
   `$ yum install -y https://repos.fedorapeople.org/openstack/openstack-liberty/rdo-release-liberty-5.noarch.rpm`\
   `$ yum clean all`\
   `$ yum install opie`\
   or\
   `$ yum install python2-keystoneauth1` \
   or \
   `$ yum install python-nova-docker`\
   or\
   `$ yum install python2-novaclient` or `$ yum install python-openstackclient`\
   or \
  &#x20;`$ yum install indigo-dc-reposync`<br>
* On Ubuntu 16.04, as root or otherwise using sudo:\
  &#x20;`$ add-apt-repository cloud-archive:liberty`\
  &#x20;`$ apt-get update`\
  &#x20;`$ apt-get install opie`\
  &#x20;or\
  &#x20;`$ apt-get install python3-keystoneauth1` or `$ apt-get install python-keystoneauth1`\
  &#x20;or\
  &#x20;`$ apt-get install python-nova-docker` \
  &#x20;or \
  &#x20;`$ apt-get install python-novaclient` or `$ apt-get install python-openstackclient`\
  &#x20;or \
  &#x20;`$ apt-get install reposync`
* For more details regarding individual services configuration please follow the links above for the respective components


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://indigo-dc.gitbook.io/indigo-datacloud-releases/chapter2/all/eoof2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.