Hi Milindu,
Thanks for the update! You can use the following information for the
setup.py description.
author=Apache Stratos
author_email=dev@stratos.apache.org
description=CLI tool to interact with Apache Stratos
url=http://stratos.apache.org
How about having 'stratos-cli' instead of just 'stratos'?
On May 9, 2015 9:40 PM, "Milindu Sanoj Kumarage" <agentmili...@gmail.com>
wrote:
>
> Sorry I missed this. This is my fork's URL
>
>
> https://github.com/agentmilindu/stratos/tree/python-cli/components/org.apache.stratos.python.cli/src/main/python
>
>
> On Sat, May 9, 2015 at 9:37 PM, Milindu Sanoj Kumarage <
> agentmili...@gmail.com> wrote:
>
>> Hi,
>>
>> I started coding, did the basic stuffs.
>>
>> I have separated the Python CLI into 3 main parts for the moment and
>> those are,
>>
>> 1. Main.py - This contains the entry point, it does the initializing
>> parts, creates a CLI instance and runs the loop and other stuffs.
>> 2. CLI.py - This is the actual CLI that extends Cmd2. This contains the
>> command to def mappings, argument and flag handling, printing outputs, etc.
>> 3. Stratos.py - This contains the actual business logic, that is, which
>> REST end point to call, and do what with the response, what to show, what
>> not, etc. At the end, this would be like a Python API for Stratos in a way.
>>
>> I'm studying the REST API for a way to generalizes the REST call
>> handling, specially on status codes and exception handling.
>>
>> I need some advice on what to put on setup.py for the following
>>
>> author=?,
>> author_email=?,
>> description=?,
>> url=?,
>>
>> I have setup-ed the setup.py. Now we can build and install Stratos CLI
>> by,
>>
>> $ python setup.py build
>> $ python setup.py install
>>
>> or use
>>
>> $ python setup.py develop
>>
>> instead install for developing
>> To start the Python CLI you can issue,
>>
>> $ stratos
>>
>>
>> Then it will start Stratos CLI, for the moment, it does not has any
>> Stratos commands.
>>
>>
>> And I was able to get up and running with Stratos on Kubernetes, I have
>> to play with it more.
>>
>>
>>
>> On Fri, May 1, 2015 at 10:23 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> It was good to have the Hangout Milindu! Thanks for joining!
>>>
>>> Please keep your remote Git repository up to date with the changes you
>>> do and it would be wise to add some documentation may be using a gist or a
>>> README.md file.
>>>
>>> As we discussed in the meeting please try to draw a high level
>>> architecture diagram for the Python CLI.
>>>
>>> Thanks
>>>
>>> On Fri, May 1, 2015 at 8:17 PM, Chamila De Alwis <chami...@wso2.com>
>>> wrote:
>>>
>>>> Thanks for the update Milindu! Could you point us to your Stratos fork?
>>>>
>>>>
>>>> Regards,
>>>> Chamila de Alwis
>>>> Software Engineer | WSO2 | +94772207163
>>>> Blog: code.chamiladealwis.com
>>>>
>>>>
>>>>
>>>> On Fri, May 1, 2015 at 5:30 PM, Milindu Sanoj Kumarage <
>>>> agentmili...@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I had a Google Hangout session with Chamila and Imesh yesterday. We
>>>>> discussed on how to push the commits. We agreed to use a separate branch
>>>>> on my Stratos fork. Therefor I created a branch as 'python-cli' after
>>>>> checking other branches for branch naming convention used. In this branch
>>>>> I
>>>>> added a directory as 'org.apache.stratos.python.cli' under the
>>>>> 'components'
>>>>> directory. I will be working on this directory.
>>>>>
>>>>> It was suggested to use the existing integration tests, I'll check how
>>>>> we can get them test the Python CLI.
>>>>>
>>>>> I will push my changes regularly, and will send a weekly update
>>>>> summarizing the work done in the week.
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Senior Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>
