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

[Paul Angus]

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 
Apache voting rules (https://www.apache.org/foundation/voting.html)

From PMC members on code changes:
+1 = yes I agree, lets do this
0 = I don't mind/care either way
-1 = I object to this change (VETO)

From the rest of the community on code changes:
+1 = yes I agree, lets do this
0 = I don't mind/care either way
-1 = I don't like this change.

As this change would effect so many people, I would hope that any issues would 
be raised during the discussion and a mutually acceptable way forward found, 
before we get as far as a vote.  


Kind regards


Paul Angus





paul.an...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: David Merrill  
Sent: 20 September 2019 18:27
To: us...@cloudstack.apache.org
Subject: Re: [DISCUSS] Primate - new UI for CloudStack?

I love this idea. Separating the UI from the code-base and crafting an API 
driven UI presents excellent opportunities for customizable UIs (and getting 
folks involved with making them) which can improve user experience.

I'd love to get involved and looking forward to trying it out.

+1 (I've never +1'ed anything before, is it OK? Can I vote?) :)

David Merrill
Senior Systems Engineer,
Managed and Private/Hybrid Cloud Services OTELCO
92 Oak Street, Portland ME 04101
office 207.772.5678  
http://www.otelco.com/cloud-and-managed-services
 
Confidentiality Message
The information contained in this e-mail transmission may be confidential and 
legally privileged. If you are not the intended recipient, you are notified 
that any dissemination, distribution, copying or other use of this information, 
including attachments, is prohibited. If you received this message in error, 
please call me at 207.772.5678  so this error can be 
corrected.
 

