maas-devel team mailing list archive

[Jeffrey Lane <jeffrey.lane@xxxxxxxxxxxxx>]

On Thu, Jul 10, 2014 at 10:13 AM, Blake Rouse <blake.rouse@xxxxxxxxxxxxx> wrote:
> Jeff,
>
> If you are looking to do something like this currently, Tycho approach would
> work well. I have added on to it, this will give you the exact version of
> the installed MAAS package.
>
> http://paste.ubuntu.com/7775359/
>
> - Blake

Thanks Tycho and Blake,

That's a much, much cleaner method but essentially exactly where we
were headed.  I wanted to be sure there wasn't a different or "more
appropriate" way first before going down that road though.


>
>
> On Thu, Jul 10, 2014 at 7:08 AM, Graham Binns <graham.binns@xxxxxxxxxxxxx>
> wrote:
>>
>> On 10 July 2014 11:10, Mark Shuttleworth <mark@xxxxxxxxxx> wrote:
>> > Would not be a bad idea to record enough information for the node (or
>> > software running on the node) to talk back to MAAS. For example, a
>> > unique shared key (readable only by root) together with the MAAS
>> > location and API version.
>> >
>> > This would allow, for example, the machine to update MAAS hardware
>> > database without a reboot cycle.
>>
>> We're planning to do something exactly like this as part of the node
>> lifecycle / robustness work. It will allow nodes to phone home to MAAS
>> in order to confirm that (say) the installation process completed
>> successfully and they're now available for use.
>>
>> --
>> Mailing list: https://launchpad.net/~maas-devel
>> Post to     : maas-devel@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~maas-devel
>> More help   : https://help.launchpad.net/ListHelp
>
>



-- 
"Entropy isn't what it used to be."

Jeff Lane - Server Certification Team Lead, Tools Developer, Warrior
Poet, Lover of Pie
Phone: 919-442-8649
Ubuntu Ham: W4KDH                          Freenode IRC: bladernr or bladernr_
gpg: 1024D/3A14B2DD 8C88 B076 0DD7 B404 1417  C466 4ABD 3635 3A14 B2DD