--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
And what builder names do you plan to use?
Remember, the builder configs are the names that shows up at build.golang.org and represent a machine + Go config. (e.g. builder name "linux-386-387" runs with GOARCH=386 + GO386=387 but runs on host type "host-linux-amd64-kubestd").
Do you intend to load balance builder "solaris-amd64" builds across the two sites? If so, they need the same host type.
If not, do we really need two Oracle Solaris 11.3 builders? I don't think so.
On Thursday, July 6, 2017 at 2:00:41 PM UTC-7, Brad Fitzpatrick wrote:And what builder names do you plan to use?
Remember, the builder configs are the names that shows up at build.golang.org and represent a machine + Go config. (e.g. builder name "linux-386-387" runs with GOARCH=386 + GO386=387 but runs on host type "host-linux-amd64-kubestd").
Then, I would assume the two builder config names would be:
solaris-amd64-oraclerel
solaris-sparc64-oraclerel
Do you intend to load balance builder "solaris-amd64" builds across the two sites? If so, they need the same host type.
By load balance, what do you mean? Does that play into numTryTestHelpers?
The test sharding?
If not, do we really need two Oracle Solaris 11.3 builders? I don't think so.
My belief was that the additional builders could be configured as trybots.
If they must all have the same host type, then perhaps these names?
host-solaris-oracle-amd64-oraclerel
host-solaris-oracle-sparc64-oraclerel
On Thu, Jul 6, 2017 at 2:12 PM, <shawn....@oracle.com> wrote:
On Thursday, July 6, 2017 at 2:00:41 PM UTC-7, Brad Fitzpatrick wrote:And what builder names do you plan to use?
Remember, the builder configs are the names that shows up at build.golang.org and represent a machine + Go config. (e.g. builder name "linux-386-387" runs with GOARCH=386 + GO386=387 but runs on host type "host-linux-amd64-kubestd").
Then, I would assume the two builder config names would be:
solaris-amd64-oraclerel
solaris-sparc64-oraclerelThose look fine.Do you intend to load balance builder "solaris-amd64" builds across the two sites? If so, they need the same host type.
By load balance, what do you mean? Does that play into numTryTestHelpers?
The test sharding?I don't think we have the Solaris machine capacity on your side or the human maintenance capacity on our side to add more trybots right now.You'd need more than 2 or 3 machines, and we'd need to react to changes in their availability.Let's start with just regular post-submit builders for now.
If not, do we really need two Oracle Solaris 11.3 builders? I don't think so.
My belief was that the additional builders could be configured as trybots.
If they must all have the same host type, then perhaps these names?
host-solaris-oracle-amd64-oraclerel
host-solaris-oracle-sparc64-oraclerelThose look fine.I'll email you keys.
On Thursday, July 6, 2017 at 2:19:43 PM UTC-7, Brad Fitzpatrick wrote:On Thu, Jul 6, 2017 at 2:12 PM, <shawn....@oracle.com> wrote:
On Thursday, July 6, 2017 at 2:00:41 PM UTC-7, Brad Fitzpatrick wrote:And what builder names do you plan to use?
Remember, the builder configs are the names that shows up at build.golang.org and represent a machine + Go config. (e.g. builder name "linux-386-387" runs with GOARCH=386 + GO386=387 but runs on host type "host-linux-amd64-kubestd").
Then, I would assume the two builder config names would be:
solaris-amd64-oraclerel
solaris-sparc64-oraclerelThose look fine.Do you intend to load balance builder "solaris-amd64" builds across the two sites? If so, they need the same host type.
By load balance, what do you mean? Does that play into numTryTestHelpers?
The test sharding?I don't think we have the Solaris machine capacity on your side or the human maintenance capacity on our side to add more trybots right now.You'd need more than 2 or 3 machines, and we'd need to react to changes in their availability.Let's start with just regular post-submit builders for now.
Well, the eventual goal is to certainly have them available for TryBots, so when possible, please let me know what I need to do to make that happen. The builders are fairly over-provisioned relative to what an actual build needs. As far as I know, at most, maybe a plugin to start Solaris Zones (containers) on demand would be required.
On Thu, Jul 6, 2017 at 2:28 PM, <shawn....@oracle.com> wrote:On Thursday, July 6, 2017 at 2:19:43 PM UTC-7, Brad Fitzpatrick wrote:On Thu, Jul 6, 2017 at 2:12 PM, <shawn....@oracle.com> wrote:
On Thursday, July 6, 2017 at 2:00:41 PM UTC-7, Brad Fitzpatrick wrote:And what builder names do you plan to use?
Remember, the builder configs are the names that shows up at build.golang.org and represent a machine + Go config. (e.g. builder name "linux-386-387" runs with GOARCH=386 + GO386=387 but runs on host type "host-linux-amd64-kubestd").
Then, I would assume the two builder config names would be:
solaris-amd64-oraclerel
solaris-sparc64-oraclerelThose look fine.Do you intend to load balance builder "solaris-amd64" builds across the two sites? If so, they need the same host type.
By load balance, what do you mean? Does that play into numTryTestHelpers?
The test sharding?I don't think we have the Solaris machine capacity on your side or the human maintenance capacity on our side to add more trybots right now.You'd need more than 2 or 3 machines, and we'd need to react to changes in their availability.Let's start with just regular post-submit builders for now.
Well, the eventual goal is to certainly have them available for TryBots, so when possible, please let me know what I need to do to make that happen. The builders are fairly over-provisioned relative to what an actual build needs. As far as I know, at most, maybe a plugin to start Solaris Zones (containers) on demand would be required.Sure, if you want to work on that.
Or you could do it all on your side, too.
You can write a thing on your side that polls http://farmer.golang.org/status/reverse.json and if it sees the "Waiters" count for your host type go up, you create more containers in Zones. If you see them idle, kill them off.
On Thursday, July 6, 2017 at 2:32:26 PM UTC-7, Brad Fitzpatrick wrote:On Thu, Jul 6, 2017 at 2:28 PM, <shawn....@oracle.com> wrote:On Thursday, July 6, 2017 at 2:19:43 PM UTC-7, Brad Fitzpatrick wrote:On Thu, Jul 6, 2017 at 2:12 PM, <shawn....@oracle.com> wrote:
On Thursday, July 6, 2017 at 2:00:41 PM UTC-7, Brad Fitzpatrick wrote:And what builder names do you plan to use?
Remember, the builder configs are the names that shows up at build.golang.org and represent a machine + Go config. (e.g. builder name "linux-386-387" runs with GOARCH=386 + GO386=387 but runs on host type "host-linux-amd64-kubestd").
Then, I would assume the two builder config names would be:
solaris-amd64-oraclerel
solaris-sparc64-oraclerelThose look fine.Do you intend to load balance builder "solaris-amd64" builds across the two sites? If so, they need the same host type.
By load balance, what do you mean? Does that play into numTryTestHelpers?
The test sharding?I don't think we have the Solaris machine capacity on your side or the human maintenance capacity on our side to add more trybots right now.You'd need more than 2 or 3 machines, and we'd need to react to changes in their availability.Let's start with just regular post-submit builders for now.
Well, the eventual goal is to certainly have them available for TryBots, so when possible, please let me know what I need to do to make that happen. The builders are fairly over-provisioned relative to what an actual build needs. As far as I know, at most, maybe a plugin to start Solaris Zones (containers) on demand would be required.Sure, if you want to work on that.
Yes, to be perfectly clear, I was volunteering for that work, not expecting anyone else to do it.Or you could do it all on your side, too.
My understanding was that this was a "simple" plugin to the buildlet/builder system. Is there any disadvantage/advantage to doing it one way or another?
I'm willing to implement whatever the preferred solution is.
You can write a thing on your side that polls http://farmer.golang.org/status/reverse.json and if it sees the "Waiters" count for your host type go up, you create more containers in Zones. If you see them idle, kill them off.
Yes, that's possible as well. The only question I have is what the requirements are for the container in this situation. For example, can I reuse a previously created container again and again? Do I have to wipe it between each reuse? I ask because currently, Solaris Zone creation is not a lightweight process, so my preference would be to simply pre-install a pool of them and then start and stop them on demand in such a scheme.
My assumption was that, in this case, there weren't any special requirements -- if it's good enough to run a buildlet, that's enough.
I'm willing to implement whatever the preferred solution is.
You can write a thing on your side that polls http://farmer.golang.org/status/reverse.json and if it sees the "Waiters" count for your host type go up, you create more containers in Zones. If you see them idle, kill them off.
Yes, that's possible as well. The only question I have is what the requirements are for the container in this situation. For example, can I reuse a previously created container again and again? Do I have to wipe it between each reuse? I ask because currently, Solaris Zone creation is not a lightweight process, so my preference would be to simply pre-install a pool of them and then start and stop them on demand in such a scheme.
My assumption was that, in this case, there weren't any special requirements -- if it's good enough to run a buildlet, that's enough.They should be new worlds between invocations. One buggy CL shouldn't impact a future non-buggy CL's test results.But if you destroy all the processes and just want to reuse the filesystem, the buildlet will create a temp dir and/or wipe a directory on startup.