+1
-Lokesh
On Mon, Sep 2, 2013 at 11:33 AM, Sylvain Bauza sylvain.ba...@bull.netwrote:
Hi Murali,
Le 02/09/2013 15:19, Murali Balcha a écrit :
I am not an expert in Heat but the way I understood the Heat project is that
it is an orchestration layer that instantiate a composite
On 01/09/13 23:11, Alex Rudenko wrote:
Hello everyone,
I would like to ask a question. But, first of all, I would like to say
that I'm new to OpenStack so the question might be irrelevant. From what
I've understood, the idea is to back up an entire stack including VMs,
volumes, networks etc.
I am not an expert in Heat but the way I understood the Heat project is that it
is an orchestration layer that instantiate a composite application based on a
template definition. The template may identify the vms, networks and storage
resources needed to instantiate the composite application.
Hi Murali,
Le 02/09/2013 15:19, Murali Balcha a écrit :
I am not an expert in Heat but the way I understood the Heat project is that it
is an orchestration layer that instantiate a composite application based on a
template definition. The template may identify the vms, networks and storage
Dear All,
This is a great discussion. If I understand this correctly, this is a proposal
for data protection as a whole for the OpenStack cloud, however this is not yet
an official incubation request. We are having a good discussion on how we can
better serve the adoption of OpenStack.
Hello everyone,
I would like to ask a question. But, first of all, I would like to say that
I'm new to OpenStack so the question might be irrelevant. From what I've
understood, the idea is to back up an entire stack including VMs, volumes,
networks etc. Let's call the information about how these
Hi murali,
A question I am wondering,
How much of the rashka code exists? It looks like from the design docs that a
lot of it might be working already??
I do understand and wonder what u think about what caitlin stated and how/if
rashka will solve these types of overlap issues (especially
Hi Murali,
Thanks for answering. I think the issues you raised indeed make sense, and
important ones.
We need to provide backup both for:
1. Volumes
2. VM instances (VM image, VM metadata, and attached volumes)
While the Cinder-backup handles (1), and is a very mature service, it does
not
Hi John,
Thanks for your comments. I am planning to attend summit we can have a wider
discussion there.
Thanks,
Murali Balcha
On Aug 30, 2013, at 12:05 AM, John Griffith
john.griff...@solidfire.commailto:john.griff...@solidfire.com wrote:
On Thu, Aug 29, 2013 at 6:36 PM, Murali Balcha
On Fri, Aug 30, 2013 at 8:02 AM, Murali Balcha murali.bal...@triliodata.com
wrote:
Hi John,
Thanks for your comments. I am planning to attend summit we can have a
wider discussion there.
Thanks,
Murali Balcha
On Aug 30, 2013, at 12:05 AM, John Griffith john.griff...@solidfire.com
On 8/29/2013 5:36 PM, Murali Balcha wrote:
Hi Kat,
Consider the following use cases that Raksha will addresses. I will discuss
from simple to complex use case and then address your specific questions with
inline comments.
1.VM1 that is created on the local file system with a cinder
On 8/30/2013 12:49 PM, Murali Balcha wrote:
Hi Caitlin,
Did you get a chance to look at the wiki? It describes the raksha functionality
in detail.
It includes more than volume backup. It includes vm images, all
volumes and network configurations associated with vms and it
supports
Hi Murali,
I think the idea to provide enhanced data protection in OpenStack is a
great idea, and I have been thinking about backup in OpenStack for a while
now.
I just not sure a new project is the only way to do.
(as disclosure, I contributed code to enable IBM TSM as a Cinder backup
driver)
On 8/28/2013 3:12 PM, Murali Balcha wrote:
Hello Stackers,
We would like to introduce a new project Raksha, a Data Protection As a
Service (DPaaS) for OpenStack Cloud.
Raksha’s primary goal is to provide a comprehensive Data Protection for
OpenStack by leveraging Nova, Swift, Glance and
From: Ronen Kat ronen...@il.ibm.com
Sen: Thursday, August 29, 2013 2:55 PM
To: openstack-dev@lists.openstack.org; openstack-...@lists.launchpad.net
Subject: Re: [openstack-dev] Proposal for Raksha, a Data Protection As a
Service project
Hi Murali,
My question is, would it make sense to add to the current mechanisms in
Nova and Cinder than add the complexity of a new project?
I think the answer is yes :)
I meant there is a clear need for Raksha project. :)
Thanks,
Murali Balcha
On Aug 29, 2013, at 7:45 PM, Murali Balcha
On Thu, Aug 29, 2013 at 6:36 PM, Murali Balcha murali.bal...@triliodata.com
wrote:
My question is, would it make sense to add to the current mechanisms in
Nova and Cinder than add the complexity of a new project?
I think the answer is yes :)
I meant there is a clear need for Raksha
Hello Stackers,
We would like to introduce a new project Raksha, a Data Protection As a Service
(DPaaS) for OpenStack Cloud.
Raksha's primary goal is to provide a comprehensive Data Protection for
OpenStack by leveraging Nova, Swift, Glance and Cinder. Raksha has following
key features:
1.
+1
On Thu, Aug 29, 2013 at 6:12 AM, Murali Balcha murali.bal...@triliodata.com
wrote:
Hello Stackers,
We would like to introduce a new project Raksha, a Data Protection As a
Service (DPaaS) for OpenStack Cloud.
Raksha’s primary goal is to provide a comprehensive Data Protection for
Hi Murali, welcome to the OpenStack community. Some comments inline...
On 08/28/2013 06:12 PM, Murali Balcha wrote:
Hello Stackers,
We would like to introduce a new project Raksha, a Data Protection As a
Service (DPaaS) for OpenStack Cloud.
Raksha’s primary goal is to provide a comprehensive
Hi Murali, welcome to the OpenStack community. Some comments inline...
Hi Jay,
Thanks for your comments. I have been involved with OpenStack since Diablo time
frame, but mostly monitoring the traffic. Always great to be part of the
community.
My comments are inline.
On 08/28/2013 06:12
21 matches
Mail list logo