Comments (8)
Noted.
The disk specification for the 'root' disk resource you mention is from a later Mesos version (post 0.24.x). Are you able to create a pull request for this change? Or, given an example that we could use to make the change? Or, can you create a unit test that would fail for the current version? Thank you.
Sorry about the delay in getting back to you, I was mostly out on summer travel and conferences.
from fenzo.
@spodila have you seen much interest in adding disk support? Or seen some applications of Fenzo that succeed in that?
from fenzo.
@EronWright I've heard of one other user mentioning this would be useful for them. If you are thinking of creating a PR for this, that would be great.
from fenzo.
@spodila I am interested in the functionality but don't have time to work on it at this time.
from fenzo.
In addition for agents that will always have a small / partition (4GB), it means that only attached volumes will serve to host the 'sandbox'
so the issue here is that you don't actually know where the disk comes from.
ideally the
public class TaskAssignmentResult
would give you a map for this successful result - in fact to all the original mesos.Proto.Offer.Resources so you can see and track where they come from.
i.e: this class
public class VMAssignmentResult {
private final String hostname;
private final List<VirtualMachineLease> leasesUsed;
private final Set<TaskAssignmentResult> tasksAssigned;
should have a way to go from the taskAssigned to one of the leasesUsed (mesos offers) per sub resource, in particular for "disk" resources.
from fenzo.
here is an example:
{
value: "2d024b1c-e037-44fd-a8f9-fa6ece3b181b-O1243"
}
framework_id {
value: "------------xxxx-------------"
}
slave_id {
value: "2e552da4-1c21-414c-ab2c-a29afc2b4027-S1"
}
hostname: "x.x.x.x"
resources {
name: "cpus"
type: SCALAR
scalar {
value: 6.0
}
role: "*"
allocation_info {
role: "*"
}
}
resources {
name: "mem"
type: SCALAR
scalar {
value: 12949.0
}
role: "*"
allocation_info {
role: "*"
}
}
resources {
name: "disk"
type: SCALAR
scalar {
value: 1728.0
}
role: "*"
allocation_info {
role: "*"
}
}
resources {
name: "disk"
type: SCALAR
scalar {
value: 206312.0
}
role: "*"
disk {
source {
type: MOUNT
mount {
root: "/partition1"
}
}
}
allocation_info {
role: "*"
}
}
resources {
name: "disk"
type: SCALAR
scalar {
value: 210338.0
}
role: "*"
disk {
source {
type: MOUNT
mount {
root: "/partition2"
}
}
}
allocation_info {
role: "*"
}
}
resources {
name: "ports"
type: RANGES
ranges {
range {
begin: 31003
end: 32000
}
}
role: "*"
allocation_info {
role: "*"
}
}
executor_ids {
value: "----------------------------------xxxx----------------"
}
url {
scheme: "http"
address {
hostname: "x.x.x.x"
ip: "x.x.x.x"
port: 5051
}
path: "/slave(1)"
}
allocation_info {
role: "*"
}
Thought the LeasesUsed.getDiskMB() => 210338.0
from fenzo.
Maybe there is a
struct NameDisk {
double size;
union type {
mount ....
path
};
}
So that you can get a getNamedDisk() and fill in the disk on the mesos protobuf
from fenzo.
A possible workaround is to write an alternate implementation of VMLeaseObject
as mentioned in #166.
from fenzo.
Related Issues (20)
- contributor agreement. HOT 8
- NamedResourceSetRequest HOT 2
- Resource ranges and "greedy" scheduling HOT 4
- Support v1 Protos (or provide utility to convert) HOT 5
- Support dynamic fitness threshold HOT 3
- Allow for custom shortfall evaluators HOT 4
- Execution failed for task ':fenzo-core:compileJava'.> 无效的源发行版: 1.8 HOT 2
- Update Mesos dependency
- BinPacking with weights HOT 2
- Incorrect handling of reserved resources HOT 2
- Unsafe concurrent access to unknown lease collection in AssignableVMs class
- Pluggable ENI fitness evaluator HOT 1
- After reading Fenzo, I don't understand how to get Framework information on Mesos?
- After reading Fenzo, I don't understand how to get Framework information on Mesos?
- DisableVM does not remember hosts HOT 2
- .travis.yml: The 'sudo' tag is now deprecated in Travis CI
- Dynamic ResAllocs
- CVE-2018-7489 on jackson-databind 2.4.5 HOT 1
- Unused variable
- Unreleased Resource: Streams HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fenzo.