Re: [lxc-users] ustuehler's lxc-desktop package

[Simos Xenitellis]

On Sat, Sep 3, 2016 at 5:05 PM, brian mullan  wrote:
> Dan
>
> I'd seen that same github on the lxc-desktop by Uwe Stuehler and tried to
> figure out how to contact him but had no luck (his email isn't on his github
> page).
>
> So I added some info to one of my "issues" I'd created on Uwe's GitHub:
> https://github.com/ustuehler/lxc-desktop/issues/12
>

You can clone his repository at https://github.com/ustuehler/lxc-desktop/
and then type "git log" in there. You will be able to see the email address,
since it was used for the commits.

Simos

> Assuming what I posted there solves the sticking points he had around a
> pre-start hook for LXD to set audio/video devices from the Host into the
> containers
> then that would only leave the effort of creating an lxd template for it
> which I don't have any experience with so not sure of how much work that
> would be.
>
> Brian
>
>
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] inventory / dashboard tool to manage LXD containers' lifecycle

[Tilak Waelde]

Haven't used it yet, but isn't there:
https://docs.ansible.com/ansible/lxd_container_module.html


On 09/05/2016 12:03 PM, Mark Constable wrote:
> On 05/09/16 19:38, Nicola Volpini wrote:
>> As per subject: is there any existing project able to manage the 
>> lifecycle of LXD containers via some form of frontend/webgui?
>> [...] 
>> Anyone out there who managed to integrate these tools and LXD? I
>> would be cool to do for LXD what has been done for VMs.
> 
> Absolutely a huge ++1 from me.
> 
> For a systemd based OS, this is in the ballpark if the LXD API was
> added to the Docker smarts...
> 
> https://github.com/cockpit-project/cockpit
> 
> If Cockpit was a Go based project I would have got more involved.
> If there is nothing more advanced then this could make for a good
> starting point, FWIW...
> 
> https://github.com/lxc/lxd-demo-server
> 
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
> 
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] inventory / dashboard tool to manage LXD containers' lifecycle

[brian mullan]

Michael DeHaan was the creator of both Cobbler and Ansible and he lives in
the same city as I do (Raleigh  NC).

I'd met Michael when he briefly worked at Cisco Systems a few years ago and
over lunch I'd talked to him about some of my work with (at the time) LXC.

Michael and already moved on from Cobbler and had just developed what
became Ansible.

Anyway.. a year ago he posted his thoughts on LXC after using it for a
while:

http://michaeldehaan.net/post/111599240017/skipping-docker-for-lxc-for-local-development

I'd also like to throw this out there.   A year or so ago I'd learned about
Rundeck.

http://rundeck.org/docs/manual/introduction.html

Rundeck is used by folks like Disney, Salesforce, etc/

I installed & used Rundeck for a short time just to see how it worked and
felt that it would make a great LXC & now LXD orchestration/provisioning
system.I kept meaning to go back and spend some more time with it but
other projects diverted my short attention span :-)

The Rundeck "tutorials" 
would should give you an idea why...

Rundeck could easily be adapted to LXD's* command line* syntax.

But someone more technically inclined than me I believe could also create
an LXD JSON plugin for Rundeck's Plugin API ecosystem
  that would also make management of
LXD containers (remotely or locally) easy.

Rundeck does support the concept of "roles" so that too could enable "user"
vs "admin" type LXD jobs to be developed.

Anyway, I thought I'd mention it as Rundeck's Web interface is easy and (to
me) it seemed a good fit for use with LXD.

Brian
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] inventory / dashboard tool to manage LXD containers' lifecycle

[Mark Constable]

On 05/09/16 19:38, Nicola Volpini wrote:
> As per subject: is there any existing project able to manage the 
> lifecycle of LXD containers via some form of frontend/webgui?
> [...] 
> Anyone out there who managed to integrate these tools and LXD? I
> would be cool to do for LXD what has been done for VMs.

Absolutely a huge ++1 from me.

For a systemd based OS, this is in the ballpark if the LXD API was
added to the Docker smarts...

https://github.com/cockpit-project/cockpit

If Cockpit was a Go based project I would have got more involved.
If there is nothing more advanced then this could make for a good
starting point, FWIW...

