Due to MAAS image names

Blake Rouse blake.rouse at canonical.com
Fri Nov 4 13:45:38 UTC 2016


You can upload those images as custom images.

maas {session} boot-resources create name=custom/win2016 title="Windows
Server 2016" content@=/path/to/image architecture=amd64/generic
filetype=ddtgz


On Fri, Nov 4, 2016 at 7:43 AM, Artūras Ražinskij <
arturasr at balticservers.com> wrote:

> Hello,
>
> I need a bit of help, or at least clarifying of situation. I’m using MAAS
> for deploying Windows images, but as I understand the names of images are
> hardcoded, so I can legally have only two names: Windows "Hyper-V Server
> 2012 R2 and Windows "Hyper-V Server 2012. But I also have build Windows
> server 2008 and Windows Server 2016 which are also works fine for me.
>
> So my question is what names should I use for those images so they will be
> available and usable for deploys.
>
> As of now, if I need windows server 2016 i’m naming it as Windows "Hyper-V
> Server 2012 R2.
>
> Or perhaps can you hardcode more valid names for Windows?
>
> Thank you.
>
>
>> Regards
> Artūras Ražinskij
>
>
>
>
>
>
> --
> 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/20161104/0d626126/attachment.html>


More information about the Maas-devel mailing list