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

Updated ToC for entire ManageIQ + added already existing topics within ToC #1806

Merged
merged 9 commits into from
Sep 11, 2024

Conversation

qahmed1998
Copy link
Contributor

@qahmed1998 qahmed1998 commented Aug 22, 2024

Added following additional topics to ToC:

  • Creating a Service in for Virtual Machine Provisioning
  • Service Provisioning Using an Orchestration Template
  • Assigning a Custom Analysis Profile to a Virtual Machine

This PR is editing the current ToC for ManageIQ. No files in terms of their locations were moved in the process. 3 existing topics (as mentioned above) were added to the ToC.

Added following additional topics to ToC:
- Creating a Service in for Virtual Machine Provisioning
- Service Provisioning Using an Orchestration Template
- Assigning a Custom Analysis Profile to a Virtual Machine
@Fryguy
Copy link
Member

Fryguy commented Aug 26, 2024

@qasim-ahmed This PR is going to need a bunch of "prior" entries, so that the page detector can understand how the pages were moved around. Basically, the way it works is for each of these "moved" sections, just add a new key called "prior" which is the url for the old location of the file. Here's an example from when we moved one of the locations from morphy to najdorf: https://github.com/ManageIQ/manageiq-documentation/blob/najdorf/_data/site_menu.yml#L42

@Fryguy
Copy link
Member

Fryguy commented Aug 26, 2024

@qasim-ahmed Can you also update the original post here with maybe a screenshot or a manual type-out of the new layout? Also, please update the PR title / commit message to be more descriptive - this is a pretty big change, and the title doesn't really reflect that.

@qahmed1998 qahmed1998 changed the title Updated ToC Updated ToC for entire ManageIQ + added already existing topics within ToC Aug 26, 2024
@qahmed1998
Copy link
Contributor Author

Installing section:
image

Upgrading section:
image

Administration section:
image

Visualizing section:
image

Controls section:
image

Managing integrations section:
image

image

image

image

APIs, Reference and Troubleshhooting sections:
image

@Fryguy
Copy link
Member

Fryguy commented Aug 28, 2024

@agrare @jrafanie Please also take a look.

@qahmed1998
Copy link
Contributor Author

Hi @agrare @jrafanie Please take a look when you get a chance.

@jrafanie
Copy link
Member

jrafanie commented Sep 5, 2024

@qahmed1998 how can I see a before and after?

It's hard to visualize what's moving around and being added/removed. I'll add my comments but they're on the existing terminology so mostly unrelated to this PR.

- title: Methods Available for Automation
path: "/docs/reference/latest/methods_available_for_automation/index.html"
desc: Advanced automation methods for ManageIQ Management Engine
- title: Scripting Actions in ManageIQ
path: "/docs/reference/latest/scripting_actions/index.html"
desc: "Real-time, bi-directional process integration for ManageIQ Management Engine"
Copy link
Member

Choose a reason for hiding this comment

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

What's the difference between ManageIQ Management Engine and ManageIQ? I see both terminology here. Do we need to normalize on one term?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

FYI @Fryguy

Copy link
Member

Choose a reason for hiding this comment

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

Note, I see this term elsewhere so we can potentially normalize the terms in a followup PR. It's more obvious here since I see both forms of what I think are the same thing.

Copy link
Member

Choose a reason for hiding this comment

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

I bet this used to be CloudForms Management Engine. Probably best to just use "Real-time, bi-directional process integration for ManageIQ"

@qahmed1998
Copy link
Contributor Author

qahmed1998 commented Sep 5, 2024

@qahmed1998 how can I see a before and after?

It's hard to visualize what's moving around and being added/removed. I'll add my comments but they're on the existing terminology so mostly unrelated to this PR.

We can potentially merge and see the ToC?

@agrare
Copy link
Member

agrare commented Sep 5, 2024

We can potentially merge and see the ToC?

I think that defeats the purpose of PR review if we have to merge it to see it, agree with @jrafanie it is hard to review without seeing what has changed easier

@qahmed1998
Copy link
Contributor Author

I have posted screenshots above as well. The ss might help!

_data/site_menu.yml Outdated Show resolved Hide resolved
Comment on lines 60 to 61
visualizing:
title: Visualizing infrastructure
Copy link
Member

Choose a reason for hiding this comment

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

