Re: [openstack-dev] [Freezer] PTL Candidacy

And you have at least all my support : ) On Wed, Jan 25, 2017 at 12:56 PM, Saad Zaher wrote: > Hello everyone, > > I'm happy to announce my candidacy to be the Freezer PTL for the Pike > release > cycle. > > The Freezer developers did a very good job over the past releases

Re: [openstack-dev] [Freezer] Replace Gnu Tar with DAR

, May 23, 2016 at 6:03 PM, Dieterly, Deklan <deklan.diete...@hpe.com> wrote: > Then it would not be an incremental backup/restore. This problem arises > when doing incremental backup and restores. > -- > Deklan Dieterly > > Senior Systems Software Engineer > HPE &g

Re: [openstack-dev] [Freezer] Replace Gnu Tar with DAR

Hi Deklan, what happen if the extract is executed without --listed-incremental or --incremental options? Does the issue still happen? Thanks, Fausto On Sat, May 14, 2016 at 12:56 AM, Dieterly, Deklan wrote: > When using incremental backups, tar will not handle

Re: [openstack-dev] [tc] supporting Go

++ Brilliant. On Fri, May 13, 2016 at 10:14 AM, Dmitry Tantsur wrote: > > This is pretty subjective, I would say. I personally don't feel Go > (especially its approach to error handling) any natural (at least no more > than Rust or Scala, for example). If familiarity for

Re: [openstack-dev] [tc] supporting Go

My take would be to select no more than 3 languages, according what they are needed for, then let the Service Team pick the best one right for what it needs to be done. Something like: - Do you need more performance for this component in your service? OK, use this. - Do you need Web and alike?

Re: [openstack-dev] [freezer] Proposing Saad Zaher for freezer core

+1. Saad Zaher is a Top Gear engineer : ) On Thu, Apr 14, 2016 at 4:20 PM, Mathieu, Pierre-Arthur < pierre-arthur.math...@hpe.com> wrote: > Hello, > > I would like to propose that we make Saad Zaher (szaher) core on freezer. > He has been a highly valuable developper for the past few month,

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Mon, Feb 8, 2016 at 11:19 AM, Jay Pipes wrote: > On 02/08/2016 10:29 AM, Sean Dague wrote: > >> On 02/08/2016 10:07 AM, Thierry Carrez wrote: >> >>> Brian Curtin wrote: >>> On Sun, Feb 7, 2016 at 3:07 PM, Jay Pipes wrote: > I would love

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Mon, Feb 8, 2016 at 6:26 AM, Thierry Carrez wrote: > Daniel P. Berrange wrote: > >> [...] >> I really agree with everything you say, except for the bit about the >> community doing organization - I think its fine to let function event >> staff continue with the burden

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

API, with core and >vendor-specific extensions. > > > Vendors (like my employer, EMC) might be somewhat opinionated about (2), > and for reason. :) > > The huge missing piece is (1), and a focused project seems to make a lot > of sense. > > As to (3), that looks like

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

Hi Preston, No need to apologize. They are aspect of the same problem. However, VMs backup is one of the many aspects that we are approaching here, such as: - VM backups - Volumes backups - Specific applications consistent data backup (i.e. MySQL, Mongo, file system, etc) - Provide capabilities

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

What motivates me every day and every night, is to provide the most advanced solution for a set a problems to solve, Open Source and in OpenStack. What motivates me is to work with brilliant people like minded, capable of doing great things working together. It is not the competition and It is not

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

Hi Sam, After our conversation, I have few questions and consideration about Ekko, mainly on how it works et similar. Also to make available to the community our discussions: - In understand you are placing a backup-agent on the compute node and execute actions interacting directly with

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

Hi Jay, Dean, totally agree, with Sam, we'll make sure there will not be any overlap. Sam, Thanks for your openness. I'd like to have a conversation about it. When you say "current direction of Ekko will add many components" do you have any reference, plan or road map where we can see that

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

Hi Sam, My opinion would be to converge, so to have Ekko features exported from the freezer-api and horizon web interface. Also the freezer-scheduler can be integrated, that would enable Ekko to execute backup syncronized over multiple nodes. By all mean, this does not mean you have to, it's

[openstack-dev] [freezer][agent][bug] Trying Freezerc with no success

Hi Deklan, Following up our conversation on restoring from swift, yes there's a bug, you are right, I've reproduced it. It can be reproduced when python-swiftclient 2.7.0 is installed on the system. In Liberty and Mitaka the requirement is python-swiftclient>=2.2.0. The issue should be solved by

[openstack-dev] [freezer] Meetings in pause state until 7th of Jan

Hi All, We'll be mostly off until the 7th of Jan. If you need anything urgent please drop me an email. I want to take this opportunity to thank the Freezer Team for the amazing job, effort and sacrifices faced during the 2015. You have all my respect, as you already know : ) Have the most