<commit_before>Notes taken on 5th June in Warwick on Pete's cloud meeting.
Talking to <NAME> who works at Birmingham and is CLIMB affiliated.

To make a BL image from my standard VBox image:

1) Remove VirtualBox drivers
2) Add cloud-init
     Edit cloud.cfg to make the manager account
     cloud-init expects to create the account itself - can it be told not to?
     At least, lock the password for the account
     Or maybe just lock SSH?  Needs thought.
3) Disable plymouth and set verbose text boot
4) Turn off Network Manager, as you do on EOS Cloud
5) Convert VMDK to RAW using VBoxManage (see OpenStack docs) and discard the OVF stuff

Simon sent the following extra notes:

The avahi-autoipd, managed to get it clean off with apt-get purge instead
of remove, apparently the if-up.d script must have changed at some point?


To make the console and log work (/etc/default/grub):

GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200"


I still haven¹t got metadata service working properly, there¹s something
not quite right with my config maybe, it injected the ssh key into the
ubuntu user (and if I add that user to the ssh group I can then ssh in),
but I can¹t get it to do it into the manager user.

I will make a copy of my pack-for-esx and then adapt it for this system.

<commit_msg>After this commit, pack-for-climb will build off the ISO not the OVA.<commit_after>Update on 19/6:

I got this all working, but it's making a raw .img file of 100GB.  What I
really want is a 20GB image and for cloud-initramfs-growroot to work it's
magic.  I think it should work on CLIMB.  So I'm re-doing the build to
run off the ISO and build a 20GB system.

---

Notes taken on 5th June in Warwick on Pete's cloud meeting.
Talking to <NAME> who works at Birmingham and is CLIMB affiliated.

To make a BL image from my standard VBox image:

1) Remove VirtualBox drivers
2) Add cloud-init
     Edit cloud.cfg to make the manager account
     cloud-init expects to create the account itself - can it be told not to?
     At least, lock the password for the account
     Or maybe just lock SSH?  Needs thought.
3) Disable plymouth and set verbose text boot
4) Turn off Network Manager, as you do on EOS Cloud
5) Convert VMDK to RAW using VBoxManage (see OpenStack docs) and discard the OVF stuff

Simon sent the following extra notes:

The avahi-autoipd, managed to get it clean off with apt-get purge instead
of remove, apparently the if-up.d script must have changed at some point?


To make the console and log work (/etc/default/grub):

GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200"


I still havent got metadata service working properly, theres something
not quite right with my config maybe, it injected the ssh key into the
ubuntu user (and if I add that user to the ssh group I can then ssh in),
but I can¹t get it to do it into the manager user.

I will make a copy of my pack-for-esx and then adapt it for this system.


{'fraction_non_alphanumeric': 0.045015005001667226, 'fraction_numerical': 0.012670890296765588, 'mean_word_length': 3.8076923076923075, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1081376', 'n_tokens_mistral': 927, 'n_tokens_neox': 858, 'n_words': 499}