Hi Wilson,
The size of your cinder-volumes VG is only 10 GiB and you're trying to
create inside of it a 10 GiB logical volume
cinder-scheduler.log says:
...
Unexpected error while running command.\nCommand: sudo cinder-rootwrap
/etc/cinder/rootwrap.conf lvcreate -n
volume-a577999a-64f3-4ffb-9044-
El 21/06/2014 20:17, "Frans Thamura" escribió:
>
>
> i want to make more common ssh without have to add -i keypair2.pem
>
> any idea?
>
What about using ssh-agent?
Alberto
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Hi,
Debian testing (jessie) is now frozen, so it seems a good time to use it as
a base for an OpenStack deployment. Debian jessie provides OpenStack
Icehouse packages from official repos, backported repos are no longer
needed.
Installation procedure works fine in a setup with OVS and GRE tunnels,
2014-11-09 21:37 GMT+01:00 George Shuklin :
> Try to disable GRO on interfaces. It's well known bug, causing significant
> net performance drop in case of the GRE tunnels.
>
> (Use ethtool)
>
Hi George,
Thanks for your reply, but as mentioned in first message disabling GRO in
physical interfaces
2014-11-10 13:45 GMT+01:00 Akilesh K :
> Hi Alberto,
> May I know the flavor and image you were using to do this test. TSO seems
> to be a method that moves the process of tcp segmentation off to the nic
> card.
>
>
Hi Akilesh,
I was using m1.tiny flavor with 512MiB of RAM and 1 vCPU for all the
Hi,
I'm continuing with testing ...
It seems this issue is related to virtio driver. Virtio driver is used by
default with the option use_virtio_for_bridges=true in nova-compute.conf,
if this option is disabled instances are created with a RTL-8139 network
interface and the bandwidth between it a
Hi Dionisis,
Reading your question I've remembered a python script that generates
OpenStack ER diagrams and I've found it again:
https://coderwall.com/p/pngadg/er-diagram-for-openstack-database
It's really nice and simple, but it needed an update:
https://github.com/albertomolina/openstack-db-s
2016-02-10 8:51 GMT+01:00 Mārtiņš Jakubovičs :
> Thanks,
>
> But how at least I can setup that if I change offering to lower it change
> just CPU and RAM and if root disk size in offering is smaller than actually
> in instance, nova don't try to change it to smaller?
>
>
Hi,
You can try defining
On mié, feb 10, 2016 at 12:41:42 +0200, Mārtiņš Jakubovičs wrote:
> Hello,
>
> Looks like it is not working, when I try to resize instance I receive:
> Server disk was unable to be resized because: Resize to zero disk flavor is
> not allowed.
>
Sorry Mārtiņš, my previous comment wasn't completel
Hi Ken,
I'm using Newton on Debian Stretch with IPv6 prefix delegation (I'm not
tested it from horizon, only from CLI). The configuration was carried out
following the steps described here: http://www.debug-all.com/?p=187
Alberto
___
Mailing list: http:
Hi Manuel,
I'm not a kolla-ansible user, but I suppose that you must modify properly
the templates:
kolla-ansible/ansible/roles/neutron/templates/neutron.conf.j2
kolla-ansible/ansible/roles/neutron/templates/ml2_conf.ini.j2
following the instructions of the link provided.
Regards,
Alberto
Hi Andrew!
AFAIK there's no difference between Liberty and Mitaka nova endpoints
(we're using newton and $(tenant_id)s is still present in the nova
endpoints and it's working properly). It seems to me that the
difference you're showing was introduced in ocata, you can compare the
official doc inst
12 matches
Mail list logo
