amsoil
play

AMsoil The glue for Aggregate Manager developers (radio edit) - PowerPoint PPT Presentation

Jan 26, 2024 •238 likes •535 views

AMsoil The glue for Aggregate Manager developers (radio edit) OpenFlow in Europe: Linking Infrastructure and Applications 2 3 Years, ending Sept. 13 OFELIA FP7 project in numbers 6.5 Budget 4.45 Funding 10

  1. AMsoil The glue for Aggregate Manager developers (radio edit)

  2. OpenFlow in Europe: Linking Infrastructure and Applications 2

  3. 3 Years, ¡ending ¡Sept. ¡’13 OFELIA ¡FP7 ¡project ¡in ¡numbers 6.5 ¡€ Budget 4.45 ¡€ Funding 10 Partners 12 a>er ¡the ¡1 st ¡OpenCall 17 a>er ¡the ¡2 nd ¡OpenCall 7 OpenFlow ¡islands Development and Experimentation on Hagen Woesner federated EU-Japan Testbeds

  4. 4

  5. phases 2010 2013 5

  6. AMsoil The glue for Aggregate Manager developers (radio edit)

  7. components 7

  8. AMsoil? Someone needs to implement this! 8

  9. motivation AM development without AMsoil Resource Mgmt Other stuff 9

  10. motivation AM development with AMsoil Extend AMsoil Learn AMsoil Resource Mgmt 10

  11. AMsoil? “ AMsoil is a light-weight framework for creating Aggregate Managers in test beds. AMsoil is a pluggable system and provides the necessary glue between RPC-Handlers and Resource Managers . Also it provides helpers for common tasks in AM development. 11

  12. what we need to know • how plugins work • what plugins you need to develop • what else AMsoil supports • how a GENI testbed works 12

  13. why plugins? • Selection An administrator can add/remove plugins/functionality. • Exchangeability The interface remains, but the implementation be changed. • Clarity Provide a set of services and hide the details behind. • Encapsulation Protect implementations from other developers.  plugin 13

  14. register and use plugins  plugin 14

  15. under the hood  plugin 15

  16. implement a plugin • create a new folder in plugins • create the manifest.json • create the plugin.py • write a setup() method • register your services  plugin 16

  17. handling the AM API or how to develop a GENI AM API v3 Aggregate 17

  18. getting the requests  GENI 18

  19. getting the requests why so complicated?  GENI 18

  20. interfaces • Delegate Should derive from DelegateBase and overwrite the methods prescribed (e.g. list_resources, allocate, ...) . • Resource Manager You make up the interface! The methods, attributes, parameters are domain-specific and depend on the resource type being handled.  GENI 19

  21. interfaces • Delegate FIXED Should derive from DelegateBase and overwrite the methods prescribed (e.g. list_resources, allocate, ...) . • Resource Manager FLEXIBLE You make up the interface! The methods, attributes, parameters are domain-specific and depend on the resource type being handled.  GENI 19

  22. needed knowledge 20

  23. hands on tips Let’s see how we can make our life even easier. 21

  24. configuration anywhere.py import amsoil.core.pluginmanager as pm config = pm . getService("config") # get the service myvalue = config . get("mygroup.mykey") # retrieve a value config . set("mygroup.mykey", myvalue) # set a value  configuration 22

  25. persistence vs. SQLAlchemy tutorial Need to know 7900 words 926 words  persistence 23

  26. 24

  27. coming up • GENI AM API v2 • Calendarization • Policy Engine integration • Clearinghouse • lot’s more developers 25

  28. check it out clone the repository  https://github.com/fp7-ofelia/AMsoil.git then read the wiki and start with the quick-start  https://github.com/fp7-ofelia/AMsoil/wiki 26

Recommend

More recommend