Merge lp:~jtv/maas/sample-commissioning-data into lp:~maas-committers/maas/trunk

Proposed by Jeroen T. Vermeulen
Status: Merged
Approved by: Jeroen T. Vermeulen
Approved revision: no longer in the source branch.
Merged at revision: 1956
Proposed branch: lp:~jtv/maas/sample-commissioning-data
Merge into: lp:~maas-committers/maas/trunk
Diff against target: 72 lines (+65/-0)
1 file modified
src/maasserver/fixtures/dev_fixture.yaml (+65/-0)
To merge this branch: bzr merge lp:~jtv/maas/sample-commissioning-data
Reviewer Review Type Date Requested Status
Raphaël Badin (community) Approve
Review via email: mp+206711@code.launchpad.net

Commit message

Sample NodeCommissionResults for development exploration.

Description of the change

This is something Raphaël suggested. I added commissioning data for two nodes: for the Failed one (which now has results reminiscent of a typical failure observed in practice) and for one of the Missing ones. You'd expect successful results for Ready nodes as well, but we have no Ready nodes in the sample data.

The one data field may look garbled: it's base64-encoded data. We encode binary fields as text in order to get Django to support them. It's a simple error message; I had to keep it brief. I did not use an actual message as observed in the wild.

Jeroen

To post a comment you must log in.
Revision history for this message
Raphaël Badin (rvb) wrote :

Nice, thanks for doing this. It will help us a great deal polish the UI.

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'src/maasserver/fixtures/dev_fixture.yaml'
2--- src/maasserver/fixtures/dev_fixture.yaml 2013-12-10 15:16:27 +0000
3+++ src/maasserver/fixtures/dev_fixture.yaml 2014-02-17 13:29:53 +0000
4@@ -190,3 +190,68 @@
5 name: zone-b
6 model: maasserver.zone
7 pk: 4
8+- fields:
9+ created: 2012-02-17
10+ updated: 2012-02-17
11+ node: 16
12+ name: '00-maas-01-lshw.out'
13+ script_result: 0
14+ model: metadataserver.nodecommissionresult
15+ pk: 1
16+- fields:
17+ created: 2012-02-17
18+ updated: 2012-02-17
19+ node: 16
20+ name: '00-maas-02-virtuality.out'
21+ script_result: 0
22+ model: metadataserver.nodecommissionresult
23+ pk: 2
24+- fields:
25+ created: 2012-02-17
26+ updated: 2012-02-17
27+ node: 16
28+ name: '00-maas-03-install-lldp.out'
29+ script_result: 1
30+ data: RXJyb3Igd2hpbGUgaW5zdGFsbGluZyBsbGRwOiBOZXR3b3JrIHVucmVhY2hhYmxlLgo=
31+ model: metadataserver.nodecommissionresult
32+ pk: 3
33+- fields:
34+ created: 2012-01-25
35+ updated: 2012-01-25
36+ node: 17
37+ name: '00-maas-01-lshw.out'
38+ script_result: 0
39+ model: metadataserver.nodecommissionresult
40+ pk: 4
41+- fields:
42+ created: 2014-01-25
43+ updated: 2012-01-25
44+ node: 17
45+ name: '00-maas-02-virtuality.out'
46+ script_result: 0
47+ model: metadataserver.nodecommissionresult
48+ pk: 5
49+- fields:
50+ created: 2014-01-25
51+ updated: 2012-01-25
52+ node: 17
53+ name: '00-maas-03-install-lldp.out'
54+ script_result: 0
55+ model: metadataserver.nodecommissionresult
56+ pk: 6
57+- fields:
58+ created: 2014-01-25
59+ updated: 2012-01-25
60+ node: 17
61+ name: '99-maas-01-wait-for-lldp.out'
62+ script_result: 0
63+ model: metadataserver.nodecommissionresult
64+ pk: 7
65+- fields:
66+ created: 2014-01-25
67+ updated: 2012-01-25
68+ node: 17
69+ name: '99-maas-02-capture-lldp.out'
70+ script_result: 0
71+ model: metadataserver.nodecommissionresult
72+ pk: 8