Hi all,
I was wondering when the manual sync of Cinder code to Nova-volume will
happen? See comment from Vish here:
https://review.openstack.org/#/c/11239/
Thanks a lot,
Avishay
___
Mailing list: https://launchpad.net/~openstack
Post to : opensta
Hi all,
I had a few questions about snapshot support in Cinder:
1) a. Why is a snapshot a fundamentally different entity than a volume?
b. Is it because some back-ends don't support the same set of operations
on snapshots?
c. Is this what the snapshot-to-volume operation was meant to achieve
John Griffith wrote on 08/11/2012 19:58:39:
> Hi Avishay,
>
> So we have plans to improve some of this in the Grizzly release,
> here's a few thoughts:
> >> a. Why is a snapshot a fundamentally different entity than a volume?
> I've asked this question a number of times myself :) There are a
> nu
John Griffith wrote on 11/11/2012 17:01:37:
> Hey Avishay,
>
> >>I guess I'm still confused about what a snapshot is
> >>in OpenStack. Currently you can't really do anything with them via
> >>OpenStack.
> Sure you can, you can use them to create a new volume. They make a
> good backup mechanism
Chuck Thier wrote on 12/11/2012 21:25:32:
> Top posting to give some general history and some thoughts.
>
> Snapshots, as implemented currently in cinder, are derived from the
> EBS definition of a snapshot. This is more of a consistent block
> level backup of a volume. New volumes can be create
Hi all,
Currently, CHAP secrets are managed by Cinder, and passed to Nova for use
when attaching volumes. This means that unless the communication is
encrypted, or a separate trusted network is used, CHAP secrets can be
sniffed on the wire.
Opinions?
Thanks,
Avishay
___
openstack-bounces+avishay=il.ibm@lists.launchpad.net wrote on
01/11/2013 06:01:20 PM:
> Just to add a little to Sajid's response, there is of course a
> default LVM implementation for Cinder/Block Storage in addition to
> the supported back ends that were mentioned.
Just to add a bit more, the
Vibhu,
What Cinder did here is:
1) Downloaded the qcow2 file to /tmp
2) Tried to convert the qcow2 file to raw (reading from /tmp and writing to
the logical volume)
The problem is that your image takes more space with raw format, and that
is why it is failing. Basically, qcow2 does not allocate s
Benoit,
openstack-bounces+avishay=il.ibm@lists.launchpad.net wrote on
01/29/2013 10:56:33 AM:
> Hello,
>
> I have an openstack installation with 1 controller node, 1 network
> node and 2 compute node, configured with GRE tunnel for the network,
> and NFS backend for volumes.
>
> I'd like to cr
Lei Zhang wrote on 01/30/2013 04:39:22 PM:
> I also have a question. What's the requirement for the image? I
> found nothing int the doc.
Hi,
The requirements that I can think of off the top of my head are:
1. The image should be bootable
2. The image is converted to raw before being written to t
openstack-bounces+avishay=il.ibm@lists.launchpad.net wrote on
01/31/2013 12:37:07 AM:
> From: Tom Fifield
> To: openstack@lists.launchpad.net,
> Date: 01/31/2013 12:38 AM
> Subject: Re: [Openstack] List of Cinder compatible devices
> Sent by: openstack-bounces+avishay=il.ibm@lists.launchpa
-1
I'm sorry to do that, and it really has nothing to do with Ollie or his
work (which I appreciate very much). The main reason is that right now
Cinder core has 8 members:
1. Avishay Traeger (IBM)
2. Duncan Thomas (HP)
3. Eric Harney (RedHat)
4. Huang Zhiteng (Intel)
5. John Griffith (Soli
12 matches
Mail list logo
