Hi Christoph, I just sent a PR which adds desired functionality for the stork driver. I already built docker images and pushed it to Kube-Linstor project. Stork scheduler is working as a charm.
Thanks a lot for such cool opportunity! On Mon, May 18, 2020, 09:36 kvaps <[email protected]> wrote: > Hi Christoph, > > > You are using Pireaus operator to deploy LINSTOR, right? > > No we're using https://github.com/kvaps/kube-linstor and I'm going to add > support of your stork plugin for that. > > I'm little skeptical about using operator approach for anything else > besides configuration or managing difficult application lifecycle :) > Instead, I like when application can be simple deployed by simple > templated manifests. Kubernetes already have all needed controllers for > managing it. > > > I'll think about how to solve this more generically. Thanks for the > report. > > I'm sure that adding support for the same environment variables like for > linstor-csi is the easiest and better way, ideally I'd like to have: > > env: > - name: LINSTOR_IP > value: https://linstor-controller:3371 > - name: LS_USER_CERTIFICATE > valueFrom: > secretKeyRef: > key: tls.crt > name: linstor-client-tls > - name: LS_USER_KEY > valueFrom: > secretKeyRef: > key: tls.key > name: linstor-client-tls > - name: LS_ROOT_CA > valueFrom: > secretKeyRef: > key: ca.crt > name: linstor-client-tls > > And of course do not hardcode driver with the piraeus-operator. it's > better to keep the things loosely coupled with each other, and components > replaceable. > > > the source code is available on GitHub, though it is somewhat hidden (in > a branch of our fork of Stork): > https://github.com/LINBIT/stork/tree/linstor-driver > > Got it! Sorry, this branch had no these changes at this weekend :) > > Best Regards, > Andrei Kvapil > > > On Mon, May 18, 2020 at 7:59 AM Christoph Böhmwalder < > [email protected]> wrote: > >> On 16.05.20 23:57, kvaps wrote: >> > Hi, I'm trying to deploy stork driver using official documentation. But >> it is >> > not starting due wrong controller endpoint name: >> > >> > time="2020-05-16T21:16:31Z" level=info msg="called: Init()" >> > time="2020-05-16T21:16:31Z" level=error msg="Error init'ing linstor >> driver: >> > error getting linstor endpoint: endpoints \"linstor-op-cs\" not found" >> > time="2020-05-16T21:16:31Z" level=info msg="Starting stork version >> 2.4.0-cba53f4c" >> > time="2020-05-16T21:16:31Z" level=info msg="Using driver linstor" >> > time="2020-05-16T21:16:31Z" level=fatal msg="Error getting Stork Driver >> linstor: >> > VolumeDriver with UID/Name: linstor not found" >> > >> > I can't find any configuration options, also I can't find any source >> code to >> > check it out. >> > >> > I've tried to assign similar variables like for csi-driver (LINSTOR_IP, >> > LS_USER_CERTIFICATE, LS_USER_KEY and LS_ROOT_CA), also try to create >> service >> > with `linstor-op-cs` name, but all my attempts to start the driver were >> even. >> > >> > - kvaps >> > >> > _______________________________________________ >> > Star us on GITHUB: https://github.com/LINBIT >> > drbd-user mailing list >> > [email protected] >> > https://lists.linbit.com/mailman/listinfo/drbd-user >> > >> >> Hi, >> >> You are using Pireaus operator to deploy LINSTOR, right? >> In that case hard coding "linstor-op-cs" was probably too naive (LINSTOR >> operator is our "enterprise support" version of Piraeus operator, so that >> is >> what we primarily test with). >> >> I'll think about how to solve this more generically. Thanks for the >> report. >> >> PS: the source code is available on GitHub, though it is somewhat hidden >> (in a >> branch of our fork of Stork): >> https://github.com/LINBIT/stork/tree/linstor-driver >> >> -- >> Christoph Böhmwalder >> LINBIT | Keeping the Digital World Running >> DRBD HA — Disaster Recovery — Software defined Storage >> >
_______________________________________________ Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list [email protected] https://lists.linbit.com/mailman/listinfo/drbd-user
