Option to save session information in adapter

[andrejcermak]

Is there any way of saving session information when submitting a job and then reading this information on job deletion inside adapter?

[johrstrom]

No I think that's better handled at the OOD layer. This library doesn't really have the concept of a session whereas OOD does.

[andrejcermak]

@johrstrom thank you for your reply. Do you have any suggestions how to do that? The idea was to create some credentials in my adapter when submitting the job and then destroy those credentials when deleting the job.

[johrstrom]

Let me transfer this ticket to that repository. IDK about deleting credentials (in a 3rd party DB or something?) but you can use conn_params to generate additional information to be used in the view.html.erb to connect to the app:

https://osc.github.io/ood-documentation/latest/how-tos/app-development/interactive/conn-params.html

[andrejcermak]

but you can use conn_params to generate additional information to be used in the view.html.erb to connect to the app:

I need the credentials for the access to the scheduler to create the job and then delete them after the job is executed. Therefore I think the OOD layer wont be really helpful.

[johrstrom]

OK I guess I can transfer it back. We do something similar for kubernetes, but it's not per job, it bootstaps the credentials when you login.

[andrejcermak]

I think you're referring to the hook functionality. Yeah that is similar to what I am trying to achieve, but I hoped that I would be able to move that kind of functionality inside the adapter.

I am talking about the coder adapter as I am trying to refine the credential handling. The issue is that users can have multiple projects in openstack and will have to have multiple credentials for each project if we adopted the approach from kubernetes.

My idea of a new approach was to create the credentials in the submit function of the coder adapter, save the credentials in the OOD session somehow and then delete the credentials once the job is stopped/deleted.

[johrstrom]

Not just hooks - we made this initializer in OOD that calls bits of the Kubernetes adapter.

https://github.com/OSC/ondemand/blob/master/apps/dashboard/config/initializers/k8s.rb#L8

[johrstrom]

My idea of a new approach was to create the credentials in the submit function of the coder adapter, save the credentials in the OOD session somehow and then delete the credentials once the job is stopped/deleted.

That sounds about right.