markmc

[
  {
    "type": "build_system",
    "req": "poetry-core>=1.0.0"
  },
  {
    "type": "build_system",
    "req": "flit_core >=3.8,<4"
  },
  {

markmc

$ git branch
[..]
  master
* payload-kubevirt
$ git rev-parse HEAD
9b6280b717cea4a68d3a057350f3af4666da1a52
[markmc@dell-r630-011 release]$ git diff
diff --git a/release/prep_release.sh b/release/prep_release.sh
index 5b9609b..36dcd18 100755
--- a/release/prep_release.sh

markmc

.config
.config/InSilmaril
.config/gtk-2.0
.config/gnome-session
.config/sealert.conf
.config/dleyna-server-service.conf
.config/autostart
.config/dconf
.config/goa-1.0
.config/user-dirs.locale

markmc

$> git grep '20[0-9][0-9]-' doc/api_samples/ | wc -l
509

with UTC TZ:

$> git grep '20[0-9][0-9]-[0-9][0-9]-[0-9][0-9]T[0-9][0-9]:[0-9][0-9]:[0-9][0-9]Z' doc/api_samples/ | wc -l
230

with zero offset TZ:

markmc

diff --git a/nova/tests/api/openstack/compute/test_servers.py b/nova/tests/api/openstack/compute/test_servers.py
index 22dc9d4..7559896 100644
--- a/nova/tests/api/openstack/compute/test_servers.py
+++ b/nova/tests/api/openstack/compute/test_servers.py
@@ -4308,7 +4308,7 @@ class ServerXMLSerializationTest(test.TestCase):
     def test_create(self):
         serializer = servers.FullServerTemplate()
 
-        self.body["server"]["adminPass"] = "test_password"
+        self.body["server"]["adminPass"] = u'\u89e3\u7801'

markmc

class Kombu(object):

    def __init__(self):

        self.params = {
            'hostname': 'localhost',
            'port': 5672,
            'virtual_host': '/',

markmc

$> python ./test-notification-server.py

$> python test-notification.py --config-file ./test.conf --debug
$> git reset --hard 5315399
$> python test-notification-old.py --config-file ./test.conf --debug

markmc

commit: de2218e
merge-base: ce71b66
onto: d34a04d

git diff ce71b66..d34a04d

CONFLICT (content): Merge conflict in requirements.txt
 - easy

CONFLICT (content): Merge conflict in nova/utils.py

markmc

There can be multiple form of actions, but two have been implemented so far:

1. http call back: you provide a URL to be called whenever the alarm has been set off. The payload of the request contains all the details of why the alarm went off.
2. log: mostly useful for debugging, stores alarms in a log file.

markmc

import eventlet

eventlet.monkey_patch(os=False)

import logging

from oslo import messaging

logging.basicConfig(level=logging.DEBUG)