Will Foster

> As opposed to prompting the user when a schedule is being added to hosts where the target cloudXX was already released why not just auto-convert a cloudXX environment upon...

> having an --auto-no-wipe is a simple fix to help to automate the process, so that you won't have to answer a prompt or pass a -y argument to add-schedule....

As both changes have merit, we'll track/implement the more core argparse `--auto-no-wipe` command enhancement in a separate RFE #360 so our change-sets are a little smaller.

The following patchset provides the visible provisioning and move status indicators as a percentage on the assignments page: https://review.gerrithub.io/c/redhat-performance/quads/+/463515 We still need to discuss, architect and implement the following: 1)...

Closing this, the scope has changed to only provide visual progress status on assignments page, we will accomplish the granularity break-out here with a proper asyncio implementation as noted here:...

After some further discussion we're re-opening this as some elements can be implemented that compliment asyncio here: https://review.gerrithub.io/c/redhat-performance/quads/+/463871

There are elements of this RFE that can/should be implemented post-asyncio, pushing this to 1.2 milestone.

This seems like a solid improvement. In our documentation examples we tend to prefer shell ```for loops``` for running multiple ```--add-schedule``` commands across a set of disparate hosts. I think...

> On Thu, Sep 13, 2018 at 9:42 AM Kambiz Aghaiepour ***@***.***> wrote: I like this idea. Currently what happens when a single host schedule request cannot be fulfilled due...

Thanks for opening this @smalleni. We're working directly with @radez on getting this tested and implemented as he's working on Ansible Networking. Let's leave this open and use it to...