SamuelMarks commented on issue #2045: URL: https://github.com/apache/libcloud/issues/2045#issuecomment-2695569860
So my literally _10-year old solution_ for marshalling libcloud constructs into JSON is what I'm using https://github.com/offscale/offutils-strategy-register/blob/master/offutils_strategy_register/__init__.py#L97C1-L101C2 I've also moved the content to this page https://verman.io/multicloud.html as its name better defines its function. Will see how far I can get with CORS and everything else in the way. (here's the code ) But here's what I'm thinking: - Make sizes, networks, nodes all JSON marshallable _properly_; not hacked together with `dir` and `getattr` [@Kami did you want to do this one?] - Finish up the collection of data from local storage for authentication purposes by using keyword arguments over splatting a tuple - Add a basic workflow: 0. Specify provider 1. Set provider auth details 2. <makes possibly remote call> 3. Select image size from dropdown 4. <makes possibly remote call> 5. Select image from searchable dropdown 6. <makes remote call> 7. Specify network or whether to create new; and special settings (maybe just static IP for now; don't want to go crazy on options!) 8. <makes remote call> 9. Specify firewall / ports or whether to create new 10. Show [editable] script that will be bootstrapped onto node 11. Provide "Execute" / "Deploy" button to 'enact the plan' on click 12. Illustrate progress in HTML with a scrolling log window Once this is working I might do something similar for Object Storage like S3. If CORS ends up being too much of a struggle to the point of impossibility without incorporating some crazy overlay network [e.g., webvm uses tailscale] then it might be easier—and possibly more user-friend—to wrap this up with tauri as a desktop web-app. What do you think of the plan? PS: As for the libcloud homepage, I suppose this should suffice: 0. Specify provider; 1. Set provider auth details; 2. Show Python REPL to user with libcloud already imported -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@libcloud.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
