Re: [Nfs-ganesha-devel] Multi instance Ganesha with DBus

2017-10-03 Thread Daniel Gryniewicz 
So, from what I've seen, it's possible to run a dbus inside a container. 
 You need to start it from your entrypoint script.  I've done this in 
the past, but not for several years.


That said, this may be a legit reason to add multiple bus keys.  I can 
see wanting to control them from outside, but I can also see wanting to 
control them from inside, so we should probably support both modes.


Daniel

On 10/03/2017 01:27 PM, sriram patil wrote:
I am running ganesha inside docker containers. I have tried to run dbus 
inside docker, but that fails because system_bus_socket does not exist. 
This is the actual problem.


To solve this, I am using the host dbus server from containers by 
mounting the host system_bus_socket inside the containers. So, all 
ganesha servers will register with the host dbus. This is why I need 
different bus names for every ganesha server running inside containers.


Thanks,
Sriram

On 03-Oct-2017 5:35 PM, "Daniel Gryniewicz" > wrote:


On 10/03/2017 02:31 AM, sriram patil wrote:

Hi,

AFAIK we can run only single instance of nfs-ganesha on a given
machine which supports dbus signals. Running with different
ports, nfs
ganesha service comes up, but the dbus signals work only for the
first
(primary) instance. We cannot interact with the ganesha instances
(other than primary) through dbus. This is a big deal, because
dynamic
exports, runtime grace periods, stats, etc are not available on
"secondary" ganesha instances.

I wanted to know if this is an issue at all? And is there anyone
working on this already?

Of the top of my head, I am thinking of handling this by adding an
identifier configuration which can be appended to the bus name. For
example, org.ganesha.nfsd.id1, org.ganesha.nfsd.id2, etc. Any
suggestions on this approach? Can we handle it in a better way?


Just out of curiosity, what's the use-case for multiple Ganesha's on
the same machine, as opposed to just putting all the exports on the
same Ganesha?

Daniel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel





--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Multi instance Ganesha with DBus

2017-10-03 Thread sriram patil 
I am running ganesha inside docker containers. I have tried to run dbus
inside docker, but that fails because system_bus_socket does not exist.
This is the actual problem.

To solve this, I am using the host dbus server from containers by mounting
the host system_bus_socket inside the containers. So, all ganesha servers
will register with the host dbus. This is why I need different bus names
for every ganesha server running inside containers.

Thanks,
Sriram

On 03-Oct-2017 5:35 PM, "Daniel Gryniewicz"  wrote:

> On 10/03/2017 02:31 AM, sriram patil wrote:
>
>> Hi,
>>
>> AFAIK we can run only single instance of nfs-ganesha on a given
>> machine which supports dbus signals. Running with different ports, nfs
>> ganesha service comes up, but the dbus signals work only for the first
>> (primary) instance. We cannot interact with the ganesha instances
>> (other than primary) through dbus. This is a big deal, because dynamic
>> exports, runtime grace periods, stats, etc are not available on
>> "secondary" ganesha instances.
>>
>> I wanted to know if this is an issue at all? And is there anyone
>> working on this already?
>>
>> Of the top of my head, I am thinking of handling this by adding an
>> identifier configuration which can be appended to the bus name. For
>> example, org.ganesha.nfsd.id1, org.ganesha.nfsd.id2, etc. Any
>> suggestions on this approach? Can we handle it in a better way?
>>
>>
> Just out of curiosity, what's the use-case for multiple Ganesha's on the
> same machine, as opposed to just putting all the exports on the same
> Ganesha?
>
> Daniel
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

[Nfs-ganesha-devel] Multi instance Ganesha with DBus

2017-10-03 Thread sriram patil 
Hi,

AFAIK we can run only single instance of nfs-ganesha on a given
machine which supports dbus signals. Running with different ports, nfs
ganesha service comes up, but the dbus signals work only for the first
(primary) instance. We cannot interact with the ganesha instances
(other than primary) through dbus. This is a big deal, because dynamic
exports, runtime grace periods, stats, etc are not available on
"secondary" ganesha instances.

I wanted to know if this is an issue at all? And is there anyone
working on this already?

Of the top of my head, I am thinking of handling this by adding an
identifier configuration which can be appended to the bus name. For
example, org.ganesha.nfsd.id1, org.ganesha.nfsd.id2, etc. Any
suggestions on this approach? Can we handle it in a better way?

Thanks,
Sriram

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel