| === zz_CyberJacob is now known as CyberJacob | ||
| === CyberJacob is now known as zz_CyberJacob | ||
| === zz_CyberJacob is now known as CyberJacob | ||
| === CyberJacob is now known as zz_CyberJacob | ||
| Smilie | Hi all! Quick question to community: is it possible to -deploy- node through MAAS CLI? | 08:14 |
|---|---|---|
| Smilie | or is it only possible to do it through GUI? | 08:14 |
| Smilie | is there a way to deploy (ready) node through CLI or API? | 08:43 |
| mup | Bug #1491947 changed: ARM64 and ARMhf nodes report only 1 core on systems with 2 - 8 cores <MAAS:Invalid> <https://launchpad.net/bugs/1491947> | 14:12 |
| mup | Bug #1491947 opened: ARM64 and ARMhf nodes report only 1 core on systems with 2 - 8 cores <MAAS:Invalid> <https://launchpad.net/bugs/1491947> | 14:18 |
| mup | Bug #1491947 changed: ARM64 and ARMhf nodes report only 1 core on systems with 2 - 8 cores <MAAS:Invalid> <https://launchpad.net/bugs/1491947> | 14:30 |
| mup | Bug #1499749 opened: Exception in bootresources.py prevents downloading boot pxe images <MAAS:Fix Committed> <MAAS 1.8:In Progress> <https://launchpad.net/bugs/1499749> | 14:34 |
| mup | Bug #1499749 changed: Exception in bootresources.py prevents downloading boot pxe images <MAAS:Fix Committed> <MAAS 1.8:In Progress> <https://launchpad.net/bugs/1499749> | 14:37 |
| mup | Bug #1499749 opened: Exception in bootresources.py prevents downloading boot pxe images <MAAS:Fix Committed> <MAAS 1.8:In Progress> <https://launchpad.net/bugs/1499749> | 14:43 |
| JZTech101 | uh | 14:46 |
| JZTech101 | http://vgy.me/e6YccL | 14:46 |
| JZTech101 | What do the different fields mean? | 14:46 |
| JZTech101 | o.O | 14:46 |
| JZTech101 | I have vmware workstation and I'm trying to understand the different fields | 14:46 |
| JZTech101 | Sep 25 11:01:17 layne maas.import-images: [WARNING] Finished importing boot images, the region does not have any boot images available. | 15:02 |
| JZTech101 | Sep 25 11:01:17 layne maas.tftp: [WARNING] No boot images have been imported from the region. | 15:02 |
| JZTech101 | uh how do I tell MaaS it IS the region controller? | 15:03 |
| JZTech101 | like I don't understand. | 15:03 |
| JZTech101 | I'm trying to tell the thing to get the images | 15:03 |
| JZTech101 | help? | 15:44 |
| alanmeadows | currently struggling on whether its possible to easily instruct a specific node to leverage a custom pxelinux.cfg for a maas node to allow maas (for certain hosts) to kick off a custom install (e.g. ESXi headless PXE install). In the past, I could override a generated 00-00-00... tftp file so at least these hosts could be inventoried and tracked in maas, | 17:30 |
| alanmeadows | but since this is all handled by a response from the API (pserv calls pxeconfig now?) I'm unsure whether there is a path forward | 17:30 |
| mup | Bug #1499820 opened: New storage/network options may be incompatible with other operating systems <networking> <storage> <MAAS:Triaged> <https://launchpad.net/bugs/1499820> | 18:01 |
| mup | Bug #1499869 opened: maas wily deployment to HP Proliant m400 fails <MAAS:New> <https://launchpad.net/bugs/1499869> | 20:07 |
| mup | Bug #1499869 changed: maas wily deployment to HP Proliant m400 fails <MAAS:New> <https://launchpad.net/bugs/1499869> | 20:13 |
| mup | Bug #1499869 opened: maas wily deployment to HP Proliant m400 fails <MAAS:New> <https://launchpad.net/bugs/1499869> | 20:16 |
| mup | Bug #1499869 changed: maas wily deployment to HP Proliant m400 fails <MAAS:New> <https://launchpad.net/bugs/1499869> | 20:19 |
| mup | Bug #1499869 opened: maas wily deployment to HP Proliant m400 fails <MAAS:New> <https://launchpad.net/bugs/1499869> | 20:28 |
| === zz_CyberJacob is now known as CyberJacob | ||
| mup | Bug #1499898 opened: Apache is optional now, so it should not be installed as Required by the maas deb packages <landscape> <MAAS:New> <https://launchpad.net/bugs/1499898> | 21:56 |
| === CyberJacob is now known as zz_CyberJacob | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!