Browse Source

Auto compute node registration

Change-Id: I1f951ef4bcc2a1e70c23dc92b891f7caf63cc0f1
Implements: bp auto-compute-node-registration
Kengo Takahara 1 year ago
parent
commit
b08b7ce819
1 changed files with 71 additions and 0 deletions
  1. 71
    0
      specs/queens/approved/lite-specs.rst

+ 71
- 0
specs/queens/approved/lite-specs.rst View File

@@ -0,0 +1,71 @@
1
+==================
2
+Masakari Spec Lite
3
+==================
4
+
5
+Please keep this template section in place and add your own copy of it between
6
+the markers. Please fill only one Spec Lite per commit.
7
+
8
+<Title of your Spec Lite>
9
+-------------------------
10
+
11
+:link: <Link to the blueprint.>
12
+
13
+:problem: <What is the driver to make the change.>
14
+
15
+:solution: <High level description what needs to get done. For example:
16
+            "We need to add client function X.Y.Z to interact with new server
17
+            functionality Z".>
18
+
19
+:impacts: <All possible \*Impact flags (same as in commit messages) or 'None'.>
20
+
21
+Optionals (please remove this line and fill or remove the rest until End):
22
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
23
+
24
+:how: <More technical details than the high level overview of `solution`
25
+       if needed.>
26
+
27
+:alternatives: <Any alternative approaches that might be worth of bringing
28
+                to discussion.>
29
+
30
+:timeline: <Estimation of the time needed to complete the work.>
31
+
32
+:reviewers: <If reviewers has been agreed for the functionality, list them
33
+             here.>
34
+
35
+:assignee: <If known, list who is going to work on the feature implementation
36
+            here>
37
+
38
+End of Template
39
++++++++++++++++
40
+
41
+Auto compute node registration
42
+------------------------------
43
+
44
+:link: https://blueprints.launchpad.net/masakari-monitors/+spec/auto-compute-node-registration
45
+
46
+:problem: If an user runs hostmonitor/instancemonitor/processmonitor without
47
+          registering the hosts in a segment and they detect a failure,
48
+          masakari doesn't perform the recovery process since source host is
49
+          unknown. Therefore, it will be more convenient if these monitors can
50
+          register a host automatically on startup.
51
+
52
+:solution: Hostmonitor/Instancemonitor/Processmonitor will register a host in
53
+           a particular segment if not already done on startup of these
54
+           services. The name of the host will be pickup automatically where
55
+           these monitors are running and it will call masakari create host
56
+           API to add a host in a particular segment. The segment to which the
57
+           host will be registered will be configurable. Also, a new config
58
+           option will be introduced to decide whether to register a host
59
+           automatically or an operator will configure it manually outside the
60
+           scope of monitors.
61
+
62
+:impacts: None
63
+
64
+:timeline: Expected to be merged within the Queens time frame.
65
+
66
+:reviewers: sam47priya@gmail.com, honjo.rikimaru@po.ntt-tx.co.jp
67
+
68
+:assignee: Kengo Takahara
69
+
70
+Auto compute node registration
71
+++++++++++++++++++++++++++++++

Loading…
Cancel
Save