yodlr / coregi Goto Github PK

Using fleetctl, I see a unit is stopped/failed, but in CoreGI it's being reported as RUNNING.

REST API for CoreGI also reports RUNNING, so it must be a backend issue.

Running in our docker staging & production environments

The default values:

FLEET_ENDPOINT = 'http://172.17.42.1:4001'
ETCD_HOST = '172.17.42.1

will not work if the ip address of the docker service is changed, which is the case when flanneld is used.

I will submit a PR that sets it to the host private ip in the unit file, if you think it is a correct fix.

The list of keys shows the "directories", but does not show the children or provide any way to recurse through the etcd tree.

Hi guys,

Thanks for the nice UI for CoreOS services.

Would be possible to change IP "172.17.42.1" vis docker env, please?
As e.g. CoreOS on vagrant docker uses different IP "10.1.42.1" so I have to add updated "index.js" via
volume for now to get it working in vagrant based CoreOS.

Thanks

could you pls add environment variable which would allowe to publish CoreGI non-root url path ?

like http:///coregi

thank you

Is ui supposed to to be coregi aka module.export?

See sample:

module.exports = {}
function test(){
    console.log('type:' + typeof(this))
    if(global === this) console.log('global')
    if(module.exports === this) console.log('exports')
}
module.exports.test = test;
test()
console.log('----')
module.exports.test();

Are you intending on having ui be short hand for module.exports and coregi?

If also noticed that ui.app was used frequently. Was message chaining avoided?

We should add os version and release channel information about the host machine, into the machines view.

Currently we are using fleetctl to grab machine info using list-machines, but the information we want is not present. We need to find a solution into getting the information we want.

Show unit uptime on #/units once fleetctl reports this (currently a PR in fleetctl: coreos/fleet#1293).

We should probably prettify that output

If you have a lot of machines / units, these views get really crowded. It would be good to have a filter / search on these views to limit the results.