- 04 Sep, 2020 1 commit
-
-
Maria A. Serrano authored
-
- 14 Oct, 2019 1 commit
-
-
- 12 Sep, 2019 2 commits
-
-
Kyle Nitzsche authored
Uses adopt-info with new 'version' part. Appends date and git info to version as previously. Signed-off-by:
Kyle Nitzsche <kyle.nitzsche@canonical.com>
-
Kyle Nitzsche authored
Needed now since master moves files around which breaks snapcraft build for edinburgh track. Signed-off-by:
Kyle Nitzsche <kyle.nitzsche@canonical.com>
-
- 04 Sep, 2019 1 commit
-
-
Daniel Harms authored
* Fixes error handling in core-data event/ POST rte Error from a call to `addNewEvent()` was being ignored in the handler, causing failures to add Events to be swallowed and 200 OKs to be returned to clients. This change adds error handling for the route in accordance with the RAML file at https://github.com/edgexfoundry/edgex-go/blob/master/api/raml/core-data.raml * Update version numbers for Edinburgh patch release Signed-off-by:
Daniel Harms <jdharms@gmail.com>
-
- 20 Aug, 2019 1 commit
-
-
- 31 Jul, 2019 2 commits
-
-
Akram Ahmad authored
Fix host config in config TOML.
-
Akram Ahmad authored
Signed-off-by:
Akram Ahmad <sftwr2020@gmail.com>
-
- 25 Jul, 2019 1 commit
-
-
Ernesto Ojeda authored
Signed-off-by:
Ernesto Ojeda <ernesto.ojeda@intel.com>
-
- 19 Jul, 2019 3 commits
-
-
Trevor Conn authored
Fix #1544 The primary issue is observed when one runs "docker-compose up" after pruning local docker volumes. The following problematic symptoms have been observed. The requisite code changes in this PR are enumerated below. I hesitate to properly call this a "fix" because I think more analysis is warranted for a long term solution. However for the purpose of stabilizing the release, this should suffice. - Observed that population of configuration data in Consul and subsequent creation of DBs/Collections and credentials in Mongo were delayed when creating volumes for the first time. This lead to timing issues in the following areas - I observed conditions where the Config-Seed was populating Consul for a given service at the same time that that service's configuration was being read into Consul by the config-seed. Thus services would come up and read their configuration from Consul when that config was only partially populated. In Delhi this would not be a problem because the listenForConfigChanges() function would listen for a change anywhere in the service's config in Consul. This would cause the entirety of the ConfigurationStruct to be populated when the last key was written. In Edinburgh, we only listen for changes to the "Writable" section, which is written first. -- This is why initializeConfiguration() has been modified to look at the last value of the service's configuration within Consul to see if it has been populated. If it is not, then we throw an error -- forcing a retry one second later. If it is populated, the whole config has been written to Consul and we can proceed. - All services write logging information when they are bootstrapping. If the service is configured to log remotely, those calls go to support-logging. Because of the observed latency (up to 5 seconds) in populating configuration and Mongo with new volumes, any service trying to send its startup messages to support-logging would throw an error. This lead to many, mnay errors in the starup process. Once support- logging came up, the remote logging would work. Understand that every service must receive its configuration information from Consul and, where applicable, establish DB connectivity before it activates its API handlers. If a service calls support-logging (or any other service) before the API is enabled, the caller will receive a "connection re- fused". -- This was also mitigated by the code change above. - In the case where a service is delayed in its startup, it will not register its endpoint with Consul. Export-client does not require a database connection and so it will come up before export-distro. It was observed that the rules-engine registers with export-client in order to receive events. As a result of that, export-client attempts to POST a notification to export-distro. Because export-distro had not registered itself with Consul at the time export-client was being configured, the endpoint information would be blank, leading to an error like this (some fields omitted): level=ERROR app=edgex-export-client source=registration.go:310 msg="error from distro: Put http://:0/api/v1/notify/registrations : dial tcp :0: connect: connection refused" Notice the the host and port. -- The code change to address this can be found in internal/pkg/startup/endpoint.go -- This only works due to the non-HA mode in which we deploy from docker-compose. Right now, what's in the docker configuration is always the same as what is (or will be) in Consul. -- Note also that there is a circular dependency between distro/client w/r/t how they call each other. Because the result of a notification sent to distro in the above case is that distro simply calls back to export-client. Signed-off-by:
Trevor Conn <trevor_conn@dell.com>
-
Jim White authored
Removes ./docs/ folder which now resides in the edgex-docs repo
-
Michael Hall authored
Fixed #1528 Signed-off-by:
Michael Hall <mhall119@gmail.com>
-
- 18 Jul, 2019 1 commit
-
-
xmlviking authored
Fix #1497 Fixed issue with Scheduler POST and PUT HTTP Verbs not supplying JSON body when creating interval actions. Fixed scheduler rst documentation around the use of interval and interval actions. Signed-off-by:
xmlviking <ecotter@gmail.com>
-
- 10 Jul, 2019 5 commits
-
-
Marco Gonzalez Hierro authored
-
Marco Gonzalez Hierro authored
-
Marco Gonzalez Hierro authored
-
Marco Gonzalez Hierro authored
-
Marco Gonzalez Hierro authored
-
- 09 Jul, 2019 1 commit
-
-
Michael Hall authored
Replace references to the delhi docker-compose file with references to the edinburgh docker-compose file. Fixes #1514 Signed-off-by:
Michael Hall <mhall119@gmail.com>
-
- 08 Jul, 2019 1 commit
-
-
Trevor Conn authored
Fix #1509 - Also noticed that if an error were to occur during publishing, our logging was dropping that from the message. Added error contents to log output in this case. Signed-off-by:
Trevor Conn <trevor_conn@dell.com>
-
- 26 Jun, 2019 1 commit
-
-
Brandon Forster authored
Signed-off-by:
Brandon Forster <brandonforster@gmail.com>
-
- 24 Jun, 2019 1 commit
-
-
Rebekah authored
* Fixes 1182 Signed-off-by:
Michael Hall <mhall119@gmail.com>
-
- 20 Jun, 2019 3 commits
-
-
Jim White authored
added the additional docs getting started PNG files from master and fixed one build error in getting started SDK C Signed-off-by:
Jim White <jpwhite_mn@yahoo.com>
-
Jim White authored
Signed-off-by:
Jim White <jpwhite_mn@yahoo.com>
-
Jim White authored
Fix security-api-gateway config file
-
- 19 Jun, 2019 1 commit
-
-
Ian Johnson authored
The upstream configuration.toml default value changed such that this sed expression changing the tokenpath to the correct one for the snap no longer applied, leading to edgexproxy being unable to use the token to load the certificates from vault into Kong for Kong to use when serving HTTPS endpoints. Fixes: #1458 Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-
- 14 Jun, 2019 1 commit
-
-
Brandon Forster authored
Signed-off-by:
Brandon Forster <brandonforster@gmail.com>
-
- 12 Jun, 2019 2 commits
-
-
Ian Johnson authored
See https://github.com/edgexfoundry/blackbox-testing/issues/185 for more details, but basically Kong isn't meant to work properly on arm64 until it is updated to use OpenResty 1.15 so until that point we just always disable the security-api-gateway services on arm64 in the install hook. Note that due to another snapd bug where all services are restarted on refresh, we also need to implement a workaround in the kong service itself because it will be started up on refresh and we still don't want kong to really run on arm64 even in the event it is erroneously started. Returning from the kong-daemon.sh script like this will result in systemd initially assuming that the process started and proceeding to start other dependent services, but shortly thereafter realizing there are not children processes and thus marking the service as "inactive". Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-
Ian Johnson authored
* Upgrade to Kong 1.0.3 * Use `kong migrations bootstrap` instead of `kong migrations up` * Remove lua and luarocks parts and use the bionic ubuntu archive pkgs lua5.1 and luarocks instead * Remove kong build dependency on openresty part as they no longer need to be built after each other * Build kong inside $SNAPCRAFT_PART_INSTALL * Upgrade to OpenResty 1.13.6.2 and build with kong's patches * Replace hard-coded location of nginx in "resty" binary from OpenResty to use /snap/edgexfoundry/current based path instead of $SNAPCRAFT_PART_INSTALL * Fix the nginx and openresty symlinks inside openresty's $SNAPCRAFT_PART_INSTALL/bin dir to be relative instead of absolute * Use dpkg --print-architecture instead of uname -m for better compatibility when cross compiling * Add layout for /etc/luarocks to view into $SNAP/etc/luarocks using a bind mount such that luarocks doesn't trigger AppArmor denials every time it starts up via kong. This path is supposedly configurable with a build time flag but I haven't been able to figure out which flag is to be used for this. Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-
- 10 Jun, 2019 1 commit
-
-
Ian Johnson authored
Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-
- 07 Jun, 2019 1 commit
-
-
Diana Atanasova authored
Fix #1410 When Deleting DeviceProfile clean command indexes too. Applicable only for Redis database. Signed-off-by:
difince <dianaa@vmware.com>
-
- 06 Jun, 2019 9 commits
-
-
Diana Atanasova authored
Fix #1392 When using Redis DB do not raise error when searching for multiple objects and none object is found. Just return empty slice. Signed-off-by:
difince <dianaa@vmware.com>
-
Ian Johnson authored
The registry arg is now a --key=val style option, where the value is a custom URL spec with the scheme as the registry type. Since the snap only works with consul for now, the scheme is just "consul". Note we have to specify the value as an environment variable because snapd doesn't allow the ":" character in a app's command spec. See https://bugs.launchpad.net/snapd/+bug/1827392 for the upstream bug/feature request to snapd. Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-
Ian Johnson authored
Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-
Ian Johnson authored
This ensures the snap is always built against the edinburgh version of the other components such as the security services, device services and support-rulesengine. Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-
Ian Johnson authored
While device services don't by default need support-logging, they could be configured to use remote logging in which case they would need access to support-logging. As such, when starting services up, order the device services after support-logging for efficiency. Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-
Ian Johnson authored
These device services will be split out into their own snaps for Edinburgh, edgex-device-modbus and edgex-device-mqtt respectively. Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-
Ian Johnson authored
Note we turn off the warning about the constant value for loop in case we ever need to add another java service it will be easier if we leave this in place. Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-
Ian Johnson authored
Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-
Ian Johnson authored
This change ensures that in the future we will be able to identify the release a snap was on before it was refreshed, to allow easier fixes in the case something is broken and we need to fix. Additionally it gives us the option to special case Edinburgh -> XYZ upgrades by using the "release" config item. Signed-off-by:
Ian Johnson <ian.johnson@canonical.com>
-