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.

Sign up for GitHub

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

Jump to bottom

docs: Update roadmap for v1.7 #7910

Merged
merged 1 commit into from May 19, 2021
Merged

docs: Update roadmap for v1.7 #7910

merged 1 commit into from May 19, 2021

Conversation

travisn
Copy link
Member

@travisn travisn commented May 14, 2021

Description of your changes:
With the v1.6 release completed, we now update the roadmap for v1.7.

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
  • Skip Tests for Docs: Add the flag for skipping the build if this is only a documentation change. See here for the flag.
  • Skip Unrelated Tests: Add a flag to run tests for a specific storage provider. See test options.
  • Reviewed the developer guide on Submitting a Pull Request
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Integration tests have been added, if necessary.
  • Pending release notes updated with breaking and/or notable changes, if necessary.
  • Upgrade from previous release is tested and upgrade user guide is updated, if necessary.
  • Code generation (make codegen) has been run to update object specifications, if necessary.

Madhu-1
Madhu-1 reviewed May 17, 2021
View reviewed changes
ROADMAP.md
* Storage Providers
* Clearly define maintainer expectations for storage providers
* Remove unmaintained storage providers: EdgeFS, CockroachDB, and YugabyteDB
* Configure bucket notifications with a CRD ([design doc](https://github.com/rook/rook/blob/master/design/ceph/object/ceph-bucket-notification-crd.md))
Copy link
Member

Choose a reason for hiding this comment

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

@travisn CSI windows support will be part of 1.7 or later versions?

Copy link
Member Author

Choose a reason for hiding this comment

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

@Madhu-1 What is the timeline for the windows node support from the CSI driver? I'm assuming it's too early to commit to v1.7, so I'll add it to the future work section for now.

Copy link
Member

Choose a reason for hiding this comment

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

Yes, it would be too early. we are planning for 3.4 of cephcsi not sure it's going to be ready. good to add it to the future section 👍

satoru-takeuchi
satoru-takeuchi reviewed May 17, 2021
View reviewed changes
ROADMAP.md Outdated
* Clearly define maintainer expectations for storage providers
* Remove unmaintained storage providers: EdgeFS, CockroachDB, and YugabyteDB
* Configure bucket notifications with a CRD ([design doc](https://github.com/rook/rook/blob/master/design/ceph/object/ceph-bucket-notification-crd.md))
* Add alpha support for COSI (Container object storage interface) with K8s 1.21
Copy link
Member

Choose a reason for hiding this comment

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

COSI alpha support were postponed to k8s v1.22.

Copy link
Member Author

Choose a reason for hiding this comment

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

Good catch, updated to v1.22.

leseb
leseb requested changes May 17, 2021
View reviewed changes
ROADMAP.md Outdated
* Clearly define maintainer expectations for storage providers
* Remove unmaintained storage providers: EdgeFS, CockroachDB, and YugabyteDB
* Configure bucket notifications with a CRD ([design doc](https://github.com/rook/rook/blob/master/design/ceph/object/ceph-bucket-notification-crd.md))
* Add alpha support for COSI (Container object storage interface) with K8s 1.21
Copy link
Member

Choose a reason for hiding this comment

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

  • OSD encryption key rotation
  • iSCSI gateway deployment
  • use go-ceph to interact with object store

Copy link
Member Author

Choose a reason for hiding this comment

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

Added. Are there any issues we could link, or could you open them? thanks

BlaineEXE
BlaineEXE reviewed May 17, 2021
View reviewed changes
ROADMAP.md
* Support the Ceph Pacific release
* CephFS Mirroring support for data replication across clusters
* RBD mirroring configuration between clusters to support application DR (disaster recovery)
* Helm chart for the cluster CR [#2109](https://github.com/rook/rook/issues/2109)
Copy link
Member

Choose a reason for hiding this comment

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

We also could consider doing larger helm re-design work: #6776

Copy link
Member Author

Choose a reason for hiding this comment

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

Honestly, I'm not sure we need to do more helm re-design work. IMO a chart for the cluster CR fills the gap, but let's discuss more.

travisn
travisn commented May 17, 2021
View reviewed changes
ROADMAP.md
* Helm chart for the cluster CR [#2109](https://github.com/rook/rook/issues/2109)
* Configure bucket notifications with a CRD ([design doc](https://github.com/rook/rook/blob/master/design/ceph/object/ceph-bucket-notification-crd.md))
* Add alpha support for COSI (Container object storage interface) with K8s 1.22 [#7843](https://github.com/rook/rook/issues/7843)
* Disaster Recovery (DR): CSI solution for application failover in the event of cluster failure
Copy link
Member Author

Choose a reason for hiding this comment

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

@Madhu-1 Is there a design doc or issue we could link for this work item?

Copy link
Member

Choose a reason for hiding this comment

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

The solution already exists. we need documentation #7034 #7033 should cover both DR solutions.

leseb
leseb requested changes May 18, 2021
View reviewed changes
Copy link
Member

@leseb leseb left a comment

Choose a reason for hiding this comment

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

I created the issues.

ROADMAP.md Outdated
* Allow OSDs on PVCs to automatically grow when the cluster is nearly full [#6101](https://github.com/rook/rook/issues/6101)
* OSD encryption key rotation [(insert issue link)]()
* iSCSI gateway deployment [(insert issue link)]()
* Use go-ceph to interact with object store instead of `radosgw-admin` [(insert issue link)]()
Copy link
Member

Choose a reason for hiding this comment

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

#7924

ROADMAP.md Outdated
* Disaster Recovery (DR): CSI solution for application failover in the event of cluster failure
* Allow OSDs on PVCs to automatically grow when the cluster is nearly full [#6101](https://github.com/rook/rook/issues/6101)
* OSD encryption key rotation [(insert issue link)]()
* iSCSI gateway deployment [(insert issue link)]()
Copy link
Member

Choose a reason for hiding this comment

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

#4334

ROADMAP.md Outdated
* Add alpha support for COSI (Container object storage interface) with K8s 1.22 [#7843](https://github.com/rook/rook/issues/7843)
* Disaster Recovery (DR): CSI solution for application failover in the event of cluster failure
* Allow OSDs on PVCs to automatically grow when the cluster is nearly full [#6101](https://github.com/rook/rook/issues/6101)
* OSD encryption key rotation [(insert issue link)]()
Copy link
Member

Choose a reason for hiding this comment

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

#7925

@travisn
docs: update roadmap for v1.7
e214a55 
With the v1.6 release completed, we now update the roadmap
for v1.7.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
@travisn travisn requested a review from leseb May 18, 2021 22:29
@leseb
Copy link
Member

leseb commented May 19, 2021

I don't understand the python script failed again where it seems that the endpoint is available...

<!DOCTYPE html>
<html>
    <head><title>Ceph Exporter</title></head>
    <body>
        <h1>Ceph Exporter</h1>
        <p><a href='/metrics'>Metrics</a></p>
    </body>
</html>Execution Failed: unable to connect to endpoint: 172.17.0.5:9283
Traceback (most recent call last):
  File "/etc/ceph/create-external-cluster-resources.py", line 801, in <module>
    raise err
  File "/etc/ceph/create-external-cluster-resources.py", line 798, in <module>
    rjObj.main()
  File "/etc/ceph/create-external-cluster-resources.py", line 779, in main
    generated_output = self.gen_json_out()
  File "/etc/ceph/create-external-cluster-resources.py", line 613, in gen_json_out
    self._gen_output_map()
  File "/etc/ceph/create-external-cluster-resources.py", line 598, in _gen_output_map
    self.out_map['MONITORING_ENDPOINT_PORT'] = self.get_active_and_standby_mgrs()
  File "/etc/ceph/create-external-cluster-resources.py", line 389, in get_active_and_standby_mgrs
    self.endpoint_dial(monitoring_endpoint)
  File "/etc/ceph/create-external-cluster-resources.py", line 245, in endpoint_dial
    "unable to connect to endpoint: {}".format(endpoint_str))
__main__.ExecutionFailureException: unable to connect to endpoint: 172.17.0.5:9283
command terminated with exit code 1
Error: Process completed with exit code 1.

@travisn
Copy link
Member Author

travisn commented May 19, 2021

I don't understand the python script failed again where it seems that the endpoint is available...

Since it's unrelated to this PR I'll go ahead and merge

@travisn travisn merged commit 4456a5a into rook:master May 19, 2021
@travisn travisn deleted the roadmap-1.7 branch May 19, 2021 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@BlaineEXE BlaineEXE BlaineEXE left review comments

@leseb leseb leseb approved these changes

@satoru-takeuchi satoru-takeuchi satoru-takeuchi approved these changes

@Madhu-1 Madhu-1 Madhu-1 approved these changes

@galexrt galexrt Awaiting requested review from galexrt

@jbw976 jbw976 Awaiting requested review from jbw976

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
5 participants
@travisn @leseb @BlaineEXE @satoru-takeuchi @Madhu-1