provisioning: add instructions for OpenStack #202
Conversation
dustymabe
force-pushed
the
dusty-add-openstack
branch
from
7209258
to
9843a68
Compare
|
|
||
| == Prerequisites | ||
|
|
||
| Before provisioning a FCOS machine, you must have an Ignition configuration file |
There was a problem hiding this comment.
Aside: looks like we inconsistently use "a FCOS" and "an FCOS" throughout the docs. We should decide on one and clean up the docs in a follow-up.
There was a problem hiding this comment.
I'm cool with that. Want to open an issue?
| by using a `clouds.yaml` file or via environment variables. If you're starting from scratch, this | ||
| environment may need networks, ssh keypairs, security groups, etc.. set up. Please consult the | ||
| https://docs.openstack.org/[OpenStack Documentation] to learn more. | ||
|
|
There was a problem hiding this comment.
Should we mention here what version of OpenStack the instructions below are tested against?
|
|
||
| == Downloading an OpenStack Image | ||
|
|
||
| Fedora CoreOS is designed to be updated automatically, with different schedules per stream. |
There was a problem hiding this comment.
Should we link to https://docs.fedoraproject.org/en-US/fedora-coreos/update-streams/ here?
There was a problem hiding this comment.
Added a NOTE: to mention it.
| FCOS_VERSION='...' | ||
| FILE=fedora-coreos-${FCOS_VERSION}-openstack.x86_64.qcow2 |
There was a problem hiding this comment.
Minor/optional: meh... I'd just pick a sample version here and roll with that. I think it's understood that they'd sub in the filename they actually have.
There was a problem hiding this comment.
Yeah, I copy and pasted this from another guide. I think all of them could probably use a single person going through and updating each of them so the language and common steps are a bit more consistent.
| ---- | ||
| FCOS_VERSION='...' | ||
| FILE=fedora-coreos-${FCOS_VERSION}-openstack.x86_64.qcow2 | ||
| IMAGE=${FILE:0:-6} # pull off .qcow2 |
There was a problem hiding this comment.
I think the canonical "shell way" to strip extensions is e.g. basename $FILE .qcow2
There was a problem hiding this comment.
wow. I've run basename $FILE in the past many times, but never used it to pull off a suffix. TIL
I still think I'd prefer to keep it the way it is, without calling out to a binary to do the same thing.
| ---- | ||
|
|
||
| Now you should be able to SSH into the instance using the IP address | ||
| associated with the floating IP. If you didn't change the defaults the |
There was a problem hiding this comment.
Minor:
| associated with the floating IP. If you didn't change the defaults the | |
| associated with the floating IP. If you didn't change the defaults, the |
There was a problem hiding this comment.
Super minor: I noticed you 👍 this, but I don't see it in the latest push.
There was a problem hiding this comment.
Sorry, I did indeed miss making that change. Should be done now!
dustymabe
force-pushed
the
dusty-add-openstack
branch
from
9843a68
to
0df2e13
Compare
|
ok I think I addressed all comments. |
dustymabe
force-pushed
the
dusty-add-openstack
branch
from
0df2e13
to
7e05807
Compare
No description provided.