feature req: add landscape server and other deployed applications to landscape itself
Bug #1681837 reported by
Adam Stokes
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Bundles |
New
|
Undecided
|
Unassigned | ||
Bug Description
tldrl The 4 services that are deployed via conjure-up or juju, have those machines registered into landscape for systems management.
From https:/
It'd be awesome for the out of the box experience if the machines that landscape runs was also managed so that you can see them in machines and look for immediate out of date packages and the like.
Revision history for this message
| Andreas Hasenack (ahasenack) wrote | #1 |
To post a comment you must log in.
There are some difficulties:
- there is no registration relation between the client and the server (so it's not mandatory to have the client in the same model/environment as the server)
- to register a client with the server, configuration settings are needed, and the bundle can't know beforehand what the address of the server will be, nor what certificate it will be using
- a client can only be registered after the first admin is created in the server: before that, there is no server "account" yet, and no computers can be registered
This is the current state. To make all this happen, at first glance these are the steps:
- grow a registration relation between server and client (first attempt here: https:/
- grow first admin creation options in the landscape-server charm, so that it will have the "standalone" account created automatically after deployment
If the deployment is done by conjure-up, then the client charm configuration and registration can easily be done as a post-deploy step in the spell.