Osidle

osidle` analyzes the usage of the different servers (Virtual Machines) in an OpenStack deployment, providing a list of all the servers in OpenStack, along with a score of how much they are used.

In a private cloud, users usually launch VM and forget that they have been started. This happens mainly because the users are not billed for the usage of private resources. But for the owner and the sysadmins, these "launch-and-forgotten" servers are a headache: 1st because the resources are finite, and 2nd because using the resources prevents rebooting the hosting servers (thus interrupting maintenance of the facilities).

Often users overestimate the resources needed for their VMs, but sometimes they are not provided with the appropriate VM flavours to run their applications (e.g. a non-parallel application needs a VM with 8 cores because there are no flavours with 32 Gb. RAM and fewer cores).

The purposes for `osidle` are:
1. to try to detect which servers are candidates to be powered off because they are not used.
1. to try to detect overestimated servers, to try to resize them.
1. to try to detect the lack of flavours with the appropriate amount of resources.

osidle` analyzes the usage of the different servers (Virtual Machines) in an OpenStack deployment, providing a list of all the servers in OpenStack, along with a score of how much they are used.

In a private cloud, users usually launch VM and forget that they have been started. This happens mainly because the users are not billed for the usage of private resources. But for the owner and the sysadmins, these "launch-and-forgotten" servers are a headache: 1st because the resources are finite, and 2nd because using the resources prevents rebooting the hosting servers (thus interrupting maintenance of the facilities).

Often users overestimate the resources needed for their VMs, but sometimes they are not provided with the appropriate VM flavours to run their applications (e.g. a non-parallel application needs a VM with 8 cores because there are no flavours with 32 Gb. RAM and fewer cores).

The purposes for `osidle` are:
1. to try to detect which servers are candidates to be powered off because they are not used.
1. to try to detect overestimated servers, to try to resize them.
1. to try to detect the lack of flavours with the appropriate amount of resources.

osidle` analyzes the usage of the different servers (Virtual Machines) in an OpenStack deployment, providing a list of all the servers in OpenStack, along with a score of how much they are used.

In a private cloud, users usually launch VM and forget that they have been started. This happens mainly because the users are not billed for the usage of private resources. But for the owner and the sysadmins, these "launch-and-forgotten" servers are a headache: 1st because the resources are finite, and 2nd because using the resources prevents rebooting the hosting servers (thus interrupting maintenance of the facilities).

Often users overestimate the resources needed for their VMs, but sometimes they are not provided with the appropriate VM flavours to run their applications (e.g. a non-parallel application needs a VM with 8 cores because there are no flavours with 32 Gb. RAM and fewer cores).

The purposes for `osidle` are:
1. to try to detect which servers are candidates to be powered off because they are not used.
1. to try to detect overestimated servers, to try to resize them.
1. to try to detect the lack of flavours with the appropriate amount of resources.

osidle` analyzes the usage of the different servers (Virtual Machines) in an OpenStack deployment, providing a list of all the servers in OpenStack, along with a score of how much they are used.

In a private cloud, users usually launch VM and forget that they have been started. This happens mainly because the users are not billed for the usage of private resources. But for the owner and the sysadmins, these "launch-and-forgotten" servers are a headache: 1st because the resources are finite, and 2nd because using the resources prevent rebooting the hosting servers (thus interrupting maintenance of the facilities).

Often users overestimate the resources needed for their VMs, but sometimes they are not provided with the appropriate VM flavours to run their applications (e.g. a non-parallel application needs a VM with 8 cores because there are no flavours with 32 Gb. RAM and fewer cores).

The purposes for `osidle` are:
1. to try to detect which servers are candidates to be powered off because they are not used.
1. to try to detect overestimated servers, to try to resize them.
1. to try to detect the lack of flavours with the appropriate amount of resources.

osidle` analyzes the usage of the different servers (Virtual Machines) in an OpenStack deployment, providing a list of all the servers in OpenStack, along with a score of how much they are used.

In a private cloud, users usually launch VM and forget that they have been started. This happens mainly because the users are not billed for the usage of private resources. But for the owner and the sysadmins, these "launch-and-forgotten" servers are a headache: 1st because the resources are finite, and 2nd because using the resources prevent rebooting the hosting servers (thus interrupting maintenance of the facilities).

Often users overestimate the resources needed for their VMs, but sometimes they are not provided with the appropriate VM flavours to run their applications (e.g. a non-parallel application needs a VM with 8 cores because there are no flavours with 32 Gb. RAM and fewer cores).

The purposes for `osidle` are:
1. to try to detect which servers are candidates to be powered off because they are not used.
1. to try to detect overestimated servers, to try to resize them.
1. to try to detect the lack of flavours with the appropriate amount of resources.