Attribute matches on RSPEC and AM

[MarshallBrinn]

We should add a feature to the portal that tags AM's with attributes they have and RSPEC's with attributes they require. That way, we can show only the right RSPEC's for a given AM.

This whole thing can be arbitrarily complicated (ands of ors of nots). So I suggest we use a simple fixed list of scalar properties and require a full 'AND' match (every attribute of the RSPEC is required to be on the AM).

Here are a first cut at possible scalars
INSTAGENI
EXOGENI
VM
BARE_METAL

Imported from trac ticket #494, created by mbrinn on 04-27-2013 at 11:35, last modified: 04-29-2013 at 09:12

[MarshallBrinn]

Additionally we can use the scheme of rspec attributes to tag some as being 'mine' or 'public/private' so that we can limit which are shown in menus on the portal.

Trac comment by mbrinn (github user: MarshallBrinn) on 04-27-2013 at 11:36

[ahelsing]

Possible scalars probably should include the valid values for geni_am_type in the AM API

http://groups.geni.net/geni/attachment/wiki/GAPI_AM_API_V3/CommonConcepts/geni-am-types.xml

In particular, that lets us see anything that is protogeni based as similar. And lets us distinguish openflow aggregates.

We will also want a tag for AMs that can do stitching.
And a tag for AMs that should be hidden from the UI dropdown maybe? Like the ION AM?

We will also want a tag to distinguish the ExoSM from the other ExoGENI AMs maybe?

Trac comment by ahelsing on 04-29-2013 at 09:02

[MarshallBrinn]

Do we need or want to distinguish between attributes that are and aren't available in the advertisement RSPEC?

The 'hidden' tag for ION is not something ION will know or provide but is a portal/clearinghouse designation.

But stitching, e.g., is something I can learn from the Advert.

Good point about EXO SM and EXO AM.

• Marshall

Trac comment by mbrinn (github user: MarshallBrinn) on 04-29-2013 at 09:12