Status update: Nicolas has submitted the CSR(s), waiting for DigiCert to ack.

this will go into the current webui, as the first endpoint that returns json stuff instead of rendering an html page

current status: about 1/3 done (by the look of it…)

This is now done. Some details:

done at https://intranet.softwareheritage.org/index.php/Phabricator_callsign_naming_convention

And apache through to rSPPROFa11a325c.

uWSGI has been deployed through rSPPROFb76ea39d4

• Runs in ~53s
• Checks everything got in

done in rDSTO793fb06f89d27c6ed94ab9392594dab14a941e3f

Final quotation obtained from Dell, and forwarded to Anna for placing the order.

chmods restarted in a scren session of root@uffizi

"create index concurrently ..." is now running on prado, in a screen section

committed rDSTO672dd1c as mkstemp creates files with mode 0o600

chmods interrupted, as we just discovered that uwsgi is currently creating object files with perms 0600, which are not the right ones.
We need to first fix that, and then restart the chmods.

current status: 16 chmods (one for each physical disk) are currently running on uffizi, in a screen session of user root

The systemd service file has been added, but it doesn't go well with the other phabricator daemons that are running...

Those repositories have been rescheduled with the rest of the 13 million repos that hadn't been imported yet.

Just pinged the Dell commercial. I've been waiting for 1 week now for a quotation from him.

In progress.

The tasks are currently running.

Added another setting "notification.types" : ["task", "cmit"]

Added a setting "notifications.verbosity" in the bot config file. The default disabled notifications...

We can configure "application emails" to route inbound email to phabricator applications. We can then use Herald rules to route those addresses properly.

Pending DNS propagation, this should be done.

done in rSPPFIX840582c1d52c and rSPPFIXf97729a999d3

swh's puppet state of art - https://forge.softwareheritage.org/diffusion/SENV/

• Inject content
• Inject directories
• Inject revision
• Inject release
• Inject occurrence
• Add tests on lower level
• Tag + Release + Install to make sure the packaging is ok
• pep8 compliance + tests ok
• Orchestration test

In light of issues like T78 , the ideal test based on "git cloning" from SWH would include both:

• verifying that the top-most commits have the right sha1_git checksum, and
• verifying that the Git object store contains all and only the objects we started with

Done in rDLDG61e2b1ecd061

Status update: after a couple of round of discussions with dell commercial and pre-sale engineers, they now get what we need.
We're now waiting on them to send us a proper quotation.