nova-orchestration team mailing list archive

[Joseph Suh <jsuh@xxxxxxx>]

Don,

Thanks for your reply. We are working on a heterogeneous hpc cloud computing system, and sometimes, we wanted to specify a library version that an image includes. Although it would be easier to be able to handle the version string directly, I agree that there are alternatives including the one you suggested. Unless many wish the feature, I guess it can be handled using work-around ways. Also, I agree the OR operator makes design and implementation much more complex. So, if the community does not call for the feature strongly, I agree that it is better to keep it simple.

Thanks for the good work!

Joseph



----- Original Message -----
From: "Donald D Dugger" <donald.d.dugger@xxxxxxxxx>
To: "Joseph Suh" <jsuh@xxxxxxx>
Cc: "Sandy Walsh" <sandy.walsh@xxxxxxxxxxxxx>, nova-orchestration@xxxxxxxxxxxxxxxxxxx
Sent: Sunday, January 22, 2012 5:30:22 PM
Subject: RE: [Nova-orchestration] Dec 1st 2011 IRC Meeting

Joseph-

Tnx for looking at this, all comments are welcome (sorry for delay, vacation & power failure that took out my workstation slowed me down).

1)  Not sure exactly what your concern about the version comparison is.  There's no concept of a `version' per se in the policies and constraints, there is the concept if a string comparison and you could put a version into the metric database to be used as a version but, as you point out, any comparisons would be against a string.  You could break a version into multiple components, represent each component as an integer, and then do comparisons against the components which would accomplish most of what you want.

2)  I thought about putting in an OR operator but I'm resisting it so far.  Although you could come up with some uses for it I can't think of any compelling need for an OR operator and it would make things much more complex as we'd have to add precedence and grouping also.  It's doable but, until there's a compelling use case for it, I'd prefer to keep things simple.

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786


-----Original Message-----
From: Joseph Suh [mailto:jsuh@xxxxxxx] 
Sent: Monday, January 16, 2012 6:30 AM
To: Dugger, Donald D
Cc: Sandy Walsh; nova-orchestration@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Nova-orchestration] Dec 1st 2011 IRC Meeting

Don,

The PC scheduler will be very useful. I thought a couple of additional features that would be useful:

1. The version string comparison is tricky. It would be useful to have a way to handle it easily. If we simply use string comparison, like version >= 3.10.4, it would match 3.2.4 as well.

2. Currently, the scheduler chooses a node using "AND" operation with constraints. If we can apply "OR" operation somehow, it would be useful. For example, os == RedHat OR os == Ubuntu. This would be also a workaround for the first issue by using version == 3.10.4 OR version == 3.10.5.

Thanks,

Joseph

----- Original Message -----
From: "Donald D Dugger" <donald.d.dugger@xxxxxxxxx>
To: "Sandy Walsh" <sandy.walsh@xxxxxxxxxxxxx>, nova-orchestration@xxxxxxxxxxxxxxxxxxx
Sent: Sunday, December 4, 2011 1:24:57 AM
Subject: Re: [Nova-orchestration] Dec 1st 2011 IRC Meeting

As promised at the meeting Thurs. I've attached a writeup of the Proof of Concept scheduler I created that offers that same functionality as the Abstract Scheduler but implements things through two new tables in the DataBase.  I implemented this scheduler based upon the Cactus release and it is fully functional but we didn't do any performance analysis on it.

Would be very interested in any questions/comments/epithets anyone has about this idea.

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786


-----Original Message-----
From: nova-orchestration-bounces+donald.d.dugger=intel.com@xxxxxxxxxxxxxxxxxxx [mailto:nova-orchestration-bounces+donald.d.dugger=intel.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Sandy Walsh
Sent: Thursday, December 01, 2011 1:35 PM
To: nova-orchestration@xxxxxxxxxxxxxxxxxxx
Subject: [Nova-orchestration] Dec 1st 2011 IRC Meeting

http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-01-20.01.html

details:
http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-01-20.01.log.html

-- 
Mailing list: https://launchpad.net/~nova-orchestration
Post to     : nova-orchestration@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~nova-orchestration
More help   : https://help.launchpad.net/ListHelp

-- 
Mailing list: https://launchpad.net/~nova-orchestration
Post to     : nova-orchestration@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~nova-orchestration
More help   : https://help.launchpad.net/ListHelp