[Container-tools] RFC: Design of next generation vagrant-adbinfo

[Brian (bex) Exelbierd]

Unfortunately during the repo move, the issue was deleted.

I will recreate the issue as soon as possible.

regards,

bex

> On Feb 10, 2016, at 12:44 PM, Lalatendu Mohanty <lmohanty at redhat.com> wrote:
> 
> On 02/10/2016 05:03 PM, Pete Muir wrote:
>> URL is broken.
> 
> The repo moved to https://github.com/projectatomic/vagrant-service-manager. But I can't find the issue about design of sub commands.
> 
>> 
>> On 8 February 2016 at 13:13, Lalatendu Mohanty <lmohanty at redhat.com> wrote:
>>> The next generation of vagrant-adbinfo i.e. vagrant-service-manager [1] is
>>> being designed with below objectives.
>>> 
>>> To provide the user a CLI to configure the ADB/CDK for different use cases
>>> and to provide glue between ADB/CDK and the user's developer environment.
>>> 
>>> Currently we use a couple of Vagrantfiles and the vagrant-adbinfo plugin to
>>> create these links/configuration changes. However these methods require the
>>> user to change Vagrantfiles based on their needs and to manually do few
>>> things.
>>> 
>>> Provide users a tool to control and configure the ADB/CDK from the
>>> developer's workstation without having to `ssh` into the ADB.
>>> 
>>> 
>>> The new Vagrant plugin i.e. vagrant-service-manager will have sub commands
>>> and here is the current plan[1] . Let us know if you have some suggestion.
>>> 
>>> [1] https://github.com/navidshaikh/vagrant-service-manager/issues/1
>>> 
>>> Thanks,
>>> Lala
>>> 
>>> _______________________________________________
>>> Container-tools mailing list
>>> Container-tools at redhat.com
>>> https://www.redhat.com/mailman/listinfo/container-tools
>>> 
> 
> _______________________________________________
> Container-tools mailing list
> Container-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/container-tools