Hello,
Samuel Winchenbach wrote as an answer to Haitao Jiang:
> I
> agree with Logan that it is personal preference.
...
> I am sure for every complaint I have about Ubuntu someone has an equal
> complaint about CentOS.
Samuel is right. Here is an example for such a "complaint":
Two or three
Hi everybody!
1) AFAIK, for creating an instance there should be a kind of "template", which
contains settings for instance, like what volume to attach, what ip address,
what image to use, etc. So that when creating an instance you don't have to
configure it for every instance. Is there any i
On 14 July 2013 23:30, comiqadze wrote:
>
>
> Hi everybody!
>
> 1) AFAIK, for creating an instance there should be a kind of "template",
> which contains settings for instance, like what volume to attach, what ip
> address, what image to use, etc. So that when creating an instance you don't
> h
Thanks,
As I reviewed the configuration of Heat is complicated as itself, since it's
ultimate for creation of "instances, floating ips, volumes, security groups,
users, etc", I thought there will be a template only for instances, something
simpler. But, ok, I can proceed without it.
When I crea
Yes, it should be, but seems not at least in grizzly. Any update of
Ceilometer?
Best Regards
-- Ray
On Sun, Jul 14, 2013 at 11:04 AM, Haomai Wang wrote:
> I think Statistics should be find in Ceilometer. Ceilometer may provide
> with
> enough information you need.
>
> Best regards,
> Haomai Wan
I do this，and the dhcp-agent.log have no error , but my vm still do not have IP
any else I can do for this?
thanks!
ttjiang
From: Arindam Choudhury
Date: 2013-07-12 05:18
To: openstack
Subject: Re: [Openstack] VM do not get ip when use quantum
Hi,
I had the same problem. I found a solution
I use devstack (Grizzly/stable). I have been trying to use a different
volume driver by muncommenting and modifying the below line in cinder.conf
under etc/cinder
# Driver to use for volume creation (string value)
#volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
But when VolumeManager is lo
Yes, that's the default driver. See cinder/volume/manager.py
volume_manager_opts = [
cfg.StrOpt('volume_driver',
default='cinder.volume.drivers.lvm.LVMISCSIDriver',
help='Driver to use for volume creation'),
]
Best Regards
-- Ray
On Mon, Jul 15, 2013 at 12:51 PM
Ray
I am wondering why I see the default driver even after I changed the entry
in cinder.conf. I un-commented the line for volume_driver and changed the
driver name. I tried to print volume driver in the __init__ and I see it
still pointing to LVMISCSIDriver. It seems I am missing something and it
Hi,
We have a reasonably large deployment with nova cells and we are having issues
consuming messages fast enough at the top level due to all the instance updates
etc.
We've done some tuning to some of the periodic tasks but users can trigger
hundreds of messages to be sent upwards.
It looks l
10 matches
Mail list logo
