(mirror of https://github.com/marekm72/vyos-cloud-init.git) https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=20.1 2020-01-21T22:15:30+00:00 2020-01-21T22:15:30+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-01-21T22:15:30+00:00 urn:sha1:8c4fd886931abcf2cc8627a47463907d655b35c3 * url_helper: drop six * url_helper: sort imports * log: drop six * log: sort imports * handlers/__init__: drop six * handlers/__init__: sort imports * user_data: drop six * user_data: sort imports * sources/__init__: drop six * sources/__init__: sort imports * DataSourceOVF: drop six * DataSourceOVF: sort imports * sources/helpers/openstack: drop six * sources/helpers/openstack: sort imports * mergers/m_str: drop six This also allowed simplification of the logic, as we will never encounter a non-string text type. * type_utils: drop six * mergers/m_dict: drop six * mergers/m_list: drop six * cmd/query: drop six * mergers/__init__: drop six * net/cmdline: drop six * reporting/handlers: drop six * reporting/handlers: sort imports 2019-11-08T21:02:07+00:00 momousta momousta 2019-11-08T21:02:07+00:00 urn:sha1:92cc71dec8da73bf43d345418b73db1a32a6b8b9 The KVPs currently being emitted to the .kvp_pool file can have duplicate keys which is wrong since these keys should be unique. The situation can occur if for example one azure function called twice or more and this function is reporting telemetry through the use of KVPs. Any KVP consumer can get confused by the duplicate keys and a race condition can and have occurred. 2019-04-29T20:22:16+00:00 Anh Vo anhvo@microsoft.com 2019-04-29T20:22:16+00:00 urn:sha1:86674f013dfcea3c075ab41373ffb475881066f6  + Truncate KVP Pool file to prevent stale entries from being processed by the Hyper-V KVP reporter.  + Drop filtering of KVPs as it is no longer needed.  + Batch appending of existing KVP entries. 2018-08-31T21:47:18+00:00 Ryan Harper ryan.harper@canonical.com 2018-08-31T21:47:18+00:00 urn:sha1:43e51a04515686a15c410d1a16dd5ff06fd1afd4 Switch the implementation to a daemon thread which uses a blocking get from the Queue. No additional locking or flag checking is needed since the Queue itself handles acquiring the lock as needed. cloud-init only has a single producer (the main thread calling publish) and the consumer will read all events in the queue and write them out. Using the daemon mode of the thread handles flushing the queue on main exit in python3; in python2.7 we handle the EOFError that results when the publish thread calls to get() fails indicating the main thread has exited. The result is that the handler is no longer spawing a thread on each publish event but rather creates a single thread when we start up the reporter and we remove any additional use of separate locks and flags as we only have a single Queue object and we're only calling queue.put() from main thread and queue.get() from consuming thread. 2018-08-24T22:25:37+00:00 Andy Liu andyliuliming@outlook.com 2018-08-24T22:25:37+00:00 urn:sha1:2320c3de2712c2f320b0d8af4aa129219cc2ad04 Linux guests can provide information to Hyper-V hosts via KVP. KVP allows the guests to provide any string key-value-pairs back to the host's registry. On linux, kvp communication pools are presented as pool files in /var/lib/hyperv/.kvp_pool_#. The following reporting configuration can enable this kvp reporting in addition to default logging if the pool files exist: reporting:     logging:         type: log     telemetry:         type: hyperv 2018-04-20T03:30:08+00:00 Scott Moser smoser@ubuntu.com 2018-04-20T03:30:08+00:00 urn:sha1:1081962eacf2814fea6f4fa3255c530de14e4a24 This enables warnings produced by pylint for unused variables (W0612), and fixes the existing errors. 2017-04-21T14:14:47+00:00 Joshua Powers josh.powers@canonical.com 2017-04-06T18:14:29+00:00 urn:sha1:5afe4cd0797a12d07ea19b9715b720d47bdea401 This will change all instances of LOG.warn to LOG.warning as warn is now a deprecated method. It will also make sure any logging uses lazy logging by passing string format arguments as function parameters. 2016-12-22T22:04:28+00:00 Jon Grimm jon.grimm@canonical.com 2016-11-22T23:09:53+00:00 urn:sha1:b2a9f33616c806ae6e052520a8589113308f567c This has been a recurring ask and we had initially just made the change to the cloud-init 2.0 codebase. As the current thinking is we'll just continue to enhance the current codebase, its desirable to relicense to match what we'd intended as part of the 2.0 plan here. - put a brief description of license in LICENSE file - put full license versions in LICENSE-GPLv3 and LICENSE-Apache2.0 - simplify the per-file header to reference LICENSE - tox: ignore H102 (Apache License Header check) Add license header to files that ship. Reformat headers, make sure everything has vi: at end of file. Non-shipping files do not need the copyright header, but at the moment tests/ have it. 2016-05-12T17:56:26+00:00 Joshua Harlow harlowja@gmail.com 2016-05-12T17:56:26+00:00 urn:sha1:f11827aee59cf2678c3d2a157218a3fe2831f5c2 2016-05-06T17:19:24+00:00 Scott Moser smoser@ubuntu.com 2016-05-06T17:19:24+00:00 urn:sha1:690bdce9a73ec6d00b4eebbbca31cc527e7b2fce If no timestamp was passed into a ReportingEvent, then the default was used. That default was 'time.time()' which was evaluated once only at import time.