Hi
I think we should do a review of the design doc review and have rough
consensus (that it should work) followed by running code. ….
As of now all the design stuff is supposedly in (as per the scheduler
meeting today)
https://etherpad.openstack.org/p/icehouse-external-scheduler
Hope the core de
I agree with RussellB on this … if the forklift's goal is to just separate
the scheduler, there should be no new features etc till the forklift is
done and it should work as is with very minor config changes.
A scheduler has several features like place resources correctly, for
example. Ideally, th
https://etherpad.openstack.org/p/SchedulerUseCases
[08:43:35] #action all update the use case etherpad
athttps://etherpad.openstack.org/p/SchedulerUseCases
Please update your use cases here ..
2014-07-14 20:57 GMT-07:00 Dugger, Donald D :
> 1) Forklift (Tasks & status)
> 2) Opens
>
> --
> D
https://etherpad.openstack.org/p/SchedulerUseCases
[08:43:35] #action all update the use case etherpad
athttps://etherpad.openstack.org/p/SchedulerUseCases
Please update your use cases here ..
thx
debo
On Tue, Jul 15, 2014 at 2:50 AM, Sylvain Bauza wrote:
> Le 14/07/2014 20:10, Jay Pipes
https://etherpad.openstack.org/p/SchedulerUseCases
[08:43:35] #action all update the use case etherpad
athttps://etherpad.openstack.org/p/SchedulerUseCases
Please update your use cases here ..
debo
On Mon, Jul 14, 2014 at 7:25 PM, Yathiraj Udupi (yudupi)
wrote:
> Hi all,
>
> Adding to the
Hi Folks
Sorry for missing today's meeting. Was reading the logs
http://eavesdrop.openstack.org/meetings/scheduling/2013/scheduling.2013-09-24-15.03.log.html
Regarding the API: the instance groups API extension could be used as
a starting point although it could be refined. Right now its quite
Joining the party late :)
I think there have been a lot of interesting ideas around wholistic
scheduling over the last few summits. However seems there is no clear
agreement on 1) where it should be specified and implemented 2) what
the specifications look like - VRT, policies, templates etc etc e
Hi Mike
We understand your point, and, academically, we agree to a large
extent. We aware of the optimization results for holistic placement
etc (and how any realistic formulation is hard). When we look at the
scheduler today, it does one thing at a time because it was meant to
be pragmatic when i
Hi!
We @Cisco just made the following repos public
https://github.com/CiscoSystems/donabe
https://github.com/CiscoSystems/curvature
Donabe was pitched as a recursive container before Heat days.
Curvature is an alternative interactive GUI front end to openstack
that can handle virtual resources, t
And just for some history on Donabe: the idea was 1st presented at the
E summit along with @dendrobates at
http://www.slideshare.net/ddutta1/donabe-models-openstack-essex-summit
debo
On Thu, Oct 3, 2013 at 11:43 AM, Debojyoti Dutta wrote:
> Hi!
>
> We @Cisco just made the following rep
, Christopher Armstrong
wrote:
> On Thu, Oct 3, 2013 at 1:43 PM, Debojyoti Dutta wrote:
>>
>> Hi!
>>
>> We @Cisco just made the following repos public
>> https://github.com/CiscoSystems/donabe
>> https://github.com/CiscoSystems/curvature
>>
>> Dona
Edgar
Thanks for your feedback during its early days ;)
debo
On Thu, Oct 3, 2013 at 12:34 PM, Edgar Magana wrote:
> Debo,
>
> Congratulations on this move! The entire Cisco team is doing an awesome
> work around OpenStack.
>
> Cheers,
>
> Edgar
>
> On 10/3/13 11:4
Mike, I agree we could have a cleaner API but I am not sure how
cleanly it will integrate with current nova which IMO should be test
we should pass (assuming we do cross services later)
On Tue, Oct 8, 2013 at 10:39 PM, Mike Spreitzer wrote:
> Thanks for the clue about where the request/response b
Alex, agree with your comments. I think we need to think of both 1.
and 2. as the eventual outcome and the destination. IF we decide to
improve upon scheduling/polices at the heat level, that should be a
very nice and independent endeavor and we can all learn from it. I
dont think we can design thi
Hi Phil
Good summary ...
I was wondering if we are shooting for too much to discuss by clubbing
i) Group Scheduling / Smart Placement / Heat and Scheduling (1),
(2), (3), & (7)
- How do you schedule something more complex that a single VM ?
I think specifying something more complex tha
Hi
As per my IRC chats with dansmith, russellb, this feature needs the
user auth checks (being taken care of in
https://bugs.launchpad.net/nova/+bug/1221396).
Dan has some more comments
Could we please do a FFE for this one has been waiting for a long
time and we have done all that we
, Sep 6, 2013 at 9:09 AM, Gary Kotton wrote:
>
>
> On 9/6/13 5:07 PM, "Russell Bryant" wrote:
>
>>On 09/06/2013 05:06 AM, Thierry Carrez wrote:
>>> Debojyoti Dutta wrote:
>>>> As per my IRC chats with dansmith, russellb, this feature needs the
>>
Hi!
It is a great pleasure to announce the development of a new project called
Cognitive. Cognitive provides Machine Learning [1] as a Service that
enables operators to offer next generation data science based services on
top of their OpenStack Clouds. This project will begin as a StackForge
proj
00:19, Debojyoti Dutta wrote:
>
>> Hi!
>>
>> It is a great pleasure to announce the development of a new project
>> called Cognitive. Cognitive provides Machine Learning [1] as a Service
>> that enables operators to offer next generation data science based servi
Hi!
Its a pleasure to introduce CephEWS, an awesome dashboard for Ceph with a
twist - it has ceph health checks and warnings built in along with OSD and
CRUSH map viz etc. https://github.com/CiscoSystems/cephEWS
Hope to see a lot of pull requests and feedback!
thx
-Debo~
Hi,
It gives me a great pleasure to introduce Surge - a system to rapidly
deploy and scale a stream processing system on OpenStack. It leverages
Vagrant and Ansible, and supports both OpenStack as well as the local mode
(with VirtualBox).
https://github.com/CiscoSystems/surge
Hope to see a lot o
void duplicating it.
>
> Thanks.
>
> On Thu, May 14, 2015 at 8:47 PM, Debojyoti Dutta wrote:
>
>> Hi Salvatore
>>
>> Thanks a lot for your comments.
>>
>> Timing: Yes it is time to do this! The nature of applications running on
>> clouds is indeed
One more thing and a typo in my mail - we would be happy to point folks
to an very early version (in Django) we prototyped and opened up recently.
thx
debo
On Fri, May 22, 2015 at 8:48 AM, Debojyoti Dutta wrote:
> Hi Sergey
>
> Thanks a lot for your interest. The bare bones API pr
sage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [new][cognitive] Announcing Cognitive - a
> project to deliver Machine Learning as a Service for OpenStack
>
> So, in case if Cognitive will use Sahara to create big data clusters -
>
Hi Tim: moving our thread to the mailer. Excited to collaborate!
From: Debo~ Dutta
Date: Wednesday, February 11, 2015 at 4:48 PM
To: Tim Hinrichs
Cc: "Yathiraj Udupi (yudupi)" , Gokul B Kandiraju <
go...@us.ibm.com>, Prabhakar Kudva , "
ruby.krishnasw...@orange.com" , "
dilik...@in.ibm.com" ,
ation APIs and enable the required migrations.
>
>
>
> Thanks,
> Yathi.
>
>
> On 2/12/15, 10:02 AM, "Tim Hinrichs" wrote:
>
> Hi Debo and Yathiraj,
>
> I took a third look at the solver-scheduler docs and code with your
> comments in mind. A
Hello Everyone
It is time for us to apply for slots for the annual Google Summer of Code
event https://developers.google.com/open-source/soc/?csw=1
Last year, we got a bunch of slots and had awesome projects
https://wiki.openstack.org/wiki/GSoC2014
We are hoping this year we will get even more sl
.
>
>
>
> So this is likely to be a major change to the scheduler?
>
>
>
> Ruby
>
>
>
> *De :* Debojyoti Dutta [mailto:ddu...@gmail.com]
> *Envoyé :* vendredi 13 février 2015 14:06
> *À :* OpenStack Development Mailing List (not for usage questions)
>
28 matches
Mail list logo