Hm I'm not sure "visualizing" is how I'd describe this section. It does include viewing inventory but also e.g. reconfiguring_a_vm_disk.md, refreshing_instances_and_images.md, removing_a_datastore.md, creating_a_vm_snapshot.md, etc...

If anything I'd call this "Inventory" or "Managing Inventory", @Fryguy wdyt?

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh I see, I can make the top level heading Managing inventory.

@jrafanie
Copy link
Member

jrafanie commented Sep 5, 2024

Ok, this is the before... I think I can imagine what it will look like:

image

@qahmed1998
Copy link
Contributor Author

qahmed1998 commented Sep 5, 2024

The changes in this PR include, adding new top level headings, moving topics from one heading to another and adding topics which existed but were not part of the ToC. The ToC changes that are in this PR currently aligns with the downstream (AIOps) ToC.

desc: "How to create a service for virtual machine provisioning"
- title: Assigning a Custom Analysis Profile to a Virtual Machine
path: "/docs/reference/latest/assigning_custom_analysis_profile_to_vm/index.html"
desc: "How to assign custom analysis profile to a virtual machine"
Copy link
Member

Choose a reason for hiding this comment

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

I don't know that most of these fall under "Administration", I do think administration for backup&restore or something like creating local users but these are all more related to managing inventory IMO.

Copy link
Member

@jrafanie jrafanie Sep 5, 2024

Choose a reason for hiding this comment

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

Good point. I don't know how to word it but one is administration of the application and one is using the application.

Perhaps a high level "using" section with categories...

  • Using
    • Authentication...
    • Automation
      • All of the provisioning, service, etc.
      • Scripting actions ...
    • Policy
      • Monitoring, alerts, reporting...
      • Policies and Profiles guide
    • Manage Infra and Inv.
    • Managing Providers...
  • Configuration
    • Assigning a Custom Analysis Profile...
    • Deployment planning guide
    • ...
  • Administration
    • Appliance backup/restore
    • installation
    • upgrading
      ...

Copy link
Member

Choose a reason for hiding this comment

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

Note, I would prefer we move things one at a time if we can't have a good visual before/after screenshots. Ideally, each commit changes one thing and the PR changes aren't too much so it's easy to review and get merged. Anything that "feels" like it's a separate change should probably be done in followup PRs so the high level reorganization can go in first.

Copy link
Contributor Author

@qahmed1998 qahmed1998 Sep 5, 2024

Choose a reason for hiding this comment

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

I can make changes to each big heading (section) in a single commit. With regards to Installing, Upgrading, It will make sense for it to be its own heading and not be under Administration. Administration should contain stuff that can be done by a user once application is installed.

Copy link
Contributor Author

@qahmed1998 qahmed1998 Sep 5, 2024

Choose a reason for hiding this comment

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

@jrafanie @agrare For the following, Should these go under Configuration or Managing inventory?

  • Provisioning Virtual Machines and Hosts
  • Service Provisioning Using an Orchestration Template
  • Creating a Service in for Virtual Machine Provisioning

Copy link
Member

Choose a reason for hiding this comment

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

  • Provisioning Virtual Machines and Hosts
  • Service Provisioning Using an Orchestration Template
  • Creating a Service in for Virtual Machine Provisioning

I think they would go in using -> automation

@agrare
Copy link
Member

agrare commented Sep 5, 2024

The ToC changes that are in this PR currently aligns with the downstream (AIOps) ToC.

Okay it seems like some items might be in the wrong place there then also so lets put them in the best place upstream first ™️ and go from there

@qahmed1998
Copy link
Contributor Author

The ToC changes that are in this PR currently aligns with the downstream (AIOps) ToC.

Okay it seems like some items might be in the wrong place there then also so lets put them in the best place upstream first ™️ and go from there

Yeah sounds good to me.

@agrare
Copy link
Member

agrare commented Sep 5, 2024

NOTE I don't see Automation Management Providers in the existing TOC, can we add under Managing Providers similar to Configuration Providers

@qahmed1998
Copy link
Contributor Author

NOTE I don't see Automation Management Providers in the existing TOC, can we add under Managing Providers similar to Configuration Providers

Do you have the URL/path of the file/content?

Added Podified and Appliance categories for "Installing"
@qahmed1998
Copy link
Contributor Author

qahmed1998 commented Sep 6, 2024

Okay so from our discussions in Slack, this is what we have as updated ToC.

Installing

Upgrading

Using

  • General Configuration

  • Monitoring, alerts, reporting

  • Policies and Profiles Guide

  • Managing Infrastructure and Inventory

  • Managing Providers and its sub-topics

  • Provisioning Virtual Machines and Hosts

  • Scripting Actions in ManageIQ

  • Creating a Service in for Virtual Machine Provisioning

  • Service Provisioning Using an Orchestration Template

  • Managing controls (seems the most suitable name to me as a heading)

    • Monitoring, alerts, reporting

    • Policies and Profiles Guide

  • Assigning a Custom Analysis Profile to a Virtual Machine

Administering Infrastructure Management

  • Authentication

  • Backup and Restore (appliances)

  • Deployment planning guide

  • High Availability Guide

  • Appliance Hardening Guide

Defining integrations

  • AWS CloudFormation and OpenStack Heat

  • ServiceNow

APIs

  • REST API

Reference

  • Capabilities Matrix

  • Methods available for automation

Troubleshooting (same as it is)

@qahmed1998
Copy link
Contributor Author

Any final adjustments or am I good to make this as the ToC in the PR?

@qahmed1998
Copy link
Contributor Author

Updated ToC as we discussed. Please review.

  • Updated the ToC
  • Added Automation Management Providers topic in ToC
  • Changed description of a topic
  • Added Chargeback topic in ToC

_data/site_menu.yml Outdated Show resolved Hide resolved
_data/site_menu.yml Outdated Show resolved Hide resolved
_data/site_menu.yml Outdated Show resolved Hide resolved
@qahmed1998
Copy link
Contributor Author

@jrafanie @Fryguy are we good to merge?

_data/site_menu.yml Outdated Show resolved Hide resolved
@qahmed1998
Copy link
Contributor Author

Hi Joe, I have addressed your comments.

@miq-bot
Copy link
Member

miq-bot commented Sep 11, 2024

Checked commits qahmed1998/manageiq-documentation@3079587~...2557ad9 with ruby 3.1.5, rubocop 1.56.3, haml-lint 0.51.0, and yamllint
1 file checked, 1 offense detected

**

  • 💣 💥 🔥 🚒 - Linter/Yaml - missing config files

Copy link
Member

@jrafanie jrafanie 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. It's hard to see the layout in this format but I think all of the concerns have been addressed.

@jrafanie jrafanie merged commit 4eda9ef into ManageIQ:master Sep 11, 2024
2 checks passed
@jrafanie jrafanie assigned jrafanie and unassigned jrafanie, Fryguy and agrare Sep 11, 2024
@Fryguy
Copy link
Member

Fryguy commented Sep 11, 2024

This PR broke the build

https://github.com/ManageIQ/manageiq-documentation/actions/runs/10814819288/job/30002189898#step:5:232

Psych::SyntaxError: (/tmp/manageiq-documentation/_data/site_menu.yml): mapping values are not allowed in this context at line 7 column 17
/tmp/manageiq-documentation/Rakefile:10:in `block in <top (required)>'
/opt/hostedtoolcache/Ruby/2.7.8/x64/bin/bundle:23:in `load'
/opt/hostedtoolcache/Ruby/2.7.8/x64/bin/bundle:23:in `<main>'
Tasks: TOP => build
(See full trace by running task with --trace)

@Fryguy
Copy link
Member

Fryguy commented Sep 11, 2024

Should be fixed by #1812

@jrafanie
Copy link
Member

Weird it passed in the PR. 😕

@Fryguy
Copy link
Member

Fryguy commented Sep 11, 2024

This PR also "broke" the user reference page - https://github.com/ManageIQ/manageiq.org/blob/master/site/docs/reference/index.md?plain=1

I wonder if instead of hardcoding the sections we can more dynamically build it up. Even so, the {{}} stuff won't work there because it's dynamically built.

@jrafanie
Copy link
Member

This PR also "broke" the user reference page - https://github.com/ManageIQ/manageiq.org/blob/master/site/docs/reference/index.md?plain=1

I wonder if instead of hardcoding the sections we can more dynamically build it up. Even so, the {{}} stuff won't work there because it's dynamically built.

@qahmed1998 see above

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

Successfully merging this pull request may close these issues.

5 participants