Skip to content

Conversation

@sadasu
Copy link
Contributor

@sadasu sadasu commented Aug 8, 2019

Create a volume type to represent the shared volume used by various containers in a Baremetal deployment. Also, the Baremetal CRD needs it ordering number bumped up by 1.

@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Aug 8, 2019
@stbenjam
Copy link
Member

stbenjam commented Aug 8, 2019

Can you remove WIP from commit message + title if this is ready to go? Looks good to me.

@sadasu sadasu changed the title WIP: Add volume type to represent shared volume for a Baremetal deployment Add volume type to represent shared volume for a Baremetal deployment Aug 8, 2019
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 8, 2019
@stbenjam
Copy link
Member

stbenjam commented Aug 8, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 8, 2019
@stbenjam
Copy link
Member

stbenjam commented Aug 8, 2019

/assign @frobware

Copy link

@imain imain left a comment

Choose a reason for hiding this comment

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

Looks good to me! Thanks Sandhya!

@enxebre
Copy link
Member

enxebre commented Aug 9, 2019

Also, the Baremetal CRD needs it ordering number bumped up by 1.

can you elaborate why in the description?

@russellb
Copy link
Contributor

russellb commented Aug 9, 2019

Also, the Baremetal CRD needs it ordering number bumped up by 1.
can you elaborate why in the description?

I've pinged @sadasu on slack to ask, but AFAICT, it looks like it's just cosmetic, and not fixing anything

@enxebre
Copy link
Member

enxebre commented Aug 9, 2019

@russellb @sadasu the local volume will be lost during rolling updates i.e during cluster upgrades, I assume you are good with that?

@russellb
Copy link
Contributor

russellb commented Aug 9, 2019

the local volume will be lost during rolling upgrades i.e during cluster upgrades, I assume you are good with that?

Yep - it's designed around losing all of this data anytime, just need to share some stuff between a handful of containers while they run

@russellb
Copy link
Contributor

russellb commented Aug 9, 2019

confirmed that the number change is just cosmetic btw @enxebre

@enxebre
Copy link
Member

enxebre commented Aug 9, 2019

/approve

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 9, 2019
@openshift-merge-robot openshift-merge-robot merged commit c7738d4 into openshift:master Aug 9, 2019
@sadasu
Copy link
Contributor Author

sadasu commented Aug 9, 2019

Also, the Baremetal CRD needs it ordering number bumped up by 1.

can you elaborate why in the description?

@enxebre I had originally picked 12 in the filename (next seriel number that was available) and then a merge went just before mine that had grabbed that #. I missed this detail in my original commit and rebase won't flag that. I bumped the # in my filename to 13 to accommodate to accommodate the file naming convention.

@enxebre
Copy link
Member

enxebre commented Aug 9, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants