| Centurion_Dan | I've been looking into the AWS situation.. they provide tools that can be used to completely offline create AMIs that can then be uploaded and registered. But they're tools are licensed with the "Amazon Software License" which is pretty much open source friendly with the exception of one little clause: | 11:22 |
|---|---|---|
| Centurion_Dan | "3.3 Use Limitation. The Work and any derivative works thereof only may be used | 11:22 |
| Centurion_Dan | or intended for use with the web services, computing platforms or applications | 11:22 |
| Centurion_Dan | provided by Amazon.com, Inc. or its affiliates, including Amazon Web Services | 11:22 |
| Centurion_Dan | LLC." | 11:22 |
| Centurion_Dan | This violates the spirit of the DFSG, and thus means it can't go in main - but should be ok for non-free.. | 11:23 |
| Centurion_Dan | License can be found here: https://aws.amazon.com/asl/ | 11:25 |
| KatolaZ | it's pretty bad as a clause :\ | 11:25 |
| Centurion_Dan | yeah... but doesn't prevent it from being redistributed... | 11:28 |
| Centurion_Dan | It's either that or hacking up a tool that produces compliant images without using their tools... | 11:29 |
| Centurion_Dan | more work.... | 11:29 |
| KatolaZ | or not including their tools :) | 11:29 |
| Centurion_Dan | need them to create the AMI's offline - which would be a big improvement on the way bootstrap-vz does it - which requires spinning up an AWS instance to create the AMI. | 11:33 |
| Centurion_Dan | my intention is to eventually be able to build them in a normal ci job and give it a special repo job to upload them and set them up in the AWS marketplace as community images. | 11:35 |
| rrq | are you talking about something else than "importing a VM image"? https://docs.aws.amazon.com/vm-import/latest/userguide/vmimport-image-import.html#import-image-prereqs | 11:52 |
| Centurion_Dan | yes - bootstrapping an image from scratch using bootstrap-vz entirely offline and the uploading it and registering it on the marketplace as an automated process - hopefully run as a normal(ish) ci job. | 11:58 |
| rrq | the "import" page suggest you can import a "raw disk" as an AMI, via S3, using some "aws" commands. It says nothing about particulars of the disk though. | 12:03 |
| Centurion_Dan | rrq - the idea being in a position to have devuan up on AWS with regularly updated consistently built images. Eventually I hope we can do the same for Azure and Google cloud too.. | 12:04 |
| * Centurion_Dan swallows back a bit of vommit at the thought | 12:05 | |
| Centurion_Dan | ;-) | 12:05 |
| Centurion_Dan | rrq: you may be able to do that but this way we could control the AMI conversion process too - there is some metadata and other tweaks to do.. | 12:07 |
| Centurion_Dan | the AMI toolkit provides a tool that does all this directly for "loopback" created images with a couple of flags... | 12:09 |
| rrq | yeah, I was just looking dreamily at the console switches :) | 12:11 |
| rrq | though you'd like the image building process eventually to be variable wrt target "instantiation platform" | 12:14 |
| rrq | I suppose, it all depends on how much tailoring of the image(s) is/are needed to fit the particular platform | 12:20 |
| rrq | I must admit I've never worried at all about the "hardware" details of my AWS machines, except for tha abstract balancing of performance needs versus price. | 12:24 |
| rrq | my = "my" | 12:26 |
| telmich | good evening | 20:05 |
| telmich | I was wondering what is the status of devuanconf and if there is any communication medium that I can join for planning? | 20:05 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!