openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #04620
Re: create/attach volume in openstack
Hi Haynes -
We just updated the documentation after learning that when you're running
KVM, the actual device name in the guest will be different than the one
specified in the attach command. (doc bug
link<https://bugs.launchpad.net/openstack-manuals/+bug/868595>)
Thanks Razique Mahroua for making the fixes and David Kranz for pointing it
out.
Vish's explanation is: "You can specify a device name to the KVM hypervisor,
but the actual means of attach to the guest is over a virtual pci bus. When
the guest sees a new device on the pci bus, it picks the next available name
(which in most cases is /dev/vdc) and the disk will show up there."
Hope this helps. Maybe the docs are only minutes behind the questions? Nah,
impossible. :)
Anne
*Anne Gentle*
anne@xxxxxxxxxxxxx
my blog <http://justwriteclick.com/> | my
book<http://xmlpress.net/publications/conversation-community/>|
LinkedIn <http://www.linkedin.com/in/annegentle> |
Delicious<http://del.icio.us/annegentle>|
Twitter <http://twitter.com/annegentle>
On Mon, Oct 10, 2011 at 12:56 AM, <haynes.davis@xxxxxxxxxxxxx> wrote:
> Thanks for the replies.
>
> My actual question was regarding euca-attach-volume. I could run
> euca-attach-volume from host successfully. But from guest I could not find a
> new disk.
>
> Regards,
> Haynes
>
>
> -----Original Message-----
> From: openstack-bounces+haynes.davis=accenture.com@xxxxxxxxxxxxxxxxxxx[mailto:
> openstack-bounces+haynes.davis=accenture.com@xxxxxxxxxxxxxxxxxxx] On
> Behalf Of Pedro Navarro Pérez
> Sent: Friday, October 07, 2011 5:47 PM
> To: Jorge Luiz Correa
> Cc: openstack@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Openstack] create/attach volume in openstack
>
> Typing the command:
>
> "nova flavor-list" you will have the output describring the local
> storage allocated on each flavor
>
> On Fri, Oct 7, 2011 at 1:10 PM, Jorge Luiz Correa <correajl@xxxxxxxxx>
> wrote:
> > I've read somewhere that flavors (different types of VMs, like m1.tiny,
> > m1.small etc) have some disk space. This disk space is available as a
> device
> > like /dev/vbd. Moreover, it seems the volume attached to a VM isn't
> > predictable in what device it will be attached, so we need to search for
> > them in the VM. I think that some scripts could be placed in some
> packages
> > to do it for us.
> > Just what I read in my recently studies.
> > Regards!
> > :)
> >
> > On Fri, Oct 7, 2011 at 6:54 AM, <haynes.davis@xxxxxxxxxxxxx> wrote:
> >>
> >> Hi,
> >>
> >>
> >>
> >> Have any one successfully create/attach volume. I have installed a
> >> stackops multinode setup. I had created instance as m1.small and I see
> the
> >> instances are having /dev/vdb with 20GB by default.
> >>
> >>
> >>
> >> And when I try euca-create-volume there is no error. Also
> >> euca-attach-volume is done without any error. But actually I am not able
> to
> >> attach any more volume to the instance. Even in the admin guide I see
> volume
> >> was created for 7 GB but fdisk -l shows vdb is of 21.5GB which would
> have
> >> been there in the instance already. Does m1.small creates an instance
> with
> >> second partition of 20GB?
> >>
> >>
> >>
> >> Regards,
> >>
> >> Haynes.
> >>
> >>
> >>
> >>
> >>
> >> ________________________________
> >> This message is for the designated recipient only and may contain
> >> privileged, proprietary, or otherwise private information. If you have
> >> received it in error, please notify the sender immediately and delete
> the
> >> original. Any other use of the email by you is prohibited.
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~openstack
> >> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~openstack
> >> More help : https://help.launchpad.net/ListHelp
> >>
> >
> >
> >
> > --
> > - MSc. Correa, J.L.
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openstack
> > More help : https://help.launchpad.net/ListHelp
> >
> >
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the email by you is prohibited.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
References