Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixed user creation after deployment #18

Open
wants to merge 34 commits into
base: master
Choose a base branch
from
Open

Fixed user creation after deployment #18

wants to merge 34 commits into from

Conversation

cwiertniamichal
Copy link

No description provided.

@groundnuty
added volume-data-sync container to volume-webdav
f210239
@groundnuty
added missing volume-webdav targets to Makefile
f12947c
@groundnuty
added elasticsearch chart
a9ae68b
@groundnuty
disabled builtInDnsServer in onezone
c793aac
@groundnuty
fixed mising / in keycloak auth.conf iconPath
a9f73f9
@groundnuty
made oneprovider compatibile with alpha version, use global alpha fla…
e7270e3 
…g to enable
@groundnuty
improved debug message of cross-support-3 support job
600f44d
@groundnuty
removed empty name configuration form elasticsearch chart
50a45c0
@groundnuty
added additional node count control envs to configuration form elasti…
cea779c 
…csearch chart
@groundnuty
corrected a name of data import volume in webdav-volume chart
c174a8d
@groundnuty
WIP removed bad global data from webdav-volume chart
04e1db6
@groundnuty
fixed helm hooks in volume-nfs chart
f44f6ce
@groundnuty
fixed clean-up job of volume-nfs
8d1effe
@groundnuty
removed misplaced condition in oneclient chart
ef7796c
@groundnuty
proper mountpoits cleanup at termination in oneclient chart
3bc7923
@groundnuty
oneclient now waits with the mount for the oneprovider support
3003b86 
Before mounting a oneclient by a particular user to a particular provider a check is made if the particular provider actually supports any space own by this user. If not the entry point waits for a support to happen.
@groundnuty
cross-support-job no longer waits for oneclient pod to be ready
ca1a9d5 
Oneclient pod is ready when oneclient properly mounts, oneclient can mount after user spaces are get support. Oneclient readiness is not needed to properly initialize environment, hence this change is justified.
@groundnuty
fixed error in argument order in entrypoint of volume-ceph
5ad30af
@groundnuty
fixed CDMI_HOST env in onedata-cli
aaae03c
@groundnuty
added jupyter container to oneclient chart
9d2409d
@groundnuty
changed local pvc storageClassName of oneprovider and onezone
b3dbc21 
The storageClassName now is the same as default storageClassName of minikube
@groundnuty
fixed subPathExpr path of pvc volume in oneprovider and onezone
6392bc7
@groundnuty
in onezone and oneprovider in batch conf. changed how mainNode is picked
0057211
@groundnuty
made onezone auth.conf compatible with version 19.02.01
d93cf27
@groundnuty
in onezone and oneprovider made user creation compatible with 19.02
c5d6cb0 
a consequence of compatibility is new onepanel admin user, that will be a part of a deployment of both 18 and 19 versions. Onepanel rest calls now use this credentials instead of admin account of onezone
@groundnuty
onezone 19.02 compatibility for location of IDPs icons
40609ae
@groundnuty
in oneclient, improved the un-mounting procedure
38bb4ec 
now the oneclient pod will no longer hang in Termination state
@groundnuty
jupyter in oneclient wip
957d4b4
@groundnuty
jupyter notebook wip
06fd6b8
@groundnuty
fixed typos in oneclient
8447209
@groundnuty groundnuty force-pushed the master branch 4 times, most recently from 0432e88 to bd67697 Compare June 10, 2019 09:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@cwiertniamichal @groundnuty