Marketplace
Move marketplace code in sampleresource bundle to vnmapper bundle.
Use own resource, capabilities and commands IDs in vnmapper.

Resource type is: 	vnmapper
Capability type is: 	vnmapping
Shell command is: 	vnmapping:mapvn

Notice: Existing examples should be updated to use these new values.
Restore original sampleresource bundle.

Restore done from version v0.14.
Merge commit 'v0.17' into marketplace

Conflicts:
	extensions/bundles/pom.xml

- Conflicts solved.
- Updated parent version to 0.17 in extensions/bundles/vcpemapper/pom.xml.
Fix VNTMapper vnode selection.

Fix method to select the next virtual node who has the maximum number of connection to the already mapped vnodes.

Patch provided by Bo Peng (University of Bristol)
Merge pull request #553 from isartcanyameres/marketplace

Fix VNTMapper vnode selection.
Initial commit
GIM implementation and APC PDU driver as delivered by TSSG.

The current driver is configured for the PDU in Dublin and works fine here,
reporting Current, Voltage, Power and Energy at the PDU level.
It also turns on and off the specified outlet and reports its status.
This has been validated against the values/statuses reported through the PDUs web front-end.

Please note though that the PDU does not seem to support outlet-level reporting of current, power, etc.
This would need to be taken into consideration if reporting the metrics for an individual router/device.
Put the driver in a maven project shape.

- Created pom.xml with snmp4j dependency.
- Moved all code to src/main/java folder
- Moved Test.java to src/test/java folder

Added .gitignore file.
[maven-release-plugin] prepare for next development iteration
Merge pull request #556 from maneljara/develop

Develop
Capability and command refactor:

 - Capability accepts the VNTRequest instead of the file url and the InPNetwork.

 - InPNetwork is built in capability, not in command.
First sample test. Refactor needed:

	- Create toString methods.
	- MappingResult extracted to a single .java.
Integrate spring-security in opennaas distribution.

To check integration is successful, I've been using sample in following url:
https://issues.apache.org/jira/browse/KARAF-785?focusedCommentId=13079628&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13079628

Notice opennaas-spring-security and war features have to be installed at boot time in order for the distribution to work properly.
All tests created + codestyle.
Added comments to requests and topologies files.
Declare classes in own .java file + refactor of methods from public to private.
Attirbutes with getters and setters. Old git references to classes removed.
Replace System.out for log.info