which is it now? Tiamat / onedir / singlebin ?

Urs Rau

unread,

Aug 17, 2022, 11:07:26 AM8/17/22

to Salt-users

We are now well past the provisional release date and I still cannot see how to actually test the actual new onedir releases on Mac, linux centos, Debian and Ubuntu as well as on windows?

The obvious or more prominent links on saltproject.io still largely seem to point at either the old format or at downloads called singlebin?

And if we explore the browse directory link it gets very confusing very quickly as it is nested and the levels seem to contradict each other the deeper you go. Is this being maintained by hand? Doesn't;t see to be scripted or automated or refreshed in a timely manner?

I assume the answer to the subject question is supposed to be 'onedir' and not Tiamat or singlebin anymore, right?

But how do we actually test this in the RCs? Some of the URLs are scheduled to only become available after GA release and not during RC testing? What sort of plan is that?

What I am seeing in this release process and the utter lack of coordinate and clear information really scares and concerns me.

Not to mention that In all the testing I have done of tiamat and singlebin and onedir I have not seen a single one that did not have a number of errors that anyone should spot on first use?

And how are the distro packagers going to both give continuity of upgrade paths as well as distinction on how to add master or minion or cloud, or syndic or ssh or api parts etc, how will the logging setup or the system, launch daemons etc login to be setup right?

What is going on?

Sincerely,

Urs Rau

GH: TheBigBear

Anil Sharma

unread,

Aug 17, 2022, 2:06:30 PM8/17/22

to Salt-users

The salt core team will discuss this in tomorrow's open hour and also we'll do again detailed discussion about all the concerns raised in the open hour on 04 September.

https://outlook.office365.com/calendar/published/284d7da9ea784ea2...@vmware.com/f9fac9fdab1c4ce0b72f5149cb5008b115345329240750421486/calendar.html

Thanks, Anil

Dafydd Jones (techneg.it)

unread,

Aug 18, 2022, 9:54:20 AM8/18/22

to salt-...@googlegroups.com

I know there is a lot of confusion around at the moment but the method for installing release candidates hasn't changed for a couple of years.

They are at https://repo.saltproject.io/salt_rc/

Dafydd

--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/salt-users/1fcb9301-b78f-435e-bae8-e7c60d4f271an%40googlegroups.com.

Urs Rau

unread,

Aug 22, 2022, 2:49:22 PM8/22/22

to salt-...@googlegroups.com

Hi Dafydd,

Well yes, I thought it used to be pretty clear myself, but if you actually navigate this directory tree now it really manages to confuse me now no end. Why is windows on so many levels? Why are there singlebin dirs when it is all supposed to be onedir now?

And the web page that tells you how to install RCs is still out of date by two weeks or more. Still full of comments about Tiamat

https://docs.saltproject.io/en/master/topics/releases/releasecandidate.html

And if you forget about the old well known ‘salt_rc’ for a moment and use the ‘Directory Listing’ function of the repo site you get the following:

_includes/

bodger/

bootstrap/

css/

fonts/

grains/

images/

js/

osx/

pkgr/

py3/

salt-dev/

salt-singlebin/

salt/

salt_rc/

tests/

tiamat/

windows/

3001.html

3002.html

3003.html

403.html

index.html

And if you read the issue that was seeking to discuss the upcoming release and solve confusion which I cannot find gains sorry. it talks of a new ongoing parallel dir structure of old salt format and new salt onedir format ( actually at the time it was talking about Tiamat).

And said that while there are two releases the old classic and the new onedir one they would co-exist in parallel and have differing repo links.

But some of the links they talked about there are only going to be created once the RC has become GA and is released.

Makes me wonder how you are supposed to test the two formats for 3005 then?

Below is the content below the good old ’salt_rc’ dir that you pointed to, but even that is too many levels and still to this day contains a number of singlebin dirs?

https://repo.saltproject.io/salt_rc/. ( sorry this does not render or present itself well in emails )

..
salt/
../
onedir/
../
3005rc1-1/
3005rc1-2/
3005rc2-1/
latest/
repo.json
repo.mp

../
py3/
../
amazon/
debian/

../
redhat/
../
7/

../
8/
../
x86_64/
../
3005rc1/

../
3005rc2/
../
SRPMS/
repodata/
SALTSTACK-GPG-KEY.pub
salt-3005~rc2-1.el8.x86_64.rpm
salt-api-3005~rc2-1.el8.x86_64.rpm
salt-cloud-3005~rc2-1.el8.x86_64.rpm
salt-master-3005~rc2-1.el8.x86_64.rpm
salt-minion-3005~rc2-1.el8.x86_64.rpm
salt-ssh-3005~rc2-1.el8.x86_64.rpm
salt-syndic-3005~rc2-1.el8.x86_64.rpm


