-
Notifications
You must be signed in to change notification settings - Fork 280
📖 doc/development: add devstack notes #1569
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
📖 doc/development: add devstack notes #1569
Conversation
this is notes from my setup, it can be useful for folks who want to develop CAPO with a single devstack instance. Signed-off-by: Mathieu Tortuyaux <[email protected]>
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
With this dev setup, it might be useful to enable DHCP for the public subnet: | ||
Admin > Network > Networks > `public` > Subnets > `public-subnet` > Edit Subnet > Subnet Details > :ballot_box_with_check: Enable DHCP + Add DNS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where's that done?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's done from the Horizon dashboard.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth to say that. But in general I'd prefer doing that from the CLI instead. I'm guessing it's enable_dhcp
option on the subnet?
LOGFILE=$DEST/logs/stack.sh.log | ||
VERBOSE=True | ||
LOG_COLOR=True | ||
enable_service rabbit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not needed, it's in the defaults: https://github.com/openstack/devstack/blob/c424a7a299e37004d318107648bb18e157344985/stackrc#L64-L83
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to know. Thanks!
enable_plugin neutron $GIT_BASE/openstack/neutron | ||
# Octavia supports using QoS policies on the VIP port: | ||
enable_service q-qos | ||
enable_service placement-api placement-client |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here.
enable_plugin octavia-tempest-plugin $GIT_BASE/openstack/octavia-tempest-plugin | ||
enable_service octavia o-api o-cw o-hm o-hk o-da | ||
# Cinder | ||
enable_service c-api c-vol c-sch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mm, initially it was not there and Cinder was not enabled. Is it possible that the octavia
service activation prevent the default services to be activated because it does not meet this condition: https://github.com/openstack/devstack/blob/c424a7a299e37004d318107648bb18e157344985/stackrc#L64 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, maybe one of the plugins disable that? Anyway we get e.g. n-cpu somehow, so I guess it's somewhere else.
# Cinder | ||
enable_service c-api c-vol c-sch | ||
# Tempest | ||
enable_service tempest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What to we want Tempest for? It's enabled by default, but I would disable it for a dev env.
enable_service c-api c-vol c-sch | ||
# Tempest | ||
enable_service tempest | ||
EOF |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a minimal setup I'd consider disabling Horizon:
disable_service horizon
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As seen in a previous comment, Horizon dashboard can be useful to configure the network.
Do you know my WIP PR #1539? I think this is mainly the same (and a bit more 🙂) as your documentation. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mdbooth, tormath1 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has been hanging for a while. I would say it is better to have the notes merged than polishing them forever so merging.
/lgtm
/hold cancel
this is notes from my setup, it can be useful for folks who want to develop CAPO with a single DevStack instance.
What this PR does / why we need it: This PR adds some documentation notes for CAPO development on a single DevStack instance.
/hold