https://github.com/lxc/lxd-demo-server

___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] inventory / dashboard tool to manage LXD containers' lifecycle

[Rémy Dernat]

Hi,

This is quite Interesting. I think Juju can do that :
https://insights.ubuntu.com/2015/06/17/12-questions-about-juju/

However I am quite interesting in such a thing too, but more "SaltStack"
oriented than Ansible ;)

Best regards,
Rémy

2016-09-05 11:38 GMT+02:00 Nicola Volpini :

> Hello, everyone.
>
> As per subject: is there any existing project able to manage the
> lifecycle of LXD containers via some form of frontend/webgui?
>
> I am very pleased by what Foreman can do for VMs: It can assign a random
> or predictable hostname, deploy a VM on a host of choice (or in the
> cloud), kickstart/preseed it and then keep track of its existence for
> all its life. When done with the vm it can be destroyed and removed from
> the database.
> Ansible tower is providing a very similar feature via system tracking
> and even allowing the users to setup their own hosts via self-service
> (surveys).
>
> I am not aware of any support to LXD provided by Foreman and Ansible,
> and I am honestly surprised since LXD is such a powerful piece of
> technology.
>
> Anyone out there who managed to integrate these tools and LXD? I would
> be cool to do for LXD what has been done for VMs.
>
> Thanks!
> Nicola
>
>
> CONFIDENTIALITY NOTICE: This email message (and any attachment) is
> intended only for the individual or entity to which it is addressed. The
> information in this email is confidential and may contain information that
> is legally privileged or exempt from disclosure under applicable law. If
> you are not the intended recipient, you are strictly prohibited from
> reading, using, publishing or disseminating such information and upon
> receipt, must permanently delete the original and destroy any copies. We
> take steps to protect against viruses and other defects but advise you to
> carry out your own checks and precautions as Kambi does not accept any
> liability for any which remain. Thank you for your co-operation.
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

[lxc-users] inventory / dashboard tool to manage LXD containers' lifecycle

[Nicola Volpini]

Hello, everyone.

As per subject: is there any existing project able to manage the
lifecycle of LXD containers via some form of frontend/webgui?

I am very pleased by what Foreman can do for VMs: It can assign a random
or predictable hostname, deploy a VM on a host of choice (or in the
cloud), kickstart/preseed it and then keep track of its existence for
all its life. When done with the vm it can be destroyed and removed from
the database.
Ansible tower is providing a very similar feature via system tracking
and even allowing the users to setup their own hosts via self-service
(surveys).

I am not aware of any support to LXD provided by Foreman and Ansible,
and I am honestly surprised since LXD is such a powerful piece of
technology.

Anyone out there who managed to integrate these tools and LXD? I would
be cool to do for LXD what has been done for VMs.

Thanks!
Nicola


CONFIDENTIALITY NOTICE: This email message (and any attachment) is intended 
only for the individual or entity to which it is addressed. The information in 
this email is confidential and may contain information that is legally 
privileged or exempt from disclosure under applicable law. If you are not the 
intended recipient, you are strictly prohibited from reading, using, publishing 
or disseminating such information and upon receipt, must permanently delete the 
original and destroy any copies. We take steps to protect against viruses and 
other defects but advise you to carry out your own checks and precautions as 
Kambi does not accept any liability for any which remain. Thank you for your 
co-operation.
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] IPTABLES isolation

[Fajar A. Nugraha]

On Mon, Sep 5, 2016 at 5:23 AM,  wrote:

> Hello !
>
> Probably someone knows about iptables. If I use a LXC based VM,
> I am sharing the host iptables with the VM. But I do not understand
> the scenario in full. Waht myke my basic running is, that I
> initialized the required modules on the host side (at its start),
> so the LXC VM is finding already loaded modules.
>
>
It should work.

I currently have an openvpn container, running unprivileged under lxd,
using lxdbr0's ip address (i.e. 10.0.3.x).
- the HOST forwards openvpn traffic (using iptables) to the container
- the container has its own IP range for openvpn clients (172.16.122.x)
- the container nat/masquarade traffic from openvpn clients, using its own
iptables
- "iptables-save" on the host and that returns different entries, as if
both are separate machines.

-- 
Fajar
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users