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

Add openstack as a testing platform #804

Merged
merged 5 commits into from
Mar 3, 2021

Conversation

TheRealFalcon
Copy link
Member

@TheRealFalcon TheRealFalcon commented Feb 8, 2021

Proposed Commit Message

Add openstack as a testing platform

Test Steps

set OPENSTACK_NETWORK appropriately in user_settings.py. Then
CLOUD_INIT_PLATFORM=openstack CLOUD_INIT_OS_IMAGE=3709d596-ce0d-45ac-976a-9d2f3ce46474 pytest tests/integration_tests

Checklist:

  • My code follows the process laid out in the documentation
  • I have updated or added any unit tests accordingly
  • I have updated or added any documentation accordingly

@TheRealFalcon TheRealFalcon added the wip Work in progress, do not land label Feb 8, 2021
Copy link
Collaborator

@OddBloke OddBloke left a comment

Choose a reason for hiding this comment

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

I've successfully run a test! A couple of small "UI" things I hit while getting that working, will review properly next.

Comment on lines 339 to 340
'When using Openstack, `OS_IMAGE` parameter MUST take the '
'form of a 36-character UUID. Passing in a release name is '
Copy link
Collaborator

Choose a reason for hiding this comment

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

OS_IMAGE can still take its :: separated form (and arguably should, given we can't possibly infer OS/release at the moment), it's just the first component of that form which is constrained in this way. Something along the lines of "OS_IMAGE MUST be specified with a 36-character UUID image ID", perhaps?

Copy link
Collaborator

Choose a reason for hiding this comment

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

This still needs addressing, I think?

@github-actions
Copy link

Hello! Thank you for this proposed change to cloud-init. This pull request is now marked as stale as it has not seen any activity in 14 days. If no activity occurs within the next 7 days, this pull request will automatically close.

If you are waiting for code review and you are seeing this message, apologies! Please reply, tagging mitechie, and he will ensure that someone takes a look soon.

(If the pull request is closed and you would like to continue working on it, please do tag mitechie to reopen it.)

@github-actions github-actions bot added the stale-pr Pull request is stale; will be auto-closed soon label Feb 25, 2021
@TheRealFalcon TheRealFalcon removed the stale-pr Pull request is stale; will be auto-closed soon label Mar 1, 2021
@TheRealFalcon
Copy link
Member Author

@OddBloke Sorry, not looking for another review on this one yet. I'm waiting to for the pycloudlib one to land before fixing this one up.

@TheRealFalcon TheRealFalcon removed the wip Work in progress, do not land label Mar 2, 2021
@TheRealFalcon TheRealFalcon changed the title WIP: Add openstack as a testing platform Add openstack as a testing platform Mar 2, 2021
@TheRealFalcon TheRealFalcon requested a review from OddBloke March 3, 2021 14:09
@OddBloke
Copy link
Collaborator

OddBloke commented Mar 3, 2021

Drive-by thought before a meeting: do we need to expand the environment variables that tox will allow through for the OpenStack library to find credentials?

Copy link
Collaborator

@OddBloke OddBloke left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

I'm seeing a few test failures locally, some of which are because I'm not using the latest cloud-init dev version; regardless, we can clean up any rough edges in follow-ups.

Comment on lines +347 to +348
'a 36-character UUID image ID. Passing in a release name is '
'not valid here.\n'
Copy link
Collaborator

Choose a reason for hiding this comment

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

Nice clarification!

@TheRealFalcon
Copy link
Member Author

Drive-by thought before a meeting: do we need to expand the environment variables that tox will allow through for the OpenStack library to find credentials?

I don't think so. We've wildcarded the CLOUD_INIT_* env vars, so for an openstack test, the network would get passed as CLOUD_INIT_OPENSTACK_NETWORK.

@OddBloke OddBloke merged commit 3dd3de7 into canonical:master Mar 3, 2021
@OddBloke
Copy link
Collaborator

OddBloke commented Mar 3, 2021

Drive-by thought before a meeting: do we need to expand the environment variables that tox will allow through for the OpenStack library to find credentials?

I don't think so. We've wildcarded the CLOUD_INIT_* env vars, so for an openstack test, the network would get passed as CLOUD_INIT_OPENSTACK_NETWORK.

Maybe this is another oddity of my workflow, but I source my Nova credentials (populating a bunch of OS_* envvars); #830 fixes it for me locally.

@TheRealFalcon TheRealFalcon deleted the openstack branch March 3, 2021 20:53
@TheRealFalcon
Copy link
Member Author

Oooooh, right. Yeah, I use env vars too.

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.

2 participants