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

Update upgrade docs for 6.0.0 #14

Closed
7 tasks
dedemorton opened this issue Jun 14, 2017 · 3 comments
Closed
7 tasks

Update upgrade docs for 6.0.0 #14

dedemorton opened this issue Jun 14, 2017 · 3 comments

Comments

@dedemorton
Copy link
Contributor

dedemorton commented Jun 14, 2017

Let's use this issue to organize the effort to update the upgrade docs for 6.0.0.

The first step is for everyone to take a look at the existing upgrade docs and identify what's missing or needs to be updated:

https://www.elastic.co/guide/en/elastic-stack/current/index.html

Last time around, we decided to point to the docs for each component for detailed instructions. Now is the time to decide if we want to continue with that approach.

  • Update stack docs
    • Restructure content - break it up into smaller sections.
    • How to do a rolling upgrade from 5.x to 6.x
  • Elasticsearch & X-Pack install and upgrades
  • Kibana & X-Pack install and upgrades
  • Logstash & X-Pack install and upgrades
  • Beats install and upgrades
@nrichers
Copy link
Contributor

Last time around, we decided to point to the docs for each component for detailed instructions. Now is the time to decide if we want to continue with that approach.

For Cloud and ECE, that's likely the best approach, especially since we're not directly tied to the Elastic Stack release cycle.

@clintongormley
Copy link
Contributor

Last time around, we decided to point to the docs for each component for detailed instructions. Now is the time to decide if we want to continue with that approach.

I think this still makes sense, but we should have a separate section in the stack docs about how to do a rolling upgrade from 5.x to 6.x.

i'd also like to break up the pages in the stack docs already - each page is quite long and complicated. Could also do with some more headers to break up the content

@michaelbaamonde michaelbaamonde mentioned this issue Jul 10, 2017
24 tasks
@michaelbaamonde
Copy link

I wrote up #15, which is a superset of this issue. Thanks for getting the ball rolling here.

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

No branches or pull requests

4 participants