reconfigureio / reco Goto Github PK

View Code? Open in Web Editor NEW

6.0 6.0 3.0 169 KB

A command line tool for interacting with Reconfigure.io services

License: Apache License 2.0

Makefile 2.89% Go 93.25% Shell 0.25% Batchfile 0.03% NSIS 3.47% Dockerfile 0.11%

reco's People

Contributors

Stargazers

Watchers

Forkers

neapace stillwater-sc mennis

reco's Issues

Users should be able to view Simulation reports

Reports should be JSON formatted

Currently there is Build Report: at the start of each build report, which I think prevents it from being machine-readable:

Build Report: {
	"partName": "xcvu9p-flgb2104-2-i",
	"lutSummary": {
		"used": 20104,
		"detail": {
			"lutLogic": {
				"used": 16718,
				"available": 1182240,
				"description": "LUT as Logic",
				"utilisation": 1.41
			},
			"lutMemory": {
				"used": 3386,
				"available": 591840,
				"description": "LUT as Memory",
				"utilisation": 0.57
			}
		},
		"available": 1182240,
		"description": "CLB LUTs",
		"utilisation": 1.7
	},
	"moduleName": "reconfigure_io_sdaccel_builder_stub_0_1",
	"regSummary": {
		"used": 54601,
		"detail": {
			"regLatch": {
				"used": 0,
				"available": 2364480,
				"description": "Register as Latch",
				"utilisation": 0
			},
			"regFlipFlop": {
				"used": 54601,
				"available": 2364480,
				"description": "Register as Flip Flop",
				"utilisation": 2.31
			}
		},
		"available": 2364480,
		"description": "CLB Registers",
		"utilisation": 2.31
	},
	"blockRamSummary": {
		"used": 17,
		"detail": {
			"blockRamB18": {
				"used": 32,
				"available": 4320,
				"description": "RAMB18",
				"utilisation": 0.74
			},
			"blockRamB36": {
				"used": 1,
				"available": 2160,
				"description": "RAMB36/FIFO",
				"utilisation": 0.05
			}
		},
		"available": 2160,
		"description": "Block RAM Tile",
		"utilisation": 0.79
	},
	"dspBlockSummary": {
		"used": 0,
		"available": 6840,
		"description": "DSPs",
		"utilisation": 0
	},
	"ultraRamSummary": {
		"used": 0,
		"available": 960,
		"description": "URAM",
		"utilisation": 0
	},
	"weightedAverage": {
		"used": 139369,
		"available": 9067200,
		"description": "Weighted Average",
		"utilisation": 1.54
	}
}

New 'status' command

$ reco build status foobar
status: errored

(the different options need fleshing out here)

Check host cmd name at start of sim

Currently if you run a simulation with an incorrect host-side command name you don't find out there's a problem until the instance is spun up etc.

Users need a way to see what host-side commands are available for a build image.

Currently once a build is run, there's no way to see what host-side commands were included at the time, this means that without the user 'remembering' running the desired command at deployment will be difficult.

Comment from old trello card:

Reco needs to be able to figure out which host commands are available based on state of disk. Needs to report those to platform. User needs to be able to view those for a build as part of reco build show-host-cmds or something. Stop a user running a sim using a host command that isn't on disk.

Error: authentication required. Run 'reco auth' to authenticate

when run reco build
show this error in linux

`make build` produces unrunnable Linux binary on OSX

Comment from Max from trello card: kubectl uses go env GOARCH and GOOS in its makefile so it detects the OS at run time. Unfortunately it doesn't quite spit out our current string, returning amd64-linux instead of x86_64-linux

Projects should be required to have a unique name

Currently it is possible to have multiple projects with exactly the same name, this makes searching and keeping track of projects difficult.

Simulate and build fail when symlinks point outside the source dir

Warn users when they use unsupported standard library imports

Can offer our targeted versions if relevant.

Unknown error when attempting to stop a deployment

When I start a deployment, then try to stop it using reco deploy stop <ID> I get the error message:

histogram-array $ reco deploy stop fc27a0c5-a106-414f-8cd0-f13038fd3ee0

Error: Unknown error occurred

But if I look at the deploy list I see it's trying to terminate:

histogram-array $ reco deploy list

             DEPLOYMENT ID                                BUILD ID                           COMMAND               STATUS           STARTED         DURATION  
  fc27a0c5-a106-414f-8cd0-f13038fd3ee0      b5e66fb4-4b0e-4f8c-97d6-32248f02f320      test-histogram             terminating      1 minute ago      -         
  7766670e-de85-467e-8469-bf94bd255ebc      b5e66fb4-4b0e-4f8c-97d6-32248f02f320      test-histogran             errored          1 week ago        2m15s     
  448ea0d3-d66f-4d14-940f-14524c8d1464      33a606f2-7f5a-4748-bb5f-221473011e93      bench-histogram-FPGA       completed        2 months ago      3m7s

reco installer .exe unsigned causing scary Windows Defender popup

The .exe needs to be signed to prevent this

Users should have the ability to delete projects (inc all sim/build/deploy associated)

There would need to be stages of warnings for this, but for users to be able to manage their accounts effectively, they need a way to at least archive work, so their workspace isn't just always full of all the work they have ever done using our service.

New command to initialise project

Can we have two options, reco project init to create empty files in the correct structure, and reco project init template to create a copy of our template at that location?


   ├── cmd
   │   ├── bench-my-program
   │   ├── test-my-program
   │      └── main.go
   ├── glide.yaml
   ├── main.go
   ├── main_test.go
   ├── reco.yml

Maybe with the option to specify a name? reco project init --name "histogram" or whatever:


   ├── cmd
   │   ├── bench-histogram
   │   ├── test-histogram
   │      └── main.go
   ├── glide.yaml
   ├── main.go
   ├── main_test.go
   ├── reco.yml