Hi Malahal,
As your change is already merged in next branch, is it possible to use this
command line interface somehow?
If yes can you please provide a small example on how to use it.
Thanks,
Supriti
On Tue, Mar 7, 2017 at 2:14 AM, Malahal Naineni <[email protected]> wrote:
> One line change to allow path! I will add it. Yes, it will pick the first
> export with the given key (if there are multiple).
>
> Regards, Malahal.
>
> On Mar 6, 2017 11:54 PM, "Frank Filz" <[email protected]> wrote:
>
>> In a non-NFSv4 environment where the flag to switch NFS v3 and 9P mount
>> to use Pseudo, Path SHOULD be unique (it could still be non-unique if Tag
>> is used), so you could allow Path, and just return error is Path is not
>> unique (actually, we will just find the first export with that Path, so
>> could still work). You could also allow specification by Tag, on the other
>> hand, with the new config to use Pseudo, I’d love to deprecate Tag.
>>
>>
>>
>> Frank
>>
>>
>>
>> *From:* Malahal Naineni [mailto:[email protected]]
>> *Sent:* Monday, March 6, 2017 5:08 AM
>> *To:* [email protected]
>> *Cc:* [email protected]
>> *Subject:* Re: [Nfs-ganesha-devel] ganesha config editor user interface
>> thoughts
>>
>>
>>
>> Yes, it makes sense while creating for sure. Someone needs to remember
>> the exportid while changing an entry that was created before. So I added
>> exportid and pseudo for now. We can add anything later. "export export_id
>> 14" and "export pseudo /root/exp1" are valid specifications now
>>
>>
>>
>>
>>
>> On Mar 6, 2017 6:30 PM, "Daniel Gryniewicz" <[email protected]> wrote:
>>
>> Isn't export_id the only actual always-required unique key? Maybe just
>> use that?
>>
>> Daniel
>>
>> On 03/05/2017 11:39 PM, Malahal Naineni wrote:
>> > Posted a patch that works at gerritio. It just creats blocks and key
>> > value pairs without checking if they constitute a valid ganesha config
>> > block. Currently, "export" block takes "pseudo value" and "client
>> > block takes "clients-value" as additional arguments. pseudo may not be
>> > used in NFSv3 only environments (not sure about 9P).
>> >
>> > I am thinking to support "pseudo", "path" or "export_id" as well. So
>> > to change an export block that has export id as 16, one would do
>> > "ganesha_conf set export export_id 16 --param1 value1 --param2
>> > value2". If one wants to use pseudo instead, it can be done as
>> > "ganesha_conf set export pseudo /nfsroot/spath1 value1 --param2 value2"
>> >
>> > I am thinking of allowing "export_id", "pseudo" and "path" keys for
>> > "export" block identification. We only use "clients" for the client
>> > block, but to be consistent with the export block, we will have
>> > "ganesha_conf export export_id 16 client clients 192.168.1.0 --param1
>> > --value" to change the corresponding "client" block.
>> >
>> > Any suggestions or issues with this approach?
>> >
>> > Regards, Malahal.
>> >
>> > On Mon, Feb 27, 2017 at 2:45 PM, Dominique Martinet
>> > <[email protected]> wrote:
>> >> Malahal Naineni wrote on Sat, Feb 25, 2017 at 03:33:17PM +0530:
>> >>> - All config is in blocks
>> >>> - Most blocks are unique with their tag names
>> >>> - exceptions: "export" and "client" blocks.
>> >>> - "export" is unique by "path" value
>> >>
>> >> More like unique by pseudo path; path can be identical for various
>> >> reasons (e.g. exporting the same backend multiple times with different
>> >> options)
>> >>
>> >>> - "client" is unique by "clients" value with in the export block.
>> >>> - Log blocks have few subblocks.
>> >>
>> >> export can also have an arbitrary number of sub-blocks (for FSAL and
>> >> stackable FSALs); I think the syntax here should be generic enough and
>> >> recursively handled e.g. maybe
>> >> ganesha_config set blockname.subblock[.subblock[...]] key value
>> >>
>> >> --
>> >> Dominique
>> >
>> > ------------------------------------------------------------
>> ------------------
>> > 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
>> > [email protected]
>> > 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
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>>
>>
>>
>> ------------------------------
>> [image: Avast logo] <https://www.avast.com/antivirus>
>>
>> This email has been checked for viruses by Avast antivirus software.
>> www.avast.com <https://www.avast.com/antivirus>
>>
>>
> ------------------------------------------------------------
> ------------------
> Announcing the Oxford Dictionaries API! The API offers world-renowned
> dictionary content that is easy and intuitive to access. Sign up for an
> account today to start using our lexical data to power your apps and
> projects. Get started today and enter our developer competition.
> http://sdm.link/oxford
> _______________________________________________
> Nfs-ganesha-devel mailing list
> [email protected]
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
