Juju User JuJu has an internal user framework, which supports sharing of controllers and models. Using JuJu user feature, a sysadmin could separated users for controllers as in multiple clouds deployment or for users as in multiple systems deployment. Each juju user can have its own permissions at application, model, or controller layer. This separation of responsibilities allow multiple users to manage multiple infrastructures with a clear border of responsibilities.

Background Recently, I received a really interesting question from my customer. He found out in his file system two files (directories), which belong to an user that not in /etc/passwd. Specifically in Ubuntu Linux 18.04, these 2 files are /var/lib/private/systemd /var/lib/private/systemd/timesync These two files belong to a user named systemd-timesync with UID/GID in 62583 and this user does not belong to /etc/passwd. Traditionally, a Linux user does not always need to be in /etc/passwd because it can come from many remote sources, for example

Developer Summit one of the biggest developer gathering in Japan, where developer will gather in one day event with full of sessions to gain knowledge and experiences, as well as technology trends of current year. This season’s topic is “society in the expansion of data”. Full event timetable and speakers’ profiles could be confirmed at event homepage (https://event.shoeisha.jp/devsumi/20180727) This year, I’m honored to be one of the speaker at this event (https://event.