os-autoinst-distri-rocky/needles/iot/zezere_provision_schedule-20200721.json

{
  "area": [
    {
      "xpos": 176,
      "ypos": 214,
      "width": 52,
      "height": 13,
      "type": "match"
    }
  ],
  "properties": [],
  "tags": [
    "zezere_provision_schedule"
  ]
}
Automate QA:Testcase_Zezere_Ignition This is a bit complex to automate, because we cannot really use the production Zezere server (provision.fedoraproject.org) as the test case shows, as we'd have to solve authentication and we also don't really want to constantly keep registering new hosts to it that are going to disappear and never be seen again. So, instead we'll do it by setting up our own Zezere, and provisioning our IoT system in that. We run two tests. The 'ignition' test is the actual IoT 'device'; all it really does is boot up, sit around, and wait to be provisioned. The 'server' test first sets up a Zezere server, then logs into it, adds an ssh key, claims the IoT device, provisions it, and connects to it to create a special file which tells the 'ignition' test everything worked and it can close out. Signed-off-by: Adam Williamson <awilliam@redhat.com> 2020-07-15 21:56:32 +00:00			`{`
			`"area": [`
			`{`
			`"xpos": 176,`
			`"ypos": 214,`
			`"width": 52,`
			`"height": 13,`
			`"type": "match"`
			`}`
			`],`
			`"properties": [],`
			`"tags": [`
			`"zezere_provision_schedule"`
			`]`
			`}`