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

Durable (non-shared) local storage management #121

Closed
smarterclayton opened this issue Oct 9, 2016 · 65 comments
Closed

Durable (non-shared) local storage management #121

smarterclayton opened this issue Oct 9, 2016 · 65 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status

Comments

@smarterclayton
Copy link
Contributor

smarterclayton commented Oct 9, 2016

Feature Description

@smarterclayton smarterclayton added sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/storage Categorizes an issue or PR as relevant to SIG Storage. labels Oct 9, 2016
@davidopp
Copy link
Member

davidopp commented Oct 9, 2016

I assume this is kubernetes/kubernetes#7562 ?

And that kubernetes/kubernetes#30044 is related?

@smarterclayton
Copy link
Contributor Author

smarterclayton commented Oct 11, 2016

Yes and yes. Consensus is to see if we can pull together a design at most in 1.5

@bprashanth
Copy link

bprashanth commented Oct 11, 2016

It would be great if we were ready to go at this in 1.6
@kubernetes/sig-storage @jingxu97

@thockin
Copy link
Member

thockin commented Oct 11, 2016

I think we can commit to that.

On Mon, Oct 10, 2016 at 9:35 PM, Prashanth B notifications@github.com
wrote:

It would be great if we were ready to go at this in 1.6
@kubernetes/sig-storage
https://github.com/orgs/kubernetes/teams/sig-storage @jingxu97
https://github.com/jingxu97


You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
#121 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVCoNyQWhL1_AAMD0eE1Uh79jaMWsks5qyxIggaJpZM4KR2_S
.

@idvoretskyi idvoretskyi modified the milestone: v1.5 Oct 11, 2016
@jingxu97
Copy link
Contributor

jingxu97 commented Oct 11, 2016

Yes, I will definitely spend more time on this after this short release
cycle for 1.5. Thanks!

Jing

On Mon, Oct 10, 2016 at 10:53 PM, Tim Hockin notifications@github.com
wrote:

I think we can commit to that.

On Mon, Oct 10, 2016 at 9:35 PM, Prashanth B notifications@github.com
wrote:

It would be great if we were ready to go at this in 1.6
@kubernetes/sig-storage
https://github.com/orgs/kubernetes/teams/sig-storage @jingxu97
https://github.com/jingxu97


You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/kubernetes/features/issues/
121#issuecomment-252810762>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFVgVCoNyQWhL1_
AAMD0eE1Uh79jaMWsks5qyxIggaJpZM4KR2_S>
.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#121 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASSNxQlkIyJ98tTTTqNRkJh2JB3OtI-jks5qyyRJgaJpZM4KR2_S
.

  • Jing

@vishh
Copy link
Member

vishh commented Jan 18, 2017

@msau42 and myself will be tackling this problem in v1.6. The plan is as follows:

  1. Design completion by v1.6
  2. Alpha support for local storage by v1.7
  3. Beta (or may be GA) by v1.8

@rkouj and @jingxu97 will also be helping with this effort.