On 9/20/19, 12:52 PM, "Simon Weller"  wrote:

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 today (we have our own UI, so this 
doesn't affect us).

One of our challenges over the last few years is the added work of getting 
UI features into the release and it has added around 30% additional work load 
due to the older style code of the current UI. Having it in VUE is great and I 
think it will also encourage others to contribute.

+1.


From: Anurag A 
Sent: Friday, September 20, 2019 11:26 AM
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: 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 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 514.466.0951
>
>
> * *
>
>
>
>
> On Fri, Sep 20, 2019 at 8:10 AM Rohit Yadav 
> wrote:
>
>> 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 general 
consensus
>> there was that this could become Cloudstacks new UI. We discussed a plan 
to
>> achieve that and now I’m bringing that plan to the list for discussion.
>>
>>
>>
>> == Background ==
>>
>>
>> The current CloudStack UI has grown technical debt over time and it has
>> become harder to extend, develop, maintain in the long run, it is also
>> difficult for new contributors to learn and get started. Since late 
2018, I
>> started working on a side-project with the aim to create a modern
>> progressive and role-based declaratively-programmed UI for CloudStack,
>> called Primate. Before creating Primate, I set out to create a list of 
core
>> requirements of what would give us an extensible, modern UI that was easy
>> 

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

[Simon Weller]

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 today (we have our own UI, so this doesn't 
affect us).

One of our challenges over the last few years is the added work of getting UI 
features into the release and it has added around 30% additional work load due 
to the older style code of the current UI. Having it in VUE is great and I 
think it will also encourage others to contribute.

+1.


From: Anurag A 
Sent: Friday, September 20, 2019 11:26 AM
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: 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 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 514.466.0951
>
>
> * *
>
>
>
>
> On Fri, Sep 20, 2019 at 8:10 AM Rohit Yadav 
> wrote:
>
>> 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 general consensus
>> there was that this could become Cloudstacks new UI. We discussed a plan to
>> achieve that and now I’m bringing that plan to the list for discussion.
>>
>>
>>
>> == Background ==
>>
>>
>> The current CloudStack UI has grown technical debt over time and it has
>> become harder to extend, develop, maintain in the long run, it is also
>> difficult for new contributors to learn and get started. Since late 2018, I
>> started working on a side-project with the aim to create a modern
>> progressive and role-based declaratively-programmed UI for CloudStack,
>> called Primate. Before creating Primate, I set out to create a list of core
>> requirements of what would give us an extensible, modern UI that was easy
>> to develop now and in the future. These are the requirements I came up with:
>>
>>  *   designed from ground up to be  a complete replacement for our
>> combined user/admin UI
>>  *   to respect all entities in cloudstack and not make assumptions on
>> use-cases of cloudstack
>>  *   data-driven and auto-generation of UI widgets and to be easy to
>> learn, develop, extend, customise and maintain.
>>  *   declarative programming
>>  *   support for API discovery and parameter completion like CloudMonkey
>>  *   support for custom roles
>>
>>
>>
>> I looked at existing Cloudstack UI projects but none of them fully
>> satisfied all these requirements and started Primate.
>>
>>
>>
>> == Project Primate ==
>>
>>
>> For the implementation, I compared a couple of opensource JS and UI
>> frameworks and decided to use VueJS (https://vuejs.org)
>> which is a JavaScript framework and AntD (https://ant.design<
>> https://ant.design/>) which is a UI design language with a well-defined
>> spec, styling guide, and an implementation-specific to VueJS. VueJS was
>> selected because among a few other JS frameworks I surveyed it was the
>> easiest (for me) to learn and get started. I also surveyed a few UI
>> frameworks and selected AntD because it came with a well-defined spec,
>> styling guide and VueJS specific implementation which gives several
>> re-usable components out of the box.
>>
>>
>>
>> During the development of Primate, I used my previous experience from
>> CloudMonkey and another PoC angular-based UI ProjectX, and it currently
>> supports:
>>
>>  *   role-based UI based on API autodiscovery
>>  *   auto-generated action/API forms with parameter completion
>>  *   declarative component-driven views
>>  *   modern programming methodologies (hot reloading, npm based
>> build/run/compile etc.)
>>  *   decoupled from core Cloudstack code
>>  *   dynamic translation (most/many of old translation files ported)
>>  *   includes dashboards, async job/API polling, all list views/tables
>> per the old UI
>>  *   browser history and url/route driven navigation
>>  *   support for mobiles/tables/desktop screens
>>  *   configuration driven UI customisation (of navigation, icons, APIs
>> etc)
>>
>>
>>
>> To get to this point, I’ve had some valuable help from Anurag and Sven et
>> al at EWerk.
>> The development strategy to support all APIs out of the box in a
>> data-driven way gives a functioning UI 

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

[Anurag A]

+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 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 514.466.0951
> 
> 
> * *
> 
> 
> 
> 
> On Fri, Sep 20, 2019 at 8:10 AM Rohit Yadav 
> wrote:
> 
>> 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 general consensus
>> there was that this could become Cloudstacks new UI. We discussed a plan to
>> achieve that and now I’m bringing that plan to the list for discussion.
>> 
>> 
>> 
>> == Background ==
>> 
>> 
>> The current CloudStack UI has grown technical debt over time and it has
>> become harder to extend, develop, maintain in the long run, it is also
>> difficult for new contributors to learn and get started. Since late 2018, I
>> started working on a side-project with the aim to create a modern
>> progressive and role-based declaratively-programmed UI for CloudStack,
>> called Primate. Before creating Primate, I set out to create a list of core
>> requirements of what would give us an extensible, modern UI that was easy
>> to develop now and in the future. These are the requirements I came up with:
>> 
>>  *   designed from ground up to be  a complete replacement for our
>> combined user/admin UI
>>  *   to respect all entities in cloudstack and not make assumptions on
>> use-cases of cloudstack
>>  *   data-driven and auto-generation of UI widgets and to be easy to
>> learn, develop, extend, customise and maintain.
>>  *   declarative programming
>>  *   support for API discovery and parameter completion like CloudMonkey
>>  *   support for custom roles
>> 
>> 
>> 
>> I looked at existing Cloudstack UI projects but none of them fully
>> satisfied all these requirements and started Primate.
>> 
>> 
>> 
>> == Project Primate ==
>> 
>> 
>> For the implementation, I compared a couple of opensource JS and UI
>> frameworks and decided to use VueJS (https://vuejs.org)
>> which is a JavaScript framework and AntD (https://ant.design<
>> https://ant.design/>) which is a UI design language with a well-defined
>> spec, styling guide, and an implementation-specific to VueJS. VueJS was
>> selected because among a few other JS frameworks I surveyed it was the
>> easiest (for me) to learn and get started. I also surveyed a few UI
>> frameworks and selected AntD because it came with a well-defined spec,
>> styling guide and VueJS specific implementation which gives several
>> re-usable components out of the box.
>> 
>> 
>> 
>> During the development of Primate, I used my previous experience from
>> CloudMonkey and another PoC angular-based UI ProjectX, and it currently
>> supports:
>> 
>>  *   role-based UI based on API autodiscovery
>>  *   auto-generated action/API forms with parameter completion
>>  *   declarative component-driven views
>>  *   modern programming methodologies (hot reloading, npm based
>> build/run/compile etc.)
>>  *   decoupled from core Cloudstack code
>>  *   dynamic translation (most/many of old translation files ported)
>>  *   includes dashboards, async job/API polling, all list views/tables
>> per the old UI
>>  *   browser history and url/route driven navigation
>>  *   support for mobiles/tables/desktop screens
>>  *   configuration driven UI customisation (of navigation, icons, APIs
>> etc)
>> 
>> 
>> 
>> To get to this point, I’ve had some valuable help from Anurag and Sven et
>> al at EWerk.
>> The development strategy to support all APIs out of the box in a
>> data-driven way gives a functioning UI and scope to customise
>> views/components over time. Support to declaratively add actions on all
>> views and some action/customisation (ex. vm/zone deployment wizard) is in
>> progress. The work was recently discussed and demo-ed at CCCNA19, the
>> slides of my talk are here:
>> https://rohityadav.cloud/files/talks/cccna19-primate.pdf
>> 
>> 
>> 
>> == Discussion ==
>> 
>> 
>> 
>> With this discussion thread, I want to propose the idea hatched in the
>> recent hackathon for Primate to become the next UI for CloudStack. I’d like
>> to seek everybody's thoughts, feedback, comments, and reviews on that idea.
>> 
>> Obviously, part of any new UI project would mean that the existing UI
>> development would eventually get abandoned. In the hackathon we discussed a
>> potential plan to formally deprecate the old 

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

[Siddhartha Kattoju]

+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 514.466.0951


* *




On Fri, Sep 20, 2019 at 8:10 AM Rohit Yadav 
wrote:

> 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 general consensus
> there was that this could become Cloudstacks new UI. We discussed a plan to
> achieve that and now I’m bringing that plan to the list for discussion.
>
>
>
> == Background ==
>
>
> The current CloudStack UI has grown technical debt over time and it has
> become harder to extend, develop, maintain in the long run, it is also
> difficult for new contributors to learn and get started. Since late 2018, I
> started working on a side-project with the aim to create a modern
> progressive and role-based declaratively-programmed UI for CloudStack,
> called Primate. Before creating Primate, I set out to create a list of core
> requirements of what would give us an extensible, modern UI that was easy
> to develop now and in the future. These are the requirements I came up with:
>
>   *   designed from ground up to be  a complete replacement for our
> combined user/admin UI
>   *   to respect all entities in cloudstack and not make assumptions on
> use-cases of cloudstack
>   *   data-driven and auto-generation of UI widgets and to be easy to
> learn, develop, extend, customise and maintain.
>   *   declarative programming
>   *   support for API discovery and parameter completion like CloudMonkey
>   *   support for custom roles
>
>
>
> I looked at existing Cloudstack UI projects but none of them fully
> satisfied all these requirements and started Primate.
>
>
>
> == Project Primate ==
>
>
> For the implementation, I compared a couple of opensource JS and UI
> frameworks and decided to use VueJS (https://vuejs.org)
> which is a JavaScript framework and AntD (https://ant.design<
> https://ant.design/>) which is a UI design language with a well-defined
> spec, styling guide, and an implementation-specific to VueJS. VueJS was
> selected because among a few other JS frameworks I surveyed it was the
> easiest (for me) to learn and get started. I also surveyed a few UI
> frameworks and selected AntD because it came with a well-defined spec,
> styling guide and VueJS specific implementation which gives several
> re-usable components out of the box.
>
>
>
> During the development of Primate, I used my previous experience from
> CloudMonkey and another PoC angular-based UI ProjectX, and it currently
> supports:
>
>   *   role-based UI based on API autodiscovery
>   *   auto-generated action/API forms with parameter completion
>   *   declarative component-driven views
>   *   modern programming methodologies (hot reloading, npm based
> build/run/compile etc.)
>   *   decoupled from core Cloudstack code
>   *   dynamic translation (most/many of old translation files ported)
>   *   includes dashboards, async job/API polling, all list views/tables
> per the old UI
>   *   browser history and url/route driven navigation
>   *   support for mobiles/tables/desktop screens
>   *   configuration driven UI customisation (of navigation, icons, APIs
> etc)
>
>
>
> To get to this point, I’ve had some valuable help from Anurag and Sven et
> al at EWerk.
> The development strategy to support all APIs out of the box in a
> data-driven way gives a functioning UI and scope to customise
> views/components over time. Support to declaratively add actions on all
> views and some action/customisation (ex. vm/zone deployment wizard) is in
> progress. The work was recently discussed and demo-ed at CCCNA19, the
> slides of my talk are here:
> https://rohityadav.cloud/files/talks/cccna19-primate.pdf
>
>
>
> == Discussion ==
>
>
>
> With this discussion thread, I want to propose the idea hatched in the
> recent hackathon for Primate to become the next UI for CloudStack. I’d like
> to seek everybody's thoughts, feedback, comments, and reviews on that idea.
>
> Obviously, part of any new UI project would mean that the existing UI
> development would eventually get abandoned. In the hackathon we discussed a
> potential plan to formally deprecate the old UI. I therefore think that
> this is something that needs discussion here and a vote if its going to
> happen.
>
>
>
> In summary, that plan is as follows (with proposed timeframes in
> [brackets]) :
>
>   *   allow the community to download & experience the UI
>   *   discuss and gather consensus around Primate [now]
>   *   take a vote on whether to take this plan forward 

Re: [URGENT] - your presentation desc

[Sven Vogel]

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 Schubert, Frank Richter
Registergericht: Leipzig HRB 9065

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

EWERK-Blog | LinkedIn | Xing | Twitter | Facebook

Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist 
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der 
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die 
E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential and 
may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.
> Am 19.09.2019 um 22:51 schrieb Andrija Panic :
>
> np - "was my pleasure" as polite people would say ;)
>
> I do have a 3-word "description" from our friends @Accelerite for one talk
> - so would be good to provide a proper description (need to check other
> presentations as well)
>
> Cheers
>
> On Thu, 19 Sep 2019 at 22:48, Siddhartha Kattoju 
> wrote:
>
>> Thank you for your efforts Andrija!
>>
>> BR/Sid
>>
>> On Thu., Sep. 19, 2019, 4:39 p.m. Anurag Awasthi, <
>> anurag.awas...@shapeblue.com> wrote:
>>
>>> Late night effect, Andrija! 
>>>
>>> Thank you for doing all the talk's/interviews recording at CCC!
>>>
>>> Regards,
>>> Anurag
>>> 
>>> From: Andrija Panic 
>>> Sent: Friday, September 20, 2019 2:05 AM
>>> To: dev 
>>> Cc: users 
>>> Subject: Re: [URGENT] - your presentation desc
>>>
>>> Was about to reply - that will work better - so YES (not enough beer
>>> apparently...)
>>>
>>> Disregard this thread...
>>>
>>> Thx Sid
>>>
>>> On Thu, 19 Sep 2019 at 22:25, Siddhartha Kattoju 
>>> wrote:
>>>
 Can you use the descriptions from the conference schedule ?

 On Thu., Sep. 19, 2019, 4:21 p.m. Andrija Panic, <
>>> andrija.pa...@gmail.com>
 wrote:

> Hi guys, speakers at CCC19NA/Las Vegas,
>
> As we speak - Rich Bowen is uploading 60GB of video material from
 CCC19NA /
> Las Vega - all talks from the CCC (that I recorded).
>
> @all speakers - I need an URGENT short description of your
>>> presentation -
> this will be placed on the "Description" field on YoutTube video.
>
> Please write the description in 3rd person "Andrija gave presentation
> about..." not "I will give presentation..."
>
> Feel free to send me a direct email (andrija.pa...@gmail.com or
> andrija.pa...@shapeblue.com) - or reply here.
>
> Thanks,
>
> --
>
> Andrija Panić
>

>>>
>>>
>>> --
>>>
>>> Andrija Panić
>>>
>>> anurag.awas...@shapeblue.com
>>> www.shapeblue.com
>>> Amadeus House, Floral Street, London  WC2E 9DPUK
>>> @shapeblue
>>>
>>>
>>>
>>>
>>
>
>
> --
>
> Andrija Panić

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

[GitBox]

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 free to add one to 
the PR!


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[GitBox]

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*?


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[GitBox]

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 better and explain how to configure Træfik 
to use the TCP-Proxy protocol.


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[Andrija Panic]

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 UI functionality after
summer 2020".

So just to clarify WHEN actually is the old UI being finally removed
(codebase removed) from the product.

Everything else - a humble +1 for the great work you've done.

Andrija

On Fri, 20 Sep 2019 at 14:10, Rohit Yadav  wrote:

> 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 general consensus
> there was that this could become Cloudstacks new UI. We discussed a plan to
> achieve that and now I’m bringing that plan to the list for discussion.
>
>
>
> == Background ==
>
>
> The current CloudStack UI has grown technical debt over time and it has
> become harder to extend, develop, maintain in the long run, it is also
> difficult for new contributors to learn and get started. Since late 2018, I
> started working on a side-project with the aim to create a modern
> progressive and role-based declaratively-programmed UI for CloudStack,
> called Primate. Before creating Primate, I set out to create a list of core
> requirements of what would give us an extensible, modern UI that was easy
> to develop now and in the future. These are the requirements I came up with:
>
>   *   designed from ground up to be  a complete replacement for our
> combined user/admin UI
>   *   to respect all entities in cloudstack and not make assumptions on
> use-cases of cloudstack
>   *   data-driven and auto-generation of UI widgets and to be easy to
> learn, develop, extend, customise and maintain.
>   *   declarative programming
>   *   support for API discovery and parameter completion like CloudMonkey
>   *   support for custom roles
>
>
>
> I looked at existing Cloudstack UI projects but none of them fully
> satisfied all these requirements and started Primate.
>
>
>
> == Project Primate ==
>
>
> For the implementation, I compared a couple of opensource JS and UI
> frameworks and decided to use VueJS (https://vuejs.org)
> which is a JavaScript framework and AntD (https://ant.design<
> https://ant.design/>) which is a UI design language with a well-defined
> spec, styling guide, and an implementation-specific to VueJS. VueJS was
> selected because among a few other JS frameworks I surveyed it was the
> easiest (for me) to learn and get started. I also surveyed a few UI
> frameworks and selected AntD because it came with a well-defined spec,
> styling guide and VueJS specific implementation which gives several
> re-usable components out of the box.
>
>
>
> During the development of Primate, I used my previous experience from
> CloudMonkey and another PoC angular-based UI ProjectX, and it currently
> supports:
>
>   *   role-based UI based on API autodiscovery
>   *   auto-generated action/API forms with parameter completion
>   *   declarative component-driven views
>   *   modern programming methodologies (hot reloading, npm based
> build/run/compile etc.)
>   *   decoupled from core Cloudstack code
>   *   dynamic translation (most/many of old translation files ported)
>   *   includes dashboards, async job/API polling, all list views/tables
> per the old UI
>   *   browser history and url/route driven navigation
>   *   support for mobiles/tables/desktop screens
>   *   configuration driven UI customisation (of navigation, icons, APIs
> etc)
>
>
>
> To get to this point, I’ve had some valuable help from Anurag and Sven et
> al at EWerk.
> The development strategy to support all APIs out of the box in a
> data-driven way gives a functioning UI and scope to customise
> views/components over time. Support to declaratively add actions on all
> views and some action/customisation (ex. vm/zone deployment wizard) is in
> progress. The work was recently discussed and demo-ed at CCCNA19, the
> slides of my talk are here:
> https://rohityadav.cloud/files/talks/cccna19-primate.pdf
>
>
>
> == Discussion ==
>
>
>
> With this discussion thread, I want to propose the idea hatched in the
> recent hackathon for Primate to become the next UI for CloudStack. I’d like
> to seek everybody's thoughts, feedback, comments, and reviews on that idea.
>
> Obviously, part of any new UI project would mean that the existing UI
> development would eventually get abandoned. In the hackathon we discussed a
> potential plan to formally deprecate the old UI. I therefore think that
> this is something that needs discussion here and a vote if its going to
> happen.
>
>
>
> In summary, that plan is as follows (with proposed timeframes in
> [brackets]) :
>

[DISCUSS] Primate - new UI for CloudStack?

[Rohit Yadav]

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 general consensus there was that 
this could become Cloudstacks new UI. We discussed a plan to achieve that and 
now I’m bringing that plan to the list for discussion.



== Background ==


The current CloudStack UI has grown technical debt over time and it has become 
harder to extend, develop, maintain in the long run, it is also difficult for 
new contributors to learn and get started. Since late 2018, I started working 
on a side-project with the aim to create a modern progressive and role-based 
declaratively-programmed UI for CloudStack, called Primate. Before creating 
Primate, I set out to create a list of core requirements of what would give us 
an extensible, modern UI that was easy to develop now and in the future. These 
are the requirements I came up with:

  *   designed from ground up to be  a complete replacement for our combined 
user/admin UI
  *   to respect all entities in cloudstack and not make assumptions on 
use-cases of cloudstack
  *   data-driven and auto-generation of UI widgets and to be easy to learn, 
develop, extend, customise and maintain.
  *   declarative programming
  *   support for API discovery and parameter completion like CloudMonkey
  *   support for custom roles



I looked at existing Cloudstack UI projects but none of them fully satisfied 
all these requirements and started Primate.



== Project Primate ==


For the implementation, I compared a couple of opensource JS and UI frameworks 
and decided to use VueJS (https://vuejs.org) which is a 
JavaScript framework and AntD (https://ant.design) which 
is a UI design language with a well-defined spec, styling guide, and an 
implementation-specific to VueJS. VueJS was selected because among a few other 
JS frameworks I surveyed it was the easiest (for me) to learn and get started. 
I also surveyed a few UI frameworks and selected AntD because it came with a 
well-defined spec, styling guide and VueJS specific implementation which gives 
several re-usable components out of the box.



During the development of Primate, I used my previous experience from 
CloudMonkey and another PoC angular-based UI ProjectX, and it currently 
supports:

  *   role-based UI based on API autodiscovery
  *   auto-generated action/API forms with parameter completion
  *   declarative component-driven views
  *   modern programming methodologies (hot reloading, npm based 
build/run/compile etc.)
  *   decoupled from core Cloudstack code
  *   dynamic translation (most/many of old translation files ported)
  *   includes dashboards, async job/API polling, all list views/tables per the 
old UI
  *   browser history and url/route driven navigation
  *   support for mobiles/tables/desktop screens
  *   configuration driven UI customisation (of navigation, icons, APIs etc)



To get to this point, I’ve had some valuable help from Anurag and Sven et al at 
EWerk.
The development strategy to support all APIs out of the box in a data-driven 
way gives a functioning UI and scope to customise views/components over time. 
Support to declaratively add actions on all views and some action/customisation 
(ex. vm/zone deployment wizard) is in progress. The work was recently discussed 
and demo-ed at CCCNA19, the slides of my talk are here: 
https://rohityadav.cloud/files/talks/cccna19-primate.pdf



== Discussion ==



With this discussion thread, I want to propose the idea hatched in the recent 
hackathon for Primate to become the next UI for CloudStack. I’d like to seek 
everybody's thoughts, feedback, comments, and reviews on that idea.

Obviously, part of any new UI project would mean that the existing UI 
development would eventually get abandoned. In the hackathon we discussed a 
potential plan to formally deprecate the old UI. I therefore think that this is 
something that needs discussion here and a vote if its going to happen.



In summary, that plan is as follows (with proposed timeframes in [brackets]) :

  *   allow the community to download & experience the UI
  *   discuss and gather consensus around Primate [now]
  *   take a vote on whether to take this plan forward [next few weeks]
  *   create a new repository under Cloudstack and accept Primate codebase, 
work on initial documentation with getting started, styling guide etc (i.e. 
make this part of the cloudstack project) [after the vote, if agreed]
  *   collaborate to get primate to be functionally on-par with current 
CloudStack UI, gather feedback, issues, iterate development/testing etc. [2-3 
months before winter LTS release]
  *   release Primate with winter LTS 2019 release as a technical preview and 
also give notice of deprecation plan 

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

[Sven Vogel]

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
s.vo...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 9065

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

EWERK-Blog | LinkedIn | Xing | Twitter | Facebook

Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist 
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der 
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die 
E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential and 
may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.
>>> Am 20.09.2019 um 09:46 schrieb Wei ZHOU :
>> 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 08:26, Riepl, Gregor (SWISS TXT) <
>> gregor.ri...@swisstxt.ch> wrote:
>>
>> 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?
>> 
>> From: Wei ZHOU 
>> Sent: 17 September 2019 19:21
>> To: dev@cloudstack.apache.org 
>> Subject: Re: VR/LB inject others options in haproxy.cfg
>>
>> fyi
>>
>> That is what we have implemented.
>>
>>
>> https://kb.leaseweb.com/customer-portal/cloudstack/network-cloudstack#Network:CloudStack-ConfiguringaloadbalancerforanIPAddressofanIsolatedNetwork
>>
>> We will create pull request later this year.
>>
>> -Wei
>>
>> On Tuesday, 17 September 2019, Rauklei P. S. Guimarães 
>> wrote:
>>
>>> Maibe in Panel/Global Config?
>>> On Tue, Sep 17, 2019 at 11:17 AM Riepl, Gregor (SWISS TXT) <
>>> gregor.ri...@swisstxt.ch> wrote:
> haproxy.cfg is generated by this file
 https://github.com/apache/cloudstack/blob/master/core/
>>> src/main/java/com/cloud/network/HAProxyConfigurator.java
 Allowing changes to the HAProxy config via the CloudStack API could be
 a very useful addition, as the defaults are sometimes a bit limiting.
 For example, the timeout values don't make much sense for certain use
 cases.
 Any thoughts?
>>> --
>>> '''
>>>  Rauklei P.S. Guimarães
>>>  
>>>   '''

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

[GitBox]

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 for Kubernetes.
   
   A PR on the k8s documentation is prepared:
   See https://github.com/kubernetes/website/issues/14817 and 
https://github.com/kubernetes/website/pull/15509


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[GitBox]

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 state how to run kube-apiserver and 
cloudstack-simulator locally to simulate a full dry-run dev environment.
   
   Prefer containers so automated test workloads can be implemented later.


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[GitBox]

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 
`spec.loadBalancerSourceRanges`:
   
https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
   
   Implement firewall configuration via this property on the CloudStack CCM.


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[GitBox]

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 annotation).
   `service.beta.kubernetes.io/cloudstack-load-balancer-proxy-protocol: enabled`
   
   Trying this ensuring the loadbalancer failed with: 
   
   `"Error creating load balancer (will retry): failed to ensure load balancer 
for service kube-system/traefik-ingress-service: error
   creating load balancer rule a9a6465af03a211e9886a02001c1a00c-tcp-proxy-80: 
CloudStack API error 537 (CSExceptionErrorCode: ): The range specified, 
80-80, conflicts with rule 37282 which has 80-80*`
   
   Likely the API Call _"create"_ is called and not _"edit"_.


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[Wei ZHOU]

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 08:26, Riepl, Gregor (SWISS TXT) <
gregor.ri...@swisstxt.ch> wrote:

> 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?
> 
> From: Wei ZHOU 
> Sent: 17 September 2019 19:21
> To: dev@cloudstack.apache.org 
> Subject: Re: VR/LB inject others options in haproxy.cfg
>
> fyi
>
> That is what we have implemented.
>
>
> https://kb.leaseweb.com/customer-portal/cloudstack/network-cloudstack#Network:CloudStack-ConfiguringaloadbalancerforanIPAddressofanIsolatedNetwork
>
> We will create pull request later this year.
>
> -Wei
>
> On Tuesday, 17 September 2019, Rauklei P. S. Guimarães 
> wrote:
>
> > Maibe in Panel/Global Config?
> >
> > On Tue, Sep 17, 2019 at 11:17 AM Riepl, Gregor (SWISS TXT) <
> > gregor.ri...@swisstxt.ch> wrote:
> >
> > >
> > > > haproxy.cfg is generated by this file
> > > >
> > > https://github.com/apache/cloudstack/blob/master/core/
> > src/main/java/com/cloud/network/HAProxyConfigurator.java
> > >
> > > Allowing changes to the HAProxy config via the CloudStack API could be
> > > a very useful addition, as the defaults are sometimes a bit limiting.
> > >
> > > For example, the timeout values don't make much sense for certain use
> > > cases.
> > >
> > > Any thoughts?
> > >
> >
> >
> > --
> > '''
> >   Rauklei P.S. Guimarães
> >   
> >'''
> >
>

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

[Riepl, Gregor (SWISS TXT)]

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?

From: Wei ZHOU 
Sent: 17 September 2019 19:21
To: dev@cloudstack.apache.org 
Subject: Re: VR/LB inject others options in haproxy.cfg

fyi

That is what we have implemented.

https://kb.leaseweb.com/customer-portal/cloudstack/network-cloudstack#Network:CloudStack-ConfiguringaloadbalancerforanIPAddressofanIsolatedNetwork

We will create pull request later this year.

-Wei

On Tuesday, 17 September 2019, Rauklei P. S. Guimarães 
wrote:

> Maibe in Panel/Global Config?
>
> On Tue, Sep 17, 2019 at 11:17 AM Riepl, Gregor (SWISS TXT) <
> gregor.ri...@swisstxt.ch> wrote:
>
> >
> > > haproxy.cfg is generated by this file
> > >
> > https://github.com/apache/cloudstack/blob/master/core/
> src/main/java/com/cloud/network/HAProxyConfigurator.java
> >
> > Allowing changes to the HAProxy config via the CloudStack API could be
> > a very useful addition, as the defaults are sometimes a bit limiting.
> >
> > For example, the timeout values don't make much sense for certain use
> > cases.
> >
> > Any thoughts?
> >
>
>
> --
> '''
>   Rauklei P.S. Guimarães
>   
>'''
>