You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Cloud Admin I want to view and administer my farm of CKAN instances
in a web UI (or via a Web API) so that I can manage them easily (and have a
non-command-line user do this)
* Simple Web API and UI for adminning a cloud CKAN environment
a. e.g. Wrap the code from US 2.2 in simple JSON based Web API
b. Wrap that with simple UI that allows one to admin all CKAN instances in
a given environment
c. Upgrade, start, stop, check usage etc
* Single login to UI is OK - e.g. could even use apache/nginx login
a. Do not need multiple users and types of user
b. However, designing so that this is possible longer-term is a nice to have
The text was updated successfully, but these errors were encountered:
This will require a lot of documenting in terms of what functionality exactly is required before it's possible to determine if this needs any changes to CKAN. As it stands, and assuming that the JSON API exists for admin then this could be an entirely distinct product.
We're aiming to do this with AWS Elastic Beanstalk. It's our pragmatic, best-of-breed response to managing a cloud farm, which Amazon is much better at.
I know that one advantage of CKAN is its true open-source with no lock-in. Perhaps, the effort can focus on Dockerized CKAN, and having some generic admin APIs that can be tailored as appropriate for each PaaS/IaaS environment (AWS, Azure, OpenStack, Softlayer, Private Cloud, etc.)
ckan-multisite is starting with the simplest approach for now: http auth login, possibly with no database at all, initially. The next step should be to turn that into an API so it can be controlled by a larger system. I've created a ticket for that: datacats/ckan-multisite#8
@jqnatividad have you share progress on topic? Right now I'm working on running my CKAN instance along with other components via Docker and AWS Elastic Beanstalk. Maybe we can cooperate.
The text was updated successfully, but these errors were encountered: