| | 2 | |
| | 3 | = 4/24/15 = |
| | 4 | == Close to pushing to devel == |
| | 5 | * When adding an rspec ('add-topology') to an empty Jacks (only has a single site with nothing in it), the new RSpec should over-ride the previous stuff; discard the empty site |
| | 6 | * Allow requesting that a link be 'non-trivial' going through a hardware switch, such that the link can be openflow controlled and shared. EG: |
| | 7 | `<vlan_tagging xmlns="http://www.protogeni.net/resources/rspec/ext/emulab/1" enabled="true"/>` |
| | 8 | * Add a 'No MAC' checkbox on disk images |
| | 9 | * Allows user custom disk images and EG images to get the nomac flag that otherwise comes only from the constraint generator's config file |
| | 10 | * Checkbox says 'Disable MAC Discovery' and is ORed with the setting in the context |
| | 11 | |
| | 12 | == Next Items == |
| | 13 | * Resources from other AMs / merging manifests: |
| | 14 | * An IG manifest may includes components which are not from the current AM |
| | 15 | * They may even be from AMs not known to the portal |
| | 16 | * The result is |
| | 17 | * The resources listed in that manifest may have since been deleted at the "real" AM, but Jacks still shows them |
| | 18 | * If the resources exist but at an AM not in the Jacks Context and not known to the portal, then Jacks shows resources that cannot be manipulated through the portal |
| | 19 | * Action: |
| | 20 | * Option 1: Jacks should only show nodes in View mode whose component_manager matches one of the aggregates in the current Jacks context |
| | 21 | * '''Option 2''': When in view mode and receive an RSpec of type 'manifest', only show nodes from the sender aggregate (alternatively implement as only nodes with a sliver_id) |
| | 22 | * Links between AMs will need to be drawn like shared VLANs, with dangling endpoints |
| | 23 | * Status: Option 2 mostly implemented, links aren't quite handled correctly |
| | 24 | * Validate RSpec on submission |
| | 25 | * When extracting RSpec from Jacks, apply some sanity checks |
| | 26 | * See above about 'any' and constraints for default values, on links in particular |
| | 27 | * Warn on duplicated IP address |
| | 28 | * Warn on a link with 'Enable OpenFlow' checked but no controller |
| | 29 | * Status: Working on the warning system to support these checks |
| | 30 | * Duplicate constraints coming from generator |
| | 31 | * Looping over nodes and generating by AM constraint does not go through de-duping code |
| | 32 | * To do: Warn when constraint loaded detects a duplicate |
| | 33 | - Should be able to set bandwidths on links. |
| | 34 | * Will warn if RSpec tried to set different BW on on same interface for 2 different destinations but pick the first |
| | 35 | |
| | 36 | == Other Items == |
| | 37 | * Constraints |
| | 38 | * If only a GRE tunnel is a valid link type, leaving the link type as 'any' will fail when you reserve |
| | 39 | * 'any' is treated as stitched by stitcher and the AMs, but stitched constraints are not applied by Jacks |
| | 40 | * Perhaps check all 'any' attributes and apply constraints as though the default (whatever that is) was selected? |
| | 41 | * Perhaps only on submission? |
| | 42 | * Action: If a link type is 'any' and the endpoints do not allow LAN or VLAN, then this is a warning (so the experimenter can pick GRE for example) |
| | 43 | * Visible indication of what is not allowed when dragging on palette (the warning system) |
| | 44 | * Ethernet/LAN should not be an option between sites |
| | 45 | * Jacks bug that constraints don't realize that a 2nd site cannot be same as a first site |
| | 46 | * Note though that if you pick ethernet and stitched ethernet is right, the right thing still happens |
| | 47 | * Stitched/VLAN and ExoGENI stitching don't work well together |
| | 48 | |
| | 49 | == Portal Items == |
| | 50 | * Deleting resources from Jacks leaves Jacks with a non-empty canvas: http://grab.by/G8Fa |
| | 51 | * Portal: Expanded editor fails to load in some situations |
| 29 | | * Resources from other AMs / merging manifests: |
| 30 | | * An IG manifest may includes components which are not from the current AM |
| 31 | | * They may even be from AMs not known to the portal |
| 32 | | * The result is |
| 33 | | * The resources listed in that manifest may have since been deleted at the "real" AM, but Jacks still shows them |
| 34 | | * If the resources exist but at an AM not in the Jacks Context and not known to the portal, then Jacks shows resources that cannot be manipulated through the portal |
| 35 | | * Action: |
| 36 | | * Option 1: Jacks should only show nodes in View mode whose component_manager matches one of the aggregates in the current Jacks context |
| 37 | | * Option 2: When in view mode and receive an RSpec of type 'manifest', only show nodes from the sender aggregate (alternatively implement as only nodes with a sliver_id) |
| 38 | | * Links between AMs will need to be drawn like shared VLANs, with dangling endpoints |
| 39 | | * When adding an rspec ('add-topology') to an empty Jacks (only has a single site with nothing in it), the new RSpec should over-ride the previous stuff; discard the empty site |
| 40 | | * Allow requesting that a link be 'non-trivial' going through a hardware switch, such that the link can be openflow controlled and shared. EG: |
| 41 | | `<vlan_tagging xmlns="http://www.protogeni.net/resources/rspec/ext/emulab/1" enabled="true"/>` |
