maas-devel team mailing list archive

[Graham Binns <graham.binns@xxxxxxxxxxxxx>]

On 27 August 2014 13:34, Julian Edwards <julian.edwards@xxxxxxxxxxxxx>
wrote:

>
> > For now the primary goal with RPC is to remove Celery and RabbitMQ
> > from the stack, and I think we'd be better served by adding a single
> > new RPC call to the region, GetSecrets (say), so we can continue to
> > use the API from clusters.
>
> Urgh.....


That said, ISTM kind of odd to be reimplementing a lot of stuff to not use
the API when we have a perfectly functioning API _which we're not going to
remove_.

Consider, in provisioningserver.dhcp.detect we have
`determine_cluster_interfaces()`, which just calls
api/1.0/nodegroups/<nodegroup_uuid>/interfaces/list to get the interfaces
on the cluster. Do we really want to add YARPC just for the sake of that?
We're going to potentially find more and more of these as we go, so we
should either declare API off-limits altogether for cluster->region comms
or we shouldn't spend time reimplementing APIs that don't need to be
reimplemented. Word from God now would be beneficial to avoid flapping
later.