SRPMS/

../
latest/
../
SRPMS/
repodata/
SALTSTACK-GPG-KEY.pub
salt-3005~rc2-1.el8.x86_64.rpm
salt-api-3005~rc2-1.el8.x86_64.rpm
salt-cloud-3005~rc2-1.el8.x86_64.rpm
salt-master-3005~rc2-1.el8.x86_64.rpm
salt-minion-3005~rc2-1.el8.x86_64.rpm
salt-ssh-3005~rc2-1.el8.x86_64.rpm
salt-syndic-3005~rc2-1.el8.x86_64.rpm

minor/
repodata/
SALTSTACK-GPG-KEY.pub
salt-3005~rc1-1.el8.x86_64.rpm
salt-api-3005~rc1-1.el8.x86_64.rpm
salt-cloud-3005~rc1-1.el8.x86_64.rpm
salt-master-3005~rc1-1.el8.x86_64.rpm
salt-minion-3005~rc1-1.el8.x86_64.rpm
salt-ssh-3005~rc1-1.el8.x86_64.rpm
salt-syndic-3005~rc1-1.el8.x86_64.rpm

9/

ubuntu/

../
windows/
../
3005rc1-1/
3005rc1-2/
3005rc2-1/
../
salt-3005rc2-1-windows-amd64.exe
salt-3005rc2-1_BLAKE2B
salt-3005rc2-1_BLAKE2B.asc
salt-3005rc2-1_SHA3_512
salt-3005rc2-1_SHA3_512.asc
salt-3005rc2-1_SHA512
salt-3005rc2-1_SHA512.asc
salt-archive-keyring.gpg

latest/
repo.json
repo.mp

../
singlebin/
../
3005rc1-1/
3005rc1-2/

../
3005rc2-1/
../
salt-3005rc2-1-linux-amd64.tar.gz
salt-3005rc2-1_BLAKE2B
salt-3005rc2-1_BLAKE2B.asc
salt-3005rc2-1_SHA3_512
salt-3005rc2-1_SHA3_512.asc
salt-3005rc2-1_SHA512
salt-3005rc2-1_SHA512.asc
salt-archive-keyring.gpg

../
latest/
../
salt-3005rc2-1-linux-amd64.tar.gz
salt-3005rc2-1_BLAKE2B
salt-3005rc2-1_BLAKE2B.asc
salt-3005rc2-1_SHA3_512
salt-3005rc2-1_SHA3_512.asc
salt-3005rc2-1_SHA512
salt-3005rc2-1_SHA512.asc
salt-archive-keyring.gpg

repo.json
repo.mp

..
windows/
../
Salt-Minion-3005rc1-1-Py3-AMD64-Setup.exe.md5
Salt-Minion-3005rc1-1-Py3-AMD64-Setup.exe.sha256
Salt-Minion-3005rc1-1-Py3-AMD64.msi
Salt-Minion-3005rc1-1-Py3-AMD64.msi.md5
Salt-Minion-3005rc1-1-Py3-AMD64.msi.sha256
Salt-Minion-3005rc1-1-Py3-amd64-Setup.exe
Salt-Minion-3005rc1-1-Py3-x86-Setup.exe
Salt-Minion-3005rc1-1-Py3-x86-Setup.exe.md5
Salt-Minion-3005rc1-1-Py3-x86-Setup.exe.sha256
Salt-Minion-3005rc1-1-Py3-x86.msi
Salt-Minion-3005rc1-1-Py3-x86.msi.md5
Salt-Minion-3005rc1-1-Py3-x86.msi.sha256

Sorry, if this all comes across overly negative, that is not the intention at all. Just want to say that this process and communication could do with some improvments.

Regards,

TheBigBear

To view this discussion on the web visit https://groups.google.com/d/msgid/salt-users/CA%2BMg1C2V0fGE6WVv1OEDL7YBF6Lm%2BhVAsu3OL2MWegs0Aq%3Dpcw%40mail.gmail.com.

Urs Rau

unread,

Aug 22, 2022, 2:49:32 PM8/22/22

to salt-...@googlegroups.com

HI Dafydd,

I have just found another document that talks about the two parallel repo paths going forward. Here 3005.html

Why is the path for Macosx for Onedir vs the classic not-onedir pkgs swapped? Is it really intended to be that way or is that a mistake? And in terms of testing of RCs it is still not as clear as I’d like it to be which path under ’salt_rc’ is corresponding to the onedir format and which is corresponding the the classic non-onedir format?

Especially in the light of the closing comment on that repo sections where it says:

“Note that the onedir paths above will not be available until the day of the Phosphorus release."