Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snapshot and restore volumes by default #45

Merged
merged 4 commits into from
Aug 22, 2017
Merged

Snapshot and restore volumes by default #45

merged 4 commits into from
Aug 22, 2017

Conversation

jrnt30
Copy link
Contributor

@jrnt30 jrnt30 commented Aug 15, 2017

  • Adjusts defaults for backup Creation and Restoration

NOTE: Additionally changes default for replicas on the PV example so that it will bootstrap properly.

@heptibot
Copy link

Can one of the admins verify this patch?

@ncdc ncdc changed the title Snapshot restore defaults Snapshot and restore volumes by default Aug 15, 2017
@@ -43,7 +43,7 @@ metadata:
name: nginx-deployment
namespace: nginx-example
spec:
replicas: 2
replicas: 1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We "cheated" a bit in here to label one node with app=nginx to ensure pods from the deployment all land on the same node. @abiogenesis-now I think it's cleaner this way, and then we can remove the node labeling bit from the docs. WDYT?

Copy link
Contributor Author

@jrnt30 jrnt30 Aug 15, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Landing on the same node wasn’t the problem for me. With the PVC in Minikibe the two replicas are contending for ownership since it is not a storage class that allows of multiple attachments Via the ReadWriteOnce

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, interesting! I think we'll probably go ahead and remove the node labeling bit from that doc, but let's wait for @abiogenesis-now to chime in before doing so.

Copy link
Contributor

@jesscodez jesscodez Aug 15, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think that makes sense, and it'll simplify the docs a lot. @ncdc @jrnt30 We also do need to make docs changes to cloud-provider-specifics.md:

  • Remove the first node-labeling example from the snapshot example instructions (This relates to discussion above)

  • Update the basic (no-PVs) example command to include --snapshot-volumes=false and --restore-volumes=false

  • It might be clearer to also update the snapshot example section to either specify --snapshot-volumes=true and --restore-volumes=true, or remove the flags entirely since its true by default

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be clearer to also update the snapshot example section to either specify --snapshot-volumes=true and --restore-volumes=true, or remove the flags entirely since its true by default

Let's remove them.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have removed the additional notes, thanks!

My preference would be to leave the --snapshot-volumes=false for the basic example to not muddle the waters as Ark works just fine if you don't have PVs but the setting is enabled. If you would still like that change, I can do so.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I was referring to removing the =true ones!

@ncdc
Copy link
Contributor

ncdc commented Aug 15, 2017

@jrnt30 thanks for this. Once we resolve the replicas discussion, could you please amend your commits so they're signed off (git rebase --signoff ...... if you have git 2.13+; otherwise you could try something like this (note, I haven't tested it) or do it by hand)?

@ncdc
Copy link
Contributor

ncdc commented Aug 15, 2017

ok to test

@ncdc ncdc modified the milestone: v0.4.0 Aug 15, 2017
@ncdc
Copy link
Contributor

ncdc commented Aug 15, 2017

LGTM. @skriss PTAL

Copy link
Contributor

@jesscodez jesscodez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jrnt30 I think you might have missed adding --snapshot-volumes=false and --restore-volumes=false in lines 289-304 of cloud-provider-specifics.md?

@jesscodez
Copy link
Contributor

Oh @jrnt30 misread your comment, you are intentionally leaving out those false flags to avoid confusing people from previous versions of Ark?

@jesscodez jesscodez dismissed their stale review August 15, 2017 19:14

misread earlier comment

@jrnt30
Copy link
Contributor Author

jrnt30 commented Aug 15, 2017

I left it out intentionally because it isn't necessary, yes. If I were to do a create/restore with the flags set to true but without any PVs, it still "just works". To me, introducing the flag would just muddy the goal of the doc which is a quickstart guide.

That being said, I can add those in explicitly if you think it is adding value or I'm overlooking the importance of said feature.

@ncdc
Copy link
Contributor

ncdc commented Aug 15, 2017

I'm fine not including the flags

@skriss
Copy link
Member

skriss commented Aug 16, 2017

Probably good to remove the flags from the 2 command snippets here: use cases

@abiogenesis-now also has an updated architecture diagram that removes the flag.

Otherwise LGTM!

@skriss
Copy link
Member

skriss commented Aug 17, 2017

Thanks for making the docs changes @jrnt30, LGTM. Before merging, it looks like a download backup commit made its way into this branch that should be pulled out, and you need to rebase.

@jrnt30
Copy link
Contributor Author

jrnt30 commented Aug 17, 2017

@skriss I do not see the file you are referring to, can you be more specific perhaps?

@jrnt30
Copy link
Contributor Author

jrnt30 commented Aug 17, 2017

Oh...right, wrong branch... Yes, I will correct this

@ncdc
Copy link
Contributor

ncdc commented Aug 21, 2017

@jrnt30 please rebase

Justin Nauman and others added 4 commits August 21, 2017 09:47
Signed-off-by: Justin Nauman <justin.r.nauman@gmail.com>
- The two replicas contend for single PVC with the defined toplogy.  Could adjust to SS but kept it simple for now

Signed-off-by: Justin Nauman <justin.r.nauman@gmail.com>
- Removed explicit setting of snapshot flags
- Removed node selector on replicaset to reduce manual steps for users

Signed-off-by: Justin Nauman <justin.r.nauman@gmail.com>
Signed-off-by: Justin Nauman <justin.r.nauman@gmail.com>
@ncdc
Copy link
Contributor

ncdc commented Aug 21, 2017

LGTM. @abiogenesis-now & @skriss, please take 1 more look. Thanks!

@skriss
Copy link
Member

skriss commented Aug 21, 2017

LGTM.

@ncdc ncdc merged commit 3ca085e into vmware-tanzu:master Aug 22, 2017
@jrnt30 jrnt30 deleted the snapshot-restore-defaults branch August 22, 2017 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants