Skip to content

Conversation

@mandre
Copy link

@mandre mandre commented Aug 19, 2019

No description provided.

For the time being, the OpenStack platform is not supported in the prompts. We will instead provide you with a template `install-config.yaml` to use below. If you want to go beyond the basic customizations we display below, there is more information available in [this document](customization.md). We have labled sections in the yaml below with the following syntax: (#). Look for the numbers below the template for explanations of how to complete those sections.
You could either use the interactive wizard to configure the installation or provide an `install-config.yaml` file for it. See [all possible customization](customization.md) via the `install-config.yaml` file.

```yaml

Choose a reason for hiding this comment

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

I kinda liked having this, I feel like it was a good way to communicate how to use the install config

Choose a reason for hiding this comment

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

Why dont we move this to customization.yaml?

Copy link
Author

Choose a reason for hiding this comment

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

It was duplicating the info from the customization.md doc, so it had to move.

Now, idk if we want to follow the same format in customization.md... I also like how customization.md is consistent across the different platforms.

Choose a reason for hiding this comment

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

Yeah, I suppose we should keep it consistent with what other platforms are doing

openstack floating ip create --port <ingress port id> <external network>
```

### Without Floating IPs

Choose a reason for hiding this comment

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

This was specifically targed towards people who were running providern-network clusters

Copy link
Author

Choose a reason for hiding this comment

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

how common do you think it will be for real-life deployments? Perhaps we could mention it in the developers documentation instead -- I feel it's out of place in the user doc.

Choose a reason for hiding this comment

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

I dont know to be honest, Tomas would know more than I do. Maybe we can add a thing for it in the dev docs later.

@iamemilio
Copy link

/lgtm

@iamemilio
Copy link

(I know it doesnt work this way)

@Fedosin Fedosin merged this pull request into Fedosin:user_docs Aug 19, 2019
@mandre mandre deleted the user_docs branch September 17, 2020 08:58
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

Successfully merging this pull request may close these issues.

3 participants