@msau42 and @vishh will post a high level design proposal before end of Jan `17.

@vishh vishh changed the title Local storage for use with PetSets and bare-metal clusters Local storage Management (ephemeral & durable) Jan 18, 2017
@davidopp
Copy link
Member

davidopp commented Jan 24, 2017

Please loop me in on the scheduling aspects of this.

@idvoretskyi idvoretskyi modified the milestones: v1.6, next-milestone Jan 26, 2017
@idvoretskyi
Copy link
Member

idvoretskyi commented Jan 26, 2017

Misread the @vishh comment, let's target 1.7 when this milestone will be open.

@wattsteve
Copy link

wattsteve commented Jan 27, 2017

@vishh and others. Given that we're already talking about targeting releases, is there a design proposal for this? FYI @saad-ali @childsb

@vishh
Copy link
Member

vishh commented Jan 27, 2017

@krmayankk
Copy link
Contributor

krmayankk commented Jan 29, 2017

@vishh has this anything to do with sticky empty dir proposal or local storage for statefulset ? I am getting confused which feature is doing what ? There are many things needed for local storage , e.g. 1: local storage support in statefulset 2: local storage volumes which is this one 3: pod should be scheduled in the same node where their data is already available 4: may be moving data to where the pod gets scheduled . It will be good to have one local storage featur which covers all related issues and proposals

@vishh
Copy link
Member

vishh commented Jan 29, 2017

@krmayankk the plan is to cover all supported use cases for local storage.

@davidopp
Copy link
Member

davidopp commented Jan 29, 2017

@vishh I assume you are not including (4) from @krmayankk's comment? (migrating data between nodes)

@msau42
Copy link
Member

msau42 commented Jan 30, 2019

/assign @cofyc

@saad-ali saad-ali added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status and removed stage/beta Denotes an issue tracking an enhancement targeted for Beta status labels Jan 30, 2019
@saad-ali saad-ali added this to the v1.14 milestone Jan 30, 2019
@liggitt liggitt added the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label Jan 31, 2019
@spiffxp spiffxp added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Feb 7, 2019
@spiffxp
Copy link
Member

spiffxp commented Feb 7, 2019

Adding tracked label to reconcile against https://bit.ly/k8s114-enhancements
FYI @claurence @lachie83 @lledru @ameukam

@jimangel
Copy link
Member

jimangel commented Feb 13, 2019

Hey @cofyc @msau42 👋 I'm the v1.14 docs release lead. Just a friendly reminder we're looking for a PR against k/website (branch dev-1.14) due by Friday, March 1. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions!

@liggitt
Copy link
Member

liggitt commented Feb 15, 2019

For 1.14 work, the following needs to be done:

it doesn't sound like there are API changes involved in the 1.14 work. Is that accurate?

@thockin
Copy link
Member

thockin commented Feb 15, 2019

I think API was done long ago.

@liggitt liggitt removed the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label Feb 15, 2019
@lledru
Copy link
Member

lledru commented Feb 25, 2019

Hello, 1.14 enhancement shadow here. Code Freeze is March 7th and all PRs must be merged by then to your issue to make the 1.14 release. What open K/K PRs do you still have that need to merge? Thanks

@msau42
Copy link
Member

msau42 commented Feb 25, 2019

The items I listed above here tracks our 1.14 work.

@kacole2
Copy link
Member

kacole2 commented Apr 12, 2019

Hello @msau42 @smarterclayton , I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet. If this was included as GA in 1.14 lets close this issue.

Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.14 milestone Apr 12, 2019
@kacole2 kacole2 added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Apr 12, 2019
@msau42
Copy link
Member

msau42 commented Apr 12, 2019

1.14 was GA and any additional enhancements should be tracked as new features.
/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Apr 12, 2019

@msau42: Closing this issue.

In response to this:

1.14 was GA and any additional enhancements should be tracked as new features.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kacole2 kacole2 removed the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Apr 12, 2019
ingvagabund pushed a commit to ingvagabund/enhancements that referenced this issue Apr 2, 2020
…our_own_vnet

Azure: Customer provisioned virtual network & subnets enhancement doc
MadhavJivrajani pushed a commit to kubernetes/design-proposals-archive that referenced this issue Nov 30, 2021
Automatic merge from submit-queue.

Volume topology aware scheduling design

Proposal for a smarter scheduler that influences PV binding.

Part of kubernetes/enhancements#121

/sig storage
/sig scheduling
/cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
MadhavJivrajani pushed a commit to MadhavJivrajani/design-proposals that referenced this issue Dec 1, 2021
Automatic merge from submit-queue.

Volume topology aware scheduling design

Proposal for a smarter scheduler that influences PV binding.

Part of kubernetes/enhancements#121

/sig storage
/sig scheduling
/cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
MadhavJivrajani pushed a commit to MadhavJivrajani/design-proposals that referenced this issue Dec 1, 2021
Automatic merge from submit-queue.

Volume topology aware scheduling design

Proposal for a smarter scheduler that influences PV binding.

Part of kubernetes/enhancements#121

/sig storage
/sig scheduling
/cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
MadhavJivrajani pushed a commit to MadhavJivrajani/design-proposals that referenced this issue Dec 1, 2021
Automatic merge from submit-queue.

Volume topology aware scheduling design

Proposal for a smarter scheduler that influences PV binding.

Part of kubernetes/enhancements#121

/sig storage
/sig scheduling
/cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
MadhavJivrajani pushed a commit to kubernetes/design-proposals-archive that referenced this issue Dec 1, 2021
Automatic merge from submit-queue.

Volume topology aware scheduling design

Proposal for a smarter scheduler that influences PV binding.

Part of kubernetes/enhancements#121

/sig storage
/sig scheduling
/cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
MadhavJivrajani pushed a commit to kubernetes/design-proposals-archive that referenced this issue Dec 1, 2021
Automatic merge from submit-queue.

Volume topology aware scheduling design

Proposal for a smarter scheduler that influences PV binding.

Part of kubernetes/enhancements#121

/sig storage
/sig scheduling
/cc @kubernetes/sig-storage-proposals @kubernetes/sig-scheduling-proposals
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
No open projects
Development

No branches or pull requests