Hi Ondrej,
the following spec tries to address the issue that you described.
https://review.openstack.org/#/c/508133/
Let me know if you have comments/suggestions.
cheers,
Belmiro
On Fri, Jan 12, 2018 at 2:31 PM, Ondrej Vaško
wrote:
> Hello guys,
>
> I am dealing with one issue and that is a q
Hi Georgios,
probably the problem is related with quotas. For some reason they were not
sync when you deleted the instances.
To confirm this, you can increase your quota and then check you can create
new instances.
If you are using Newton you can use "nova-manage project
quota_usage_refresh" to fi
Hi,
you can use:
enable_new_services = False
With this option new services will be disabled when added.
There is also a proposed change to include a default disabled reason for
these services.
See: https://review.openstack.org/#/c/136645/
Belmiro
---
CERN
On Tuesday, January 13, 2015, gustavo
Hi Martinx,
currently nova only supports "fallocate" to preallocate space.
Use the confirmation option "preallocate_images=space".
"preallocation=metadata" is mentioned in
https://blueprints.launchpad.net/nova/+spec/preallocated-images
as future work.
Belmiro
-
d with the cache) but
we expect that OpenStack will behave in the same way.
Anyone running OpenStack in Mysql 5.6?
thanks,
Belmiro
------
Belmiro Moreira
CERN
IRC: belmoreira
___
Mailing list: http://lists.openstack.o
ds,
> Bill Owen
> billo...@us.ibm.com
> GPFS and OpenStack
> 520-799-4829
>
>
> [image: Inactive hide details for Belmiro Moreira ---03/05/2014 01:31:54
> PM---Hi, in our cinder setup we would like to have different v]Belmiro
> Moreira ---03/05/2014 01:31:54 PM---Hi, in our cin
Hi,
in our cinder setup we would like to have different volume types associated
to different qos. For example: standard, high_iops.
If the user doesn't specify explicitly the volume type when it creates the
volume in our use case it should default to one. "standard" for example.
I can't find a
; Date: Sat, Feb 1, 2014 at 5:09 PM
> Subject: Re: [Openstack] nova unique name generator middleware
> To: Belmiro Moreira
>
>
> Since I am relatively new to the guts of OpenStack this might be an off base
> suggestion but why is this even OpenStack's problem vs. somethi
Hi,
in our case we have a network DB were all VMs are registered.
We just check if the name provided by the user don’t conflict.
Belmiro
On Feb 1, 2014, at 20:19 , Craig J wrote:
> Hi,
>
> In our OpenStack environment, we have the need to enforce unique names for
> each VM. Long story short,
