watch out for architecture dependent charms

[Gustavo Niemeyer]

Hi Mark,

> Just a note for charm-craft (writing, reviewing, and testing)... ran across
> an architecture-dependent bug while reviewing a charm.  No real surprise...
> the charm downloads binary bits.
>
> Charm authors/reviewers, please watch out for such things.

That's a good point, and a known edge we have to sort out eventually.

> Our automated test framework should at least tag charms according to which
> architectures they pass tests against. (?)

The responsibility should probably reversed: the testing framework
should run tests only on the architectures that the charms have been
_declared_ to run on.

We still have to nail down details of how the architecture tagging
works, because this impacts other areas too. For instance, we need to
deploy the charm in the right machine, of course.

We covered some strategies for that at UDS, with the file-get idea,
but it needs to be polished up.

-- 
Gustavo Niemeyer
http://niemeyer.net
http://niemeyer.net/plus
http://niemeyer.net/twitter
http://niemeyer.net/blog

-- I'm not absolutely sure of anything.