Makefile: Add subjects for storage and client wallets to FrostfsID #75
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-dev-env#75
Loading…
Reference in a new issue
No description provided.
Delete branch "aarifullin/frostfs-dev-env:feat/fidsubj_makefile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Signed-off-by: Airat Arifullin a.arifullin@yadro.com
79952e82e0
to4b55eb102e
@ -87,2 +92,3 @@
done
@echo "FrostFS sidechain environment is deployed"
@echo "Create frostfsid subject for ./wallets/wallet.json" \
&& subj_key=`neo-go wallet dump-keys -w ./wallets/wallet.json | head -2 | tail -1` \
We've got no
neo-go
in.vendor
. So, it assumes thatneo-go
is installed separately.Probably, this is not right for
frostfs-dev-env
bootupThe alternative way to get parsed script is:
(returns the same result)
WDYT?
FrostfID subject is required to create containers. Neo-go or Frostfs-storage should not to create containers. So their wallets are not required to be stored in FrostfsID contract.
Okay, I'll leave it only for client wallet. But the problem is that we need to get a subject key for this wallet
Fixed
@ -85,2 +85,4 @@
&& ./vendor/frostfs-adm -c frostfs-adm.yml morph refill-gas --storage-wallet $${f} --gas 10.0 \
|| die "Failed to transfer GAS to alphabet wallets"; \
echo "Create frostfsid subject for storage wallet $${f}" \
&& subj_key=`neo-go wallet dump-keys -w $${f} | head -2 | tail -1` \
I think storage nodes are ok not being in the frostfsid, we have user wallet for containers.
OK.
But still WDYT about
neo-go
?using neo-go is more robust than
jq + tail c+3
Got
neo-go
away, please, checkWhy, though? "robust" is a good thing.
Then neo-go should be vendored.
neo-go
binary in.env
along withto get it vendored
So, we need to upload it to somewhere. Once, we had a discussion and we didn't agree on uploading to
http.t5.fs.neo.org
(I may mistake)We already have a docker image for neo-go, right?
Can we use it?
That's really a brilliant idea. Fixed that
4b55eb102e
to28916ea278
28916ea278
toe3201f89d3
e3201f89d3
tod03be14312