search

bigfix / developer.bigfix.com

The source for developer.bigfix.com
https://developer.bigfix.com
Apache License 2.0
27 stars 23 forks source link

Evaluator doesn't work on production site #50

Closed strawgate closed 8 years ago

strawgate commented 9 years ago

https://developer.bigfix.com/

Fails with status 502

Works in local environment

briangreenery commented 9 years ago

Ah yeah, I haven't set up that machine yet. I'll do that real soon now.

briangreenery commented 9 years ago

This is basically set up, I just need to double check that it's okay for everything on that machine to be visible to the internet. I don't know how long that will take...hopefully not too long.

gnawhleinad commented 9 years ago

I started gnawhleinad/evaluate to move the relevance evaluation in a Docker container. It currently runs on node:onbuild.

briangreenery commented 9 years ago

Nice.

I'm unfamiliar with docker. It looks like 'name of operating system' still returns 'red hat'. Is this still red hat? Do we have to worry about having the right libraries available to look at rpms and stuff? Would we put some example stuff on the filesystem to inspect?

Orr what do you think we should do next to use this?

gearoidibm commented 9 years ago

From woking with the agent in containers for a while I'd say pretty much everything will work. Only obvious strangeness is the operating system inspector, for example Ubuntu containers on CentOS or RHEL host will return Red Hat as the operating system. So I'd say best to match the container OS to the guest OS.

gnawhleinad commented 9 years ago

Do we have to worry about having the right libraries available to look at rpms and stuff?

I fixed the rpm inspector issue at gnawhleinad/evaluate@630b757!

Would we put some example stuff on the filesystem to inspect?

We could add some example files (and mention them at https://developer.bigfix.com/relevance/guide/client/files.html).

Maybe longer term, we could allow users to add any file to the container via ADD.

Orr what do you think we should do next to use this?

I want to make it easier to deploy and update the evaluate application (gnawhleinad/evaluate#3). After that, it should be in a state for us to resolve this issue.

gnawhleinad commented 9 years ago

I've chosen to pursue a different (but similar) route that does not use node:onbuild. Pull request is coming!

briangreenery commented 8 years ago

I took the work that Daniel started and incorporated it into the site here. The relevance evaluator now runs inside of a centos 7 docker container.