Accessing the metadata API?
Jim Tilander
jim at tilander.org
Wed Feb 8 16:52:16 UTC 2017
Ah, thanks Blake for the documentation pointer.
Cheers,
Jim
> On Feb 8, 2017, at 8:44 AM, Blake Rouse <blake.rouse at canonical.com> wrote:
>
> Jim,
>
> At the moment the best documentation we have for this is here:
>
> https://maas.ubuntu.com/docs/configure.html#altering-the-preseed-file <https://maas.ubuntu.com/docs/configure.html#altering-the-preseed-file>
>
> We are working on improving the documentation for MAAS, but we have not add that section yet as we are working through it. The updated documentation is located here: https://docs.ubuntu.com/maas/2.1/en/ <https://docs.ubuntu.com/maas/2.1/en/> but does not document the preseed possibilities.
>
> There is a bug filed about this: https://bugs.launchpad.net/maas/+bug/1334426 <https://bugs.launchpad.net/maas/+bug/1334426> and I will raise it with our documentation team to get it improved.
>
> Thanks,
> Blake
>
> On Wed, Feb 8, 2017 at 11:17 AM, Jim Tilander <jim at tilander.org <mailto:jim at tilander.org>> wrote:
> Hi Blake,
>
> Thanks for that. Is there some way / docs that I can discover what can be templated like this? I’ve been struggling to find the “correct” docs and iterating on these things to discover them by trial and error is a little bit long since it takes a whole install for me.
>
> Cheers,
> Jim
>
>> On Feb 8, 2017, at 8:14 AM, Blake Rouse <blake.rouse at canonical.com <mailto:blake.rouse at canonical.com>> wrote:
>>
>>
>>
>> On Wed, Feb 8, 2017 at 11:10 AM, Jim Tilander <jim at tilander.org <mailto:jim at tilander.org>> wrote:
>> Hi Andres,
>>
>> Basically I’ve been struggling with how curtin works, but I finally got the the following stuck in curtin_userdata:
>>
>> 99_bootstrap: ["curtin", "in-target", "/bin/bash", "/usr/local/bin/post-install.sh"]
>>
>> 99_bootstrap: ["curtin", "in-target", "/bin/bash", "/usr/local/bin/post-install.sh", "{{node.fqdn}}"]
>>
>> With that the FQDN of the node will be passed as the first parameter of your script.
>>
>>
>>
>> Then in the post-install.sh script I actually want to extract the FQDN of my node (but since I run in the installer environment, I can’t really rely it seems on the network to tell me this).
>>
>> When you mention that I could do node.fqdn(), where would I put that? Is that some curtin templating? Python?
>>
>> Thanks,
>> Jim
>>
>>> On Feb 3, 2017, at 6:06 AM, Andres Rodriguez <andres.rodriguez at canonical.com <mailto:andres.rodriguez at canonical.com>> wrote:
>>>
>>> All I wanted to do was to reliably lookup my own FQDN, as well optionally get some custom payload for each node into a script that runs during setup.
>>>
>>> I would need more context than that, but you could get the FQDN of a deploying machine in the preseeds context (i.e. node.fqdn()). That said, you could also do post_install configuration via preseeds.
>>>
>>> You could inject user_data on the deployment (if doing so via the API of course).
>>
>>
>> --
>> Maas-devel mailing list
>> Maas-devel at lists.ubuntu.com <mailto:Maas-devel at lists.ubuntu.com>
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel <https://lists.ubuntu.com/mailman/listinfo/maas-devel>
>>
>>
>> Hope that helps.
>>
>> Thanks,
>> Blake Rouse
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20170208/93e59c51/attachment.html>
More information about the Maas-devel
mailing list