Open Stack

On 11/22/13 12:16 PM, "Soren Hansen" <soren at linux2go.dk> wrote:

>I'd very much like to take part in the discussions. Depending on the
>outcome of said discussion, I may or may not want to participate in
>the implementation :)
>
>Soren Hansen             |
>https://urldefense.proofpoint.com/v1/url?u=http://linux2go.dk/&k=oIvRg1%2B
>dGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3
>D%0A&m=pr4FBldPmZvECJD7jpPfjv0XLo1P3PPXDRd3dhn56k0%3D%0A&s=2dba15816537ae5
>61ef54f0548fd0da0c5ce37fce819acc4c056134590c40cef
>Ubuntu Developer         |
>https://urldefense.proofpoint.com/v1/url?u=http://www.ubuntu.com/&k=oIvRg1
>%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq
>8%3D%0A&m=pr4FBldPmZvECJD7jpPfjv0XLo1P3PPXDRd3dhn56k0%3D%0A&s=462ef9df3aed
>afde406b7d73ed571630344691b79c9809f86084557f7ce303c3
>OpenStack Developer      |
>https://urldefense.proofpoint.com/v1/url?u=http://www.openstack.org/&k=oIv
>Rg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFx
>PEq8%3D%0A&m=pr4FBldPmZvECJD7jpPfjv0XLo1P3PPXDRd3dhn56k0%3D%0A&s=1c8236fed
>c4e15ca9c3d4ff1b970f41648ce6c639dc3d99becabcc6a7158a138
>
>
>2013/11/21 Robert Collins <robertc at robertcollins.net>:
>> 
>>https://urldefense.proofpoint.com/v1/url?u=https://etherpad.openstack.org
>>/p/icehouse-external-scheduler&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0p
>>xTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=pr4FBldPmZvECJD7jpPfjv0
>>XLo1P3PPXDRd3dhn56k0%3D%0A&s=c0f64e4db8aa810d1a8412fc40fafa260d8ad43d8428
>>b2aaa254e98ed6273947
>>
>> I'm looking for 4-5 folk who have:
>>  - modest Nova skills
>>  - time to follow a fairly mechanical (but careful and detailed work
>> needed) plan to break the status quo around scheduler extraction

I would be happy to take part. But prior I think that we need to iron out
a number of issues:
1. Will this be a new service that has an API, for example will Nova be
able to register a host and provide the host statisticsŠ.
2. How will the various components interact with the scheduler - same as
today - that is RPC? Or a REST API? The latter is a real concern due to
problems we have seen with the interactions of nova and other services
3. How will current developments fit into this model?

All in all I think that it is a very good and healthy idea. I have a
number of reservations - these are mainly regarding the implementation and
the service definition.

Basically I like the approach of just getting heads down and doing it, but
prior to that I think that we just need to understand the scope and mainly
define the interfaces and how they can used/abused and consumed. It may be
a very good topic to discuss at the up and coming scheduler meeting - this
may be in the middle of the night for Robert. If so then maybe we can
schedule another time.

Please note that this is scheduling and not orchestration. That is also
something that we need to resolve.

Thanks
Gary

>>
>> And of course, discussion galore about the idea :)
>>
>> Cheers,
>> Rob
>>
>> --
>> Robert Collins <rbtcollins at hp.com>
>> Distinguished Technologist
>> HP Converged Cloud
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> 
>>https://urldefense.proofpoint.com/v1/url?u=http://lists.openstack.org/cgi
>>-bin/mailman/listinfo/openstack-dev&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r
>>=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=pr4FBldPmZvECJD7jp
>>Pfjv0XLo1P3PPXDRd3dhn56k0%3D%0A&s=8bfc07a9380a0bcae8430b746a543267b2823b1
>>205ebb0f8000341b0ea5b80f6
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>https://urldefense.proofpoint.com/v1/url?u=http://lists.openstack.org/cgi-
>bin/mailman/listinfo/openstack-dev&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=e
>H0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=pr4FBldPmZvECJD7jpPfj
>v0XLo1P3PPXDRd3dhn56k0%3D%0A&s=8bfc07a9380a0bcae8430b746a543267b2823b1205e
>bb0f8000341b0ea5b80f6