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
Hey @mnaser, so far no preparation work has been done. A prerequisite is to have openapi for it. Looking at the magnum code I see it uses wsme (similarly to octavia which is already supported) and some validation decorators it should be feasible.
Even if it is not possible to extract reasonable schemas from the code it is still possible to (at least temporarily) hardcode those in the codegenerator. Once codegerator has access to openapi adding support is not a problem at all.
I will start looking at the magnum openapi generation, so pls be patient ;-)
Hey @mnaser, first stuff is now included in the 0.10.0. There is still something known to be fixed: cluster actions are missing, edit for resources is a patch so I am wondering what good UX can be implemented for that at all. I would still love if you give it a try and report whether it is working good or not. I haven't deployed a devstack with magnum support yet so I was not having possibility to test it is practice anywhere.
Are you interested in seeing some of the resources in TUI? I was thinking that maybe listing clusters may be useful.
In general I found the api-ref of Magnum a nightmare - codegenerator found something like 2x amount of undocumented apis
Activity
gtema commentedon Feb 28, 2025
Hey @mnaser, so far no preparation work has been done. A prerequisite is to have openapi for it. Looking at the magnum code I see it uses wsme (similarly to octavia which is already supported) and some validation decorators it should be feasible.
Even if it is not possible to extract reasonable schemas from the code it is still possible to (at least temporarily) hardcode those in the codegenerator. Once codegerator has access to openapi adding support is not a problem at all.
I will start looking at the magnum openapi generation, so pls be patient ;-)
gtema commentedon Mar 14, 2025
Hey @mnaser, first stuff is now included in the 0.10.0. There is still something known to be fixed: cluster actions are missing, edit for resources is a patch so I am wondering what good UX can be implemented for that at all. I would still love if you give it a try and report whether it is working good or not. I haven't deployed a devstack with magnum support yet so I was not having possibility to test it is practice anywhere.
Are you interested in seeing some of the resources in TUI? I was thinking that maybe listing clusters may be useful.
In general I found the api-ref of Magnum a nightmare - codegenerator found something like 2x amount of undocumented apis
mnaser commentedon Mar 26, 2025
Thanks—I’ll try and get to this soon and check it out.