Thanks, that helps a lot. At what point in the process is it decided (and
by what) which host will run the VM instance? Is that host picked from
the same pool as is used for non-reserved instances? How does the outline
go if there is not enough capacity for the reserved instance?
Thanks,
Mik
Mike, I'll try to describe the reservation process for the virtual
reservations. I'll use Nova project as an example.
As I said, this Nova workflow is only the example that may and certainly
will be modified for other 'virtual' projects.
1) User goes to Nova via CLI/Dashboard and commits all usua
On 10/9/13 6:53 AM, Mike Spreitzer wrote:
Yes, that helps. Please, guys, do not interpret my questions as
hostility, I really am just trying to understand. I think there is
some overlap between your concerns and mine, and I hope we can work
together.
No probs at all. Don't see a sign of hosti
Sylvain: please do not interpret my questions as hostility. I am only
trying to understand your proposal, but I am still confused. Can you
please walk through a scenario involving Climate reservations on virtual
resources? I mean from start to finish, outlining which party makes which
decisi
Yes, that helps. Please, guys, do not interpret my questions as
hostility, I really am just trying to understand. I think there is some
overlap between your concerns and mine, and I hope we can work together.
Sticking to the physical reservations for the moment, let me ask for a
little more e
which party makes which decision, based on what.
Thanks,
Mike
From: Sylvain Bauza
To: OpenStack Development Mailing List
,
Cc: Mike Spreitzer/Watson/IBM@IBMUS
Date: 10/07/2013 05:07 AM
Subject:Re: [openstack-dev] [Climate] Questions and comments
Hi Mike,
Dina and you
Hi Mike,
There are actually more facets to this. Sorry if it's a little confusing
:-( Climate's original blueprint
https://wiki.openstack.org/wiki/Blueprint-nova-planned-resource-reservation-api
was about physical host reservation only. The typical use case being: "I
want to reserve x number
Hi Mike,
Dina and you outlined some differences in terms of seeing what is
dependent on what.
As Dina explained, Climate plans to be integrated into Nova and Heat
logics, where Heat and Nova would request Climate API by asking for a
lease and would tag on their own the resources as 'RESERVED'.
Thanks, Dina. Yes, we do not understand each other; can I ask some more
questions?
You outlined a two-step reservation process ("We assume the following
reservation process for the OpenStack services..."), and right after that
talked about changing your mind to use Heat instead of individual
Hello, Mike!
As for Nova connected thoughts, it was just a reference to the Roadmap,
that includes implementing the reservations opportunity first of all for
the solid virtual resources (VMs, volumes, …) and next for the complex ones
(Heat stacks, Savanna clusters, …). To implement complex reserva
I looked at the blueprint (
https://blueprints.launchpad.net/heat/+spec/stacks-reservation) and
associated wiki page (https://wiki.openstack.org/wiki/Heat/Reservation),
and I have a few comments/questions.
The wiki page has some remarks that are Nova-centric, and some other
remarks that emphasi
11 matches
Mail list logo
