tt
> To:"OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 12/11/2013 04:41 PM
> Subject:Re: [openstack-dev] [nova] Configure overcommit policy
> --
>
>
>
> On 11 November 2013 12:04, Alex
workload, this is definitely not the case for Hadoop clusters, which
usually consume 100% of system resources.
Is there any way to tell Nova to schedule specific instances (the ones
which consume 100% of system resources) without overcommitting resources on
compute node?
Alexander Kuznetsov
On Fri, Nov 1, 2013 at 12:39 AM, Clint Byrum wrote:
> Excerpts from Alexander Kuznetsov's message of 2013-10-31 10:51:54 -0700:
> > Hi Heat, Savanna and Trove teams,
> >
> > All this projects have common part related to software configuration
> > management. For creation, an environment user s
Jay. Do you have a plan to add a Savanna (type: Heat::Savanna) and Trove
(type: Heat::Trove) providers to the HOT DSL?
On Thu, Oct 31, 2013 at 10:33 PM, Jay Pipes wrote:
> On 10/31/2013 01:51 PM, Alexander Kuznetsov wrote:
>
>> Hi Heat, Savanna and Trove teams,
>>
>>
teams can you comment these ideas, what approach
are the best?
Alexander Kuznetsov.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>> Program: OpenStack Data Processing
> > >>>> Mission: To provide the OpenStack community with an
> > >>>> open, cutting edge, performant and scalable data
> > >>>> processing
, not relating to datastore technologies.
On Fri, Sep 13, 2013 at 8:17 PM, Michael Basnight wrote:
>
> On Sep 13, 2013, at 9:05 AM, Alexander Kuznetsov wrote:
>
> >
> >
> >
> > On Fri, Sep 13, 2013 at 7:26 PM, Michael Basnight
> wrote:
> > On Sep
On Fri, Sep 13, 2013 at 7:26 PM, Michael Basnight wrote:
> On Sep 13, 2013, at 6:56 AM, Alexander Kuznetsov wrote:
> > On Thu, Sep 12, 2013 at 7:30 PM, Michael Basnight
> wrote:
> > On Sep 12, 2013, at 2:39 AM, Thierry Carrez wrote:
> >
> > > Sergey Lukjanov wr
On Thu, Sep 12, 2013 at 7:30 PM, Michael Basnight wrote:
> On Sep 12, 2013, at 2:39 AM, Thierry Carrez wrote:
>
> > Sergey Lukjanov wrote:
> >
> >> [...]
> >> As you can see, resources provisioning is just one of the features and
> the implementation details are not critical for overall architectu
Thanks for your comments let me explain a bit more about Hadoop topology.
In Hadoop 1.2 version, 4 level topologies were introduced: all network,
rack, node group (represent Hadoop nodes on the same compute host in the
simplest case) and node. Usually Hadoop has replication factor 3. In this
case
better performance and robustness.
Alexander Kuznetsov.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
My suggestion OpenStack Data Processing.
On Tue, Sep 10, 2013 at 4:15 PM, Sergey Lukjanov wrote:
> Hi folks,
>
> due to the Incubator Application we should prepare Program name and
> Mission statement for Savanna, so, I want to start mailing thread about it.
>
> Please, provide any ideas here.
>
I updated the REST API draft -
https://etherpad.openstack.org/savanna_API_draft_EDP_extensions. New
methods related to job source and data discovery components were added;
also the job object was updated.
On Fri, Jul 19, 2013 at 12:26 AM, Trevor McKay wrote:
> fyi, updates to the diagram based
Chad,
I suggest following improvement in Job Parameter Tab. You can find new
variant at the same page under your variant.
Alexander Kuznetsov.
On Tue, Jul 16, 2013 at 1:59 PM, Ruslan Kamaldinov wrote:
> Chad,
>
> I'd like to see more details about job progress on the "
On the tab with parameters, we see case for Hadoop streaming API. Could you
please add more examples for parameters tab including cases for Hadoop jar,
Pig and Hive scripts?
Thanks,
Alexander Kuznetsov.
On Fri, Jul 12, 2013 at 7:14 PM, Chad Roberts wrote:
> I have added some initial
://blueprints.launchpad.net/savanna/+spec/methods-for-plugin-api-to-support-edp
Each blueprint contains short component descriptions, objects model and
methods, which will be implemented in this component.
Your comments and suggestions are welcome.
Thanks,
Alexander Kuznetsov
better way to scheduler this
job (on existing clusters or create a new one)
- User makes a decision based on the hint from dispatcher
- Dispatcher (if needed) creates or resizes existing cluster and schedules
job to it
- Dispatcher periodically pull status of job and shows it on UI
Thanks,
Ale
17 matches
Mail list logo
