LXC-Web-Panel
LXC-Web-Panel copied to clipboard
LXC Web Panel v1.0
Coming in few weeks/months
Programming (fully recoded):
- Python 3.x
- HTML5
- CSS3
- Javascript
- Bash
Frameworks:
- Python-lxc
- Bootstrap 3.x
- Flask 0.10.x
- AngularJS
New features:
- RESTful API
- Manage multiple nodes with one interface
- SSL
- SQLite / MySQL
- Users ACL system
- Containers backup
- Tasks workers ?
- ...
Developpers:
- Élie Deloumeau (back-end)
- Antoine Tanzilli (front-end)
Contributors:
- Stéphane Graber (helps me for python-lxc)
The plan looks great man! Hope to ser this soon
Who wants to help me ? Because i'm sysadmin and not dev, i can't convert these regex... https://github.com/googley/lxc-checkconfig
Have you ever thought about joining forces with the webvirtmgr project to add lxc to it and of course just improve things for both of you as a whole? You have done an amazing job with this panel and I currently use both projects, but would be even better if there was a single solution that did both! Just a thought.
No, i've not heard about it before. I want a stable version of LWP before integrate other things
I understand. Though obviously it wouldn't really be an integration. Would be more of a collaboration with their project since since it has much more features and appears to have more active contributors. Anyway, it was just an idea. Looking forward to the new release.
-Mark
----- Original Message ----- From: "Elie Deloumeau" [email protected] To: "lxc-webpanel/LXC-Web-Panel" [email protected] Cc: "MACscr" [email protected] Sent: Thursday, June 19, 2014 4:15:33 AM Subject: Re: [LXC-Web-Panel] LXC Web Panel v1.0 (#69)
No, i've not heard about it before. I want a stable version of LWP before integrate other things
Reply to this email directly or view it on GitHub: https://github.com/lxc-webpanel/LXC-Web-Panel/issues/69#issuecomment-46539188
Help/fork me please: https://github.com/googley/lxc-checkconfig
Will the current version of LWP work on the latest LXC? I use sudo when running the wget command, then I see the output "Saving to STDOUT", then the large graphic LXC WebPanel, then "Automatic Installer", then "You must be root to install LXC WebPanel".
It does not
On June 24, 2014 7:46:00 PM CDT, rayj00 [email protected] wrote:
Will the current version of LWP work on the latest LXC? I use sudo when running the wget command, then I see the output "Saving to STDOUT", then the large graphic LXC WebPanel, then "Automatic Installer", then "You must be root to install LXC WebPanel".
Reply to this email directly or view it on GitHub: https://github.com/lxc-webpanel/LXC-Web-Panel/issues/69#issuecomment-47048609
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bummer....
would multi-user ACL include ACL against different LXC containers, such that an LXC container could be "assigned" to a user, and only admins or that user could access it? That would be ideal. Also, a console feature would be very helpful, so that users could get into their machines. Here's one I found recently:
http://www.web-console.org/
Yes, actually i can add or remove containers for a user with a rule "deny" or "allow". So if you add "ct1" and "ct2" with deny rule, the user can see all containers except "ct1" and "ct2".
I'll try to set containers ACL for groups too and the more restrictive acl will be applied
For the web console, i'm not able to translate PHP to Python and i don't know how to do this by myself :s if someone want to do that... :)
I would only recommend novnc for web console access as its almost an industry standard for large virt projects (openstack, cloudstack, cloudmin, etc).
-Mark
----- Original Message ----- From: "Elie Deloumeau" [email protected] To: "lxc-webpanel/LXC-Web-Panel" [email protected] Cc: "MACscr" [email protected] Sent: Wednesday, July 9, 2014 2:43:39 PM Subject: Re: [LXC-Web-Panel] LXC Web Panel v1.0 (#69)
Yes, actually i can add or remove containers for a user with a rule "deny" or "allow". So if you add "ct1" and "ct2" with deny rule, the user can see all containers except "ct1" and "ct2".
I'll try to set containers ACL for groups too and the more restrictive acl will be applied
For the web console, i'm not able to translate PHP to Python and i don't know how to do this by myself :s if someone want to do that... :)
Reply to this email directly or view it on GitHub: https://github.com/lxc-webpanel/LXC-Web-Panel/issues/69#issuecomment-48524427
This plan is great, and I can't wait to have a web panel for lxc 1.x.
Are there any taks or is there any schedule for the work to be done? I would like to help you out, but I don't know where to start.
Hi guys :) I wonder if we could yet add other new features to the above todo list :
- Backup containers (locally and remotely via NFS for example).
- Perfom some actions (creation, cloning, etc of container(s)) in background (using workers) to avoid blocking the web application. This also should be interessting for example when we would create several containers in "parallel". I could work on these features on the current LWP version and I think it'll be easy to test code after on 1.0. what do you think?
Hi abessifi,
- Yes i look for features in lwp's forks (i will rewrite your backup function for lwp 1.0)
- GOOD IDEA I don't know how to do that and after a small google search, i see a complicated work for me (cause i'm not developer). Can do this feature for me/us ? (this feature is needed for multiple users and multiple applications using the REST API)
Push your code in a public repository, so real developers can help you.
Yes but i must write a doc EDIT : Next week maybe?
Hi googley, I'm not a developer too, however I like contribute with some code snippets to some smart projects ;)
I would agree with @alexkn. It would be nice to see the code, so we can start helping, even if the doc is missing.
I am willing to help aswell I have a simluar (less featurefull) project https://github.com/grimpy/lxcweb which works with lxc 1.0.
When source is available i can help with backend code (I dont do frontend stuf fmuch)
@googley, any updates?
@gopi-ar I'm very busy at this time, sorry...
@googley, do consider spending a few minutes pushing the whatever progress you have on the code to a branch. And possibly add @claudyus as a maintainer; he's doing some great work on his fork. Shame to see an awesome project go out of date..
@googley do you have any updates?
@googley I am more than happy to help on this. Please say what's the current status and push your current code and we will help you making it beautiful and working.
Hi, current status: i'm very busy :-( What's the best solution ? :
- Stay with one repo with backend + frontend or
- Split repo with one for backend/REST API and one for frontend
Split. You'll can transform backend into something like standalone/node/SaaS with API. Frontend(s) will follow.
Hello, any news?
The backend is almost done!
Great !
Where is the code ? The last commit on this repo seems to be 6 months old.