RE: [DISCUSS] Primate - new UI for CloudStack?

Lol - with great power comes great responsibility David! Actually this is a discussion thread, once any issues which people may raise are ironed out I expect Rohit will start a VOTE on a concrete proposal and timeline. -- For anyone not used to this process, now would be a good time to explain

Re: [DISCUSS] Primate - new UI for CloudStack?

I like the idea of separating the UI from the main code base. I think that will provide a lot more flexibility moving forward and the project is well overdue for a new look and feel. I think the time frame proposed to sunset the old UI is doable and we'll need some feedback from those using it

Re: [DISCUSS] Primate - new UI for CloudStack?

+1 to the new UI as it supports: 1. Faster development of features 2. Better experience as a user 3. Easy customisation declaratively Regards, Anurag > On 20-Sep-2019, at 8:17 AM, Siddhartha Kattoju wrote: > > +1 from me as well. > > Just a side note: I feel like there is a high risk of

Re: [DISCUSS] Primate - new UI for CloudStack?

+1 from me as well. Just a side note: I feel like there is a high risk of tldr here. May be its just me. It may be would be good to put most of the details in a wiki page and just post a summarized version on the list ? *Sid Kattoju* Cloud Software Architect | Professional Services c

Re: [URGENT] - your presentation desc

Hi Andrija, Thanks for your work. Can you share the YouTube link if its ready? Cheers Sven __ Sven Vogel Teamlead Platform EWERK DIGITAL GmbH Brühl 24, D-04109 Leipzig P +49 341 42649 - 99 F +49 341 42649 - 98 s.vo...@ewerk.com www.ewerk.com Geschäftsführer: Dr. Erik Wende, Hendrik

[GitHub] [cloudstack-kubernetes-provider] onitake commented on issue #6: Improved Ingress Controller example to be clearer and more complete

onitake commented on issue #6: Improved Ingress Controller example to be clearer and more complete URL: https://github.com/apache/cloudstack-kubernetes-provider/pull/6#issuecomment-533546965 What's wrong with Træfik? :smiley: I think an example for both would be even better. Feel

[GitHub] [cloudstack-kubernetes-provider] joschi36 commented on issue #6: Improved Ingress Controller example to be clearer and more complete

joschi36 commented on issue #6: Improved Ingress Controller example to be clearer and more complete URL: https://github.com/apache/cloudstack-kubernetes-provider/pull/6#issuecomment-533543728 maybe we could use the nginx-ingress to be a little more "standard/basic*?

[GitHub] [cloudstack-kubernetes-provider] onitake opened a new pull request #6: Improved Ingress Controller example to be clearer and more complete

onitake opened a new pull request #6: Improved Ingress Controller example to be clearer and more complete URL: https://github.com/apache/cloudstack-kubernetes-provider/pull/6 This PR expands the Ingress Controller example to a minimal viable config. It should illustrate the concept

Re: [DISCUSS] Primate - new UI for CloudStack?

Hi Rohit, been on CCC19NA and I'm fine with the whole idea (having seen everything, etc.) One thing to clarify: you mentioned "old UI reaches EOL in Winter lts 2020, old UI codebase is removed from codebase" - but later stated, that since we support LTS until 2022, that means "but, with no new

[DISCUSS] Primate - new UI for CloudStack?

All, == Summary == I have been working on a new, modern role-based UI for Cloudstack (project Primate: https://github.com/shapeblue/primate) I demoed this for the first time at CCCNA19 last week and it was very well received. It was discussed, at length, as an item in the hackathon and the

Re: VR/LB inject others options in haproxy.cfg

The new UI will be the best step forward. I think auto generated UI needs also a design and not only an api list. Thanks Wei for the PR... Von meinem iPhone gesendet __ Sven Vogel Teamlead Platform EWERK DIGITAL GmbH Brühl 24, D-04109 Leipzig P +49 341 42649 - 99 F +49 341 42649 - 98

[GitHub] [cloudstack-kubernetes-provider] onitake opened a new issue #5: Submit request to integrate into Kubernetes documentation

onitake opened a new issue #5: Submit request to integrate into Kubernetes documentation URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/5 Now that transfer to the ASF is complete, the project should be submitted to be advertised as the "official" CloudStack provider

[GitHub] [cloudstack-kubernetes-provider] onitake opened a new issue #4: [OLD] Document how to run a fully simulated dev/test environment

onitake opened a new issue #4: [OLD] Document how to run a fully simulated dev/test environment URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/4 Moved from: https://github.com/swisstxt/cloudstack-cloud-controller-manager/issues/6 The documentation should

[GitHub] [cloudstack-kubernetes-provider] onitake opened a new issue #3: [OLD] Implement IP whitelists

onitake opened a new issue #3: [OLD] Implement IP whitelists URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/3 Moved from: https://github.com/swisstxt/cloudstack-cloud-controller-manager/issues/7 Other CCMs/cloud providers support source IP whitelisting via

[GitHub] [cloudstack-kubernetes-provider] onitake opened a new issue #2: [OLD] Changing from TCP to TCP Proxy doesn't work

onitake opened a new issue #2: [OLD] Changing from TCP to TCP Proxy doesn't work URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/2 Moved from: https://github.com/swisstxt/cloudstack-cloud-controller-manager/issues/8 I tried changing from TCP to TCP-Proxy (with

Re: VR/LB inject others options in haproxy.cfg

Hi Gregor, Agree that it would be nice to have a better UI. However, I am not a frontend developer. The settings are not set frequently so we think it is good enough. Let's see what we can improve when we have a new cloudstack UI (proposed by Rohit on CCC NA 19). -Wei On Fri, 20 Sep 2019 at

Re: VR/LB inject others options in haproxy.cfg

Nice! I wonder if LB configuration could be put into a dedicated UI. Editing network and rule tags seems a bit clunky. The disadvantage would be that the UI has to be adapted whenever support for new options is added. Maybe an autogenerated UI from the list of supported tags is possible?