Open Stack

On Sat, Mar 14, 2015 at 12:18 PM, Nikesh Kumar Mahalka <
nikeshmahalka at vedams.com> wrote:

> I am using below local.conf file
> http://paste.openstack.org/show/192320/
>
> Actually i am deploying SOS-CI.
> I am using ubuntu 14.04 VM having 150 GB sda and 24GB RAM and 8 core cpu.
> Installing devstack is very fast on this VM and nova instances are
> creating on getting desired gerrit cinder events,
>
> But nova instances performance is very slow,
> I am using official trusty(ubuntu 14.04) image (
> http://uec-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
> )
> for nova instances.
> I am using flavor-id 3 for nova instances.
> Installing devstack in nova instance is taking 8-9 hrs.
>
> so wondering how to resolve this
>
>
>
> Regards
> Nikesh
>
>
> On Sat, Mar 14, 2015 at 8:10 PM, John Griffith <
> john.griffith at solidfire.com> wrote:
>
>>
>>
>> On Sat, Mar 14, 2015 at 8:22 AM, Nikesh Kumar Mahalka <
>> nikeshmahalka at vedams.com> wrote:
>>
>>> from where devstack instances consumes space for rootdisk,
>>> if i have a ubuntu setup with sda 150gb.
>>>
>>> devstack is creating two volume groups on loop-back files of 10gb each
>>> (stack-volumes-default and stack-volumes-lvmdriver-1).
>>>
>>> are they consume these volume groups for nova instances root-disk?
>>>
>>>
>>> Regards
>>> Nikesh
>>>
>>> _______________________________________________
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to     : openstack at lists.openstack.org
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>> Those loopbacks are specifically for Cinder (well, the
>> stack-volume-default is actually for "nothing" right now but that's a whole
>> separate debate I have had with some folks and have given up on).
>>
>> Ephemeral Nova instances by default in devstack are going to consume qcow
>> files in /opt/stack/data/nova/instances (assuming you're still using the
>> same local.conf I gave you a while back).
>>
>> Thanks,
>> John
>>
>>
> Hi Nikesh,

I believe I already went through this with one of your coworkers via IRC a
week or so ago.  Check and make sure you're not using QEMU and that you're
using KVM for your virtualization.  This of course assumes you're on a
modern processor that support nested virt.  To check this, just set:
virt_type=kvm in your nova.conf.

You may need to enable virt settings on your physical machines bios.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20150314/65f1e271/attachment.html>