Hah, OK good, thanks for clearing that up (I was *fairly* sure I was toe-ing
the line)...sorry for the extra chatter.
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-manag
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
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 nev
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 t
+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
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 Schuber
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
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
that was supposed to be "live normally with that limitation and migrate
things to another pooL" ...
On Fri, 20 Sep 2019 at 10:01, Andrija Panic wrote:
> The way you can live normally and migrate things to another poo -
> assuming you are migrating from pool1 (which you do NOT want to use any
>
The way you can live normally and migrate things to another poo - assuming
you are migrating from pool1 (which you do NOT want to use any more to
provision new volumes on it) to pool2 - is to have identical tags on both
pools, but then disable the pool1 (cloudmonkey update storagepool
enabled=false
Hi Piotr,
which release are you running?
Until recently, even if tags did NOT match between 2 different pools (UI
will say "Not suitable") - migration was still possible - and will execute
properly - but later you would be unable to change the Offering of the disk
to match any offering that's poin
11 matches
Mail list logo
