Yes,the log content is the output from my condor job.
I run the job on the worker machine in my condor pool.
if i run the script in my worker machine manually. the scipt work ok and the dir /data mount to /dev/vdb success.
but if i run the script on the worker machine in the condor pool, the dir /data mount to /dev/vdb fail.
------------------------------------------------------------------
åääïhtcondor-users-request <htcondor-users-request@xxxxxxxxxxx>
åéæéï2019å5æ22æ(ææä) 07:01
æääïhtcondor-users <htcondor-users@xxxxxxxxxxx>
äãéïHTCondor-users Digest, Vol 66, Issue 53
Send HTCondor-users mailing list submissions to
htcondor-users@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
or, via email, send a message with subject or body 'help' to
htcondor-users-request@xxxxxxxxxxx
You can reach the person managing the list at
htcondor-users-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of HTCondor-users digest..."
Today's Topics:
1. Re: condor mount disk problem in shell script (Jason Patton)
2. Re: Linux Containers to consider with HTCondor in the near
future? (Oliver Freyermuth)
----------------------------------------------------------------------
Message: 1
Date: Tue, 21 May 2019 21:43:12 +0000
From: Jason Patton <jpatton@xxxxxxxxxxx>
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] condor mount disk problem in shell
script
Message-ID:
<CAFyOkSUVHk1QHJD2oRtAT=-hTA3iJeBhQjoXXNzYzeEVkLGygw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
To be clear, the log content is the output from your condor job?
Is this condor job running on your local machine or do you have other machines in your condor pool?
Jason Patton
On Tue, May 21, 2019 at 3:35 AM ?? <kan.wu@xxxxxxxxxxxxx<mailto:kan.wu@xxxxxxxxxxxxx>> wrote:
my shell script is:
sudo mkfs.ext4 /dev/vdb
if [ $? == 0 ]; then
echo "format /dev/vdb success"
else
echo "format /dev/vdb fail"
fi
out_dir=/data
sudo mkdir -p $out_dir
sudo mount /dev/vdb $out_dir
if [ $? == 0 ]; then
echo "mount /dev/vdb to /data success"
else
echo "mount /dev/vdb to /data fail"
fi
sudo chown wukan:wukan $out_dir
echo "..........." >> /data/test.txt
if [ ! -f /data/test.txt ]; then
echo "/data/test.txt file is not exist"
else
echo "/data/test.txt file is exist"
fi
when i run this script in condor worker machine in condor system.
the statement "sudo mount /dev/vdb $out_dir" does not work yet.
when i execute command "df -h"
the dir /data does not mount to /dev/vdb success.
but the log say it work ok.
the log content is:
Creating filesystem with 131072000 4k blocks and 32768000 inodes
Filesystem UUID: 441915d2-ab78-4258-8f76-f90c7c3a1a3f
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
format /dev/vdb success
mount /dev/vdb to /data success
/data/test.txt file is exist
What's the problem may be? but when i run this script outside of the condor system.
the script work ok.and the dir /data mount to /dev/vdb success.
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx<mailto:htcondor-users-request@xxxxxxxxxxx> with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www-auth.cs.wisc.edu/lists/htcondor-users/attachments/20190521/db38487e/attachment.html>
------------------------------
Message: 2
Date: Wed, 22 May 2019 01:00:14 +0200
From: Oliver Freyermuth <freyermuth@xxxxxxxxxxxxxxxxxx>
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Linux Containers to consider with
HTCondor in the near future?
Message-ID: <2084312e-c5d6-1dd3-9889-882ef781b1fe@xxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
Dear Brian,
Am 17.05.19 um 14:50 schrieb Bockelman, Brian:
> Hi Max,
>
> I find it better if users "tell HTCondor what they need, not how to do it".
I don't think this is what Max meant - at least it's not what I was asking for when I asked for OCI support ;-).
>
> That is, the users are better served if they are asked to put in a submit file line like:
>
> +RequiredOS = "rhel7"
That's (almost) exactly what we are using right now with Singularity. My question for OCI support was _not_ for a new universe, but I was asking for having HTCondor support OCI "behind the scenes"
to allow for a more free choice of the container runtime. That means that I (as administrator) would love to select a different implementation without the users seeing anything of that -
exactly what you suggest :-).
So what's "bad" about Singularity and Docker, and why would I love to use something else? Of course, that really depends on your usecase.
From my point of view, there are four main issues with Singularty:
- Interactive jobs only work with a hack in 8.6, and don't really work yet in 8.8 - but Greg's on it, so that's (hopefully) a temporary thing.
In my opinion, though, if you require interactive jobs, things are still not in reasonably good shape just yet for Singularity.
And with the "users should choose what they need" approach, which I also love, you definitely _need_ interactive jobs
to give the users the environment they ask for - for interactive development, testing, and to have the very same environment their batch job will see.
- The rate at which CVEs appear is still pretty high. That's expected, the project is still young - and the developer community
is (still, even with Sylabs!) small as compared to other full-fledged off-the-shelf solutions.
- There are still breaking changes introduced - regularly.
- There's no distro-maintained version of any recent release available yet (and following discussion on distro bug trackers, it's clear there are reasons for that,
and they don't speak for good quality of upstream's code).
What are the issues with Docker?
Of course, the "Docker universe" may be seen as an issue, since it's indeed not having the users tell HTCondor "what they need", but rather "how to do it".
But this could be hidden from the users.
My main issues with Docker are:
- Daemon running as root (but CVEs have become really rare, so maybe I am just too anxious / conservative here).
- The way images are stored does not fit our usecase very well.
- The overhead is a bit heavy by default (network virtualisation really kills MPI performance by design, etc.).
All these things are reasons why Singularity, Charliecloud, runc, podman and more were born.
So why am I asking for OCI?
There are mainly two, strong reasons:
- Freedom of choice of implementation!
I'd love to be able to use runc / podman. It's shipped with RHEL 8 and will surely receive good support by them - if RedHat does take care of something,
they do it with a lot of manpower. They even have CRIU integration,
and while that might now work perfectly well, it's still better than nothing (just look at https://github.com/sylabs/singularity/issues/468 which is over 2 years old).
I'd love to use these with user namespace support, of course.
- Hopefully, less work for the HTCondor developers, since there can (hopefully) be a common implementation on the HTCondor end for most (all?) OCI implementations,
maybe with a few quirks / knobs to be tweaked for each runtime implementation, but not one implementation in HTCondor for each single container runtime as it is done right now.
I strongly believe the HTCondor devs agree with my last point. That was also why https://github.com/htcondor/htcondor/pull/18 was closed - after discussion with Greg, I agreed that adding
another container implementation (even one that's hidden from the user!) is a maintenance burden which is not really worth it. It's better to have the HTCondor devs invest their energy
in developing OCI support in the future.
I hope this explains it and you have made it through my long mail ;-).
Cheers and all the best,
Oliver
>
> (what they need!) as opposed to asking them to learn the Docker universe:
>
> universe = docker
> docker_image = myrepo:custom_centos7
>
> (how to do it!)
>
> This way, you have some ability to decide on switching the implementation later without having to worry about asking users to change their submit files.
>
> That said, both Singularity and Docker support are in reasonably good shape. I happen to use both, depending on the application.
>
> Brian
>
>> On May 17, 2019, at 4:48 AM, Fischer, Max (SCC) <max.fischer@xxxxxxx> wrote:
>>
>> Hi all,
>>
>> we are currently transitioning out HTC farm from RHEL6 to RHEL7. As we should probably have expected, every VO/user realises in the last minute that they are *not* quite ready to make the transition. So for our next revision, we would like to add containerisation to have per-VO/user environments.
>>
>> What are our options to consider for container with HTCondor in the near/medium future? Say about a year from now on?
>> We've already used HTC with both docker and singularity; each had it quirks to which we would like not to lock us in on. I've seen that Oliver asked for OCI support about a year ago, but I cannot find any current information on this.
>>
>> Cheers,
>> Max
>>
>> _______________________________________________
>> HTCondor-users mailing list
>> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
>> subject: Unsubscribe
>> You can also unsubscribe by visiting
>> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>>
>> The archives can be found at:
>> https://lists.cs.wisc.edu/archive/htcondor-users/
>
>
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/
>
--
Oliver Freyermuth
Universit?t Bonn
Physikalisches Institut, Raum 1.047
Nu?allee 12
53115 Bonn
--
Tel.: +49 228 73 2367
Fax: +49 228 73 7869
--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5432 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www-auth.cs.wisc.edu/lists/htcondor-users/attachments/20190522/de00651d/attachment.p7s>
------------------------------
Subject: Digest Footer
_______________________________________________
HTCondor-users mailing list
HTCondor-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
------------------------------
End of HTCondor-users Digest, Vol 66, Issue 53
**********************************************
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}