-
Notifications
You must be signed in to change notification settings - Fork 29
Document COSI API, resources, and add a simple getting started section #17
Conversation
|
||
For more information about COSI, visit our [documentation](https://github.com/kubernetes-sigs/container-object-storage-interface-api/tree/master/docs/index.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
documentation link returns 404
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same issue with link
README.md
Outdated
|
||
API definitions for Container Object Storage. | ||
All API definitions are in [`apis/objectstorage.k8s.io/` ](./apis/objectstorage.k8s.io/). All API changes **_MUST_** satisfy the following requirements: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[
apis/objectstorage.k8s.io/ ]
has an extra space after /
make codegen | ||
``` | ||
|
||
## Adding new fields to protocols |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should make this an issue template in the repository.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, template is already in place.
- [Deployment Guide](https://github.com/kubernetes-sigs/container-object-storage-interface-api/tree/master/docs/deployment-guide.md) | ||
- [Project Board](https://github.com/orgs/kubernetes-sigs/projects/8) | ||
- [Weekly Meetings](https://github.com/kubernetes-sigs/container-object-storage-interface-api/tree/master/docs/meetings.md) | ||
- [Roadmap](https://github.com/orgs/kubernetes-sigs/projects/8) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Project Board & Roadmap point to same board. Might want to consider just one Project Roadmap
link instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Roadmap and Work in Progress
docs/meetings.md
Outdated
---------------- | ||
|
||
### Engineering meeting | ||
- Monday at 11:00 - 11:30 AM PST |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we replace the date/time with something like Monday at 11:00AM - 11:30AM PT. Make it easy for folks not in PT time zone and avoid confusion around Daylight Savings Time
@@ -0,0 +1,21 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace with # Weekly Community Meetings
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought doc purely technical. I prefer meeting.md can be merged into the top level readme.
docs/meetings.md
Outdated
Weekly Meetings | ||
---------------- | ||
|
||
### Engineering meeting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change from ###
to ##
docs/meetings.md
Outdated
- [SIG Storage Zoom Meeting Room](https://zoom.us/s/614261834) | ||
- Password is ```77777``` | ||
|
||
### Community Meeting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change from ###
to ##
docs/meetings.md
Outdated
- [SIG Storage Zoom Meeting Room](https://zoom.us/s/614261834) | ||
- Password is ```77777``` | ||
|
||
### Organizers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change from ###
to ##
docs/meetings.md
Outdated
- [SIG Storage Zoom Meeting Room](https://zoom.us/s/614261834) | ||
- Password is ```77777``` | ||
|
||
### Community Meeting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Include link to meeting minutes and recordings.
docs/meetings.md
Outdated
Weekly Meetings | ||
---------------- | ||
|
||
### Engineering meeting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Include link to meeting minutes and recordings.
db3995b
to
528bd2a
Compare
@@ -0,0 +1,23 @@ | |||
--- | |||
title: Weekly Community Meetings | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove this block? I don't think it is needed.
---
title: Weekly Community Meetings
---
--- | ||
|
||
# Weekly Meetings | ||
---------------- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Delete this line ----------------
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a part of markdown
---------------- | ||
|
||
## Engineering meeting | ||
- Monday at 11:00AM - 11:30AM PT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add link to calendar event similar to community meeting here as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont have a public link for now. We'll have to move forward with this for now
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tparikh, wlan0 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 |
LGTM |
|
||
# Container Object Storage Interface Spec | ||
|
||
This repository hosts the API defintion of the Custom Resource Definitions (CRD) used for the Container Object Storage Interface (COSI) project. The provisioned unit of storage is a `Bucket`. The following CRDs are defined for managing the lifecycle of Buckets: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: Definition
make codegen | ||
``` | ||
|
||
## Adding new fields to protocols |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, template is already in place.
|
||
## Community, discussion, contribution, and support | ||
- Must be backwards compatible | ||
- Must be in-sync with the API definitions in [sigs.k8s.io/container-object-storage-interface-spec](https://github.com/kubernetes-sigs/container-object-storage-interface-spec) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we detail a bit more here, not all of the API but only the protocol structure right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be overkill for inital doc PR
@@ -0,0 +1,21 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought doc purely technical. I prefer meeting.md can be merged into the top level readme.
## References | ||
|
||
- [Documentation](docs/index.md) | ||
- [Deployment Guide](docs/deployment-guide.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
404 link
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tparikh is working on the deployment guide
/lgtm |
Participation in the Kubernetes community is governed by the [Kubernetes Code of Conduct](code-of-conduct.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link is one level more direct: https://github.com/kubernetes/community/blob/master/code-of-conduct.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but maybe you prefer the link to be inside the repo here?
|
||
- Automate object storage provisioning, access and management | ||
- Provide a common layer of abstraction for consuming object storage | ||
- Facilitate lift and shift of workloads across object storage providers (i.e. prevent vendor lock-in) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of "lift and shift", or in addition to this goal, I would include the important goal of app portability across the same protocols.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you have a one-liner that i could just add to that list?
- No common protocol for consumption across various implementations of object storage. | ||
- Management policies and primitives - for instance, mounting and unmounting do not apply to object storage. | ||
|
||
The existing primitives in CSI do not apply to objectstorage. Thus the need for a new standard to automate the management of objectstorage. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"objectstorage" -> "object storage"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mention POSIX but do you want to also mention that, unlike POSIX and iSCSI, there is no standard defining bucket provisioning?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is implicitly assumed at the beginning of this section. Should we mention this though?
|
||
## Links | ||
|
||
- [User Guide](user-guide.md) <!-- this should explain all use cases of COSI, and include a section for best pratices --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
404
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, @tparikh needs to get working fast to add these docs
## Links | ||
|
||
- [User Guide](user-guide.md) <!-- this should explain all use cases of COSI, and include a section for best pratices --> | ||
- [Deployment Guide](deployment-guide.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
404
|
||
- [User Guide](user-guide.md) <!-- this should explain all use cases of COSI, and include a section for best pratices --> | ||
- [Deployment Guide](deployment-guide.md) | ||
- [How to write a COSI driver](how-to-write-a-cosi-driver.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
404
- [User Guide](user-guide.md) <!-- this should explain all use cases of COSI, and include a section for best pratices --> | ||
- [Deployment Guide](deployment-guide.md) | ||
- [How to write a COSI driver](how-to-write-a-cosi-driver.md) | ||
- [How to make your application COSI-compatible](how-to-make-your-application-cosi-compatible.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
404
|
||
## Advanced | ||
|
||
- [Protocols](protocols.md) <!-- cosi protocols as the API between COSI and applications --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
404
## Advanced | ||
|
||
- [Protocols](protocols.md) <!-- cosi protocols as the API between COSI and applications --> | ||
- [Architecture](architecture.md) <!-- components, object lifecycles, and [sidecar <-> driver] swimlane diagram etc. --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
404
|
||
- [Protocols](protocols.md) <!-- cosi protocols as the API between COSI and applications --> | ||
- [Architecture](architecture.md) <!-- components, object lifecycles, and [sidecar <-> driver] swimlane diagram etc. --> | ||
- [Internals](internals.md) <!-- implementation details such as finalizers, bucket naming scheme etc. --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
404
@jeffvance @rrati @brahmaroutu @tparikh