I have added the `--pull` option in the job configuration so the python image will always be pulled (if needed) during the build :
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 28 2020
Sep 27 2020
It seems the python 3.7 images on the jenkins master is quite old :
root@thyssen:~# docker images | grep python python 3.7 a4cc999cf2aa 16 months ago 929MB
Sep 25 2020
@olasd All the points we have checked yesterday should be addressed.
isolate the reverse_proxy configuration in a dedicated profile
- Use the archive module to install the tgz
- Declare missing dependencies to fix the initial puppet run
- Install dir is now read-only for the netbox user
- Restore the whitespaces on the cassandra configuration
Rebase
Sep 24 2020
- add apache and redis configurations
- Use the swh forge's redis repository
- use role::swh_server as base roleto activate the backup
Add the properties for netbox on vagrant
Sep 23 2020
- declare site.pp to override the default puppet entrypoint
- add the inventory vm
Sep 22 2020
The configuration is now managed by puppet.
Update the base image to use ethX interfaces
- fix hiera configuration in the context of vagrant
- fix vms network configuration
Sep 21 2020
Remove useless comment
remove useless properties
Remove unecessary comments
I don't know what's the current state of the diff is (I see quite a lot of commented code, don't know if you want to merge it like this or not, e.g. Vagrantfile).
I just discover there is still an issue with the network interfaces not configured after a restart of a vm. IMO we can wait for this problem to be solved before landing the diff.
Fix plenty of " :" ;)
The recurring visits looks good.
update the diff according the previous feedbacks :
- The logstash hosts are declared on a uniq property
- No more yaml templates ;)
- The profile::filbeat doesn't use parameters anymore
- Ensure the permissions are correctly set
- Add the purge option on the inputs.d directory
Sep 18 2020
Add vagrant configuration and documentation
Sep 17 2020
add vagrant usage documentation
prefix the preseed file by the debian version name
rebase
- lister's cache truncated :
swh-lister=> truncate gitea_repo; TRUNCATE TABLE swh-lister=> truncate launchpad_repo; TRUNCATE TABLE
- recurring task for full listing created :
- gitea
swhscheduler@saatchi:~$ swh scheduler --config-file /etc/softwareheritage/scheduler.yml task add list-gitea-full url=https://codeberg.org/api/v1/ limit=100 INFO:swh.core.config:Loading config file /etc/softwareheritage/scheduler.yml Created 1 tasks
- Task types registered on the scheduler :
swhscheduler@saatchi:~$ swh scheduler --config-file /etc/softwareheritage/scheduler.yml task-type register -p lister.launchpad INFO:swh.core.config:Loading config file /etc/softwareheritage/scheduler.yml INFO:swh.scheduler.cli.task_type:Loading entrypoint for plugin lister.launchpad swhscheduler@saatchi:~$ swh scheduler --config-file /etc/softwareheritage/scheduler.yml task-type register -p lister.gitea INFO:swh.core.config:Loading config file /etc/softwareheritage/scheduler.yml INFO:swh.scheduler.cli.task_type:Loading entrypoint for plugin lister.gitea
the iso is available on the public annex at this url : https://annex.softwareheritage.org/public/isos/virtualbox/debian/
In D3967#98011, @olasd wrote:In D3967#97981, @ardumont wrote:I think this should be moved to the sysadm-provisioning repository [1] instead.
[1] https://forge.softwareheritage.org/source/swh-sysadmin-provisioning/
No, I think a puppet-specific thing like this should definitely be in the puppet repository.
- initial gitea lister launched :
swhworker@worker02:~$ SWH_CONFIG_FILENAME=/etc/softwareheritage/lister.yml swh lister run --lister gitea --priority high url=https://codeberg.org/api/v1/ limit=100 ... INFO:root:listing repos starting at 1198 INFO:root:listing repos starting at 1199 INFO:root:listing repos starting at 1200 INFO:root:stopping after page 1200, no next link found
everything seems to work well, the production deployment will be done in T2608
- initial manual launchpad listing launched :
swhworker@worker02:~$ SWH_CONFIG_FILENAME=/etc/softwareheritage/lister.yml swh lister run --lister launchpad --priority high INFO:swh.core.config:Loading config file /etc/softwareheritage/lister.yml INFO:swh.core.config:Loading config file /etc/softwareheritage/global.ini INFO:swh.core.config:Loading config file /etc/softwareheritage/lister.yml
- schedult tak-types created:
swhscheduler@saatchi:~$ swh scheduler --config-file /etc/softwareheritage/scheduler.yml task-type register -p lister.gitea INFO:swh.core.config:Loading config file /etc/softwareheritage/scheduler.yml INFO:swh.scheduler.cli.task_type:Loading entrypoint for plugin lister.gitea INFO:swh.scheduler.cli.task_type:Create task type list-gitea-full in scheduler INFO:swh.scheduler.cli.task_type:Create task type list-gitea-incremental in scheduler swhscheduler@saatchi:~$ swh scheduler --config-file /etc/softwareheritage/scheduler.yml task-type register -p lister.launchpad INFO:swh.core.config:Loading config file /etc/softwareheritage/scheduler.yml INFO:swh.scheduler.cli.task_type:Loading entrypoint for plugin lister.launchpad INFO:swh.scheduler.cli.task_type:Create task type list-launchpad-full in scheduler INFO:swh.scheduler.cli.task_type:Create task type list-launchpad-incremental in scheduler INFO:swh.scheduler.cli.task_type:Create task type list-launchpad-new in scheduler
- user guest granted to access the new tables :
swh-lister=> grant select swh-lister-> on all tables in schema public swh-lister-> to guest; GRANT
- lister model updated from worker01:
swhworker@worker01:/etc/softwareheritage$ swh lister --db-url postgresql://*****@db.internal.softwareheritage.org:5432/swh-lister db-init INFO:swh.lister.cli:Loading lister bitbucket INFO:swh.lister.cli:Loading lister cgit INFO:swh.lister.cli:Loading lister cran INFO:swh.lister.cli:Loading lister debian INFO:swh.lister.cli:Loading lister gitea INFO:swh.lister.cli:Loading lister github INFO:swh.lister.cli:Loading lister gitlab INFO:swh.lister.cli:Loading lister gnu INFO:swh.lister.cli:Loading lister launchpad INFO:swh.lister.cli:Loading lister npm INFO:swh.lister.cli:Loading lister packagist INFO:swh.lister.cli:Loading lister phabricator INFO:swh.lister.cli:Loading lister pypi INFO:swh.lister.cli:Initializing database INFO:swh.lister.core.models:Creating tables INFO:swh.lister.cli:Calling init hook for debian
New version of the lister package deployed :
- on workers
root@pergamon:~# clush -b -w @swh-workers 'apt-get update; apt install -y python3-swh.lister' ... root@pergamon:~# clush -b -w @swh-workers "dpkg -l python3-swh.lister" --------------- worker[01-16] (16) --------------- Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==================-====================-============-================================================================= ii python3-swh.lister 0.1.4-1~swh1~bpo10+1 all Software Heritage Listers (bitbucket, git(lab|hub), pypi, etc...)
- on the scheduler :
root@saatchi:~# apt update && apt install python3-swh.lister ... Restarting services... systemctl restart gunicorn-swh-scheduler.service icinga2.service journalbeat.service postfix@-.service rabbitmq-server.service rpcbind.service ssh.service swh-scheduler-runner.service unbound.service
Actions :
- deploy the new version of the lister on each worker
- update the lister data model
- create the new task-type on the scheduler
- manually launch a listing to create high priority loading tasks for launchpad and gitea repository to ingest soon the repositories and not at the end of the current git queue
- truncate lister cache to allow the recurring loading tasks to be created
- schedule the recurring listing tasks for both repositories
Sep 16 2020
Use the capability of filebeat to use a file per input.
Sep 15 2020
The loading is in progress and seems ok
The loading task for guix is scheduled in production :
swhscheduler@saatchi:~$ swh scheduler --config-file /etc/softwareheritage/scheduler.yml task add load-nixguix url=https://guix.gnu.org/sources.json INFO:swh.core.config:Loading config file /etc/softwareheritage/scheduler.yml Created 1 tasks
The configuration was fixed on moma :
root@moma:/etc/filebeat# diff -U3 /tmp/filebeat.yml /etc/filebeat/filebeat.yml --- /tmp/filebeat.yml 2020-09-15 08:10:20.512838905 +0000 +++ /etc/filebeat/filebeat.yml 2020-09-15 08:16:13.096135043 +0000 @@ -1,4 +1,4 @@ -filebeat.prospectors: +filebeat.inputs: - type: log paths: - /var/log/apache2/archive.softwareheritage.org_non-ssl_access.log
and the logs since the last rotation correctly ingested :
Sep 14 2020
An email was sent on the swh-devel mailing list to ask for reviews.
The deployment in production will be performed in the middle of week 38 is no problems are raised.
An email was sent on the swh-devel mailing list to ask for reviews.
The deployment in production will be performed in the middle of week 38 is no problems are raised.
Sep 11 2020
Sep 10 2020
reopened to validate to complete process from the listing to the loading of some repository