cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gabriel Beims Bräscher <gabrasc...@gmail.com>
Subject Re: [ANNOUNCE] Open source distributed virtual machine scheduling platform
Date Wed, 27 Apr 2016 15:11:38 GMT
Hi all,
Thanks for your cheers, it means a lot for us.

Anshul, thanks for asking. We are very excited about the project, our plan
is to add new algorithms. Also, We foresee the need to use/add other types
of agents. All of that is going to be done as our research goes forward.

That is great that you have already worked on this. You probably understand
how hard it is to work alone in a project like this. Gladly, we are not
alone on this boat. Today our whole system is based on symbolic artificial
intelligence, our heuristics are based on specialist knowledge. But, as you
pointed out the use of machine learning (connectionist artificial
intelligence) is pretty interesting for some problems. And yes, we intend
to use some neural/Bayesian Network techniques to help us improve our
heuristics. Again, that is something that will be done as our research and
project go forward.

Cheers, Gabriel.

2016-04-27 3:27 GMT-03:00 Anshul Gangwar <anshul.gangwar@accelerite.com>:

> Hi Gabriel,
>
> Project looks promising.
>
> I was curious to know whether you guys are planning to add new algorithms
> or use the existing algorithms.
>
> P.S. I was working on same problem for my master’s thesis some 5 years
> back. My main intention was to utilise the machine learning based
> approaches to solve the problem.
>
>
>
>
> On 27/04/16, 2:29 AM, "Gabriel Beims Bräscher" <gabrascher@gmail.com>
> wrote:
>
> >Hello CloudStack community members (@dev and @users),
> >
> >This email is meant to announce the publication of a project on Github
> that
> >provides a distributed virtual machine scheduling platform that can be
> >easily integrated with Apache CloudStack (ACS). The project is available
> at
> >[1], you can find a detailed explanation of the idea of the project, its
> >aspirations, basic concepts, installation and uninstallation processes and
> >other information at [2]. Also, if you want to know more about the
> >Autonomiccs and its creators, you can access the link [3].
> >
> >The code that was opened at Github is part of a bigger system that has the
> >goal of managing a cloud computing environment autonomously. All of that
> is
> >being developed and used in my Ph. D. thesis and the masters’ thesis of
> >some colleagues. The formalization of that component will be published at
> >the 12th IEEE World Congress on Services (SERVICES 2016) at San Francisco
> >USA.
> >
> >You can see the stats of our code at [4] and [5]. Right now we only have
> >~40% of code test coverage. However, we intend to increase that value to
> >~60% until next week and ~90% until the end of June.
> >
> >To give you a picture of what we are preparing for the future, we can
> >highlight the following goals for this year (You can find others short
> term
> >goals at [6]):
> >
> >   -
> >
> >   Integrate our platform [1] with a multi-agent system (MAS) platform, in
> >   order to facilitate the development of agents. Currently, we are using
> >   Spring-integration to “emulate” and an agent life cycle; that can
> become a
> >   problem when needing to add more agents and they start to communicate
> with
> >   each other. Therefore, we will integrate the platform in [1] with JADE
> [7];
> >   -
> >
> >   Today the metrics about the use of resource are not properly gathered
> by
> >   ACS; in order to develop more accurate predictions we need to store
> >   resource usage metrics. Also, those metrics have to be gathered in a
> >   distributed way without causing service degradation. For that and a few
> >   other reasons (you can send us an email so we can provide you more
> >   details), we are developing an autonomic monitoring platform that will
> >   integrate with the system available in [1];
> >   -
> >
> >   We also foresee the need to develop a better way to visualize the cloud
> >   environment, a way to detect hot spots (pods and hosts) with higher
> >   resource usage trends (VMs trends). We see the need to change the
> rustic
> >   view of the environment with tables for a better suitable one for
> humans
> >   (this is a surprise that we intend to present at the CCCBR).
> >
> >We hope you like the software and that it meets your expectations. If it
> >does not suffice all of your needs, let’s work together to improve it. If
> >you have any doubts or suggestions please send us an email; we will reply
> >it as fast as we can. Also, critics that can help us improve that platform
> >are very welcome.
> >
> >[1] https://github.com/Autonomiccs/autonomiccs-platform
> >
> >[2] https://github.com/Autonomiccs/autonomiccs-platform/wiki
> >
> >[3] http://autonomiccs.com.br/
> >
> >[4] http://jenkins.autonomiccs.com.br/
> >
> >[5] http://sonar.autonomiccs.com.br/
> >
> >[6] https://github.com/Autonomiccs/autonomiccs-platform#project-evolution
> >
> >[7] http://jade.tilab.com/
> >
> >
> >Cheers, Gabriel.
>
>
>
> DISCLAIMER
> ==========
> This e-mail may contain privileged and confidential information which is
> the property of Accelerite, a Persistent Systems business. It is intended
> only for the use of the individual or entity to which it is addressed. If
> you are not the intended recipient, you are not authorized to read, retain,
> copy, print, distribute or use this message. If you have received this
> communication in error, please notify the sender and delete all copies of
> this message. Accelerite, a Persistent Systems business does not accept any
> liability for virus infected mails.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message