Can anyone advise on or provide a documentation for Octavia installation ?
Rgds
Yngvi
-Original Message-
From: Yngvi Páll Þorfinnsson
Sent: 23. júní 2016 15:42
To: Turbo Fredriksson ; openstack@lists.openstack.org
Subject: Re: [Openstack] Create instance fails on creating block device
On Jun 23, 2016, at 4:30 PM, Eugen Block wrote:
> They are running because you didn't stop the services, you just disabled them.
I kind'a expected a disable to stop the service.. But what if I wanted to
stop only ONE service (of several)? For example the "nfs" backend but leave
the "lvm" online.
meone please correct me, if I'm wrong on this
Cheers
Yngvi
-Original Message-
From: Turbo Fredriksson [mailto:tu...@bayour.com]
Sent: 23. júní 2016 13:36
To: openstack@lists.openstack.org
Subject: Re: [Openstack] Create instance fails on creating block device - Block
Device Mapp
"rbd"?
It's a different storage backend, something like a network RAID. But
don't mind it right now ;-)
But even after disabling them, they're still show as
"status=disabled,state=up"
They are running because you didn't stop the services, you just
disabled them. You could stop them for
I'm starting to think that it might have something to do with the
networking after all:
- s n i p -
2016-06-23 15:52:13.775 25419 DEBUG nova.compute.manager
[req-87a08e39-96ac-4c23-96dd-5227c972b865 0b7e5b0653084efdad5d67b66f2cf949
2985b96e27f048cd92a18db0dd
03aa23 - - -] [instance: d75b
On Jun 23, 2016, at 2:10 PM, Turbo Fredriksson wrote:
> But even after disabling them, they're still show as
> "status=disabled,state=up"
> with a "cinder service-list".. ?
I tried anyway, but creating a volume (empty or from an image) gave
the host field as empty. And the status was Error!
So
On Jun 23, 2016, at 12:26 PM, Eugen Block wrote:
> /etc/cinder/cinder.conf:enabled_backends = rbd--> that's what I use
> currently
"rbd"?
> I'm not sure if it would work, it's been a while since I used local storage,
> but if you just comment the enabled_backend option out and restart cind
How can I create a local volume?
You have probably configured your cinder.conf to use lvm as backend:
control1:~ # grep -r enabled_backends /etc/cinder/
/etc/cinder/cinder.conf:#enabled_backends = lvm
/etc/cinder/cinder.conf:enabled_backends = rbd--> that's what I
use currently
I'm not
Now that my authentication problems seems to be fixed, it's back on track with
trying to boot my first instance..
On Jun 21, 2016, at 3:17 PM, Cynthia Lopes wrote:
> If not, the command is: openstack volume create --size (size in GB) --image
> (image name or id) volume_name
> Just for info the c
Hi,
First of all, think dis question did no get answered:
-I'll try that thanx. How do you do that with the "openstack" command?
If not, the command is: openstack volume create --size (size in GB) --image
(image name or id) volume_name
Just for info the cinder command was not exact, it should b
If it was the flavor, you would get different errors, something like
"flavor disk too small" or "out of memory". Again, I recommend to
launch an instance on local disk to see if that is working, then fix
the iscsi issue to be able to create volumes at all, first empty
volumes, then from an
On Jun 21, 2016, at 12:19 PM, Abhishek Shrivastava wrote:
> Have you tried any other flavors?
No, I never saw the point. The resources I specified was well within
the flavors rules. And the error was "Block Device Mapping is Invalid"
I can not see how changing the flavor would change that.
--
S
Have you tried any other flavors?
For instance if you are creating a 1GB volume then you can go for flavor
m1.tiny flavor.
So try creating a VM having boot volume size 1GB and use flavor m1.tiny
and see if it works.
On Tue, Jun 21, 2016 at 4:36 PM, Turbo Fredriksson wrote:
> On Jun 21, 2016,
On Jun 21, 2016, at 11:40 AM, Abhishek Shrivastava wrote:
> The first thing I want to know
>
> - Which VM are you creating(i.e; which OS image are you taking)?
I've tried both the CirrOS and Debian GNU/Linux Jessie images.
http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img
Hi Turbo,
The first thing I want to know
- Which VM are you creating(i.e; which OS image are you taking)?
- What size are you using and all?
Secondly,
- Which flavor are you using for VM creation.?
On Tue, Jun 21, 2016 at 12:56 PM, Eugen Block wrote:
> Can't you boot an instance wi
Can't you boot an instance without cinder?
Don't know, can I??
Well, you should ;-) How do you try to boot your instance, from CLI or
Horizon? If it's Horizon, you would have to NOT klick the button
"Create a new volume --> Yes" ;-) If it's CLI it's sufficient to only
execute "nova boot
On Jun 20, 2016, at 3:27 PM, Eugen Block wrote:
> Can't you boot an instance without cinder?
Don't know, can I??
> You could edit nova.conf to use local file system, just to have a running
> instance. If that works you can switch to another backend.
How?
> cinder create --image --name
I'l
Can't start any instances because I can't create volumes
Can't you boot an instance without cinder? You could edit nova.conf to
use local file system, just to have a running instance. If that works
you can switch to another backend.
How do i do that from the shell?
cinder create --image
On Jun 20, 2016, at 1:01 PM, Eugen Block wrote:
> Is it possible to create an empty volume?
Yes.
> try to attach it to a running instance
Can't start any instances because I can't create volumes.. :(
> Do you see the iscsi session on your compute node?
No.
> Then you could try to create a vo
Is it possible to create an empty volume? Without nova or glance, just
a volume. If that works and the volume is not deleted immediately, you
could try to attach it to a running instance to see if nova can handle
it.
Do you see the iscsi session on your compute node?
Then you could try to cr
On Jun 17, 2016, at 2:38 PM, Eugen Block wrote:
> I don't even see the attempt to attach it. If it works, these steps should be
> processed:
Neither can I! And running with debugging doesn't
show anything either :(
The log literally say (no changes, no additions or removal!):
- s n i p ---
Then I would turn on debug logs for cinder and see if there is more
information on why it's deleting the volumes before attaching them. I
don't even see the attempt to attach it. If it works, these steps
should be processed:
- Created volume successfully.
- Initialize volume connection co
On Jun 17, 2016, at 1:12 PM, Eugen Block wrote:
> Have you nova-compute.logs?
They don't say a thing, so I'm guessing it never gets
that far.
If I'm quick, i can see the LVM volume being created
successfully (which the log also indicates).
___
Mailing
I had also some trouble getting volume backed instances to boot. I use
xen hypervisor and found out that the instance was assigned a device
name of "vda" (which is set by default) instead of xvda, I filed a bug
report for this. Have you nova-compute.logs? I can't find them in your
link. The
I'm trying my newly installed Openstack system and I'm getting
problem in starting my first instance.
- s n i p -
Build of instance 5193c2d9-0aaf-4f84-b108-f6884d97b571 aborted: Block Device
Mapping is Invalid.
File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1926, in
25 matches
Mail list logo
