On 11/10/2015 08:34 PM, Martin Zobel-Helas wrote:
> Microsoft would like to use the Debian name and logo to promote those
> Debian images in the Azure Marketplace.[6] credativ will maintain and
> enhance those Debian images and Debian developers at credativ will
> accompany this process.
FYI, thi
g said, I'd love to have our release team be more liberal on
updates of cloud stuff. Cloud-init for example, has an open bug for
MONTHS which we are stuck on.
Cheers,
Thomas Goirand (zigo)
ybe stable + some
backports would be ok...).
Cheers,
Thomas Goirand (zigo)
images. But could Microsoft
design some kind of the same process, which would trigger an upload? I
don't think writing such a REST API server is hard, and it could be just
a hack on a VM which would then download from cdimages.d.o and upload to
Azure.
Your thoughts everyone?
Cheers,
Thomas Goirand (zigo)
On 11/12/2015 04:06 PM, Marco d'Itri wrote:
> On Nov 12, Thomas Goirand wrote:
>
>> changes, isn't a point of argumentation (see my previous mail). All of
>> the packages must be taken from stable, unchanged, and if some are taken
>> from backports, this must be
On 11/12/2015 04:52 PM, kuLa wrote:
> On 2015-11-12 15:58:03, Thomas Goirand wrote:
>> As per the discussions during debconf, to be called "official", the
>> images have to be built:
>> - directly from an unmodified stable
>> - with reproducibility on any
(it's IMO a distraction of very low importance).
Cheers,
Thomas Goirand (zigo)
On 11/12/2015 07:58 PM, Bastian Blank wrote:
> On Thu, Nov 12, 2015 at 03:58:03PM +0100, Thomas Goirand wrote:
>> As per the discussions during debconf, to be called "official",
>
> And the rules for "unofficial" would be? At least I can't remember
&
On 11/13/2015 12:16 PM, Marco d'Itri wrote:
> On Nov 12, Thomas Goirand wrote:
>
>>>> changes, isn't a point of argumentation (see my previous mail). All of
>>>> the packages must be taken from stable, unchanged, and if some are taken
>>>>
On 11/15/2015 06:50 PM, Wouter Verhelst wrote:
> On Thu, Nov 12, 2015 at 09:04:29PM +0100, Thomas Goirand wrote:
>> On 11/12/2015 04:52 PM, kuLa wrote:
>>> On 2015-11-12 15:58:03, Thomas Goirand wrote:
>>>> As per the discussions during debconf, to be called "of
On 11/15/2015 11:41 PM, Wouter Verhelst wrote:
> On Sun, Nov 15, 2015 at 11:28:57PM +0100, Thomas Goirand wrote:
>> On 11/15/2015 06:50 PM, Wouter Verhelst wrote:
>>> On Thu, Nov 12, 2015 at 09:04:29PM +0100, Thomas Goirand wrote:
>>>> On 11/12/2015 04:52 PM, kuLa wr
On 11/21/2015 04:17 PM, Marcin Kulisz wrote:
> On 2015-11-15 18:50:45, Wouter Verhelst wrote:
>> On Thu, Nov 12, 2015 at 09:04:29PM +0100, Thomas Goirand wrote:
>>> On 11/12/2015 04:52 PM, kuLa wrote:
>>>> On 2015-11-12 15:58:03, Thomas Goirand wrote:
>>>&
On 11/23/2015 01:28 AM, Steve McIntyre wrote:
> [ Apologies for delayed responses - massively busy in the last week
> ... ]
No worries, and no hurry. :)
> On Thu, Nov 12, 2015 at 10:04:19PM +0100, Thomas Goirand wrote:
>> On 11/12/2015 07:58 PM, Bastian Blank wrote:
>>
On 11/25/2015 04:06 PM, Charles Plessy wrote:
> Le Thu, Nov 12, 2015 at 04:01:50PM +0100, Thomas Goirand a écrit :
>>
>> Unfortunately, "driven by technological necessity", or the size of
>> changes, isn't a point of argumentation (see my previous mail). All o
est extensively.
Your thoughts? Is there anything we could do with other types of cloud
in an automated way?
Cheers,
Thomas Goirand (zigo)
cloud-init?
Cheers,
Thomas Goirand (zigo)
explicitely selected. Does somebody know if this has already been discussed
> somewhere ?
I'd also would like this feature to be added to APT (with a possible
option for it).
Cheers,
Thomas Goirand (zigo)
tly uses the Cirros image, because it's smaller (a few megs),
so it's faster to test OpenStack. In the context of testing the Debian
image, I could switch to the Debian image: it's only 1 or 2 lines to
change, as this was what I was doing to begin with.
Cheers,
Thomas Goirand (zigo)
diskimage-builder, which really, does a lot (really a lot) and is
really modular. If there's one tool to work on so it becomes *the*
generalist solution, then it's that one.
Cheers,
Thomas Goirand (zigo)
s a slightly patched version of zigo's OpenStack image
> builder script.
Despite asking multiple times, I haven't seen the patch. Could you
please publish it somewhere?
Cheers,
Thomas Goirand (zigo)
we
stop caring for oldstable, which is anyway EOL (well, LTS...).
As Steve re-added generation of the weekly testing images for OpenStack,
hopefully next week, we'll see new official images using Grub and Ext4.
Hoping these changes will please everyone,
Cheers,
Thomas Goirand (zigo)
o attend remotely, for example with hangout or
this kind of thing? Even if it was very late for me, I wouldn't mind. I
would also suggest that we prepare everything and start discussion here
on the mailing lists.
Cheers,
Thomas Goirand (zigo)
On 08/12/2016 10:10 AM, Thomas Goirand wrote:
> Hi,
>
> As the maintainer of OpenStack in Debian, and the person maintaining the
> official Debian image for OpenStack available from cdimage.debian.org,
> I'd be interested to join. However, both the timing (ie: right after th
c to bikeshed about tooling. If it
was, then we'd be much better to discuss it over the lists first.
Cheers,
Thomas Goirand (zigo)
buntu was (or still is?) using
live-build for its official images.
> Do EC2 eimages really need to be built in an EBS volume? Would it be
> good enough to copy them there after, building in a loop file like
> everything else until that moment?
Well, it's been about a year I'm asking that someone tests the openstack
images on EC2:
http://cdimage.debian.org/cdimage/openstack/
IMO, they should "just work" out of the box. The jessie one though
should only work on HVM though.
Could someone really take the time to test?
Cheers,
Thomas Goirand (zigo)
On 08/16/2016 09:19 PM, Sam Hartman wrote:
> For me, my concerns are:
>
> 1) I think involving d-i is the wrong approach for building images.
>
> 2) For me, the lack of shared libraries in Go is a deal-killer for
> infrastructure tools I'm going to depend on.
I very much agree with all of the abo
On 08/19/2016 03:02 AM, Adam Bolte wrote:
> On Wed, Aug 17, 2016 at 11:19:42AM +0200, Thomas Goirand wrote:
>> I'm however surprised that in your review, you didn't take into account:
>> - openstack-debian-images (currently the only tool which is officially
>&g
On 08/22/2016 01:29 PM, Adam Bolte wrote:
> On 22/08/16 18:49, Thomas Goirand wrote:
>> On 08/19/2016 03:02 AM, Adam Bolte wrote:
>>> I continue to use and maintain debian-image-builder (over at
>>> https://github.com/sitepoint/debian-image-builder) which is somewhat
&
and
report success or failure.
I'd like to hereby thanks Steve for his support and continuous work.
He's been just great.
Hoping this work will please all Debian users on the cloud,
Cheers,
Thomas Goirand (zigo)
> report success or failure.
>
> I honestly wasn't aware that I can run arm64 on AWS if this is the case I have
> some reading to do (any pointers appreciated).
That's not what I wrote (or did I?). You can test the *amd64* image from
this URL:
http://cdimage.debian.org/cdimage/openstack/
Cheers,
Thomas Goirand (zigo)
anymore (let's not go into details why this happened), Steve does it at
the same time as other Debian images. It's now included in a single
process of building images.
Cheers,
Thomas Goirand (zigo)
"to go into details".
> This type of thing keeps people in the dark and that is something I do
> not support. There is no need to go over all the details but at least
> provide proof as I have done.
>
> On 5 July 2017 at 08:34, Thomas Goirand <mailto:tho...@goirand
you could integrate the image-test script run within
the image build process? I'm particularly interested in having it
integrated in the Debian testing image, so we make sure there's no
regression.
Cheers,
Thomas Goirand (zigo)
On 12/11/2017 07:01 PM, Steve McIntyre wrote:
> On Sun, Dec 10, 2017 at 06:34:32PM +0100, Thomas Goirand wrote:
>> Hi Steve and everyone else,
>>
>> This was overdue, but here it is.
>>
>> In Casulana, under /home/cloud-build/hack/zigo2, you'll find a script
roxy Node │
>
>
Oh, that's just great! Thanks for doing this.
I've attached the diff for adding OpenStack tasks. As you can see, it's
simply using the meta packages that we have already.
Cheers,
Thomas Goirand (zigo)
rary, discussing the tasks themselves
is helpful, because they are easy to modify.
I'm sure someone will reply to this thread with more nice ideas to
improve it even more.
Cheers,
Thomas Goirand (zigo)
[1] https://lists.debian.org/debian-boot/2014/09/msg00206.html
[2] https://wiki.
On 09/09/2014 06:21 AM, Paul Wise wrote:
> On Mon, Sep 8, 2014 at 11:15 PM, Thomas Goirand wrote:
>
>>
>> It's looking like some of the options are confusing for both advanced
>> users and newbies. The technologies behind the tasks are hidden, and
>> there
37 matches
Mail list logo
