On Thu, Apr 24, 2014 at 04:07:16PM +1000, Julian Edwards wrote: > On 23/04/14 09:31, Julian Edwards wrote: > > On Tuesday 22 Apr 2014 11:42:57 Gavin Panella wrote: > >> No, but Tycho does care a fig, and he's speaking for the community cloud > >> installer. It needs to be able to run m-i-p-f and know that it has > >> finished. There's no good way to do that right now via the API. We > >> should add it, but in the meantime it would be sensible to preserve > >> invocation from the command-line. Also, for better or worse, m-i-p-f > >> forms part of MAAS's API, in a broad sense of the term. > > > > I'm not suggesting that we get rid of it until there's a replacement. > > > > I would be open to keeping it provided the settings are still in the DB (ie > > make it a dedicated api script). > > > > Ultimately, external systems should not be relying on internal scripts that > > are not part of the official API surface. > > It turns out that we have an API call to query available boot images, so > once the import is kicked off via the API, it can then poll for completion. > > So unless I am missing something, there's no blocker to getting rid of > the command line script?
Except if the script fails, we have no way to detect completion, and we sit in a poll loop forever. \t > > J > > -- > Mailing list: https://launchpad.net/~maas-devel > Post to : maas-devel@lists.launchpad.net > Unsubscribe : https://launchpad.net/~maas-devel > More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~maas-devel Post to : maas-devel@lists.launchpad.net Unsubscribe : https://launchpad.net/~maas-devel More help : https://help.launchpad.net/ListHelp
