Question about MAAS and KVM PXE

[Sean F.]

Hey wahi,

To access the deployed machine, go to the maas UI , select "settings" in
the upper right.

At the top you will see a section to add your ssh key. Make sure you do so,
you can either import a key via launchpad or add one from a local system.

After doing so, click back on your "nodes" tab and release & deploy the kvm
instance again. You should be able to ssh into the machine once it comes up
again.

To find what the IP is, simply click on your "networks" tab or you can
watch the VM console.

-sfeole

On Jul 21, 2017 4:18 AM, "wahi" <wahi at sci.am> wrote:

> Hi Mike,
>
> Actually Lloyd suggestion was rigth, the issue was from the iptables, I
> opened the 5240 port and it worked. The interesting question is, what is
> the default username and password for KVM PXE VM (Ubuntu 16.04)
>
>
> Best,
>
>  Wahi
>
> On 07/21/2017 10:58 AM, Mike Pontillo wrote:
>
> On Fri, Jul 21, 2017 at 7:36 AM, wahi <wahi at sci.am> wrote:
>
>> On 07/20/2017 10:56 PM, Lloyd Parkes wrote:
>>
>>> The error message indicates that the VM couldn’t download its bootstrap
>>> from the server using the TFTP protocol. The TFTP protocol isn’t used when
>>> installing from an ISO.
>>>
>>> I can think of two things to check.
>>>
>>> First of all, got to Nodes -> Controllers and select your rack
>>> controller. Then select the Services tab and check that there is a green
>>> tick next to the “tftp” item. If there isn’t a green tick, then you will
>>> have to search the MAAS logs under /var/log/maas/ for possible problems.
>>>
>>> Secondly, there is always the possibility of a firewall blocking tftp
>>> traffic. This could be on your server or on your network.
>>>
>>
> In addition to Lloyd's suggestions, you can try using this script for
> testing:
>
> https://git.launchpad.net/maas/tree/scripts/maas-test-enlistment
>
> If you run this script manually from the same network as the nodes are
> booting from (using the private IP address, 10.0.17.1, as the parameter)
> you should be able to check that the TFTP files are accessible and the
> cloud parameters are correct (that is, the MAAS metadata server that
> cloud-init will contact is reachable and providing correct metadata URLs
> for booting nodes).
>
> Regards,
> Mike
>
>
>
> --
> Maas-devel mailing list
> Maas-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/maas-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20170722/52bfbc73/attachment.html>