Panic in xen container about jobs

[albrow]

@fzerorubigd thanks for bringing this to my attention. Did you mean a xen container? As in http://www.xenproject.org/.

[fzerorubigd]

@albrow Sorry :)))) yes. it is xen.

[albrow]

@fzerorubigd I'm surprised that xen containers don't expose a mac address, and I'm sorry that I made an incorrect assumption here. What if I add a field to PoolConfig which lets you set your own id for the pool? If not provided, jobs will still default to the mac address-based id.

Something like:

type PoolConfig struct {
    // Id is a unique identifier for the pool. If not provided, jobs will attempt
    // to generate an id based on the machine's mac address
    Id string
    // (additional fields omitted here)
}

I also will try and fix the code so it doesn't panic when the mac address isn't found. Instead it will return an error message asking you to provide your own pool id.

Could you share the full stack trace so I can track down what went wrong?

[fzerorubigd]

Thank you. yes, its enough :)

On Sun, Jun 21, 2015 at 4:32 AM, Alex Browne [email protected]
wrote:

@fzerorubigd https://github.com/fzerorubigd I'm surprised that xen
containers don't expose a mac address, and I'm sorry that I made an
incorrect assumption here. What if I add a field to PoolConfig which lets
you set your own id for the pool? If not provided, jobs will still default
to the mac address-based id.

Something like:

type PoolConfig struct {
// Id is a unique identifier for the pool. If not provided, jobs will attempt
// to generate an id based on the machine's mac address
Id string
// (additional fields omitted here)
}

I also will try and fix the code so it doesn't panic when the mac address
isn't found. Instead it will return an error message asking you to provide
your own pool id.

Could you share the full stack trace so I can track down what went wrong?

—
Reply to this email directly or view it on GitHub
#24 (comment).

---

http://fzero.rubi.gd