You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During my POC testing of hooks in Carbon, I was having a hard time using the new boot log collection hooks using the example from docs/workspaces/openstack-simple. Specifically it fails with
Based on the openstack openstack cli docs openstack command will either use any OS_* variables exported or any cloud.yml files in the following directories
Current Directory
~/.config/openstack
/etc/openstack
Once it finds the cloud yaml you still need to specify which cloud profile to use either using the OS_CLOUD variable or CLI option --os-cloud=<profile name>
In my testing I'm using the the clouds.yml and passing it to linchpin using the credentials key in the pinfile. The current implementation of the os_server_boot_log won't work unles the OS_* variables are exported.
I think right now the only one that can probably work with the credentials file option is the Azure one. The OS, EC2, and OCP ones probably won't work.
Plus I think user documentation is missing, I couldn't find anything on the new hooks or at the very least what are the specific vars/params that need to be specified in the cfgs or layout section of the PinFile/Topology that the built in hook requires to function.
To Reproduce
Steps to reproduce the behavior:
pip install linchpin
cd `docs/workspace
Scroll down to '....'
See error
The text was updated successfully, but these errors were encountered:
Describe the bug
During my POC testing of hooks in Carbon, I was having a hard time using the new boot log collection hooks using the example from
docs/workspaces/openstack-simple
. Specifically it fails withBased on the openstack openstack cli docs openstack command will either use any OS_* variables exported or any
cloud.yml
files in the following directoriesOnce it finds the cloud yaml you still need to specify which cloud profile to use either using the
OS_CLOUD
variable or CLI option--os-cloud=<profile name>
In my testing I'm using the the clouds.yml and passing it to linchpin using the credentials key in the pinfile. The current implementation of the os_server_boot_log won't work unles the OS_* variables are exported.
I think right now the only one that can probably work with the credentials file option is the Azure one. The OS, EC2, and OCP ones probably won't work.
Plus I think user documentation is missing, I couldn't find anything on the new hooks or at the very least what are the specific vars/params that need to be specified in the
cfgs
orlayout
section of thePinFile/Topology
that the built in hook requires to function.To Reproduce
Steps to reproduce the behavior:
pip install linchpin
The text was updated successfully, but these errors were encountered: