This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-22
Channels
- # announcements (11)
- # architecture (7)
- # babashka (26)
- # beginners (314)
- # calva (20)
- # chlorine-clover (1)
- # cider (5)
- # circleci (27)
- # clara (6)
- # clj-kondo (41)
- # cljsrn (6)
- # clojure (120)
- # clojure-berlin (2)
- # clojure-czech (2)
- # clojure-dev (4)
- # clojure-europe (45)
- # clojure-france (4)
- # clojure-germany (1)
- # clojure-nl (5)
- # clojure-uk (20)
- # clojuredesign-podcast (8)
- # clojurescript (6)
- # conjure (42)
- # datascript (5)
- # datomic (21)
- # deps-new (28)
- # duct (1)
- # fulcro (36)
- # graalvm (10)
- # graphql (24)
- # jackdaw (19)
- # jobs (2)
- # jobs-discuss (46)
- # kaocha (6)
- # malli (26)
- # off-topic (21)
- # parinfer (5)
- # re-frame (10)
- # sci (19)
- # shadow-cljs (95)
- # tools-deps (24)
- # vim (3)
I’m trying to launch a “Solo” Datomic Cloud CloudFormation stack. But it consistently fails with
CREATE_FAILED: Embedded stack arn:aws:cloudformation:blah:blah:stack/appname-StorageF7F305E7-S5WZ9NKP2OOE/ebc51350-fc61-11ea-9f8a-12709ad3d671 was not successfully created: The following resource(s) failed to create: [GetSystemName].
Is there anything basic I’m missing? Details are in this SO post.
https://stackoverflow.com/questions/64001410/stack-resource-fails-datomic-cloud-cloudformation-launchWe are running HAProxy to load balance peer requests. What do you recommend to stick our sessions to? Is SSL session ID a good idea?
We were looking for something along the lines of https://www.haproxy.com/blog/maintain-affinity-based-on-ssl-session-id/
This was many years ago, but I worked on a project that tried to use SSL session ids as a session id. We abandoned it pretty quickly. There was no guarantee that clients would even try to resume an SSL session. Some had built-in timers to reinitiate SSL sessions every n minutes where n was very small. I have no idea if things have changed, but I certainly wouldn't just do this without a lot of research first
I'm currently trying to follow the datomic ions tutorial, but after installing the datomic cli
tools I'm stuck:
Executing datomic system list-instances <system>
fails with AWS Error: Unable to fetch region.
.
The alternative command using the aws
cli directly, succeeds though. I've installed the aws cli via docker and made an alias. Could this be my problem?
Edit: Installed AWS CLI tools via docker and tried again with a normal installation of the V1 and V2 tools. But the problem remains.
Edit2: Okay nervermind. The old docker aws process was locking the .aws/credential file. With a standard aws cli V1 version everything runs fine now.
Yes it's all running now, thanks! My problem was the aws docker image blocking my entire ~/.aws
directory. So when i finally installed a regular V1 CLI it couldn't access the config files.
I have another question though, that got buried in #beginners.
I want to deploy a fulcro3 project with a dependency to libpython-clj
to datomic ions. It includes http-kit
as server.
1. Can I just ssh into the ION EC2 instance and set up the necessary python environment?
2. When deploying a :web
ion: Do I just ignore http-kit
and route the incoming request straight through my ring middleware stack, like so?
(def get-items-by-type-lambda-proxy
(apigw/ionize my-middleware-stack))
(def -main []
(start-dev-server-normally)
your web ion points to the ionize
ed handler, where as an http-direct connection points to your standard, unionized handler
the ec2 instance(s) that run datomic are intended to be ephemeral and replaceable, i would definitely recommend against modifying their environments directly
I see, any other ideas than on how to achieve my requirements? Further down the line we might even have the need for EC2 instances with GPU's for some machine learning and rendering tasks. I'd love to have it all neatly packaged in an ion, so we don't have to mess with all the AWS setups ourselves
@rob703 consider putting your python code to separate environment and interact via lambdas
I did consider this yesterday evening, it just looses the charm of being able to work with the code through clojure. Setting up a completely separate python environment and accessing it via remote calls just isn't the same as simply using it directly. But yes, if all things fail that will be our workaround. It won't be too bad, but I still hope someone comes up with another solution