Open Stack

Hello David,

I have been using and installing Horizon dashboard for last two years. What
is see is Horizon has developed as private cloud control panel. Private
cloud is people from industry who already have some degree of system
administration. And you can always educate professional who are going to
use a private cloud created with OpenStack.

On the other hand, if any provider, data center or any small IT business
want to sell cloud infrastructure created with OpenStack needs more than
what Horizon currently offer. Because they want to package and sell
OpenStack and they need a dashboard that can sell cloud services while
managing it from UI.

If you ever heard of WHMCS, I can tell you that dash-stack will be WHMCS of
OpenStack.



On Mon, Nov 14, 2016 at 6:08 AM, David Moreau Simard <dms at redhat.com> wrote:

> I'm all for diversity but I'm still curious.
>
> In what way does Horizon not already provide what you are looking for and
> why could it not be improved to get what you feel is lacking ?
>
> I think this answer could translate into valuable feedback for the Horizon
> team.
>
> David Moreau Simard
> Senior Software Engineer | Openstack RDO
>
> dmsimard = [irc, github, twitter]
>
> On Nov 12, 2016 7:47 AM, "Ferhat Ozkasgarli" <ozkasgarli at gmail.com> wrote:
>
>> Hello to All Infra team,
>>
>> We have been developing a new dashboard for OpenStack. But recently we
>> have decided to use StackForge to benefit all the advantages of OpenStack
>> development environment and system.
>>
>> I would be glad if any of you guys can review following change so we can
>> continue developing:
>>
>> https://review.openstack.org/#/c/394010/
>>
>> Sincerely,
>> Ferhat Ozkasgarli
>>
>> _______________________________________________
>> OpenStack-Infra mailing list
>> OpenStack-Infra at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20161114/4f3fd8d1/attachment.html>