[PKG-Openstack-devel] Status?

[Turbo Fredriksson]

On 14 Jul 2017, at 17:28, Thomas Goirand <zigo at debian.org> wrote:

> - PXE booted live system with a custom public ssh key to get in [1]
> - Reset on demand (through IPMI?)
> - Enough RAM (16, maybe 32 GB of RAM)
> - A small scratch disk for swift (100 GB should be enough)
> 
> [1] I do have the scripts to generate this PXE image, it's somewhere on
> Alioth in /git/openstack …

I have one to, if that’s of  any interest. It uses a pre-seed file which in
turn calls an initial install-setup script which in turn uses another bunch
of scripts to do the actually install of OS.

It sets up either a all-in control node OR a compute node (depending on
the hostname my DHCP server is providing to the host), using pre-seeding
to debconf, but also manual installations and modifications of files etc.

It takes less than an hour (from initial boot to finished “product”), and that’s
by copying/downloading packages from the official repos…

Using Puppet would have been much better, but because I’m replacing ALL
my infrastructure at home with a 16 node OS cluster, I’m facing a
chicken-and-egg problem :).


If we’re going to do automated testing (which in my opinion is an absolute
MUST before even uploading ANYTHING to the repos), we should have at
least two nodes to test this on - one control and one compute.

And my control node, running almost EVERYTHING, have 48GB memory,
which almost all of it is in use...

>>    I do not think that there's my way vs your way. I don't think anyone can
>>    even remotely contest the advantage of functional testing. The only
>>    issue is how, and if there's enough resources to do it.
>> 
>> As i sad: functional testing is nice, but not must-have.
> 
> Let's agree to not agree on the urgency, and just attempt to fix the
> current situation! :)

Personally, as a user, I rather have NO OS in Debian GNU/Linux than one
that can’t be guaranteed to work! OS is way, WAY to difficult and complicated
as it is to get working in it self, than to have to worry about “stuff” not being
tested or maybe not working [correctly].
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.alioth.debian.org/pipermail/openstack-devel/attachments/20170714/c1f63fd5/attachment.sig>